Using the RC29 NBH rollback will indeed wipe all of your applications. Use one of the file managers that offer backing up of applications, or you can redownload them with the list google saves (assuming you'll be using the same google account to activate.)
Using the RC29 NBH rollback will indeed wipe all of your applications. Use one of the file managers that offer backing up of applications, or you can redownload them with the list google saves (assuming you'll be using the same google account to activate.)
What list are you referring to? Is it in the market?
Yeah, Google keeps a list of all the applications you've installed using the Google account you activated your phone with (or something unique akin to it.)
If you were to wipe your phone, and activate again (rooted, hopefully ) after a little while, in the market you could click 'My Downloads' and get all of your applications, paid and not, back again.
I don't have service on mine personally, but a friend highly recommends SMS Backup. You can see the other options you have available here: http://www.cyrket.com/search?q=sms+backup
Took a while longer because the extension of the DREAIMG.NBH was lowercase and it gave me a FAIL. I had to put the SD card in something else and rename the file. After I did that it all worked great.
Maybe... When I figure that out, or Tethering first.
Just another quick question, I followed the rooting directions and everything including the recovery.img part of it and it all seems to have worked fine.
What happens when an update is pushed out OTA? Is that what the recovery.img part of the procedure prevents, an OTA update?
Pretty much, the updates aren't signed with the same key as the test keys. You'll know when new updates come out, everywhere goes nuts for a few days, or weeks.
It all depends what the new version changes and stuff like that. When in doubt, wiping never hurts (assuming you have backups )
Thats if you update to a non rooted standard update, right? Cause i tried to use the JFUpdater app and it updated fine, but i reverted back cause it was somewhat buggy.
Google does the builds ... then when ready to be released they are turned over to TMO and TMO then pushes them out OTA in random to users
TMO bring the carrier correct? (What does TMO stand for btw?)
If that is correct, does the carrier do any further modifications to the OS before releasing it out OTA to customers - like branding it or putting restrictions on it?
TMO bring the carrier correct? (What does TMO stand for btw?)
If that is correct, does the carrier do any further modifications to the OS before releasing it out OTA to customers - like branding it or putting restrictions on it?
TMO = T-Mobile.
Not to my knowledge .. they dont have that abiltiy and that is what google does is make the code and the carrier (t-Mobile) distribute the updates ..
Do you lose your apps if you perform the root process?
) after a little while, in the market you could click 'My Downloads' and get all of your applications, paid and not, back again.
)
