Database Users

Kindle Fire Bricked? Please Help! (In panic mode)

I was following the tutorial at http://rootkindlefire.com because the tool wasn't working. I got to the point where I typed in these commands and thats when things went downhill in a hurry.
adb shell
su
idme bootmode 4002
reboot
When it rebooted I was instructed to reinstall the drivers but, this was unsuccessful and I tried to reboot both the device and the computer. Afterwards when I tried to access the device using these commands
adb root
adb remount
It said the device cannot be found.
The device is listed as Android ADB Interface with and exclamation point by it. At this point I have no Idea what to do because it is stuck on the Kindle Fire logo and I think I may have bricked it for good. I hope that someone can help remedy this. I booted it into fast mode to try to install the twrp recovery if that information helps any. I am running windows 7 64 bit.

First, What where you trying to do on the kindle fire? Rooting it or something else?
Second, Do you have TWRP installed on your kindle fire?
PS: Don't freak out yet. Always stay calm there will almost always be a fix.

Search the forums. This has already been covered more than a dozen times.
Sent from my Kindle Fire using xda premium

Don't panic yet. I am guessing you are stuck at the yellow triangle and not the Kindle Fire logo?
To reinstall drivers right click on the device in device manager and point the installation to where you have your kindle device drivers. (should be .android folder)(if you have followed the instructions to root then you already updated those files to contain the Kindle drivers)
Then you need to change out of fast boot mode (4002) back to regular boot mode ((4000)

GBH2 said:
Don't panic yet. I am guessing you are stuck at the yellow triangle and not the Kindle Fire logo?
To reinstall drivers right click on the device in device manager and point the installation to where you have your kindle device drivers. (should be .android folder)(if you have followed the instructions to root then you already updated those files to contain the Kindle drivers)
Then you need to change out of fast boot mode (4002) back to regular boot mode ((4000)
Click to expand...
Click to collapse
I seem to have gotten it working. After several reboots with both devices the KFU finally recognized the device and allowed me to change back to normal boot. Now I dont have to buy my dad a new KF

[Q] Bootloop in TWRP

So unfortunately i clicked reboot into recovery under CM7 and i am now in a bootloop. also unfortunately i dont have my laptop which has everything i already need to just type in the 4000 commmand. im also having difficulty installing the sdk platform 2.3.3 api 10. is there any way for me to get out of the boot loop?

Look here, this might help: http://forum.xda-developers.com/showthread.php?t=1422832

Use the kindle fire utility and reinstall twrp
1 turn kindle off
2 run kindle fire utility
3 install twrp
4 plug in kindle
5 follow instructions on screen
Sent from my Kindle Fire using Tapatalk

[Q] adb won't recognize kindle

i was able to root but now adb won't recognize my kindle. have tried reinstalling the drivers like i found in many threads. they install fine but adb won't recognize kindle. any ideas?

to help further a bit more information would be helful
os/bit of computer ?
rooted - which method ? burritoroot3 ? via patched kfu ?
status of kf ? normal boot - hang ?
fff / twrp or cwm allready installed ?
allready tried cold reset ? holding pwr ~20sec

i had this trouble too
i couldnt get adb to work then out of some miracle it started working after restarting my kindle and installing different usb drivers. i ended up using the nexus s driver and i guess it worked

b63 said:
to help further a bit more information would be helful
os/bit of computer ?
rooted - which method ? burritoroot3 ? via patched kfu ?
status of kf ? normal boot - hang ?
fff / twrp or cwm allready installed ?
allready tried cold reset ? holding pwr ~20sec
Click to expand...
Click to collapse
win7 64bit
rooted burritoroot2
kindle works normal. boot shows fff and then boots up
fff installed. no twrp or cwm (that's my next step if i get this adb thing fixed)
yes already tried cold reset? no difference.

Make sure that Android USB Debugging is enabled (checked) in settings. You could also try going to device manager in Windows and uninstall the kindle fire drivers, then reinstall them, restart computer. Hopefully will work then.

would recommend to use kfu cause there is everything included that you need
http://forum.xda-developers.com/showthread.php?t=1399889
place/extract it to c:\ and rename it to "kfu" - it don't like spaces in pathname
patch it for use with burritoroot3
http://forum.xda-developers.com/showpost.php?p=21749205&postcount=792
Follow these steps to set driver verification levels:
1.Press [Windows]Break to display the System Properties dialog box.
2.Select the Hardware tab and click the Driver Signing button in the Drivers panel.
3.Select the Block-Never Install Unsigned Driver Software button. (Verify that the Make This Action The System Default check box is selected.)
4.Click OK twice.
try to install the included drivers by running install_drivers.bat
if it does'nt work try to update them manually:
http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41
the drivers are in c:\kfu\drivers\kindle
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
also check adb_usb.ini in your .android folder in your personal folder
it should include 0x1949 and 0x18D1 - if not add it in a new line
also unplug, restart of kf & computer and replug sometimes helps ...

[resolved] cannot recognize usb driver after showing fire icon

If your kindle fire bricked after flashing nipad firmware or other firmware.you will see below two issues.
1.pc show kindle in device manager，can not install driver.
2.kindle fire show yellow fire logo in screen.
I think the kindle fire is under recovery mode(5002). So, You just change the boot mode to normal boot(4000). you can fix it.
how to fix：
1.find your adb driver files，select usbwin.inf to find kindle fire vid and pid.it is replaced 0x18d1 and 0x0100.after saving usbwin.inf you can install the driver
2.after installing，replug your usb cable.
3.you can type fastboot cmd to unbrick. some thing like fastboot oem idme bootmode 4000.
maybe you will see unknow device.this issue belong power key.if your kindle fire was power off，you will only see kindle in device manager.
After reading，do it！no bricks will appear.

good info thx for your post

does anyone have this issue?

Important
before do any fix brick or flash firmware. Please use the normal cable to charge your kindle fire at first. The 950ma charger is best. You charging time is 6-8H(battery empty). most confuse case can be solved!

xiaohewu said:
If your kindle fire bricked after flashing nipad firmware or other firmware.you will see below two issues.
1.pc show kindle in device manager，can not install driver.
2.kindle fire show yellow fire logo in screen.
I think the kindle fire is under recovery mode(5002). So, You just change the boot mode to normal boot(4000). you can fix it.
how to fix：
1.find your adb driver files，select usbwin.inf to find kindle fire vid and pid.it is replaced 0x18d1 and 0x0100.after saving usbwin.inf you can install the driver
2.after installing，replug your usb cable.
3.you can type fastboot cmd to unbrick. some thing like fastboot oem idme bootmode 4000.
maybe you will see unknow device.this issue belong power key.if your kindle fire was power off，you will only see kindle in device manager.
After reading，do it！no bricks will appear.
Click to expand...
Click to collapse
I was looking at this device driver distribution hoping to find something in here that would help people having fastboot problems. When compared to the set of files you'd get in KFU, this one is missing a couple of DLL files and some adb hardware IDs in the INF file.
I think most people would have already installed from KFU or used directions to install from SDK before looking at this set because in most cases, you'd need the adb drivers before the fastboot drivers. Maybe I'm just not understanding why you'd want to just install only the fastboot drivers and skip the adb ones?

kinfauns said:
I was looking at this device driver distribution hoping to find something in here that would help people having fastboot problems. When compared to the set of files you'd get in KFU, this one is missing a couple of DLL files and some adb hardware IDs in the INF file.
I think most people would have already installed from KFU or used directions to install from SDK before looking at this set because in most cases, you'd need the adb drivers before the fastboot drivers. Maybe I'm just not understanding why you'd want to just install only the fastboot drivers and skip the adb ones?
Click to expand...
Click to collapse
The method is not adb driver. it's only recovery mode fastboot driver. and donot need type -i 0x1949.

?
xiaohewu said:
If your kindle fire bricked after flashing nipad firmware or other firmware.you will see below two issues.
1.pc show kindle in device manager，can not install driver.
2.kindle fire show yellow fire logo in screen.
I think the kindle fire is under recovery mode(5002). So, You just change the boot mode to normal boot(4000). you can fix it.
how to fix：
1.find your adb driver files，select usbwin.inf to find kindle fire vid and pid.it is replaced 0x18d1 and 0x0100.after saving usbwin.inf you can install the driver
2.after installing，replug your usb cable.
3.you can type fastboot cmd to unbrick. some thing like fastboot oem idme bootmode 4000.
maybe you will see unknow device.this issue belong power key.if your kindle fire was power off，you will only see kindle in device manager.
After reading，do it！no bricks will appear.
Click to expand...
Click to collapse
how can i find the adb driver files?

visitor831 said:
how can i find the adb driver files?
Click to expand...
Click to collapse
in this mode, can not use adb. If the kf was booted, you can use the adb. below is the adb driver.

[HELP!] Halfbricked my Kindle Fire HD 7. Can only access TWRP.

Hello,
Yesterday i tried to load a Cyanogenmod custom Rom on my Kindle Fire HD (7") and followed an instruction to do so. I rooted the Device via ADB and FlashFire11. The KindleFireFirstAide tool was part of the tutorial but i didn't really understand how to use it. However, in FireFlash11 i installed a file called kfhd7-freedom-boot-7.4.3.img as the main Boot section and a file called kfhd7-twrp-2.4.4.0-recovery.img as recovery section. Before that i put a file with the custom ROM (cm-10.2-20131115-UNOFFICIAL-tate) on the sdcard.
Everything worked fine (after some troubleshooting) and finally i booted with that blue "Kindle Fire"-symbol. In the TWRP (v2.4.4.0) menu i installed the custom ROM. everything worked fine. Android loaded safely.
My mistake was that i wanted to install a new version of the cyanogenmod (cm-11-20131126-UNOFFICIAL-tate.zip). I wiped all the userdata and tried to insall it via TWRP. But this time it said "Fail".
Now i have no ROM installed. The Device will only boot into TWRP.
The only ROM i have saved to the SDcard is the failing ROM. Under the point "reboot" in the TWRP menu i can choose "Bootloader" wich works.
I desperately tried figuring out how to get the files from a working ROM on the device to install it via TWRP, but i cant access the device via ABD. But one thing does work: If i set the device to "Bootloader"-Mode, i can access it via KFFirstAide. With option 10 of the KFFA i can reboot the Kindle in normal mode. This proofs to me, that i can access the Device in a way. Isn't it possible to send the working ROM Data to the Device via Fastboot?
Sorry for my limited knowledge in this area. And sorry for my bad English, i'm from germany
Would be so nice if anyone could help me. If you need more information on my case i will post it immediately.
For clarification:
I need to know how i can load a custom ROM on the Device to Flash the Device Succesfully. Unfortunately the Device doesn't appear in the Drive Selection of my Windows (8.1). In the Device Manager it is featured as "Kindle Fire HD 7" with a little triangle. During boot the Kindle appears for short period of time as ADB-Device.
I need access to the SDcard of the device to load the working ROM on it. But how do i get access?
EDIT2:
I found a thread about fastboot commands. There is a command as following: fastboot -i 0x1949 update <filename>. Is this a way to install a ROM using fastboot, or is there no way to install a ROM via fastboot?
SOLVED:
I found out that the device had to be accessable (ADB) while in recovery. So looked at my ADB drivers. in a thread there was posted, that TWRP 2.4.4.0 is to old for the newest ADB-driver (which i had installed). So i installed older ADB drivers. Then the device was recognized as ADB Interface. I used the command "adb push" to load the working files to the sdcard. In TWRP installed the Cyanogenmod and now everything boots and works fine
thanks

Did you have the Kindle Fire HD 7 from Year 2013?
If yes how you do this? I AM TO FROM GERMANY!! Can you answer please on german PN?

Arti96 said:
Did you have the Kindle Fire HD 7 from Year 2013?
If yes how you do this? I AM TO FROM GERMANY!! Can you answer please on german PN?
Click to expand...
Click to collapse
got no pn

Arti96 said:
Did you have the Kindle Fire HD 7 from Year 2013?
If yes how you do this? I AM TO FROM GERMANY!! Can you answer please on german PN?
Click to expand...
Click to collapse
Only root exists for the 2013 KFHD7 at this time. No custom ROM's yet.