Database Develop

[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

rooting galaxy tab 10.1v (working)

hi, this is how i managed to get root working on my tab, everything went fine for me till it came to booting into recovery then nothing use to happen so i combined two separate guides to get it working. thanks (bcmobile and 411tecknology)
the command in "(getting root 5) )" worked for me as i was getting stuck with "fastboot flash recovery skitzandroid-recovery.img"
i unlocked the bootloader by firmware upgrade the the following
for all those people like me with no experience in dos commands or linux, hope this works for you​
PREPARE:
1) With your Tab in fastboot mode (step 1 of “GETTING ROOT” below), make sure you have a working fastboot implementation:
working dir\\fastboot devices
If all is well, you should see your device serial number. If there is a problem, you won’t get any response.
2) Downlad the two files attached to this thread
3) create a folder in drive c naming it "root"
This will be referred to as the working directory throughout the rest of this guide
4) Copy skitzandroid-10-1v-root.zip to your working directory (DO NOT UNZIP!) c: root
5) Extract the skitzandroid-recovery.img file from skitzandroid-stock-recovery.zip to your working folder. Your working folder( c: root) should now have 1 IMG file and one ZIP file.
6) copy fastboot files to the the folder that you are going to use as working dir ( c:root)
7) Copy the skitzandroid-10-1v-root.zip file to the root of your sdcard. You can eithe drag/drop, or run:
working dir or c:\root>adb push skitzandroid-10-1v-root.zip /sdcard
GETTING ROOT:
1) Power off your Tab and power it back on, while holding the VOLUME DOWN button.
2) When the DOWNLOAD / FASTBOOT icons appear, press VOLUME DOWN again to select FASTBOOT icon (the one with the USB logo) and press VOLUME UP to confirm selection.
3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
4) Open a terminal / CMD prompt and CD to your working folder
keep doing cd.. until you get to "c:>" then
cd/root
5) Run the following command:
c:\root> fastboot boot skitzandroid-recovery.img
..and wait. It might not look like anything is happening but it is.
6) You should now have a recovery menu. Use the volume rocker (up/down navigates menu options)
to select “Install zip from SDCARD” (or something like that)
7) Navigate to the root of your internal storage (/sdcard), select the skitzandroid-10-1v-root.zip file and press (tap!) the POWER button to confirm selection.
Once complete, use the Volume rocker to select “REBOOT” from the menu and press (tap!!!) the POWER button to confirm selection.
9) YOUR’RE DONE. Press the thanks button on this thread to continue
TESTING:
Check your apps menu to confirm the existence of SuperUser app.

whats wrong with this?
http://forum.xda-developers.com/showthread.php?t=1079781

Nothing!
I used it on UNLOCKED 10.1v (not from Vodafone) and had no data loss!
Great, Thanks
Frank

I do not understand: 3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
Where do I enter this data?
I mean - fastboot deviсes

TNTCOSMOS said:
I do not understand: 3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
Where do I enter this data?
I mean - fastboot deviсes
Click to expand...
Click to collapse
once you start your device in fastboot mode and connect it with the computer to make sure your device is recognized by the computer you open command prompt take it to your working dir.. (ie. c:>root) in our case type fastboot devices and hit enter, if your computer recognized your device you will the serial number under it.

im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....

TNTCOSMOS said:
im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....
Click to expand...
Click to collapse
assuming you have installed sdk if not please do so, then staying in sdk go to
(C:\android\android-sdk-windows\platform-tools ) by clicking your mouse in desktop
(not cmd prompt). above eg.. is how i installed sdk on my desktop yours may be different, now in platform-tools you will see two files called fastboot copy them both to to your folder called ..root.. and you are set to go.
bottom line is if you want to start fastboot from any folder in cmd you have to have these two files in the folder.
also if you know that your device is detected by your computer dont worry about step 3. all it does is tell you that your device is connected.

I have all turned out, the problem was the drivers. I copied the driver from pdanet and it worked!

TNTCOSMOS said:
I have all turned out, the problem was the drivers. I copied the driver from pdanet and it worked!
Click to expand...
Click to collapse
Glad to hear that you finally got the root.

same problem
TNTCOSMOS said:
im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....
Click to expand...
Click to collapse
i've tried with pdanet too but it's not working....like the computer can't see the device...any ideea ???
and when i write "fastboot boot ......etc......" it says <waiting for the device>
please help

You need the drivers installed for fastboot, have you installed them? Please have a look at the [Guide] Unlock your bootloader thread. it contains all the details to get fastboot working.

thank you...finally did it
another noob question...how do i enter in cwm for installing another ROM ???

zbuggy said:
thank you...finally did it
another noob question...how do i enter in cwm for installing another ROM ???
Click to expand...
Click to collapse
The easiest way if you are rooted is to install rom manager from the market. It has an option to reboot to recovery if you have CWM installed. It also allows you to update to the latest CWM recovery if there is one.

i've tried putting the TB Galaxy 1.0.9: Honeycomb 3.1 + TouchWiz UX and i made a mistake... in cwm i've uploaded the zip file only with the update and not the rom itself.since then the tab won't start...it stop's in the beggining at the "samsung galaxy tab 10.1v"...any ideea...what can i do ?

Download latest rom and instructions from samfirmware.com using odin Get ur tab into fastboot mode with 3 button recovery and start from scratch.
It should work out
Sent from my GT-P7500 using Tapatalk

zbuggy said:
i've tried putting the TB Galaxy 1.0.9: Honeycomb 3.1 + TouchWiz UX and i made a mistake... in cwm i've uploaded the zip file only with the update and not the rom itself.since then the tab won't start...it stop's in the beggining at the "samsung galaxy tab 10.1v"...any ideea...what can i do ?
Click to expand...
Click to collapse
Do the following. If you have not yet odin.
Download the full rom.
Follow instructions in how to get into fasboot in sticky thread.
Once in fastboot you can load recovery via it, to do that download the recovery from droidbasement.com/blog, search on pershoot's website for recovery 4.0.4 if i remember correctly then type
fastboot boot recovery.img
where recovery.img is the name of the file you downloaded from droidbasement.com
Recovery will then load give it a minute or so.
Once loaded you can push the downloaded full rom via adb. That is part of the android sdk.
Like this: adb push romfile.zip /data/media/ (this will take a few minutes)
Then in cwm instal rom.
I hope it helps. Btw, remember you need to flash the wipe script of the rom before you install the rom if you are comming from stock.
Send from my GT-P7100

10x everybody it worked!!!!!!!!

Still me, posting in yet another thread. Still can't get the proper drivers. Pda method is not working. Which version of PDanet should I use ? The latest ? This is ****ing irritating...
I'm used to have to struggle to get things work at the beginning, but with my Magic and Hd2 it was a matter of hours...not weeks ! I'm sure it's something stupid but everybody deserted these guides topics...
I'm actually considering posting in the Dev section just to get attention...
Also, pershoot blog's advices are a joke : with no tags, a not working search field, no categories, try to find an info ! Knowing that the word "Recovery" will pop about 3 times per subject, I'm good to spend the week-end searching...

DannyBiker said:
Still me, posting in yet another thread. Still can't get the proper drivers. Pda method is not working. Which version of PDanet should I use ? The latest ? This is ****ing irritating...
I'm used to have to struggle to get things work at the beginning, but with my Magic and Hd2 it was a matter of hours...not weeks ! I'm sure it's something stupid but everybody deserted these guides topics...
I'm actually considering posting in the Dev section just to get attention...
Also, pershoot blog's advices are a joke : with no tags, a not working search field, no categories, try to find an info ! Knowing that the word "Recovery" will pop about 3 times per subject, I'm good to spend the week-end searching...
Click to expand...
Click to collapse
Hello,
I have been successful with rooting on win7. With win xp - after a few day struggling - fastboot did not give a go. Hope this helps

I just can't get the "Adb Original" signature from Pdanet. I always get standard Adb. I add the galaxy tab lines in the .inf file but still...
Do you guys edit the inf file with Wordpad or another tool ?

[Q] Newb here making progress. Got a question for my next step on rooting.

So I have done my homework and read tutorial guide and the nexus all in one beginners guide.
It took me a few hours to be able to get my pc to recognize my computer in fastboot mode using sdk and adp. (Hopefully my terminology is on track but doubtfully so).
So now in the command prompt, i can get the pc to recognize the phone in fastboot mode. Now all I really want to do is (this may sound silly) is to be able to use Air Mirror in airdroid... for now. I do like the stock android feel to this phone as I am new to nexus from the touchwiz **** from samsung.
So can i proceed to the commands of:
fastboot oem unlock
then
fastboot reboot
and then be done with it? Proceed to set up my google account and download my previous apps and contacts yada yada?
TIA

Hamm1701 said:
So I have done my homework and read tutorial guide and the nexus all in one beginners guide.
It took me a few hours to be able to get my pc to recognize my computer in fastboot mode using sdk and adp. (Hopefully my terminology is on track but doubtfully so).
So now in the command prompt, i can get the pc to recognize the phone in fastboot mode. Now all I really want to do is (this may sound silly) is to be able to use Air Mirror in airdroid... for now. I do like the stock android feel to this phone as I am new to nexus from the touchwiz **** from samsung.
So can i proceed to the commands of:
fastboot oem unlock
then
fastboot reboot
and then be done with it? Proceed to set up my google account and download my previous apps and contacts yada yada?
TIA
Click to expand...
Click to collapse
yup, make sure you have all data backed up to a pc, OEM Unlock will wipe your internal storage.
you also need to unlock developer settings, by tapping the build multiple times. Once unlocked you need to go into developer settings and click the check box to allow OEM Unlock
Afterwords if you want to run root, don't fastboot reboot you can use chainfires auto root and root-windows.bat and let it do its thing, then it will reboot and you can setup google account and move your files back over
If you want to flash TWRP, download that .img file and either use flashify to flash it from the google market or use fastboot flash recovery recovery.img

so it sounds like if i want root access, to do things such as air mirror from airdroid I need to flash cf's auto root?
Also in the all in one guide in imlicitly states to not skip the fastboot reboot step. Is this just a if you can do it, then do it step?
And yea, everything is backed up into google drive/cloud/plus and so on. So I am hoping once I am done I can setup my google account and everything should sync back as normal?
BTW thanks for the speedy reply.

Hamm1701 said:
so it sounds like if i want root access, to do things such as air mirror from airdroid I need to flash cf's auto root?
Also in the all in one guide in imlicitly states to not skip the fastboot reboot step. Is this just a if you can do it, then do it step?
And yea, everything is backed up into google drive/cloud/plus and so on. So I am hoping once I am done I can setup my google account and everything should sync back as normal?
BTW thanks for the speedy reply.
Click to expand...
Click to collapse
If you want to go the CF Auto root, you can just run root-windows.bat and it will actually perform the OEM Unlock step and complete that process for you, then it will root the phone and youll be back at the setup screen to enter your google account info, I think this will be the easiest route. It will take care of OEM Unlock, Adding Superuser and the binaries so you can run air mirror and any other root required app.
Yup if everything is backed up then once your login to the google account it will resync your apps and you can login to anything that needs credentials.

should I run fastboot reboot after it does its thing?

Hamm1701 said:
should I run fastboot reboot after it does its thing?
Click to expand...
Click to collapse
no, once you execute the root-windows.bat it will do all the fastboot commands, youll just have to hit a key on the CMD prompt after executing, it gives you a warning that OEM Unlock will wipe data, but you are already aware of that.
Basically, download cf-autoroot for shamu
unzip the zip into the same folder you have ADB installed (platform-tools)
get into adb and boot into bootloader mode or if your phone is in android already, adb reboot-bootloader
then root-windows.bat in the cmd window
and it will walk you through it from that point.

Circaflex said:
no, once you execute the root-windows.bat it will do all the fastboot commands, youll just have to hit a key on the CMD prompt after executing, it gives you a warning that OEM Unlock will wipe data, but you are already aware of that.
Click to expand...
Click to collapse
Cool, thanks for dealin with me. So now for the recovery. I downloaded the specified and latest vs of twrp recovery and I am told to rename it to and typed exactly the following after highlighting the file name: recovery.img
how can i verify that I have indeed named it recovery.img and not recovery.img.img

Hamm1701 said:
Cool, thanks for dealin with me. So now for the recovery. I downloaded the specified and latest vs of twrp recovery and I am told to rename it to and typed exactly the following after highlighting the file name: recovery.img
how can i verify that I have indeed named it recovery.img and not recovery.img.img
Click to expand...
Click to collapse
Do you have file extensions turned on for windows?
Depending on your version of windows it is different, but if they are turned on you would see the extensions for all files, if they are not turned on your files will not be showing extensions. If there is no extension rename the file to recovery and that's all if there are extensions youll see two .img's
Place that in your platform-tools folder as well, once autoroot is all installed and does its thing, set your phone up completely and get all the good stuff going
then power down and boot into boot loader or again use adb reboot-bootloader
then fastboot format cache (this wont harm any data or settings)
very important to then boot into recovery and let it load, then use recovery to reboot phone and youll be back in the android system
OR
download Flashify from the play store and select the .img you downloaded and it will flash the file, it works great

Hamm1701 said:
Cool, thanks for dealin with me. So now for the recovery. I downloaded the specified and latest vs of twrp recovery and I am told to rename it to and typed exactly the following after highlighting the file name: recovery.img
how can i verify that I have indeed named it recovery.img and not recovery.img.img
Click to expand...
Click to collapse
Just manually flash it....
fastboot flash recovery whatever-your-file-is-called.img
No need to rename it.
If you're going to remain rooted, it's a good idea to understand adb and fastboot correctly. Please take the time to read my thread.
http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500

@Hamm1701 how did it go

Circaflex said:
@Hamm1701 how did it go
Click to expand...
Click to collapse
Yikes, didnt realize my post didnt go through last night. Well it went very well. I'll admit that when the little android guy was staying on "erasing" for a few to 5 ish min i started to panic a little. I was expecting something like erasing then installing then some other imaginative windows installation words.
But I am now trying to figure out why a certain app is not working 100% as it was before the root and unlock procedure. Ill be researching on learning how to provide feedback developers can use to make any neccasry changes. Do you know of any such threads/posts I can read up on in this regard?

Hamm1701 said:
Yikes, didnt realize my post didnt go through last night. Well it went very well. I'll admit that when the little android guy was staying on "erasing" for a few to 5 ish min i started to panic a little. I was expecting something like erasing then installing then some other imaginative windows installation words.
But I am now trying to figure out why a certain app is not working 100% as it was before the root and unlock procedure. Ill be researching on learning how to provide feedback developers can use to make any neccasry changes. Do you know of any such threads/posts I can read up on in this regard?
Click to expand...
Click to collapse
which app is misbehaving? Basically if you have a problem the easiest solution is to pull a catlog that will detail what your phone was doing and show the error. You can do this through ADB or a free program from playstore is called Catlog.

Circaflex said:
which app is misbehaving? Basically if you have a problem the easiest solution is to pull a catlog that will detail what your phone was doing and show the error. You can do this through ADB or a free program from playstore is called Catlog.
Click to expand...
Click to collapse
It was the manual camera app. So I think i figure out how to view and store catlogs. Going to post my question about it over in dev Q&A.

[GUIDE] How to flash 1.5 update on LG Urbane (non-LTE version)

For some Urbane users, for whatever the reason may have been, they were unable to install the 1.5 OTA, the "dead" android continued to come up. This guide assumes that you have Minimal ADB and Fastboot installed on your computer, a guide that includes how to set your computer up for this is found HERE. This guide also assumes your watch is already on ADB debugging, etc, etc, else follow the previously mentioned guide.
READ ENTIRE GUIDE BEFORE YOU START. NEEDLESS TO SAY YOU'RE TRYING THIS AT YOUR OWN RISK..
Files needed:
- System
- Boot
- Recovery
(these are for 6.01 version, and can be found HERE with the 5.01 version).
- 1.5 update zip found HERE
1 - Connect your watch's charger to your PC and set your watch on the charger.
2- Open Minimal ADB and Fastboot, and type:
Code:
adb devices
and hit enter
3- If properly connected you should see something similar to "504KPJP00XXXX8 device".
4- Now type in:
Code:
adb reboot bootloader
and hit enter. The watch should reboot into the bootloader.
5- While in bootloader type:
Code:
fastboot flash system
and drag the System file you downloaded earlier to the Minimal ADB and Fastboot window, and hit enter.
6- When it's done installing type in:
Code:
fastboot reboot
and hit enter.
7 - Repeat steps 1-6 for EACH of the other two files: Boot and Recovery files you downloaded. Keep in mind that EACH TIME when you get to step 5 you must type in:
Code:
fastboot flash boot
for the Boot file, and
Code:
fastboot flash recovery
for the Recovery file respectively and drag their respective files to the window. So, to recap, do steps 1-6 for Boot, and 1-6 for Recovery. Got it? Good.
8- Get into bootloader mode again (see steps 2-4). Using the left and right (< >) arrows in bootloader screen on your watch look for "Recovery Mode" and hit the (o) option.
9- Now you will see the good ol' "dead" android. Fear not, touch the screen and you should get some options. Sliding your finger up or down scroll to "Mount /system", and swipe left or right.
10- Now slide down to "Apply update from ADB" and slide left or right to get into ADB sideload mode.
11- Once in sideload mode go to Minimal ADB and Fastboot window and type in:
Code:
adb sideload
AND drag the 1.5 update zip file you downloaded onto the screen, THEN hit enter.
12- If done properly the Minimal ADB and Fastboot window will start showing you some progress and so will the watch. wait until it's done. When it's done reboot your watch. Be advised it will take a little bit to power on, be patient!
You're all done!
Now you can go back and install TWRP, root, etc..
I want to point out that 1 or many of the above steps may not be necessary but this is exactly what I did to successfully flash the update. No wiping, no factory reset was necessary.

Can you please share how to disable auto update after installing 1.5 on urbane? I successfully downgraded but in couple of hours my watch updated back to AW2.

caughtmountain said:
Can you please share how to disable auto update after installing 1.5 on urbane? I successfully downgraded but in couple of hours my watch updated back to AW2.
Click to expand...
Click to collapse
Here. By the way what's so bad about 2.0?

How do I update to M1D65H (the last aw 1.5 update) ?
Thanks for the detail tutorial. BTW the aw 1.5 version given in your link (MM) was MWD48B.
How to find and upgrade to the last aw 1.5 just before the aw 2.0 was released. i.e M1D65H
Update : Somehow I managed to upgrade to M1D63G (OTA package - using adb sideload), after which I could not able to find further updates.
Updating to M1D65H (OTA package using "adb sideload") directly fails.
---------- Post added at 03:04 AM ---------- Previous post was at 02:58 AM ----------
cubandanger05 said:
Here. By the way what's so bad about 2.0?
Click to expand...
Click to collapse
I keep getting the notifications even after running this APP in my watch.
After running this APP, the message says disabled update and please restart.
But after some time I get back the "Notification for the Update"
Does the watch requires to be rooted ?

razebond said:
Thanks for the detail tutorial. BTW the aw 1.5 version given in your link (MM) was MWD48B.
How to find and upgrade to the last aw 1.5 just before the aw 2.0 was released. i.e M1D65H
Update : Somehow I managed to upgrade to M1D63G (OTA package - using adb sideload), after which I could not able to find further updates.
Updating to M1D65H (OTA package using "adb sideload") directly fails.
---------- Post added at 03:04 AM ---------- Previous post was at 02:58 AM ----------
I keep getting the notifications even after running this APP in my watch.
After running this APP, the message says disabled update and please restart.
But after some time I get back the "Notification for the Update"
Does the watch requires to be rooted ?
Click to expand...
Click to collapse
I believe so, yes.

Have installed updatedisabler.apk on both phone and watch (watch is rooted) both come up with "Check your watch to find the application". Still get nags about updating?
Has anyone got this to work?

updatedisabler is not working, somebody knows how to uninstall it?

First, it's slow and buggy. Google Assistant takes several seconds to load before you can speak to it, sometimes so long the screen times out before you can speak your command. I always get a notification vibration, but rarely get the notification card, destroying the most useful smart feature of the watch, and instead of cards peaking, I always have a full screen card of whatever song or podcast I'm listening to, that is persistent and blocks my watch face, destroying the most useful feature of not smart watches (since I can't see the time). But, those apps run on the watch natively by default, so if I try to start playing music or podcasts it can only playback locally from the watch, not start the playback on the phone. Do disturb on the watch is also now separate from dnd on the phone, which means when going into meetings I have to silence both independently. In short, what's wrong with aw2? Everything! Oh, and my battery just says 50% all the time since the update. Totally garbage.

Hello. I'm getting an error that it's locked and so I can't flash the file to downgrade. Does the bootloader need to be unlocked ????? I'm currently on AW 2 and I would like to flash back down. Thanks.

Im confused, I know how to flash .img files but what do I do with this 1.5 update file? I currently downgraded to 1.3 but thats a little too old for my liking.

mexiken said:
Hello. I'm getting an error that it's locked and so I can't flash the file to downgrade. Does the bootloader need to be unlocked ????? I'm currently on AW 2 and I would like to flash back down. Thanks.
Click to expand...
Click to collapse
Yes, your bootloader needs to be unlocked

RunNgun42 said:
Im confused, I know how to flash .img files but what do I do with this 1.5 update file? I currently downgraded to 1.3 but thats a little too old for my liking.
Click to expand...
Click to collapse
If you're on stock 1.3 you should be able to flash the update following the adb sideload steps

Hi guys. I tried to follow the steps, but the "adb sideload" part is not working. The watch presents an error: "can't mount /system". Any tips? Is there any 1.5 full rom out there?

[fixed]

[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...