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!!!!!!!!!!
So here's where I'm at. Currently I'm at the fire fire fire logo. Before I could get into TWRP. Ten minutes ago I could see the Kindle Fire after installing the USB Drivers. but all that was listed was TWRP no other dir. I copied over the update.zip to try and go back to stock because the KF wouldn't boot back into C7 after a month of no problems and it wouldn't take the update. When I reconnected it said it needed to format the KF Drive. I accidentally clicked yes. It said couldn't do it and now I cannot see the KF via USB. I have an android google phone device in device manager listed but nothing else after I reinstall the drivers. The KF will no longer boot into TWRP. I think its totally bricked. I dont' even know why. I haven't installed anything in 5 days. Any help is appreciated and worth a $20 amazon gift card from me.
it actually states Adroid ADB Interface in the device manager under Android Phone
Is your device listed when you run "adb devices".
where would i run abd devices?
gbutler288 said:
where would i run abd devices?
Click to expand...
Click to collapse
ABD comes with the Android SDK.
If you have the Android SDK installed, it can be found under :
64bit system :
C:\Program Files (x86)\Android\android-sdk\platform-tools
32bit system :
C:\Program Files\Android\android-sdk\platform-tools
If you don't have the android SDK installed, you can install it using this link :
hxxp://developer.android.com/sdk/index.html
(replace hxxp by http, I'm not allowed to post external links)
gbutler288 said:
where would i run abd devices?
Click to expand...
Click to collapse
If you have downloaded the necessary Android SDK parts which I assume you have if you've installed a recovery and flashed CM7 then the ADB will be found in that SDK directory (well in a directory just off it.
Running this command will enable us to tell you if your Kindle is actually detected.
you can check if its connected in normal or recovery mode by:
adb devices
you can check if its connected in fastboot mode by:
fastboot -i 0x1949 getvar product - it should return "kindle"
from there you could do:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
fastboot oem idme bootmode 4000
fastboot reboot
you should allready have twrp-blaze-2.0.0RC0.img somewhere - if not redownload it
hi im new in this page and i was searching how to unbrick my kindle fire beacause i make 2 big mistake when i was rooting my kindle fire the last week the first was root twice my kindle fire beacuse the kindle was slow and i think i have to restore it to fabric mode and all my documents was erase it and i think ooooh i have too root again my kindle and in that moment i saw the vido of zedomax how root a 6.21 kindle fire and i do all in correct step but when i have to install the twrp my computer didnt let me upgrade the kindle to twrp because my computer recognizes my kindle fire like a android phone and all the step of zedomax erase the frimware of the kindle so i paid to a guy to repair my kindle and he only can install the twrp be didnt upgrade the frimware beacause the twrp didnt find the zip so i used the java kindle fire brick utilities and i uses the option of flash upgrade and now the kindle get stock in the yellow triangle and my coimputer recognizes the kindle fire like unknown device so what can i do for repair that brick? help me please!!!!!!!!!!!!!!!!!!!!!!!
first you have to get rid of your drivers (update manually):
under android phone it has to be "android adb interface"
cause your kf is in fastboot mode now
adb commands will not work in this mode
then you can try to follow this post starting at point 3:
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
but the problem is know because konw my computer reconoigze my kf like unknown system
man the kindle fire isnt in fastboot beacause whe ni type "fastboot -i 0x1949 getvar product" the computer said me "fastboot cant be reconoigze like a command" what i can do please help me
eratos said:
man the kindle fire isnt in fastboot beacause whe ni type "fastboot -i 0x1949 getvar product" the computer said me "fastboot cant be reconoigze like a command" what i can do please help me
Click to expand...
Click to collapse
are you working with the sdk ? - the above message says that you dont have fastboot.exe in your current path - so you cant handle it when it is in fastboot mode.
would recommend to download kfu extract it to c:\ and rename it to "kfu" - now all necessary commands are in c:\kfu\tools - cd with a command promt to c:\kfu\tools and issue the necessary commands
if you have a driver problem you can also use the drivers from kfu - first you can try install_drivers.bat or install them manually - they are in c:\kfu\drivers\kindle
manually updating: http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
if your drivers are correct you can also use kfu - option1 - bootmode normal
I know how to get out of it by tying fastboot -i 0x1949 oem idme bootmode 4000
but when i open kindle fire utility 0.9.5 i try to install firefirefire or twrp but it just reboots and gets stuck on the kindlefire logo. what do i do. i believe i installed all the drivers just like it said
i get a online and 4000 status on the utility.
it says the img has been found in the utility
also i havent even seen a yellow triangle yet
I assume you rooted first...?
jluke86 said:
I assume you rooted first...?
Click to expand...
Click to collapse
yes.
i install the google apps with the utlity and it worked fine
im not sure why i cant get into recoverymode
KFU 0.9.5 does not seem to produce the yellow triangle upon startup. The only way I could enter TWRP was to run the utility again and install TWRP from scratch. 0.9.1 does not have this problem though.
Uninstall your drivers. Reinstall them manually.
Use command prompt to enter fastboot command.
Sent from my Amazon Kindle Fire using xda premium
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.