Database Users

Rooting Kindle Fire and ADB

I'm trying to root a Kindle Fire and I don't know why but I'm having alot of trouble getting ADB and drivers set up right on my laptop. I'm not sure which packages I need to install in SDK manager. When I try to use the adb command at a command prompt it says command not recognized and I'm thinking it's because I don't have the right packages installed or installed right.I didn't have to go through this when rooting a couple other phones I've done.

http://forum.xda-developers.com/showthread.php?t=1399889

Thanks so much for the link. I ran it and I'm having a hard time getting it to recognize the device. It said it installed the correct drivers but when I attempt the temp root it will not recognize the device, make sure device is plugged in and turned on.

With kindle unplugged Go into ur comps device manager and remove the kindle fire...then install drivers. Then plug it back in. I had same problem. Windows auto installed some generic driver when I first plugged it in before installing correct driver. If still not working try a diff usb port on computer. Hope that helps

I finally got it. Thanks very much. I finally had to switch computers for some reason to get it to work.

[Q] Problem...Recovery with no ROM to flash or USB recognition

Hi XDA. I have a problem and could use your help.
In order to make flashing ROM’s easier for myself I thought it would be a good idea to place them in the first folder listed on the internal sd card. In order to do this I placed a “.” befor the name of the folder. After wiping everything I learned CWM 5.8.1.8 (touch) does not see folders with dots(“.”) at the beginning. So I now am in recovery with no ROM to flash
I then proceeded to dig an even deeper hole for myself. In my attempts to install drivers for my device I have done something; now my computer fails to recognize that the device is plugged into the USB at all. Prior to my messing with it I would hear the USB input chime and Device Manager would show an “unknown device”. Now when I plug in my device nothing happens. I have tried two computers and both Win7 and Ubuntu.
I read that Linux might be able to see my device so I installed Ubuntu then the Android SDK as per this thread. It did not work for me. I still cannot see my tf101 but I can see my Nexus s with the “adb devices” command.
I bought my tf101 refurbished and can’t find the “B” version written on the device. I think I initially rooted with razorclaw...not %100 sure. I am not sure adb debugging was checked when I wiped...not sure it makes a difference at this point.
I am now looking at these NvFlash instructions but I can’t get past the 2nd step (I am a noob...obviously)
- run “./blobunpack recovery-clockwork-5.8.2.1-tf101.img” (Replace “recovery-clockwork-5.8.2.1-tf101.img” with the name of your downloaded file”)
Will this NvFlash tutorial work if the computer can’t see the device?
Any ideas?
Thanks for your time!

Try those steps from this website Reverting to Stock ROM (unroot and remove CWM recovery)
this is easier for you when u try to nvFlash your tf101. remember update driver, run as administrator on program

Thanks for the info!
I am away until tomorrow evening. I will try it then.

Hi,
I am still having problems.
Can I install drivers if the device is not listed in device manager? How?
Thanks again!

it will be reinstall or request when you unplug and plugin back your connect from tablet to PC
if your driver had been load or connected just go to Devices and Printers to check your connection, after that update your driver

Hi. Thanks for trying to help.
My problem is my computer is not seeing the device at all. No USB input chime. Nothing showing up in device manager. No nothing!
Could be the chord I guess but I don't think so. I was getting "unknown device" in device manager initially after I wiped the ROM. After attempts to install drivers I stopped getting any sign of the tf101 in device manager.

[Q] Computer not recognizing phone when in USB Debugging Mode

I am trying to install the ADB drivers but my phone is not appearing in the device manager at all for some reason. I have USB Debugging mode turned on but all that pops up when I plug my phone in is the auto play that asks me if I want to open the device to view files. I have no android device listed in my device manager to install drivers to. I have tried on two different computers and my phone is not recognized.
I have the google edition on 4.3

have you tried a different usb cable?

jedinegotiator said:
I am trying to install the ADB drivers but my phone is not appearing in the device manager at all for some reason. I have USB Debugging mode turned on but all that pops up when I plug my phone in is the auto play that asks me if I want to open the device to view files. I have no android device listed in my device manager to install drivers to. I have tried on two different computers and my phone is not recognized.
I have the google edition on 4.3
Click to expand...
Click to collapse
Uninstall and then reinstall Kies and try again bro, that should work bro.

Try a different cable. Had an issue was GNex where it charged fine, connected to the computer okay, but couldn't get adb or use odin. Spent hours trying to figure it out, uninstslling, reinstalling, and rebooting everything under the sun. Then thought maybe, just maybe it might be the cable. Swapped it out, and it worked like a charm.
Sent from my SCH-I545 using Tapatalk 4

Recovery mode, device not detected by Windows

ok, trying to follow the instructions to sideload the OTA update to kitkat here:
http://www.androidcentral.com/how-manually-update-your-nexus-tablet-kitkat
However, I am running into a problem with the recovery mode. it isn't seen by my PC. So adb cannot find my device to let me sideload the OTA.
adb sees my tablet when it is running normally, though. I was able to reboot into recovery using adb. It just lost the connection as soon as I was rebooted in recovery.
Does anyone know how to make windows see my tablet while it is in recovery mode?
Thanks,

brandonyoung said:
ok, trying to follow the instructions to sideload the OTA update to kitkat here:
http://www.androidcentral.com/how-manually-update-your-nexus-tablet-kitkat
However, I am running into a problem with the recovery mode. it isn't seen by my PC. So adb cannot find my device to let me sideload the OTA.
adb sees my tablet when it is running normally, though. I was able to reboot into recovery using adb. It just lost the connection as soon as I was rebooted in recovery.
Does anyone know how to make windows see my tablet while it is in recovery mode?
Thanks,
Click to expand...
Click to collapse
You need to pull up the recovery menu by clicking the power button and then clicking the volume up button and then letting go of both of them. then click the button that says something along the lines of sideloading an update via adb and then you're set to send the adb command. Be wary, however, I seemed to somehow brick my N10 earlier by doing this. I finally got it up and running (by what I'm calling luck) but it wasn't a fun hour.

sparkplugDev said:
You need to pull up the recovery menu by clicking the power button and then clicking the volume up button and then letting go of both of them. then click the button that says something along the lines of sideloading an update via adb and then you're set to send the adb command. Be wary, however, I seemed to somehow brick my N10 earlier by doing this. I finally got it up and running (by what I'm calling luck) but it wasn't a fun hour.
Click to expand...
Click to collapse
I can get to recovery, no problem there. I can select the option to sideload via adb. the problem is in Windows. Once my tablet is in recovery, the tablet is no longer seen by Windows, so the adb sideload command fails because it doesn't see the tablet is connected anymore,

brandonyoung said:
I can get to recovery, no problem there. I can select the option to sideload via adb. the problem is in Windows. Once my tablet is in recovery, the tablet is no longer seen by Windows, so the adb sideload command fails because it doesn't see the tablet is connected anymore,
Click to expand...
Click to collapse
I've heard that unplugging the device from the PC until you're in recovery mode might help. I would also suggest, if that doesn't work, to install the ADB drivers again once you're in recovery mode.

Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.

garysargent said:
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
Click to expand...
Click to collapse
When it is running, and usb debugging is enabled, it shows up under Android Phone as Android Composite ADB Interface.
I turn USB debugging off, and it shows up under Portable Devices as Nexus 10
I boot into the bootloader and it shows under Android Phone as Android Bootloader Interface.
but It doesn't show at all when I am in recovery

How are you connecting your N10 to your Windows machine? Are you using good USB cable? Are you using USB2 or USB3 port? Is the port attached to mobo directly, or is it on the case?
Some claim there can be issues with poor USB cables, using USB3 instead of USB2, or using port not directly on the mobo, so if you're doing any of those, I'd suggest trying a switch.
Also, I'm confused, has USB debugging on or off when you go into Recovery?

mevensen said:
How are you connecting your N10 to your Windows machine? Are you using good USB cable? Are you using USB2 or USB3 port? Is the port attached to mobo directly, or is it on the case?
Some claim there can be issues with poor USB cables, using USB3 instead of USB2, or using port not directly on the mobo, so if you're doing any of those, I'd suggest trying a switch.
Also, I'm confused, has USB debugging on or off when you go into Recovery?
Click to expand...
Click to collapse
I am connecting with a USB cable. I don't know if it is "good' or not, but it works with the tablet in all other modes. I was able to use adb to transfer files, reboot, etc. I was able to use fastboot to flash Chainfire's autoroot, and to flash the factory images.
I was using a USB2 port directly on my laptop, but I just tried the USB3 port and it didn't change anything.
Plugging it into my USB hub, and my hub did not detect that it was plugged in either while it was in recovery mode. It was detected when I rebooted back into the system.
USB debugging is on when I enter recovery. I used "adb reboot recovery" to reboot my tablet into the recovery mode

garysargent said:
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
Click to expand...
Click to collapse
Thank you !!!!!!!!!

my lenovo a6000 shot no display but detecting n device manager.
it occured due to flash flash.rec.
please help me.

ADB Connection mysteriously lost

All along ADB was working fine. Now when I enabled it, nothing is detected on the computer. The phone went entirely missing. If I turn it off, the phone comes back. Anyone encountered this?
With ADB turned off
- Phone works in PTP Mode to PC
- Phone works in MTP Mode to PC
- Phone works in MIDI to PC
With ADB turned on
- No phone device detected at all. So I am not even able to change to any of the ADB drivers

mobileman88 said:
All along ADB was working fine. Now when I enabled it, nothing is detected on the computer. The phone went entirely missing. If I turn it off, the phone comes back. Anyone encountered this?
With ADB turned off
- Phone works in PTP Mode to PC
- Phone works in MTP Mode to PC
- Phone works in MIDI to PC
With ADB turned on
- No phone device detected at all. So I am not even able to change to any of the ADB drivers
Click to expand...
Click to collapse
What do you mean by "ADB turned off" and "ADB turned on"?
Are you talking about USB Debug?
Sent from my interstellar 6P

CyberZeus1977 said:
What do you mean by "ADB turned off" and "ADB turned on"?
Are you talking about USB Debug?
Sent from my interstellar 6P
Click to expand...
Click to collapse
Yes, USB debug in development menu, even turning it on/off, revoke does not seem to make it work again. it just does not show up on my PC.

Further tests done.
Fastboot works.
Adb works in recovery mode when booted into TWRP 3.0.2-3.
Think I need a way to reset the ADB /usb debug settings within the phone as it looks more and more to be an issue from the phone rather than Windows (v7 x64 sp1)

mobileman88 said:
Further tests done.
Fastboot works.
Adb works in recovery mode when booted into TWRP 3.0.2-3.
Think I need a way to reset the ADB /usb debug settings within the phone as it looks more and more to be an issue from the phone rather than Windows (v7 x64 sp1)
Click to expand...
Click to collapse
Not the way I read it. Sounds to me like the exact opposite.... a driver issue with your PC/OS, not the phone. In order for the phone to have adb/fastboot capabilities, the correct drivers need to be installed and actually working on the PC. Without going into detail, you could use a few different tools to REMOVE and install the correct PC drivers. Wug's NRT Toolkit has a very good step-by-step driver configuration guide with verification. I now just use the 15 second ADB installer here on XDA because it is minimalist, and just works. That being said, the NRT has a USB removal tool to rid your system of old USB entries that are likely causing your problem. Give it a whirl.

v12xke said:
Not the way I read it. Sounds to me like the exact opposite.... a driver issue with your PC/OS, not the phone. In order for the phone to have adb/fastboot capabilities, the correct drivers need to be installed and actually working on the PC. Without going into detail, you could use a few different tools to REMOVE and install the correct PC drivers. Wug's NRT Toolkit has a very good step-by-step driver configuration guide with verification. I now just use the 15 second ADB installer here on XDA because it is minimalist, and just works. That being said, the NRT has a USB removal tool to rid your system of old USB entries that are likely causing your problem. Give it a whirl.
Click to expand...
Click to collapse
Shall give it a whirl. Previously it was incorrect driver issue years ago but everything has been working fine on all my Android devices till yesterday when I can't seem to ADB to my 6P. I have the latest USB drivers installed via Android SDK Manager.

v12xke said:
Not the way I read it. Sounds to me like the exact opposite.... a driver issue with your PC/OS, not the phone. In order for the phone to have adb/fastboot capabilities, the correct drivers need to be installed and actually working on the PC. Without going into detail, you could use a few different tools to REMOVE and install the correct PC drivers. Wug's NRT Toolkit has a very good step-by-step driver configuration guide with verification. I now just use the 15 second ADB installer here on XDA because it is minimalist, and just works. That being said, the NRT has a USB removal tool to rid your system of old USB entries that are likely causing your problem. Give it a whirl.
Click to expand...
Click to collapse
Still no go. There's no device at all where I need to change/delete/update driver if I turn on ADB USB mode. Phone is only seen by Windows Device Manager when I turn off USB debugging in developer menu. I still feel it might well be something in the developer menu causing this issue.
I am checking on the folder /data/misc/adb . Permissions is rwxr-s--- . What's the permissions you have for this folder?
Using USBDeview (trying to compare between 2 sets of 6P, both with the December 7.1.1 roms)
6P that works over ADB
Reported VID and PID is 18d1 / 4ee2
6P that does not work over ADB
Reported VID and PID is 18d1 and PID is 4ee1, 4ee5 and 4ee8 depending on which mode (PTP/MTP/MIDI).
Nothing gets reported to be connected at all when I used USBDeview while the 6P that does not connect over ADB USB has USB debugging turned on.

Problem fixed. No idea what was the cause. Hopefully it will help someone else who gets this down the road.
Steps performed
- Clean up SU
- Reboot
- No go
- Reboot to Recovery
- Reflash EFS backup
- Reboot
- No go
- Reboot to recovery
- Clear cache, clear dalvik
- Reboot
- No go
- Reboot to fastboot
- Reflash System, Vendor, Boot
- Reboot
- Works
- Reflash Magisk and PHH
- Still works
Puzzling.

Glad you got it fixed.

v12xke said:
Glad you got it fixed.
Click to expand...
Click to collapse
Yeah, would have done a full factory reset if all else fails since the hardware was indeed able to connect to my PC properly. Glad the various flashing worked out.