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!!!!!!!!!!
As mentioned in the guide, Kindle Fire For Beginners (KFFB), fastboot is the key to fixing all software related problems on the Kindle Fire. Regardless of the actual bricking circumstances, the Kindle Fire can be unbricked if the device can be put into fastboot mode. Even in the worst situation, the unbricking steps boil down to...
Get to fastboot mode
Use fastboot flash to install a recovery
Use recovery to flash a bootloader and ROM
Although these points are covered in KFFB, it can be difficult to discern the actual procedures for putting the device into fastboot mode and recognize when it has been enabled. This guide is a more concise presentation, but it assumes at least some basic knowledge discussed in KFFB. If you are unfamiliar with that guide, please read that one first.
WARNING: Multiple users have reported problems with fastboot when using a USB 3.0 port. This is probably a bug in the fastboot program. Move the cable to a USB 2.0 port before using fastboot.
Identifying The Bootloader
Because the bootloader is responsible for enabling fastboot mode, one must be loaded and working properly to issue fastboot commands to the Kindle Fire. To determine which bootloader is booting the device, take note of the bootlogo on the display when it first powers up.
Stock Bootloader - white and orange "kindle fire" logo
FireFireFire (versions 0.9 to 1.2) - yellow triangle with flames
FireFireFire (version 1.3) - white and orange "kindle fire" logo with green android
FireFireFire (version 1.4) - white and blue "kindle fire" logo
Recognizing fastboot mode
The Display - As the bootloader loads up on the device, one of the previously mentioned bootlogos will appear on the display. With fastboot mode enabled, that bootlogo will be persistent and remain bright on the display. If the display blacks out and redisplays the bootlogo with the backlight slightly dimmed, the bootloader has bypassed fastboot mode and moved on in the boot process.
The bootlogo on the display is the easiest way to see whether or not the device is putting itself into fastboot mode. Again, when the device is in fastboot mode, the bootlogo will appear on the display upon start up, never black out, and remain bright on the screen.
The Device Manager - In the Windows Device Manager, "Android Phone -> Android ADB Interface" will appear in the list when the device drivers have loaded properly. If "Other devices -> kindle" (with 'k' in lower case) appears in the list instead, the proper device drivers have not been loaded and the device drivers must be reinstalled.
Hardware IDs - Also in the Windows Device Manager, right-click on whatever interface name appears for the connected device and select "Properties" from the contextual menu. In the window that appears, select "Hardware IDs" from the drop-down menu. When the device is in fastboot mode, one of the following sets of IDs will appear in that window.
Stock Bootloader
USB\VID_1949&PID_0006&REV_0100
USB\VID_1949&PID_0006
FireFireFire Bootloader
USB\VID_18D1&PID_0100&REV_0100
USB\VID_18D1&PID_0100
Windows identifies each USB device by these three numbers, the VID, PID and REV. Only these two sets of hardware identification numbers will appear when the Kindle Fire's bootloader is running. If the numbers differ at all, the bootloader no longer controls the device and therefore not in fastboot mode.
Linux users can use "lsusb -v" to get a list of all connected USB devices. The corresponding IDs are idVendor, idProduct and bcdDevice. Mac OS X users can use "system_profiler SPUSBDataType" and those IDs will be listed as Vendor ID, Product ID and Version in the list. The numbers are formatted slightly different than their Windows counterparts, but it's straightforward to determine what they are.
Methods for Enabling Fastboot Mode
Realistically, there are 3 potential methods of enabling fastboot mode on a working bootloader. There is a 4th method, but it should only be considered as a last ditch effort because the case must be opened for access to the motherboard. Let's cover the first 3 methods...
Factory cable - Using a factory cable is the most straightforward method of enabling fastboot mode on the Kindle Fire and it will work with any bootloader. With the device off, plug the cable into the Kindle Fire, then the computer and the device will boot up directly into fastboot mode. No other user intervention is required.
Temporary fastboot mode - The FireFirefire custom bootloader temporarily enables fastboot mode for a short amount of time. Issuing a fastboot command like...
Code:
fastboot getvar product
to the device during this time will stop the fastboot countdown and enable fastboot mode indefinitely. If the device displays a plain white and orange "kindle fire" logo, the stock bootloader is installed. The stock bootloader does not enable fastboot temporarily, so another method must be used.
Bootmode setting - The Kindle Fire has a bootmode setting that indicates to the bootloader how to proceed in its booting process. One of these bootmodes (4002) will tell the bootloader to enable fastboot mode. The bootmode setting is recognized by all bootloaders, so even the stock bootloader will go into fastboot mode when the bootmode is set to 4002. The only place this feature is likely to be used is from the system software, but there's a catch. The system must be able to provide access to a shell prompt.
For an unrooted stock device, use pokey9000's fbmode.
For a rooted stock device...
Code:
adb shell su -c 'idme bootmode 4002'
For a ROM with built-in root privileges...
Code:
adb shell idme bootmode 4002
If an error message similar to...
exec '/system/bin/sh' failed: No such file or directory (2)appears when attempting to any of the above methods, the system cannot provide shell access. Consequently, the system will not be able to change the bootmode in this manner.
Making the decision
Then the choice of which method to use in order to enable fastboot is simple:
Do you have a factory cable available?
Does the device have a bootloader with temporary fastboot?
Can the device be booted into a system that can grant shell access?
With a working bootloader, the first question to which you can answer in the affirmative is your best choice. If the device does not have a working bootloader or you've answered "no" to all of the above, there's only one option remaining to you. Remove the back cover of the Kindle Fire to get access to the motherboard, short an exposed connection to the metal frame and employ pokey9000's Firekit. This procedure will set the device into USB bootmode and Livekit can upload a fastboot mode enabled bootloader through USB.
Getting out of fastboot mode
To get out of fastboot mode, make sure the bootmode is set to something other than 4002 and reboot the device. The examples below will set the bootmode to normal and reboot the device.
With the stock bootloader...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
With the FFF bootloader...
Code:
fastboot oem idme bootmode 4000
fastboot reboot
If a factory cable was used to enable fastboot mode, it must be disconnected before the bootloader loads again or it will go back into fastboot mode. You can quickly yank the cable after the reboot command has been issued, but it's probably safer to press and hold the power button for around 20 seconds to turn off the device, disconnect the cable, and turn it back on.
Using Fastboot commands and other information
There are many guides related to fastboot. Here are just a handful of starting points...
Installing Windows device drivers for fastboot
A list of fastboot commands
Using fastboot to install TWRP (See "Installing a recovery and custom bootloader")
@kinfauns, can a broken bootloader boot into fastboot with a factory cable?
Gửi từ Kindle Lửa của tôi qua Tapatalk 2
linktohack said:
@kinfauns, can a broken bootloader boot into fastboot with a factory cable?
Gửi từ Kindle Lửa của tôi qua Tapatalk 2
Click to expand...
Click to collapse
No. The bootloader is what enables fastboot mode. The factory cable does not help the situation if the device does not have a working bootloader. Under these circumstances, you must open the case, use the "shorting trick" and upload a bootloader into memory using usbboot.
kinfauns said:
No. The bootloader is what enables fastboot mode. The factory cable does not help the situation if the device does not have a working bootloader. Under these circumstances, you must open the case, use the "shorting trick" and upload a bootloader into memory using usbboot.
Click to expand...
Click to collapse
Thanks, so an advice for normal user is not to mess around with bootloader and double check md5 before flash it.
Gửi từ Kindle Lửa của tôi qua Tapatalk 2
I've rearranged the sections in this guide in a more logical order, clarified a few points and cleaned it up. I've also added a list of hardware IDs that should be fairly foolproof to see whether or not the KF is actually in fastboot mode. A section on how to get out of fastboot mode has also been added.
Excellent guide! Thanks.
Sent from my GT-P1000 using XDA
Thank you so much for this. I have been reading up on fast boot recently and it is a huge help to have it spelled out in one place.
Sent from my Amazon Kindle Fire using Tapatalk 2
Interesting guide. Problem is that it probably doesn't work on newer fires.
Let me explain: So I had my Kindle Fire replaced and following this guide got into fastboot mode (through factory cable in my case). Problem is that once I'm there neither Windows nor Linux recognizes my device. This must be an ailment of newer KFs because the old ones -I remember clearly- could well be recognized while in FB mode.
Any recommendations?
edit: I can't get out (FB mode) right now so I would *really* appreciate any help.
Stevethegreat said:
Interesting guide. Problem is that it probably doesn't work on newer fires.
Let me explain: So I had my Kindle Fire replaced and following this guide got into fastboot mode (through factory cable in my case). Problem is that once I'm there neither Windows nor Linux recognizes my device. This must be an ailment of newer KFs because the old ones -I remember clearly- could well be recognized while in FB mode.
Any recommendations?
edit: I can't get out (FB mode) right now so I would *really* appreciate any help.
Click to expand...
Click to collapse
I have nothing to offer in your immediate situation, but do not use any technique from these forums if you have a KF2.
http://forum.xda-developers.com/showthread.php?t=1930681
Stevethegreat said:
Interesting guide. Problem is that it probably doesn't work on newer fires.
Let me explain: So I had my Kindle Fire replaced and following this guide got into fastboot mode (through factory cable in my case). Problem is that once I'm there neither Windows nor Linux recognizes my device. This must be an ailment of newer KFs because the old ones -I remember clearly- could well be recognized while in FB mode.
Any recommendations?
edit: I can't get out (FB mode) right now so I would *really* appreciate any help.
Click to expand...
Click to collapse
- You are in the wrong forum if you have a 2nd generation KF, but fastboot mode is definitely accessible on them and commands can be issued.
- This guide was written for the original KF, so a great deal of the information here is does not apply to the 2nd generation KF. The custom bootloaders will not work, the hardware ID values are different, the bootmode values are different.
- If you can't get your computer to recognize the device in fastboot mode, it's a problem with the device drivers on Windows or incorrect permissions to access the device on Linux. Both of these are probably caused by the different hardware ID values. You'll need to alter the INF file to match them for Windows and redo your udev rules on Linux. This guide includes the procedure for finding the hardware ID values, you'll have to look at some other guides for applying them.
- If you used the factory cable to enter fastboot mode, all you need to do is force the device off, disconnect the factory cable and reboot. If you changed the bootmode on a 2nd generation device, you're on your own. The various bootmode values have changed and I don't know what the proper ones are to get it booting normally again.
kinfauns said:
- You are in the wrong forum if you have a 2nd generation KF, but fastboot mode is definitely accessible on them and commands can be issued.
- This guide was written for the original KF, so a great deal of the information here is does not apply to the 2nd generation KF. The custom bootloaders will not work, the hardware ID values are different, the bootmode values are different.
- If you can't get your computer to recognize the device in fastboot mode, it's a problem with the device drivers on Windows or incorrect permissions to access the device on Linux. Both of these are probably caused by the different hardware ID values. You'll need to alter the INF file to match them for Windows and redo your udev rules on Linux. This guide includes the procedure for finding the hardware ID values, you'll have to look at some other guides for applying them.
- If you used the factory cable to enter fastboot mode, all you need to do is force the device off, disconnect the factory cable and reboot. If you changed the bootmode on a 2nd generation device, you're on your own. The various bootmode values have changed and I don't know what the proper ones are to get it booting normally again.
Click to expand...
Click to collapse
I don't think I'm on 2nd Gen KF, I got mine pretty much by replacing my dying KF (1st gen), so I can't see how I could end up with 2nd gen.
But say I am as you correctly pointed out Fastboot should had worked, problem is that it never did.
The reason that I'm stuck (on FB) right now is that I had though that it was because of the cable why I was unable to get properly into Fastboot, so I used a dif. method.
edit: The hardware ID is:
USB\VID_1949&PID_0006&REV_0100
USB\VID_1949&PID_0006
So I'm definately on first gen, so back to my orginal question why the heck my KF is not recognized (in either Windows or Linux, I've tried both multiple times)?
edit2: Well, to make matters worse upon booting my Fire is recognized (so the drivers are correct) but when I'm trying to do anything, anything at all, the device does not respond. So I reconnect the usb cable and this time around I get "unknown device" in Windows and in Linux -well- I pretty much get nothing, as if the device was never there. I fear that my replacement is not exactly in working order, unless there's something major I'm missing. I literally did nothing else apart from trying to get into FB since I got the device out of its package...
Stevethegreat said:
I don't think I'm on 2nd Gen KF, I got mine pretty much by replacing my dying KF (1st gen), so I can't see how I could end up with 2nd gen.
But say I am as you correctly pointed out Fastboot should had worked, problem is that it never did.
The reason that I'm stuck (on FB) right now is that I had though that it was because of the cable why I was unable to get properly into Fastboot, so I used a dif. method.
edit: The hardware ID is:
USB\VID_1949&PID_0006&REV_0100
USB\VID_1949&PID_0006
So I'm definately on first gen, so back to my orginal question why the heck my KF is not recognized (in either Windows or Linux, I've tried both multiple times)?
Click to expand...
Click to collapse
Yes, that is the original KF. Almost every one of these cases is related to device drivers on Windows. I suggest you read/follow this...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
If that doesn't help, you should try Linux which is not as temperamental when it comes to fastboot mode. You might want to try soupkit to get your Linux environment configured properly. Whatever route you choose, you need to try rebooting the KF at least once in a while. Your computer and KF need to see each other the moment the KF goes into fastboot mode. If that doesn't happen, nothing you do after that will matter.
If you continue to have problems, post in the Q&A forum. Someone hanging out there will help you.
Naturally I did those before posting here (if you read my post you'd see that I'm talking about Linux), I've posted about Windows so that I'd make my situation more relevant to most people's experiences with those things...
Obviously my situation is out of the ordinary (or else -again- I woudln't post here). Anyway, I'd try the Q&A hoping that I'd find answers there, but I insist my problem is most probably hardware (if it was SW I would had found a solution until now, me thinks).
@ kinfauns,
Do you have some way of posting a video of what Fastboot mode looks like when launched via a Factory Cable please? I have had many people tell me its booting up but not into Fastboot mode, however I have been under the impression that the KF splash screen logo means its in Fastboot mode already.
A few weeks ago someone told me his device was not passing the initial splash screen then a few days later he tells me it was his computer at fault and that it was already in Fastboot mode and that my Factory Cable worked perfectly for him. Now today another individual is telling me the exact same thing, its not passing the initial splash screen and that Fastboot on his computer does not see the device. I have been under the impression that if Fastboot does not communicate with the KF, then the computer/drivers etc is possibly at fault.
So, I am wondering what the KF's Fastboot mode screen looks like as I have never personally seen it, only has it been described to me as the KF logo screen. lol
Thanks man...
SkOrPn said:
@ kinfauns,
Do you have some way of posting a video of what Fastboot mode looks like when launched via a Factory Cable please? I have had many people tell me its booting up but not into Fastboot mode, however I have been under the impression that the KF splash screen logo means its in Fastboot mode already.
A few weeks ago someone told me his device was not passing the initial splash screen then a few days later he tells me it was his computer at fault and that it was already in Fastboot mode and that my Factory Cable worked perfectly for him. Now today another individual is telling me the exact same thing, its not passing the initial splash screen and that Fastboot on his computer does not see the device. I have been under the impression that if Fastboot does not communicate with the KF, then the computer/drivers etc is possibly at fault.
So, I am wondering what the KF's Fastboot mode screen looks like as I have never personally seen it, only has it been described to me as the KF logo screen. lol
Thanks man...
Click to expand...
Click to collapse
That would be a pretty boring video.
This is what I would suggest people do with their factory cable...
1) Shut down the Kindle Fire completely (press/hold the power button for ~20 seconds if necessary).
2) Plug the factory cable into the Kindle Fire.
3) Plug the other end into the computer.
4) Watch the display.
One of the following should happen...
a) The initial bootlogo never appears on the display.
b) The initial bootlogo comes up at full brightness on the display, then dims or blacks out completely.
c) The initial bootlogo comes up at full brightness on the display and remains that way.
and here's what that probably means...
a) The bootloader is missing or not working properly. The factory cable won't help here. See Firekit, Soupkit, and usbboot.
b) This shouldn't happen with a factory cable, so it's the only case where you need to worry about a faulty factory cable.
c) The Kindle Fire is in fastboot mode. That's all that's supposed to happen on the display (for a 1st generation Kindle Fire).
All of the above are completely independent of whether or not the computer is communicating properly with the KF. The cable by itself will tell the bootloader to go into fastboot mode when it powers up. So, if it's "not passing the initial splash screen" with the factory cable, that means the cable is doing its job. The issue of the computer not being able to see the KF once it's been put into fastboot mode is a device driver problem 99% of the time. That has nothing to do with the factory cable.
On a side note, the 7" Kindle Fire HD has a distinctive fastboot logo that comes up when it goes into fastboot mode. I'm guessing the KF2 also has this feature, but I haven't seen any confirmation of it.
Wow, thanks for the detailed reply. This should help a LOT to narrow down the problems that a very small few of Factory Cable users have had...
As always, thanks again man... :good:
kinfauns said:
No. The bootloader is what enables fastboot mode. The factory cable does not help the situation if the device does not have a working bootloader. Under these circumstances, you must open the case, use the "shorting trick" and upload a bootloader into memory using usbboot.
Click to expand...
Click to collapse
how would one go about doing this?
jparnell8839 said:
how would one go about doing this?
Click to expand...
Click to collapse
In the OP is a link to pokey9000's Firekit post. It has the necessary software attached and contains details for the process. You'll need to use Linux. If you don't have a Linux box readily available, Soupkit might be the least painful way to get there. You can find Soupkit in the Development subforum.
kinfauns said:
As mentioned in the guide, Kindle Fire For Beginners (KFFB), fastboot is the key to fixing all software related problems on the Kindle Fire. Regardless of the actual bricking circumstances, the Kindle Fire can be unbricked if the device can be put into fastboot mode. Even in the worst situation, the unbricking steps boil down to...
Get to fastboot mode
Use fastboot flash to install a recovery
Use recovery to flash a bootloader and ROM
Although these points are covered in KFFB, it can be difficult to discern the actual procedures for putting the device into fastboot mode and recognize when it has been enabled. This guide is a more concise presentation, but it assumes at least some basic knowledge discussed in KFFB. If you are unfamiliar with that guide, please read that one first.
WARNING: Multiple users have reported problems with fastboot when using a USB 3.0 port. This is probably a bug in the fastboot program. Move the cable to a USB 2.0 port before using fastboot.
Identifying The Bootloader
Because the bootloader is responsible for enabling fastboot mode, one must be loaded and working properly to issue fastboot commands to the Kindle Fire. To determine which bootloader is booting the device, take note of the bootlogo on the display when it first powers up.
Stock Bootloader - white and orange "kindle fire" logo
FireFireFire (versions 0.9 to 1.2) - yellow triangle with flames
FireFireFire (version 1.3) - white and orange "kindle fire" logo with green android
FireFireFire (version 1.4) - white and blue "kindle fire" logo
Recognizing fastboot mode
The Display - As the bootloader loads up on the device, one of the previously mentioned bootlogos will appear on the display. With fastboot mode enabled, that bootlogo will be persistent and remain bright on the display. If the display blacks out and redisplays the bootlogo with the backlight slightly dimmed, the bootloader has bypassed fastboot mode and moved on in the boot process.
The bootlogo on the display is the easiest way to see whether or not the device is putting itself into fastboot mode. Again, when the device is in fastboot mode, the bootlogo will appear on the display upon start up, never black out, and remain bright on the screen.
The Device Manager - In the Windows Device Manager, "Android Phone -> Android ADB Interface" will appear in the list when the device drivers have loaded properly. If "Other devices -> kindle" (with 'k' in lower case) appears in the list instead, the proper device drivers have not been loaded and the device drivers must be reinstalled.
Hardware IDs - Also in the Windows Device Manager, right-click on whatever interface name appears for the connected device and select "Properties" from the contextual menu. In the window that appears, select "Hardware IDs" from the drop-down menu. When the device is in fastboot mode, one of the following sets of IDs will appear in that window.
Stock Bootloader
USB\VID_1949&PID_0006&REV_0100
USB\VID_1949&PID_0006
FireFireFire Bootloader
USB\VID_18D1&PID_0100&REV_0100
USB\VID_18D1&PID_0100
Windows identifies each USB device by these three numbers, the VID, PID and REV. Only these two sets of hardware identification numbers will appear when the Kindle Fire's bootloader is running. If the numbers differ at all, the bootloader no longer controls the device and therefore not in fastboot mode.
Linux users can use "lsusb -v" to get a list of all connected USB devices. The corresponding IDs are idVendor, idProduct and bcdDevice. Mac OS X users can use "system_profiler SPUSBDataType" and those IDs will be listed as Vendor ID, Product ID and Version in the list. The numbers are formatted slightly different than their Windows counterparts, but it's straightforward to determine what they are.
Methods for Enabling Fastboot Mode
Realistically, there are 3 potential methods of enabling fastboot mode on a working bootloader. There is a 4th method, but it should only be considered as a last ditch effort because the case must be opened for access to the motherboard. Let's cover the first 3 methods...
Factory cable - Using a factory cable is the most straightforward method of enabling fastboot mode on the Kindle Fire and it will work with any bootloader. With the device off, plug the cable into the Kindle Fire, then the computer and the device will boot up directly into fastboot mode. No other user intervention is required.
Temporary fastboot mode - The FireFirefire custom bootloader temporarily enables fastboot mode for a short amount of time. Issuing a fastboot command like...
Code:
fastboot getvar product
to the device during this time will stop the fastboot countdown and enable fastboot mode indefinitely. If the device displays a plain white and orange "kindle fire" logo, the stock bootloader is installed. The stock bootloader does not enable fastboot temporarily, so another method must be used.
Bootmode setting - The Kindle Fire has a bootmode setting that indicates to the bootloader how to proceed in its booting process. One of these bootmodes (4002) will tell the bootloader to enable fastboot mode. The bootmode setting is recognized by all bootloaders, so even the stock bootloader will go into fastboot mode when the bootmode is set to 4002. The only place this feature is likely to be used is from the system software, but there's a catch. The system must be able to provide access to a shell prompt.
For an unrooted stock device, use pokey9000's fbmode.
For a rooted stock device...
Code:
adb shell su -c 'idme bootmode 4002'
For a ROM with built-in root privileges...
Code:
adb shell idme bootmode 4002
If an error message similar to...
exec '/system/bin/sh' failed: No such file or directory (2)appears when attempting to any of the above methods, the system cannot provide shell access. Consequently, the system will not be able to change the bootmode in this manner.
Making the decision
Then the choice of which method to use in order to enable fastboot is simple:
Do you have a factory cable available?
Does the device have a bootloader with temporary fastboot?
Can the device be booted into a system that can grant shell access?
With a working bootloader, the first question to which you can answer in the affirmative is your best choice. If the device does not have a working bootloader or you've answered "no" to all of the above, there's only one option remaining to you. Remove the back cover of the Kindle Fire to get access to the motherboard, short an exposed connection to the metal frame and employ pokey9000's Firekit. This procedure will set the device into USB bootmode and Livekit can upload a fastboot mode enabled bootloader through USB.
Getting out of fastboot mode
To get out of fastboot mode, make sure the bootmode is set to something other than 4002 and reboot the device. The examples below will set the bootmode to normal and reboot the device.
With the stock bootloader...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
With the FFF bootloader...
Code:
fastboot oem idme bootmode 4000
fastboot reboot
If a factory cable was used to enable fastboot mode, it must be disconnected before the bootloader loads again or it will go back into fastboot mode. You can quickly yank the cable after the reboot command has been issued, but it's probably safer to press and hold the power button for around 20 seconds to turn off the device, disconnect the cable, and turn it back on.
Using Fastboot commands and other information
There are many guides related to fastboot. Here are just a handful of starting points...
Installing Windows device drivers for fastboot
A list of fastboot commands
Using fastboot to install TWRP (See "Installing a recovery and custom bootloader")
Click to expand...
Click to collapse
I have a kindle fire hd that is recovery boot loop and is not being recognised by my computer, not evn a mouse quik wen connected. PLZ how do I I solve this problem or how do I get it into fastboot mode? Thanx.
lo4b said:
I have a kindle fire hd that is recovery boot loop and is not being recognised by my computer, not evn a mouse quik wen connected. PLZ how do I I solve this problem or how do I get it into fastboot mode? Thanx.
Click to expand...
Click to collapse
You quoted the entire OP. Did you not also read the entire OP?
Methods for Enabling Fastboot Mode
Realistically, there are 3 potential methods of enabling fastboot mode on a working bootloader. There is a 4th method, but it should only be considered as a last ditch effort because the case must be opened for access to the motherboard. Let's cover the first 3 methods...
Factory cable - Using a factory cable is the most straightforward method of enabling fastboot mode on the Kindle Fire and it will work with any bootloader. With the device off, plug the cable into the Kindle Fire, then the computer and the device will boot up directly into fastboot mode. No other user intervention is required.
Temporary fastboot mode - The FireFirefire custom bootloader temporarily enables fastboot mode for a short amount of time. Issuing a fastboot command like...
Code:
fastboot getvar product
to the device during this time will stop the fastboot countdown and enable fastboot mode indefinitely. If the device displays a plain white and orange "kindle fire" logo, the stock bootloader is installed. The stock bootloader does not enable fastboot temporarily, so another method must be used.
Bootmode setting - The Kindle Fire has a bootmode setting that indicates to the bootloader how to proceed in its booting process. One of these bootmodes (4002) will tell the bootloader to enable fastboot mode. The bootmode setting is recognized by all bootloaders, so even the stock bootloader will go into fastboot mode when the bootmode is set to 4002. The only place this feature is likely to be used is from the system software, but there's a catch. The system must be able to provide access to a shell prompt.
For an unrooted stock device, use pokey9000's fbmode.
For a rooted stock device...
Code:
adb shell su -c 'idme bootmode 4002'
For a ROM with built-in root privileges...
Code:
adb shell idme bootmode 4002
If an error message similar to...
exec '/system/bin/sh' failed: No such file or directory (2)appears when attempting to any of the above methods, the system cannot provide shell access. Consequently, the system will not be able to change the bootmode in this manner.
Click to expand...
Click to collapse
Have you tried all of the methods listed above?
"That's a special kind of stupid. The kind that makes me laugh."