-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Help Best and easiest way to unroot and flash stock on my gnex?
- Thread starter gale65
- Start date
Have you gone to the official Android factory images page?
https://developers.google.com/android/images
https://developers.google.com/android/images
I managed to download the factory image but I can't figure out how to flash it without using a utility. But the utility I've used before isn't working. Even though I downloaded the image, when I go to flash it it says there's no image, even after I've navigated to it.
eta: will following the instructions on the android page unroot my phone? I want to unroot it.
edit again-probably a moot point. I looked and don't even understand the first part of the instructions. It says Once you have the fastboot tool, add it to your PATH environment variable (the flash-all script below must be able to find it). but I don't know what any of that means.
eta: will following the instructions on the android page unroot my phone? I want to unroot it.
edit again-probably a moot point. I looked and don't even understand the first part of the instructions. It says Once you have the fastboot tool, add it to your PATH environment variable (the flash-all script below must be able to find it). but I don't know what any of that means.
It can be confusing when you've not used it before. But yes, the factory image will unroot your device and return it to a completely stock state.
You will need to download the platform tools here:
https://developer.android.com/studio/releases/platform-tools.html
And you might need this driver:
https://developer.android.com/studio/run/win-usb.html
Essentially what you will do is unzip the platform tools to your PC.
You should then have a folder, you can put it wherever you want (desktop is fine) it doesn't matter. Inside this folder will be several utilities, one of them being the fastboot utility.
The easiest way to use the fastboot utility is to hold shift and right click the folder that contains the fastboot utility. Select open command prompt here. That will open a command prompt with the correct path. Basically your command prompt needs to be set up to run commands from that folder.
You will need to extract the zip of the factory image you downloaded and place all the files and the other zip file that was contained inside into the same folder as your fastboot utility.
Then you will power off your device and boot into the bootloader. For your device it looks like you hold volume down+volume up+power
When you are on the bootloader screen you should plug the device into the computer. It should automatically install fastboot drivers.
You can test that everything is working by typing:
fastboot devices
Into the command prompt. If you see your device serial number returned then everything is working.
From this point, just double click on the flash-all.bat and everything should happen automatically.
I downloaded one of the factory images for your device and I noticed that it didn't contain a flash-all.bat and only contained flash-all.sh
This will not work for Windows but if you tell me which version of the Galaxy Nexus you have, I'd be happy to build a flash-all.bat for you.
Just need to know which one is yours...
Takju
Yakju
Mysid
Mysidspr
Also, wugs should be simple, but without more information I have no idea why it's not working for you. Hopefully this will do the trick though.
You will need to download the platform tools here:
https://developer.android.com/studio/releases/platform-tools.html
And you might need this driver:
https://developer.android.com/studio/run/win-usb.html
Essentially what you will do is unzip the platform tools to your PC.
You should then have a folder, you can put it wherever you want (desktop is fine) it doesn't matter. Inside this folder will be several utilities, one of them being the fastboot utility.
The easiest way to use the fastboot utility is to hold shift and right click the folder that contains the fastboot utility. Select open command prompt here. That will open a command prompt with the correct path. Basically your command prompt needs to be set up to run commands from that folder.
You will need to extract the zip of the factory image you downloaded and place all the files and the other zip file that was contained inside into the same folder as your fastboot utility.
Then you will power off your device and boot into the bootloader. For your device it looks like you hold volume down+volume up+power
When you are on the bootloader screen you should plug the device into the computer. It should automatically install fastboot drivers.
You can test that everything is working by typing:
fastboot devices
Into the command prompt. If you see your device serial number returned then everything is working.
From this point, just double click on the flash-all.bat and everything should happen automatically.
I downloaded one of the factory images for your device and I noticed that it didn't contain a flash-all.bat and only contained flash-all.sh
This will not work for Windows but if you tell me which version of the Galaxy Nexus you have, I'd be happy to build a flash-all.bat for you.
Just need to know which one is yours...
Takju
Yakju
Mysid
Mysidspr
Also, wugs should be simple, but without more information I have no idea why it's not working for you. Hopefully this will do the trick though.
How do I find out which of those is the correct one for my device? Under about device it says this:
CyanogenMod version 12.1-20160710-NIGHTLY-maguro
under android version it says 5.1.1
under baseband version it says I9250XXL.J1
I have the android sdk platform tools on my computer from unrooting my nexus 5 the other day but I was able to use the wugfresh kit for that one (after a lot of trouble but I don't think it was a wug issue). I downloaded the takju factory image but maybe it's the wrong one?
CyanogenMod version 12.1-20160710-NIGHTLY-maguro
under android version it says 5.1.1
under baseband version it says I9250XXL.J1
I have the android sdk platform tools on my computer from unrooting my nexus 5 the other day but I was able to use the wugfresh kit for that one (after a lot of trouble but I don't think it was a wug issue). I downloaded the takju factory image but maybe it's the wrong one?
When I open the cmd window (it says powershell window-is that the same?) and type fastboot devices it says this:
PS C:\Program Files (x86)\Android\android sdk\platform-tools> fastboot devices
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fastboot devices
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command fastboot was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\fastboot". See "get-help about_Command_Precedence" for more details.
PS C:\Program Files (x86)\Android\android sdk\platform-tools>
PS C:\Program Files (x86)\Android\android sdk\platform-tools> fastboot devices
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fastboot devices
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command fastboot was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\fastboot". See "get-help about_Command_Precedence" for more details.
PS C:\Program Files (x86)\Android\android sdk\platform-tools>
I managed to get a regular cmd window opened and got this:
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Android\android sdk\platform-tools>fastboot devices
C:\Program Files (x86)\Android\android sdk\platform-tools>
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Android\android sdk\platform-tools>fastboot devices
C:\Program Files (x86)\Android\android sdk\platform-tools>
Based off of the software you have installed, it sounds like you have one of the gsm models. So your device is probably takju or yakju. But go into your bootloader screen, you should see one of those codenames there.
Ignore powershell and use the normal command prompt. It looks like you managed to get the command prompt open with the correct path. One thing to double check is that you don't have 2 platform-tools folders. Sometimes, depending on how you unzip, you can end up with a folder within a folder.
When you ran the command fastboot devices, were you connected to the phone in fastboot mode? You have to boot the phone into the bootloader and then connect to the PC.
Ignore powershell and use the normal command prompt. It looks like you managed to get the command prompt open with the correct path. One thing to double check is that you don't have 2 platform-tools folders. Sometimes, depending on how you unzip, you can end up with a folder within a folder.
When you ran the command fastboot devices, were you connected to the phone in fastboot mode? You have to boot the phone into the bootloader and then connect to the PC.
The android lying on his back with his tummy open is bootloader mode right? That's what was on my screen. Then there are choices at the top that are selected with the power button.
on that screen it says maguro 16gb. I think all the files that say magura say cdma though, and this phone is definitely gsm. I've only ever used at&t sims through straight talk.Edit
never mind-the maguro part doesn't have anything to do with the takju, etc parts. I definitely only have one platform tools folder.
On a fully unrelated note, when I try to edit a post a little pop up occurs that says edit and report and no matter what I do, it stays there. So while I'm editing I can't see the full screen because of it. So if I have typos, they were probably behind that little pop up.
on that screen it says maguro 16gb. I think all the files that say magura say cdma though, and this phone is definitely gsm. I've only ever used at&t sims through straight talk.Edit
never mind-the maguro part doesn't have anything to do with the takju, etc parts. I definitely only have one platform tools folder.
On a fully unrelated note, when I try to edit a post a little pop up occurs that says edit and report and no matter what I do, it stays there. So while I'm editing I can't see the full screen because of it. So if I have typos, they were probably behind that little pop up.
Last edited:
That sounds like the recovery screen and not the bootloader screen. I don't have any first hand experience with that particular Nexus. The instructions I saw said to hold volume up+volume down+power.
Usually, the bootloader just looks like a black screen with some text on it. And then from that screen you can choose recovery, which takes you to the screen you are describing.
Usually, the bootloader just looks like a black screen with some text on it. And then from that screen you can choose recovery, which takes you to the screen you are describing.
I get that same issue. The only thing that takes it away for me is to tap into the text portion that I'm trying to edit, then hit the back button on my phone. I've notified the devs of the issue and hopefully it's on the list to get fixed.
Alright, it does sound like that is bootloader mode on your phone. Do you see the words "fastboot mode" on that screen?
And if so, when you connect to a PC, that text will likely change to read fastboot usb or something similar.
Any chance you can post a pic of your bootloader screen for me?
Also, I'm pretty sure you got the correct image. Takju should be the one you want. You downloaded the 4.3 (JWR66Y) factory image?
And if so, when you connect to a PC, that text will likely change to read fastboot usb or something similar.
Any chance you can post a pic of your bootloader screen for me?
Also, I'm pretty sure you got the correct image. Takju should be the one you want. You downloaded the 4.3 (JWR66Y) factory image?
Last edited:
That's definitely your bootloader screen. Perhaps the fastboot text doesn't change on your device. When you're in the bootloader and connect to the PC, what happens when you type:
fastboot devices
If you get your device serial number returned in the command prompt, you should be good to go to run the flash-all.bat assuming you have everything in your folder.
fastboot devices
If you get your device serial number returned in the command prompt, you should be good to go to run the flash-all.bat assuming you have everything in your folder.
GNex was a PITA to get the fastboot driver installed. Let me look to see if I have instructions around. FWIW, it is the same driver and installation for Nexus 7 (both generations) so you may find instructions there. I'm only around for another 1/2 hour so I may not be able to get back with an answer.
it says this so I guess it's not recognizing it this way either.
C:\Program Files (x86)\Android\android sdk\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
C:\Program Files (x86)\Android\android sdk\platform-tools>
I'll do some googling. thank you. I wonder how I managed to root this thing in the first place. It was a different pc though.
Oh wait. I didn't have it connected. I connected it and it says this
C:\Program Files (x86)\Android\android sdk\platform-tools>adb devices
List of devices attached
014E0F5016010017 device
C:\Program Files (x86)\Android\android sdk\platform-tools>
eta: the number above IS the phone's serial number. So now how do I get it to recognize it on the fastboot screen?
C:\Program Files (x86)\Android\android sdk\platform-tools>adb devices
List of devices attached
014E0F5016010017 device
C:\Program Files (x86)\Android\android sdk\platform-tools>
eta: the number above IS the phone's serial number. So now how do I get it to recognize it on the fastboot screen?
Last edited:
I downloaded the drivers again (google usb drivers, through the android studio app) and still it says the best drivers are already installed and it won't recognize it in fastboot mode. I really need to get this phone unrooted for my daughter to use, because she uses a couple of apps that don't work on rooted phones.
Okay, with your phone booted up and connected, try running adb reboot bootloader
That should put you in the bootloader screen. Possibly, Windows will automatically install the fastboot drivers. If not, unzip the Google driver zip you downloaded and go to the device manager on your computer. Find your Android device with most likely a yellow question mark.
Right click it and say update driver. Go to have disk and browse to the location of the unzipped driver you saved. Hopefully that will get it working.
What's funny to me, is that adb is usually the place people have driver problems. Fastboot is usually no big deal.
Other things to consider is that windows 10 sometimes has connection issues. Especially with usb 3.0 ports and even more so if you're using a USB hub.
You may need to try different USB ports on the computer as well. If it's a PC and not a laptop, try a usb port on the back of the computer.
That should put you in the bootloader screen. Possibly, Windows will automatically install the fastboot drivers. If not, unzip the Google driver zip you downloaded and go to the device manager on your computer. Find your Android device with most likely a yellow question mark.
Right click it and say update driver. Go to have disk and browse to the location of the unzipped driver you saved. Hopefully that will get it working.
What's funny to me, is that adb is usually the place people have driver problems. Fastboot is usually no big deal.
Other things to consider is that windows 10 sometimes has connection issues. Especially with usb 3.0 ports and even more so if you're using a USB hub.
You may need to try different USB ports on the computer as well. If it's a PC and not a laptop, try a usb port on the back of the computer.
still not working. It recognizes it when I have it on and unlocked and type adb devices but when I have to go to the fastboot screen and type fastboot devices it does nothing at all. I tried Wug's again, going through every step meticulously, and it gets all the way to step 4 with no problem and then says Fastboot Device Not Found. I tried a different cable, different USB port, nothing works. I'm tearing my hair out and about to give up. But i don't have another phone that works to let her use. My only other smartphone is one that won't charge via cable so it's useless for anyone to use away from home.
I've rooted many devices, particularly Nexus devices, and I have to say, it's usually painless. It's really hard to troubleshoot driver issues like this via back and forth conversation.
Did you try the manual steps I suggested by right clicking the device in device manager and selecting the Google driver manually?
Put the phone in fastboot mode and have it connected to the computer. Check device manager for your device and hit update driver. Browse computer and choose have disk, and manually browse to the driver location.
Did you try the manual steps I suggested by right clicking the device in device manager and selecting the Google driver manually?
Put the phone in fastboot mode and have it connected to the computer. Check device manager for your device and hit update driver. Browse computer and choose have disk, and manually browse to the driver location.