Related
Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!
What is firefirefire? Have yet to see a formal definition of that
androidcues said:
What is firefirefire? Have yet to see a formal definition of that
Click to expand...
Click to collapse
Its a bootloader
Sent from my Kindle Fire using xda premium
Thanks Man, I was messing around with CM7 and I rebooted into recovery not knowing that it would keep me in a recovery boot loop and KFU wasn't helping trying to help me.
Tierehl said:
Thanks Man, I was messing around with CM7 and I rebooted into recovery not knowing that it would keep me in a recovery boot loop and KFU wasn't helping trying to help me.
Click to expand...
Click to collapse
Happy to help
Zombiepiratez said:
Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!
Click to expand...
Click to collapse
Unfortunately this will only work if your windows based computer even recognizes the kindle, which mine doesn't. Thanks tho. I've given mine to my tech geek who has access to linux based system, so hopefully he will be able to recover my brick.
Sent from my MB860 using XDA App
Sorry about that. I wish I could help.
I am a newbie. I recover my kf using the recovery boot with kfu and it works fine now. how could
I know if it is in the recovery boot loop? Many thanks.
Sent from my GT-I9100 using XDA App
Zombiepiratez said:
Sorry about that. I wish I could help.
Click to expand...
Click to collapse
Its ok. I read everywhere its impossible to brick a kindle so im hoping that's true.
Sent from my MB860 using XDA App
My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?
*Snip*
Double post, fail.
CiggyPipe said:
My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?
Click to expand...
Click to collapse
Did it just immediately recognize it, or did you have to re-install drivers? And i'm not sure about the battery drain thing...
CiggyPipe said:
My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?
Click to expand...
Click to collapse
Tried that to no avail as well.
Sent from my MB860 using XDA App
Zombiepiratez said:
Did it just immediately recognize it, or did you have to re-install drivers? And i'm not sure about the battery drain thing...
Click to expand...
Click to collapse
I guess I should make note that by this point I'd uninstalled the driver I used. It was recognized as "kindle" once after I plugged it in while off, so then I went ahead and manually reinstalled the driver (from Jayce Ooi's site), which allowed the fastboot commands to work. Otherwise, the command would hang at <waiting for device>.
Thanks! My kindle fire was stuck at the firefirefire logo. My computer couldn't even recognize my kindle but I uninstalled the Android ADB composite interface and plugged it back in, when the kindle was off. Then I used your commands to get fastboot. I installed TWRP, now I'm stuck in TWRP and can't mount my sd... to flash any rom.
Thanks
Thanks for the info. i thought i'd bricked it and the info worked a treat. that will teach me to keep my mouth shut "of course i can root your kindle"
try fixing permissions under advanced, and then make sure only the sdcard box is marked in mount option.
Sent from my Amazon Kindle Fire using xda premium
Zombiepiratez said:
Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!
Click to expand...
Click to collapse
I'm sorry but I tried all the steps above but KF's still stuck at boot logo. I flashed CM9 stock kernel 3.0 with FFF 1.4a and CWR, wiped everything and factory reset, then install...but it just hangs at the blue skating droid logo... any idea?
jamesphan said:
I'm sorry but I tried all the steps above but KF's still stuck at boot logo. I flashed CM9 stock kernel 3.0 with FFF 1.4a and CWR, wiped everything and factory reset, then install...but it just hangs at the blue skating droid logo... any idea?
Click to expand...
Click to collapse
The Unbrick utility won't help in your case. When the device hangs at the boot animation or goes to a blank screen afterwards, the problem is usually one of three things.
* the rom installed is corrupted
* you didn't wipe the necessary data before installing
* you tried flashing a rom that's incompatible with the recovery you are using (I'm betting this is most likely the case)
Try installing a different rom (preferably non-ICS) to see if that fixes the problem. Of so, check to see if you're using the latest version of CWM by Hashcode or install TWRP to run ICS based roms.
Any further questions regarding this matter should be redirected to the Q&A section.
[Edit:] For some reason I thought this was the thread for the Unbrick Utility. Regardless, the solution is still the same.
You are a GENIOUS!!!
Thanks a LOT!!!!!!!!!!
I just overall screwed up big time with this thing. I rooted 6.2.1, then uninstalled/froze a bunch of the stock apps (including the default Kindle launcher, as I had Go Launcher installed).
I then decided I wanted to restore to the factory default settings, as I wanted to use Amazon prime, among other things. I went into settings and hit the "restore to factory defaults button" (which was stupid, I know). Unsurprisingly, this resulted in Kindle Fire bootloops.
Trying to fix this, I used the KindleFireTool to install the most recent TWRP...which didn't work at all. It would just stay on the yellow triangle screen. Now, things have gotten even worse, though I don't know why. Whenever I plug the fire into the computer, it goes into TWRP bootloops!
For the brief few seconds that the Fire is on when plugged into my computer, the driver isn't recognized at all (shows up as "kindle" with a triangle next to it in device manager).
I know what I did was dumb, but even so, any help would be hugely appreciated.
YES YES YES!!!! OK HERES HOW I DID IT TO FIX THE BOOTLOOP OF TWRP
First you must download Kindle Fire Utility and extract it to your desktop
then go to command prompt or cmd then type in the location of the folder heres mine for example: C:\Users\Madaran\Desktop\Kindle Fire Utility\tools
then type in fastboot -i 0x1949 oem idme bootmode 4000
For me it said waiting for device all I did is rebooted the device and it worked
as the device reboot it will still go back to TWRP now type this in the command prompt
fastboot -i 0x1949 oem idme bootmode 4000
then it should reboot again and ITS FIXED
----------------------------------
I used this thread to fix it.
http://forum.xda-developers.com/showthread.php?t=1428715
Thank you so much! I'll post results when I get the opportunity.
Well it didn't work...the thing isn't connecting to the computer properly. I think it's a goner.
Mine didn't connect also but it still worked. You don't need the device to be connected just plug it in and put it in the TWRP recover mode. Then do the steps again.
1.Download Kindle Fire Utility
2.Extract it to desktop.
3.You can't connect it while its in FastBoot mode so open up CMD or Command Prompt.
4.Again locate the folder and type it in the CMD for example I typed:
"cd C:\Users\Madaran\Desktop\Kindle Fire Utility\tools"
5.Then type this in "fastboot -i 0x1949 oem idme bootmode 4000"
6.It should say waiting for device. Go to TWRP and hit reboot system.
7.It should work now and while waiting for your Kindle to boot up, the power button should be orange.
8.When it turned orange I immediately typed this in the CMD or Command Prompt
"fastboot -i 0x1949 oem idme bootmode 4000" so it wouldn't boot to the TWRP recovery menu.
9.It should reboot again and load up your CyanogenMod 7
10. If it work hit the thanks button please.
I did all of that up until step 6. My device won't allow me to reboot. When it's plugged in via USB, it boots up, dies within 20 seconds, then boots again. I can't break the cycle, and it just says waiting for device on and on...
skippwhy said:
I did all of that up until step 6. My device won't allow me to reboot. When it's plugged in via USB, it boots up, dies within 20 seconds, then boots again. I can't break the cycle, and it just says waiting for device on and on...
Click to expand...
Click to collapse
It maybe your battery its low. Try to charge it and connect it again.
Definitely worth a shot
You were right! It was a battery issue
sirmavs said:
Mine didn't connect also but it still worked. You don't need the device to be connected just plug it in and put it in the TWRP recover mode. Then do the steps again.
1.Download Kindle Fire Utility
2.Extract it to desktop.
3.You can't connect it while its in FastBoot mode so open up CMD or Command Prompt.
4.Again locate the folder and type it in the CMD for example I typed:
"cd C:\Users\Madaran\Desktop\Kindle Fire Utility\tools"
5.Then type this in "fastboot -i 0x1949 oem idme bootmode 4000"
6.It should say waiting for device. Go to TWRP and hit reboot system.
7.It should work now and while waiting for your Kindle to boot up, the power button should be orange.
8.When it turned orange I immediately typed this in the CMD or Command Prompt
"fastboot -i 0x1949 oem idme bootmode 4000" so it wouldn't boot to the TWRP recovery menu.
9.It should reboot again and load up your CyanogenMod 7
10. If it work hit the thanks button please.
Click to expand...
Click to collapse
Hey guys... I kinda bricked my Kindle... I tried all the steps mentioned above. My Kindle boots but it freezes on the Kindle Fire Boot Screen. It does not load the home screen of Kindle with Shelf.
Please help
http://forum.xda-developers.com/showthread.php?t=1428428
This tutorial is by Jayceooi I just added some more stuff to it.
The reason your TWRP is boot looping is its because, you installed a file or zip that cause for your system to corrupt or break. It can also be a file that is in the system that you deleted and rebooted your Kindle to save changes.
How to solve stuck at yellow triangle issue on Kindle Fire?
Via Kindle Fire Utility
1. Connect it to your computer.
2. Select 1 Bootmode Menu.
3. Select 1 Normal (4000).
That’s all.
=============================================
Via Command Prompt
Note – you need to have fastboot.exe (located in Kindle Fire Utility\tools folder)
Bring up Command Prompt.
Go to Kindle Fire Utility\tools folder.
Key in fastboot -i 0×1949 oem idme bootmode 4000 (don’t cut and paste).
Key in fastboot -i 0×1949 reboot (don’t cut and paste).
That’s it.
=========================================================
FQA (Frequently Asked Questions)
My computer won't detect my device. Why is this?
-If it doesn't detect it you need to do the Via Command Prompt.
=========================================================
I don't know how to do the Via Command Prompt part how do you do it?
-Well you can try what I did to my Kindle Fire when it keeps boot looping TWRP
1.Download Kindle Fire Utility
2.Extract it to desktop.
3.You can't connect it while its in FastBoot mode so open up CMD or Command Prompt.
4.Again locate the folder and type it in the CMD for example I typed:
"cd C:\Users\Madaran\Desktop\Kindle Fire Utility\tools"
5.Then type this in "fastboot -i 0x1949 oem idme bootmode 4000"
6.It should say waiting for device. Go to TWRP and hit reboot system.
7.It should work now and while waiting for your Kindle to boot up, the power button should be orange.
8.When it turned orange I immediately typed this in the CMD or Command Prompt
"fastboot -i 0x1949 oem idme bootmode 4000" so it wouldn't boot to the TWRP recovery menu.
9.It should reboot again and load up your CyanogenMod 7 or previous ROM build.
10. If it work hit the thanks button please.
=========================================================
Thats a great simple guide. One thing I want to add is that on my Windows 7 box, after I installed TWRP, the Kindle started being detected as "kindle" in lowercase and the drivers would not reinstall correctly, and if I manually installed them, the device would not start. I fixed this issue by doing standard USB device troubleshooting on Windows 7.
Open the Device Manager.
Expand Universal Serial Bus Controllers.
Locate all the USB Root Hubs and uninstall them by right clicking and selecting "Uninstall".
Do the same for all the controllers listed afterwards. Basically remove the USB Root Hubs first, then all the controllers listed so everything under the Universal Serial Bus Controllers is gone.
Reboot the machine and wait for the controllers and hubs to reinstall.
Then reconnect the kindle and hopefully the drivers will install correctly and allow ADB to connect.
sirmavs said:
This tutorial is by Jayceooi I just added some more stuff to it.
The reason your TWRP is boot looping is its because, you installed a file or zip that cause for your system to corrupt or break. It can also be a file that is in the system that you deleted and rebooted your Kindle to save changes.
How to solve stuck at yellow triangle issue on Kindle Fire?
Via Kindle Fire Utility
1. Connect it to your computer.
2. Select 1 Bootmode Menu.
3. Select 1 Normal (4000).
That’s all.
=============================================
Via Command Prompt
Note – you need to have fastboot.exe (located in Kindle Fire Utility\tools folder)
Bring up Command Prompt.
Go to Kindle Fire Utility\tools folder.
Key in fastboot -i 0×1949 oem idme bootmode 4000 (don’t cut and paste).
Key in fastboot -i 0×1949 reboot (don’t cut and paste).
That’s it.
=========================================================
FQA (Frequently Asked Questions)
My computer won't detect my device. Why is this?
-If it doesn't detect it you need to do the Via Command Prompt.
=========================================================
I don't know how to do the Via Command Prompt part how do you do it?
-Well you can try what I did to my Kindle Fire when it keeps boot looping TWRP
1.Download Kindle Fire Utility
2.Extract it to desktop.
3.You can't connect it while its in FastBoot mode so open up CMD or Command Prompt.
4.Again locate the folder and type it in the CMD for example I typed:
"cd C:\Users\Madaran\Desktop\Kindle Fire Utility\tools"
5.Then type this in "fastboot -i 0x1949 oem idme bootmode 4000"
6.It should say waiting for device. Go to TWRP and hit reboot system.
7.It should work now and while waiting for your Kindle to boot up, the power button should be orange.
8.When it turned orange I immediately typed this in the CMD or Command Prompt
"fastboot -i 0x1949 oem idme bootmode 4000" so it wouldn't boot to the TWRP recovery menu.
9.It should reboot again and load up your CyanogenMod 7 or previous ROM build.
10. If it work hit the thanks button please.
=========================================================
Click to expand...
Click to collapse
Or one can just use firekit if they are new to this kind of thing and it works a lot like the kindle fire utility. Here is the link to my guide and the link for kindle fire kit is in there. I must warn those of you that are not on windows that this is a windows only program so those of you running different OS on their pc should either use this thread or my guide as well... Very nice thorough tutorial by the way!
Link to my guide with firekit link in it:
http://forum.xda-developers.com/showthread.php?t=1417234
Link directly to firekit:
http://forum.xda-developers.com/showthread.php?t=1428428
If I helped dont forget that thanks button!!!
Thx guys i will add those and credits as soon as i get to my computer
Hey:
I am having this bootloop problem but when I use KFU 9.2 to get to normal the program just hangs with a white blinking cursor. Should I just wait or do I need an alternate solution. I have TWRP installed, I made a backup of my stock KF but when I crashed it and attempted to restore from TWRP there was no backed-up file to use.
I have downloaded the KF 6.2.1 upgrade using KFU but unsure how to install it at this point.
Thanks
maybe this one will solve your bootloop:
http://forum.xda-developers.com/showthread.php?t=1428428
sirmavs,
I tried your last method and everything went fine until step 8. The light never turned orange and now I'm stuck on the Yellow Triangle.
EDIT:
At this point I opened up the Fire Utility.
I changed the bootmode to normal from there and CM7 rebooted fine.
I really do not understand why FireFireFire hasn't been updated to fix this?
sirmavs said:
This tutorial is by Jayceooi I just added some more stuff to it.
The reason your TWRP is boot looping is its because, you installed a file or zip that cause for your system to corrupt or break. It can also be a file that is in the system that you deleted and rebooted your Kindle to save changes.
How to solve stuck at yellow triangle issue on Kindle Fire?
Via Kindle Fire Utility
1. Connect it to your computer.
2. Select 1 Bootmode Menu.
3. Select 1 Normal (4000).
That’s all.
=============================================
Via Command Prompt
Note – you need to have fastboot.exe (located in Kindle Fire Utility\tools folder)
Bring up Command Prompt.
Go to Kindle Fire Utility\tools folder.
Key in fastboot -i 0×1949 oem idme bootmode 4000 (don’t cut and paste).
Key in fastboot -i 0×1949 reboot (don’t cut and paste).
That’s it.
=========================================================
FQA (Frequently Asked Questions)
My computer won't detect my device. Why is this?
-If it doesn't detect it you need to do the Via Command Prompt.
=========================================================
I don't know how to do the Via Command Prompt part how do you do it?
-Well you can try what I did to my Kindle Fire when it keeps boot looping TWRP
1.Download Kindle Fire Utility
2.Extract it to desktop.
3.You can't connect it while its in FastBoot mode so open up CMD or Command Prompt.
4.Again locate the folder and type it in the CMD for example I typed:
"cd C:\Users\Madaran\Desktop\Kindle Fire Utility\tools"
5.Then type this in "fastboot -i 0x1949 oem idme bootmode 4000"
6.It should say waiting for device. Go to TWRP and hit reboot system.
7.It should work now and while waiting for your Kindle to boot up, the power button should be orange.
8.When it turned orange I immediately typed this in the CMD or Command Prompt
"fastboot -i 0x1949 oem idme bootmode 4000" so it wouldn't boot to the TWRP recovery menu.
9.It should reboot again and load up your CyanogenMod 7 or previous ROM build.
10. If it work hit the thanks button please.
=========================================================
Click to expand...
Click to collapse
I've already made a too0l designed to fix this >.< http://forum.xda-developers.com/showthread.php?t=1428428
Thanks!
This worked perfectly
my kindle fire is stuck on the Kindle Fire screen, with no animation.
i have looked through XDA but could not find anything with my problem.
i do not have TWRP or FFF.
I'm running the stock rom.
kindle is not recognized on ADB.
i uninstalled the driver, but now computer management doesn't have anything for the device listed.
i used the kindle fire utility to install the drivers, still not listed on computer management.
it is recognized in the bottom right as plugged in as a 'android adb interface'
i have tried using the kindle unbrick utility, but it says there is no device plugged in.
EDIT:
i restarted my computer. now the kindle is listed as unknown device in the bottom right and in computer management.
i am still unable to install new driver software on it, though.
EDIT:
I tried using the driver from the .android download, it says that it's not going to work.
if someone could help me, please, it would be great.
EDIT::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
UPDATE TO THE PROBLEM::::
the kindle is still in the kindle fire boot screen brick.
it went from being an 'unidentified device' to being 'android adb interface'
the error code has switched from code 43 to code 10.
it says Device Cannot start (code 10)
it is not recognized by ADB
unbrick utility still doesn't recognize.
neither does kindle fire utitlity.
look above
look above
look above
can someone please help me..
im having the same problem and cant find an answer anywhere we need help guys
maybe this helps:
for the kfu drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or:
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
Click to expand...
Click to collapse
that means:
your kf seems to be in fastboot mode -> adb commands not working
the question is what have you done to come to this situation ?
you can:
- try to switch to normal bootmode
- or try to install fff & twrp (this is done in fastboot mode)
switch to normal boot:
use kfu option 1 - bootmode normal or manually (see above)
when it says <waiting for device> power off the kf by holding the pwr button for ~20sec till it turns off - pwr on again - the command should be resumed and finished - another pwr off/on should bring you back
install fff & twrp:
refer to this post http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
if you can't get rid of the windows drivers:
http://forum.xda-developers.com/showthread.php?t=1430038
Thanks so much I was having this same problem and have been bashing my head against the wall all day. This kind of thing is a little above my paygrade but I'm learning quickly!
I tried to root my kindle through, http://forum.xda-developers.com/showthread.php?p=24128777 , but I got half way and got stuck at the fastboot mode. I don't have recovery or anything because it was a stock 6.3 kindle fire. Does anybody know how to get out of this? The adb isn't recognizing my device right now and I've tried hard resetting.
Any help would be appreciated!
Edit: Is the only way out of this is through a factory cable?
what means got half way ?
you switch to fastboot at a point - then adb commands are not recognized
only fastboot commands are recognized in fastboot mode
would try to issue:
fastboot -i 0x1949 getvar product - it should return "kindle"
if not check your drivers
if you got the drivers working resume with the above manual
about drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Oh. Is that it? . So is it normal for the cmd command "adb devices" to not show the kindle device?
If so, that's a pretty big relief! And all I need to do is type that cmd?
you have a great manual here explaining how the kf works:
http://forum.xda-developers.com/showthread.php?t=1552547
furthermore this one could help you to understand how drivers/bootmode/commands correlate:
http://forum.xda-developers.com/attachment.php?attachmentid=943772&d=1331571368
I'm having a similar problem. I can boot into fastmode but when I try to reboot, it just seems to hang with a <waiting for device> message. I get the same <waiting for device> message if I do the fastboot -i 0x1949 getvar product command.
I am stuck in TWRP and if I hit reboot, the command prompt does return the info.
OK, it appears that the KF didn't update. It was just stuck in some weird boot loop or something. Maybe it was trying to update and couldn't for some reason? I am keeping all this info bookmarked in case something does happen though.