Develop Bugs

[HOW TO] Restore Galaxy Nexus to Stock V2

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​This is a tutorial on how to return your Galaxy Nexus to stock if needed. This method uses the official images from Google
I am not to be held responsible if anything goes wrong when attempting this. This includes bricking your phone, flashing a bad image, causing WW3 etc. I am also not responsible for any files in this tutorial. They were all provided by other people.
There may be inaccuracies in this post that may lead to various things such as bricked devices so be warned. Let someone check it over first! If you see anything wrong, let me know and I will edit it!
What you need
Samsung Galaxy Nexus GSM Version
All the usual fastboot & ADB drivers etc
Fastboot
Official Google Image
Google Images
https://developers.google.com/android/nexus/images
Fastboot
DOWNLOAD
1) Take a Nandroid Backup if you have CWM installed
2) Extract the content of the Google Image
3) Copy the contents of the Fastboot download to the same folder as where you extract the Google Image too.
4) Boot your phone into the Bootloader mode
5) Open up Command Prompt or Terminal, navigate to the folder you've extracted it all too and enter the following commands waiting for each to finish
Windows
fastboot-windows flash bootloader bootloader-maguro-primekk15.img
fastboot-windows reboot-bootloader
fastboot-windows flash radio radio-maguro-i9250xxkk6.img
fastboot-windows reboot-bootloader
fastboot-windows -w update image-yakju-icl53f.zip
Linux
./fastboot-linux flash bootloader bootloader-maguro-primekk15.img
./fastboot-linux reboot-bootloader
./fastboot-linux flash radio radio-maguro-i9250xxkk6.img
./fastboot-linux reboot-bootloader
./fastboot-linux -w update image-yakju-icl53f.zip
OSX
./fastboot-mac flash bootloader bootloader-maguro-primekk15.img
./fastboot-mac reboot-bootloader
./fastboot-mac flash radio radio-maguro-i9250xxkk6.img
./fastboot-mac reboot-bootloader
./fastboot-mac -w update image-yakju-icl53f.zip
6) The last step is to lock the bootloader. Restart the phone into the bootloader
7) Open CMD in the location of Superboot and type:
fastboot-windows oem lock
Click to expand...
Click to collapse

Anyone other than the OP try this yet? If so, what state were you starting from (cwm installed, which custom rom etc) and did it work? did you need to do anything differently?

It works, can confirm!!
1. copy the extracted rom folder to clockworkmod\backup\maguro_4.0.1 on your internal storage
2. boot in too cwm
3. (what i do) in mount and storage menu, format system/data/cache
4. install super wipe lite zip file
5. restore the maguro_4.0.1 rom
phone boot up, everything fine, first run wizard start..
6. reboot to fastboot
7. flash the stock recovery "fastboot flash recovery recover.img"
8. boot in to recovery to test
9. reboot the phone
i didnt lock the bootloader while i will only root the device and other things let on stock.
i came from unlocked bootloader, clockworkmod recovery and android revolution hd rom..

Brilliant news.
I've updated the tutorial to include the latest updates

so you cant just do a erase all content and setting like you can on the iphone?

TroyBoy30 said:
so you cant just do a erase all content and setting like you can on the iphone?
Click to expand...
Click to collapse
Even on a jailbroken iPhone, when you do a factory reset you get all your settings reset but the phone is still jailbroken.
Same thing applies with Android. You need to flash the stock files to get back to stock.

@evostance
Another possibility (as yours relies on having access to a backup/nandroid as well as somehow being able to access the SDCARD partition) which some people may not have
would be Peter Alfonsos "return to stock"way
http://www.peteralfonso.com/2011/11/download-100-stock-fastboot-images-for.html
flash it via fastboot and you are golden
All you need is fastboot and the image

Evostance said:
Even on a jailbroken iPhone, when you do a factory reset you get all your settings reset but the phone is still jailbroken.
Same thing applies with Android. You need to flash the stock files to get back to stock.
Click to expand...
Click to collapse
ah i got ya. so when you say stock you mean unrooted, etc? So if i never root I can simply wipe data

Thyrus said:
@evostance
Another possibility (as yours relies on having access to a backup/nandroid as well as somehow being able to access the SDCARD partition) which some people may not have
would be Peter Alfonsos "return to stock"way
http://www.peteralfonso.com/2011/11/download-100-stock-fastboot-images-for.html
flash it via fastboot and you are golden
All you need is fastboot and the image
Click to expand...
Click to collapse
I tried that and it trashed my phone, so I had to restore to the zip above and all way fixed.
I think Peter might have changed his files now but not sure

guys have one problem, after i sucessdully restore the stock rom over the method i wrote i try it over fastboot with the original oem files from peter, erase system and user partition over fastboot and flash it again with the files on his site.. everything seems to work, and i finish with the setup from my device bit then i see in google account my calendar didnt sync, there is no entry for it.. i try to delete the account and recreate it but without success.. anybody here a idea what can ne the problem?? any suggestions how to fix that?? i dont want make the whole proceess over recovery, i like this method more while they are really empty images and not a nandroid backup..
many thanks!!
Sent from my Galaxy Nexus using XDA App

and a seccond problem.. when im listening music over power amp, when the screen goes off, the sound didnt play correct, like a scratch on a cd, jumps little bit.. here any sugestions?? (sorry for my english)
Sent from my Galaxy Nexus using XDA App

m_adnan said:
guys have one problem, after i sucessdully restore the stock rom over the method i wrote i try it over fastboot with the original oem files from peter, erase system and user partition over fastboot and flash it again with the files on his site.. everything seems to work, and i finish with the setup from my device bit then i see in google account my calendar didnt sync, there is no entry for it.. i try to delete the account and recreate it but without success.. anybody here a idea what can ne the problem?? any suggestions how to fix that?? i dont want make the whole proceess over recovery, i like this method more while they are really empty images and not a nandroid backup..
many thanks!!
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I had the same issues hence why I wrote this tutorial as doing it this way was the only guaranteed way of getting it back to perfect stock

Evostance said:
I had the same issues hence why I wrote this tutorial as doing it this way was the only guaranteed way of getting it back to perfect stock
Click to expand...
Click to collapse
ok, im flashing now the one from paul obrian and go then back to stock recovery.. thanks

right then - officially from google
http://code.google.com/android/nexus/images.html
howto: http://groups.google.com/group/andr...a058a737b9/43c3a418144fc6c5?#43c3a418144fc6c5

Thank you
been waiting for official images

Thyrus said:
right then - officially from google
http://code.google.com/android/nexus/images.html
howto: http://groups.google.com/group/andr...a058a737b9/43c3a418144fc6c5?#43c3a418144fc6c5
Click to expand...
Click to collapse
Excellent. I'll update when home
Sent from my Galaxy Nexus using Tapatalk

Thyrus said:
right then - officially from google
http://code.google.com/android/nexus/images.html
howto: http://groups.google.com/group/andr...a058a737b9/43c3a418144fc6c5?#43c3a418144fc6c5
Click to expand...
Click to collapse
Nice of them to include the volume fix

anybody care to explain the "how to" a lil' bit more than JBQ? I'm kinda lost w/ fastboot commands

hi there..
i report a small bug whit poweramp when the screen goes off, its very easy to fix it:
- start poweramp and go to settings
- press on audio engine
- press advanced twaks
- press audio buffer size
- i choose **large (+250ms)**
after them it plays very well..
---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------
Thyrus said:
right then - officially from google
http://code.google.com/android/nexus/images.html
howto: http://groups.google.com/group/andr...a058a737b9/43c3a418144fc6c5?#43c3a418144fc6c5
Click to expand...
Click to collapse
but can we flash that on lte devices??

So, when I restore my Galaxy Nexus with this method, I will have my full warranty back?

Cant write to/view Interal storage [GNEX]

I cant not view files on my internal SD card. For example pictures in the gallery only display blank thumbnails but ARE THERE. This means i cant download anything and save it (Apps from the play store are fine) but i CAN view files with no problem while connected to a computer and move files to my phone on there with no issues but downloading straight to the phone wont work. I was flasing experemental roms when this happend and yes, i did make a back up but this made no diffrence. I have flashed stock 4.0.2, 4.0.3, locked the bootloader, unroooted, re unlocked the bootloader but the problem persists. Any idea's anyone?

Can you clarify if it's only existing files that are already on your phone, or does this happen for all new files created on your phone as well (taking new photos and videos for example).
Sent from my Galaxy Nexus using Tapatalk

-
Yes it does, but apps are not effected. But these are put on a diffrent space on the phone i think. But no, for example when i take a picture it will not save it, i cannot download files of the internet either. Any idea's would be appreciated

JustArchiee said:
[snip]
Any idea's would be appreciated
Click to expand...
Click to collapse
Copy your data to your computer, erase all the partitions on your device, and re-flash your ROM.

efrant said:
Copy your data to your computer, erase all the partitions on your device, and re-flash your ROM.
Click to expand...
Click to collapse
+ 1
Sent from my Galaxy Nexus using Tapatalk

Ok just to make sure (Yes - im a noob) just plug it into the computer and wipe everything yes?

How to wipe your device completely
JustArchiee said:
Ok just to make sure (Yes - im a noob) just plug it into the computer and wipe everything yes?
Click to expand...
Click to collapse
N00b step-by-step
1) Ensure you have the drivers installed properly on you computer;
2) Copy everything you want to keep off of your device (i.e., to the cloud, to your computer, etc.);
3) Reboot your device into fastboot mode: turn it off, then hold vol+ & vol- & press and hold power;
4) Plug your GN to your computer;
5) Download the attachment to your computer, and extract the contents to a directory;
5a) Download this and extract the files within to the same directory (extract ALL archives, including the zip inside the second archive);
6) Open a command prompt in that directory;
7) Make sure your computer recognizes your device by typing: fastboot devices
8) Wipe everything by typing the following:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot erase cache
9) Flash the ICL53F system partition: fastboot flash system system.img
10) Flash the ICL53F data partition: fastboot flash userdata userdata.img
11) Flash the ICL53F boot partition: fastboot flash boot boot.img
12) Download CWM from here, save it to the same directory and rename it to cwm.img
13) Flash CWM: fastboot flash recovery cwm.img
14) Now you are on the stock ROM with CWM recovery. You can flash whatever ROM you want now in recovery.

Ok all good till '9)' i get 'cannot determine image filename for system.img'
Is there a certion way to open Command prompt?

Ahh don't worry i used wugfreash to flash everything. Thanks so much for you help - Will donate

JustArchiee said:
Ok all good till '9)' i get 'cannot determine image filename for system.img'
Is there a certion way to open Command prompt?
Click to expand...
Click to collapse
For others whovarevhaving that issue: you need to extract ALL the archives. There is a zip inside the archive inside the main archive...
Sent from my Galaxy Nexus using Tapatalk

This may have been a permissions issue. I wish I'd replied sooner
Sometimes pushing files to /sdcard from an incorrectly programmed ROM or over ADB in recovery can result in making "root" the owner of all the files. I experienced this when I pushed a bunch of files to my phone over ADB while in ClockworkMod.
I posted a solution here: http://forum.xda-developers.com/showthread.php?p=23767694

[HOWTO] Install Google SDK and ADB drivers in Windows 7

I'm posting this guide because my Galaxy Nexus I9250 I purchased from Google Play would not to recognize in any way, shape or form the official Google drivers provided into Android SDK. Obviously, if you installed any Samsung drivers, you will have to uninstall them. Personally, I always connect the device to my PC and let Windows Update find the best driver. In this way, the basic Windows interface is handled by Microsoft drivers:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google SDK 64bits Setup
This is a quick howto for those who actually want to setup their SDK properly in Windows 7 64bits. I saw a lot of craziness on the Internet so I wanted to share how I set a proper 64bits development environment.
Android SDK: http://developer.android.com/sdk/ (installer_r21-windows.exe)
Java JDK: http://www.oracle.com/technetwork/java/javase/downloads/ (jdk-7u5-windows-x64.exe)
Eclipse Classic: http://www.eclipse.org/downloads/ (eclipse-SDK-4.2-win32-x86_64.zip)
First, download the 64bits software versions, not 32bits. Android SDK is the only 32bits package but it will work fine with 64bits development tools, if you know what you are doing. Obviously, if you are on a 32bits OS download the 32bits software versions. We are discussing a 64bits setup, so let's move on.
Install Java JDK and only if you run a 64bits OS, set a JAVA_HOME variable with value "%ProgramFiles%\Java\jdk1.7.0_05" into Environment Variables (adjust the value with whatever version you downloaded):
Reboot your PC to enable all the settings done above.
Next, install Android SDK. You only need to download Android SDK Tools, Android SDK Platform-tools and Google USB Driver, if you just want to play with the phone. If you plan to develop apps, install also the API of your choice and Eclipse Classic (yes, that is the recommended version by Google devs).
To make available everywhere your platform tools (adb, fastboot, etc.), add your platform-tools directory to Path:
Myself, I installed the SDK in "C:\Program Files (x86)\Android\sdk" directory, so my path looks like:
Code:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;%ProgramFiles(x86)%\Android\sdk\platform-tools
Technically, you need to add the ";%ProgramFiles(x86)%\Android\sdk\platform-tools" location at the end of your current path.
Reboot your PC to enable all the settings done above.
Now, on with the fun part. There are 2 drivers needed for Google Nexus, the Composite ADB and Bootloader (Android 1.0).
Android Composite ADB Interface Driver
First, enable USB Debugging in your phone:
Plug your USB cable, you will notice in Device Manager the failed driver notice:
Right-click on it and select "Update Driver Software...", then "Browse my computer for driver software". Don't bother browsing to your ADB USB driver location, it will not install the proper driver. Instead, click on "Let me pick from a list of device drivers on my computer" button:
Make sure "Show All Devices" is selected and click on Next button:
With the list of devices displayed, click on Have Disk button:
Browse to your Google Driver location, mines is set in "C:\Program Files (x86)\Android\sdk\extras\google\usb_driver":
Pick the "Android Composite ADB Interface" driver and click on Next button:
You will be asked to accept the driver installation, do it and be done with this part of drivers setup:
Android Bootloader Interface Driver
Make sure USB Debugging is still enabled in your phone. With the USB cable connected, manually boot into Bootloader mode by powering down your phone and restarting it with all 3 buttons pressed (Volume Up + Volume Down + Power). You will notice in Device Manager the new unrecognized Android 1.0 device. Follow the same steps explained above and when you reach the driver selection, choose "Android Bootloader Interface":
To test the setup, run few basic commands:
Code:
adb devices
adb reboot bootloader
fastboot reboot
You are done, enjoy the official USB drivers from Google.

Quick Root Command references
Nexus Images: https://developers.google.com/android/nexus/images#mysid
CWM: http://www.clockworkmod.com/rommanager/
Superuser: http://hosted.androidsu.com/superuser/
SuperSU: http://download.chainfire.eu/205/SuperSU/
Root Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install Supersuer + Root (match the file names with the ones downloaded):
Code:
adb push Superuser-3.1.3-arm-signed.zip /sdcard/
adb reboot bootloader
fastboot boot recovery-clockwork-6.0.1.0-maguro.img
Flash Superuser: On device, select "install zip from sdcard", then "choose zip from sdcard" and select "Superuser-3.1.3-arm-signed.zip". Confirm install, then "+++++Go Back+++++" and "reboot system now".
3) Lock the bootloader (optional):
Code:
adb reboot bootloader
fastboot oem lock
Stock Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install the image files (match the file names with the ones downloaded).
Commands are listed inside flash-all.sh shell script, validate them:
Code:
adb reboot bootloader
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jro03c.zip
3) Lock the bootloader:
Code:
adb reboot bootloader
fastboot oem lock
Backup Device
Code:
adb backup -apk -shared -all -f backup.ab

TECK said:
Nexus Images: https://developers.google.com/android/nexus/images
CWM: http://www.clockworkmod.com/rommanager/
Superuser: http://hosted.androidsu.com/superuser/
Root Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install Supersuer + Root (match the file names with the ones downloaded):
Code:
adb push Superuser-3.1.3-arm-signed.zip /sdcard/
adb reboot bootloader
fastboot boot recovery-clockwork-6.0.1.0-maguro.img
Flash Superuser: On device, select "install zip from sdcard", then "choose zip from sdcard" and select "Superuser-3.1.3-arm-signed.zip". Confirm install, then "+++++Go Back+++++" and "reboot system now".
3) Lock the bootloader (optional):
Code:
adb reboot bootloader
fastboot oem lock
Stock Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install the image files (match the file names with the ones downloaded).
Commands are listed inside flash-all.sh shell script, validate them:
Code:
fastboot reboot-bootloader
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jro03c.zip
3) Lock the bootloader:
Code:
adb reboot bootloader
fastboot oem lock
Click to expand...
Click to collapse
This is nice I wish this was around 2 weeks earlier when I got this phone this would have made setting up a lot easier. This deserves to be sticky
Sent from my Galaxy Nexus using Tapatalk 2

I added also a quick Howto for the Android SDK setup in Windows 64bits. Lots of crazy info out there on the Internet so I said might as well post it so others can do it right in their computers.

TECK said:
I added also a quick Howto for the Android SDK setup in Windows 64bits. Lots of crazy info out there on the Internet so I said might as well post it so others can do it right in their computers.
Click to expand...
Click to collapse
glad i came across this post. I'm going to use your instructions to return my daughter's GSM Galaxy Nexus to stock JB so we can determine if the proximity sensor is bad or if it's due to the other JB ROMs i've put on her phone. right now, the proximity sensor does not turn the screen off when she places the phone to her ear during phone calls.
question: i prefer not to overwrite the CWM recovery, so i'm planning to remove the recovery.img from the image-yakju-jro03c.zip file before updating via fastboot. next i'll reboot to recovery and flash the superuser zip file to gain ROOT access. my question is this: will removing the recovery img cause the update via fastboot to fail? thanks to anyone who replies to my question.

I would simply flash the entire stock image without skipping any files. Then temporarily flash back the CWM, just to keep the phone stock.
Code:
adb reboot bootloader
fastboot boot recovery-clockwork-6.0.1.0-maguro.img
This will not write CWM to the phone, but rather use it once to bypass the stock recovery. Personally, I'm only interested to root the device and will not install custom ROM's. But even if you do install custom ROM's, you rarely need CWM... and if you do, you will work near your computer where you have access to adb.

This is a splendid guide!
Absolutely what all new Androiders need.
Sent from my Transformer TF101 using Tapatalk 2

Did everything you said and got to the point where I was testing those commands, and it says devices attached but my device isnt listed. I was still in boootloader and fastboot usb was attached. is that correct? any ideas? I do have CM9 installed and there are plenty of options regarding root access.

TECK said:
To test the setup, run few basic commands:
Code:
adb devices
adb reboot bootloader
fastboot reboot
Click to expand...
Click to collapse
Mate, when I type "adb devices" I am getting an error saying that "'adb' is not recognized as an internal or external command, operable program or batch file"
I installed Android SDK and Java SE JDK and it all went well. I installed the drivers and when in fastboot mode, I get "Samsung Galaxy Nexus BootLoader Interface" in Device Manager, which I think is what I should be getting.
Would you know what is it that I am missing? Could it be something that I haven't installed from the Android SDK? Thanks again for the tutorial.

You need to change to the directory in which you installed the SDK
So like:
cd <insert directory here and remove the arrow brackets>
Sent from my Galaxy Nexus using Tapatalk 2

geoffcorey said:
You need to change to the directory in which you installed the SDK
So like:
cd <insert directory here and remove the arrow brackets>
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll try that, thanks.
His screenshot shows that he is not in the SDK installed folder though.
My phone was in fastboot mode when I tried that. I hope that's the correct mode.
One more thing, when I choose go to Recovery in fastboot, the red triangle comes up, but Volume Up + Power doesn't do anything and I have to take out the battery in order to reboot.

bozint said:
I'll try that, thanks.
His screenshot shows that he is not in the SDK installed folder though.
My phone was in fastboot mode when I tried that. I hope that's the correct mode.
Click to expand...
Click to collapse
That is because you missed this part:
TECK said:
[snip]
To make available everywhere your platform tools (adb, fastboot, etc.), add your platform-tools directory to Path:
Myself, I installed the SDK in "C:\Program Files (x86)\Android\sdk" directory, so my path looks like:
Code:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;%ProgramFiles(x86)%\Android\sdk\platform-tools
Technically, you need to add the ";%ProgramFiles(x86)%\Android\sdk\platform-tools" location at the end of your current path.
Reboot your PC to enable all the settings done above.
Click to expand...
Click to collapse
bozint said:
One more thing, when I choose go to Recovery in fastboot, the red triangle comes up, but Volume Up + Power doesn't do anything and I have to take out the battery in order to reboot.
Click to expand...
Click to collapse
What you are seeing is the main screen for the stock recovery. To access the menu from that screen, hold power and press volume up.

efrant said:
That is because you missed this part
Click to expand...
Click to collapse
I did add a line in the Environment Variables, I installed the Android SDK in the root of "C" though (C:\!Android\.....). It might be the issue, and I will use default path after I uninstall it and then install it again. I also added the Java SE in the Environment Variables.
efrant said:
What you are seeing is the main screen for the stock recovery. To access the menu from that screen, hold power and press volume up.
Click to expand...
Click to collapse
Thanks for this, I got into now. I guess all the time I was holding vol.up and then power.
I am on stock now, so in order to root, should I be following the following procedure?
Stock Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install the image files (match the file names with the ones downloaded).
Commands are listed inside flash-all.sh shell script, validate them:
Code:
fastboot reboot-bootloader
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jro03c.zip
3) Lock the bootloader:
Code:
adb reboot bootloader
fastboot oem lock
My baseband is XXLF1, and the build is JRO03C.I9250WLH2, if this helps in any way.
Thanks for the comment guys, much appreciated.
====================================================
EDIT: @efrant, I just checked your guide on rooting without unlocking the bootloader, so should I fail with the backup you also referenced in you guide, I will give it a try. The phone is rather new though, so even if I lose some apps it's not that big a deal.

bozint said:
[snip]
I am on stock now, so in order to root, should I be following the following procedure?
Click to expand...
Click to collapse
I think you are confusing a few things. Unlocking the bootloader is not the same as getting root. You should have a look at the "basics" link in my signature.

bozint said:
I did add a line in the Environment Variables, I installed the Android SDK in the root of "C" though (C:\!Android\.....).
Click to expand...
Click to collapse
So the path was not the issue. Originally I had this in Path in the Environment Variables: "....;%!Android%\Google_Dev\android-sdk\platform-tools" and adb did not work unless I went directly inside the platform-tools folder in command prompt.
I then tried to add additional line in Environment Variables for the whole path, without the % symbol (C:\!Android\Google_Dev\android-sdk\platform-tools). And it worked, now adb lists the device at any time and location.
The final line in Path looks like this: ....bunch of lines......;%!Android%\Google_Dev\android-sdk\platform-tools;C:\!Android\Google_Dev\android-sdk\platform-tools

bozint said:
Mate, when I type "adb devices" I am getting an error saying that "'adb' is not recognized as an internal or external command, operable program or batch file"
Click to expand...
Click to collapse
If you add adb to the Windows path, you will not get this error. I explained into tutorial what to do.
Edit: Never mind, efrant explained well what to do.

efrant said:
I think you are confusing a few things. Unlocking the bootloader is not the same as getting root. You should have a look at the "basics" link in my signature.
Click to expand...
Click to collapse
I got it rooted now, but I need to do some additional reading yes. I'll read the guide and hopefully things will be more clear. Thanks guys.

bozint said:
I am on stock now, so in order to root, should I be following the following procedure?
Click to expand...
Click to collapse
No. The tutorial has separate sections, Root Device" and "Stock Device", not "Rooted Device". You want to root, so you follow the "Root" procedure, right?

Does anyone have a separate link to the ADB drivers for windows? I need this pc to recognize my N7 in bootloader etc but I don't want to go through the whole Java SDK etc hassle to get ADB just to get the drivers, it's not my pc.
Thanks

Logic_ said:
Does anyone have a separate link to the ADB drivers for windows? I need this pc to recognize my N7 in bootloader etc but I don't want to go through the whole Java SDK etc hassle to get ADB just to get the drivers, it's not my pc.
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1379875

Nexus won't Boot after 4.3 OTA Update

Hello,
After having waited for SuperSu to support the survival mode, I finally decided to apply the 4.3 update to my Nexus.
It seemed to have gone well just like the other times.
The problem rose after the updated was installed and the phone rebooted. It got stuck onto the "X" screen.
I removed the battery and tried to boot again. Same thing. It gets stuck on boot.
Is there any way out of this? The phone was perfectly fine and I have lots of data on it.
Please let me know if there's any fix to this issue.
Thank you very much for helping.

I found the solution to my problem.
It seems that the only way out of this problem is reflashing.
Here's exaclty what I did. I hope it will help someone in my same situation. I DID perform a backup through TWRP before flashing and pulled it through Galaxy Nexus Toolkit (Found somewhere here on XDA) [It could have been done via the ADB tool found in the Android SDK Toolkit, available on Google].
The stock images were found here and then extracted in "...\adb\sdk\platform-tools"
0) Phone Shut Down;
1) Go to Bootloader by pressing: Power + Vol Up + Vol Down;
2) Run the Galaxy Nexus Toolkit;
3) Select current model (mine was a GSM Model 4.2.2);
4) Input Option 10 ("Boot Custom Recovery Without Permanently Flashing it") --> Option 2 ("Boot to TWRP Touch Recovery...") --> type "yes";
5) On the phone, wait for TWRP to be loaded, then select "Backup" and check all the boxes, set the Backup Name;
6) Swip to Back Up and wait for it to be done (It may take a few minutes). Once done, note down the path where the files where backed up;
7) Then, back on the PC and Galaxy Nexus Toolkit (perhaps it may need to be restarted), select Option 14 ("Pull Files or Folders from the Device". --> Option 2 ("Manually Answer Question") --> type "yes" --> type the full directory you want to be pulled onto your PC (for example, mine was: "/data/media/0/TWRP/BACKUPS/016B7378060040" --> Wait, it will take a while depending on how big the backup is;
8) The files that have just been pulled are inside "...\Galaxy Nexus ToolKit\pulled_files_are_put_here";
9) Still on the PC, we open a console instance, we move to the following folder of the extracted Android SDK: "...\adb\sdk\platform-tools";
---------
We have to make sure that all the .img files we downloaded are exactly in the folder mentioned in point 9), ALL OF THEM (so the ones in the subfolders need to be in the above mentioned SDK folder as well for it to work properly); In my case they were: "bootloader-maguro-primemd04.img", "radio-maguro-i9250xxlj1.img", "boot.img", "recovery.img", "system.img".
Pay ATTENTION: the first two images "bootloader-maguro..." and "radio-maguro..." might be different in name depending on your phone, whereas the othes should be the same. What follows is exactly what I wrote, so the first two images will be the above mentioned: please adjust your command accordingly.
----------
10) On the Phone (still on TWRP) select the option "Reboot", then "Bootloader";
11) On the PC type:
"fastboot flash bootloader bootloader-maguro-primemd04.img" (Again, may be different in your case)
"fastboot reboot-bootloader"
"fastboot flash radio radio-maguro-i9250xxlj1.img"
"fastboot reboot-bootloader"
"fastboot flash boot boot.img"
"fastboot reboot-bootloader"
"fastboot flash recovery recovery.img"
"fastboot reboot-bootloader"
"fastboot flash system system.img"
The last one may take quite a "long" time, so be ready to wait.
[I know it may not be necessary to reboot every time an image is flashed but that's how I did it, plus anything should go wrong we can get to know what didn't work]
11) On the Phone, scroll down the options by pressing Vol Down (or Up), when you see the option "Start", hit the power button to start Android.
That's it.
I hope it's of any help .

How to root Your MICROMAX IN1B (64GB)

First of all, before i start, I'll make this clear, i have done this procedure and rooted my IN1B successfully BUT if anything goes wrong with your device,
I WILL NOT BE RESPONSIBLE FOR BRICKED DEVICES
PreRequisites (Stuff you will need)
So, Let's get into it.
Before Begining, Here are the things you'll need :-
1. A windows PC with all the necessary drivers.
2. ADB and fastboot which you can get from here.
3. A USB C cable, preferably the original one.
4. Make sure your Device is atleast 60% charged.
5. Backup all your data because the very first step will reset your phone.
NOTE- MICROMAX DOES NOT PROVIDE ANY USB DRIVERS. So i had trouble finding the Drivers too, so i recomend you use "Driver booster" it's free, you can get it from here. After installing the driver booster, let it scan and then update all the drivers related to "Android" and "ADB".
That's it, once you are done with all the above points we are good to start.
These are the PATCHED files you need to flash to root your device.
1. Get the files from Here
After you download the files, copy and paste the files in the folder where ADB & Fastboot is located, if you have not changed the Install location, it should be at this directory- C:\Program Files (x86)\Minimal ADB and Fastboot
After you paste all the 3 downloaded files in the ADB folder, the process will now start.
Unlocking the BootLoader
The first step is to unlock the boot loader.
1. Connect your device with a USB C cable.
2. Enable USB debugging from the developer options-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Now run ADB and run this command- adb devices As you run this, something like this should appear on your mobile-
4. Now allow it and Voila!, you are now connected!
5. Now find "OEM Unlocking" and enable it.
6. Now enter this command- adb reboot bootloader As you run this command your device will reboot and show a black screen with only "fastboot" written on it.
7. Now finally Enter this command- fastboot flashing unlock
8. Now it will ask you to confirm, if you change your mind and dont want to root now, press the "Volume-Down" Button or if you want to root, press the "Volume-Up" button.
NOTE- UNLOCK MAY VOID SOFTARE WARRANTY. FOR DETAILS, CHECK THIS (Read 6e)
9. Awesome! Now you have unlocked your boot loader!!
Flashing the Patched Files
Now remember you need the 3 files i linked above, once you get them, paste them in the ADB folder.
Make sure you DON't change the file names.
Let's Start!
1. Run this command- fastboot flash boot patched_boot.img
2. After that, Run this- fastboot --disable-verification flash vbmeta vbmeta.img
3 And he final command, run this- fastboot flash recovery recovery.img
After all these 3 complete succesfully, Just run- fastboot reboot This will start your device normally, go on and set up your device.
1.As you complete the setup, you should see the magisk app-
2. Now the magisk app will ask you to install the full version, click on confirm and it will install the magisk app, you will have to turn on the "Unknown sources" option.
3. Once it is installed, you can ENJOY YOUR ROOTED IN 1B!!
IF YOU NEED ANY HELP, FEEL FREE TO WRITE IT BELOW, OR DM ME ON TELEGRAM- Âkio or DISCORD- Âkio#7134

Akahat27 said:
First of all, before i start, I'll make this clear, i have done this procedure and rooted my IN1B successfully BUT if anything goes wrong with your device,
I WILL NOT BE RESPONSIBLE FOR BRICKED DEVICES
PreRequisites (Stuff you will need)
So, Let's get into it.
Before Begining, Here are the things you'll need :-
1. A windows PC with all the necessary drivers.
2. ADB and fastboot which you can get from here.
3. A USB C cable, preferably the original one.
4. Make sure your Device is atleast 60% charged.
5. Backup all your data because the very first step will reset your phone.
NOTE- MICROMAX DOES NOT PROVIDE ANY USB DRIVERS. So i had trouble finding the Drivers too, so i recomend you use "Driver booster" it's free, you can get it from here. After installing the driver booster, let it scan and then update all the drivers related to "Android" and "ADB".
That's it, once you are done with all the above points we are good to start.
These are the PATCHED files you need to flash to root your device.
1. Get the files from Here
After you download the files, copy and paste the files in the folder where ADB & Fastboot is located, if you have not changed the Install location, it should be at this directory- C:\Program Files (x86)\Minimal ADB and Fastboot
After you paste all the 3 downloaded files in the ADB folder, the process will now start.
Unlocking the BootLoader
The first step is to unlock the boot loader.
1. Connect your device with a USB C cable.
2. Enable USB debugging from the developer options-
View attachment 5326971
3. Now run ADB and run this command- adb devices As you run this, something like this should appear on your mobile-
View attachment 5326979
4. Now allow it and Voila!, you are now connected!
5. Now find "OEM Unlocking" and enable it.
View attachment 5326983
6. Now enter this command- adb reboot bootloader As you run this command your device will reboot and show a black screen with only "fastboot" written on it.
7. Now finally Enter this command- fastboot flashing unlock
8. Now it will ask you to confirm, if you change your mind and dont want to root now, press the "Volume-Down" Button or if you want to root, press the "Volume-Up" button.
NOTE- UNLOCK MAY VOID SOFTARE WARRANTY. FOR DETAILS, CHECK THIS (Read 6e)
9. Awesome! Now you have unlocked your boot loader!!
Flashing the Patched Files
Now remember you need the 3 files i linked above, once you get them, paste them in the ADB folder.
Make sure you DON't change the file names.
Let's Start!
1. Run this command- fastboot flash boot patched_boot.img
2. After that, Run this- fastboot --disable-verification flash vbmeta vbmeta.img
3 And he final command, run this- fastboot flash recovery recovery.img
After all these 3 complete succesfully, Just run- fastboot reboot This will start your device normally, go on and set up your device.
1.As you complete the setup, you should see the magisk app-
View attachment 5326989
2. Now the magisk app will ask you to install the full version, click on confirm and it will install the magisk app, you will have to turn on the "Unknown sources" option.
3. Once it is installed, you can ENJOY YOUR ROOTED IN 1B!!
IF YOU NEED ANY HELP, FEEL FREE TO WRITE IT BELOW, OR DM ME ON TELEGRAM- Âkio or DISCORD- Âkio#7134
Click to expand...
Click to collapse
ON which android version u have done this given me firmware name

pankspoo said:
ON which android version u have done this given me firmware name
Click to expand...
Click to collapse
I did on the android 10 which it initially came with..