Database Users

Unbricking Kindle stuck at Boot Logo/Recovery loop

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!!!!!!!!!!

[Q] Kindle Fire 6.3 in FFF Recovery Loop, Not Detected -- Need Help [Linux]

Hey guys,
I'm sorry I couldn't figure out what to do next simply by searching your forum, so I will try to be both as brief and as descriptive as possible.
I started here (http://forum.xda-developers.com/showthread.php?t=1568340) trying to root my fiancee's KF 6.3. I didn't feel comfortable using KFU or similar because those programs are built for Windows and I am using Linux. The Kindle Fire seems to be stuck in a recovery loop. When plugged into USB (using the cable that's actually for my LG Optimus phone), it boots to FireFireFire (yellow triangle) then reboots constantly. At no point is it accessible via adb devices or fastboot, and it doesn't show up under lsusb, which would be the equivalent to not showing up in Device Manager in Windows. (The driver should be fine because all of this was working fine originally when I started the process.)
So I guess my question is what now? I've read a few things about needing a "factory cable" which may set it back into fastboot mode, and I'm pretty sure I could get going again from there. Is that what I need to do? TIA for any help.
PS - I've successfully rooted my LG Optimus S and flashed custom ROMs, so I'm not totally inexperienced. I use Arch Linux and I'm comfortable on the command line. If you have a solution for Windows, I *might* be able to translate it into Linux speak, so don't hold back. Same goes for Ubuntu/Debian - those are totally different than Arch Linux, but I might "get it" enough to translate it.
PPS - I have intentionally omitted information relating to what I was doing when I caused this for brevity, but I would be happy to discuss what steps I took in following the above linked thread if some guru believes it's relevant or someone wants to know.

A factory cable is a last resort kind of thing so I wouldn't jump the gun quite yet, although it doesn't hurt to have one in the first place.
It would be helpful to know which step in the rooting process things went awry. The constant rebooting/restarting isn't typical. Did you make sure you had enough battery before trying to root?
FIREFIREFIRE loads in a temporary fastboot and with the version you are using it lasts for about ten seconds (before the green light goes dim). You can issue fastboot commands during this time without the need of a factory cable.
See if you can get...
fastboot devices
...to be recognized during this time.
Sent from my Amazon Kindle Fire using xda premium

If you get stuck at a screen with a yellow triangle, run: fastboot -i 0x1949 oem idme bootmode 4000 If your device is always booting TWRP run: adb shell "idme bootmode 4000" If you still can't get out of booting TWRP, first run: adb shell "idme bootmode 4002" reboot your device, then run: adb shell "idme bootmode 4000" reboot again and you should be out of your bootloop.
Sent from my LG-VM670 using Tapatalk

It would be helpful to know which step in the rooting process things went awry.
Click to expand...
Click to collapse
OK, let's start with that.
From the thread I linked in the first post:
Your device will now boot into twrp recovery, and flash the firefirefire bootlaoder. When done it will prompt you to reboot. Upon reboot you will get stuck on the "yellow triangle" screen of firefire fire.
Click to expand...
Click to collapse
That was not my experience. My device loaded TWRP but just sat there on its home screen without prompting me to reboot. I used adb reboot recovery to see if it had indeed flashed FFF but was simply not prompting me to reboot, and it had not. So I used instructions from elsewhere (http://forum.xda-developers.com/showthread.php?t=1369405) to flash FFF at this point myself:
Howto flash by hand
Get into fastboot mode somehow. Having and older FFF from the TWRP installer is a good start. Currently KFU or fbmode is the easiest
flash with "fastboot -i 0x1949 flash bootloader u-boot.bin" (take out "-i 0x1949" if FFF is already installed)
disable fastboot: "fastboot -i 0x1949 oem idme bootmode 4000"
reboot: "fastboot -i 0x1949 reboot"
Click to expand...
Click to collapse
There were a couple of weird issues with this but the process seemed to go smoothly. However, when I rebooted (the last command) is when I discovered I was stuck in a recovery loop, and the last time I was able to see the device normally via adb devices/lsusb/dmesg.
I guess it may have been the battery because I've since let it fully charge (this is the first time I've looked at it in days) and now it's not in a recovery loop but stably sitting at the "yellow triangle". There is also now an entry for it in lsusb:
Code:
Bus 002 Device 008: ID 18d1:0100 Google Inc.
fastboot devices gives me something like "no permissions fastboot" but I have no idea what that means because I've never seen its normal output.
EDIT: I should note that I do notice the device ID now seems to register as 0x18d1 rather than 0x1949, but I'm not entirely sure what to do about that. I copied my udev rules but changed '1949' to '18d1' and 'Lab126' to 'Google Inc' but I don't even know if that was a sensible move because I've never really done much with udev rules.

pbailey212 said:
If you get stuck at a screen with a yellow triangle, run: fastboot -i 0x1949 oem idme bootmode 4000 If your device is always booting TWRP run: adb shell "idme bootmode 4000" If you still can't get out of booting TWRP, first run: adb shell "idme bootmode 4002" reboot your device, then run: adb shell "idme bootmode 4000" reboot again and you should be out of your bootloop.
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
I think the problem here is the he can't get past the bootloader and stuck in an ACTUAL bootloop. In which case, adb commands are useless.
One thing that could be causing problems is the USB cable being used. If the device only experiences these symptoms when plugged in then I would say that's most likely the case.
Sent from my Amazon Kindle Fire using xda premium

I suggest you build a firekit USB for Linux. Search for firekit for Linux thread in the development section.
Sent from my Amazon Kindle Fire using Tapatalk 2

palintropos said:
OK, let's start with that.
From the thread I linked in the first post:
That was not my experience. My device loaded TWRP but just sat there on its home screen without prompting me to reboot. I used adb reboot recovery to see if it had indeed flashed FFF but was simply not prompting me to reboot, and it had not. So I used instructions from elsewhere (http://forum.xda-developers.com/showthread.php?t=1369405) to flash FFF at this point myself:
There were a couple of weird issues with this but the process seemed to go smoothly. However, when I rebooted (the last command) is when I discovered I was stuck in a recovery loop, and the last time I was able to see the device normally via adb devices/lsusb/dmesg.
I guess it may have been the battery because I've since let it fully charge (this is the first time I've looked at it in days) and now it's not in a recovery loop but stably sitting at the "yellow triangle". There is also now an entry for it in lsusb:
Code:
Bus 002 Device 008: ID 18d1:0100 Google Inc.
fastboot devices gives me something like "no permissions fastboot" but I have no idea what that means because I've never seen its normal output.
EDIT: I should note that I do notice the device ID now seems to register as 0x18d1 rather than 0x1949, but I'm not entirely sure what to do about that. I copied my udev rules but changed '1949' to '18d1' and 'Lab126' to 'Google Inc' but I don't even know if that was a sensible move because I've never really done much with udev rules.
Click to expand...
Click to collapse
Make sure your linux environment is set up correctly.
http://forum.xda-developers.com/showthread.php?t=1475740
Installing TWRP 2.0.0 is different than installing TWRP 2.1.0. I think the instructions on the TWRP site is for the old version, but they link the new one.
http://forum.xda-developers.com/showpost.php?p=24732291&postcount=1298
Your OP sounds suspiciously like a dead battery, but you say you've corrected that. You might want to connect to your OEM charger for a while anyway and see if that helps
Also, in my experience, fastboot on linux required elevated privileges. Try running it as root.

Make sure your linux environment is set up correctly.
http://forum.xda-developers.com/show....php?t=1475740
Click to expand...
Click to collapse
I've done the Arch Linux equivalents of all of that, and I'm set up with udev rules per our wiki here: https://wiki.archlinux.org/index.php/Android#Adding_udev_Rules
I'm pretty sure the USB cable I'm using might actually be the issue because it was fine straight off the OEM charger, and I even momentarily got a correct reading with fastboot devices (as root), but now I'm back to almost like earlier. The yellow triangle screen is still "stuck"/stable, but I can't find it on adb/fastboot devices or lsusb.

palintropos said:
EDIT: I should note that I do notice the device ID now seems to register as 0x18d1 rather than 0x1949, but I'm not entirely sure what to do about that. I copied my udev rules but changed '1949' to '18d1' and 'Lab126' to 'Google Inc' but I don't even know if that was a sensible move because I've never really done much with udev rules.
Click to expand...
Click to collapse
This is fine. It just indicates you are running the FFF bootloader... pokey9000 changed the VID to a value fastboot recognizes by default instead of the custom vendor ID (1949) that Amazon uses in the stock bootloader. With the FFF bootloader, you can drop the "-i 0x1949" part of the fastboot command.
---------- Post added at 12:30 PM ---------- Previous post was at 12:27 PM ----------
palintropos said:
I've done the Arch Linux equivalents of all of that, and I'm set up with udev rules per our wiki here: https://wiki.archlinux.org/index.php/Android#Adding_udev_Rules
I'm pretty sure the USB cable I'm using might actually be the issue because it was fine straight off the OEM charger, and I even momentarily got a correct reading with fastboot devices (as root), but now I'm back to almost like earlier. The yellow triangle screen is still "stuck"/stable, but I can't find it on adb/fastboot devices or lsusb.
Click to expand...
Click to collapse
Have you tried setting the bootmode to normal and rebooting?
fastboot oem idme bootmode 4000
fastboot reboot
Like I said before, it would probably be best for you to try this as root.
EDIT: It's also possible your system is broken and the KF can't complete its boot process. When you start up the device, the boot logo will first come up. Does the display go black after that and come back with a dimmer yellow triangle logo? Because if it's doing that, it's not in fastboot any more.

kinfauns said:
This is fine. It just indicates you are running the FFF bootloader... pokey9000 changed the VID to a value fastboot recognizes by default instead of the custom vendor ID (1949) that Amazon uses in the stock bootloader. With the FFF bootloader, you can drop the "-i 0x1949" part of the fastboot command.
Click to expand...
Click to collapse
Ditto. If you can get the device to be recognized even for a second, it's still enough time to issue...
fastboot -i 0x1949 oem idme bootmode 4000
Just keep trying
[Edit:] or what he said
Sent from my Amazon Kindle Fire using xda premium

Yay! I played around and got my udev rules working, and I got a reading on (sudo) fastboot devices, so I was finally able to set the bootmode to 4000 and reboot. Everything seems to be back to normal now. The Kindle appears to be working fine though not rooted.
Please let me know:
if there is anything else I should know to make sure the KF is normal
if there is any additional info I should post to benefit other users who might have this same problem
or if I should mark this thread SOLVED/RESOLVED or equivalent and how to do so.

if your fastboot ever stucks in waiting for device mode and you are on linux
try once with either root user or using sudo command.
thats one of the thing people forget most of the time and get stuck there.

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

Try the above with the kindle switched off you should see waiting for devic, then press power once ( fast boot should kick in when you power on)
Sent from my Amazon Kindle Fire using xda premium

can't enter TWRP on Kindle HD 7

I'm in need of help. I believe I was successfully installed the 2nd bootloader and TWRP. However, after having been once in TWRP and made back up of the Kindle, on boot up I can't seem to enter TWRP. I hold the Volume up button until the logo turn blue and let go, but it default back on to the normal logo and enter into the Kindle. What could be the problem?

Try booting into the kindle os, install a mobile terminal or use an adb shell and run
Code:
su -c 'reboot recovery'
this should force it to reboot into recovery.
Sent from my Amazon Kindle Fire HD using xda app-developers app

stunts513 said:
Try booting into the kindle os, install a mobile terminal or use an adb shell and run
Code:
su -c 'reboot recovery'
this should force it to reboot into recovery.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
Thank you! that did the trick.

Can't enter TWRP either abd shell command didn't work
Hi,
I was following the guide from the cyanogen mod website "Install_CM_for_tate" and after selecting the optional Backup, which ran through w/o errors, I was asked to restart and since then, I can't enter TWRP anymore.
I tried the adb shell command as suggested earlier in this thread but get an error 'device not found'. I though adb doesn't work in fastboot mode, why should I use it then?
Device is Kindle Fire HD 7, 3rd gen., 2012 (Tate)
fastboot -i 0x1949 getvar product
returns the product

"fastboot -I 0x1949 reboot bootloader" might do it, or you could just hold volume down as soon as you power on the kindle and keep holding it till you see twrp logo.

Kindle rom wiped - adb device offline

I had a rooted kindle fire hd with CM rom. Wanted to update rom to kitkat. In TWRP, wiped everything, cache, data, system and dalvik.
I rebooted the recovery, so i can sideload the rom files thru adb. But the kindle is stuck at blue kindle fire logo.
If i try adb, it says device offline and no command works. Tried kindle fire firstaide, it is stuck when starting daemon.
Any way to bring it to life?

sam298 said:
I had a rooted kindle fire hd with CM rom. Wanted to update rom to kitkat. In TWRP, wiped everything, cache, data, system and dalvik.
I rebooted the recovery, so i can sideload the rom files thru adb. But the kindle is stuck at blue kindle fire logo.
If i try adb, it says device offline and no command works. Tried kindle fire firstaide, it is stuck when starting daemon.
Any way to bring it to life?
Click to expand...
Click to collapse
something similar happened to me yesterday,
have you tried getting into twrp manually ? sometimes it takes a while to boot into recovery id give it 15 to 20 seconds holding the vol+ button. if you cant get into twrp, you might have to use the system restore tool, but let me know if you can get into twrp first.

When it went to fastboot mode just before this happened, I pushed twrp.img thru PC and rebooted hoping I can get to recovery. Tried power vol+ for several seconds, starts with orange logo and then blue logo then stuck at black screen.
Not sure if I can send to amazon with blue logo showing up.
Sent from my Nexus 7 using Tapatalk

That should still be fixable from fastboot if you can't get it into recovery... No reason to send it back to amazon.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
That should still be fixable from fastboot if you can't get it into recovery... No reason to send it back to amazon.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Is there any way to get into fastboot mode? I tried vol - and power for a minute and also vol + and power. If i enter adb devices, i see the device but it says offline. If i use fastboot devices command, no devices are seen. PC shows it as Kindle but can't access its storage.

If the logo turns blue you can get it into fastboot without a fastboot cable, otherwise you will need a fastboot cable, unless he device is a 8.9" model. Which model do you have? Also doing it without a fastboot cable would probably be easier from Linux if you never installed the fastboot drivers on windows because the device will only show up for a brief second and then disappear, and I will state this now in case you don't know, adb commands do not work with fastboot mode, you use fastboot commands with fastboot mode. I recommend a Ubuntu 13.10 live CD and then telling it to install the fastboot package in the Ubuntu software center and running "fastboot -i 0x1949 getvar product" from a terminal with the device in plugged and powered off, and when it says waiting for device, plug the kindle in and you should be able to get into fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

I have a 7". Thanks for the tip, i finally was able to boot into the system. I downloaded ubuntu but thought of trying it in windows. The only fastboot command that worked is the getvar product you mentioned. The part i missed is, enter the command and then plug the powered off kindle. Finally got into the fastboot logo.
After that none of the other fastboot command worked - said waiting for device. But kffirstaide worked luckily. I pushed 7.2.3 into the kindle and kindle is back working.
stunts513 said:
If the logo turns blue you can get it into fastboot without a fastboot cable, otherwise you will need a fastboot cable, unless he device is a 8.9" model. Which model do you have? Also doing it without a fastboot cable would probably be easier from Linux if you never installed the fastboot drivers on windows because the device will only show up for a brief second and then disappear, and I will state this now in case you don't know, adb commands do not work with fastboot mode, you use fastboot commands with fastboot mode. I recommend a Ubuntu 13.10 live CD and then telling it to install the fastboot package in the Ubuntu software center and running "fastboot -i 0x1949 getvar product" from a terminal with the device in plugged and powered off, and when it says waiting for device, plug the kindle in and you should be able to get into fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse

sam298 for future, encase you cant get into fastboot, this adapter will get you there and you can use your regular usb power cable with it so you have a factory cable at all times, especially since you have a kindle. i bought 2 of these cause why not they were $9.00 dollars each. and no i dont make anything from these, i just seen it on hashcodes post and thought it would be good to buy one encase i need to put something in fastboot. i got mine and fast, took only a few days to get it from this guy.
http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm

Kindle Fire HD (3rd Generation) Bootloader Unlock and TWRP

Code:
#include <std/disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will amputate it with
* a piece of rusty metal. Unless it kills your cat, in which case I shall apologise
* for your loss.
*/
This is for the 2013 Kindle Fire HD (3rd Generation) "soho" or KFSOWI. Please follow the instructions below very carefully. These instructions WILL change, ensure you keep up to date.
First, download and extract the attachment (exploit.zip) into a folder. Then you need to download Fire OS 4.5.5.1 and SuperSU into that folder. Check the MD5 sums!
Although not recommended, if your Fire is rooted, you can enter fastboot mode without a fastboot cable. Using a fastboot cable covers you against most cases of bricking your device. Not using one increases the likelihood.
To use this totally unsupported, unsafe method of accessing fastboot mode, run
Code:
adb shell su -c "dd if=/dev/zero of=/dev/block/platform/omap_hsmmc.1/by-name/boot bs=1 count=1 seek=848"
adb reboot
Make sure you have the latest version of adb and fastboot and that you have installed drivers for the Fire (if you run an inferior operating system). Boot into Fire OS and ensure you have a good charge on the device. Connect the device with a fastboot cable and enter fastboot mode.
Run
Code:
fastboot -i 0x1949 oem format
fastboot -i 0x1949 flash boot hijack.img
fastboot -i 0x1949 flash system system.img
fastboot -i 0x1949 continue
Now wait for the Amazon logo with the orange underline and run
Code:
fastboot -i 0x1949 flash boot recovery.img
fastboot -i 0x1949 oem format
fastboot -i 0x1949 continue
Now wait for TWRP to load up and go into Advanced -> ADB Sideload and tick the two boxes (Wipe Dalvik Cache and Wipe Cache) then swipe the slider (Swipe to Start Sideload). Return to your terminal and run (changing the filename, if necessary)
Code:
adb sideload [B]update-kindle-11.4.5.5_user_455002120.bin[/B]
Now wait for TWRP to finish flashing and press Back then go into ADB Sideload and swipe the slider (Swipe to Start Sideload). Return to your terminal and run (changing the filename, if necessary)
Code:
adb sideload [B]UPDATE-SuperSU-v2.46.zip[/B]
If you want to, you can download the Google Apps and flash them in a similar manner. Google Apps will cause issues with Fire OS if you perform a factory reset! You have been warned.
Now wait for TWRP to finish flashing, remove the fastboot cable and press Reboot System. When the device has booted, reinsert the cable and run
Code:
adb push recovery.img /sdcard/recovery.img
adb shell su -c "dd if=/sdcard/recovery.img of=/dev/block/platform/omap_hsmmc.1/by-name/recovery"
adb push exploit.img /sdcard/exploit.img
adb shell su -c "dd if=/sdcard/exploit.img of=/dev/block/platform/omap_hsmmc.1/by-name/exploit"
adb shell rm /sdcard/recovery.img /sdcard/exploit.img
To boot into recovery, power off the device and hold the volume button [ - ] then push the power button (you may need to do this more than once). When the Amazon logo appears, release the volume button.
Please could any testers report back with results, and which model they have (pictures of it running TWRP would be nice). If you have any problems, also include your entire terminal session and any errors TWRP gives when flashing. You shan't recieve help otherwise. If you are inexperienced, please wait for other testers to try this method.
Please refrain from mirroring any of the files, just link back to this post.
ROM Developers: you need to add boot.img from the files to the beginning of your ROM's boot.img
XDA:DevDB Information
Kindle Fire HD (3rd Generation) Bootloader Unlock and TWRP, Tool/Utility for the Amazon 7" Kindle Fire HD
Contributors
spudowiar
Version Information
Status: Alpha
Created 2015-12-13
Last Updated 2016-01-01

Reserved

Reserved

Reserved

nice work
To be clear this is for:
[Kindle Fire HD] 3rd Gen/2013
Codename: soho
Model # KFSOWI

sd_shadow said:
nice work
[Kindle Fire HD] 3rd Gen/2013
Codename: soho
Model # KFSOWI
Click to expand...
Click to collapse
I'll start on TWRP soon then I'll post a full unlocking tutorial

Many happy people in soho-land today--thanks!

sd_shadow said:
nice work
To be clear this is for:
[Kindle Fire HD] 3rd Gen/2013
Codename: soho
Model # KFSOWI
Click to expand...
Click to collapse
Yep, KFSOWI. I've tried this on my 8GB one but I'll need someone with a rooted 16GB to confirm something

spudowiar said:
Yep, KFSOWI. I've tried this on my 8GB one but I'll need someone with a rooted 16GB to confirm something
Click to expand...
Click to collapse
I can help, tell me what to do
Sent from my Mi-4c using Tapatalk

http://i.imgur.com/tuMFhAP.jpg

The unlock is released, go to the first post to find out how to install!

Test #1
This is a major accomplishment and all us hackers love you. :good:
I tested and here are some observations/suggestions.
1. Make a backup of your device before starting this exploit.
2. The command "adb reboot" does not reboot into fastboot mode even when connected with fastboot cable.
Try to disconnect fastboot cable, turn off device, and reconnect fastboot cable. Boots into fastboot ok.
Will try from scratch again.

bobcat131 said:
2. The command "adb reboot" does not reboot into fastboot mode even when connected with fastboot cable.
Click to expand...
Click to collapse
does this work?
Code:
adb reboot-bootloader
Sent from my KFFOWI using Tapatalk

Got it!
sd_shadow said:
does this work?
Code:
adb reboot-bootloader
Of course! My bad.
Click to expand...
Click to collapse

I got stucked.
Everything went well until the second oem format command. Thats just not working. I'm using ubuntu in a virtualbox on windows 7, i'll try it tomorrow from my workplace where I have a real ubuntu installation.
I have a 16G version.
the console output:
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 devices
00D306073494080F fastboot
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 oem format
...
OKAY [ 0.052s]
finished. total time: 0.052s
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 flash boot recovery.img
target reported max download size of 1005584384 bytes
sending 'boot' (8192 KB)...
OKAY [ 1.033s]
writing 'boot'...
OKAY [ 0.583s]
finished. total time: 1.616s
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 flash system system.img
target reported max download size of 1005584384 bytes
sending 'system' (6370 KB)...
OKAY [ 0.821s]
writing 'system'...
OKAY [ 0.913s]
finished. total time: 1.734s
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 continue
resuming boot...
OKAY [ 0.004s]
finished. total time: 0.004s
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 oem format
...
FAILED (command write failed (Broken pipe))
finished. total time: 0.002s
[email protected]:/home/bari/SOHO#
Click to expand...
Click to collapse

Test 2 failed.
All went well, until I rebooted to system from TWRP. It booted straight into language select then system settings and no navigation bar or home screen.
Stuck in system settings .
Is this just me or a bug?

bobcat131 said:
This is a major accomplishment and all us hackers love you. :good:
I tested and here are some observations/suggestions.
1. Make a backup of your device before starting this exploit.
2. The command "adb reboot" does not reboot into fastboot mode even when connected with fastboot cable.
Try to disconnect fastboot cable, turn off device, and reconnect fastboot cable. Boots into fastboot ok.
3. The adb reboot recovery command reboots into red triangle options and unable to enter recovery.
Using power button and volume button also boots into red triangle. Needs a fix.
4. Boot into system is not complete. No navigation.
5. Missed the exploit flash, so I will reset and test again.
Click to expand...
Click to collapse
Which model do you have (8GB or 16GB)? I tested these instructions from stock using my fastboot cable, YMMV.
That is probably wise but Amazon provide complete stock images of everything but the system (which can be reconstructed), cache and userdata
"adb reboot" should reboot into fastboot mode since it does a hard reboot, I did this since my fastboot cable (whilst it worked with the "otter2") only allowed one command if it had been plugged into the powered off "soho". I only have access to one fastboot cable and this worked for that one.
That means you didn't flash SuperSU or the recovery (that is the stock recovery)
Not flashing the exploit results in the recovery not booting (the screen would flash red and fastboot would load up on both of the methods you tried), you didn't flash SuperSU or the recovery (the stock recovery booted up)
Rhyn said:
I got stucked.
Everything went well until the second oem format command. Thats just not working. I'm using ubuntu in a virtualbox on windows 7, i'll try it tomorrow from my workplace where I have a real ubuntu installation.
I have a 16G version.
the console output:
Click to expand...
Click to collapse
You were too quick on that command. I wrote "arrow underline" in the instructions, I meant "orange underline". (originally I wrote "orange arrow underline" ) What happened is fastboot reinitialised but was not accepting commands. Also, VirtualBox may take a bit of time (there was a USB disconnect/reconnect). A live CD would be much easier, I avoided putting any Linux commands in here (I have a script to craft the images).
bobcat131 said:
All went well, until I rebooted to system from TWRP. It booted straight into language select then system settings and no navigation bar or home screen.
Stuck in system settings .
Is this just me or a bug?
Click to expand...
Click to collapse
As I said, I tested these instructions from stock. Did you try a factory reset? (You can do a backup in TWRP )
sd_shadow said:
does this work?
Code:
adb reboot-bootloader
Of course! My bad.
Click to expand...
Click to collapse
See above.
Anyway, this is definitely a WIP, I have access to one device and one fastboot cable. You can help iron out any bugs with this method. Thanks for trying!

Booting into TWRP might cause a TWRP bootloop (when you reboot, it boots back into TWRP instead of system). For now, only use TWRP with access to a fastboot cable (so you can go into fastboot and do fastboot -i 0x1949 continue) or you could flash /system/recovery.img to the recovery partition and reboot using the stock recovery - but don't bother!

spudowiar said:
You were too quick on that command. I wrote "arrow underline" in the instructions, I meant "orange underline". (originally I wrote "orange arrow underline" ) What happened is fastboot reinitialised but was not accepting commands. Also, VirtualBox may take a bit of time (there was a USB disconnect/reconnect). A live CD would be much easier, I avoided putting any Linux commands in here (I have a script to craft the images).
Click to expand...
Click to collapse
It was the virtualbox. On my work computer from linux it worked perfectly.
Pictures as you requested http://imgur.com/a/GVr7f

Rhyn said:
It was the virtualbox. On my work computer from linux it worked perfectly.
Pictures as you requested http://imgur.com/a/GVr7f
Click to expand...
Click to collapse
It could be a coincidence (if the first fastboot worked, it must have been VirtualBox reconnecting the USB). But still, good to see it worked