Android OS Forum banner
1 - 7 of 7 Posts

·
Registered
Joined
·
18 Posts
PLEASE UNDERSTAND THE RISKS IN FLASHING THIS.
  • You may lose Fastboot and ADB access if it is not flashed correctly (and maybe even if it is)
  • You may lose functionality to receive OTA updates from Amazon
  • You will be able to flash custom ROMS and kernels using TWRP
  • Neither I or Team Win are responsible for anything that you flash on your devices. You do this accepting the risks
Hello, I'm Pyrostic and I volunteered to test TWRP 2.0 for the Kindle Fire. I hope the following tutorial helps you:

READ EVERYTHING and at least until page 3 and the last few pages in this thread before you continue.

Download the following file and place it in the location of your "fastboot" file. (mine is located in platform-tools because I figured it would be easier to start commands for ADB and Fastboot from the same prompt)

twrp-blaze-2.0.0RC0.img

Right Click+shift the folder where your twrp-blaze-2.0.0RC0.img file is located (along with ADB and Fastboot) and click Open Command Window Here:

Execute the commands below from this command prompt with your Kindle connected to the PC.

Code:
adb shell<br />
idme bootmode 4002<br />
exit<br />
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img<br />
your command window should state that it is <waiting for device> (if it doesn't instantly reboot itself). If the device doesn't reboot immediately hold the power button on the bottom of your device until it turns off. Then power it on. You should see some on screen signage and then the installing of TWRP 2.0 and the FIREFIREFIRE Bootloader.

AFTER it is done and the REBOOT option shows up. Open up a command prompt from your platform-tools folder.

type the following

Code:
<br />
adb shell<br />
idme bootmode 4000<br />
reboot<br />
your device should reboot into the OS

From now on:
tapping power repeatedly during boot up will bring you into TWRP 2.0
not doing anything during boot up will bring you to your OS

For those of you that are still stuck on the yellow triangle:

Thanks to rwphwp:

Add the vendor ID 0x18d1 and
Code:
<br />
%SingleAdbInterface%			= USB_Install, USB\VID_18D1&PID_0100<br />
%CompositeAdbInterface%  = USB_Install, USB\VID_18D1&PID_0100&MI_01<br />
to the android_winusb.inf (PID came from properties/detail under device manager)

If you LOVE TWRP 2.0 on your Kindle Fire. I suggest donating to @agrabren (<--- donation link) for his hard work and thanking me here for my testing
.

TWRP 2.0 is solely supported here at RootzWiki.
 

·
Registered
Joined
·
18 Posts
Discussion Starter · #8 ·
I think those of us stuck at the yellow triangle are permanently bricked.
No you are not perma bricked, the delay that U-Boot has is too short for Fastboot to recognize on Windows. For a fix we will have to get you booted into linux I beleive.
 

·
Registered
Joined
·
18 Posts
Discussion Starter · #11 ·
Can someone try something for me. Try running the following while on that "Yellow Triangle" screen. Plug in your kindle and try running:

Code:
fastboot -1 0x18d1 boot[font=monospace] [/font]twrp-blaze-2.0.0RC0.img<br />
If it says <Waiting for Device>

hard reset your kindle

if it still says <Waiting for Device> use (CTRL+C) to stop the command and run

Code:
<br />
fastboot devices<br />
and let me know what it says.

Furthermore if it runs the install again. at the screen where it says "Reboot" type the following
Code:
<br />
adb shell<br />
idme bootmode 4000<br />
 

·
Registered
Joined
·
18 Posts
Discussion Starter · #13 ·
Well this is interesting... I got TWRP installed, and after doing so I went to reboot the device from inside of cyanogenmod and I told it to reboot into recovery.. it did I made a backup and I thought all was well until I went to reboot it and now no matter how I reboot it, it goes back to TWRP recovery. I mean I assume I am still ok as I have a recovery and a backup..... But how in the world do I get it to boot back into the os ?
from recovery do the following

Code:
<br />
adb shell<br />
idme bootmode 4000<br />
 

·
Registered
Joined
·
18 Posts
Also if none of the above is working. Try the following:

1. Reboot your PC. The reason is that it still thinks your Android device is still connected (you'll see this in Device Manager).
2. Once rebooted, connect your Kindle again via USB. You'll probably hear 3 tones (which means it recognized a device, but didn't load any drivers). In device manager, you'll see a device just called "kindle" with an exclamation point by it. At this point, you'll need to install drivers for it again. Pick "Browse my computer for driver software" BUT don't browse, just click on "Let me pick from a list...", and select "Android Phone" and then pick the newest "Android Composite ADB Interface" from the list. I think you may have 4.0.0.0 or something similar (you may have only a 2.x version possibly depending on which drivers you loaded to root your phone).
3. Once you've done that, you'll need to run the following:

Code:
<br />
fastboot -i 0x1949 oem idme bootmode 4000<br />
fastboot -i 0x1949 reboot<br />
hopefully fastboot will be working again.

thanks to http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222
 

·
Registered
Joined
·
18 Posts
Discussion Starter · #29 ·
Okay, so my kindle fire is stuck at the yellow triangle screen and when ever i try to install the drivers in device manager, the light on my kindle changes from green to orange and than the kindle disconnects from the computer. Does this need that I need to charge my kindle and retry this or do I have a serious problem?
Sounds like you missed the part to set your idme bootmode back to 4000 while on the "reboot" screen during flashing. Not a serious problem, people have recovered from it.

The drivers you are wanting to install aren't those that have been installed already, you actually have to append a new device code. Try 0x18d1. If that doesn't work try also what rwphwp mentioned in his post here. Just remember, it may be a combo of things to get it back up and running.

During testing of this recovery, I soft bricked more times than you could think of. Some of them were so scary, I would lose fastboot and adb. luckily they werent gone for god, but simply the device codes have changed.

I hope something here helps you, I honestly do.
 

·
Registered
Joined
·
18 Posts
Discussion Starter · #32 ·
rdwyer228 said:
Thanks man. I'll try it when I get off of work tonight at nine. I'll let you know how it goes!

Edit-Okay so I tried adding the new device code. Saved the android-winusb files and then plugged my kindle in. Nothing happened. It still continues to show the device for a second or two then the light changes again and It disappears from Device Manager.
Anybody else have any ideas? That is about all I have.
 
1 - 7 of 7 Posts
Top