[GUIDE] Fastboot Mode

Abrar126 said:

What does that mean

Click to expand...

Click to collapse

sd_shadow said:

this thread is for the kindle fire 1

Sent from my KFFOWI using XDA Labs

Click to expand...

Click to collapse

Afrodelix said:

guys guys guys I need some help. I have problem installing my Kindle Fire Gen5 5.1.2 into my device manager.

Fire is recognized in any mode, inclucing ADB mode when system is loaded. Problem occurs when I go into stock recovery and try to do ADB sideload, my device is being recognized as KEFOWI and cannot install any drivers for this.


I'm lost and I'm not a total naab in terms of androids !!!!

Click to expand...

Click to collapse

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

ocarinaz64 said:

So then is the "factory cable" something different than regular USB cable? Like I have a cable that I normally issue fastboot / adb commands with (in Linux) to my Nexus 5. Will that same cable work for the KF8? Or do I need a different cable?

Where I'm at is that someone threw me a free KF8 to fix, because it had CM loaded on it, and they didn't know what that was all about. I saw it had TWRP installed and that CM was loaded up on it. So I was just trying to revert it to "factory" settings, and now it's stuck on that initial logo. All I know for sure is that right now the power + volume button combinations don't do anything. I only entered TWRP one time via software reboot into recovery from within CM. I also can't get it to recognize my device either in Linux or in Windows.

What is the correct next move?

Click to expand...

Click to collapse

sd_shadow said:

see
Fire Index: Which Amazon (Kindle) Fire Do I have?

Sent from my XT1060 using XDA Labs

Click to expand...

Click to collapse

ocarinaz64 said:

I have a KF 8.9, then. And people are saying it doesn't need a special cable. If that's the case, and neither adb nor fastboot will recognize the device, what options are left? (adb and fastboot work for my Nexus)

Click to expand...

Click to collapse

JRVA said:

oi pessoal eu sou novo aqui
tou com meu kindle fire que quando eu ligo ele vai para uma tela vermelha e nao sai dali
ja fiz de tudo que vi na internet ja fiz um jamp em um cabo tentando fazer fastboot cable e nada
por favor alquem me ajude.
obs: ele ficou assim depois que instalei um TWRP

Click to expand...

Click to collapse

Hi guys, I'm new here
I'm with my kindle fire that when I call it goes to a red screen and does not leave there
I've done everything I've seen on the internet and I've done a jamp on a cable trying to make cable fastboot and nothing
Please help me.
Obs: it looked like this after I installed a TWRP

Click to expand...

Click to collapse

shaurya609 said:

I have Kindle Fire HD (second generation) I was trying to download the new OS since then my Kindle is unable to boot. It is stuck on "Your Fire doesn't seem to be able to boot". With two options "Reboot your Fire" and "Reset to Factory Defaults", I have tried both but end up back here. Please help!!!

Click to expand...

Click to collapse

tim_patterson said:

Set up a kindle fire 1st gen with kindle fire utility v0.9.9 installed FireFireFire and Twrp - Not sure which versions they are, but I know they are old.

Started reading about Otter x when I went looking for a newish custom Rom. Never got to flashing one however.

Long story short... Using the old twrp i managed to flash the boot loader for Otter X but but NOT Twrp for Otter X !

Sooo it boots into the Otter X bootloader and then Nothing works! Basically, if you let it boot normal, boot into recovery, or select USB boot, it goes to a black screen.

Windows XP and Windows 10 will not recognize it as a Kindle, Only Unknown Device.
When I try and apply the drivers, it says: "there is not compatible hardware for this driver.

It is not recognized as ADB interface, nor android phone, nor Kindle.
Only One time it popped up in device manager as a omap4430 device.

I have tried rekindle and Umbuntu desktop with fireKit . When I issue a command in Firekit LiveUSB repair kit 1.1 I keep getting no path or no device or something to that effect.

Click to expand...

Click to collapse

sd_shadow said:

[Video] Flashing TWRP in OtterX bootloader


Sent from my PH-1 using Tapatalk

Click to expand...

Click to collapse

tim_patterson said:

Stuck at waiting for device!

With all of the proper drivers installed, the win PC does not detect the kindle.

When I connect it to the PC via USB, the Otter X bootloaders white "Kindle Fire" logo appears for about 2 seconds, then the screen goes black.

I am getting no response from the PC at all today.

Click to expand...

Click to collapse

sd_shadow said:

Connect kindle to pc
Power off Kindle
Run flash command
Power on kindle

Click to expand...

Click to collapse

tim_patterson said:

Flash Command ? Sorry not familiar with that.
Could you link to the thread please?
If you mean run ADB and install fff in a command prompt, I cannot because the PC does not know a Kindle is connected.

Click to expand...

Click to collapse

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