I have a factory cable, the adb and fastboot files from android sdk and the android adb composite interface drivers installed. I lost adb permissions on my kindle when updating twrp. If anyone has any idea why it isn't being detected please let me know. My computer itself recognizes it though.
Related
Trying to use Qemu to root a kindle fire hd but I'm not having any luck (adb device not found..." . The adb drivers are installed and the setting to allow adb is checked on the device itself. Is there anything I could possibly be doing wrong? Or is the tool not compatiable with the 7.15 update
this tool is fully compatible with 7.1.5 update.
You should re-check if adb drivers installed.
Then switch-on adb on kindle and be shure new device (smth like "android adb device") appear at your windows device manager.
Then you can start Qemu
kashei said:
this tool is fully compatible with 7.1.5 update.
You should re-check if adb drivers installed.
Then switch-on adb on kindle and be shure new device (smth like "android adb device") appear at your windows device manager.
Then you can start Qemu
Click to expand...
Click to collapse
Uninstalled and reinstalled several times, tried on windows 8 windows 7 and xp. no luck
I cant remember how I got mine to work. but after hooking it in i uninstalled the adb drivers and re installed to get it recognized
Any help with my problem would be greatly appreciated!
Recently I managed to soft brick my Kindle Fire HD 7", and hoped to use the "KFHD System.img Restore Tool" to fix. I bought a factory cable and was able to put my Kindle into fastboot mode. Prior to this I had ADB installed so I could root my KFHD (which I did).
Now obviously when I rooted my KFHD, ADB recognized my device then. Unfortunately, now I have no such luck. While in fastboot I tried to use the command ---> adb shell su -c "reboot bootloader" <--- but I kept getting error messages that stated there was no recognized device.
I re-installed the AndroidSDK file to ensure there were no errors there and tested ADB with successful results. I also re-installed the Device Drivers and made sure that in my device manager under Kindle Fire it said "Android ADB composite interface" (or similar, I don't remember off of the top of my head). I went back and tested again, and ADB still does not recognize my device while in fastboot. I then left my Kindle on until it ran out of battery to test to see if ADB would recognize when out of fastboot.
After turning on my Kindle when not in fastboot, I typed in the command prompt "adb devices" and no device showed up. Also, now under my device manager "Android ADB composite interface" or whatever doesn't even show up. I have searched over and over again on many forums with no luck. Does anyone know what I am doing wrong? Or what I should try doing?
Sorry for that ^huge story^ but thanks in advance for any feedback!
ADB and fastboot are completely different programs that work in completely different modes. And entering ’ adb shell su -c "reboot bootloader" ’ is pointless because (even if adb commands in fastboot were possible) fastboot mode is the "bootloader" part of the aforementioned command.
"That's a special kind of stupid. The kind that makes me laugh."
I have a similar problem with both linux and windows 8
I have a factory cable and the kindle is in fastboot mode
Under linux I just get a "waiting for fastboot" upon entering a command
Under windows I have an otter2-prod-04 device which I have no drivers for. I have tried the latest ADB composite drivers and the amazon kindle ones.
I'm pulling my hair out now, not only have I got into this situation that I need to restore but now find I cant!!
Any help, please....
Bryan
bryanchapman9999 said:
I have a similar problem with both linux and windows 8
I have a factory cable and the kindle is in fastboot mode
Under linux I just get a "waiting for fastboot" upon entering a command
Under windows I have an otter2-prod-04 device which I have no drivers for. I have tried the latest ADB composite drivers and the amazon kindle ones.
I'm pulling my hair out now, not only have I got into this situation that I need to restore but now find I cant!!
Any help, please....
Bryan
Click to expand...
Click to collapse
In Linux, you need udev rules set for adb and sometimes fastboot. And from what I've seen, Windows 8 is incompatible with the Android device drivers.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
In Linux, you need udev rules set for adb and sometimes fastboot. And from what I've seen, Windows 8 is incompatible with the Android device drivers.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Ive been using the android drivers on windows 8 without an issue. They have to be manually installed and driver signing needs to be turned off.
Sent from my KFOT using Tapatalk 2
soupmagnet said:
ADB and fastboot are completely different programs that work in completely different modes. And entering ’ adb shell su -c "reboot bootloader" ’ is pointless because (even if adb commands in fastboot were possible) fastboot mode is the "bootloader" part of the aforementioned command.
Click to expand...
Click to collapse
I see, well the program seemed to work fine without it apparently (the line of code). My Kindle is working perfectly again! Thank you for the reply.
I'm having issues getting adb and fastboot to work with my kindle fire hd 7in. When I plug it into my computer with a factory cable, my kindle goes into the fastboot screen, but neither adb nor fastboot can find it. One possible reason for this is that my kindle appears in device manager as "Android ADB Interface", not "Android Composite ADB Interface". Everything I can find in many different forums says that it is supposed to appear as "Android Composite ADB Interface". Is this actually a problem? And if so, how can I fix this? I tried uninstalling and reinstalling the drivers multiple times, but it still doesn't connect with adb.
http://forum.xda-developers.com/showthread.php?t=2162986
Hi,
I bricked my kindle after I accidentally used an app for a different Kindle. It boots up with the orange logo, then blue artifacts flash and it goes blank.
I purchased a Factory Cable from ScOrPn and it boots up into flashboot mode. At first, it installed the wrong driver entitled "adb interface device" or something. Adb wouldn't recognise it. I uninstalled the first driver, and I replaced it with a driver which had worked for me previously entitle "Adb composite interface device" <not exactly but it's the composite part that's important, I think. Anyway, I thought that would fix it but it doesn't. Adb doesn't recognise it so I can't unbrick it. Any help would be greatly appreciated.
Things that I have tried:
Installed composite interface driver
Kill-server
EDIT: Hi, after reading for several hours I installed KindleFireAide and it seems to be doing the job.
no adb recognition
Neither the standard cable works for kindle fire hd KFFA (kindle fire hd first aide) it does not find path since adb is not recognizing the unit and using homemade factory cable still does not recognize it . Unit starts system recovery and reboot but fail each time. KFFA path not found while running program. Any ideas?
Hello, I have an Kindle Fire HD 7 inch, which is in a boot-loop due to my failed experimentation with ROMs. I purchased a fastboot cable from amazon, and I can successfully boot in to fastboot mode. The problem lies when I try to access the device via fastboot.
When I first plugged the device in, running 'fastboot devices' returns no devices, so I installed the Google USB driver via the SDK Manager. Updating the driver, and rebooting the Kindle to fastboot mode was again unsuccessful. I tried this with 'Android ADB Interface' and 'Android Composite ADB Interface' So, after digging around on the Amazon website, I installed the Amazon Kindle Fire ADB Drivers, and tested both the included drivers, to no avail. Typing 'fastboot devices' returns an empty linespace, then the command exits.
I need to restore my Kindle to factory settings, as it will soon be my primary tablet device. Any help?
Thanks.