View Single Post
Old 11-27-2011, 11:50 PM   #99
hieronymos
Groupie
hieronymos is that somebody.hieronymos is that somebody.hieronymos is that somebody.hieronymos is that somebody.hieronymos is that somebody.hieronymos is that somebody.hieronymos is that somebody.hieronymos is that somebody.hieronymos is that somebody.hieronymos is that somebody.hieronymos is that somebody.
 
Posts: 186
Karma: 45172
Join Date: Nov 2011
Device: Kobo Vox
After cooling off, I decided to play the game and I had a look at what happened during the last update. As pokee had pointed out somewhere else, the recovery doesn't work anymore so I got a little curious.

This is what happened:
dd if=/cache/u-boot.bin of=/dev/block/mmcblk0 bs=1024 skip=1 seek=1
dd if=/cache/uImage of=/dev/block/mmcblk0 bs=1048576 seek=1
dd if=/cache/uramdisk.img of=/dev/block/mmcblk0 bs=1048576 seek=11
dd if=/cache/recovery-uramdisk.img of=/dev/block/mmcblk0 bs=1048576 seek=12
package_extract_file("system.img", "/dev/block/mmcblk0p1");
package_extract_file("recovery_backup.img", "/dev/block/mmcblk0p2");

Funny thing is: I'm not even sure the kernel changed! Thanks for the hint, Victor!

So from here I can start compiling a uboot that I configured to boot from SD, dd it there, reboot, hope it works, dd the old uboot and reboot into Android.
Also for custom ROMs and recoveries all the information is there. No need to worry about locked bootloaders or kernels.

void_warranty: did you get any dmesg for the USB? The kernel support is there (/proc/config.gz)...

Last edited by hieronymos; 11-27-2011 at 11:59 PM.
hieronymos is offline   Reply With Quote