Originally Posted by pts69666 (Post 2075036)

I ran the provisioning built into the ROM (it had Sprint provisioning in it) and I ran a provisioning cab file. Both to no avail. Government computers don't like USB devices, so I can't try flashing stock ROM until I get off.

Originally Posted by [ACL] (Post 2075221)

finally got word about the autobuild server. Looks like we had a power supply issue.

I'm going to back up some stuff tonight and have an alternate download link. Wistlitl is going to upgrade us to a new server so make sure to thank him if yall see him on IRC.

Originally Posted by natemcnutty (Post 2075079)

Although you may have no way to get it on there, you can actually extract the NBH from the stock ROM's EXE and flash that from the sd card as well.

Originally Posted by natemcnutty (Post 2075236)

That's a bummer about the power supply. Glad that Wiltilt is able to help us out. If you have a backup of the autobuild stuff, can you shoot me the details? I'd love to see how that all works and maybe set my server up to do something similar :)

Originally Posted by [ACL] (Post 2074863)

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

Originally Posted by natemcnutty (Post 2075424)

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.

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.

Originally Posted by [ACL] (Post 2075491)

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.

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.