Quote:
Originally Posted by Lmiller1708
Yup! Sad part about being a developer... You are never done flashing!
I do like android a lot better then windows... Every time you flashed a ROM it took forever to get it back how you wanted it, that is why I started to cook my own ROM's.  Now with android all you have to do is back up your data.img and wallah you are back to where you started! So that might be a option too via the replimenu.
Never heard of kexec before but it might work... Until a reboot then it will get overwritten by the original kernal.
Edit: Are you running Full NAND currently and do you have data working? |
Finally stabilised this bad boy. No more reboots, all done via sysinit.rc and its the sexiest thing to be able to mount the sdcard as mass storage.
I'll talk to jonpry about this whole kernel portion poop. When wozzer bricked himself i know he was talking about possibly writing to nand from within android. If this is possible, then all kernel updates can be done from inside without bothering the damn bootloader.
In anycase i'll repost my stuff up tonight and continue working on this. Wifi is still broken for me but i know why. Eventually i think our build will have a set of custom scripts that android will execute on boot. 2 i can think of is setting up the wifi nvram part and the other applying the calib points to the input. This way our initrd remains small since the kernel will only get bigger.
I think we have done a great deal of streamlining and i'll discuss with stinedb about possibly using our sysinit.rc for frx05. This way we will only have to worry about updates and not the build itself.
I'll commit the mtd parts tonight..