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?

✪✪✪ [ROOT] [Restore] [OneClick OR Manual] [PC] [MAC] Kwongger's FLO Noob Root Kit ✪✪✪

✪✪✪ [ROOT] [Restore] [OneClick OR Manual] [PC] [MAC] Kwongger's FLO Noob Root Kit ✪✪✪
EVERYBODY!
WE ARE BACK DUE TO POPULAR DEMAND!!!​
Kwongger's All-In-One FLO Noob Root/Restore Kit FOR PC and Mac
YES! We are ADB FREE!!!​
Why we are back:
I really feel accomplished when I acutally do the commands myself! Apparently so do others, we are back B****ES!
I felt that I didn't get the help I needed/wanted as a n00b on XDA, this is a new account FYI, so I like to make n00b kits with AWESOME instructions, ENJOY!!!
FYI: I want to provide the best possible support that I can (even though this is free)
DOWNLOAD v3 ​
Hey! The ONE-CLICK/Restore update is currently uploading!
Instructions in post #2, Change-log in post #3.
DISCLAIMER:
By downloading the files, you accept the fact that I am NOT in anyway responsible for what YOU do to YOUR device, unless it starts shooting lasers at iOS devices, then all the credit is mine . Really,in all seriousness, this procedure is a BEGINNER procedure, I am simply providing instructions and TOOLS! I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE!!!​

Manual ROOT Instructions!
(If you want One-Click, then Just double-click either the Flo ROOT by Kwongger.bat (to root) or the Flo RESTORE.bat for a out-of-box restoration!
I’ll make a video soonish.​
Driver Installation!
To Install The Drivers Fresh
Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Devices in the left pane.
Locate and expand Other device in the right pane.
Right-click the device name (such as Nexus S) and select Update Driver Software. This will launch the Hardware Update Wizard.
Select Browse my computer for driver software and click Next.
Click Browse and locate the USB driver folder. (The Google USB Driver is located in<sdk>\extras\google\usb_driver\.)
Click Next to install the driver.
Follow the Instructions!
Upgrade Existing Drivers
Or, to upgrade an existing Android USB driver on Windows 7 with the new driver:
Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Device Manager in the left pane of the Computer Management window.
Locate and expand Android Phone in the right pane.
Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.
Select Install from a list or specific location and click Next.
Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
Click Browse and locate the USB driver folder. (The Google USB Driver is located in<sdk>\extras\google\usb_driver\.)
Click Next to upgrade the driver
Follow the Instructions!
Click to expand...
Click to collapse
Unlocking The Boot Loader!
1. Enable USB Debugging on your Nexus 7 in Development Settings
2. Open yourself a Command Prompt (or Terminal for MAC) in the Kwongger Nexus 7 folder!
a. Hold down shift
b. Right Click in the folder
c. Click Open Command Window/Prompt here
3. Boot into the bootloader using:
Code:
adb reboot bootloader
!!!!!!!!!!!NOTICE!!!!!!!!!!!!!!!
The next step will FACTORY RESET your device!!!
4. Once it is in the bootloader, enter this:
Code:
fastboot oem unlock
5. It will now ask you if you do, in fact, want to unlock your bootloader. Use Volume up/down to select YES and hit power to Confirm.
6. Your Nexus 7 FHD now has an Unlocked Bootloader.
7. IMPORTANT:
Reboot the device!
Click to expand...
Click to collapse
Choose either TWRP or CWM!
Installing TWRP!!!
1. Get into Your bootloader Again. (Above)
2. Type the following to flash the Team Win Recovery Project version 2.6:
Code:
fastboot flash recovery nexus7twrp.img
note: if you change the name use that in the .img part
3. Done!!!
Installing Clockwork Mod Recovery!!!
1. Get into Your bootloader Again. (Above)
2. Type the following to flash the Team Win Recovery Project version 2.6:
Code:
fastboot flash recovery nexus7CWM.img
note: if you change the name use that in the .img part
3. Done!!!
Click to expand...
Click to collapse
Rooting on Android 4.3!!!
.01 Copy The SuperSU.zip to the internal storage of your device.
1. Boot in to your bootloader and use the volume keys to select Recovery and use the Power button to confirm.
1a. RECOMMENDED: Tap BACKUP and Swype to confirm to make a backup of your current, UNROOTED n7.
2. Tap INSTALL.
3. Navigate to where you put the SuperSU.zip
4. Tap the zip.
5. Swype to confirm the flash!
6. If all goes well (no reason that I know that it shouldn’t) YOUR NEXUS 7 IS ROOTED!!!!
Click to expand...
Click to collapse
CONGRATS!!!!!!!!!!!!!

v1
Nothing New! This is 1.0
Click to expand...
Click to collapse
v2
I updated the Fastboot and ADB because some people were having some issues, it seems to have fixed the issues.
Click to expand...
Click to collapse
v3
I added the ever popular Mac Support! AND Clockwork Mod Recover, I don't know it is touch or not XD, could someone check? Just type
Code:
fastboot boot recovery nexus7CWM.img
and let me know! Thanks in advance.
Click to expand...
Click to collapse

I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.

Gabik123 said:
I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.
Click to expand...
Click to collapse
That's weird. I will update it.
Sent from my HTCONE using XDA Premium HD app

Actually!
Are you on 32bit? I included 64bit.

I like that you moved it to General!!!
I always thought that the DEVELOPMENT threads should be only used for KERNELS/ROMS
THANK YOU

Hey man, thanks for the instructions but could you clarify that you have to restart/boot up completely after unlocking the bootloader? I was still in fastboot after unlocking it when I flashed TWRP, and now TWRP is asking for a password, failing on all operations and I'm stuck in a bootloop.

EvanVanVan said:
Hey man, thanks for the instructions but could you clarify that you have to restart/boot up completely after unlocking the bootloader? I was still in fastboot after unlocking it when I flashed TWRP, and now TWRP is asking for a password, failing on all operations and I'm stuck in a bootloop.
Click to expand...
Click to collapse
Dang Dude, I am sorry. I just went ahead and put that in. :/
I want to help you with this.
Can you get into the boot loader or anything? Maybe if you can get TWRP working, I can send you a Nandroid of a stock, one (Once I get mine )

Kwongger said:
Dang Dude, I am sorry. I just went ahead and put that in. :/
I want to help you with this.
Can you get into the boot loader or anything? Maybe if you can get TWRP working, I can send you a Nandroid of a stock, one (Once I get mine )
Click to expand...
Click to collapse
Just found the solution in another thread: Open TWRP, Format Data first, then Factory Reset, finally reboot. I knew it wasn't a long term problem but I'm glad I didn't have to wait for Google to release Factory Images lol.

Gabik123 said:
I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.
Click to expand...
Click to collapse
I am having this issue in windows 8 also, "offline" but I am getting the same thing using android sdk. Can someone provide some assistance please. Not sure why having such an issue.

EvanVanVan said:
Just found the solution in another thread: Open TWRP, Format Data first, then Factory Reset, finally reboot. I knew it wasn't a long term problem but I'm glad I didn't have to wait for Google to release Factory Images lol.
Click to expand...
Click to collapse
AWESOME!!!!!!!!!!
I feel better now XD

jmill75 said:
I am having this issue in windows 8 also, "offline" but I am getting the same thing using android sdk. Can someone provide some assistance please. Not sure why having such an issue.
Click to expand...
Click to collapse
I don't know... I have Windows 7. I also have NO IDEA why this would happen... Try using a port on the back of the PC (desktop) . If that doesn't do it, try USB 3.0 (if you have it). Also, if you are using the Stock cord, try other cords. That is all I can think of... :/

Kwongger said:
I don't know... I have Windows 7. I also have NO IDEA why this would happen... Try using a port on the back of the PC (desktop) . If that doesn't do it, try USB 3.0 (if you have it). Also, if you are using the Stock cord, try other cords. That is all I can think of... :/
Click to expand...
Click to collapse
There is a way to disable driver verification after rebooting in windows 8. I had to do this with my SGSIII and Win 8 x64, just google around for it, bet that's the problem.

RubenRybnik said:
There is a way to disable driver verification after rebooting in windows 8. I had to do this with my SGSIII and Win 8 x64, just google around for it, bet that's the problem.
Click to expand...
Click to collapse
Thanks! I will find it and add it to the instructions with credit.
Sent from my HTCONE using XDA Premium HD app

I see the pack includes the tools for MAC. I am on 10.8.4. Has anyone tried this on a MAC yet? I will be doing so later.

androidfr33k said:
I see the pack includes the tools for MAC. I am on 10.8.4. Has anyone tried this on a MAC yet? I will be doing so later.
Click to expand...
Click to collapse
Wait how would you do this on mac? Does the same .zip file work or would I need a different one? If you get it working please post a tutorial!

Looks like SuperSU came with the TWRP image(no need to copy it over separately). I tried to reboot from TWRP after updating the recovery and it forced me to flash SuperSU to root.

Nxxx said:
Wait how would you do this on mac? Does the same .zip file work or would I need a different one? If you get it working please post a tutorial!
Click to expand...
Click to collapse
I included Mac ADB... But not fastboot, you would need Fastboot as well, i'll get a Mac pack up tonight.

disregard....
working great! thanks OP

[GUIDE] Install Windows ADB Drivers for Fire HDs ("Newbie Friendly")

➜ No big ol’ SDK ➜ Latest Google drivers ➜ No messing with inf files ➜ ADB from any location ➜ Drag and drop files
Figured XDA needed a couple more ADB driver guides, so I'm bringing these down from Google drive where they've been getting a lot of use--with no complaints so far. :fingers-crossed:
Follow the steps below to install the Google ADB driver for "normal" (OS) mode.
Follow post #2 to install the driver for sideload mode. You must do this to sideload OS .bin files via stock recovery.
See post #3 for basic info/tips for using the command window and entering adb commands.
[EDIT September 21, 2015] If you're running Windows 10, read this:
At step 3 you install 15 Second ADB Installer. Some Win 10 users are reporting a problem. Please do this to help track it down:
- Be sure to run as Administrator.
- If you get an error, post the exact error and when it happens. Do not rerun Installer until someone replies to post.
- If you do not get an error, please post and say so and tell what type of Win 10 you have (home, pro, enterprise, etc.)
Thanks!
Install ADB Driver for "Normal" (OS) Mode
This uses @Snoop05's 15-Seconds ADB Installer. It provides the driver and software you need and puts the path to adb.exe into your PATH variable so you can run ADB commands from any folder.
Before you begin:
(1) Turn off anti-virus software
(2) Disconnect other physical devices that use adb and shut down any virtual ones. This can go very smoothly if you're not running anything that uses adb, including emulators, some photo-sync software, Gatesjr debloater, etc.
1. Make sure adb debugging is enabled on the the device. (Settings->My Device->Developer Options: Debugging)
To open Developer Options: In Settings -> My Device, tap on the serial number until Developer Options appears at bottom of screen.
2. If you've never connected Fire HD to computer, connect now and read this:
a. You may see a USB debugging message on tablet, tap "Always" and "Allow."
Even if you don't see message, Windows should try to install generic MTP drivers (not ADB!). Wait until you see success or failed message.
b. Unplug/replug and wait for Windows Explorer OR for message that prompts what to do when device is connected and choose Open window to Display Files, check Always do this and then OK.
c. Disconnect..
3. If you KNOW there’s no adb driver installed for the device, go to next step.
. . . If driver might already be installed, do hidden steps.
Connect to computer, open Device Manager (instructions below) and see if a driver is listed under Android Device.
- If a driver is NOT listed, go to next step.
- If a driver IS listed, open CMD window in folder containing adb.exe and run adb devices command (step 12).
* If adb devices DOES return an ID, this driver is working and you don’t need to install a different one.
* If adb devices does NOT return an ID:
a. In Device Manager, right-click the driver and choose Uninstall.
b. Unplug the device and restart Windows.​
4. Download the latest version, currently v. 1.4.3, of 15 seconds ADB Installer and run it as Administrator.
If you are not Administrator, right-click the file and choose “Run as Administrator“
Read all about 15-seconds Installer at the link.
Press Y to install ADB and Fastboot
Press Y to install ADB system-wide or N for current user onlyYou should see:
Installing ADB and Fastboot . . .
4 files(s) copied
If you see 0 files copied, post the error with your Windows version and the drive it's installed on.​
Press Y to install drivers
View attachment 3455788​
5. An Install Wizard will run. Look for it and install device software!
6. Connect the Fire to the computer and wait until you see it in Windows Explorer.
7. 6/3/2016 Update for Win 10: Your drivers might already be installed. Check for Allow USB Debugging on tablet. Go to step 12 and run the adb devices command.
. . . If it shows serial number and unauthorized, you need to enable USB debugging and run command again. It should then show serial number and "device." You're done!
. . .If it doesn't show serial number, continue the steps.
Win 7 and 8.1: Open Device Manager:
Win10: ? Win8: Right-click Start Button and choose Device Manager. Win7: Click Start button and type Device Man [enter]
8. Find Fire under Other Devices, right-click it, and choose Update Driver Software.
If you don't see Fire under Other Devices, disconnect/reconnect or try a different USB port, or try toggling Enable ADB in Developer Options. If nothing works, disconnect and reboot both Fire and computer and try again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
9. Press Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.
​
10. Find Android Device, click it and press Next.
. . . If Android Device is not listed, look here.
If you DID NOT run 15 Seconds ADB Installer, STOP, disconnect from PC and run it now.
If you DID run 15 Seconds ADB Installer:
a. Double-click Show All Devices.
b. Under Manufacturer, scroll to Google, Inc, click it and continue.
↠ If Google, Inc is not listed, the ADB drivers are not installed, they installed incorrectly or were corrupted. STOP now and follow all the steps again.
11. Select Google, Inc in left pane and then Android Composite ADB interface in right, and press Next.
If the screen you see only has the Model pane (on the right above), scroll down to Android Composite ADB.
↠ If the driver is not listed, drivers have not been installed, they installed incorrectly or were corrupted. STOP now and follow all the steps again.​ 12. At the warning screen, press Yes.
Driver is updated!
13. Run the adb devices command and confirm it returns a device id:
a. Open CMD window: Hold down the Shift key, right-click the desktop (or an empty space in a folder) and choose Open command window here.
b. Type: adb devices [enter]
View attachment 3467199
If you see an ID followed by “device,” the driver is installed correctly. DONE!
If you see an ID followed by “unauthorized,” look at the tablet for “Allow USB Debugging?” message and tap OK.
If debugging message disappears before you say “OK,” unplug/replug tablet to see it again.
Repeat the adb devices command and confirm it now looks like above. DONE!
If you do not see an ID, the driver may not be correctly installed or USB debugging might still be disabled on your tablet. Verify all connections and reboot tablet and PC and repeat this step. If adb devices still doesn’t return an ID, follow this guide from the beginning again.

Install ADB Driver for Sideload Mode
Windows can’t recognize the Fire in sideload mode until you install the driver for it.
Note: These steps are pretty much identical to Post #1. Refer there for illustrations.
1. Connect the tablet to the computer and put it into sideload mode, like this: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
To reboot to recovery:
- From CMD window, run: adb reboot recovery
or
- Manual: (a) Power off the Fire. (b) Hold the power and volume-up buttons until Amazon logo appears, then let go.​
2. Open Device Manager, find KFARWI under Other Devices, right-click it and select Update Driver Software.
If you don't see KFARWI under "Other Devices," see hidden text.
When KFARWI isn't under Other Devices, first be sure you "clicked" Apply Update from ADB on tablet to get into sideload mode.
If you did, see if "Android Device" is listed at top of Device Manager with a driver under it.
If Android Device is not listed, unplug/replug the tablet and see if KFARWI shows up under Other Devices. If it does, go to step 3. If it doesn't, post the problem.
If Android Device is listed, open CMD window in folder containing adb.exe and run adb devices command
- If adb devices returns an ID, this driver is working and you don’t need to install a different one.
- If adb devices does not return an ID, in Device Manager, right-click the driver, select Update Driver Software and go to Step 4.
3. Press Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.
[See “Select your device’s type”]
4. Click Android Device.
[See "Select the device driver you want . . .”]
5. Select the same driver you use for “normal” OS mode (post #1, step 10) and press Next.
6. Click Yes at warning screen.
Driver is updated!
7. In CMD window, run adb devices command and confirm you see your device ID and "sideload," like this:
8. DONE! Issue the sideload command or reboot to exit sideload mode.
Note (shouldn't happen, but . . . ) If you don't get a device ID and you had a driver installed at step 2 and updated it, you'll have to uninstall the driver.
In Device Manager, right-click and uninstall the driver under Android Device.
Restart computer and reboot tablet (to get out of sideload).
Go into sideload mode, right-click KFARWI under Other Devices and see if it has Update Software option.
- If YES, update the driver.
- If NO, reboot once more and go into sideload and you'll have Update option. Update the driver.

Info and Tips for Using the Command (CMD) Window - for "Newbies"
Here's some basic info for using the CMD window and entering commands found in the guides.
Open CMD window
Hold down the shift key, right-click an empty space in an open folder (including desktop), and choose "open command window here"
Give commands on-the-fly
If you used 15-Second Installer (post #1) you can open the CMD window from any convenient location, so you can easily give adb commands "on the fly."
Example: Open CMD from desktop and run adb devices to confirm adb recognizes your Fire.
Install an app (or sideload a bin file)
Open CMD window in the folder containing the file and enter the command: adb install filename.apk
If you open CMD from a different folder, include the full path: adb install "full_path_to\filename.apk"
Format: If there are spaces in the path or filename, put quote marks ( " ) around "full_path_to\filename.apk"
Drag & drop files and copy/paste commands
To enter a long or complicated command or file name into the CMD window, use drag & drop or copy/paste.
Drag and Drop
Type: adb install <--type a space after "install"
. . . then drag and drop your file into the window. The "full_path_to\filename.apk” will be inserted at cursor.
Copy and Paste
Select the command or long file name and use CTRL-C to copy it. In CMD window, type adb install(space) as above, right-click the top bar of the window and choose Edit then Paste.

Installing drivers for sideload
Is there a discussion or a fix for installing the ADB drivers for sideload using windows 10? I'm not sure if Windows 10 is the issue, but instead of getting KFARWI in device manager, I get MT65xx android device. I've followed the instructions after step 9 several times with no luck. I've tried updated the drivers with the ones mentioned in step 3 but ADB device doesn't list a device. Any suggestions?

rking38 said:
Is there a discussion or a fix for installing the ADB drivers for sideload using windows 10? I'm not sure if Windows 10 is the issue, but instead of getting KFARWI in device manager, I get MT65xx android device. I've followed the instructions after step 9 several times with no luck. I've tried updated the drivers with the ones mentioned in step 3 but ADB device doesn't list a device. Any suggestions?
Click to expand...
Click to collapse
Sounds like you're opening Device Manager while in recovery, not sideload mode. Look at step 1 again: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
Once in sideload mode, you should see KFARWI.
(I edited OP to make step for getting into sideload more obvious)

DoLooper said:
Sounds like you're opening Device Manager while in recovery, not sideload mode. Look at step 1 again: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
Once in sideload mode, you should see KFARWI.
(I edited OP to make step for getting into sideload more obvious)
Click to expand...
Click to collapse
Wow...follow the instructions from step one! thanks for your patience

15 Second ADB problem
DoLooper said:
Installing Google ADB drivers for your Fire HD:
Click to expand...
Click to collapse
MRDirtyPixels said:
I followed a guide to install Lolipop on my device, I managed to get the 15 Second ADB Installer but could only get the 1.3 version to work.
When I try to do it now it states on the device that I need 1.3.2 or higher. The 1.4 download gives me an Access Denied message and installed 0 drivers.
Click to expand...
Click to collapse
Someone else encountered this with 15 Second installer. Are you running Win10? What flavor (pro, home, etc)? At what point exactly is "Access Denied" displayed with version 1.4.2?
Also, do you have folder, C:\adb or C:\users\username\adb? If yes, what files are in it?
Please let me know these things so I can try to find a fix. EDIT: @MRDirtyPixels I'll post how to update the driver when you reply. Thanks!

Fire HD 6 on 4.5.3
Win7 Ultimate x64
I'm having an issue at "Apply update from ADB". I do not have this option in recovery - only "Reboot your Fire", and "Reset to Factory Defaults".
I've had ADB drivers installed from past projects. Tried it, got this issue. Went back and installed the ADB drivers from the 15 second installer to see if that helped, still have this issue.
Also, at no point is my Fire listed under "Other Devices" - I don't even have that listed as a category. The Fire is always listed under "Android Device" > "Android Composite ADB Interface", so I figured my drivers were all set.
Any ideas would be greatly appreciated.
**EDIT: Should I somehow remove/uninstall all ADB related drivers and software and try again?

You use sideload mode to downgrade to 4.5.3 from OS 5. (It's only an OS 5 recovery option.) Since you're on 4.5.3, presumably with OTA blocked, you don't need sideload. Sounds like your drivers set up right for OS mode. Go root!
EDIT: @jiznon Be sure OTA is blocked. Else you'll OTA update as soon as you turn on wifi to root!

DoLooper said:
You use sideload mode to downgrade to 4.5.3 from OS 5. (It's only an OS 5 recovery option.) Since you're on 4.5.3, presumably with OTA blocked, you don't need sideload. Sounds like your drivers set up right for OS mode. Go root!
EDIT: @jiznon Be sure OTA is blocked. Else you'll OTA update as soon as you turn on wifi to root!
Click to expand...
Click to collapse
Oh, great! I may have overlapped a guide or two. Thanks so much!
I managed to turn airplane mode earlier as the OTA began to download. Should be good, ya?

jiznon said:
I managed to turn airplane mode earlier as the OTA began to download. Should be good, ya?
Click to expand...
Click to collapse
NO! you'll have to turn it off and use wifi to root. Run these commands:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier

DoLooper said:
NO! you'll have to turn it off and use wifi to root. Run these commands:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier
Click to expand...
Click to collapse
I see. That step isn't for sometime in the guide I'm following (it also states to install sideload drivers). Maybe it should be edited.
http://forum.xda-developers.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408/

jiznon said:
I see. That step isn't for sometime in the guide I'm following (it also states to install sideload drivers). Maybe it should be edited.
http://forum.xda-developers.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408/
Click to expand...
Click to collapse
Well, it's the step you do before turning on wifi to root. Notice that first step says that if you're on 4.5.3, get kingroot and go to step 6. So you're right there, at step 6.

jiznon said:
. . . (it also states to install sideload drivers). Maybe it should be edited. http://forum.xda-developers.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408/
Click to expand...
Click to collapse
Yes, I see I introduced some confusing info about drivers/versions in last update. I'll fix. thanks.

DoLooper said:
NO! you'll have to turn it off and use wifi to root. Run these commands:
adb shell pm block com.amazon.dcp
adb shell pm block com.amazon.otaverifier
Click to expand...
Click to collapse
DoLooper said:
Well, it's the step you do before turning on wifi to root. Notice that first step says that if you're on 4.5.3, get kingroot and go to step 6. So you're right there, at step 6.
Click to expand...
Click to collapse
Right. I'm still at "Before You Begin:
Install adb device drivers if you don't have them.
Here's an illustrated guide for Windows drivers. Install driver for both OS mode and sideload mode."
Wanted to make sure I don't miss anything. Looks like I'm on the right track. Thanks!
**EDIT: Everything went smooth. Thanks everyone!

Hi DoLooper, I'm currently following your [Root] OS 4, 5.0.n and Install Lollipop & Gapps ("Newbie Friendly") guide to root and update a Fire HD 7 and that's how I got here. I have successfully completed this guide, but only after I solved a problem that I ran into along the way. I solved it myself, so I want to share how I did it.
I had a Samsung phone before, had Samsung Kies (bringing along drivers) and "Minimal ADB and Fastboot" installed. I had removed all of these and all traces of them I could find. But when I got to step 4 of your first post in this guide, it always asked whether I wanted to install a driver with the name "Google, Inc. SAMSUNG Android Phone". I was worried the driver might be set wrongly in some way and I would brick my Fire tablet during the rooting process because of that (possible?). I continued anyway and after the driver installation finished, it didn't refer to the Fire as a Samsung device in the device manager anymore and the other steps in this guide were successful as well. So I guess I'm safe now.
However, I do have to add that when the Samsung drivers from Kies were still installed (I forgot about them at first), the device manager did refer to the Fire as a Samsung even after step 4. So I guess the moral is that you have to clean your system of other Android drivers/software thoroughly and restart first - and only then begin the procedure described in this guide.
Last but not least, thank you very much for spelling everything out step by step, it all seems like a doable task now.

podikan said:
. . .
I had a Samsung phone before, had Samsung Kies (bringing along drivers) and "Minimal ADB and Fastboot" installed. I had removed all of these and all traces of them I could find. But when I got to step 4 of your first post in this guide, it always asked whether I wanted to install a driver with the name "Google, Inc. SAMSUNG Android Phone". I was worried the driver might be set wrongly in some way and I would brick my Fire tablet during the rooting process because of that (possible?). I continued anyway and after the driver installation finished, it didn't refer to the Fire as a Samsung device in the device manager anymore and the other steps in this guide were successful as well. So I guess I'm safe now.
However, I do have to add that when the Samsung drivers from Kies were still installed (I forgot about them at first), the device manager did refer to the Fire as a Samsung even after step 4. So I guess the moral is that you have to clean your system of other Android drivers/software thoroughly and restart first - and only then begin the procedure described in this guide.
Click to expand...
Click to collapse
This is helpful and I'd like to add it, but I'm a little confused. Step 4 is just installing the 15-second Installer software. I don't think it asks anything. Could you please clarify the step where you got that prompt? Also, when it was listed under Samsung, you were able to right-clicking and choose Update and install the google drivers, right? Thanks.

Well, at the end of step 3 the program 15 Second ADB asks "Do you want to install device drivers?" and then a windows prompt appears. This is when I got the following prompt on top of that (only have it in German, sry): imageshack.com/a/img911/8983/bBg2q0.jpg I assume it's some kind of driver, as 15 Second ADB calls it. Is it really specific to a device?
As for your second question, if I remember correctly I was able to do that (I had to dig for it like you explain in step 9 after ". . . If Android Device is not listed, look here."). But afterwards it was still displayed as a (fully installed) Samsung portable device in my device manager. No chance I would go ahead and root from there. That's when I found and removed the Samsung drivers which came with Kies, rebooted, and started the procedure from the beginning.

ADB not cooperating
Ok. I am on a Fire HD 7 Gen 4 at OS 5.1.1, and attempting to downgrade to 4.5.3 for rooting purposes. (My eventual goal is to get CyanogenMod or another 'pure android' ROM on it, if you can help with that, great) When in sideload mode, Windows doesn't detect my device at all (no KFARWI or any other 6-letter combo) but ADB can detect it in both sideload and OS mode. My problem is this: Whenever I attempt to flash a .bin stock recovery, adb stalls for about a second, while on my Fire I only see:
Now send the package you want to apply to the device with "adb sideload <filename>"
Finding update package...
Opening update package...
Verifying update package...
before the device reboots. On adb I then see: "failed to read command: connection reset by peer" Any subsequent attempts without a manual reboot into sideload mode just instantly time out. I have a feeling this has something to do with the weird reboot, but how do I prevent it?

DoLooper said:
Install ADB Driver for Sideload Mode
Windows can’t recognize the Fire in sideload mode until you install the driver for it.
Note: These steps are pretty much identical to Post #1. Refer there for illustrations.
1. Connect the tablet to the computer and put it into sideload mode, like this: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.
To reboot to recovery:
- From CMD window, run: adb reboot recovery
or
- Manual: (a) Power off the Fire. (b) Hold the power and volume-up buttons until Amazon logo appears, then let go.​
2. Open Device Manager, find KFARWI under Other Devices, right-click it and select Update Driver Software.
If you don't see KFARWI under "Other Devices," see hidden text.
When KFARWI isn't under Other Devices, first be sure you "clicked" Apply Update from ADB on tablet to get into sideload mode.
If you did, see if "Android Device" is listed at top of Device Manager with a driver under it.
If Android Device is not listed, unplug/replug the tablet and see if KFARWI shows up under Other Devices. If it does, go to step 3. If it doesn't, post the problem.
If Android Device is listed, open CMD window in folder containing adb.exe and run adb devices command
- If adb devices returns an ID, this driver is working and you don’t need to install a different one.
- If adb devices does not return an ID, in Device Manager, right-click the driver, select Update Driver Software and go to Step 4.
3. Press Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.
[See “Select your device’s type”]
4. Click Android Device.
[See "Select the device driver you want . . .”]
5. Select the same driver you use for “normal” OS mode (post #1, step 10) and press Next.
6. Click Yes at warning screen.
Driver is updated!
7. In CMD window, run adb devices command and confirm you see your device ID and "sideload," like this:
8. DONE! Issue the sideload command or reboot to exit sideload mode.
Note (shouldn't happen, but . . . ) If you don't get a device ID and you had a driver installed at step 2 and updated it, you'll have to uninstall the driver.
In Device Manager, right-click and uninstall the driver under Android Device.
Restart computer and reboot tablet (to get out of sideload).
Go into sideload mode, right-click KFARWI under Other Devices and see if it has Update Software option.
- If YES, update the driver.
- If NO, reboot once more and go into sideload and you'll have Update option. Update the driver.
Click to expand...
Click to collapse
thank you

[GUIDE] Bypass FRP Tested on 6.0

Hi All,
After seeming that I'm locked out of my own device for 72 hours, I managed to scour the net and use parts of other tutorials to successfully bypass the "you're device was reset, please log in" loop.
So I should point out I was running a Pure Nexus rom running 6.0 with a custom recovery, you're results may differ but you've got nothing to loose.
Pre Requisite
ADB and Fastboot - You don't need to spend an hour installing the whole kit, just visit http://developer.android.com/sdk/index.html and scroll right down to the section where it says "SDK Tools Only" and click on "installer_r24.4.1-windows.exe"
Once installed the SDK manager will open, now make sure the top 3 are checked which are:
Android SDK Tools
Android SDK Platform-tools
Android SDK Build-tools
And also scroll down in the list to find Google USB Driver
Once all of that is done download the latest Google USB drivers (although the SDK installs USB drivers it still shown an exclamation mark in device manager") http://developer.android.com/sdk/win-usb.html
To install those USB drivers just go into device manager and if you se Nexus 6 under "Other Devices" just right click and click update driver software and then click browse my computer and get it to scan the Google USB driver folder you downloaded.
restart your phone into recovery (Volume Down and Power button)
now again in device manager make sure the Nexus 6 doesn't have a yellow icon identifying there's a problem with drivers or that the nexus 6 is listed in other devices. If either of those are present right click and update drivers > browse from computer and select the Google USB drivers you downloaded previously.
Bypass FRP
With all that confirmed restart your Nexus and leave it on the Welcome screen.
Now, you need to get into platform tools which is located:
C:\Users\YOURUSERNAME\AppData\Local\Android\android-sdk\platform-tools
if you can't see AppData you need to enable hidden files and folders
once in platform tools hold SHIFT and right click any blank space and click "Open command window here"
then type "adb devices" and it should list your nexus under devices, if it doesn't open device manager and check your drivers.
If it does show your nexus execute this command which edited from another source:
"adb shell am start -n com.android.settings/.Settings"
Your nexus will now open the settings menu =] in settings go to "Backup & reset" then click "Factory data reset" (although it says it wipes user data, mine was untouched, I can't say the same for so you may lose some data if you proceed)
your phone will reboot and in my case it opened my custom recovery and executed a script, the phone will restart again and go to boot, hold the power button to force shut down the nexus and boot into recovery mode. In recovery mode flash a ROM, if you don't have a ROM download one on your PC and then connect your Nexus to your PC via USB and copy it over.
Once the ROM is installed you won't get the "you're device was reset" screen.
"

You left out some key details which are covered in the guide I wrote up a few days ago. Here's the link.
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk

this does not work, because in order to adb devices to populate anything you would of had to enable usb debugging from within the phone, and if you're locked our from FRP, you cant access the settings to turn on the usb debugging

Bootloader LOCKED .. and asking for gmail ID ??

Help!! trying to root

Im trying to root and I get to bootloader. But I go to update drivers in device manager and it fails every time. what am i not doing?

As i was going through the same trouble yesterday i ll try to help you
Follow everything of this guide depending on your shield tv model :
2015 :
http://nvidiashieldzone.com/shield-.../tutorial-root-shield-android-tv-16gb-nougat/
or 2017 :
http://nvidiashieldzone.com/shield-...rial-root-shield-android-tv-2017-16gb-nougat/
Make sure you are using a micro usb cable that works well with other android devices (i got many problems just because of the cable especially to get the adb and fastboot to see the device )

You have to go in to device manager on PC and find the yellow exclamation and manually point it to the driver's that you'll download. The key is to point your PC to the good driver's.

yep.. and still says windows is unable to install fasboot.

i bet you have 16gb 2017 model right? if so read the following to fix it:
https://forum.xda-developers.com/sh...-sheild-root-status-faq-t3542005/post70773777
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ DroidMote user ~ Full Android for Shield TV and Nexus Player

ewimbe said:
yep.. and still says windows is unable to install fasboot.
Click to expand...
Click to collapse
You have to manually select "I want to choose from a list.... " and then browse to the android_winusb.inf file, then select "Android Bootloader Interface"

mr-tee said:
You have to manually select "I want to choose from a list.... " and then browse to the android_winusb.inf file, then select "Android Bootloader Interface"
Click to expand...
Click to collapse
Thank you all. It worked and got root. Wanna try to put full android on now