Database Develop

Kindle not found in adb & stuck

I realize there are dozens of similar threads but none so far has helped. I'll keep looking but in the mean time I thought I would try asking for advice.
I screwed up somehow attempting to root my Kindle HD 7". It was stuck in a loop returning to the "restore factory" screen w/ orange triangle every time. I bought a factory cable and the kindle is now in Fasboot mode.
However, every set of instructions I can find to take the next step of restoring the original firmware requires adb and/or fastboot to recognize the kindle. I cannot figure out how to get that to happen. Both fail to recognize it. I modified my adb_usb.ini file to add the line 0x1949 and I modified
sdk\extras\google\usb_driver\android_winusb.inf file to have the required hardware ids for the kindle (I tried the "stock" ids as well as the ids currently listed for the tablet in device manager). I added the sdk paths to my environmental variables. adb & fastboot commands work but neither finds the kindle.
Windows Vista is recognizing the kindle HD as Other Devices > Tate-PVT-08 but fails to load any drivers when it is first found (I get an error).
Any ideas?
Edit/update: I found a thread explaining how to force Windows to change the drivers. I forced it to change to the Android Sooner Composite ADB Driver and it is now listed as an ADB Interface device. still not recognized in adb though.
Another thing is that I am unable to update the drivers to use the adb kindle drivers. Windows simply reports that it "could not find driver software for your device".

Try the drivers in my SIG, they might do what yours already did though and not show up, but they should work if you update the driver to them. I am not a fan of vista, but I can think of several reason why u could be having issues offhand, like uac or driver signature enforcement, I believe driver signature enforcement was on vista, not positive though. Anyways try out my drivers and if that doesn't work maybe the command prompt isn't running with admin privis.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Your drivers were recognized and installed by Vista! Windows now sees it as an Android Phone > Android ADB Interface. Still no luck getting adb to find the kindle though. I think next I'm going to try deleting/uninstalling adb & the sdk and starting again. It isn't spelled out anywhere but I half suspect the paths are wrong somehow.
I can update to Windows 7 if there is any chance that would help.
Thanks for your help!
Michael
stunts513 said:
Try the drivers in my SIG, they might do what yours already did though and not show up, but they should work if you update the driver to them. I am not a fan of vista, but I can think of several reason why u could be having issues offhand, like uac or driver signature enforcement, I believe driver signature enforcement was on vista, not positive though. Anyways try out my drivers and if that doesn't work maybe the command prompt isn't running with admin privis.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse

Your device is listed as a Tate device correct? That is not going to work with adb because that means it is in fastboot. You can't use adb commands with fastboot. Try running "fastboot -i 0x1949 getvar product" and see if it reports anything back.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Yes, if I uninstall the device and let Windows Vista find it, it is listed as a Tate device. My kindle is indeed in fastboot (I have a factory cable). If I manually force it to switch drivers I can have windows list it as a ADB interface device.
Ahh, I tried fastboot -i 0x1949 getvar product and I get a response from the kindle!
So...I guess on to the next step! One of these 40 tabs I have open probably has something on flashing the rom.
Thanks all!
Michael
stunts513 said:
Your device is listed as a Tate device correct? That is not going to work with adb because that means it is in fastboot. You can't use adb commands with fastboot. Try running "fastboot -i 0x1949 getvar product" and see if it reports anything back.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse

MichaelBrock said:
I realize there are dozens of similar threads but none so far has helped. I'll keep looking but in the mean time I thought I would try asking for advice.
I screwed up somehow attempting to root my Kindle HD 7". It was stuck in a loop returning to the "restore factory" screen w/ orange triangle every time.
Click to expand...
Click to collapse
I know this is an old thread, but it seems to be the one most relevant to my problem.
I've got pretty much the same issue, but its because i was trying to install chainfire on my rooted kindle fire hd 7 (tate). Installation was taking longer than expected, actually thought my kindle had frozen so did a hard reset....big mistake as now it doesn't load past the kindle fire logo screen.
I bought a factory cable and the kindle is now in Fasboot mode.
Click to expand...
Click to collapse
Done the same, but when in fastboot, nothing.
However, every set of instructions I can find to take the next step of restoring the original firmware requires adb and/or fastboot to recognize the kindle. I cannot figure out how to get that to happen. Both fail to recognize it. I modified my adb_usb.ini file to add the line 0x1949 and I modified
sdk\extras\google\usb_driver\android_winusb.inf file to have the required hardware ids for the kindle (I tried the "stock" ids as well as the ids currently listed for the tablet in device manager). I added the sdk paths to my environmental variables. adb & fastboot commands work but neither finds the kindle.
Windows Vista is recognizing the kindle HD as Other Devices > Tate-PVT-08 but fails to load any drivers when it is first found (I get an error).
Any ideas?
Click to expand...
Click to collapse
This is pretty much where i'm at now, except on a windows 8 laptop, tried uninstalling everything related to my kindle, all adb, fastboot and sdk etc from my laptop before reinstalling and trying to update drivers but still not being recognised, did all the same things as above post, as been trying to sort this off and on for a while.
stunts513 said:
Try the drivers in my SIG, they might do what yours already did though and not show up, but they should work if you update the driver to them. I am not a fan of vista, but I can think of several reason why u could be having issues offhand, like uac or driver signature enforcement, I believe driver signature enforcement was on vista, not positive though. Anyways try out my drivers and if that doesn't work maybe the command prompt isn't running with admin privis.
Click to expand...
Click to collapse
I've tried to install the drivers from your sig but keep getting the message "the hash for this file is not present in the specified catalog file, the file is likely corrupt or been the victim of tampering" so i'm at a bit of a stand still at the minute.
stunts513 said:
Your device is listed as a Tate device correct? That is not going to work with adb because that means it is in fastboot. You can't use adb commands with fastboot. Try running "fastboot -i 0x1949 getvar product" and see if it reports anything back.
Click to expand...
Click to collapse
Any command i try use through fastboot just gives the <waiting for device> message with no response from my kindle. If either of you (or anyone else who reads this) can help it would be greatly appreciated.
EDIT: Got it recognised by windows finally, I opened "device manager", clicked "update driver software", "browse my computer for driver software" then "let me pick from a list of device drivers on my computer" where i found the right driver to enable fastboot to work and windows to recognise my tablet. Now to fix the damn thing.

Having same issue where my kindle isn't found in fastboot for some reason. When I type
Code:
fastboot -i 0x1949 getvar product
I get back Tate-PVT-08, but when i do fastboot devices I get nothing. I have Andoid ADB drivers installed and a factory cable. What is the problem?
Edit: Turns out i had to paste this in before everything -i 0x1949.

I'm glad this is a current topic again. I also need help. I've been running my rooted Kindle Fire HD 3d Gen going on two years now. I was using the firerooter to get it updated to 4.5.5 today and I'm pretty sure I bricked it--again. But this time I think I bricked it up real good.
I was doing this to hopefully get a recently updated game working again. But when it got hung up I freaked out for a second and made a mistake... I went ahead with a factory reset but then I realized that this would delete my game progress and I hadn't made a game backup before the update came on today so I was pretty much screwed in several ways.
Right, so when I was in the middle of the factory reset I was like... "****! I don't want to lose all my game progress!" and I immediately powered it down. And I immediately punched myself in the face after I turned it on and it did the lovely "kindle_fire" grey-scale initial load screen loop over and over. Based on what I've read, I'm pretty sure I've corrupted the bootloader or possibly deleted some boot partition.
I'm about sick of Amazon's bull****. They don't manager this part of their business very well at all. /RAGE
But before I throw this garbage in the dump where it belongs... I'm tempted to try to get this thing working.
I have a fastboot cable and some time. I can get to the fastboot info such as "fastboot -i 0x1949 getvar product" and it returns "product: Soho-PVT-Prod-07" . But, I can't get anything out of the adb commands to recognize the device. I've updated the .ini files from the android SDK.
Is there any boot partition I can load to this thing? Some way to hack into this? thx for any help

Help- Accidental No OS on Kindle Fire HD7

Hello all.
Was tinkering around with my KF- And accidentally wiped everything from my internal storage and system. When it boots up I get the blue KF logo and it stays stuck there- Can't boot into recovery.
ADB doesnt recognize it.
Have a fastboot cable.
How do I atleast push files to it /boot into recovery??
Many thanks.

To boot into recovery, after you power on the kindle, immediately let go of power and instead hold volume down usually only until you see the blue kindle logo. You can hold it longer if it makes ya feel better, it should then show the twrp logo and from there you can use adb to push the ROM of your choosing onto the device, here's a tutorial for that assuming you get into recovery. http://forum.xda-developers.com/showthread.php?t=2459498
I think I know how to get it into recovery from fastboot as well but if that doesn't work you'd just have to reflash Amazon's os with kindle fire first aid.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
To boot into recovery, after you power on the kindle, immediately let go of power and instead hold volume down usually only until you see the blue kindle logo. You can hold it longer if it makes ya feel better, it should then show the twrp logo and from there you can use adb to push the ROM of your choosing onto the device, here's a tutorial for that assuming you get into recovery. http://forum.xda-developers.com/showthread.php?t=2459498
I think I know how to get it into recovery from fastboot as well but if that doesn't work you'd just have to reflash Amazon's os with kindle fire first aid.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I tried all of this- Yes, I got it into recovery, It was recognized once by ADB and when I attempted to push the files from a flash drive it stopped working. Did the flash drive effect it or? It's also not showing up in device manager at all anymore after updating the drivers to ADB.

SilverRoxas said:
I tried all of this- Yes, I got it into recovery, It was recognized once by ADB and when I attempted to push the files from a flash drive it stopped working. Did the flash drive effect it or? It's also not showing up in device manager at all anymore after updating the drivers to ADB.
Click to expand...
Click to collapse
You cannot use a flash drive with the Kindle Fire HD as it's unsupported. You have to push it via command prompts on your computer. Follow the tutorial posted. try adb sidelad rather than adb push as the command.

LinearEquation said:
You cannot use a flash drive with the Kindle Fire HD as it's unsupported. You have to push it via command prompts on your computer. Follow the tutorial posted. try adb sidelad rather than adb push as the command.
Click to expand...
Click to collapse
I don't believe I made myself clear. I attempted to push a file from a flash drive connected from my computer and after it was attempted ADB couldn't find my device. Unless I am misunderstanding you, this is what I did. I have attempted cmd prompts and none are moving to my avail.
My apologizes if I am misunderstanding you, sir.

SilverRoxas said:
I don't believe I made myself clear. I attempted to push a file from a flash drive connected from my computer and after it was attempted ADB couldn't find my device. Unless I am misunderstanding you, this is what I did. I have attempted cmd prompts and none are moving to my avail.
My apologizes if I am misunderstanding you, sir.
Click to expand...
Click to collapse
Ah gotcha, I was thinking you were trying to use OTG with a flashdrive. So, I wonder if the problem was that you were trying to flash from a flashdrive or maybe you are missing the adb.exe file. The folder you put the ADB drivers in should have a file marked adb.exe as well. This is what will execute the pushing of the files. Make sure you point the drivers after it is in the folder you will CD from. If you don't have this then download the sdk package and in one of the tool folders you will have adb.exe. Just throw your drivers and ROM in that folder and that will be the folder you CD from.
So try this:
a. Make sure the ROM, ADB drivers and adb.exe are in the same folder.
b. Now go into device driver and manually (choose from your files) update the adb drivers and install them.
c. Once the adb is again recognised go into the folder with all the files and find a white area and hold shift and right click on the mouse and choose open a command window here.
d. Now enter the commands adb sideload name-of-rom-or-file-here-make-sure-to-add (.zip) - at - the-end /sdcard/
e. Give a minute for the process to show in the command window. You should start seeing some percentages as the file is pushed.

LinearEquation said:
Ah gotcha, I was thinking you were trying to use OTG with a flashdrive. So, I wonder if the problem was that you were trying to flash from a flashdrive or maybe you are missing the adb.exe file. The folder you put the ADB drivers in should have a file marked adb.exe as well. This is what will execute the pushing of the files. Make sure you point the drivers after it is in the folder you will CD from. If you don't have this then download the sdk package and in one of the tool folders you will have adb.exe. Just throw your drivers and ROM in that folder and that will be the folder you CD from.
So try this:
a. Make sure the ROM, ADB drivers and adb.exe are in the same folder.
b. Now go into device driver and manually (choose from your files) update the adb drivers and install them.
c. Once the adb is again recognised go into the folder with all the files and find a white area and hold shift and right click on the mouse and choose open a command window here.
d. Now enter the commands adb sideload name-of-rom-or-file-here-make-sure-to-add (.zip) - at - the-end /sdcard/
e. Give a minute for the process to show in the command window. You should start seeing some percentages as the file is pushed.
Click to expand...
Click to collapse
I attempted your method shown here and I get stuck at ADB drivers. There is no Kindle Fire device in my device manager and no bubble shows up when my kindle is attached to my pc. Could the cord be the issue? (I'm also running Windows XP, if that makes a difference.)
Also, I have drivers installed, but I'm unsure they're the correct ones. Where can I find them?

SilverRoxas said:
I attempted your method shown here and I get stuck at ADB drivers. There is no Kindle Fire device in my device manager and no bubble shows up when my kindle is attached to my pc. Could the cord be the issue? (I'm also running Windows XP, if that makes a difference.)
Also, I have drivers installed, but I'm unsure they're the correct ones. Where can I find them?
Click to expand...
Click to collapse
You won't have a pop up when your tablet is plug in at this point. In your device manage do you see a yellow triangle? There should be some android device in your device manager of some sort the pops up when plugged in. To test abd being recognized type adb devices in the command window and you should see your device show in the command window within 30 seconds.

LinearEquation said:
You won't have a pop up when your tablet is plug in at this point. In your device manage do you see a yellow triangle? There should be some android device in your device manager of some sort the pops up when plugged in. To test abd being recognized type adb devices in the command window and you should see your device show in the command window within 30 seconds.
Click to expand...
Click to collapse
After another day of messing with it, yes, finally, it's recognized in ADB. I can push anything but the .zip files for Gapps and Roms. When I try to, it just gives me a list of all the commands you can use with ADB. I've tried ADB sideload and push. Neither work.

SilverRoxas said:
After another day of messing with it, yes, finally, it's recognized in ADB. I can push anything but the .zip files for Gapps and Roms. When I try to, it just gives me a list of all the commands you can use with ADB. I've tried ADB sideload and push. Neither work.
Click to expand...
Click to collapse
Check the md5sum for corruption. Make sure to have those zips in the same folder you're CDing from.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

LinearEquation said:
Check the md5sum for corruption. Make sure to have those zips in the same folder you're CDing from.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay, so now no file is pushing/sideloading to my Kindle. I have them in the same folder I'm CDing from and it's still just running through what commands ADB can do. I'm unsure why it's doing this? It pushed once and now it won't anymore (similar to how it detected my kindle before then didnt).

SilverRoxas said:
Okay, so now no file is pushing/sideloading to my Kindle. I have them in the same folder I'm CDing from and it's still just running through what commands ADB can do. I'm unsure why it's doing this? It pushed once and now it won't anymore (similar to how it detected my kindle before then didnt).
Click to expand...
Click to collapse
Is adb still recognized in you device drivers?
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

LinearEquation said:
Is adb still recognized in you device drivers?
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, my Kindle is still recognized.

i dont os on my kindle fire hd 7
I am having a mare with my kindle fire hd 7
It all starrted when anything google related kept crashing.
I tried to find solutions to the problem but no joy.
I then tried to install a different update to cyanogenmod nightly software but i then had a major problem with not being able to turn on my wifi.
I went into Twrp and tried to restore to my previous software but when my kindle re-booted i got stuck with a flashing teamwin logo
After trawling for days i managed to get out of that but im now in a situation where i dont have any OS on my kindle.
I have followed instructions on how to push files onto my kindle but despiote finding some files on my sdcard i am unable to reboot past the blue and white Kindlefire logo.
I have tried using the kindle un-brick java option but no joy either
I would really appreciate some help solving this proble as it is really driving me crazy.
I can still access twrp and i can access bootloader to get the orange and white fastboot logo.
If someone can help guide me through how i can get my kindle working again id really appreciate it
cheers
JJ

Might be able to help.
I had the exact same problem as you and watched this video and i fixed it youtube(dot)com/watch?v=NaK5OxUeDKM
sorry im not allowed to post links because im a new user.

Hey Danny101
Danny101 said:
I had the exact same problem as you and watched this video and i fixed it youtube(dot)com/watch?v=NaK5OxUeDKM
sorry im not allowed to post links because im a new user.
Click to expand...
Click to collapse
Thanx for your response.
Sorry its taken me a while to reply but have had loads going one recently.
Shortly after making my post i did find that exact same youtube vid tutorial and was able to solve my problem.
I just wanted to say thanx for taking time to respond even so.
All the best.
JJ

I'm stuck! Is a factory cable required?

I spent about 6 hours yesterday trying to root my Kindle Fire HD 7" tablet using various methods. I've searched numerous posts and tried several ways with no success.
I believe my ADB drivers are working properly because I am able to reboot the tablet from adb successfully. And in the Windows Device Manager it shows the "Android Composite ADB Interface" as my driver. But the command "adb reboot bootloader" just reboots back into the standard Home screen. And any fastboot command just gives me the "waiting for device" response.
I am on Version 7.4.8 of the firmware so I am trying to find a way to downgrade. I purchased it in November 2012 so it is the 2012 tablet. But every method I try just fails for one reason or another. So my question is, do I need a factory cable in order to get anywhere with this? Is it even doable with this version firmware?
Thank you in advance.

It is doable without a factory cable, the known rooting utilities people typically use are kindle fire first aid or binary's root. If you still can't get it to root, you can technically use a fastboot cable and kffa to restore it to a earlier is that os pre-rooted.
Sent from my Amazon Kindle Fire HD using Tapatalk

pastorbob62 said:
I spent about 6 hours yesterday trying to root my Kindle Fire HD 7" tablet using various methods. I've searched numerous posts and tried several ways with no success.
I believe my ADB drivers are working properly because I am able to reboot the tablet from adb successfully. And in the Windows Device Manager it shows the "Android Composite ADB Interface" as my driver. But the command "adb reboot bootloader" just reboots back into the standard Home screen. And any fastboot command just gives me the "waiting for device" response.
I am on Version 7.4.8 of the firmware so I am trying to find a way to downgrade. I purchased it in November 2012 so it is the 2012 tablet. But every method I try just fails for one reason or another. So my question is, do I need a factory cable in order to get anywhere with this? Is it even doable with this version firmware?
Thank you in advance.
Click to expand...
Click to collapse
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct. The fact you see it in your device manager is a pretty good sign though.
The command you are looking for is (must be rooted to use this command otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.

LinearEquation said:
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct. The fact you see it in your device manager is a pretty good sign though.
The command you are looking for is (must be rooted to use this command otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
Click to expand...
Click to collapse
I appreciate your reply and information very much. However, I downloaded the SDK package and installed it over a year ago and have used Fastboot for three other devices numerous times. I used Fastboot with my Asus TF300T to flash recoveries, and return to Asus Stock on more occasions than I can count. I am currently running CROMBi-kk 20140323 on that same tablet. Just to be certain, I connected it just now as I am typing this and verified several Fastboot commands. I also have a Huawei U8800-51 and a Samsung S4 Mini Duo GT-I9192 and have used Fastboot commands with them as well.
So I don't think it is an issue with the driver not being installed correctly, or the SDK not being present unless it is a version specific issue. But the Samsung phone is much newer than the Kindle so I don't think it is that either.
So I guess that puts me at an impasse until I get a factory cable. Or I can just forget customizing the Kindle.

pastorbob62 said:
I appreciate your reply and information very much. However, I downloaded the SDK package and installed it over a year ago and have used Fastboot for three other devices numerous times. I used Fastboot with my Asus TF300T to flash recoveries, and return to Asus Stock on more occasions than I can count. I am currently running CROMBi-kk 20140323 on that same tablet. Just to be certain, I connected it just now as I am typing this and verified several Fastboot commands. I also have a Huawei U8800-51 and a Samsung S4 Mini Duo GT-I9192 and have used Fastboot commands with them as well.
So I don't think it is an issue with the driver not being installed correctly, or the SDK not being present unless it is a version specific issue. But the Samsung phone is much newer than the Kindle so I don't think it is that either.
So I guess that puts me at an impasse until I get a factory cable. Or I can just forget customizing the Kindle.
Click to expand...
Click to collapse
You said you were using simply adb reboot bootloader right? Did you try the command I suggested? "adb shell su -c reboot bootloader" because if everything is set up right then this should work. CD from the tools folder.

LinearEquation said:
You said you were using simply adb reboot bootloader right? Did you try the command I suggested? "adb shell su -c reboot bootloader" because if everything is set up right then this should work. CD from the tools folder.
Click to expand...
Click to collapse
Okay, got it working. Not sure what the problem was but I reinstalled SDK-Tools and Platform-Tools using the latest version of SDK. I was then able to use KFFA to root the Kindle and do a full backup. Not sure why it didn't work before the reinstall since I used ADB and Fastboot with my TF300T as recently as a week and a half ago while testing CROMBi-kk. Also verified they still worked with that tablet yesterday. Whatever the problem, it was specific to the Kindle.
One more question. Is it necessary to downgrade from 7.4.8 before installing a second bootloader and custom ROM? Or is that just a precautionary step because some people have had issues.

pastorbob62 said:
Okay, got it working. Not sure what the problem was but I reinstalled SDK-Tools and Platform-Tools using the latest version of SDK. I was then able to use KFFA to root the Kindle and do a full backup. Not sure why it didn't work before the reinstall since I used ADB and Fastboot with my TF300T as recently as a week and a half ago while testing CROMBi-kk. Also verified they still worked with that tablet yesterday. Whatever the problem, it was specific to the Kindle.
One more question. Is it necessary to downgrade from 7.4.8 before installing a second bootloader and custom ROM? Or is that just a precautionary step because some people have had issues.
Click to expand...
Click to collapse
Its kinda just a precautionary measure, to put it plainly, your kindle will bootloop into recovery if you do the process on 7.4.8, so unless you know how to use "Adb push" its suggested to put the rom and gapps onto the kindle ahead of time so it will be there when you start to bootloop into recovery. On another note, you do need to downgrade the bootloader though, if you use hashcodes method, please check the md5sum on the bootloader file before flashing it to avoid a hardbrick. If you used the fireflash method i wouldnt worry about it, just make sure you check off the downgrade bootloader button above or beside the red warning text.

I had these same issues. The device wouldn't boot into fastboot while it was <waiting for device>.
I did this.
1. Used Many Root Tool to gain root. http://forum.xda-developers.com/showthread.php?t=1886460
2. Placed the Rom and Gapps file on my sd card to be safe.
3. Used Anonymous.123's Tool up until the fastboot <waiting for device> malfunction. http://forum.xda-developers.com/showthread.php?t=2685414
4. Opened the Batch File for the Flasher Tool and copied and pasted the fastboot commands into a terminal with the Kindle in Fastboot. The only way I could get it in fastboot was "adb shell su -c reboot bootloader"
This will install the 4.2 bootloader so you don't have to flash back.
5. Profit 2nd Bootloader and TWRP
Good luck. You'll get it.
Sorry I Keep using the quote reply wrong. Havn't been on XDA in a while.

Okay, following Hashcode's procedure, I have successfully completed all steps up to flashing CM 10.2. TWRP works great and I made a backup from it. Not really necessary since I had backed up my Kindle three different ways and also copied all of my data to my PC as well.
But when I went to copy the TWRP backup to my PC for safekeeping I discovered that now I no longer have access to my Kindle from my PC's file explorer when I am booted into my Kindle. Prior to doing any of the steps here I could swap files back and forth without any problem. So how do I get that feature back??
I am running WIndows 8.1. This worked before I followed the procedures here. Also, when I pull files in adb where do they get stored??? Can't seem to find them.

Check the storage settings in CM you have to turn MTP storage in.
Sent from my Galaxy Nexus using xda app-developers app

[Q] Kindle Fire HD Stuck Booting on TWRP Instead of Android

I've tried a bunch of tutorials on here to fix this, but can't figure it out.
I was on my Kindle HD 8.9" running CyanogenMod 10.1, which it has for a year. Suddenly, I got some popup last night. It said there was a nightly build update in my notifications area, so I just clicked "OK" and let it do its thing. It installed for a little bit, all was okay... but now I cannot access my Android OS.
I went to turn my Kindle on after the update, but it keeps going to TWRP. What will happen exactly is it starts... orange letters... then blue letters... then restarts again to orange letters... then blue letters... then TWRP. Why does it keep going to TWRP? How do I fix this?
My Kindle can't even connect to the PC. I just either get "Unknown Device" or "Kindle" in my Device Manager, and mounting from TWRP does nothing.
Then I try installing the Android SDK to get the ADB on my machine, and I added the "Path" in my environment to the two tools folders, but nothing... same thing happens. Constant loop into TWRP. Driving me nuts.
The update it wanted me to install when I could still get into the Android OS was cm-11-20140420-NIGHTLY-jem. I thought maybe trying to connect my Kindle to my PC in order to open the drive, then pasting the cm-11-20140420-NIGHTLY-jem into a folder and installing again from TWRP would solve my problem, but I can't even get that far.
I'm at a loss. Please help.

GogoplataMMA said:
I've tried a bunch of tutorials on here to fix this, but can't figure it out.
I was on my Kindle HD 8.9" running CyanogenMod 10.1, which it has for a year. Suddenly, I got some popup last night. It said there was a nightly build update in my notifications area, so I just clicked "OK" and let it do its thing. It installed for a little bit, all was okay... but now I cannot access my Android OS.
I went to turn my Kindle on after the update, but it keeps going to TWRP. What will happen exactly is it starts... orange letters... then blue letters... then restarts again to orange letters... then blue letters... then TWRP. Why does it keep going to TWRP? How do I fix this?
My Kindle can't even connect to the PC. I just either get "Unknown Device" or "Kindle" in my Device Manager, and mounting from TWRP does nothing.
Then I try installing the Android SDK to get the ADB on my machine, and I added the "Path" in my environment to the two tools folders, but nothing... same thing happens. Constant loop into TWRP. Driving me nuts.
The update it wanted me to install when I could still get into the Android OS was cm-11-20140420-NIGHTLY-jem. I thought maybe trying to connect my Kindle to my PC in order to open the drive, then pasting the cm-11-20140420-NIGHTLY-jem into a folder and installing again from TWRP would solve my problem, but I can't even get that far.
I'm at a loss. Please help.
Click to expand...
Click to collapse
boot into twrp, check what version of twrp you have. Then you may need to update your twrp to be cm 11 compatible if its not at latest version, current version is like 2.7.0.0(least it is for the 7", havnet check to see if that builds out for 8.9 as well), anyways check the device manager for a device with a yellow triangle next it, if you don't see that and you do have a adb interface showing up but adb doesnt detect it then uninstall the adb device and mtp device and search for devices, if it still doesnt work look for a component device with a vid of 1949 in the properties>details>hardware id's section, if you find it then remove it and scan for device. Windows is a pain in terms of drivers for the kindle in different modes. Once adb is working its as simple as pushing the rom with adb push. You may need to factory reset and/or wipe internal storage so i recommend backing up the data, i would assume the current bootloop has something to do with either no factory reset before going to cm 11 or selinux issues, but that would mean the kernel didnt flash in the ota which would be weird.

stunts513 said:
boot into twrp, check what version of twrp you have. Then you may need to update your twrp to be cm 11 compatible if its not at latest version, current version is like 2.7.0.0(least it is for the 7", havnet check to see if that builds out for 8.9 as well), anyways check the device manager for a device with a yellow triangle next it, if you don't see that and you do have a adb interface showing up but adb doesnt detect it then uninstall the adb device and mtp device and search for devices, if it still doesnt work look for a component device with a vid of 1949 in the properties>details>hardware id's section, if you find it then remove it and scan for device. Windows is a pain in terms of drivers for the kindle in different modes. Once adb is working its as simple as pushing the rom with adb push. You may need to factory reset and/or wipe internal storage so i recommend backing up the data, i would assume the current bootloop has something to do with either no factory reset before going to cm 11 or selinux issues, but that would mean the kernel didnt flash in the ota which would be weird.
Click to expand...
Click to collapse
Now I'm all screwed up. Before I saw this message, I restored my Kindle back to when it was still running the factory default OS with root, then I shut it down to enter TWRP, and it appeared on its own, but it was installing some sort of update... and when the Kindle's factory default OS appeared, my root was gone. Now I am stuck on the factory default Kindle HD 8.9" on System Version 8.4.8. Man, I should have never accepted that update and just left it as it was. Ugh. Well, for right now, there's an entry in my Device Manager that says "Kindle Fire" and when you click the arrow to bring down the submenu, it says "Android ADB Interface." The Kindle is now working when connected through USB. Now... how do I go about rooting this thing and getting TWRP on it again, because it seems the entire thing got erased. Not having my ROM installed on this thing makes it mostly useless to me.

Root with kffa or binary's root, think the newest version has different choices than the tutorial, use the old normal method. Last I checked it worked.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Root with kffa or binary's root, think the newest version has different choices than the tutorial, use the old normal method. Last I checked it worked.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I can't find anything. Download links are dead for KFFA. You have a link to get it through another source?

They are up and running when I click em. You were on this thread right?: http://forum.xda-developers.com/showthread.php?t=2096888
If that doesn't work you can always use binary's root.
http://forum.xda-developers.com/showthread.php?t=1886460
Use the old normal method if I remember correctly.
Sent from my Amazon Kindle Fire HD using Tapatalk

Nah, the link is dead here. Says the file was removed. There are other members in the forum asking as well for a new link.
I managed to get ADB working, and in Device Manager, I have "Android Device -> Android Composite ADB Interface."
I open CMD and type "ADB" and it scrolls a bunch of stuff, but when I type "ADB Devices" I get a list with nothing there. It's just blank.
I tried using BIN4RY Revision 33, using Option #1, but it just keeps bringing me to a "Path not Found" error of some sort.
It looks like all I need to manage to do now is get ADB to list my Kindle device before attempting the ROOT, but how can I do that?
I still wanna give KFFA a try, but no downloads anywhere, and I don't trust random 4Share and the likes, not that it's gonna fix my problem.
I'm close... I just need this damn ADB to list my Kindle device and I think I'll be okay.
Also, I want to say thanks for the help you've given me so far. It's greatly appreciated. :highfive:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb kill-server
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
i.imgur.com/gZrrqXm.jpg

No problem, i like helping people fix things.
Try uninstalling the device and letting it search for new hardware. This is more than likely a driver issue.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
No problem, i like helping people fix things.
Try uninstalling the device and letting it search for new hardware. This is more than likely a driver issue.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Oh, believe me. I tried that like 50 times. I think I'm just gonna make a virtual machine of Win7, completely clean install without all my drivers everywhere, and try my luck there.

GogoplataMMA said:
Oh, believe me. I tried that like 50 times. I think I'm just gonna make a virtual machine of Win7, completely clean install without all my drivers everywhere, and try my luck there.
Click to expand...
Click to collapse
From the administrator profile on your PC open a command prompt and type Bcdedit.exe -set TESTSIGNING ON then hit enter. Now restart your computer. This will disable Windows driver security enforcement. Then try to install the drivers in the device manager.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

LinearEquation said:
From the administrator profile on your PC open a command prompt and type Bcdedit.exe -set TESTSIGNING ON then hit enter. Now restart your computer. This will disable Windows driver security enforcement. Then try to install the drivers in the device manager.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately, that didn't work. I'm pretty sure one or more of my drivers are interfering with the connection to the Kindle, but this is such an old OS with so many drivers, it's hard to tell.
Right now, I have a Virtual Machine of Windows 7 up. I plugged my Kindle in and I can instantly see it. I can even enter the internal storage! I'm currently installing the Android SDK for the ADB after installing the Java SE x86 version. Once I get ADB on it, I'll see if it lists my device now. Seems promising since the VM sees and allows me to already enter the internal storage, unlike my original Win7 OS.
EDIT #1: Great news! ADB now lists my device! Thing is... Root with Bin4ry Revision 33 does not seem to want to work. This is what I get...
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (14.12.2013) v33 =
======================================================================
Device type:
0) Xperia Root by cubeundcube
1) New Standard-Root (thx Ariel Berkman)
2) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
3) Old
4) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 1
Please connect Device with enabled USB-Debugging to your Computer
The system cannot find the path specified.
Doing a Backup first, please confirm this on your device!
The system cannot find the path specified.
Done!
Press any key to continue . . .
Click to expand...
Click to collapse
It doesn't give me a chance to do anything. All of that pops up as soon as I press enter. ADB and third party software is enabled on my Kindle. ADB even reads my device as:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
B0C9110232560198 device
Click to expand...
Click to collapse
I'm at a loss now. Any ideas?
EDIT #2: Success! The issue was I was using Root with Bin4ry Revision 33. I should have been using Root with Bin4ry Revision 30. That worked, and I am now ROOT. Mission accomplished. Now the next part of my mission... figuring out how to get TWRP on this thing.

Well, trying to install TWRP is going very wrong. I'm using the tutorial here: http://forum.xda-developers.com/showthread.php?t=2128175
Everything seemed to work until I get to Step 3. I'll enter the commands but it tells me that there is no such directory or something. Something about there not being any "stack." Can't recall. I wanted to ask on the thread there but the site isn't allowing me to post there.
adb push stack /sdcard/ is where the issue occurs. Everything else worked.
I'm at a loss, and the comments don't seem to help on that thread. Please tell me there is an easier method of getting TWRP on this thing.
ERROR:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push stack /sdcard
/
cannot stat 'stack': No such file or directory
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse

GogoplataMMA said:
Well, trying to install TWRP is going very wrong. I'm using the tutorial here: http://forum.xda-developers.com/showthread.php?t=2128175
ERROR:
Click to expand...
Click to collapse
That tutorial is for the 8.9. You want the tutorial for the 7". http://forum.xda-developers.com/showthread.php?t=2218796
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

LinearEquation said:
That tutorial is for the 8.9. You want the tutorial for the 7". http://forum.xda-developers.com/showthread.php?t=2218796
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
He's on a 8.9", he just posted in the wrong section. Use the fireflash method from seokhuns tutorial, just don't forget to check the box with red text near it or you will get a nice redscreen brick. Lemme grab a link
Edit: link grabbed! http://forum.xda-developers.com/showthread.php?t=2277105

I used FireFlash, followed the instruction... now I cannot get passed the first "Kindle Fire" logo when I turn the Kindle on. It just freezes at "Kindle Fire" as soon as I turn it on. I can't seem to do anything at all, and it won't connect via USB. Any ideas?

You missed a check box somewhere. If it is indeed a 8.9" kindle this should be fairly easy to fix. Open the device manager and plug the kindle in while it is off, it should briefly appear as a jem device. While it briefly shows up you need to right click it and hit update drivers and navigate to where you would have downloaded and extracted the drivers in my signature, once you manage to install them you just need to run a "fastboot -i 0x1949 getvar product" with the kindle unplugged and off, and then plug it in once it says waiting for device. It should then go into fastboot mode where you can restore from kffa or SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
You missed a check box somewhere. If it is indeed a 8.9" kindle this should be fairly easy to fix. Open the device manager and plug the kindle in while it is off, it should briefly appear as a jem device. While it briefly shows up you need to right click it and hit update drivers and navigate to where you would have downloaded and extracted the drivers in my signature, once you manage to install them you just need to run a "fastboot -i 0x1949 getvar product" with the kindle unplugged and off, and then plug it in once it says waiting for device. It should then go into fastboot mode where you can restore from kffa or SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
It's not working... it won't read at all. Device Manager doesn't see the Kindle at all. And yes it is 8.9". I think it may be bricked now. ;'(
And all because of that stupid update... ughhhh. Sucks!

You should try the command from a Ubuntu live CD/USB if is a lot easier to do from there, if it won't work from there then I would be convinced something may be wrong with the bootloader, but I don't see the bootloader as the problem because if anything it would have just been downgraded and I'm more inclined to thinking the bootimg is corrupted. That can cause odd behavior with the bootloader. Are you positive this is the 8.9" model and not the 7" model?
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
You should try the command from a Ubuntu live CD/USB if is a lot easier to do from there, if it won't work from there then I would be convinced something may be wrong with the bootloader, but I don't see the bootloader as the problem because if anything it would have just been downgraded and I'm more inclined to thinking the bootimg is corrupted. That can cause odd behavior with the bootloader. Are you positive this is the 8.9" model and not the 7" model?
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I switched over to my main Windows 7 OS and did what you said. I connected it and it showed for a brief moment in Device Manager, so I quickly loaded the driver and updated. But wen I type the command you gave me, it says <waiting for device>, so I plug it back in and... nothing. At all. Just sits there at <waiting for device>
I'd try Linux, I have several copies of different OS's, but I'm not very good at working with it or using Terminal... I can try that though, but no clue how I'd get ADB or the Kindle to read on it. :\
And yes, 100% it's the 8.9". The resolution is 1200p.

OK the command has to be run while the device is off and disconnected, once it says waiting for device, plug the kindle in and it should work if the drivers are working. Linux is really easy to use with a kindle, it has the fastboot and adb drivers built in natively, only thing you need is the fastboot command from the Ubuntu repos if you are using Ubuntu, believe they were added to the repo in 13.10.
Sent from my Amazon Kindle Fire HD using Tapatalk

Kindle Fire HD Bircked Help

Ok I bricked my Kindle Fire HD 7.... Ive heard you needed to order a fastboot cable to fix it and I did.. Now I just need help to fix it as im not the best when it comes to this stuff. Again I have the fastboot cable and the tablet goes into fastboot mode but I dont know what to do... Could someone give me instructions on how to fix it?

AidenOwns said:
Ok I bricked my Kindle Fire HD 7.... Ive heard you needed to order a fastboot cable to fix it and I did.. Now I just need help to fix it as im not the best when it comes to this stuff. Again I have the fastboot cable and the tablet goes into fastboot mode but I dont know what to do... Could someone give me instructions on how to fix it?
Click to expand...
Click to collapse
2012 or 2013 model? Camera or no camera?
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app

LinearEquation said:
2012 or 2013 model? Camera or no camera?
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
2012 And it only has a front camera

AidenOwns said:
2012 And it only has a front camera
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1951254
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app

Ok well on my tablet it shows the Fastboot logo... On the KFHD SRT Thing I selected the first option (Restore Factory Rooted With SuperSU)
And all it shows is < waiting for device >
Is there something else I need to do before this???

AidenOwns said:
Ok well on my tablet it shows the Fastboot logo... On the KFHD SRT Thing I selected the first option (Restore Factory Rooted With SuperSU)
And all it shows is < waiting for device >
Is there something else I need to do before this???
Click to expand...
Click to collapse
Make sure you are logged in as admin on your computer. Open a command prompt and type "fastboot -i 0x1949 getvar product" without the quotations. Wait 10 seconds and tell me what the screen says.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
---------- Post added at 11:03 AM ---------- Previous post was at 10:57 AM ----------
Make sure your drivers are installed properly. Windows 8/7 64bit need to be put in test mode so your drivers will install right. Windows is not going to let you do this until you disable device driver signature enforcement.
Disable device driver signature enforcement in Windows 7 read on. Windows 8 has different steps.
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 type these in the command prompt one at a time hitting enter after each one.
bcdedit.exe -set TESTSIGNING ON
bcdedit.exe -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. To exit test mode follow steps 1,2 and 3 in part B of my writeup and type 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
Now restart computer.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
---------- Post added at 11:06 AM ---------- Previous post was at 11:03 AM ----------
Here are the modified drivers http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9 if you have <still waiting for device> use the guide above and the drivers in this post.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app

AidenOwns said:
Ok well on my tablet it shows the Fastboot logo... On the KFHD SRT Thing I selected the first option (Restore Factory Rooted With SuperSU)
And all it shows is < waiting for device >
Is there something else I need to do before this???
Click to expand...
Click to collapse
Please wait for at least 20 minutes. the process takes a long time