Paul Wise <[email protected]> writes: > On Fri, Jan 20, 2017 at 5:05 PM, Rodolfo Medina wrote: > >> Yes, there is one. > > Could you paste /proc/mtd into an email?
It's an empty file. >> I did as you suggested. I downloaded the firmware, unpacked it with `unar' >> and >> then ran rkunpack over the file update.img. Some other files were created. >> What now? > > What files do you see? > Is there a zImage or vmlinuz? The following two files were created: BOOT and embedded-update.img, and the following output was produced: rkunpack: info: RKFW signature detected rkunpack: info: version: 1.1.0 rkunpack: info: date: 2013-04-17 15:57:08 rkunpack: info: family: rk30xx rkunpack: info: 00000066-0002ee73 BOOT (size: 192014) rkunpack: info: 0002ee74-1a137e77 embedded-update.img (size: 437293060) unpacked . Is embedded-update.img our kernel image? And should we conclude that maybe 0x00000066 is the system RAM base address we are looking for? >> Thanks indeed for your help... What comes now? > > Continue to go through the article, getting the needed info. Now I'm at: # mkdir my-initramfs # cd my-initramfs # mkdir -p proc sys dev mnt/root sbin # cp /my/arm/busybox sbin/busybox # cp /above/init init # chmod a+x init sbin/busybox # find . | cpio --quiet -H newc -o | gzip > ../initramfs.cpio.gz # cd .. # mkbootimg --base 0x00200000 --kernel zImage --ramdisk initramfs.cpio.gz -o my-boot.img . So I need the two parameters: --base and --kernel. Should I maybe put, in place of 0x00200000, the above 0x00000066 that came out from the output of rkunpack? And what should I put in place of zImage? Besides, the binary busybox was already in my computer and the command `mkbooting' seems to be part of the package android-tools-mkbootimg. Is that right? Thanks, Rodolfo
