Develop Bugs

[HOW TO] Unlock Bootloader & Root GSM Nexus (4.0.x devices only)

I know there a few tutorials already on here, however it seems quite a lot of people are eitiher asking questions about the ADB method, or cannot understand other methods. So i'll try and put it all in one easy to follow tutorial. This is for the latest version on Android 4.0.x.
For this method we are going to use Paul O'Briens Superboot.
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
Click to expand...
Click to collapse
APPLY THIS AT YOUR OWN RISK!
Download the latest version of Superboot: DOWNLOAD
You might need the drivers, however its worth getting them anyway as you'll probably need them in the future: DOWNLOAD DRIVERS
If you get you might need the USB drivers: DOWNLOAD
Windows
1) Extract the contents of the above file into C:\root
2) Power your device off
3) Connect your phone to your computer
4) Put device into the bootloader by holding down Vol Up + Vol Down + Power
5) Open up cmd and navigate to by typing to following (Hit enter after each line):
cd C:/
cd root
6) Unlock your bootloader by typing - this will wipe your device!:
fastboot-windows oem unlock
7) You should get a warning on your phone. Use the volume keys to select an option, and press the power button to confirm it
8) Your bootloader should now say that it is unlocked at the bottom
9) To root your device, double click:
install-superboot-windows.bat
10) You should now be able to reboot your phone and it will have root
11) Optional: Install CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642
Make a Nandroid Backup!
Click to expand...
Click to collapse
Linux
1) Extract the contents of the above file into a folder
2) Power your device off
3) Connect your phone to your computer
4) Put device into the bootloader by holding down Vol Up + Vol Down + Power
5) Open up terminal and navigate to the folder used in step 1
6) Unlock your bootloader by typing - this will wipe your device!:
./fastboot-linux oem unlock
7) You should get a warning on your phone. Use the volume keys to select an option, and press the power button to confirm it
8) Your bootloader should now say that it is unlocked at the bottom
9) To root your device, type the following (Hit enter after each line):
chmod +x install-superboot-linux.sh
./install-superboot-linux.sh
10) You should now be able to reboot your phone and it will have root
11) Optional: Install CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642
Make a Nandroid Backup!
Click to expand...
Click to collapse
OS X
1) Extract the contents of the above file into a folder
2) Power your device off
3) Connect your phone to your computer
4) Put device into the bootloader by holding down Vol Up + Vol Down + Power
5) Open up terminal and navigate to the folder used in step 1
6) Unlock your bootloader by typing - this will wipe your device!:
./fastboot-mac oem unlock
7) You should get a warning on your phone. Use the volume keys to select an option, and press the power button to confirm it
8) Your bootloader should now say that it is unlocked at the bottom
9) To root your device, type the following (Hit enter after each line):
chmod +x install-superboot-mac.sh
./install-superboot-mac.sh
10) You should now be able to reboot your phone and it will have root
11) Optional: Install CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642
Make a Nandroid Backup!
Click to expand...
Click to collapse
If i've missed any steps out such as downloading drivers etc, let me know what to add in etc. I did mine on OS X and it didn't require me to install anything extra
Update: it would appear some people are having issues with 4.1 rooting. I'll see what I can find an then update it. For the time being, just reflash the vanilla install and you should be fine. I'd imagine there's an incompatibility between this root and 4.1

Very nice indeed, might be worth doing a tutorial on how to return to stock if there isn't already one out there somewhere. Not many people know that it's possible to Fastboot OEM lock, I've tried it

Yeah I'm going to wait until there's a proper system.img about.
I got mine back to stock, however it was a complete bodge and highly advised against.
Locking the boot loader is the easy bit. It's going back to the default rom
Sent from my iPad 2 using Tapatalk

...but this should be moved to general i think. This subforum will br crowded next months.
sent from a kanged gt-i9000 using Tapatalk

It's based on development so I don't see why. General is anything to do with the phone. Unlocking and rooting is the first step of development
Sent from my iPad 2 using Tapatalk

Thank you for your work.
Just a small correction for your original post.
Instead of
fastboot-windows oem unlock
it's actually:
.\fastboot-windows oem unlock

Cheers. I'll edit that. Didn't work for me like that when I did it on a windows PC, however I'll add it in
Sent from my iPad 2 using Tapatalk

Maybe it worth to mention in the first post that many ppl (including me) had issues with this process, because we had no proper drivers installed first, and for that the solution was installing the newest PDAnet software. After that everything went pretty well.

Aylarth said:
Maybe it worth to mention in the first post that many ppl (including me) had issues with this process, because we had no proper drivers installed first, and for that the solution was installing the newest PDAnet software. After that everything went pretty well.
Click to expand...
Click to collapse
Ah yes. Added
Sent from my Galaxy Nexus using Tapatalk

I'm very new to this so prepare for a stupid question!
I'm trying to run this on a Mac, and when I'm trying to run fastboot oem unlock I get the following:
/Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac: No such file or directory
What could cause this?

helen_xxxx said:
I'm very new to this so prepare for a stupid question!
I'm trying to run this on a Mac, and when I'm trying to run fastboot oem unlock I get the following:
/Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac: No such file or directory
What could cause this?
Click to expand...
Click to collapse
Have you navigated to the folder where the files are located? Stupid question but not sure what you've done
Sent from my Galaxy Nexus using Tapatalk

Evostance said:
Yeah I'm going to wait until there's a proper system.img about.
Click to expand...
Click to collapse
Are the files from Peter Alfonso not suitable? They include boot.img, recovery.img, system.img and userdata.img
I want to uninstall clockwork mod and get back to stock recovery. I used Peter Alfonso's recovery.img file and did a "fastboot boot recovery.img" but I just got a picture of a droid with a red triangle. I was hoping that would work before I issued the "fastboot flash recovery recovery.img" command. As it didnt, I guess I'll have to wait to find out what the proper method is.

Evostance said:
Have you navigated to the folder where the files are located? Stupid question but not sure what you've done
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I extracted the .zip to /Users/extra_ham.
Then put the following in terminal: /Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac oem unlock
I wasn't sure whether I had to run 'cd' before doing that but terminal already appeared to be looking at extra_ham$.
I'm pretty sure it's something simple I'm missing.

Oppressa said:
Thank you for your work.
Just a small correction for your original post.
Instead of
fastboot-windows oem unlock
it's actually:
.\fastboot-windows oem unlock
Click to expand...
Click to collapse
I am pretty sure you don't need the .\ on Windows? Only Mac & Linux.

StuMcBill said:
I am pretty sure you don't need the .\ on Windows? Only Mac & Linux.
Click to expand...
Click to collapse
Thats what I thought. Worked without the .\ for me at work as its just an exe

helen_xxxx said:
I extracted the .zip to /Users/extra_ham.
Then put the following in terminal: /Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac oem unlock
I wasn't sure whether I had to run 'cd' before doing that but terminal already appeared to be looking at extra_ham$.
I'm pretty sure it's something simple I'm missing.
Click to expand...
Click to collapse
OK, If you files are in the folder r2-galaxynexus-superboot, open terminal and just type (after each line hit enter):
cd /Users/
cd extra_ham/
cd r2-galaxynexus-superboot
./fastboot-mac oem unlock
chandlerweb said:
Are the files from Peter Alfonso not suitable? They include boot.img, recovery.img, system.img and userdata.img
I want to uninstall clockwork mod and get back to stock recovery. I used Peter Alfonso's recovery.img file and did a "fastboot boot recovery.img" but I just got a picture of a droid with a red triangle. I was hoping that would work before I issued the "fastboot flash recovery recovery.img" command. As it didnt, I guess I'll have to wait to find out what the proper method is.
Click to expand...
Click to collapse
I tried that system.img and it bricked my phone. Couldn't get it to launch, it just hung on the animation. I did a boot to CWM, messed with some stuff and then the phone randomly launched. Its not a stock image, missing all the Google apps etc and the Gallery doesn't work. I think for now though, its the closest thing to a stock image we have

Brilliant thank you, will give it a try.
Think I need to tune up on Unix....

helen_xxxx said:
I extracted the .zip to /Users/extra_ham.
Then put the following in terminal: /Users/extra_ham/r2-galaxynexus-superboot./fastboot-mac oem unlock
I wasn't sure whether I had to run 'cd' before doing that but terminal already appeared to be looking at extra_ham$.
I'm pretty sure it's something simple I'm missing.
Click to expand...
Click to collapse
On OSX you can just drag the fastboot-mac file from finder into the terminal window and it will automatically fill in the path for you, then type the rest of the unlock command and hit enter

chandlerweb said:
Are the files from Peter Alfonso not suitable? They include boot.img, recovery.img, system.img and userdata.img
I want to uninstall clockwork mod and get back to stock recovery. I used Peter Alfonso's recovery.img file and did a "fastboot boot recovery.img" but I just got a picture of a droid with a red triangle. I was hoping that would work before I issued the "fastboot flash recovery recovery.img" command. As it didnt, I guess I'll have to wait to find out what the proper method is.
Click to expand...
Click to collapse
The Droid with triangle actually is stock recovery. When you see it just press power + volume down.
Sent from my Galaxy Nexus using XDA App

I hope the LTE version is as easy to root/unlock as this.
Knowing Verizon though...probably not.

Problem Rooting with Galaxy Nexus Toolkit

Hi,
I am attempting to Root my Galaxy Nexus (GSM) using the instructions in the Complete Guide given at How to Root Galaxy Nexus Jelly Bean / Ice Cream Sandwich! [GSM/Verizon/Sprint] [Windows] This tutorial seems to use the Galaxy Toolkit (v7.8.0). The most upto date version I could find is at Galaxy_Nexus_ToolKit_v10.1.0.exe which I used for my purpose. However I cannot seem to be able to root my device. I am hoping someone could help me.
The following is my run of this Toolkit after installing it: (My Entries are in Bold)
Check for update: Yes
Current ToolKit [V10.1.0], Latest Available [V10.5.0]
Current Mods Section [V3.4.0], Latest Available [V3.5.0]
Select Model 7. Android 4.2.1 (Build JOP40D)
FASTBOOT MODE [If serial shows, drivers are installed]
List of devices attached
ADB MODE
List of devices attached
014E100007012003 device
Selected 3. UnLock or Re-Lock your BootLoader [Fastboot Mode]
Selected1. UnLock Bootloader
Is your device in Fastboot Mode and you are ready to continue? no
Waiting for adb Mode
Rebooting to Fastboot Mode and continuing..
Phone reboots with Fastboot Mode i.e. I can see it in RED on the phone screen
Then what do I do i.e. choose Start, Restart bootloader or Recorvery mode
On the windows cmdline I get < waiting for device > and it sits there forever.
Thanks in advance to anyone who has ideas. If I have been unclear above, please ask.
O. O.

1. Don't use the toolkit
2. Learn to do it manually, it takes 10 minutes
In a nutshell, tho, you've not installed the fastboot drivers, hence it doing nothing

EddyOS said:
1. Don't use the toolkit
2. Learn to do it manually, it takes 10 minutes
In a nutshell, tho, you've not installed the fastboot drivers, hence it doing nothing
Click to expand...
Click to collapse
Why do you say not to use the Toolkit when the Complete Guide given in the sticky in this Forum recommends it? If what you say is true, then it should not be mentioned there.
O. O.

o.o. said:
Why do you say not to use the Toolkit when the Complete Guide given in the sticky in this Forum recommends it? If what you say is true, then it should not be mentioned there.
O. O.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1529058
rooting a nexus boils down to this:
1) install drivers
2) boot into fastboot
3) fastboot oem unlock
4) fastboot flash recovery cwmortwrp.img
5) flash su.zip
done.
you dont need a toolkit.

Solved
Zepius said:
http://forum.xda-developers.com/showthread.php?t=1529058
rooting a nexus boils down to this:
1) install drivers
2) boot into fastboot
3) fastboot oem unlock
4) fastboot flash recovery cwmortwrp.img
5) flash su.zip
done.
you dont need a toolkit.
Click to expand...
Click to collapse
Thank you Zep. I have no clue how I missed that link/FAQ. Anyway I got this to work using the Toolkit.
After trying a bit with the ToolKit I got this to work. I think my mistake may have been:
1. I needed to Install the Drivers first (I think it is option 1 in the Toolkit after you select your phone model number.)
2. I had no clue what Fastboot was. Basically you need to reboot your phone by powering it using Power & Volume UP & Down buttons all at the same time. In my above description where I got:
Is your device in Fastboot Mode and you are ready to continue?
Attach the device while in Fastboot Mode at this point and respond yes to the prompt. This worked for me
3. Have patience with the Toolkit. For some reason it take ridiculously the long time i.e. almost 5 mins sitting and doing nothing. Wait for it.
4. Finally I did a Factory Reset after this. It still maintained root after the reset. Since I did not have anything of value on my phone, it was OK.
Thank you all
O. O.

Please help,,questions after Rooting...

Hello,first of all I apologize if posting in wrong section..I have a Acer iconia tablet A100..have to say love it..well other day did some reading and searching and decided to root it,I followed the following proceed( http://forum.xda-developers.com/showthread.php?t=1531646).worked perfect with no issues..thanks xda for making it simple. My question is what's the best way to install recovery and what are some of the good roms recommended I can use...I appreciate for the help..thank you..

Check this thread out http://forum.xda-developers.com/showthread.php?t=1711125 it has recovery and rom info plus alot more

OK do I download the unlock boot loader n extract files.and run it..just a lil confused bout the codes on the thread..

Cheony81 said:
OK do I download the unlock boot loader n extract files.and run it..just a lil confused bout the codes on the thread..
Click to expand...
Click to collapse
Go in order you'll be fine.
Root, which you already did.
Install the boot loader, just extract the files and run the script with it connected on USB.
After that, and only after, install a recovery and you can turn install custom ROMs. That guide covers it all if you spend some time reading before jumping in, always a good idea.
Sent from my HTC DNA

thank you..when it says volume up and volume down to pick,what happens if you hit the wrong one..( i hit wrong key and said cancelled or time out..hit the reset button and then started over and picked correctly this time and hit power buttom to restart tablet..Am i doing ok now..
pio_masaki said:
Go in order you'll be fine.
Root, which you already did.
Install the boot loader, just extract the files and run the script with it connected on USB.
After that, and only after, install a recovery and you can turn install custom ROMs. That guide covers it all if you spend some time reading before jumping in, always a good idea.
Sent from my HTC DNA
Click to expand...
Click to collapse

1- Open a command prompt in your working folder (usually in your platform tools, mine is C:\android-sdk-windows\platform-tools) make sure you are administrator.
2- Connect Tablet to pc and get excited.
3- Type: adb devices (verify your Tab is connected and listed)
4- Type: adb reboot bootloader
5- Once bootloader is in fastboot type: fastboot flash recovery recovery.img
You will see writing recovery, flashing recovery, etc.
6- Once flashed Type: fastboot reboot
7- Profit
im a lil confused on this part..i downloaded the image just confused on the steps and adb? command promt? and do i put debug on or off?

ok i found on how to open cmd. i follow instructions when i type adb devices it tells me adb is not recognized as internal or external command ?am i missing a step or doing something wrong.. 1- Open a command prompt in your working folder (usually in your platform tools, mine is C:\android-sdk-windows\platform-tools) make sure you are administrator.
2- Connect Tablet to pc and get excited.
3- Type: adb devices (verify your Tab is connected and listed)
4- Type: adb reboot bootloader
5- Once bootloader is in fastboot type: fastboot flash recovery recovery.img
You will see writing recovery, flashing recovery, etc.
6- Once flashed Type: fastboot reboot
7- Profit
Cheony81 said:
1- Open a command prompt in your working folder (usually in your platform tools, mine is C:\android-sdk-windows\platform-tools) make sure you are administrator.
2- Connect Tablet to pc and get excited.
3- Type: adb devices (verify your Tab is connected and listed)
4- Type: adb reboot bootloader
5- Once bootloader is in fastboot type: fastboot flash recovery recovery.img
You will see writing recovery, flashing recovery, etc.
6- Once flashed Type: fastboot reboot
7- Profit
im a lil confused on this part..i downloaded the image just confused on the steps and adb? command promt? and do i put debug on or off?
Click to expand...
Click to collapse

Cheony81 said:
ok i found on how to open cmd. i follow instructions when i type adb devices it tells me adb is not recognized as internal or external command ?am i missing a step or doing something wrong.. 1- Open a command prompt in your working folder (usually in your platform tools, mine is C:\android-sdk-windows\platform-tools) make sure you are administrator.
2- Connect Tablet to pc and get excited.
3- Type: adb devices (verify your Tab is connected and listed)
4- Type: adb reboot bootloader
5- Once bootloader is in fastboot type: fastboot flash recovery recovery.img
You will see writing recovery, flashing recovery, etc.
6- Once flashed Type: fastboot reboot
7- Profit
Click to expand...
Click to collapse
That means you aren't in the folder where your adb.exe is. It'll be in with your rooting files usually.
Sent from my HTC DNA

ok the files i have downloaded so far are(ICS_rooting_A10x_A5xx) used this one to root device. (fastboot recovery) which i used to unlock bootloader..what steps do i have to do now and do i need to have debug on?
pio_masaki said:
That means you aren't in the folder where your adb.exe is. It'll be in with your rooting files usually.
Sent from my HTC DNA
Click to expand...
Click to collapse

Cheony81 said:
ok the files i have downloaded so far are(ICS_rooting_A10x_A5xx) used this one to root device. (fastboot recovery) which i used to unlock bootloader..what steps do i have to do now and do i need to have debug on?
Click to expand...
Click to collapse
Debugging should be on.
Copy your chosen recovery.img to the folder where your adb.exe is, if its in the rooting folder, put them there.
For ease I would make a folder called root so its like this
c:\root
Place the adb and fastboot files in there with the recovery image.
Open a command prompt and type
cd c:\root
Type
adb devices
Should now work properly and list some numbers
Then do
adb reboot bootloader
Then
fastboot flash recovery recovery.img
Where recovery.img is the name of the recovery image you downloaded and copied to the folder with adb.exe
Sent from my HTC DNA

ok i open the ics rotting folder,in there i have a folder that says tools, adb image,fastboot image, fastboot, runit-win/ is the adb image the adb.exe you talking bout? honest;y i am lost.. i have rooted phones before but this cmd got me confused sorry..
pio_masaki said:
Debugging should be on.
Copy your chosen recovery.img to the folder where your adb.exe is, if its in the rooting folder, put them there.
For ease I would make a folder called root so its like this
c:\root
Place the adb and fastboot files in there with the recovery image.
Open a command prompt and type
cd c:\root
Type
adb devices
Should now work properly and list some numbers
Then do
adb reboot bootloader
Then
fastboot flash recovery recovery.img
Where recovery.img is the name of the recovery image you downloaded and copied to the folder with adb.exe
Sent from my HTC DNA
Click to expand...
Click to collapse

i did a lil more reading can i use A100 TWRP recovery (TeamWin Recovery Project) 2.2.0+..seems a lil more easier to be honest instead of cwm?
Cheony81 said:
ok i open the ics rotting folder,in there i have a folder that says tools, adb image,fastboot image, fastboot, runit-win/ is the adb image the adb.exe you talking bout? honest;y i am lost.. i have rooted phones before but this cmd got me confused sorry..
Click to expand...
Click to collapse

Cheony81 said:
ok i open the ics rotting folder,in there i have a folder that says tools, adb image,fastboot image, fastboot, runit-win/ is the adb image the adb.exe you talking bout? honest;y i am lost.. i have rooted phones before but this cmd got me confused sorry..
Click to expand...
Click to collapse
Once again, the folder that has adb.exe is where you need to be working from. Open a command prompt, cd to wherever that folder is, then do the commands. You can also hold shift and right click in the folder and choose command prompt to open it right there.
Sent from my HTC DNA

ok something is not right...you talking bout adb.exe.but when i look in the files that i mentioned earlier the only thing there is adb image and adb command window icon which if i click on it it runs for a sec and closes//
pio_masaki said:
Once again, the folder that has adb.exe is where you need to be working from. Open a command prompt, cd to wherever that folder is, then do the commands. You can also hold shift and right click in the folder and choose command prompt to open it right there.
Sent from my HTC DNA
Click to expand...
Click to collapse

Cheony81 said:
ok something is not right...you talking bout adb.exe.but when i look in the files that i mentioned earlier the only thing there is adb image and adb command window icon which if i click on it it runs for a sec and closes//
Click to expand...
Click to collapse
Your show extensions are off. The one that opened the prompt was it. Its not run directly, its used in a command prompt with a command. Open your prompt there or change its directory to where it is, then carry on with the instructions.
I take it all your other rooted devices had one click setups, this is a very basic device to work on, it just doesn't have a program doing it for you. This seriously should take as long as it took me to write this post to do from start to finish.
Sent from my HTC DNA

ok figured it out now i put all files together now..should i leave it in my documents or put it in my c folder..

is it power+vol up or down

I think its power on with the volume closest to the power button for fast boot, its been awhile though it may be the other one.
Sent from my HTC DNA

i just did it and showed android guy then showed him laying down with a red triangle simble coming out his stomach

Cheony81 said:
i just did it and showed android guy then showed him laying down with a red triangle simble coming out his stomach
Click to expand...
Click to collapse
Then try the other one.
Sent from my HTC DNA

Upgrade Stock 4.2.2 to Stock 4.3 from Android Factory Images

1. Download the 4.3 factory images for Takju from http://goo.gl/ABbAmc
2. Extract files using 7-zip on Windows (you need to extract twice and will get the files as: bootloader-xxx.img; radio-xxx.img and image-xxx.zip)
3. Copy these files to the location android-sdk/platform-tools/ (if you have the android-sdk installed or to the location where adb & fastboot is)
4. Plug in your Galaxy Nexus (ensure Debug option is enabled under Developer Settings
5. Follow these commands:
a. adb reboot bootloader
b. fastboot flash bootloader bootloader-xxx.img
c. fastboot reboot-bootloader
d. fastboot flash radio radio-xxx.img
e. fastboot reboot-bootloader
f. fastboot update image-xxx.zip
This would update your Galaxy Nexus from Stock 4.2.2 to Stock 4.3 without losing any data/apps
Note:
1. If you using Windows follow the video tutorial to setup adb and fastboot http://goo.gl/jGcic
2. If you are on Mac, use ./ before the commands for execution
Note 2: With this method you don't need to remove the userdata.img as the command "fastboot update image-xxx.zip" does not touch the userdata on your device.
*Disclaimer: I have followed the above to the T and moved from Stock 4.2.2 to Stock 4.3 with Unlocked Bootloader, but you follow these at your own risk.

I have lost my data.
freezer2000 said:
1. Download the 4.3 factory images for Takju from
2. Extract files using 7-zip on Windows (you need to extract twice and will get the files as: bootloader-xxx.img; radio-xxx.img and image-xxx.zip)
3. Copy these files to the location android-sdk/platform-tools/ (if you have the android-sdk installed or to the location where adb & fastboot is)
4. Plug in your Galaxy Nexus (ensure Debug option is enabled under Developer Settings
5. Follow these commands:
a. adb reboot bootloader
b. fastboot flash bootloader bootloader-xxx.img
c. fastboot reboot-bootloader
d. fastboot flash radio radio-xxx.img
e. fastboot reboot-bootloader
f. fastboot update image-xxx.zip
This would update your Galaxy Nexus from Stock 4.2.2 to Stock 4.3 without losing any data/apps
Note:
1. If you using Windows follow the video tutorial to setup adb and fastboot
2. If you are on Mac, use ./ before the commands for execution
Note 2: With this method you don't need to remove the userdata.img as the command "fastboot update image-xxx.zip" does not touch the userdata on your device.
*Disclaimer: I have followed the above to the T and moved from Stock 4.2.2 to Stock 4.3 with Unlocked Bootloader, but you follow these at your own risk.
I have lost all my apps/data and I have followed this post.
Thanks.
Click to expand...
Click to collapse

You MUST remove userdata.img from image-XXXXX.zip

EvenStar.III said:
freezer2000 said:
1. Download the 4.3 factory images for Takju from
2. Extract files using 7-zip on Windows (you need to extract twice and will get the files as: bootloader-xxx.img; radio-xxx.img and image-xxx.zip)
3. Copy these files to the location android-sdk/platform-tools/ (if you have the android-sdk installed or to the location where adb & fastboot is)
4. Plug in your Galaxy Nexus (ensure Debug option is enabled under Developer Settings
5. Follow these commands:
a. adb reboot bootloader
b. fastboot flash bootloader bootloader-xxx.img
c. fastboot reboot-bootloader
d. fastboot flash radio radio-xxx.img
e. fastboot reboot-bootloader
f. fastboot update image-xxx.zip
This would update your Galaxy Nexus from Stock 4.2.2 to Stock 4.3 without losing any data/apps
Note:
1. If you using Windows follow the video tutorial to setup adb and fastboot
2. If you are on Mac, use ./ before the commands for execution
Note 2: With this method you don't need to remove the userdata.img as the command "fastboot update image-xxx.zip" does not touch the userdata on your device.
*Disclaimer: I have followed the above to the T and moved from Stock 4.2.2 to Stock 4.3 with Unlocked Bootloader, but you follow these at your own risk.
I have lost all my apps/data and I have followed this post.
Thanks.
Click to expand...
Click to collapse
If you follow the steps as they are apps/data stays intact.... Unless you had a locked Bootloader. Unlocking the bootloader formats the complete storage. Else the command to remove the complete userdata partition is : fastboot update -w image-xxx.zip
Click to expand...
Click to collapse

I cant boot into android. Can I just reboot to bootloader and enter the commands?
Or do i need to be on adb sideload mode?
Sent from my YP-GP1 using xda app-developers app

Worked !! Thx

Flashed it with Mobile ODIN
I flashed it with Chainfire's MobileODIN. No problems with updating to 4.3 but lost root (everoot in Odin would not stick). Wiped data is not an issue as I backed it up. Will same root method as before work? Or do I need to wait for new method?

freezer2000 said:
1. Download the 4.3 factory images for Takju from http://goo.gl/ABbAmc
2. Extract files using 7-zip on Windows (you need to extract twice and will get the files as: bootloader-xxx.img; radio-xxx.img and image-xxx.zip)
3. Copy these files to the location android-sdk/platform-tools/ (if you have the android-sdk installed or to the location where adb & fastboot is)
4. Plug in your Galaxy Nexus (ensure Debug option is enabled under Developer Settings
5. Follow these commands:
a. adb reboot bootloader
b. fastboot flash bootloader bootloader-xxx.img
c. fastboot reboot-bootloader
d. fastboot flash radio radio-xxx.img
e. fastboot reboot-bootloader
f. fastboot update image-xxx.zip
This would update your Galaxy Nexus from Stock 4.2.2 to Stock 4.3 without losing any data/apps
Note:
1. If you using Windows follow the video tutorial to setup adb and fastboot http://goo.gl/jGcic
2. If you are on Mac, use ./ before the commands for execution
Note 2: With this method you don't need to remove the userdata.img as the command "fastboot update image-xxx.zip" does not touch the userdata on your device.
*Disclaimer: I have followed the above to the T and moved from Stock 4.2.2 to Stock 4.3 with Unlocked Bootloader, but you follow these at your own risk.
Click to expand...
Click to collapse
ive already flash to 4.3 but how to root??

Root for 4.3 is currently Work In Progress... Chainfire is working hard to resolve the challenges...
Soon it'll be rooted

is this only work for takju ?

@artlogics Follow the same for Yakju too..just download the appropriate Factory Image from Android Developers...

Root is finally available for 4.3 by Chainfire...
Download from http://forum.xda-developers.com/showthread.php?t=1538053
Happy Rooting!!!

I think my nexus 4.3 already fully rooted rite?
Sent from my Galaxy Nexus using xda

Well, I´ve got problem, when I type " fastboot flash bootloader bootloader-xxx.img" with the corrent name of the file adb says "Unknown error" ... Does anyone know how to fix it?

alfel said:
Well, I´ve got problem, when I type " fastboot flash bootloader bootloader-xxx.img" with the corrent name of the file adb says "Unknown error" ... Does anyone know how to fix it?
Click to expand...
Click to collapse
Need to know the following things:
1. Which system are you on - Windows/Linux/Mac?
2. Current version of OS on GNex?
3. Exact error message

freezer2000 said:
Need to know the following things:
1. Which system are you on - Windows/Linux/Mac?
2. Current version of OS on GNex?
3. Exact error message
Click to expand...
Click to collapse
1. Windows 7 - 64 bit
2. Android 4.2.2 - Yakju
3. As I said it says Unknow error

alfel said:
1. Windows 7 - 64 bit
2. Android 4.2.2 - Yakju
3. As I said it says Unknow error
Click to expand...
Click to collapse
It could be due to corrupt adb/fastboot files. Try downloading a minimal packaged adb/fastboot from http://forum.xda-developers.com/showthread.php?p=42407269 and see if that helps. I don't have a windows machine to test it... but i have used something similar on mac too

freezer2000 said:
It could be due to corrupt adb/fastboot files. Try downloading a minimal packaged adb/fastboot from http://forum.xda-developers.com/showthread.php?p=42407269 and see if that helps. I don't have a windows machine to test it... but i have used something similar on mac too
Click to expand...
Click to collapse
Still the same error..
EDIT: oh crap small size.. in the other way it still says Unknow error..

alfel said:
Still the same error..
EDIT: oh crap small size.. in the other way it still says Unknow error..
Click to expand...
Click to collapse
Few more questions:
1. Is your bootloader Locked (do you see a lock under Google when you turn your phone On)
2. Under Settings>Developer options> USB Debugging (do you see a check mark)
3. Have use used adb/fastboot before
4. Share a large screen shot for proper view.

freezer2000 said:
Few more questions:
1. Is your bootloader Locked (do you see a lock under Google when you turn your phone On)
2. Under Settings>Developer options> USB Debugging (do you see a check mark)
3. Have use used adb/fastboot before
4. Share a large screen shot for proper view.
Click to expand...
Click to collapse
1. Yep, my bootloader is locked, to be honest I dont see a lock when my phone is On but in bootloader I can see its locked
2. Yes, USB Debug is on
3. Well thats my first time to work with ADB but before I used command prop. so about commands I know..
4. working on it. Ok.. here is it
http://img209.imageshack.us/img209/2367/by8.png

Help I bricked my Oneplus 3

Hi, i played around with my new OP3, and i wanted to root it. Since i'm noob at rooting, it went wrong. (i did it with twrp)
So first it just went in to bootloop, then i was still able to get to rcovery and stuff, but i followed a guide to fix bootloop, and that ****ed it even more up. The guide i followedet told me to use "OnePlus3_Unbrick_Tool"
After using "OnePlus3_Unbrick_Tool", i now cant even go into recovery anymore, the only thing i can do is go to bootloader, but when i'm in bootloader now, it wont connect proberly, so that i can use "flash twrp", so that i can use twrp recovery.
Also when i try to boot it, it because of "OnePlus3_Unbrick_Tool" goes into something, where it says "md5 checksum failed", and then restarts and does it again and again.....
I hope it's not bricked forever, pls help ))

have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.

bonham1988 said:
have you tried re-flashing the stock or twrp recovery adb sideload command?
Click to expand...
Click to collapse
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)

Godeske said:
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Click to expand...
Click to collapse
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs

bonham1988 said:
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?

Godeske said:
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Click to expand...
Click to collapse
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.

simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"

Godeske said:
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Click to expand...
Click to collapse
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?

ghostofcain said:
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
Click to expand...
Click to collapse
Pretty sure i have, but i have booked a session with oneplus costumer service now, so that they do it for me live lololol

bonham1988 said:
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
Click to expand...
Click to collapse
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?

gavintoronto2016 said:
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
Click to expand...
Click to collapse
Adb version is outdated. Just download the latest ones.
Sent from my OnePlus3 using XDA Labs

Hey guys, if there are some of you, who knows a lot about this, would you like to answer this comment? Idk maybe we could use teamviewer to help me or something

simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))

Godeske said:
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Click to expand...
Click to collapse
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.

simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Thank you, but i have not enabled "allow oem unlocking" in the developer settings when the phone worked, so i get a error message "FAILED (remote: oem unloc is not allowed)
What to do to unlock it then?

Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..

jaganmohans said:
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
Click to expand...
Click to collapse
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...

simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Hey i have the same problem but this fix does not work for me.
So I have the bootloader unlocked and I can enter the bootload and my computer detects my device which is nice.
when I flash twrp on my phone trough CMD it doesnt work, my PC tells me that everything is okay but my phone will not boot into twrp and instead it will give me weird errors.
---------- Post added at 03:31 PM ---------- Previous post was at 02:56 PM ----------
this fix worked for me,
On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
- download this : https://www.androidfilehost.com/?fid=24591000424942573
and then extract.
- download platform tools attached below. extract in the same folder with first file you've downloaded.
- Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
- on the folder, hold shift and right click, click open command here
- type fastboot devices
- make sure your serial number appear.
- now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
- e.g. "fastboot flash boot_aging boot_aging.img.
- make sure you flash all the missing partition.
- type fastboot reboot.
this will boot you to oos 3.1.2.
unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA
goodluck mate. sorry for my english

Godeske said:
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
Click to expand...
Click to collapse
Hmm bad try installing all op3 drivers and see whether phone is detected or not. I was in the same situation previously. Pushing zip through adp terminal is painful process. I got device offline first,after solving that i got service not recognized issue. For solving that usb debugging needs to be enabled i stuck in that step.

can you enter recovery trough fastboot mode? I.e. if you are in fastboot mode you van use the volume keys to select recovery.
100% sure you can't enter recovery?
you can try Fast and pro's option. let us know!