NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery

[Lmiller1708]

Originally Posted by [ACL]

ahh booo yeah thats what im tlaking about.


I have to flash like crazy to continue kernel dev. unless i kexec or go back to sdcard temporarily

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?

[Lmiller1708]

For Reference... Using OSbuilder:

WinMo Roms:
Vogue Dump
TP2 Dump

Nand:
Vogue_Nand_Dump
TP2_Nand_Dump (current)

[[ACL]]

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..

[natemcnutty]

Originally Posted by [ACL]

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..

You're awesome

Also, for calibration, the program we invoke to do the calibration is pretty small and wouldn't really cause problems with initrd or adding it to system. The problem is that I always end up with random text cluttering up the touch points. I'd much rather see an app in Android for calibration so lcd density doesn't mess up calibration. I really agree that the closer we can mimic true android devices, the better experience we are going to get.

On the kernel side of things, I was looking at the work of cedesmith on a bootloader that builds on top of tinboot. He's done some interesting things including the ability to load a kernel from the computer which would absolutely rock. He's designing it for the HD2 crowd, but I think I'm going to play around with it and see what I can learn about it. Might be something useful there

http://forum.xda-developers.com/showthread.php?t=901305

[Lmiller1708]

Originally Posted by natemcnutty

Wonder if that's why magldr just uses the zImage and initrd.gz from the first partition. Then you could use the update utility to update them without having to ever flash again.

On a side note, I would double check with the Vogue guys to make sure everything does get wiped when they update their kernel. I'm still wondering if partition tables may have something to do with this. Hopefully I can finally get a break from work and home to actually do some serious testing. I find it really odd that the partition table has two partitions that start at the same location rather than simply erasing the second partition and moving the locations of everything.

Magldr is a custom bootloader... It can do about anything.

We are in the same as the Vogue (since we copied it). They need to reflash to upgrade there kernal too. No way around it with out a custom bootloader...

Originally Posted by [ACL]

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..

GREAT!

If it is possible to write to nand from within that would probably solve our problem. (Maybe)


I will wait for your System.tgz. Did you get data working on it?
That was my problem.. It was stable but with no data.

[[ACL]]

Originally Posted by Lmiller1708

Magldr is a custom bootloader... It can do about anything.

We are in the same as the Vogue (since we copied it). They need to reflash to upgrade there kernal too. No way around it with out a custom bootloader...




GREAT!

If it is possible to write to nand from within that would probably solve our problem. (Maybe)


I will wait for your System.tgz. Did you get data working on it?
That was my problem.. It was stable but with no data.

i cant test cdma data since i have no service but wifi is coming up.. so i'll post my stuff tonight. last night i passed out and forgot to upload.

i guess its time to unleash this info to the cookers soon.. see what nand abominations they come up with.