Simple guide: Unlock bootloader/root N4 on Window 8.1 - Nexus 4 General

And yes, i dont know if there is any simple way to unlock bootloader and root for Nexus 4 on Window 8.1, but now i will show you guys
Step-by-step:
1/ Download Android SDK
2/ Install it to your computer
3/ Open Android SDK and download google usb-driver
Open device manager, find your N4, update driver, link it to your folder where you downloaded usb-driver and update
4/ Active debugging mode on your phone
5/ Download Kingo Android Root at: www.kingoapp.com
6/ Install it to your computer
7/ Open Kingo
8/ Connect your phone to computer
9/ Click Root
10/ Waiting about 3 mins
11/ And yes, done. Your phone is now unlocked bootloader/root
12/ Go find some custom rom for you and install it.
Simple huh??? Dont worry, i tried 10 mins ago and now my phone good to go.
PS: Important things: Your data will be wiped all, so make sure you back up all your data first.(Because i dont know that, my i lost all my data on my phone, ****tttttt.
This is a simple guide for NOOB to unlocked bootloader and root your nexus 4, just like me.

Shameless advertising for an app that simply automates two terminal commands.
There's nothing wrong with the tried and true method...
The SDK takes too long to install on windows just to unlock and root. This takes seconds, and installs everything 99% of users will need http://forum.xda-developers.com/showthread.php?t=2317790
after adb/fastboot are set up, it's only two steps:
open terminal and flash a custom recovery via fastboot
open recovery and flash the superuser zip
done!
Does that really need to be automated with some completely unknown app? Honestly, if you're too lazy to learn two simple terminal commands to root a Nexus (it really doesn't get any easier on any other phone) then you have no business using a rooted phone, either.

Related

[Q] About to root phone with 2.32.651.2

Hello,
I unfortunately just updated to 2.32.651.2 before deciding to root my phone. Is it still possible to root with this updated version, or should I downgrade. If I need to downgrade, can anyone tell me which software version I need to downgrade to in order to root, and a thread linking to a guide to downgrade?
forum.xda-developers.com/showthread.php?t=847993
this should do it
I think you can root this version, search around... if it possible you will find a post regarding it.
If you plan to downgrade, I would recommend .5 and then root using regaw's method - you should find all the details on the CDMA hero wiki page.
xlectik67 said:
I unfortunately just updated to 2.32.651.2 before deciding to root my phone. Is it still possible to root with this updated version [?]
Click to expand...
Click to collapse
HERE is the link to the post i wrote (in the thread which guided me) to get root in this stock-rom... so, yes, it can be done...
as far as dowgrading, im not sure i would recommend it - but as mentioned earlier, the wiki has a guide which i believe is based on a ...31...5 version you could use...
gl, h.
Root Sprint 2.32.651.2 OTA Permanently (in 10 steps)
Hi All
I have been able to root the Sprint 2.32.651.2 OTA permanently with the old boot-patched method. It is a little tricky and requires some knowledge of the Android SDK and Android Commander (There are several documents on how to install and use these 2 tools. Please search them out and learn.)
None of the other rooting methods seem to hold root after booting on this update. I have done this twice and it retains root permanently.
You must follow these steps to the letter.
First gather the tools needed for this root method
Android SDK (up and running)
Android Commander (androidcommander.com - makes moving and deleting so much easier)
SuperOneClick http://forum.xda-developers.com/showthread.php?t=803682 (this will give you temporary rootand install superuser, It is only temporary. After you do a boot the phone will loose root)
RomManager (download from Market after you have temp root)
Boot-Patched.zip (place this at the root of your SD Card. Flash through recovery. This is what will give you permanent root. File attached)
I take no credit for the tools that are needed. They are freely distributed. If I could remember who they belonged to I would give them props. Props to all the devs for making my Hero more enjoyable!!!
Process:
1: Install Android SDK. Make sure it is up and running and you have knowledge of the tools
2: Install Android Commander. Make sure it is up and running and you have knowledge of the tools
(Plug your phone into your computer with a USB cable)
3: Download and install SuperOneClick on your Windows based computer.
4: Run SuperOneClick.exe from the programs folder and click the ROOT button. (this will give you temorary root and install superuser onto your phone)
(At this point DO Not Reboot!! You will loose root and have to re-run step 4)
5: Download and install RomManger from the Market
6: Open the RomManager App and install the Clockwork Recovery (now you have a custom recovery on the phone. This will allow you to run Boot-Patched.Zip while temporarily rooted.
7: Through Android Commander copy Boot-Patched.zip to the root of your SD Card
8: Once Boot-Patched.zip is copied, boot into recovery either from Android Commander or RomManger
9: From recovery, flash boot-patched.zip like any other ROM. (this will permanently root this Sprint Update)
10: From recovery, boot the phone. re-run Android Commander and look at the bottom left corner of the program window. If it says "root OK" then it worked. If it says "root NO" then start over at step 4.
To test if you have permanent root, through Android Commander, remove a stock app that you do not want on your phone. If it works, you have permanent root. You will not be able to remove apps with temporary root.
I have an understanding of all of these tools. For you noobs out there, just keep learning. Trial and Error that is how its done. Keep asking questions (in the right forums please) someone will answer.
Enjoy
PS: Once rooted your WiFi will be non-functional. The only Kernel I have been able to get to work with this update and fix WiFi is the ZenKernel from 08122010. Serch it out, download and flash. (If you dont, you will be stuck with a phone with no WiFi and a top speed of 585mhz through SetCpu)
ccrosno said:
Hi All
I have been able to root the Sprint 2.32.651.2 OTA permanently with the old boot-patched method. It is a little tricky and requires some knowledge of the Android SDK and Android Commander (There are several documents on how to install and use these 2 tools. Please search them out and learn.)
None of the other rooting methods seem to hold root after booting on this update. I have done this twice and it retains root permanently.
You must follow these steps to the letter.
First gather the tools needed for this root method
Android SDK (up and running)
Android Commander (androidcommander.com - makes moving and deleting so much easier)
SuperOneClick http://forum.xda-developers.com/showthread.php?t=803682 (this will give you temporary rootand install superuser, It is only temporary. After you do a boot the phone will loose root)
RomManager (download from Market after you have temp root)
Boot-Patched.zip (place this at the root of your SD Card. Flash through recovery. This is what will give you permanent root. File attached)
I take no credit for the tools that are needed. They are freely distributed. If I could remember who they belonged to I would give them props. Props to all the devs for making my Hero more enjoyable!!!
Process:
1: Install Android SDK. Make sure it is up and running and you have knowledge of the tools
2: Install Android Commander. Make sure it is up and running and you have knowledge of the tools
(Plug your phone into your computer with a USB cable)
3: Download and install SuperOneClick on your Windows based computer.
4: Run SuperOneClick.exe from the programs folder and click the ROOT button. (this will give you temorary root and install superuser onto your phone)
(At this point DO Not Reboot!! You will loose root and have to re-run step 4)
5: Download and install RomManger from the Market
6: Open the RomManager App and install the Clockwork Recovery (now you have a custom recovery on the phone. This will allow you to run Boot-Patched.Zip while temporarily rooted.
7: Through Android Commander copy Boot-Patched.zip to the root of your SD Card
8: Once Boot-Patched.zip is copied, boot into recovery either from Android Commander or RomManger
9: From recovery, flash boot-patched.zip like any other ROM. (this will permanently root this Sprint Update)
10: From recovery, boot the phone. re-run Android Commander and look at the bottom left corner of the program window. If it says "root OK" then it worked. If it says "root NO" then start over at step 4.
To test if you have permanent root, through Android Commander, remove a stock app that you do not want on your phone. If it works, you have permanent root. You will not be able to remove apps with temporary root.
I have an understanding of all of these tools. For you noobs out there, just keep learning. Trial and Error that is how its done. Keep asking questions (in the right forums please) someone will answer.
Enjoy
PS: Once rooted your WiFi will be non-functional. The only Kernel I have been able to get to work with this update and fix WiFi is the ZenKernel from 08122010. Serch it out, download and flash. (If you dont, you will be stuck with a phone with no WiFi and a top speed of 585mhz through SetCpu)
Click to expand...
Click to collapse
Sorry I forgot to mention that there were a couple times that the phone locked up durring the reboot to recovery stage. I do not know why. I beleive that it was due to forgetting to install the recover before rebooting. If this happens, pull the battery, replace the battery and start over.
Thanks
tailsthecat3 said:
forum.xda-developers.com/showthread.php?t=847993
this should do it
Click to expand...
Click to collapse
my WiFi worked fine after rooting the ota update by following the linked method. ^
Go ahead and root using the method mentioned above, if anything goes wrong... you can always RUU and reroot.
BTW, I have downgraded using .5 RUU and rooted my phone, so based on my experience I can say, it works well. I had initially rooted my .7 and was running CM 6.0 stable, had some issues, got my recovery screwed up, so had to go all the way... ;-).
tailsthecat3 said:
my WiFi worked fine after rooting the ota update by following the linked method. ^
Click to expand...
Click to collapse
Ya I tried that one. Couldn't get it to take. Mine is sort of the non-syntax method.

[GUIDE] Complete and Thorough Guide to Rooting the Nexus S [+ No wipe] [GRH78C]

May NOT work for 2.3.3, if attempting on 2.3.3 use old part 1! - Will wipe all data though
Windows ONLY!
Hey guys, rooted my Nexus S today, and decided to write a thorough, detailed guide on how I did it, as none of the guides I had found had everything detailed. I came across a few problems, and all of this is in the guide. I successfully completed it on my Nexus S running 2.3.2, so any version below that will also work.
The original guide was made by AllGamer, and can be found here. I followed this guide, and added things when I found it was needed
The full guide with everything (including links, pictures) can be found on my site, Complete Android.
New info: Upon finding another thread over at XDA (http://forum.xda-developers.com/showthread.php?t=931865) it has been realized that you can root your Nexus S without unlocking the bootloader, and therefore not loosing your data on the SD card. Part 1 for the new method is still the same, but choose the new Part 2!
WARNING: Rooting your device will wipe all data off it, so you will loose EVERYTHING! Make sure you backup all important data first. Only applies to old Part 2 (fastboot oem unlock method), but it is still a good idea to backup important information!
Click to expand...
Click to collapse
What you will need:
Nexus S (obviously)
Android 2.3 SDK
USB Cable
PDAnet (for drivers)
Clockwork Recovery Image
Superuser
Part 1
Download the Android 2.3 SDK (or direct from Google here, 32MB).
Once it has finished downloading, unzip it, and run the SDK manager.
Select whatever components you wish to install, but you MUST make sure you install Google USB Driver (Available packages > Third party Add-ons > Google Inc. Add-ons > Google Usb Driver package, revision 4) otherwise this guide will not work!
We must now install the Google USB Driver, or the phone will not be recognised as a device other than a mass storage device.
Connect your Nexus S to your computer, and put it in USB storage mode.
Put it in USB Debugging Mode (Settings > Applications > Development > USB Debugging)
Windows should now recognise your Nexus S when you plug it in, and ask to install drivers. It probably won’t find anything, so we need to help it manually.
(Installing drivers manually varies between Windows versions, so please refer to http://developer.android.com/sdk/win-usb.html if you are having trouble). Launch Device Manager (you can find it in Control Panel), find Other Devices, and listed under that heading, you should find Nexus S. Right click, and select Update Driver Software. Click Browse my computer for driver software, find your SDK folder, then the google-usb_driver folder inside it, click OK, then Next. This should install the USB driver successfully. Reboot your computer.
Power off your Nexus S, connect it to your computer via USB cable, and boot it into the Bootloader Interface (you can do so by holding down the Power and Volume Up buttons at the same time).
It should say LOCK STATE – LOCKED, in white just above the green Android. You are now ready to move on!
Part 2 - Fastboot oem unlock method - WIPES ALL DATA!
We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don’t worry about this!). Follow along with any other instructions. You should be set now.
With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use ‘fastboot oem unlock’ (the rooting command) now.
Open a command prompt window (Start > Run > cmd.exe).
Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) ‘cd c:\*YOUR SDK*\tools’.
Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn’t).
Now in the command prompt, type in (without the quotes) ‘fastboot oem unlock’.
Now turn your attention to the phone, and read through the new information displayed on the screen. Using the Volume keys select Yes, then press the Power button. This will WIPE EVERYTHING! I bear no responsibility for any lost data on your phone!
If everything is successful, on your phone, the LOCK STATE should now read UNLOCKED, and on your computer, the command prompt window should say something like this:
Download the Clockwork Recovery image (here if you don’t already have it) to your Android SDK tools folder (*Android SDK*\tools).
Rename the newly downloaded Clockwork Recovery image to ‘recovery.img’ (no quotes).
Now we need to flash it to our Nexus S, so enter this command into the Command Prompt (make sure it is in the Androis SDK tools folder!) ‘fastboot flash recovery recovery.img’ (without the quotes).
If all is successful, the Command Prompt window should look something like this now:
Download the superuser app to the Android SDK tools folder.
Power on your Nexus S, leaving it connected to USB.
Mount the USB storage, and drag and drop the superuser .zip file you just downloaded into the root of the internal SD card (so Computer > *Device Name*, not in any other folders!). It should look something like this:
Power off the Nexus S, and return to the Bootloader Interface (step 9, part 1).
Select Recovery using the Volume buttons, then the Power button.
The phone should reboot into Clockwork Recovery, but if not don’t panic, just repeat steps 9-12, including downloading a new copy of the file (mine only worked the second time around, don’t worry!)
Using the Volume buttons and Power button, select install zip from sdcard.
Select choose zip from sdcard.
Select the su-version#-signed.zip file you downloaded earlier and apply it.
Select yes (there are lots of nos).
Confirm it says something like this: install from sdcard complete
Select Go Back.
Select Reboot. (You will now also have an unlocked padlock when you boot up)
Done! You now have to set up your phone again like when you first got it, but it will be rooted now.
New Part 2 - Does NOT wipe everything - Keeps a locked bootloader
Make sure Part 1 is completed.
Make sure you have downloaded the Clockwork Recovery file and the Superuser file.
Move the Clockwork Recovery file to your tools folder within the Android SDK folder, and rename it to recovery.img (for simplicity).
Connect your Nexus S via USB to your computer and mount it as USB storage. Copy across the Superuser file to the top level of your sdcard. (So the first window you see, not in any other folders. The sdcard is just where all the files are stored, don't worry about it too much for now).
We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don't worry about this!). Follow along with any other instructions. You should be set now.
With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use 'fastboot boot' (the boot image command) now.
Open a command prompt window (Start > Run > cmd.exe).
Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) 'cd c:\*YOUR SDK*\tools'.
Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn't).
We now need to use the 'fastboot boot' command to load Clockwork Recovery onto our Nexus S. In the command prompt, type in the following (but without the quotes, as always) 'fastboot boot recovery.img'
Once you are in Clockwork Recovery (it may take a couple of tries, don't panic, just redownload Clockwork Recovery, and complete steps 3 and 10, part 2) it should look something like this:
Using the Volume buttons and Power button, select install zip from sdcard.
Select choose zip from sdcard.
Select the su-version#-signed.zip file you downloaded earlier and apply it.
Select yes (there are lots of nos).
Confirm it says something like this: install from sdcard complete
Select Go Back.
Select Reboot.
Done! You should still have all your data present on your phone, and have root access!
Notes
As AllGamer said in his tutorial:
It’s normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you’ll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you’ll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Keep this in mind! It's not because you did something wrong
Also, some root apps require BusyBox to be installed, as I found out with Titanium Backup, so once you set up your Nexus S again, head on into the Market, and download BusyBox. It installed fine on my Nexus S this way, and now TB works fine.
I hope this is the best, most thorough guide you will find on rooting the Nexus S. Enjoy! Feedback is appreciated, and I will help out if you need any extra help.
Your guide has been wonderful however I'm stuck on part 2, step 4. I tried writing in the path to my directory and they keep giving me whatever I wrote in the command prompt "is not recognized as an internal or external command, operable program or batch file"
"Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) ‘cd c:\*YOUR SDK*\tools’."
This is how my command prompt looks like when I first open it. "C:\Users\Du>"
and this is what I typed in the command prompt: "Downloads\android-sdk_r09-windows\android-sdk-windows"
^^^I did exactly what you said above and nothing is happening. I don't know whether I'm writing in the directory wrong or what. Please help me out thanks
Your guide is nice, however as shown in distortedloop's stickied Root & Recovery thread, fastboot oem unlock is not required for rooting & flashing. We no longer have to lose all our sdcard data when first rooting and/or flashing a ROM.
Other than that, this seems to be a nice amendment of Allgamer's sticked root & recovery thread. I'm sure it will be useful to many.
STARSCR33M said:
This is how my command prompt looks like when I first open it. "C:\Users\Du>"
and this is what I typed in the command prompt: "Downloads\android-sdk_r09-windows\android-sdk-windows"
^^^I did exactly what you said above and nothing is happening. I don't know whether I'm writing in the directory wrong or what. Please help me out thanks
Click to expand...
Click to collapse
Ok so if you want to change directories in the command prompt, you need to use the command
Code:
cd
So in your case I would type in
Code:
cd c:\Users\Du\Downloads\android-sdk_r09-windows\android-sdk-windows\tools
That way is fool proof, however you could take a shortcut, because you are already in the Users/Du folder (because of how it looks when you first open it), you could just type in
Code:
cd Downloads\android-sdk_r09-windows\android-sdk-windows\tools
Hope that helps
ravidavi said:
Your guide is nice, however as shown in distortedloop's stickied Root & Recovery thread, fastboot oem unlock is not required for rooting & flashing. We no longer have to lose all our sdcard data when first rooting and/or flashing a ROM.
Click to expand...
Click to collapse
I think this way is a cleaner approach personally, but hey choice is good That's what Android is all about
EDIT: New approach added, now there is choice and easyness for all
Other than that, this seems to be a nice amendment of Allgamer's sticked root & recovery thread. I'm sure it will be useful to many.
Click to expand...
Click to collapse
Thanks
Jonathon Grigg said:
I think this way is a cleaner approach personally, but hey choice is good That's what Android is all about
Thanks
Click to expand...
Click to collapse
I'm not sure that wiping all your data pointlessly is "cleaner."
It's not even clear what exactly the oem unlock of the bootloader really does for us, since you can get into clockwork recovery without that step. Once you're in clockwork you pretty much own the phone. I'll be interested to see if someone can use clockwork to flash a new boot image once rooted without the unlock; if so I can't see any reason to unlock the bootloader. That said, mine is unlocked, and I like it that way, but many won't root for fear of losing data on the phone.
Even if you end up having to do the oem unlock in the long run for some activities you want to do, it seems that rooting, then installing Titanium and backing up your apps and app data fully is a better way to go than just losing all your data (any app that doesn't store its data on the sdcard) that can't be backed up without root would be a lot less painful than WIPING everything on the phone, including the sdcard.
It's not worth arguing about, but I think any method that is including the oem unlock step should at least mention that that step can be skipped. How many people will go through the pain of a wipe that they didn't need to because they didn't see that there was an option without it. I guess that's there own fault for not doing enough searching on their own...
Anyways, nice and thorough effort. I'm sure many will benefit from your additions to AllGamer's tutorial.
distortedloop said:
I'm not sure that wiping all your data pointlessly is "cleaner."
It's not even clear what exactly the oem unlock of the bootloader really does for us, since you can get into clockwork recovery without that step.
Click to expand...
Click to collapse
I have been wondering that myself. My guess is that for the average user you don't need to, but maybe it's for real power users who build their own ROM which has been fully modded or something, I'm not sure.
but many won't root for fear of losing data on the phone.
Click to expand...
Click to collapse
I definitely agree with that, and your guide is probably the best way for those people!
Even if you end up having to do the oem unlock in the long run for some activities you want to do, it seems that rooting, then installing Titanium and backing up your apps and app data fully is a better way to go than just losing all your data (any app that doesn't store its data on the sdcard) that can't be backed up without root would be a lot less painful than WIPING everything on the phone, including the sdcard.
Click to expand...
Click to collapse
Exactly, this is one of the better uses for both methods. I already had to wipe my phone twice due to Samsung CS so I'm used to it Although it does give you a chance to clear out the apps you don't need. Doing that I noticed better battery life on my phone.
It's not worth arguing about, but I think any method that is including the oem unlock step should at least mention that that step can be skipped. How many people will go through the pain of a wipe that they didn't need to because they didn't see that there was an option without it.
Click to expand...
Click to collapse
I wasn't going to argue I'm happy to adjust my tut to include something about this, after all it was aimed at more beginners.
EDIT: Added a new part to my tutorial based on your guide, just includes some more detail. Thanks again.
Thanks distortedloop
This is awesome cause i relocked my bootloader i really just needed root. Thanks!
Edit oops lost track of tabs open.
I think we can use this method to unlock oem without wiping data.
boot cw -> full backup -> unlock and flash cw (wipes data) -> restore backup (got ur data back and oem unlocked)
the only problem i can think of is that restoring backup would re-lock oem again but i am not sure of that.
i can't try this right now but if someone could, please give feedback.
Jonathon Grigg said:
I wasn't going to argue I'm happy to adjust my tut to include something about this, after all it was aimed at more beginners.
EDIT: Added a new part to my tutorial based on your guide, just includes some more detail. Thanks again.
Click to expand...
Click to collapse
Nicely done. Thanks.
sam4free said:
I think we can use this method to unlock oem without wiping data.
boot cw -> full backup -> unlock and flash cw (wipes data) -> restore backup (got ur data back and oem unlocked)
the only problem i can think of is that restoring backup would re-lock oem again but i am not sure of that.
i can't try this right now but if someone could, please give feedback.
Click to expand...
Click to collapse
That's what I suggesting a couple of posts above (root without unlock to at least make a backup of user data).
Restoring a titanium backup would not re-lock the phone. A nandroid restore might, depends on what all it imaged and restores, but it's so easy to re-root, that doesn't seem like a big deal.
Jonathon Grigg said:
Download the Android 2.3 SDK (or direct from Google here, 32MB).
Click to expand...
Click to collapse
Looks like you forgot to add the link in your copy pasta.
AtomicPC said:
Looks like you forgot to add the link in your copy pasta.
Click to expand...
Click to collapse
I've been working on it I just wanted to get it up here as soon as I could That's why I mentioned that the full guide is available on my website. I'm going back to school today, so I don't really have too much time for changing links now. Besides, most people on XDA should know how to look at the 'What's needed' part
Sent from my Nexus S using XDA App
Jonathon,
Thank you for posting this detailed guide to rooting without losing your data! I do have a question. As you've probably heard, there are a few updates coming soon and if they are like they were on the N1, they always broke root. So getting root back was tricky unless I "unrooted" before applying the update. Using your method, is it easy to "unroot"? Thanks!
No problems
As for your problem, I never actually had a N1 so I don't exactly know why that would happen. So far from the 2 updates available to NS owners it seems like the OTA update does break root but it appears to be the same to get it back again. Can someone confirm this? I haven't been through an update with my root yet.
As for unrooting, if you haven't unlocked the bootloader (so you have followed the new part 2) I think it is just a case of finding a stock image (I think there's a GRH78 one around here somewhere) and booting into Clockwork Recovery and flashing it. That should remove root and then also give you a notice to install the GRH78C OTA update so you get the latest version.
I think that is what you meant? If you did unlock the bootloader (using the original part 2) then I think you just have to follow the same steps as I mentioned just then but afterwards go back into the bootloader interface and run 'fastboot oem lock' and it should be right.
Sent from my Nexus S using XDA App
Question on Part 2- step 1.
Code:
# We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don’t worry about this!). Follow along with any other instructions. You should be set now.
Why above step is required if one already installed USB Driver for Nexus S and "ADB devices" command can find the device ?
On Allgamer thread didnt ask to repeat installing USB driver ?
What purpose for the pdanet driver ?
I dont want to put redundant drivers into my system which may interfere each other during flashing process.
hmanxx said:
Why above step is required if one already installed USB Driver for Nexus S and "ADB devices" command can find the device ?
On Allgamer thread didnt ask to repeat installing USB driver ?
What purpose for the pdanet driver ?
I dont want to put redundant drivers into my system which may interfere each other during flashing process.
Click to expand...
Click to collapse
When I tried to use the fastboot command with my Nexus S connected, it would hang and not do anything, despite leaving it for about 5 minutes. I searched online, and found the PDAnet solution, so I don't know what the difference is exactly. All I found the Google SDK USB drivers to do is enable you to see your device in Device Manager, however you could try it without the PDAnet drivers, and let me know what happens!
Thanks
Thanks for the prompt reply.. I tried out the google driver..it doesnt work under fastboot. I eventually get the fastboot enabled driver..that could explain why the pdanet driver required.
After i installed the fastboot enabled driver, i could test the connectivity under fastboot with "fastboot devices"
thanks going to try out rooting..i just want simple root access..without wiping data is a ++ ..
I managed to run fastboot boot recovery.img...going into clockwork menu..apply the superuser.zip.(for froyo version)..till completion..no word of failure..
However after rebooting, su and SuperUser.apk are not installed.( I used adb to check the system/app and system/bin folder.
Edit- manage to root properly after system mounting .
Just a note..to properly complete the rooting, one need to apply mounting then mount system before applying the Superuser.zip install from sdcard.
Prior to step 11, you may want to add the following steps for folks having problem to get the superuser.zip to install properly.
Originally Posted by droidmage
So all you guys who are having trouble getting root inside the rom, When your in recovery before you flash the superuser.zip file select -- mounts and storage -- then --mount /system -- then flash the .zip file and reboot
Click to expand...
Click to collapse
Thanks for the extra bit of info, I will attempt to add that in when I get a bit more time on my hands. when I did it it seemed to work fine so thanks for discovering that!
Enjoy your rooted phone
Sent from my Nexus S using XDA App

Root guide with lots of pictures and instructions [AndroidNZ]

Hi everyone,
I see more people than usual having issues with Rooting their Nexus 7 because of problems with booting into CWM recovery post flash - thought I would do a nice plain and easy to follow guide including instructions for booting into CWM recovery from a command point (thanks to Wugfresh for his Toolkit which is used in the guide).
http://www.androidnz.net/2012/07/how-to-root-your-nexus-7.html
Porting the full guide here, first the text because that is a simple cut n paste job, images to follow soon:
Before we get down into the nitty-gritty of the guide itself you should familiarise yourself with our usual disclaimers at the beginning of this post. I say this not because we don't care if you have problems, it's just that our capacity to trouble shoot is limited, and you shouldn't have embarked on an adventure to Root your device unless you did your due diligence first and had some understanding of what you were up to. One final disclaimer weasel-word at the off: the CWM recovery ports for the N7 are still a little iffy at this stage and even when taking appropriate steps to make it permanent you may only be able to boot into it via a command prompt window. Expect updates once fixes are available.
Disclaimers out of the way, here are the things you will need:
A Nexus 7, fully charged
A windows PC (the guide may work on macs via Windows virtual environments, but that isn't confirmed by us and is outside the scope of this guide)
The appropriate Nexus 7 USB drivers, there are several ways to get these:
Preferred method - Go to this thread at XDA-Developers and download and install the Root Toolkit there, which has an automated drivers installation included (this is preferred because it is what the guide that follows is based on because the Toolkit is probably going to be the most straightforward for the majority to use, and even if it fails and they have to resort to using command prompts that is more easily done from the Toolkit). Many many thanks to WugFresh at XDA for producing such a noob-friendly Rooting application - please consider making a donation to him here.
Install the Android SDK from here. Please note if you are already an SDK user that the Google USB drivers in the SDK have updated with the release of the Nexus 7 and Jelly Bean and you should update your drivers from within the SDK itself
Install the universal drivers from this post at XDA-Developers, but please make note of how you will need to adjust fastboot commands if you are using these drivers
Go to this post at XDA-Developers and install the USB drivers from there if you have no luck whatsover with any of the other methods
OK, now that you've got the Root Toolkit let's proceed (if you plan to do this with the SDK and command prompts then you should be advanced enough to follow the guide here, I did the first time and if you've done this stuff before the process is trivial).
Open the Root Toolkit, at the prompt to select your device scroll down to the bottom and select the Nexus 7 and the version number that corresponds to the firmware installed on your Nexus 7 (you can find this out in Settings --> About tablet --> Android version)
You'll be greeted with a screen that looks like this:
Click on Initial Setup and use the automatic driver installation facility from here to install USB drivers, it will check that ADB and Fastboot commands are working before dropping you back to the install window.
Turn on USB Debugging in the Nexus 7 by navigating to Settings --> Developer options. Turn on Developer options using the toggle in the top right hand corner, and then turn on USB debugging
Connect your Nexus 7 to your computer with the micro USB cable that came in the box. At this point it is vital that your computer recognises the Nexus 7 as a connected device, you will know if it has because a Nexus 7 "AutoPlay" window should pop up and ask you what action you want to take. If it doesn't show up, pull down the notification tray and press on the notification that says "Connected as a media device". A new menu will open and select the "Camera (PTP)" option. You should now get the AutoPlay window.
Head back to the Toolkit, and select "Unlock" from here, be aware that this will wipe your device (you might want to take a backup if you've already installed a lot of stuff on the device, that's just a button click away also in the Toolkit)
This will boot the device up to a screen giving you the option to unlock the bootloader, with "Yes" selected hit the power button. You'll see some text in the top left corner telling you it is unlocking the device, and then you will see the red "Locked" text toward the bottom of the screen change to "Unlocked". Moments later the device will reboot, and because it will have been wiped you will need to either set it up again or just skip past set-up and get back to the homescreen.
Once you're back onto the home screen, connect as you did before and take the same steps to turn on USB debugging and get the AutoPlay prompt to appear. Then go back to the Toolkit and select the Root option with permanent CWM recovery. All things going well the process will be fully automated from here, it will check that ADB and Fastboot are working, push the SU and CWM files to the device, boot the Nexus 7 into it's bootloader, flash CWM recovery to the device, and then reboot with Root privileges and a fresh new recovery permanently installed.
...or so the theory goes. Using this method I get Root, but CWM recovery is only accessible via command prompt, and I see others having the same problem. So...
Accessing CWM recovery:
In the Root toolkit go to Advanced Utilities by launching it here:
On the next screen select Launch CMD Prompt:
Once the command prompt appears type: ADB reboot recovery - the phone will boot into CWM recovery for you, so you can do things like make Nandroid backups, install zip files and so forth
Installing the 4.1.1 update post-Root and installation of CWM recovery:
Install OTA Rootkeeper by Supercurio from the Play Store here
Open the app once installed and grant it SuperUser privileges
In the app select "Protect Root", and then "temp unroot" the device
Download a zip of the 4.1.1 update here.
Copy it to the internal SD of the Nexus 7
Access CWM recovery as per the instructions above. In this version of CWM recovery you will navigate the options with the volume keys and press the power button to select an option - do that to navigate to "Install zip from SD card" and press the home button
On the next screen go to down "Toggle signature verification" and toggle it until it says "disabled" at the bottom of the screen (it should be set to default to disabled, but you lose like 5s making sure)
Go up to install zip, navigate to the zip file you downloaded in step one and install it
When the device reboots go to OTA Rootkeeper and restore Root, viola! You're done!
So, after all is said and done you should have a Rooted Nexus 7, running the 4.1.1 update, and with a custom recovery that can only be accessed via command prompt. Don't forget to shout WugFresh, the Toolkits developer, a coffee - make a donation here.
Would be nice if you posted that guide on this forum too.
Thanks for the guide.
Oooohh pictures
Caliyork said:
Oooohh pictures
Click to expand...
Click to collapse
You know, for the totally acopic
Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?
Dillon610 said:
Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?
Click to expand...
Click to collapse
No idea. You can simply downgrade to an older stock image using his Toolkit though and then follow the same process used in the guide to update to the latest build.
"Meh" at requirement #2:
A windows PC
Click to expand...
Click to collapse
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.
JaSauders said:
"Meh" at requirement #2:
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.
Click to expand...
Click to collapse
"Windblows"
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
There's a wiki on cyanogenmod.com that explains root.
mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
Should be doable on mac in a windows virtual environment, which seems to be how most mac users are doing things here at XDA.
Actually looking for someone to write "for mac" guides, if anyone is up for that!

[Guide] How to Unlock and Magisk Root on Stock OOS 9.0.7 (For Beginners)

NOTE: Since I am a semi-amateur at unlocking/rooting, this is not independent development. Instead, I noticed these forums don't seem to have a single one-stop guide that lays out the process for safely rooting the latest (9.0.7) Oxygen OS 9.0.7. This process may seem obvious to experts, but for people who are rusty or new to this, I wanted a process that didn't require lots of extra cross-referencing and research. I hope this is ok.
Big thanks to Dameon87 who supplied the patched boot rom, and deserves all the credit for the actual hard work with the patched boot image.
STEP 1: PREPARATION
Check that your phone is on 9.0.7.
On PC: Download patched_boot-9.0.7.img and MagiskManager-v6.0.1.apk from Dameon87's thread ( https://forum.xda-developers.com/oneplus-6t/how-to/9-0-7-patched-magisk-boot-img-t3875498 ) . Download ADB Tools if you don't have them ( https://developer.android.com/studio/releases/platform-tools#download ) and extract to a folder. Copy patched_boot-9.0.7.img to your PC’s ADB root directory (the directory with fastboot.exe and adb.exe).
On phone: Boot into OOS. Navigate to Setup->About Phone. Tap Build Number until you turn on Developer Options.
On phone: Navigate to System->Developer Options. Enable OEM Unlocking and USB Debugging.
STEP 2: UNLOCKING
Connect your phone to your PC. Click ok on the OEM Debugging prompt on your phone.
On PC: Open a command prompt [Windows: Start->type "cmd.exe"], and navigate to the ADB tools directory. Run this command in the command prompt:
Code:
adb reboot bootloader
The phone should reboot to the bootloader.
On PC: When phone finishes rebooting to the bootloader, run this command in the command prompt:
Code:
fastboot oem unlock
IMPORTANT: ALL DATA WILL BE ERASED WHEN YOU DO THIS, INCLUDING ANY PERSONAL DATA, TEXTS, PHOTOS, MUSIC, ETC. If the phone has been used, please move your files off your device first! The phone will take some time to factory reset.
On Phone: Repeat Preparation Steps 3-4 to turn back on OEM Debugging in OOS.
STEP 3: INSTALLING MAGISK
On PC: Copy MagiskManager-v6.0.1.apk to the phone.
On PC: In the command prompt window, run this command (note this .img file should be in the adb.exe and fastboot.exe directory):
Code:
fastboot boot patched_boot-9.0.7.img
Phone will reboot.
On Phone: Use a file manager app to install MagiskManager-v6.0.1.apk (I use Astro or ES, but admittedly there are probably better ones out there).
On Phone: Open the Magisk Manager App, agree to the setup popup, and click install. When prompted, choose Direct Install.
On Phone: Reboot.
On Phone: In the OS, open Magisk Manager again and add MagiskHide exceptions.
This enabled all apps that I typically need SafetyNet for, including Pokemon Go, Netflix and Google Pay, as well as of course all root apps like TItanium Backup.
Again, apologies if this seems basic, but I hope this is useful for some who don't know all of the inner workings of android unlocking and rooting by heart. If you have any improvements, feel free to suggest them.
You need to change adb oem unlock to fastboot oem unlock. Otherwise good job!
Dameon87 said:
You need to change adb oem unlock to fastboot oem unlock. Otherwise good job!
Click to expand...
Click to collapse
Ah, thanks! Fixed.
Does OTA update lock bootloader?
BesoC said:
Does OTA update lock bootloader?
Click to expand...
Click to collapse
No it doesn't, the root will be lost though.
geminium said:
No it doesn't, the root will be lost though.
Click to expand...
Click to collapse
I'm also a semi amateur at unlocking/rooting so I'm the target audience of the OP.
Ready to get my hands dirty and try it out. Last time I rooted it was on my old phone before Magisk was a thing.
I ended up not updating out of laziness.
Does magisk make OTA updates / keeping the phone up to date easier?
What's the best method for doing so if you want to keep your phone rooted?
spudsrus said:
I'm also a semi amateur at unlocking/rooting so I'm the target audience of the OP.
Ready to get my hands dirty and try it out. Last time I rooted it was on my old phone before Magisk was a thing.
I ended up not updating out of laziness.
Does magisk make OTA updates / keeping the phone up to date easier?
What's the best method for doing so if you want to keep your phone rooted?
Click to expand...
Click to collapse
Well there's quite detailed procedure explained on the forum. You'll find easily...
In general, you have to restore images in magisk, then install OOS OTA update, then install magisk to inactive slot... It's one of the easiest steps for keeping root and be up to date .
I've been rooting for almost a decade and I am grateful for this. I don't know why some of these devs always assume you know when their talking about using a PC or running shell commands. Lol. Everyone started as a noob.
Sent from my OnePlus6TSingle using XDA Labs
ScaryBugThing said:
NOTE: Since I am a semi-amateur at unlocking/rooting, this is not independent development. Instead, I noticed these forums don't seem to have a single one-stop guide that lays out the process for safely rooting the latest (9.0.7) Oxygen OS 9.0.7. This process may seem obvious to experts, but for people who are rusty or new to this, I wanted a process that didn't require lots of extra cross-referencing and research. I hope this is ok.
Big thanks to Dameon87 who supplied the patched boot rom, and deserves all the credit for the actual hard work with the patched boot image.
STEP 1: PREPARATION
Check that your phone is on 9.0.7.
On PC: Download patched_boot-9.0.7.img and MagiskManager-v6.0.1.apk from Dameon87's thread ( https://forum.xda-developers.com/oneplus-6t/how-to/9-0-7-patched-magisk-boot-img-t3875498 ) . Download ADB Tools if you don't have them ( https://developer.android.com/studio/releases/platform-tools#download ) and extract to a folder. Copy patched_boot-9.0.7.img to your PC’s ADB root directory (the directory with fastboot.exe and adb.exe).
On phone: Boot into OOS. Navigate to Setup->About Phone. Tap Build Number until you turn on Developer Options.
On phone: Navigate to System->Developer Options. Enable OEM Unlocking and USB Debugging.
STEP 2: UNLOCKING
Connect your phone to your PC. Click ok on the OEM Debugging prompt on your phone.
On PC: Open a command prompt [Windows: Start->type "cmd.exe"], and navigate to the ADB tools directory. Run this command in the command prompt:
Code:
adb reboot bootloader
The phone should reboot to the bootloader.
On PC: When phone finishes rebooting to the bootloader, run this command in the command prompt:
Code:
fastboot oem unlock
IMPORTANT: ALL DATA WILL BE ERASED WHEN YOU DO THIS, INCLUDING ANY PERSONAL DATA, TEXTS, PHOTOS, MUSIC, ETC. If the phone has been used, please move your files off your device first! The phone will take some time to factory reset.
On Phone: Repeat Preparation Steps 3-4 to turn back on OEM Debugging in OOS.
STEP 3: INSTALLING MAGISK
On PC: Copy MagiskManager-v6.0.1.apk to the phone.
On PC: In the command prompt window, run this command (note this .img file should be in the adb.exe and fastboot.exe directory):
Code:
fastboot boot patched_boot-9.0.7.img
Phone will reboot.
On Phone: Use a file manager app to install MagiskManager-v6.0.1.apk (I use Astro or ES, but admittedly there are probably better ones out there).
On Phone: Open the Magisk Manager App, agree to the setup popup, and click install. When prompted, choose Direct Install.
On Phone: Reboot.
On Phone: In the OS, open Magisk Manager again and add MagiskHide exceptions.
This enabled all apps that I typically need SafetyNet for, including Pokemon Go, Netflix and Google Pay, as well as of course all root apps like TItanium Backup.
Again, apologies if this seems basic, but I hope this is useful for some who don't know all of the inner workings of android unlocking and rooting by heart. If you have any improvements, feel free to suggest them.
Click to expand...
Click to collapse
Can you elaborate a bit more on how you got Pokemon Go working.
OS. 9.0.2 Magisk v18. Successfully rooted.
I'm selecting Pokemon Go under Magisk hide. But it still detects it. PoKe will sometimes run for about 30 secs then it gives me the error incompatible os.
Sent from my [device_name] using XDA-Developers Legacy app
Ok I'm new to this as well..I'm trying to understand the patched boot img part...so do u need the patched boot img for whichever oos ur currently running so to install magisk cleanly is that it...also I can't find the tutorial on how to install the ota's after ur rooted to where everything doesn't get erased etc..I need sumone to point me in the right area to look..I found a lil bit on it once but now I can't seem to find it..thx to everyone in this great community for all the time and effort all put into this. It's so easy to overlook all the hard work that gets done behind the scenes..so I just thank u personally for what u do for us...

HTC Incredible S alive again! S-Off not possible at the moment, though.

Hi all,
First of all I would like to say how awesome this site has been. I knew nothing about my first venture into rooting a phone so this has been a learning experience.
Right - now for those who have a HTC Incredible S and are looking to breathe some new life into this device (like I have purely for giving to my son to watch YouTube - so no calling, texting, etc) this is what I did (all information sourced from various threads on XDA and some external links as well):
1. Read through the following guide: {[GUIDE]} HTC Incredible S Unlock Bootloader, flash recovery, Root, S-OFF. Note: It appears that it is no longer possible to get S-OFF due to the Revolutionary site no longer existing. So you will have to stop at the end of Step 5.
2. Assuming you are using Windows 10 I had to do the following in order to successfully connect to the HTC Incredible S using fastboot/adb:
1. Install HTC Sync.
2. Once you have done this go to Control Panel -> Programs and Features then uninstall the HTC Sync program (the one with the sync icon) but leave the drivers etc installed.
3. Then download and install the Android SDK and update it as per the instructions https://www.andreszsogon.com/using-android-8-and-9-emulators-without-android-studio/
4. You then want to create a folder called C:\Android.
5. Now browse to the C:\Users\<username>\AppData\Local\Android\android-sdk\platform-tools folder and copy the adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll files to C:\Android.
6. Now make the changes to the registry. Put this in a *.reg file (with your texteditor and rename the file to e.g. import.reg
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\0BB40FF00100]
"SkipBOSDescriptorQuery"=hex:01,00,00,00
Then import that import.reg via regeditor (as admin) into your registry. Then reboot your computer.
7. Restart your PC.
8. If you are unlocking the bootloader for your HTC device - put the "fastboot.exe" file from the HTC Dev webpage (https://www.htcdev.com/bootloader/) here as well. Also put any recovery mods, roms, etc here as well.
9. Make sure - if you can that - that you boot your phone normally and go into the settings and turn USB Debugging "ON" and Fastboot "Off" (the second one is you can get to the bootloader on your phone using the appropriate key combinations). You may also want to turn on the option to install apps from unknown sources. Power off your phone.
10. Now turn on your phone into Fastboot mode then connect it to the PC it should change to Fastboot USB.
11. Open a command prompt as administrator and browse to C:\Android. You should now be able to use the Fastboot command.
Click to expand...
Click to collapse
3. You should now be able to complete steps 2 - 5 from the guide.
4. For my HTC Incredible S I went with the following:
Clockwork Mod Recovery 5.0.2.0 (download it here: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-vivo.img)
Root obtained using SuperUser 3.1.3 (filename is Superuser-3.1.3-arm-signed.zip from here https://forum.xda-developers.com/showthread.php?p=39959468#post39959468)
Installed Unofficial CyanogenMod 10.1 for vivo (download it here: https://forum.xda-developers.com/showthread.php?t=2127020) [EDIT: You may or may not need to also install this patch for it as well https://forum.xda-developers.com/showpost.php?p=38765296&postcount=493]
Installed Google Apps (Gapps) (download it here: https://www.teamandroid.com/gapps/ Just scroll down until you get to Gapps CyanogenMod 10.1)
Thanks all!
Hey bud, try https://web.archive.org/web/20150601030338/http://revolutionary.io/
Nonverbose said:
Hey bud, try https://web.archive.org/web/20150601030338/http://revolutionary.io/
Click to expand...
Click to collapse
Hi. Yeah, tried that.
While you can download the required zip file it doesn't let you generate the beta key required.
How about the solution posted here?
https://forum.xda-developers.com/showpost.php?p=63060287&postcount=11

Categories

Resources