Device not detected in adb or fastboot - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Hi, my device (tate) cannot connect to any of my computers in adb or fastboot modes, rendering me unable to transfer any files onto my device. However, I am able to perfectly boot into TWRP recovery. The ROM I previously flashed didn't work, and I had already factory reset the device without making a backup. How can I now transfer a working ROM given my problems in adb?
OS: Windows 8 x64 (failed to install the KFHD adb drivers)
Upon command 'adb devices' or 'adb usb': 'no device found'
Upon command 'fastboot -i 0x1949 getvar product': nothing happens

You need to install the drivers while in twrp/fastboot. I would recommend just using adb to push the ROM onto the sdcard from twrp. You will need to fix your drivers first though, to do that you need to disable windows driver signature enforcement, look it up on Google. Then download the drivers in my signature and update the drivers for the device with a triangle in the device manager and point then to where you extracted the drivers. Then try adb again while in twrp.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Disable device driver signature enforcement.
Both must be done from the administrator profile to work right.
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue.
A.
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."
Note: This must be done on every bootup you want to install something not MS signed.
B. For a more permanent solution.
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now copy these in the command prompt one at a time hitting enter after each one.
bcdedit /set testsigning on
bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers next time. Following steps 1, 2 and 3 in part B of tutorial enter these commands
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
Since I don't have Windows 8 to do a personal tutorial, I'll just link to a good tutorial for that http://www.fotoclubinc.com/blog/how...on-of-windows-7-printer-drivers-on-windows-8/
---------- Post added at 10:18 PM ---------- Previous post was at 09:55 PM ----------
chemicalrubber said:
Hi, my device (tate) cannot connect to any of my computers in adb or fastboot modes, rendering me unable to transfer any files onto my device. However, I am able to perfectly boot into TWRP recovery. The ROM I previously flashed didn't work, and I had already factory reset the device without making a backup. How can I now transfer a working ROM given my problems in adb?
OS: Windows 8 x64 (failed to install the KFHD adb drivers)
Upon command 'adb devices' or 'adb usb': 'no device found'
Upon command 'fastboot -i 0x1949 getvar product': nothing happens
Click to expand...
Click to collapse
You need to push a ROM onto TWRP using this tutorial http://forum.xda-developers.com/showthread.php?t=2459498 Also disable drivers via my post above this post. Lastly, make sure to use Hashcodes crackflasher mirro as TWRP is still messed up making goo.img zip file downloads a mere shell that fail to flash. Make sure to have the most up to date TWRP as well http://forum.xda-developers.com/showthread.php?t=2128848

Thanks stunts and Linearequation! Disabling driver signature enforcement was the crucial step. Adb now works perfectly in recovery!

chemicalrubber said:
Thanks stunts and Linearequation! Disabling driver signature enforcement was the crucial step. Adb now works perfectly in recovery!
Click to expand...
Click to collapse
You're welcome. To clarify my post, TWRP works fine, goo,.img is causing some corrupted downloads yet.
Sent from my Amazon Kindle Fire HD running CM 11 KitKat 4.4 using xda app-developers

Related

help with fastboot

I need to get fastboot working to flash the 2708+ radio/hboot combo, for a rom I want to try. No devices show up under fastboot devices (from command prompt), but it does show up under adb devices. I don't have sdk properly installed, for some reason it wont take on my pc. It was a lengthy process getting adb to work a few months ago, I don't even remember what I did. Please help.
make certain the phone is in fastboot and not hboot mode by hitting the back button
you can flash the radio in recovery,attention it has chance to be bricked.
Ok i just recently installed adb for the same reason, i had trouble at first but then i found this video which made everything really easy.
http://www.youtube.com/watch?v=Bg-cGTZE2XI&feature=related
Now adb works on my computer perfectly
once u install adb fastboot is already there, all u have to do is install the correct drivers for fastboot. So this is what you do:
1. turn off your phone and then turn it back on using the back and home button
(this will boot you into bootloader)
2. Now it should some information and it should say FASTBOOT in green letters.
3. If it does, now plugin your usb to your phone and computer and now it will say FASTBOOT USB.
4. NOw that your phone is in fastboot, go to command prompt on your pc to lauch fastboot.
5.If you installed adb using the video above, type cd..
6. again type cd..
7. then type cd android
8. last type cd tools
9. To check if your phone is connected to your computer through fastboot, type fastboot devices.
10. It should show a long number and then connected, this is your device, if it doesnt show this u need to install the correct drivers for fastboot, if it does show your device then fastboot is working and you can use it.
11.If its not working, you need to install the correct drivers.
12. Keep your phone in FASTBOOT USB, Just leave it how it is.
13. Now on your pc, go to start.
14. right click on computer
15. click on properties.
16. click on device manager
17. now find your device, since it doesnt have the correct drivers it should be under other devices.
18. once you find it double click on it.
19. click update drivers, and choose the option that lets you choose the drivers.
20. your pc wiil scan for drivers and if you installed adb correctly, their should be adb interface drivers.
21. choose those drivers.
22. now wait for those drivers to install.
23. ANd there now u have the correct drivers for fastboot!
24. to check if it is working repeat steps 4-9
25. IF it does, You now have fastboot working on both your pc and device!
please hit the "thank you" button

[Quick Tutorial] Getting into Fastboot

In this guide I'm going to assume you know how to get SDK working. Here's the video if you don't: http://www.youtube.com/watch?v=oaNM-lt_aHw
This is in reference to Hascode's guide http://forum.xda-developers.com/showthread.php?t=2128175]
for steps 4.5 AND BEYOND or if you just want to enter Fastboot for yourself.
1. Download this: https://dl.dropbox.com/u/54456659/KFFirstAide64.zip (64 bit) OR https://dl.dropbox.com/u/54456659/KFFirstAide32.zip (32 bit)
Latest version of Java: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
Source: prokennexusa
2. Extract it to your C Drive (or primary), keep the folder name the same KFFirst AIDE (Do not change it)
3. Make a Path to that folder, as shown in the video. Instead you will put ;C:\KFFirstAide
4. Download Hashcode's files and place them in that FirstAide Folder.
5. Before going further, uninstall any previous drivers for the Kindle in Control Panel and Device Manager.
6. Install ADB Drivers found within KFFirstAide -> KindleADB
7. Open up RunMe.bat and run option 11 to verify ADB is working.
8. Now run option 15 to boot into Fastboot, it may take a min.
9. Once in Fastboot, open Device Manager and update the driver, browse to C: -> Program Files -> Amazon -> Drivers -> WinUSB
10. Open CMD and type in cd C:\KFFirstAide
11. Now type in Hashcode's Fastboot lines and it should run (you can verify this because the files pushed will also show up on your Kindle)
NOTE: It's important that you do not have any ADB or Kindle drivers installed prior to installing the one in the FirstAide folder (Check Device Manager)
If you have questions, post a comment down below and I will try to answer them.
Fixed Links. Working Now.
I need some help! I was using KFFristaide64 with my 8.9 KFHD. I was trying to flash to the 8.1.2, option 5, and it flashed the boot, recovery and system, them hung at deleting user data for about 2 hours. When it finally rebooted the kindle screen never comes on, and windows emits the beeps it uses to notify a usb device attachment and removal back to back to back, and the kindle never shows up in windows or ADB. I have tried to get into fastboot with option 15 and 16 using a standard and factory USB cable, but no combination will bring up fast boot, just get the cycling connection/disconnect sounds from windows. Does anyone know if there is a way to recover from this? I have a full back up (all 11 partitions) that I created just before starting. My device was rooted before I began, but I have no clue where in the process it would be now. Can anyone help, or should I just start looking for a new 8.9 KFHD?
Whenever I try to run step 6 of this, the installer tells me that it's failed and that I need to install the drivers manually. Doing that doesn't change anything, I still get the Kindle in the device manager with the exclamation point telling me that drivers have not been installed. I've removed everything from device manager/control panel before I run it.

[Q] Stuck in boot loop, have fastboot cable?

I tried installing a second bootloader with Fireflash, and apparently I missed a step. This led to my Kindle being stuck in a bootloop. I bought a fastboot cable from ebay, which arrived today. When I connect with that cable, the logo changes to the fastboot logo, but anything I try with the KFHD System.img Restore Tool doesn't work, neither does Kindle FirstAide.
With KFHD System.img Restore Tool, I always get < waiting for device >.
I'm not sure what to do now, can anyone suggest anything?
You need to install the drivers for the device, open your task manager and hit update driver on the Tate device with a triangle next to it, and download the drivers in my signature, then after extracting them, poi t the update drivers wizard to the place you extracted the drivers to and let them install.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You need to install the drivers for the device, open your task manager and hit update driver on the Tate device with a triangle next to it, and download the drivers in my signature, then after extracting them, poi t the update drivers wizard to the place you extracted the drivers to and let them install.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I just tried that, and the wizard tells me that the hash is not present in the catalog file?
Ah your on windows 8, you need to first disable driver signature enforcement, Google it and then try again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Disable device driver signature enforcement -
Both must be done from the administrator profile to work right
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue
A.
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."
Note: This must be done on every bootup you want to install something not MS signed.
B. For a more permanent solution.
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now copy these in the command prompt one at a time hitting enter after each one.
bcdedit /set testsigning on
bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers next time. Following steps 1,2 and 3 in part B of tutorial, copy these commands in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set loadoptions
ENABLE_INTEGRITY_CHECKS bcdedit.exe -set TESTSIGNING OFF
Since I don't have Windows 8 to do a personal tutorial, I'll just link to a good tutorial for that.
http://www.fotoclubinc.com/blog/how...on-of-windows-7-printer-drivers-on-windows-8/

MTP device problem HTC One M7

Hello, i searched but i couldn'tfind any solution. I connect my phone to laptop(xp) by usb but laptop doesnt recognize my phone. It says mtp driver couldnt install. I found some mtp driver installed but didnt solved again.Someone can help me about that.
Sent from my HTC One using XDA Free mobile app
Any support?
Sent from my HTC One using XDA Free mobile app
forcible79 said:
Hello, i searched but i couldn'tfind any solution. I connect my phone to laptop(xp) by usb but laptop doesnt recognize my phone. It says mtp driver couldnt install. I found some mtp driver installed but didnt solved again.Someone can help me about that.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Check out this FAQ #2 to see if it will fix your issue.
There was just windows 7 and 8. İ am using windows XP. This solution doesnt work for wndows xp. Any different idea?
There was just windows 7 and 8. I am using windows XP. This solution doesnt work for wndows xp. Any different idea?
forcible79 said:
There was just windows 7 and 8. I am using windows XP. This solution doesnt work for wndows xp. Any different idea?
Click to expand...
Click to collapse
The steps are basically the save for XP, Win 7 and Win 8. Here are the HTC drivers for XP it is labeled 2K.
majmoz said:
The steps are basically the save for XP, Win 7 and Win 8. Here are the HTC drivers for XP it is labeled 2K.
Click to expand...
Click to collapse
Still i have same failure. Computer see nothing about my phone. I put jpeg about problem
forcible79 said:
Still i have same failure. Computer see nothing about my phone. I put jpeg about problem
Click to expand...
Click to collapse
Have you tried different ports? Cables? Computers?
You can try Linux on a USB and you don't have to install it on your computer, here how:
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219​Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
If you get "no permissions ?????????" when trying to use adb, type:
Code:
killall adb
Disconnect the phone for a few seconds, then reconnect and type:
Code:
sudo adb devices
adb should now work as normal without the sudo prefix.
Click to expand...
Click to collapse

can't install drivers on win7 or win10

i've tried all suggestions to install the drivers and when i connect my fire to my computer, it shows up as portable device > fire. if i try to update drivers, it says that i am already using the best one, the MTP usb device.
i've followed this:
http://forum.xda-developers.com/showpost.php?p=63072252&postcount=2
and also tried the drivers from amazon and neither allow me to select the adb driver.
You have turned adb on on the Fire?
Pond-life said:
You have turned adb on on the Fire?
Click to expand...
Click to collapse
thanks for the reply.
yes, i put it in dev mode by tapping the serial numbers and it is adb enabled.
ultraman69 said:
and also tried the drivers from amazon and neither allow me to select the adb driver.
Click to expand...
Click to collapse
What error message from windows are you getting when you select the ADB driver in device manager?
For Windows 10 in case it's an unsigned driver issue.
Post #84 linux VM solution if your absolutely hitting a wall.
i cannot select the adb drivers, when i try to manually select it, by going the the folder and clicking install, windows says i already have the best drivers installed. if i try to right click and install the inf, it says it is invalid for my computer.
i also have a macbook that i can try this on, are there instruction for a mac?
i'll take a look at the vm thing, but i have no idea about vm's.
thanks.
thekrakah said:
What error message from windows are you getting when you select the ADB driver in device manager?
For Windows 10 in case it's an unsigned driver issue.
Post #84 linux VM solution if your absolutely hitting a wall.
Click to expand...
Click to collapse
ultraman69 said:
i cannot select the adb drivers, when i try to manually select it, by going the the folder and clicking install, windows says i already have the best drivers installed. if i try to right click and install the inf, it says it is invalid for my computer.
i also have a macbook that i can try this on, are there instruction for a mac?
i'll take a look at the vm thing, but i have no idea about vm's.
thanks.
Click to expand...
Click to collapse
From the images you posted it looks like you should be able to at least poll your device using the windows version of adb, and start rooting. I'll presume you already have adb installed somewhere on your system, "c:\adb", or something like that.
You should be able to poll your Fire device serial number.
Open a command prompt as administrator, goto your adb directory. On the command line type the following.
adb start-server
adb devices
adb kill-server
On your fire device you should see a popup asking you to approve the USB connecting from xxxxxxx hardware id when you try to poll it.
If you get this far you can proceed with the root process for whichever version of Fire OS 5.x.x you have.
i tried that and polling comes up with nothing. after running adb devices, there is no popup on the fire and it lists nothing.
thekrakah said:
From the images you posted it looks like you should be able to at least poll your device using the windows version of adb, and start rooting. I'll presume you already have adb installed somewhere on your system, "c:\adb", or something like that.
You should be able to poll your Fire device serial number.
Open a command prompt as administrator, goto your adb directory. On the command line type the following.
adb start-server
adb devices
adb kill-server
On your fire device you should see a popup asking you to approve the USB connecting from xxxxxxx hardware id when you try to poll it.
If you get this far you can proceed with the root process for whichever version of Fire OS 5.x.x you have.
Click to expand...
Click to collapse
for some reason, on only one out 4 of my win 10 rigs, i had to turn off driver signature enforcement. to do this go to settings, update and security, recovery, advanced startup, restart now. then in the restart menu push, troubleshoot, advanced options, startup settings, then restart. when booted choose "Disable driver signature enforcement" (which is option 7 on current build). now try to install the drivers. after successful just do a normal restart to enable the signature enforcement again
ultraman69 said:
i tried that and polling comes up with nothing. after running adb devices, there is no popup on the fire and it lists nothing.
Click to expand...
Click to collapse
Can you verify that, "android debug" mode is turned on in the Fire devices developer settings? At least that was the only way I could reproduce the same message output from "adb devices".
I faut with my win 7 laptop for about an hour with one of my fires. Has the yellow icon on unknown device. Ended up "update driver" "browse for file" "let me choose from a list" picked Android/adb composite device. Adb and fast boot now work. I originally had to install Android studio and some extras to get my first fire to link up. Pm if you need help.
Sent from my Nexus 6P using Tapatalk
I recommend RootJunky tool, does everything and gives you instructions what to dohttp://www.rootjunky.com/amazon-fire-5th-gen-supertool/ Also recommend watching all his videos https://www.youtube.com/watch?v=sVv1D_LNLTg&feature=youtu.be

Categories

Resources