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

[[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!

[a460162314]

I got some other feedback.
V version of the phone to normal use.
But there he was, the screen no longer wake up after shut down, need to restart to resolve.
S version of the phone,Even the use of CDMA SIM cards.
Same constantly reboot.
While the other is stuck in more: SMD: ch 0 Opening -> Opened.
And someone said to me,They do not have permission to access the phone ROOT.
But when I tested, I have ROOT permissions.
Keep up, man, look forward to your updates.
Good luck

[pts69666]

Ill try the stock ROM after work and let you guys know if it fixes data.

[Lmiller1708]

Originally Posted by natemcnutty

Yikes, that doesn't sound good. I hope nothing we are doing in Android is affecting Windows Mobile. A good thing to test would be flashing stock and see if that fixes data in WinMo. I don't think we can affect the radio firmware from within Android, but I guess anything is possible.

You are correct there should be no harm at all to the radio. I'm about 99.9% sure...

Originally Posted by pts69666

Ill try the stock ROM after work and let you guys know if it fixes data.

Did you remember to run the provisioning for your carrier once you flashed the new winmo ROM? If you have never had to do that in the past you might have to now. And make sure you have rebooted a couple of times just to be safe.

I have flashed back and forth many time with both of my TP2's with no issues at all.

[pts69666]

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.

[natemcnutty]

Originally Posted by pts69666

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.

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.

[[ACL]]

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.

[natemcnutty]

Originally Posted by [ACL]

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.

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

[[ACL]]

Originally Posted by natemcnutty

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

Ill send you over the script i got from Netripper. Its very flexible incase you wanna run your own autobuilds.Its good because it will always use a clean pull from a separate machine thats not affected by dirty code. But i'll shoot you over the email.