Database Users

[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9023 and i9020A)

Hi all,
i've recently bought a Nexus S which is a non-US/UK (GT-i9020) version having a SC-LCD screen (GT-i9023).
Which is not, sadly, the only difference...
MOD EDIT: This tutorial also applies to AT&T/Rogers/Telus variants of the Nexus S with SAMOLED screen (i9020A)
This tutorial is based on AllGamer's [GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020 only).
Part 1 - Drivers
1 - Download Android SDK
2 - Unzip & launch "SDK Manager.exe"
3 - Cancel the first popup & go to "Available packages" > "Third party Add-ons" > "Google Inc."
4 - Select "Google USB Driver package" & click "Install Selected"
5 - Once you're finished go to your SDK installation "extras\google\usb_driver" dir
6 - (MOD EDIT: Ignore this step for i9020A models) Open "android_winusb.inf" and add the following lines to both "[Google.NTx86]" and "[Google.NTamd64]" sections :
;
;Google Nexus S GT-i9023
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20​as described here [SOLVED] Google Android USB drivers - Nexus S SCLCD GT-i9023 not recognized
7 - Turn Off your SNS
8 - Make sure the SNS is connected to the PC via the USB cable
9 - Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
It reads LOCK STATE - LOCKED
Open Device Manager (or run devmgmt.msc) make sure you don't see this problem (windows failed to identify the SNS and install the correct drivers)
10 - Do a right click and select Update Driver Software
11 - Select Brose my computer for driver software
12 - Point it to your Android SDK installation "extras\google\usb_driver" dir
13 - Make sure to CLICK "Let me pick from a list of device drivers on my computer"
14 - Then from the list 3 choices select Android Bootloader Interface
15 - If it's installed properly it should show up like this (reboot is not required)
NOTE: if you encounter problems like question marks, unknown drivers, or exclamation marks eve after you have installed the drivers, download and try the USBDeview 32/64 to remove and uninstall all the junk USB devices from your computer/registry​
Part 2 - Unlock
1 - Open a command prompt go to run & type "CMD" & hit enter
2 - Switch to the directory where you unzipped the Android SDK & go to "tools"
3 - Type "fastboot oem unlock" & hit enter
Then you will get thisfastboot oem unlock
...​Selecting YES will wipe EVERYTHING from the SNS, so make sure you have backed up everything you needed to safe before you continue.
4 - Use the Volume up/down keys to select and Power key to apply
you should see something like this after it's done... OKAY [435.433s]
finished. total time: 435.433s​Now back on this screen you should read
LOCK STATE - UNLOCKED​
Part 3 - Recovery
1 - Download the ClockworkMod recovery image (for i9020A models, use this i9023 recovery image too!) 3024v3-i9023.img from [MOD][RECOVERY]Clockwork 3.0.2.4 New wipe & confirm menus!! i9023 & i9020 versions
2 - Save it to the Android SDK "tools" dir
3 - Open a command prompt go to run & type "CMD" & hit enter
4 - Switch to the directory where you unzipped the Android SDK & go to "tools"
5 - Then type "fastboot flash recovery 3024v3-i9023.img" & hit enter
You should get something like this, if not your image is corrupted, download it again
sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s​6 - Then back on the SNS select Power Off (Reboot also works)​
Part 4 - Root
1 - Power ON the SNS
2 - Download su-2.3.6.1-ef-signed.zip from [APP] Superuser 2.3.6.1 - Now on the Market [2010-09-05]
3 - Save it to the Android SDK "platform-tools" dir
4 - Open a command prompt go to run & type "CMD" & hit enter
5 - Switch to the directory where you unzipped the Android SDK & go to "platform-tools"
6 - Type "adb push su-2.3.6.1-ef-signed.zip /sdcard/su-2.3.6.1-ef-signed.zip" & hit enter
7 - Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
8 - Select "Recovery
9 - Then it should boot into this screen, if not then repeat the steps to download the image
10 - Select "Install ZIP from sdcard" (power button to apply)
11 - Select "Choose ZIP from sdcard" (power button to apply)
12 - Select su-2.3.6.1-ef-signed.zip (power button to apply)
13 - Select "Yes - su-2.3.6.1-ef-signed.zip"
Should says
Install from sdcard complete​15 - select go back
16 - select reboot​
You're now free to install the ROM you want.
Have fun, take care !
Credits goes to AllGamer & afilopou

I was heading through this toturial and many others present in the SNS forum. There seems to be some confusion regarding rooting && flash custom roms.
Being rooted does not imply that we can flash new roms. For that we need custom recovery. In several phones, we could only had a custom recovery if the phone was rooted. In SNS, we just need an unlocked bootloader and a compatible recovery. No root is needed IMHO.
Also, in this guide, as in several others, there isn't said anywhere that the custom recovery will be reverted by the system as soon it finishes booting the stock rom. I think it should be clear that we need to remove/rename the script that does that.
Still... Thanks.

Brilliant. Thanks!

this is a very nice, but i'll suggest including the modifications instructions in this topic as well, instead of just linking it to the other topic

DoomFragger said:
I was heading through this toturial and many others present in the SNS forum. There seems to be some confusion regarding rooting && flash custom roms.
Being rooted does not imply that we can flash new roms. For that we need custom recovery. In several phones, we could only had a custom recovery if the phone was rooted. In SNS, we just need an unlocked bootloader and a compatible recovery. No root is needed IMHO.
Click to expand...
Click to collapse
This tutorial is based on AllGamer's one concerning the GT-i9020.
Im very new to Android customisation, i've just followed some toturials i've found trying to make them works, so it may be inconsistent.
As far as i know, i got some problem using the RomManager application that was asking for superuser rights in order to install new rom. This application placed a superuser-xxx-signed.zip at the root of the sdcard, but install on my SNS SCLCD never worked.
Consider using the manual way, not the RomManager application, will be more straiforward.
May be all these steps are not mandatory, but in the end you'll be able to be able to nistall new rom.
Consider it as a global package for customisation.
DoomFragger said:
Also, in this guide, as in several others, there isn't said anywhere that the custom recovery will be reverted by the system as soon it finishes booting the stock rom. I think it should be clear that we need to remove/rename the script that does that.
Still... Thanks.
Click to expand...
Click to collapse
Never noticed that. ClockworkMod recovery has ever stayed in place, even after rebooting the stock rom many times.
Cheers !

AllGamer said:
this is a very nice, but i'll suggest including the modifications instructions in this topic as well, instead of just linking it to the other topic
Click to expand...
Click to collapse
By the way AllGamer, i apologize for the non-agreed use of your tutorial, i was all in the thing at that time, just thinking about to end up with my cyanogen rom.
It works now, thanks to you. MIUI this evening

hi
i also have the 9023 and tried your guide. but im am stuck at #14 because it dont find the android bootloader interface entry, there are just three adb interface driver in this list. i also cleared the driver registry with usbdeview before.
adb driver is installed and i tried to unlock the bootloader but fastboot dont recognice the phone.
and i tried it on 2 different pcs, one with win xp and one with win7, same problem on both systems
ugrubni

When I unlock my bootloader, I've downloaded the "Google USB Driver package" and the "Galaxy Tab by Samsung Electronics".
I haven't edited any .inf file. Those were the instructions I followed from this article.

ok, finally i have bootloader interface installed with edited .inf installed on win7.
i tried to unlock with fastboot but it just does nothing. my nexus says
usb control init
usb control init end
standard_set_configuration
anyone an idea?
ugrubni

Before I root my Nexus S, i got some questions to ask.
Can I "unroot" my nexus s to stock if I do this?
What kind of roms are there available other than CM7 mod?

Hi all,
Followed advice above, had to reinstall SDK as did not have an adpfile. SDK all fine now, but am stuck on fastboot not recognising the phone - stays on waiting for device, did a search on xda but brought up other phones and nothing that could helped me...
updated: adb devices works fine, it sees the phone with adb, but just not with fastboot?
another update:
tried usbdeview to uninstall drivers
re-installed them again, no such luck.. annoyingly adb sees the nexus but fastboot does not..
would appreciate any more ideas?

i finally got it work
fastboot also dont recognized my phone
what i did is:
go to android-sdk/platform-tools folder and copy adbwinapi.dll and adbwinusbapi.dll to /tools folder where fastboot also is located and it worked.
cheerz, ugrubni

kursk said:
This tutorial is based on AllGamer's one concerning the GT-i9020.
Im very new to Android customisation, i've just followed some toturials i've found trying to make them works, so it may be inconsistent.
As far as i know, i got some problem using the RomManager application that was asking for superuser rights in order to install new rom. This application placed a superuser-xxx-signed.zip at the root of the sdcard, but install on my SNS SCLCD never worked.
Consider using the manual way, not the RomManager application, will be more straiforward.
May be all these steps are not mandatory, but in the end you'll be able to be able to nistall new rom.
Consider it as a global package for customisation.
Never noticed that. ClockworkMod recovery has ever stayed in place, even after rebooting the stock rom many times.
Cheers !
Click to expand...
Click to collapse
That's right.The script which removes Cwm recovery after reboot does not exist in i9023(slcd)
Sent from my Desire HD using Tapatalk

hi Guys
sorry about the noob question,
but actually I have a problem installing JDK,
Android SDK always give me back "JDK SE development Kit (JDK) not found."
But I did install several times...,
SDK still not recognise it.
what should I do?
thx
Cheers

Colombus said:
hi Guys
sorry about the noob question,
but actually I have a problem installing JDK,
Android SDK always give me back "JDK SE development Kit (JDK) not found."
But I did install several times...,
SDK still not recognise it.
what should I do?
thx
Cheers
Click to expand...
Click to collapse
Did you try to install eclipse and start sdk from eclipse?
http://www.eclipse.org/downloads/ (download this one Eclipse IDE for Java Developers)
and then read this one
http://developer.android.com/sdk/eclipse-adt.html#installing
Had as well problems, but now i am using eclipse in order to start sdk

thx now it's working, all good, with it, and able to setting up
cheers

thanks ugrubni,
worked like a charm...
now have zeroxs on my nexus sorted!

Hey guys,
Im stuck at part 2 "Unlock", when i run cmd and type fastboot oem unlock i get an error saying fastboot is not recognized as an in or external command, program or batchfile.
I then uninstalled all usb junk with USBDeview 32/64, i didnt quite know what to uninstall, so i just uninstalled everything, maybe a bit to rigorous?
Im in no way a tech wonder and this is the very first phone i tried to root, so if you would be as detailed as possible i would really apreciate that!
hope you guys can help me out?

Fmbl said:
Hey guys,
Im stuck at part 2 "Unlock", when i run cmd and type fastboot oem unlock i get an error saying fastboot is not recognized as an in or external command, program or batchfile.
I then uninstalled all usb junk with USBDeview 32/64, i didnt quite know what to uninstall, so i just uninstalled everything, maybe a bit to rigorous?
Im in no way a tech wonder and this is the very first phone i tried to root, so if you would be as detailed as possible i would really apreciate that!
hope you guys can help me out?
Click to expand...
Click to collapse
Ok lets try to solve it.
First things first, uninstall everything related to sdk and do the part 1 from scratch.Then go to androidsdk/tools folder and check if you have a file named "fastboot".If yes (normally yes because after updating android sdk manager the "fastboot" file must be there.Also make sure you downloaded the google usb driver) then go to androidsdk/platform-tools and find the two files AdbWinApi.dll and AdbWinUsbApi.dll .Copy-paste them to androidsdk/tools .Restart your pc and try the second part.
Hope to help

afilopou said:
Ok lets try to solve it.
First things first, uninstall everything related to sdk and do the part 1 from scratch.Then go to androidsdk/tools folder and check if you have a file named "fastboot".If yes (normally yes because after updating android sdk manager the "fastboot" file must be there.Also make sure you downloaded the google usb driver) then go to androidsdk/platform-tools and find the two files AdbWinApi.dll and AdbWinUsbApi.dll .Copy-paste them to androidsdk/tools .Restart your pc and try the second part.
Hope to help
Click to expand...
Click to collapse
Thnx for your reply,
I followd everything you said, but fastboot is still not recognized, the above error message still aplies!
I do however dont get step 2 of part 2, maybe noobish but how do i get to that directory in CMD?
hmmm what to try next?

[GUIDE] Workaround for attaining S-OFF (for Windows 8.1. users)

For those on Windows 8.1 who have just about given up trying to get S-OFF...
For reference I have an ATT HTC One, but showing in bootloader as m7ul (didn't seem to make a difference to any downloads/steps anyway so meh)....
hboot = 1.44
S-ON (hence the inability to install the new GPE 4.4 ROMs)...
So I have tried every single fix imaginable on these forums and the Internet in general... absolutely nothing has worked... trust me....
I then seen a comment from someone mentioning using Ubuntu to do it... I thought... no way, I'm not bothering, all that effort, and it'll still fail... well tell you what, via various forums, sites, fixes etc (lol) I got there in the end.
Prerequisites:
Rooted
hboot 1.44 (I haven't tested newer versions... assume you're looking here really because you had the same problems as me - test with other hboot versions at your own risk I guess)
Not sure if the version of Rom you are currently on matters, I was on 4.3 Google edition (Eragon V14), so don't ask me which to be on
Let's do the following:
1) Download Windows Ubuntu from here:
http://www.ubuntu.com/download/desktop/windows-installer
Click "Get the Installer"
Download and save the .exe to wherever you want
2) Right click the .exe and create shortcut
3) Change the target of the shortcut (right click --> Properties) to end with the following: \wubi.exe --32bit
4) Run the installer, and just go with any defaults
5) Once rebooted in to Ubuntu we are going to download and install fastboot and adb
6) Click the Windows key, type "Terminal" and hit RETURN
7) type the following at the "command" prompt: (do not type [RETURN] <-- lol)
sudo add-apt-repository ppa:nilarimogard/webupd8 [RETURN]
sudo apt-get update [RETURN]
sudo apt-get install android-tools-adb android-tools-fastboot [RETURN]
When prompted, enter the password you set up when you installed Ubuntu in the first place.
8) To confirm Fastboot now works (yes... it was that easy)
Boot your phone in to Fastboot (hold VOL DWN + Power --> Fastboot)
Connect up the phone to USB
In the terminal, type the following then press RETURN
sudo fastboot devices
You should see your device serial, confirming it is recognised by Fastboot ----
9) Now to download Rumrunner -- get the archive from the following location:
http://rumrunner.us/rumrunner_downloads/rumrunner_HTC_0.5.0.tgz
Open the download (rather than save), and extract all files to the Home/Download folder (you can just click and drag them over)
10) Now, we need to allow the "soju" file to be executed
Right click the extracted file "soju" --> go to Properties --> Permissions tab --> Tick "allow executing file as program"
Almost there.....
11) Boot the phone back up and enable USB Debugging via Developer Options
Also change display timeout to 10mins, and set screen security to None
12) Disable Fastboot where applicable (Settings --> Power --> Fast boot)
13) Now to run the Rumrunner application....
Again, within the terminal, type the following:
cd Downloads [RETURN]
(if this doesn't work, you need to navigate to the folder you extracted the "soju" file to, so the cd (change directory) DOS command works fine here)
Now type the following (once you are in the same location as "soju")
sudo ./soju
If you are ready (definitely) to start the process, now press RETURN.
14) You will be asked twice to type "Yes" exactly as displayed followed by RETURN to confirm, please do not type Yes to the warnings that will come up periodically after the script starts (if you give them a moment, you will see them continue without any input from yourself)
15) Sit back... and wait for it to complete. The process took about 20mins in total to complete on my phone... and I've now got S-OFF. If you keep getting prompted for what to do with your phone being plugged in - just press cancel to the prompts.
p.s. if this worked - please press THANKS :good:
If anyone needs any clarification, let me know, I will try and respond as soon as possible (if others could help - that would be appreciated too)

Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!

EM101 said:
Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!
Click to expand...
Click to collapse
whats yer firmware fella?

painnpleasure said:
whats yer firmware fella?
Click to expand...
Click to collapse
It was 3.17.502.3 but since I achieved s-off I am now a "converted to Google Edition" with firmware 3.62.1700.1.

EM101 said:
It was 3.17.502.3 but since I achieved s-off I am now a "converted to Google Edition" with firmware 3.62.1700.1.
Click to expand...
Click to collapse
Ok thnx fella.im on 3.63.111.3 and having difficulties running rumrunners.ill give it another go then. I want to get to go Google edition aswel.

sudo ./soju
I get err command not found!!
help plz should I be using the linux?
No prob I gut it :laugh:

skythunder83 said:
sudo ./soju
I get err command not found!!
help plz should I be using the linux?
No prob I gut it :laugh:
Click to expand...
Click to collapse
Use the ls command to see what is in the directory you are in. Use the cd command to change directories. Keep searching til you find the directory where you put the soju file. Good luck.

Does my HTC One still have to be unlocked from HTC-Dev? Thank you in advance.

EM101 said:
Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!
Click to expand...
Click to collapse
Glad to hear buddy. I also spent a considerable amount of time trying to find a solution to this and had just about given up.
Thanks for providing some additional notes on your steps too, might help someone else get theirs working too.
Sent from my One using XDA Premium 4 mobile app

alessiomoro1994 said:
Does my HTC One still have to be unlocked from HTC-Dev? Thank you in advance.
Click to expand...
Click to collapse
By whatever means, you will need to initially be rooted. Unlocking via HTC Dev was how I got root.
Ironically this also (at the time, not sure if it's changed) doesn't work in Windows 8.1 lol and I had to root my phone using my parents laptop with Windows 7 installed.
They then upgraded to 8,1 so I couldn't use it to get S-OFF later on.
Sent from my One using XDA Premium 4 mobile app

I finally got s-off on my att htc one. Was pretty much trying the same thing as OP stated here, but had some difficulties with other things.
1. OP's instructions didn't work for latest ubuntu (13.10)
2. Had linux mint installed on my pc, but it was 64bit.. tried quite a bit to get it working there (adb and fastboot work), but rumrunner was not happy with 64bit
3. Finally tried it on Ubuntu 12.04.3 LTS 32 bit and everything was smooth with it
One other thing to note.. I used live USB instead of installing ubuntu on my pc. had no issues, but had to use a bit older version of ubuntu and 32 bit (even tho my pc has 16Gigs of memory)

Don't know what's different, but Rumrunner worked for me - hboot 1.56, ARHD 41.0 and Windows 8.1

I'm using crouton install of Ubuntu on my chromebook and after trying to install adb and fastboot I get:
E: Unable to locate package android-tools-adb
E: Unable to locate package android-tools-fastboot
Any ideas guys? I really want s-off! Any help would be appreciated!
Sent from my Nexus 7 using XDA Premium 4 mobile app

roose21 said:
I'm using crouton install of Ubuntu on my chromebook and after trying to install adb and fastboot I get:
E: Unable to locate package android-tools-adb
E: Unable to locate package android-tools-fastboot
Any ideas guys? I really want s-off! Any help would be appreciated!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sounds like the location of those packages has changed? Unless the reason it isn't working is because of the version of Ubuntu you're on. Hmm.
Sent from my One using XDA Premium 4 mobile app

Try this:
http://vondroid.com/threads/how-to-...on-ubuntu-and-other-linux-based-systems.9793/
Sent from my One using XDA Premium 4 mobile app

My computer finally can recognize my phone in fastboot mode. Thanks !
Sent from my HTC One using Tapatalk

punisher195 said:
My computer finally can recognize my phone in fastboot mode. Thanks !
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Use the "thanks" button and rate the thread then
Sent from my One using XDA Premium 4 mobile app

[HOW TO] Root Yoga Tablet 2 [STEP-BY-STEP] [NOOB FRIENDLY]

Hi?
I'm posting this thread for all those who want to root their tablet but need a step by step guide for the same. I have condensed the information from many threads and put it into one. All the credit goes to the respective thread owners who have posted the guides. Let's begin:
NOTE: Im not responsible if you brick your device. You are solely responsible for what happens. If you follow the steps correctly it is unlikely that it will harm your device. If you face any issues you can post it here and I will try to solve them ( or someone else will). All good.
Scary stuff apart, let's begin to root your device ?
1. On your device, Go to Settings, Developer Options, and click on Enable USB Debugging. If there is no Developer Options in Settings, Click on About Phone and click 7 times on Build Number. This will give u the option.
2. Once you have enabled it, connect your device to your computer via USB cable.
3. Install the device drivers from the autoplay options.
4. Right click on My Computer and click on Manage
5. A new window will open called Computer Management, under which u have to click on Device Manager.
6. A list of devices connected to your computer will be shown on the right hand side.
If your device is listed under heading Android, as Android ADB Composite Device, then there is no need to download and install adb/fastboot drivers, and you can go ahead with the rooting process.
But its most likely your device will be listed under Other Devices. Under that it will be as MTP device or by the name of your device itself. This means you have to download and install adb/fastboot drivers on your computer before rooting it.
7. Open your browser and click on http://adbdriver.com/upload/adbdriver.zip which will download the adb installer on your computer. Run through the setup and install it. Run the program, it will automatically detect your device and install the necessary adb/fastboot drivers for it on your computer.
Alternatively, you can click on http://forum.xda-developers.com/showthread.php?p=48915118 through which you can install the same. I did it with the first method for my device.
Download and install it in [C drive].
8. Once the drivers are installed, go to Device Manager again (Step 4 and 5), and check on the list of devices. Your device should be listed under the heading Android, and showing as Android ADB Composite Device.
9. Open up C drive, there should be a folder named 'adb' under it. Open that folder and right click anywhere and open a command prompt.
U can also press 'Win+R' keyboard keys and type in 'cmd.exe' to open up a command prompt and use the cd command to come into the right folder. Once your into the adb folder in the command prompt (it should show as "C://adb>".
Type in command 'adb devices' and press enter (without the colons).
This should show you that your device is connected by the name of your chipset as Baytrail******. If it doesn't show this it means the adb drivers are not installed or ur device is not connected to the computer. Only once after it detects your device you have to go ahead with your rooting process.
10. After you have successfully completed all the above steps you are now ready to root your device.
11. Click on this link forum.xda-developers.com/showpost.php?p=57543871&postcount=1 from where you will have to download 'Intel Fastboot Tethered Temporary Recovery Session Launcher' onto your computer and extract it to some folder.
12. Download the UPDATE SuperSU zip file to your device and store it in your internal memory so you can find it easily later.
13. Now open the folder where you have extracted the Intel Fastboot Tethred Temporary Recovery Session launcher. Double click the launcher.bat file to start and type " ACCEPT " case sensitive without quotes to continue.
check that the tool is reporting as either :
DEVICE STATUS: ADB-ONLINE
DEVICE STATUS: FASTBOOT-ONLINE*
If " DEVICE STATUS: UNKNOWN " please check your cable connection and driver installation under Windows Device Manager
If " DEVICE STATUS: UNAUTHORIZED "
Please check if your devices is displaying an authorization prompt.
Be sure to check 'Always allow from this computer' and then press ok.
It will ask for the type of recovery u would prefer to run. Options 1-4 will be TWRP recovery and 5 will be CWM. I selected the CWM recovery. So enter number '5' and press enter.
14. It will display the list of triggers to be selected for the rooting process. Select the trigger to launch the Temporary CWM Recovery Session.
The list will be as follows:
T1 oem startftm ( very few devices support this command , but its the original used so )
T2 oem backup_factory ( limited devices support this command )
T3 oem stop_partitioning ( should work on alot of kitkat builds )
T4 oem stop_partitioning ( probably works on all devices that are supported (Jellybean , KitKat , Lollipop)
15. Select trigger 'T4' if you have upgraded your tablet to Lollypop Android 5.0.1. After selecting the trigger your device should reboot into fastboot and begin to copy files to your device.
note :*If your device hangs at the waiting-for-device screen and you see droidboot CMD Waiting on your devices double check that the fastboot driver installed correctly.
note :*If you see unknown oem command the trigger isn't supported by your device.
16. The temporary cwm recovery session will start at this point on your device.
17. Select install zip from the recovery menu using vol up / vol down to navigate and power to select.
18. Select install zip from sdcard / external_sd depending on where you placed the file and select the UPDATE-SuperSU-vX.Xx.zip you downloaded earlier
19. Confirm the installation.
20. After install completes reboot your device*through the reboot device option in the recovery menu itself.
21. It's going to take a while for the device to reboot. 'Android is upgrading' window will pop up once the screen gets on. After the boot is complete open all apps to see Super SU installed in it.
Now you have successfully rooted your Yoga Tablet 2. Enjoy ☺
NOTE: Follow all steps carefully and correctly so it becomes highly unlikely that you may brick your device. Make sure there is no powercut to your computer during the rooting process if you are not using a laptop or a UPS for your system. You can post any queries or questions in the thread.
All credit goes to the original thread owners, social-design-concepts, workdowg for helping all yoga tablet users to be able to root their devices.
A lot of work has gone into making this NOOB friendly step by step guide. Hit thanks if this helps you. Much appreciated. Have fun rooting.☺
Posted from my Rooted Lenovo Yoga Tablet 2 (830LC).

Much appreciated for this noob guide.

Thanks for the tutorial.
I did all the steps as you said. I am at step 15 and selected t4 and then the command prompt showed waiting for device and then my tab rebooted itself and then came to a fastboot mode.
Now n TAB its showing error that "E: No valid installer medium found"
now when i press the volume keys, the boot option changes and then the error message changes to
"could not open /sys/devices/virtual/backlight"
Please help

Thanks........ successfully rooted yt2 1050L
Sent from my YOGA Tablet 2-1050L using Tapatalk

anilkumar247 said:
Thanks for the tutorial.
I did all the steps as you said. I am at step 15 and selected t4 and then the command prompt showed waiting for device and then my tab rebooted itself and then came to a fastboot mode.
Now n TAB its showing error that "E: No valid installer medium found"
now when i press the volume keys, the boot option changes and then the error message changes to
"could not open /sys/devices/virtual/backlight"
Please help
Click to expand...
Click to collapse
Did u check that ADB/fastboot drivers installed correctly? Try to reinstall those drivers and check again. Did u select the UPDATE SuperSU zip file and install it?

AndroMAN said:
Did u check that ADB/fastboot drivers installed correctly? Try to reinstall those drivers and check again. Did u select the UPDATE SuperSU zip file and install it?
Click to expand...
Click to collapse
How can i make sure they are installed correctly ?
I have reinstalled them and tried again, but still getting the same error.
I am not getting the update Super SU option, or any options to get it installed.

@AndroMAN any idea why my 64gb sdcard is not recognized.
Sent from my YOGA Tablet 2-1050L using Tapatalk

anilkumar247 said:
How can i make sure they are installed correctly ?
I have reinstalled them and tried again, but still getting the same error.
I am not getting the update Super SU option, or any options to get it installed.
Click to expand...
Click to collapse
Step 8 and 9. Check under command prompt. It should show the name Baytrail***** when you type in the command "adb devices". Only then u can go ahead.

sajsaj7829 said:
@AndroMAN any idea why my 64gb sdcard is not recognized.
Sent from my YOGA Tablet 2-1050L using Tapatalk
Click to expand...
Click to collapse
Have you rooted your tablet? Was it detecting it earlier?

AndroMAN said:
Have you rooted your tablet? Was it detecting it earlier?
Click to expand...
Click to collapse
Hv rooted...Yes 32gb was working perfect but 64gb it says blank sdcard
Sent from my YOGA Tablet 2-1050L using Tapatalk

Hi
yes, its showing the device ID
prntscr.com/948uzk
prntscr.com/948ybk
I have blackened the device ID

sajsaj7829 said:
Thanks........ successfully rooted yt2 1050L
Sent from my YOGA Tablet 2-1050L using Tapatalk
Click to expand...
Click to collapse
Good? All the best and enjoy your rooted device. Have you installed Xposed Framework on it yet?

sajsaj7829 said:
Hv rooted...Yes 32gb was working perfect but 64gb it says blank sdcard
Sent from my YOGA Tablet 2-1050L using Tapatalk
Click to expand...
Click to collapse
Try formatting the new sd card via the tablet, even I have put a 64GB card and I had to format it before it could detect.

anilkumar247 said:
Hi
yes, its showing the device ID
prntscr.com/948uzk
prntscr.com/948ybk
I have blackened the device ID
Click to expand...
Click to collapse
Sorry to hear your facing issues. There are already people saying they have successfully rooted their device using this guide. So there must be some step u might have missed or done incorrectly.
Send me the details of your device, model of tablet, which Android version.

AndroMAN said:
Good? All the best and enjoy your rooted device. Have you installed Xposed Framework on it yet?
Click to expand...
Click to collapse
Thanks.. cld u please link me to ver of xposed working on yt2.
---------- Post added at 11:25 AM ---------- Previous post was at 11:21 AM ----------
AndroMAN said:
Try formatting the new sd card via the tablet, even I have put a 64GB card and I had to format it before it could detect.
Click to expand...
Click to collapse
@AndroMAN somebody hv made a exfat binary zip to be flashed via teetherd recovery.... any idea how to go into twrp recovery.

anilkumar247 said:
Hi
yes, its showing the device ID
prntscr.com/948uzk
prntscr.com/948ybk
I have blackened the device ID
Click to expand...
Click to collapse
AndroMAN said:
Sorry to hear your facing issues. There are already people saying they have successfully rooted their device using this guide. So there must be some step u might have missed or done incorrectly.
Send me the details of your device, model of tablet, which Android version.
Click to expand...
Click to collapse
Hey i think i have the solution for your problem because everytime i am facing the same issue
That means at first adb drivers are shown as installed correctly within the window of the 'Intel Fastboot Tethered Temporary Recovery Session Launcher' tool. But after my tablet reboots into fastboot via method t4 it always says "No valid installer medium found".
Note: I have these adb drivers installed http://forum.xda-developers.com/showthread.php?t=2588979
So here is my solution that works for me: (this is my first post so i cant provide any screenshots.. )
1. let the tablet stay within the fastboot mode
2. in windows: navigate to the device manager --> there you should see the symbol "android phone" with a yellow triangle
3. right click on this symbol and choose the first option "update drivers" (sry i don't know if i translated it correctly xD)
4. choose the option "search on pc .."
5. there you select the second option "choose from a list.."
6. within the list you select 'android device'
7. within the next list you select 'google nexus adb device'
8. after that the drivers are installing and the recovery starts on your tablet :fingers-crossed:

1subw00fer1 said:
Hey i think i have the solution for your problem because everytime i am facing the same issue
That means at first adb drivers are shown as installed correctly within the window of the 'Intel Fastboot Tethered Temporary Recovery Session Launcher' tool. But after my tablet reboots into fastboot via method t4 it always says "No valid installer medium found".
Note: I have these adb drivers installed http://forum.xda-developers.com/showthread.php?t=2588979
So here is my solution that works for me: (this is my first post so i cant provide any screenshots.. )
1. let the tablet stay within the fastboot mode
2. in windows: navigate to the device manager --> there you should see the symbol "android phone" with a yellow triangle
3. right click on this symbol and choose the first option "update drivers" (sry i don't know if i translated it correctly xD)
4. choose the option "search on pc .."
5. there you select the second option "choose from a list.."
6. within the list you select 'android device'
7. within the next list you select 'google nexus adb device'
8. after that the drivers are installing and the recovery starts on your tablet :fingers-crossed:
Click to expand...
Click to collapse
That might just work :fingers-crossed:

1subw00fer1 said:
Hey i think i have the solution for your problem because everytime i am facing the same issue
That means at first adb drivers are shown as installed correctly within the window of the 'Intel Fastboot Tethered Temporary Recovery Session Launcher' tool. But after my tablet reboots into fastboot via method t4 it always says "No valid installer medium found".
Note: I have these adb drivers installed http://forum.xda-developers.com/showthread.php?t=2588979
So here is my solution that works for me: (this is my first post so i cant provide any screenshots.. )
1. let the tablet stay within the fastboot mode
2. in windows: navigate to the device manager --> there you should see the symbol "android phone" with a yellow triangle
3. right click on this symbol and choose the first option "update drivers" (sry i don't know if i translated it correctly xD)
4. choose the option "search on pc .."
5. there you select the second option "choose from a list.."
6. within the list you select 'android device'
7. within the next list you select 'google nexus adb device'
8. after that the drivers are installing and the recovery starts on your tablet :fingers-crossed:
Click to expand...
Click to collapse
Hello
That worked
But instead of google nexus adb device in the list, i got only motorola ADB device, but still it worked .
Thanks to both of you for the help.

sajju73 said:
Thanks.. cld u please link me to ver of xposed working on yt2.
---------- Post added at 11:25 AM ---------- Previous post was at 11:21 AM ----------
@AndroMAN somebody hv made a exfat binary zip to be flashed via teetherd recovery.... any idea how to go into twrp recovery.
Click to expand...
Click to collapse
There is no working mode of Xposed on YT2 as far as I have seen. Still have to look into it.
Go to recovery the same way u did last time, through 'Intel fastboot launcher:

Congratulations @anilkumar247. I hope your device is rooted and working well. And thanks to @1subw00fer1 for helping out and contributing to this thread. Great work guys. All good ☺

Please help (need working unlock and root instructions)

I've been up and down the forums for two days trying every method and app and whatever else is recommended.
asus zenfone 2 laser
Z00TD (ZE551KL)
-i cannot unlock bootloader (Asus unlock tool does not work for any variant)
- cannot root with any one click app (assuming because bootloader is locked)
- cannot manually install drivers via any instructional method online. (They all seem to be 64 bit when I have a 32 bit machine) and there is no actual exe file to install anywhere that i can locate.
- cannot use windroid as it requires twrp (basically root) ....useless.
-cannot adb command unlock or root, does not recognize device (assuming because proper drivers are not installed)
I'm on the updated software version 1.16.40.763-20151201
Someone please give me a hint or some lead as to what I'm missing or where I'm going wrong.
Thanks in advance.

Download the adb-fastboot tool from here...:- Moderator EDIT PPC links are not allowed
Install it.. it will ask you for installing drivers also.. install them... Visit Asus.com and download the drivers for your device. . Now search for Device manager in Windows start menu. Click on Device Manager and then you will see a device named as Android or something like that... Right click on it.. then select update drivers... Then you will see two options 1). Check online 2. Browse my Pc for updated drivers.. select the 2nd one now browse the downloaded file of drivers and select it.. select the folder of files .(After unzipping the folder)...
Click on update.. now drivers will get installed.. now
Use Ctrl+shift+right click..(in adb folder mainly located in local disk c) and select open command Windows here. Enable the USB debugging option in developer options of your device.. At first it will ask for permissions. Alow it.. Now you can flash anything.. for further information ,if needed you can contact me..

Njishi said:
Now you can flash anything.. for further information ,if needed you can contact me..
Click to expand...
Click to collapse
LOL

Njishi said:
Download the adb-fastboot tool from here...:- Moderator EDIT PPC links are not allowed
Install it.. it will ask you for installing drivers also.. install them... Visit Asus.com and download the drivers for your device. . Now search for Device manager in Windows start menu. Click on Device Manager and then you will see a device named as Android or something like that... Right click on it.. then select update drivers... Then you will see two options 1). Check online 2. Browse my Pc for updated drivers.. select the 2nd one now browse the downloaded file of drivers and select it.. select the folder of files .(After unzipping the folder)...
Click on update.. now drivers will get installed.. now
Use Ctrl+shift+right click..(in adb folder mainly located in local disk c) and select open command Windows here. Enable the USB debugging option in developer options of your device.. At first it will ask for permissions. Alow it.. Now you can flash anything.. for further information ,if needed you can contact me..
Click to expand...
Click to collapse
When uninstall those drivers I get the yellow triangle on them. They aren't functioning.
Sent from my A1R using XDA-Developers mobile app

nujaxx said:
When uninstall those drivers I get the yellow triangle on them. They aren't functioning.
Sent from my A1R using XDA-Developers mobile app
Click to expand...
Click to collapse
You don't need to uninstall them.. just update them..

Typo.... install
Sent from my A1R using XDA-Developers mobile app

I must be doing something wrong. Because I've done all of that. And the drivers don't install properly. I can get into fast boot and that's where it stops for me. The bootloader 20007.img code keeps failing.
I don't know. Something isn't right. I can't even unlock it with the Asus unlock tool. I've tried every one for every variant.
Sent from my A1R using XDA-Developers mobile app

this might sound stupid, but try a different, better, usb cable.
I had a similar issue years ago, trying to flash my first android phone, windows would also give me device manager error. i beat my head on the wall for two days using the motorola supplied data cable, until on a whim i tried a different USB cable and everything worked.

Oneplus 5 ADB

Can someone guide me how to get ADB working on OnePlus 5?

stalvekio said:
Can someone guide me how to get ADB working on OnePlus 5?
Click to expand...
Click to collapse
i'm using 'block this!'

What's the problem about it?
download android platform tools or minimal adb and fastboot, make sure drivers are installed and activate ADB Debugging in Developer Options

colin.pohle said:
What's the problem about it?
download android platform tools or minimal adb and fastboot, make sure drivers are installed and activate ADB Debugging in Developer Options
Click to expand...
Click to collapse
I have tried all of those. All i get is emty list. It cant detect my phone.
Probably i havent found the right drivers

stalvekio said:
I have tried all of those. All i get is emty list. It cant detect my phone.
Probably i havent found the right drivers
Click to expand...
Click to collapse
Try these.

I had driver issue for side loading even after Installing OnePlus drivers windows wanted to use standard ADB drivers

Download the Android SDK kit first. Then plug in your OP5 to your PC and you should see something called "CD Drive (F: ) OnePlus Drivers". Click on it and it will install the OP5 drivers. Then enable developer options on your phone, by hitting the build number 7 times. Then go into developer settings and enable USD debugging. After that, go to the Android SDK folder and go to tools/platform tools, then hold shift and right click and open a command/powershell window and type adb devices. After that you should receive a fingerprint notification on your phone so just say yes to it. Ten type in adb devices again in the command/powershell window and it should be able to detect your device. I said everything from scratch so I hope it sort of helps!

What exactly do you want to accomplish. Because I just flashed everything on my phone. When the phone was running normal ADB was not recognized in my phone. However when I was in bootloader mode I got to unlock my bootloader and flash TWRP.

ddaharu said:
What exactly do you want to accomplish. Because I just flashed everything on my phone. When the phone was running normal ADB was not recognized in my phone. However when I was in bootloader mode I got to unlock my bootloader and flash TWRP.
Click to expand...
Click to collapse
Adb still somehow has to work... The drivers are there (although all my win 10 devices installed the correct ones automatically) and it doesn't even really matter which adb he is using

shadowstep said:
Try these.
Click to expand...
Click to collapse
I tried. Device manager still shows adb interface yellow.
d0nsman said:
Download the Android SDK kit first. Then plug in your OP5 to your PC and you should see something called "CD Drive (F: ) OnePlus Drivers". Click on it and it will install the OP5 drivers. Then enable developer options on your phone, by hitting the build number 7 times. Then go into developer settings and enable USD debugging. After that, go to the Android SDK folder and go to tools/platform tools, then hold shift and right click and open a command/powershell window and type adb devices. After that you should receive a fingerprint notification on your phone so just say yes to it. Ten type in adb devices again in the command/powershell window and it should be able to detect your device. I said everything from scratch so I hope it sort of helps!
Click to expand...
Click to collapse
I did that. ADB devices gives me empty list.

stalvekio said:
I tried. Device manager still shows adb interface yellow.
Click to expand...
Click to collapse
Do you have Windows? If yes, what version? With 10, I know they work a 100% for sure. With 7, after installing these, there is still a yellow exclamation mark in Device Manager. To resolve that, right click on the device in Device Manager, uninstall the driver. Then, reconnect the device after enabling USB Debugging, and then let windows download the required drivers from Windows Update. It should be ~8.5 MB. Once it's downloaded and installed automatically, you should be good to go.

shadowstep said:
Do you have Windows? If yes, what version? With 10, I know they work a 100% for sure. With 7, after installing these, there is still a yellow exclamation mark in Device Manager. To resolve that, right click on the device in Device Manager, uninstall the driver. Then, reconnect the device after enabling USB Debugging, and then let windows download the required drivers from Windows Update. It should be ~8.5 MB. Once it's downloaded and installed automatically, you should be good to go.
Click to expand...
Click to collapse
win 8.1.
Did as you sugsested but no change .... adb interface is yellow

stalvekio said:
win 8.1. Did as you sugsested but no change .... adb interface is yellow
Click to expand...
Click to collapse
Stop using the worst windows ever! Jokes apart, try using the these or these. I had them installed before, and they worked fine, in Windows 7 & 10 at least. Good luck! :good:

shadowstep said:
Stop using the worst windows ever! Jokes apart, try using the these or these. I had them installed before, and they worked fine, in Windows 7 & 10 at least. Good luck! :good:
Click to expand...
Click to collapse
Nope. No help.
I think it´s something very easy i have missed

Finaly - got it working.
This guide helped:
http://www.asunsoft.com/android/how-to-manually-install-usb-driver-for-android-phone.html