Now I know your first thought “I bet this tool didn’t even use Search like the rest of the shlubs on here”. Well you are mistaken. I have not only searched xda but even tried Google and Yahoo (just in case) as well. I have found numerous posts (like HERE and HERE and many others) with similar situations but haven’t seen a resolution. Here is the rundown:
Running JF’s 1.5 CRB21 ROM
Hard SPL (HSPL10.95.3000)
JF’s 1.43 Recovery Image
SDK 1.5_r1
Fastboot.exe placed in System32
Haykuro’s Updated Drivers placed in System32
Windows XP 2002 SP3
I have been able to flash nandroid backups without issue in the past but adb started intermittently not recognizing my phone when I flashed from JF’s RC33 to JF’s 1.5. I was able to restore a backup once but now adb will not recognize my phone at ALL. Tried different USB plugs and cables with no result. If I mount the phone to view the SD card via Windows Explorer it shows as “HTC Dream Composite ADB Interface” in Device Manager. However if I boot into the Bootloader (which I have the Hard SPL HSPL10.95.3000) , connect via USB, hit back to go into Fastboot, and try to flash a nandroid backup I get "Waiting on Device" infinitely. “Adb shell” yields “Device Not Found”. The "adb devices" command yields a blank list. But if I type "Fastboot Reboot" it will reboot the phone so I know it is communicating and the cable is in good order. I have deleted my SDK and drivers and re-downloaded/installed them and STILL cannot get adb to connect. It has to be something simple I am missing here right? Any idea why this would have worked without issue in the past and now not at all? Could it have been a Windows Security update? (That's about the only thing I can thing that has changed other than the newer ROM)
Thank you for your help.
Did you update you USB Drivers or try reloading them?
Also.... Settings > Applications > Development > USB debugging has to be checked....
and stop being a tool.
nah im jk.
USB Debugging is checked - thanks Senorkabob for at least trying to help.
Phoenix - I apologize for posting in the wrong place. If I could move it, I would. I apparently missed the "How to be a Good Xda Citizen" thread... I shall repent
Could you choose View -> "Devices by Connections" in Device Manager and uninstall the USB Root Hub device your android is connected to. This should clean up all the device nodes and allow you a clean start. Click "Scan for hardware changes" in the toolbar and wait for the system to detect your phone. In the new hardware detected wizard, make sure you specify the path to drivers folder of the correct architecture, i.e. x86 or x64.
gPhunk said:
USB Debugging is checked - thanks Senorkabob for at least trying to help.
Phoenix - I apologize for posting in the wrong place. If I could move it, I would. I apparently missed the "How to be a Good Xda Citizen" thread... I shall repent
Click to expand...
Click to collapse
Repent .. Repent..
Did reloading the USB Driver work?.. Did for me =)
billc.cn said:
Could you choose View -> "Devices by Connections" in Device Manager and uninstall the USB Root Hub device your android is connected to. This should clean up all the device nodes and allow you a clean start. Click "Scan for hardware changes" in the toolbar and wait for the system to detect your phone. In the new hardware detected wizard, make sure you specify the path to drivers folder of the correct architecture, i.e. x86 or x64.
Click to expand...
Click to collapse
How do I know which one to install? (I am running Vista Home Premium 32bit)
Thank you for your help
Use the x86 drivers. Also try installing them in safe mode. That made it work for me
ubernicholi said:
Use the x86 drivers. Also try installing them in safe mode. That made it work for me
Click to expand...
Click to collapse
Thanks man - I was able to install the drivers but am still unable to view my device. It shows as "HTC Dream" in Device Manager but when I run "adb devices" in the command line, it yields a blank list. Further commands (I.e. adb shell) say "cannot find device. Running fastboot commands result in "waiting on device". This happens on both my laptop and my home pc so I am beginning to think it's the phone. Should I have something loaded on the phone? I have USB Debugging checked so that's not it. Any ideas?
possibly the problem is that ADB does not work in Bootloader mode, it is designed to work while the phone is running.
However if I boot into the Bootloader (which I have the Hard SPL HSPL10.95.3000) , connect via USB, hit back to go into Fastboot, and try to flash a nandroid backup I get "Waiting on Device" infinitely. “Adb shell” yields “Device Not Found”. The "adb devices" command yields a blank list. But if I type "Fastboot Reboot" it will reboot the phone so I know it is communicating and the cable is in good order.
Click to expand...
Click to collapse
Yuo are obviously trying this in bootloader mode, underline for emphasis.
try >fastboot devices
see if that shows you your phone
Otherwise try ADB while in the OS already.
➜ 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
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.
Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.
Following
I have the same error and like to follow
Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.
No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.
Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.