08:12 <jcarlos> naobsd: Yes, I thought about those two options, but option one scares me, and option two is not clear enough for me. Your multiboot.img file is rkcrc'ed signed. I have your mkbootimg command compiled. I know I can create an image with it. But I'm not sure I can use your signed ramdisk. Must I unsigned it before create de packed image (my kernel+your ramdisk) ? If that is the case, how can I unsign it? Or does the mkbootimg command

08:12 <jcarlos> take into account the signed ramdisk and creates a final correct image?

08:24 <jcarlos> By the way, my kernel is 8,4M sized, and my kernel partition has 8M ...

09:17 <karlp> how is your kernel 8.4meg?

09:18 <karlp> is that just a kernel or a kernel+?

09:27 <jcarlos> karlp: Well, that's the size.

09:28 <jcarlos> I have rechecked it just now.

09:32 <jcarlos> karlp: Obviously I'm talking about my stock kernel, not a kernel compiled by me.

09:32 <jcarlos> An Android kernel.

21:27 <naobsd> jcarlos: don't mix different thing, anything about kernel+ramdisk image and about kernel-only/ramdisk-only image are unrelated

21:28 <jcarlos> naobsd: I don't understand what you are trying to tell me :/

21:28 <naobsd> you can't use rkcrc-ed kernel as kernel part of kernel+ramdisk image

21:28 <jcarlos> Ok

21:28 <jcarlos> That was my question

21:28 <jcarlos> So, how can I do a combined image if I only have a signed kernel?

21:29 <jcarlos> How can I unsigned it?

21:29 <naobsd> rkunpack can be used

21:29 <jcarlos> Ah

21:29 <jcarlos> Great

21:29 <naobsd> https://github.com/naobsd/rkutils/blob/master/rkunpack.c

21:30 <naobsd> or just remove first 8 bytes and last 4 bytes ;)

21:30 <jcarlos> You asked me before "how large?"

21:30 <jcarlos> My kernel is 8,4 megas

21:30 <jcarlos> And my kernel partition is only 8 megas

21:31 <naobsd> rkcrc just add KRNL and payload size(4bytes ) to header, and RK's CRC(4bytes) to trailer

21:31 <naobsd> KRNL(4bytes)+size(4bytes)

21:31 <jcarlos> OK, I understand.

21:31 <naobsd> I see

21:31 <jcarlos> Perhaps a more important question ... or at least more interesting for me.

21:32 <jcarlos> Do you have sources availables to your cwm for rk3188?

21:32 <jcarlos> available*

21:32 <jcarlos> s/to/for/

21:32 <naobsd> probably kernel is not compressed, it's standard way by RK SDK document

21:33 <naobsd> cwm source is somewhere in my backup file

21:33 <naobsd> 40GB+ backup file

21:33 <jcarlos> naobsd: That's why I asked you some days ago about "file kernel.img" and its "data" output ... :)

21:33 <naobsd> I'm preparing new build machine

21:34 <jcarlos> naobsd: But have you patched cwm a lot to be able to work with RK3188?

21:34 <naobsd> no

21:34 <naobsd> not so "a lot"

21:35 <jcarlos> I have compiled my own cwm from cyanogenmod 11.0

21:36 <jcarlos> I have created a device/bq/fnac310plus/ directory with some files generated with makevendor.sh

21:36 <naobsd> ah

21:36 <jcarlos> And I wanted you see your work

21:37 <naobsd> changes for recovery program is small

21:37 <jcarlos> You have deleted a menu option, I think.

21:37 <naobsd> changes for other parts are larger than it ;)

21:37 <naobsd> deleted?

21:37 <jcarlos> Or disabled.

21:37 <naobsd> well

21:38 <naobsd> my last build was based on cm-10.0 or .1

21:38 <jcarlos> I remember to have read something about that in I don't know what forum :)

21:38 <naobsd> I'm not sure latest CWM

21:38 <jcarlos> Well, it dosn't matter.

21:38 <jcarlos> doesn't*

21:38 <naobsd> I can't remember what I deleted

21:39 <jcarlos> One more question, please.

21:39 <jcarlos> I'm investigating your generic rk3188 cwm image

21:39 <jcarlos> The file recovery.img

21:40 <jcarlos> How can I see its contents

21:40 <jcarlos> ?

21:40 <naobsd> generic image is ramdisk-only image

21:40 <jcarlos> It's not a cpio+gzip file

21:40 <naobsd> rkunpack, then gunzip+cpio

21:40 <jcarlos> Ahhhh

21:41 <jcarlos> I need to rkunpack

21:41 <jcarlos> Ok, I understand

21:41 <naobsd> or I guess gunzip may ignore first 8bytes

21:41 <naobsd> I must go out soon

21:42 <jcarlos> Never mind. Thanks for your time!!

21:43 <naobsd> please check first few byes in image

21:43 <jcarlos> KRNL ...

21:43 <naobsd> KRNL is -only image, or ANDROID! is kernel+ramdisk image

21:43 <jcarlos> Yes, I know it, now

21:43 <jcarlos> :)

21:44 <naobsd> I'll add ANDROID! unpack function to rkunpack, then no need to think about format ;)

21:45 <jcarlos> Good idea :)

21:56 <jcarlos> naobsd: I'm comparing your recovering ramdisk with my stock recovering ramdisk. And there are lots of differences, I don't know very well if they are important or not for my device.

21:57 <jcarlos> That's my stock firmware: https://s3.amazonaws.com/tabletfirmwares/fnac+3.0+10+Plus/fnac_3_10_Plus_1.1.0_20131031-0908_HR.rar

21:58 <jcarlos> If I would like to do a custom cwm recovery for it using your work, what should I change in it? Some tutorial or URL?

22:10 <jcarlos> That was why I wanted to know if your sources were available somewhere. I would like to see your /device/[vendor]/[codename] directory ...

22:14 <naobsd> well

22:14 <naobsd> at first, my images have no relation to stock rom, everything must be different

22:14 <naobsd> I'll put source somewhere when I have time

22:15 <naobsd> but I can't get time for long time

22:15 <naobsd> same for now, I must go now

22:15 <naobsd> see you later