This does fit in with the "factory image" thread where you posted it, Rain, but I think it still should have a thread in its own right, so I've used your post as the OP for a new thread here in GNex ATR.
From that linked site, the steps:
Instructions:
1. Download the Android 4.0.2 factory images to your PC. [Download]
2. Unzip the file and its contents into your SDK/Tools folder (wherever your adb.exe and fastboot.exe files are).
*Make sure they are not in their own folder, but have all been extracted to Tools.
3. From within your Tools folder, open a command prompt (SHIFT + right click – “open command prompt here”):
4. Type the following commands, allowing each to finish before moving onto the next:
5. Reboot your phone by highlighting “Start” and pressing the lock switch.
6. It really is as simple as that. Your phone is now back to a 100% stock, unrooted and locked state.
At this point if you wish to keep the unlocked bootloader go to step 5 if your phone did not reboot (if it did reboot and you want the unlocked bootloader you are done), to lock the bootloader follow these steps
Your phone may reboot after the flash done by the last ADB command. If your phone reboots and you wish to lock the bootloader use the following commands:
First you will need to skip the google sign in (just press next over and over until it is done. Then go into settings and turn USB debugging on again. Now you can begin using the command prompt again with the following commands
Code:
adb reboot bootloader
fastboot oem lock
If your phone does not reboot after the last ADB command and you wish to lock the bootloader use the following commands:
Code:
fastboot reboot-bootloader
fastboot oem lock
5. Reboot your phone by highlighting “Start” and pressing the lock switch and you are unrooted
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.
I followed these steps and they worked perfectly. First boot takes a LOOOOOONG time. However I did stop before I re-locked the bootloader as Yeahha states above...
The Following 2 Users Say Thank You to BringTheRain403 For This Useful Post:
rebooted itself. I did go back into the bootloader though to make sure it still said "unlocked." I have to manually put it into the bootloader because when I ptu the command in to reboot into the boot loader it kept saying "waiting for device" which I assume was because it no longer had root access. either way it worked out and everything was fine.
Okay that is odd. Seeing as you have already finished my next step wouldn't work which would be to use "adb devices" to see if your cpu realizes the phone is connected.
Also did you turn on USB debugging after the reboot? (that is what I sould have asked) the last command you did before the reboot would have reset the device in turn removing the USB debugging system option being checked.
I've just spent the last hour and a half trying to re-flash back to stock...the first three attempts "sort-of" worked...but the "writing 'system'..." part never finished...it just sat there. Tried this with different fastboot programs and finally realized that the USB port I was using was a 3.0 port. When I switched to a USB 2.0 port, things took off:
Now, I only updated the system image and didn't flash the bootloader or radio (they shouldn't have been different and there's no good that can come from tempting fate, eh? ).
Also, what is curious is that ALL of my apps are still there in the app drawer...even the busybox and Superuser apps--of course I am not rooted anymore, but the telltale signs are there.
Okay, I'm off to test rooting via using ClockworkMod custom recovery...
I was unrooting/unlocking according to the instructions at DL.
I got to where I finished this step:
fastboot -w update image-mysid-icl53f.zip
It then went into a bootloop with the flying squares. I was not patient and pulled the battery. I am able to boot into recovery and Odin, but my command window on the computer is not recognizing the device.
When I type "adb reboot bootloader", it says:
"error: device not found".
I think it might not be in debugging mode, although it most definitely was until I pulled the battery.
If I start the boot, it doesn't get past the "Google" logo with the unlock symbol, just keeps repeating itself.
Can someone help me please???
Edit:
Guys, I just went ahead and made this a separate thread.
Last edited by HanSolo; December 17th, 2011 at 06:42 PM.
Hey guys, nice find. But I have asked this all over the place and I think it is a very relevant question, especially if one uses this method to return the phone; so I ask it here as well.
P3Droid says that when you boot into bootloader/fastboot mode there is a counter visible on the screen showing how many times the bootloader has been unlocked/locked. Has anyone seen this? And if so, when you go through this method, does the counter in fact reset?
I hope someone takes a look at this as I feel it's an important thing to take note of in this endeavor.
Hey guys, nice find. But I have asked this all over the place and I think it is a very relevant question, especially if one uses this method to return the phone; so I ask it here as well.
P3Droid says that when you boot into bootloader/fastboot mode there is a counter visible on the screen showing how many times the bootloader has been unlocked/locked. Has anyone seen this? And if so, when you go through this method, does the counter in fact reset?
I hope someone takes a look at this as I feel it's an important thing to take note of in this endeavor.
teddyearp,
I just rebooted back in to bootloader (fastboot) mode and do not see any such counter...
Perhaps that was only on P3droid's development device (presuming that's what he has)?
My fastboot screen looks nearly identical to this (this is not my screenshot, by the way):
except that mine says "VARIANT - toro" and different serial numbers, etc. -- but no unlock counter (I actually think I remember reading / hearing about this a long while back, too).
Cheers!
The Following User Says Thank You to scary alien For This Useful Post:
Ive been reading that the signal issues for many users got much worse after the 4.0.2 update. I dont know bc I accepted the upgrade as soon as it appeared. Im wanting to fo back to stock 4.0.1 just to test my signal and see if its any better. I assume these steps will work with the older factory image, judt substituting the older files in these steps? I want to run a day original locked and stock on the older firmware.
Also, can Odin program be used to flash this instead of adb and fastboot?
Just realized I have a flawed screen and I want to get a replacement so I'm gonna have to lock/unroot it seems.
How do I do this if I followed the "slightly easier manual method" of rooting. I never had to download the SDK or use adb for that so I don't know how that translates to doing the unroot...
but once I've got the SDK-tools.zip from the "how to root" thread then I can follow the steps on this page?
Yes, since you should have the fastboot utility in from the sdk-tools.zip, that's all you'll need to reflash back to stock using the information Frisco listed in post #2 above.
The Following User Says Thank You to scary alien For This Useful Post:
Just realized I have a flawed screen and I want to get a replacement so I'm gonna have to lock/unroot it seems.
How do I do this if I followed the "slightly easier manual method" of rooting. I never had to download the SDK or use adb for that so I don't know how that translates to doing the unroot...
I think you will need to download the SDK and setup ADB to unroot. The instructions linked in the OP, quoted in post 2 and edited by me in post 3 should unroot you (they are all basically the same )
I am not sure what all remnants of root are left behind when you unroot, perhaps SA will chime in with what will need to be removed. I assume you will need to do this via ADB as well.
Device(s): CURRENT - LTE Verizon Nexus
OLD - HTC VIGOR, Droid Bionic, HTC Incredible as a 3.7 AMOLED Tablet
Carrier: Not Provided
Thanks: 18
Thanked 206 Times in 120 Posts
Get back to Stock (Locked bootloader and not Root)
Okay, I dont see a clear method on how to do this on here.
I want to take this phone and not be rooted and lock the bootloader all over again. Then factory reset or whatever as if I was going to take it to Verizon. No traces of anything...
I really want to get back to stock and retry Google Wallet, as I had it working and reset data and its throwing errors at me now.
But I download this:
Stock image for VZW (Verizon) CDMA/LTE "toro/mysid" from Google:
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!
You are correct, you have to extract twice
The Following User Says Thank You to Yeahha For This Useful Post:
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.
Last edited by Mr. Orange 645; December 19th, 2011 at 01:25 AM.
...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.
The Following User Says Thank You to iowabowtech For This Useful Post:
Bjanow they should be correct. Be aware that there is a possibility unrooting will not remove all traces of root.
I think we're good now re. this...
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...
Cheers!
The Following 3 Users Say Thank You to scary alien For This Useful Post:
Device(s): S3, Galaxy Nexus(wifi), TB(backup), DI(wife), Eris (love that thing)
Carrier: Not Provided
Thanks: 336
Thanked 484 Times in 358 Posts
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.
Last edited by bjanow; December 19th, 2011 at 01:49 PM.
The Following 2 Users Say Thank You to bjanow For This Useful Post:
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?
How to: Unroot the Galaxy Nexus, Re-lock the Bootloader and Return to a Factory State
