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

[[ACL]]

nate/lmiller:

ok so the damn autobuild server is down. So i cant post some new stuff yet. I did manage to commit everything to tinboot so thats all uptodate.

I also commited some stuff to bootenv. Mostly the portion about the modules. Now we are deploying the modules as an sqsh and it gets mounted to the correct folder in system. This way we can wipe and restore with no issues. Actually thanks to this new setup, ive been able to install and restore my data in the same recovery session. All without losing my modules. Only downside is you will need mksquashfs version 3.4 to make this file.

Check out the commits and yall will see. Once autobuild comes up you guys can download it and dissect it

[Lmiller1708]

Originally Posted by [ACL]

nate/lmiller:

ok so the damn autobuild server is down. So i cant post some new stuff yet. I did manage to commit everything to tinboot so thats all uptodate.

I also commited some stuff to bootenv. Mostly the portion about the modules. Now we are deploying the modules as an sqsh and it gets mounted to the correct folder in system. This way we can wipe and restore with no issues. Actually thanks to this new setup, ive been able to install and restore my data in the same recovery session. All without losing my modules. Only downside is you will need mksquashfs version 3.4 to make this file.

Check out the commits and yall will see. Once autobuild comes up you guys can download it and dissect it

Great Job ACL! As soon as my Darn VM gets up and running again I will give it a try! It like to just freeze up after about 2 - 3 hours of use... Wish I could just run with out!

Anyway how can I add a section to the recovery? I plan on making the install script today right from the system.ext2.

Originally Posted by natemcnutty

Wirelessly posted (Opera/9.80 (Android; Opera Mini/6.0.24212/24.743; U; en) Presto/2.5.25 Version/10.54)
That sounds great ACL. I'll take a look at it and update the how-to thread tomorrow. Got myself a Xoom today, so I've been a little preoccupied

Ahh new toy! Have fun with it! I'm hoping to get a ThunderBolt soon for work!

EDIT: Has anyone tried my system FRX06 yet?

[[ACL]]

Originally Posted by Lmiller1708

Anyway how can I add a section to the recovery? I plan on making the install script today right from the system.ext2.

Just edit the install-seq in the recovery/sbin directory. right now our install seq is similar to the old seq but with some differences you may notice.

But in there you can have it check if there is the system.img and do your dirty business.

[natemcnutty]

Originally Posted by [ACL]

nate/lmiller:

ok so the damn autobuild server is down. So i cant post some new stuff yet. I did manage to commit everything to tinboot so thats all uptodate.

I also commited some stuff to bootenv. Mostly the portion about the modules. Now we are deploying the modules as an sqsh and it gets mounted to the correct folder in system. This way we can wipe and restore with no issues. Actually thanks to this new setup, ive been able to install and restore my data in the same recovery session. All without losing my modules. Only downside is you will need mksquashfs version 3.4 to make this file.

Check out the commits and yall will see. Once autobuild comes up you guys can download it and dissect it

Was getting an invalid mount, so I committed loop3 thinking that would fix it. Then got another error that it was an invalid argument. Finally figured out that I simply did sudo apt-get install squashfs-tools and ended up with v4, not 3.4...

Anyway, I did get system.ext2 loop mount off sdcard then cp -a everything over to /system working perfectly. I tried using dd to do a low level copy of everything, but that failed on me for some reason. I'll commit that change to the script in recovery shortly.

[[ACL]]

Originally Posted by natemcnutty

Was getting an invalid mount, so I committed loop3 thinking that would fix it. Then got another error that it was an invalid argument. Finally figured out that I simply did sudo apt-get install squashfs-tools and ended up with v4, not 3.4...

Anyway, I did get system.ext2 loop mount off sdcard then cp -a everything over to /system working perfectly. I tried using dd to do a low level copy of everything, but that failed on me for some reason. I'll commit that change to the script in recovery shortly.

yeah i updated the code right before your commit. I actually moved it to use loop0.

I'm actually just using the 3.4 mksquasfs binary so i dont have to mess with the versioning for squash fs tools.

Autobuild should spit out an image shortly. I was able to install fresh, restore without reboot and then after a reboot get back to android with a new kernel and no module issues so i think we are set for now. So everyone should be able to now continue without losing anything. Even after a full upgrade

ive been using the phone for about 4 hours and i do notice some small bugs that need fixing.. I killed my batt on purpose to work on that charging issue.

[arrrghhh]

Originally Posted by [ACL]

yeah i updated the code right before your commit. I actually moved it to use loop0.

I'm actually just using the 3.4 mksquasfs binary so i dont have to mess with the versioning for squash fs tools.

Autobuild should spit out an image shortly. I was able to install fresh, restore without reboot and then after a reboot get back to android with a new kernel and no module issues so i think we are set for now. So everyone should be able to now continue without losing anything. Even after a full upgrade

ive been using the phone for about 4 hours and i do notice some small bugs that need fixing.. I killed my batt on purpose to work on that charging issue.

Good news bro! That is very good news indeed... No more need to constantly reflash!