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?
Our you could just wait for a pre rooted ZIP file that you could apply through CWM...
and everything went fine. No significant wait times, nothing over a couple or few minutes. I would recommend looking at your phone while in fastboot and seeing which version of the radio you have, and only flashing the radios if your current one is older (i.e. a lower number).
Quote:
Originally Posted by Yeahha
I am not sure these instructions are correct. Someone unrooted in the how to thread and had some issues. I would suggest altering it like this
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:
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:
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.
+1 on sticky. I won't want to hunt it down when I'm already miffed about having to go back to VZW! Then after we all see proven effective ways to return to stock OP may want to edit!
__________________
"We are a democracy of readers and we should keep it that way." -- Ray Bradbury
Device(s): HTC Rezound
returned Galaxy Nexus LTE
retired X2 & OG
Carrier: Not Provided
Thanks: 268
Thanked 319 Times in 149 Posts
Sorry if this was already stated above (I skimmed) but I thought I would give feedback while it was fresh:
I followed Yeahha's steps and they worked fine. I was re-locking the bootloader so that I can exchange for another Nexus. When the image file finished uploading, the phone automatically reboots. It takes about 3-5 minutes on the Samsung bootup screen before rebooting a 2nd time then ends on the activation screen.
At that point, to follow step 5, you have to first walk through the activation steps to get to the unlock screen. You can skip all the steps by just pressing "Next" through everything (no need to enter email or check/uncheck boxes, etc). Once you are in to the phone, you have to re-enable USB debugging in settings before proceeding.
After that Yeahha's steps are back on track and you are back to a like-new, unrooted and locked device. Thanks for the HOWTO. Can't wait to get the replacement and root again. Hopefully now that the SDK and drivers are installed, the next root wil go easier.
The Following 2 Users Say Thank You to esmith818 For This Useful Post:
+1 on sticky. I won't want to hunt it down when I'm already miffed about having to go back to VZW! Then after we all see proven effective ways to return to stock OP may want to edit!
It should be linked in the root guide sticky, if it isn't I will update it to link this thread.
Quote:
Originally Posted by esmith818
Sorry if this was already stated above (I skimmed) but I thought I would give feedback while it was fresh:
I followed Yeahha's steps and they worked fine. I was re-locking the bootloader so that I can exchange for another Nexus. When the image file finished uploading, the phone automatically reboots. It takes about 3-5 minutes on the Samsung bootup screen before rebooting a 2nd time then ends on the activation screen.
At that point, to follow step 5, you have to first walk through the activation steps to get to the unlock screen. You can skip all the steps by just pressing "Next" through everything (no need to enter email or check/uncheck boxes, etc). Once you are in to the phone, you have to re-enable USB debugging in settings before proceeding.
After that Yeahha's steps are back on track and you are back to a like-new, unrooted and locked device. Thanks for the HOWTO. Can't wait to get the replacement and root again. Hopefully now that the SDK and drivers are installed, the next root wil go easier.
I will update this, thanks! I didn't think about the phone trying to make you sign into google Edit: Updated!
With the SDK and drivers installed it should be easier next time just unlock then flash or softboot CWM and flash SU done!
It should be linked in the root guide sticky, if it isn't I will update it to link this thread.
An easy to locate UNROOT or BACK TO STOCK thread is easier to find when you are pre-stressed! It can be short, sweet and offer whatever viable and proven methods we have seen to nearly flawlessly work with Linux/Mac/Windows and eschew the obfuscation of "chatter" or enhance the "signal to noise" ratio... It is just a suggestion, I can see myself in that predicament with this phone as I did with my DINC in multiple scenarios.
I was a stressed clicker and missed some important notes. Of course, my mileage varies and some flashes/scripts are quite ambiguous.
An easy to locate UNROOT or BACK TO STOCK thread is easier to find when you are pre-stressed! It can be short, sweet and offer whatever viable and proven methods we have seen to nearly flawlessly work with Linux/Mac/Windows and eschew the obfuscation of "chatter" or enhance the "signal to noise" ratio... It is just a suggestion, I can see myself in that predicament with this phone as I did with my DINC in multiple scenarios.
I was a stressed clicker and missed some important notes. Of course, my mileage varies and some flashes/scripts are quite ambiguous.
Mahalo (and all),
I'm going to spend some time this weekend scanning through the threads here in our root areas to glean some good threads to link in the root guides.
Things have been pretty hectic around here in this first week or so for this phone, eh? (which is great, IMO ).
The stock image files that Google provides actually include a flash-all.sh script (meant for Linux, of course). I thought I had read in the thread where Google releases them that Jean-Baptiste M. "JBQ" Queru might consider creating a Windows .bat file version of that file, but its actually pretty simple to copy and paste these fastboot commands from that script into a Windows command prompt (fastboot utility name differences notwithstanding).
Anyway, if others feel a separate unroot / return-to-stock thread would be helpful, I'd be happy to author one (I've done that process about 12 times now ) -- although the process is pretty simple and straightforward as Frisco has already documented in post #2 of this thread.
Will this just flash the stock factory image and take us back to normal, maintaining root and bootloader unlock? (assuming your radios are already updated...)
It's not too hard to unroot and then reroot, but I'd rather have a better understanding of what each step actually does
Will this just flash the stock factory image and take us back to normal, maintaining root and bootloader unlock? (assuming your radios are already updated...)
It's not too hard to unroot and then reroot, but I'd rather have a better understanding of what each step actually does
Well, flashing with the above command will replace all of your OS (even the root parts), so you lose root at that point...but yes, the bootloader and radios are untouched by the above component being flashed (that's the OS part (boot/recovery/system images)).
Your bootloader will remain unlocked (its only affected by the fastboot oem lock and fastboot oem unlock commands).
You should be able to just use the above command to return to stock as long as the radios and the bootloaders haven't changed. That being said, whenever Google publishes a new OTA and the accompanying stock image package, you'll want to keep everything (radios, bootloader, OS (boot/recovery/system images)) in-sync.
Cheers!
The Following User Says Thank You to scary alien For This Useful Post:
Well, flashing with the above command will replace all of your OS (even the root parts), so you lose root at that point...but yes, the bootloader and radios are untouched by the above component being flashed (that's the OS part (boot/recovery/system images)).
Your bootloader will remain unlocked (its only affected by the fastboot oem lock and fastboot oem unlock commands).
You should be able to just use the above command to return to stock as long as the radios and the bootloaders haven't changed. That being said, whenever Google publishes a new OTA and the accompanying stock image package, you'll want to keep everything (radios, bootloader, OS (boot/recovery/system images)) in-sync.
Ha... When I lock, it will not wipe the phone, right? Only when unlocking?
Yes, I believe so...(I know that the unlock will wipe, but I've never heard anyone talk about wiping taking place during locking). I'm pretty sure it won't wipe anything during re-lock and I found a reference on XDA who corrected someone about that same question:
I've relocked my phone a few times, but I don't think I ever bothered to check the SD card contents afterwards...
I would test that for you, but I can't do that this evening...sounds like you are on the cusp of doing this anyway , you could backup your SD card contents just before re-locking and then let us know?
By the way, are you re-locking because you need to return your device or do you have another reason?
Cheers!
The Following User Says Thank You to scary alien For This Useful Post:
Yes, I believe so...(I know that the unlock will wipe, but I've never heard anyone talk about wiping taking place during locking). I'm pretty sure it won't wipe anything during re-lock and I found a reference on XDA who corrected someone about that same question:
I've relocked my phone a few times, but I don't think I ever bothered to check the SD card contents afterwards...
I would test that for you, but I can't do that this evening...sounds like you are on the cusp of doing this anyway , you could backup your SD card contents just before re-locking and then let us know?
By the way, are you re-locking because you need to return your device or do you have another reason?
Cheers!
Thanks. Re-locked. No files lost. I'm going to take the phone into a Verizon store and compare signals and camera quality to another SGN. You never know what might happen when I do that...
The Following User Says Thank You to sperho For This Useful Post:
Thanks. Re-locked. No files lost. I'm going to take the phone into a Verizon store and compare signals and camera quality to another SGN. You never know what might happen when I do that...
LOL, for sure!
Thank you for replying to confirm (great and interesting asked-and-answered question !).
I downloaded the factory image multiple times, but Windows 7 doesn't recognize it and Winzip tells me that it can't read its header (whatever that means). Is there a known issue with this?
I downloaded the factory image multiple times, but Windows 7 doesn't recognize it and Winzip tells me that it can't read its header (whatever that means). Is there a known issue with this?
Yeah, that's probably because its a .tgz (compressed tar archive) type of file.
iowabowtech, was spot-on...7zip or winrar or even Winzip should be able to understand its format (and probably a few dozen other archive utilities, too).
Hello there, thanks for the helpful tips. I am planning to root my G-nexus but I cant find a factory image for my device. I have 4.0.1 yakjuux G-nexus from bell. If there is no stock image for my device, will the stock image yakju 4.0.1 work on mine?
Hello there, thanks for the helpful tips. I am planning to root my G-nexus but I cant find a factory image for my device. I have 4.0.1 yakjuux G-nexus from bell. If there is no stock image for my device, will the stock image yakju 4.0.1 work on mine?
Check out the middle part of the first post in this thread for the stock image information under the "Stock Factory Images" section:
Hello there, thanks for the helpful tips. I am planning to root my G-nexus but I cant find a factory image for my device. I have 4.0.1 yakjuux G-nexus from bell. If there is no stock image for my device, will the stock image yakju 4.0.1 work on mine?
I believe Bell is a CDMA/LTE carrier if that is the case I think you would need the toro/mysid files not yakju
You should be able to boot into fastboot (power off hold volume up and down then hold down the power button and wait) and it should tell you the device type in the lower left corner after variant.
maguro = GSM toro = CDMA
The Following 2 Users Say Thank You to Yeahha For This Useful Post:
I believe Bell is a CDMA/LTE carrier if that is the case I think you would need the toro/mysid files not yakju
You should be able to boot into fastboot (power off hold volume up and down then hold down the power button and wait) and it should tell you the device type in the lower left corner after variant.
maguro = GSM toro = CDMA
Thanks, Yeahha!
I saw the "yakju" references and improperly matched that up to GSM (although that's normally correct, but apparently isn't for Bell).
I believe Bell is a CDMA/LTE carrier if that is the case I think you would need the toro/mysid files not yakju
You should be able to boot into fastboot (power off hold volume up and down then hold down the power button and wait) and it should tell you the device type in the lower left corner after variant.
maguro = GSM toro = CDMA
It is mainly a CDMA/LTE carrier but the Nexus that they have is GSM/HSPA+
That is odd, but good to know I knew they had a HSPA+ network but didn't realize they had GSM as well.
Quote:
Originally Posted by Flavoristic
the same as yours
That isn't mine, I am on VZW so I have CDMA/LTE, found that using google
Quote:
Originally Posted by Flavoristic
Yes i need it for a back up if something went wrong.
That is 100% understandable. I would also keep a copy of the stock rooted nandroid on a CPU so if you can boot to recovery you can just use that and not worry about unrooting if it isn't for warranty issues
The Following User Says Thank You to Yeahha For This Useful Post:
I get the error "cannot load bootloader-toro-primekk15.img"
I assume this is somehow related to the files / folder location. I downloaded the 4.02 img file, and unzipped it to the following:
c:\android-sdk\tools folder
Then I ran 7zip to extract the files to that folder, which created a folder "mysid-icl53f" in my tools folder. So, I have a folder "c:\android-sdk\tools\mysid-icl53f". In THAT folder, I have a file called "bootloader-toro-primekk15.img". I am running the fastboot command from within that folder, where the img file is located.
What am I doing wrong??? Thanks for any and all help!
Move the file you are trying to flash to the same folder as your adb and fastboot is. So if you have fastboot in c:\android-sdk\tools then put the contents from folder "mysid-icl53f" into the c:\android-sdk\tools.
The Following User Says Thank You to Yeahha For This Useful Post:
I get the error "cannot load bootloader-toro-primekk15.img"
I assume this is somehow related to the files / folder location. I downloaded the 4.02 img file, and unzipped it to the following:
c:\android-sdk\tools folder
Then I ran 7zip to extract the files to that folder, which created a folder "mysid-icl53f" in my tools folder. So, I have a folder "c:\android-sdk\tools\mysid-icl53f". In THAT folder, I have a file called "bootloader-toro-primekk15.img". I am running the fastboot command from within that folder, where the img file is located.
What am I doing wrong??? Thanks for any and all help!
NCTurner,
That should be working, assuming that your fastboot command is executable from that directory, too.
If you didn't set your PATH environment variable to also know about where the fastboot utility is located, you might just want to make sure that fastboot is also in the same directory with all of the files from the mysid-icl53f subfolder.
Also, check your spelling and/or try doing a copy and paste (I usually pull-up the flash-all.sh file in an editor and copy and paste the commands from that file so that I don't make any typing mistakes).
I just did this same process for 4.0.1 tonight (was testing some stuff) and have done this about a dozen times...so, its probably something simple.
Let us know.
Cheers!
edit: ninja'd by the Yeahha!
The Following User Says Thank You to scary alien For This Useful Post:
Device(s): The Beast - Galaxy Nexus, Toshiba Thrive
Carrier: Not Provided
Thanks: 602
Thanked 392 Times in 146 Posts
Thank you very much!!! I got it. I did use Wugs, but I think the problem was that I didn't have the file contents in the correct subfolder. You guys rock!
Question, I currently have my bootloader locked but I would like to be install the 4.0.4 update for my GN. I know I have to unlock the bootloader to apply the update, and want to relock the bootloader, just type "fastboot oem lock"
I would like to see if the new GN update will help with the random reboots.
Question, I currently have my bootloader locked but I would like to be install the 4.0.4 update for my GN. I know I have to unlock the bootloader to apply the update, and want to relock the bootloader, just type "fastboot oem lock"
I would like to see if the new GN update will help with the random reboots.
JMO, but if anyone is still locked and looking to mess with the leaked 4.0.4, you might just want to consider waiting for the OTA at this point since it's bound to be just around the corner. Also, don't forget if you do decide to unlock, you just said goodbye to all your internal storage contents including that which resides on the virtual "sd card". So if there's anything that needs to be retained, act accordingly before you unlock.
The Following User Says Thank You to iowabowtech For This Useful Post:
I walked through the following steps to put the stock OS back on my device...
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img (Note: This one takes a couple minutes. Be patient)
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
I now have the stock OS loaded and can boot alright, unlocked. When I get back into the OS I turn debugging on and then head back to adb. I get the following error when attaching to my device, though.
c:\android\android-sdk\platform-tools\adb shell
shell@android:/ $ adb reboot bootloader
adb reboot bootloader
error: device not found
1|shell@android:/ $
Further, if I run "fastboot devices" from my command prompt I get no devices returned.
What am I missing?? I need to get this device relocked to send back in for warranty quickly. I'm trying to get the device locked back up. Any help you can provide is appreciated!
When I did all of the initial commands I did them from within the adb shell by running fastboot first. I could reboot the bootloader and such from within adb. After putting the stock OS back on I was unable to get fastboot to work (no devices listed when running "fastboot devices"). I was able to boot into fastboot and simply run the command from my computer for oem lock. I did that, rebooted, noticed the unlocked symbol gone on the boot splash screen, pulled the battery and tossed the phone in the box to go back. Whew.
I had been having problems with the device having high pitch squeals when on the phone. So far I've only been able to get the squeal when talking to other GNex users, though. Odd, and maybe a huge coincidence but still what I was able to get out of it. I'm on my third device. If this doesn't work I'll raise hell with vzw to give me a different device altogether.
The Following User Says Thank You to aharper For This Useful Post:
Edit: Updated! 
).
