Quote:
Originally Posted by BloodRagg
@pazos
Thanks, Im thinking of compiling u-boot from the latest upstream source. At least compile it with ext4 and mboot so it can boot zImage from the rootfs instead. That would allow for a bigger kernel and some proper experimenting. Afaict it would be possible to compile the latest kernel and make it work,but then again I'm no expert 
I've dissected the boot.img (that not so empty space before partition 1) and I can unpack and repack it. (running a clean version now). But i need some more firmwares to create a proper tool. At least one thats not specific for the AuraHD alone. Any idea where i can get a hold of a couple ? 
EDIT: I can repack an entire firmware image to 125MB compressed. Although i need a tweak to let it one-time boot into the recovery image. |
You need a uImage (with headers and crc), not a bzImage. If by upstream you mean a kernel released for kobo, then yes it should work. If you mean a vanilla kernel from kernel.org then noooop.
Loading a kernel from a partition is A BAD IDEA because partitions can become corrupt and you'll need to replace the sdcard to be able to boot the device.
IMHO it is a BAD IDEA to release something that you cannot test yourself. uboot is at offset 0x0(you have 512kb to tinker with), uboot environment is at 768k(128kb, but can grow to 256kb), kernel is at 1m (you have 3mb to tinker with).
If you want to tinker with low level stuff you probably want a serial com to catch bootloader & kernel messages.
I don't see the point you're trying to achieve, but go ahead. Aaaand if you release something please do it just for devices with a removable internal sdcard and put a big red alert saying "this can soft-brick your device to a state where you will need to open it, and replace the internal sdcard to recover).
I think I provided all the info I have for these kind of things, please look again at the threads I linked and the github commits I send you privately.
Good luck and have fun
