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."
Related
edit: Kindle Fire fastboot working. Allows for reflashing ROMs and booting over USB.
Recommended that you have your kindle already opened so that you can get to the battery cable to hard reset if necessary.
Instructions to follow.
transfuntioner said:
<posting here as i dont have access to devel forum yet>
Looking at the bootloader & the u-boot source, it looks like there's 2 ways to get to fastboot. The bootmode nvram setting, and a special usb cable.. I think I'll go the nvram route though I havent investigated how to set it yet.
Just to be prepared I'm going to add usb driver's inf.
%SingleBootLoaderInterface% = USB_Install, USB\VID_1949&PID_0FFF
So .. anyone else working on this?
Click to expand...
Click to collapse
I dont have a gingerbread build handy, is there another dev that can build me a fastboot.exe to include 0x1949?
I think my fire is stuck in fastboot mode.
transfuntioner said:
I dont have a gingerbread build handy, is there another dev that can build me a fastboot.exe to include 0x1949?
I think my fire is stuck in fastboot mode.
Click to expand...
Click to collapse
NVM on the fastboot.exe request, I have a working one.
fastboot mode is confirmed .. i have a fastboot talking to the fire. It shows up in 'fastboot devices' (the id is 0123456789abcdef), and responds to reboot & boot commands.
Now trying to boot out of fb mode, I should have set the 'other' nvram bootmode
NOTE: Instructions are terse and intended towards developers for now.
Standard disclaimer, I am not liable if you brick your fire.
Requisities:
- working adb, (on windows) with the additional %SingleBootLoaderInterface% entry mentioned
- working fastboot binary that recognizes / allows specifying the vendor id (0x1949)
- root. it may work without, but you probably want or have it already
Also recommended:
- boot.img from the latest sw update.
Procedure:
- get a adb shell
- use the '/system/bin/idme' command to set the bootmode. I suggest you first run 'idme ?' and write down your default, mine is "4000 0".
- if you set bootmode to 0x4002, the fire will stay in fastboot mode when it reboots
- if you set bootmode to 0x4003, it's supposed to timeout from fastboot mode, but I did not have much luck getting a normal boot after the timeout (did not play too much here).
- if you decide you dont want fastboot mode, run 'idme bootmode "4000 0"' to reset back to default for normal booting.
WARNING:
IF YOU REBOOT AT THIS POINT THE FIRE WILL BE IN THE FASTBOOT MODE. I HAVE NOT FOUND A WAY TO EXIT THIS MODE AND RETURN TO THE NORMAL OS WITHOUT A WORKING FASTBOOT CLIENT.
REPEAT:
YOU MAY BE BRICKED IF YOU DONT HAVE WORKING TOOLS.
When you boot into fastboot mode, it will show the "Kindle Fire" logo. The power button does not appear to do anything; therefore, if you boot a bad kernel/image it may get stuck and require a hard reset (pulling the battery cable).
You should now have access to the standard flashboot functionality (update, flash, usb boot, etc). Note that reboot-bootloader will bring you back to fastboot.
I currently use 'fastboot boot boot.img' (from the sw update) to get back to a working state. Once booted, use idme to disable fastboot.
Now, on to recovery's & custom roms!
so any more information on the "special usb cable" like what size resistor on pin 4?
death2all110 said:
so any more information on the "special usb cable" like what size resistor on pin 4?
Click to expand...
Click to collapse
I dont have hardware handy to determine this, but having a cable will definitely make things easier going forward.
Brief updates..
Unlike previously mentioned, it looks like long press power button typically should work.
The idme command is available in the bootloader. So you can set normal bootup mode from fastboot, then reboot. eg.
fastboot oem idme bootmode 4000
fastboot reboot
How to get latest update pack ?
Sent from my SAMSUNG-SGH-I777 using XDA Premium App
any idea what tools i can use to check what amount of resistance i need? I may just go out to the garage and grab 3 100k resistors and try the numerous SGS2 methods (specifically 3 resistors twisted together and jumping pins 4 & 5
Stuck in fastboot
Hello,
I followed these steps including adding the %SingleBootLoaderInterface% line mentions to the usb inf. I was able to get the Kindle Fire to set bootmode to 0x4002.
I downloaded fastboot from here, 32-bit only?
http://forum.xda-developers.com/showthread.php?t=463627
Tried to get fastboot 64-bit via this route, no good:
http://rootzwiki.com/topic/4551-guide-making-fastboot-work-on-64-bit-windows-7-systems/
Now that it's in bootmode, neither my x64 PC or x86 Mac can see the device via a recent fastboot.exe and fastboot-mac application using a standard mini-USB cable. Suggestions? Is there a different fastboot.exe that I should be using?
transfuntioner said:
NOTE: Instructions are terse and intended towards developers for now.
Standard disclaimer, I am not liable if you brick your fire.
Requisities:
- working adb, (on windows) with the additional %SingleBootLoaderInterface% entry mentioned
- working fastboot binary that recognizes / allows specifying the vendor id (0x1949)
- root. it may work without, but you probably want or have it already
Also recommended:
- boot.img from the latest sw update.
Procedure:
- get a adb shell
- use the '/system/bin/idme' command to set the bootmode. I suggest you first run 'idme ?' and write down your default, mine is "4000 0".
- if you set bootmode to 0x4002, the fire will stay in fastboot mode when it reboots
- if you set bootmode to 0x4003, it's supposed to timeout from fastboot mode, but I did not have much luck getting a normal boot after the timeout (did not play too much here).
- if you decide you dont want fastboot mode, run 'idme bootmode "4000 0"' to reset back to default for normal booting.
WARNING:
IF YOU REBOOT AT THIS POINT THE FIRE WILL BE IN THE FASTBOOT MODE. I HAVE NOT FOUND A WAY TO EXIT THIS MODE AND RETURN TO THE NORMAL OS WITHOUT A WORKING FASTBOOT CLIENT.
REPEAT:
YOU MAY BE BRICKED IF YOU DONT HAVE WORKING TOOLS.
When you boot into fastboot mode, it will show the "Kindle Fire" logo. The power button does not appear to do anything; therefore, if you boot a bad kernel/image it may get stuck and require a hard reset (pulling the battery cable).
You should now have access to the standard flashboot functionality (update, flash, usb boot, etc). Note that reboot-bootloader will bring you back to fastboot.
I currently use 'fastboot boot boot.img' (from the sw update) to get back to a working state. Once booted, use idme to disable fastboot.
Now, on to recovery's & custom roms!
Click to expand...
Click to collapse
I had the same issue....but i fixed it!
Code:
fastboot -i 0x1949 oem idme bootmode 0x4000
fastbooot -i 0x1949 reboot
Played with the 0x4003 fastboot "countdown" mode a bit. Seems like it is timing out of fastboot, but not continuing to boot up the rest of the way. After a few seconds the kindle fire logo goes away and the device no longer responds to fastboot commands. Waited maybe a minute or so after it left fastboot and it didn't boot. Though since you found that we can set the bootmode value from fastboot it doesn't really matter.
Also have been playing around with attempting to get my fire to boot a modified boot image. So far I've simply extracted the kernel/initrd from the 6.1 update boot.img and repacked it without modifications. Unfortunately the Fire refused to boot the resulting image.
Going to continue fiddling.
Well managed to successfully repack a boot.img.
The problem i was facing was caused by 2 issues while running mkbootimg.
1) Derped and didn't specify the correct page size (4096)
2) Needed to include a base address of 0x80000000.
wait i'm stuck in the phase where it times out after the kindle logo and it doesn't respond to fastboot commands... what did you do to get out of that?
any help would be GREATLY appreciated before my battery dies. i have my clockwork port saved on the sdcard!
or if somebody can upload their fastboot binary
edit: got it, i needed to specify the vendor id as mentioned on the bottom of page one
thanks to those who were trying to help me (although probably nobody as it's 3am...)
JackpotClavin said:
wait i'm stuck in the phase where it times out after the kindle logo and it doesn't respond to fastboot commands... what did you do to get out of that?
any help would be GREATLY appreciated before my battery dies. i have my clockwork port saved on the sdcard!
or if somebody can upload their fastboot binary
Click to expand...
Click to collapse
I did a long press of the power button and it turned off. Then before turning it back on i ran:
Code:
fastboot oem idme bootmode 4000
Let it sit in "waiting for device" and powered the kindle back on.
Attached my fastboot binary for linux if it's useful for you. It's compiled from AOSP with the 0x1949 vendorid added in.
I don't have the -i option on my version of fastboot. Could you post a windows version of the one you're using?
Edit: found version of fastboot.exe that supports -i in SDK_r07.
I can't post outside links yet, but here's the URL:
code.google.com/p/softy-warely/downloads/detail?name=android-sdk_r07-windows.zip&can=2&q=
Thanks death2all110. Got it to reboot to break out of the fastboot cycle.
New question:
I did fastboot -i 0x1949 boot recovery.img (from the Kindle 6.1 update) and now I can't fastboot back in to break out of the fastboot cycle again:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot -i 0x1949 oem idme bootmode 4000
< waiting for device >
I'm giving CM7 a shot right now. Gonna fastboot flash the system.img generated as well as the boot.img although I doubt this will work
death2all110 said:
any idea what tools i can use to check what amount of resistance i need? I may just go out to the garage and grab 3 100k resistors and try the numerous SGS2 methods (specifically 3 resistors twisted together and jumping pins 4 & 5
Click to expand...
Click to collapse
I dont think it'll hurt to try.. FWIW I didnt see anythign obvious in the source or from quick googling for the specs. Didnt spend a lot of effort on it though.
JackpotClavin said:
I'm giving CM7 a shot right now. Gonna fastboot flash the system.img generated as well as the boot.img although I doubt this will work
Click to expand...
Click to collapse
Yeah I am going to play with existing gingerbread builds as well because I dont think ICS will ever finish building on my machine!
I am planning on just flashing system.img and then usb boot with the stock kindle kernel / boot.img.
It didnt do anything, I found a Micro USB for LG Devices with selectable resistance. But I might buy an actual USB jig for the SGS2 but i dont want to waste my money on it if it doesn't work...
Hmm. Theres gotta be a way...
careful flashing
This may be known to experienced android devs but I thought I'd mention as I am not & just ran into it.
When you flash an individual partition you're limited by the ram, in this case the image size needs to be less than the value reported.
fastboot getvar downloadsize
downloadsize: 1d0000000
So around 486 megs.. just some extras steps needed if you're working with the 512M system partition.
As a disclaimer, I've searched for this question, but have only found when the question is asked as a much broader topic and goes unanswered.
That being said, I can't seem to get TWRP 2.0 installed through using "fastboot boot", the Kindle Fire Utility, or the technique using dd to rewrite the contents of the parttitions.
The closest I've come is getting FIREFIREFIRE to start up using the "dd" technique, but TWRP still will not start when I hit the power button for recovery. And yes, I did use "dd" on the TWRP image file as well.
Also, I even tried using fastboot to flash u-boot.bin onto the bootloader partition, and twrp onto the recovery partition. Still, I can get to the yellow, but no further into starting TWRP.
Any help would be appreciated. At current time, I have the stock bootloader and recovery partitions on the Fire and it is rooted.
Thanks.
maybe your in fastboot mode and hopefully your drivers are installed correctly you can use:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
this should bring you to normal bootmode
I've tried that in case there was an issue. In fact, if I don't press the power button during the yellow triangle, the Kindle Fire OS will start as normal after 10-15 seconds. So, it looks like the bootloader is working right and I'm in the correct bootmode. But, if I hold down the power on the yellow triangle (which is supposed to start TWRP), I just get stuck and nothing starts.
That being said, I think I'm in the correct bootmode.
if i don't remember wrong there is an issue with installing twrp with dd
i think you could retry the installation or simply use KFU (but don't use the drivers of kfu if you have working ones)
Thanks.. I'll give it another shot tonight, and then.
when the device starts and the Triangle appears, are you just pressing the power button once? or are you pressing it until it turns orange?
I have to press it a few times before it changes color to orange and then just let it alone. A long press doesn't work for me.
I can get it to turn orange. I think the long press worked for me on that one. Though, I do know I did the multiple presses as well and didn't get any further.
Is it possible that it might be goofed up because I used SuperOneClick for the original root on 6.2 instead of KFU?
not possible - had the same - rooted with superoneclick on 6.2 then updated
i think your twrp install failed - would retry
I finally figured out my problem. For whatever reason (which is still unknown to me), the Kindle Fire Utility was not able to properly download the twrp.img. The file that was downloaded was 8K (which I'm guessing was some sort of error web page). Anyway, I went straight to teamw.in and downloaded the latest version that clocked in at around 10MB, installed it via the "fastboot -i 0x1949 boot twrp.img" command and all is well now.
If anybody is having similar problems, you might want to check the size of the twrp.img file. 10M = good, 8K = bad.
vaporofnuance said:
I can get it to turn orange. I think the long press worked for me on that one. Though, I do know I did the multiple presses as well and didn't get any further.
Is it possible that it might be goofed up because I used SuperOneClick for the original root on 6.2 instead of KFU?
Click to expand...
Click to collapse
It turns orange the second it starts booting recovery. That's when you should let go. Holding the power button for ~30 seconds for any reason is a hard signal to the PMIC chip to power off.
good that it works again ...
please mark the subject of the topic (edit first post) to [Solved]
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
So, my HTC U Ultra got stuck in bootloop just 3 days after warranty ended(tough luck level : 100).
My phone runs on everything stock and no root.
I press all the buttons when powered off and it goes into bootloader mode. It displays options to boot into recovery mode, boot into download mode and power down, all of which(except power down) gets device into bootloop again.
THE PRIORITY OF GOALS IS : DATA RECOVERY > PHONE BOOTING AND WORKING PROPERLY AGAIN
I did a little research and figured out some sort of procedure by putting bits and pieces together :
1. Download ADB/Fastboot toolkit || universal driver from koush github // I have HTC Sync manager installed as well || twrp custom recovery image for htc u ultra || new ruu from htc support for rom update.
2. Now I put my phone into fastboot mode (since it doesn't show up on adb devices), connect to pc using usb.
3. I type in cmd : "fastboot devices" --> My device shows up there --> Again in cmd : "fastboot boot recovery mytwrp.img" --> the twrp boots into my phone
I was able to put this many steps together and after the last step, i have an abstract idea of what to do :
Enable USB Debugging using twrp recovery --> Use ADB Pull Command to get my all my data from phone to pc --> Use adb wipe the old Firmware (Not sure which command) --> Use adb again to flash new RUU (again not sure how, I've got an .exe file as RUU || should I get it in zip or img or any other format ? || Please help on this too) --> Finally Boot and hopefully everything turns out smooth and secure.
CAN YOU EXPERTS HELP ME TO PUT TOGETHER REMAINING STEPS (AND MODIFY ERRORS, IF ANY, OF EXISTING STEPS ) OF THIS PROCEDURE...???
Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>
jwoegerbauer said:
Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>
Click to expand...
Click to collapse
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly ?
noobie12112 said:
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly in my case?
Click to expand...
Click to collapse
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.
jwoegerbauer said:
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.
Click to expand...
Click to collapse
@jwoegerbauer Thank you for the insight. In my case, the phone wasn't physically damaged, the bootloop occurred out of the blue one day. Now, what I presumed I should do, is to flash a custom recovery (twrp) using "fastboot boot recovery.img" command, and using twrp (Can I enable USB Debugging using twrp ?) to access files, backup and then flash a new RUU. But I found that I need to unlock bootloader, is there any way to use command "fastboot oem unlock" and not lose data, or any other method to unlock bootloader, where i don't lose data?
Thank you for your help.
Unlocking phone's bootloader always causes complete loss of data.
Forget the TWRP thing, it's not helpful at all in your case.
Try to flash phone's Stock ROM by means of ADB - what requires ADB got installed on Windows computer and USB debugging got ( manually !!! ) enabled on phone.
Hey guys, I know this isn't super active anymore, but I tried looking and tried posting elsewhere, and I can't find the answer I need. I'm sure it's something super simple I've overlooked.
I was gifted a 2015 Nvidia Shield TV Pro that was never used, so when I turn it on it gets stuck forever asking for my google login and won't proceed (like this thread here).
I can access the fastboot menu on the unit, and I've installed the PC drivers - BUT
When I open command and type "adb devices" it shows no devices connected.
I'm TOLD this is because I need to activate USB debugging on the unit, but how can I toggle on the USB debugging if I can't get past the google sign-in for a first-time set up?
Am I approaching this wrong?
PLEASE help!
Hello, I have exactly the same issue.
I would be really grateful if someone could help us.
i think you must set your SHIELD in FASTBOOT mode and after flash the stock firmware from https://developer.nvidia.com/gameworksdownload (you can't set FASTBOOT mode from ADB because of the wrong login)
to set fastboot mode look here : https://nvidia.custhelp.com/app/ans...invoke-the-android-fastboot-menu-on-shield-tv
Thanks conduisant! It helped.
I have spent some time to flash new recovery:
How far I was able to proceed:
I downloaded ADB Fastboot drivers
I downloaded recovery image (nv-recovery-image-shield-2017-atv-8.2.3)
I connected Nvidia Shield 2017 (model: P2897) with USB-A-to-USB-A cable to the PC
I was able to see "unknown device" so I installed ADB drivers (SHIELD_Family_WHQL_USB_driver_201801)
In device manager I can see my shield (as a Android Bootloader Interface)
I can access fastboot (pressing A+B on controller during turn on of shield)
I opened CMD and type "fastboot devices" - press enter - I can see my device is listed "03xxxxxxx fastboot"
I am able to execute "fastboot oem unlock", so bootloader is unlocked
I am able to write recovery image by using following commands written in instructions:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot oem lock
fastboot reboot
(no errors, everything was "OKAY")
But after the device restart , I can post only until the nvidia logo and that is it. Unfortunately I do not even know which was the original (stock) version of system in nvidia shield pre-installed. I tried to flash several versions of recovery images, but nothing helped. I can still see only nvidia logo :-(
But what I noticed, my Fastboot looks pretty different. I do not see my bootloader version, also some options are missing (lock bootloader, unlock bootloader etc.)
I also tried another options - boot recovery kernel, safe mode, but only nvidia logo every time.What is strange, when I turn-on the device, the Fastboot is automatically booted (I do not even hold A+B to initiate fastboot) I need to select continue.
So now I am not even able to try login into the shield anymore. I guess I already bricked the device :-(
what you have done is pretty correct !
Shield seems to be hard bricked, you can also try to flash TWRP + lineage OS ROM only to see if the SHIELD still not boot...i've no other idea
Thank conduisant for your effort!
Unfortunately, I am not able to boot into the TWRP.
I tried to flash TWRP what I have found here on forum:
UNOFFICIAL-twrp-3.0.2-ALL-Shields-build2.zip
But no success.
I tried to also flash official TWRP:
twrp-3.2.3-0-foster.img
But also no success.
I do not know which offical recovery to flash before LineageOS ROM (or it does not matter?)
Unfortunately, for some reason my gamepad in Fastboot stopped working (gamepad is connectied via USB to the shield, closest to HDMI port)
It just rumble when Fastboot booted and blinks blue led. I tried to charge gamepad - or - another nvidia shield gamepad but it does not work.
Also USB keyboard does not work. Looks like the USB port does not work properly anymore, so I am not able to click "Continue" in fastboot anymore to post at least until nvidia logo.
Luckily, the bootloader is still unlocked, so I am able to flash anything but I have already lost my mind.
I need another coffee and one full-day of meditaion.
i've got 2017 SHIELD, and i've flashed this TWRP last days + this LINEAGE OS : and all working good
TWRP = https://eu.dl.twrp.me/foster/twrp-3.7.0_9-0-foster.img.html
LINEAGE OS = https://download.lineageos.org/foster
when USB debugging is ON, only one USB port is activate for USB devices (keyboard for example) : it's the port near HDMI, the other port (near fan grid) is for ADB connection for the PC