ok...upon looking into this a little more I have a question.
Am I supposed to extract the file containing the image twice? It starts as a tgz, then when I extract it it's a tar, and if I extract THAT I get a folder containing the image-mysid-icl53f.zip plus the other .img files that are needed.
I think maybe I answered my own question.... But if that's not right, someone lemme know please!
ok...upon looking into this a little more I have a question.
Am I supposed to extract the file containing the image twice? It starts as a tgz, then when I extract it it's a tar, and if I extract THAT I get a folder containing the image-mysid-icl53f.zip plus the other .img files that are needed.
I think maybe I answered my own question.... But if that's not right, someone lemme know please!
It should be on (just like when you are ready to make a phone call) and when you run the first command "adb reboot bootloader" it puts it into the bootloader or if you are completely bricked I assume you can just start from the bootloader...
Ok...I got that issue figured out. For some reason, even though my paths were correct, it wouldn't work from platform-tools. I extracted the sdk-tools mini folder, placed my files there and ran my commands through that path, and it worked.
...I am also not sure that radio flashing is needed currently either (yet at least) there are only the stock radios available and I don't see a reason to risk 2 extra bootloader flashes if they aren't needed.
Agreed. Its also likely that many users will be accepting OTA updates through Google which will always keep our radio updated. With an unlocked bootloader, its not a worry like it is on many other devices that rely on exploits that may get patched via OTA. Even thinking about roms...we are on the leading edge here with the newest android version. Most roms are going to be based off what we get as stock. So why needlessly flash partitions, especially the radio which is the most apt to cause problems? I think this topic need more discussion. It may just be that we would be best served to throw out what we know...full wipes...and focus on targeted wipes? Idk, I'm still learning here too but I'm finding that fastboot is a powerful tool and moving forward with caution may be beneficial.
I flashed back to stock about 8 times this weekend... For the first 7 times, I kept re-signing back-in during the activation / setup part and saw that my apps had mysteriously reappeared. I was also re-applying the root package via ClockworkMod at times, so I was putting those pieces back manually (and, of course, you can't examine the /data/app directory to see what's there without being rooted--a small catch-22).
I believe this occurred because Android was auto-downloading my apps.
On the last time I flashed back to stock, I skipped the sign-in part and there were no sign of my old apps.
I would just re-lock and unlock the bootloader, flash back to stock (skip the sign-in part of the activation / setup), and finally, re-lock the bootloader one last time before returning.
I also think you can skip re-flashing the radio and bootloader if you haven't changed them...
Done, thanks guys. No trace of superuser afaik. Off the the vzw store now.
Edit: I got a new phone, rerooted, installed cwr, restored my old backup, back to where I was an hour ago. Once again, thanks guys for the great support.
So if I follow the steps in post #3 to unroot, this will allow me to get OTA updates? Then I can root again and be back where I was with but with an update?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.