Windows News and info 15th Anniversary 2009-2024

Mobile Devices and Apps | Mobile O.S's => Tablets | Foldables | Phablets│Hybrids => Topic started by: javajolt on January 06, 2012, 06:36:20 PM

Title: New tools for unbricking a Kindle Fire
Post by: javajolt on January 06, 2012, 06:36:20 PM
(http://i40.tinypic.com/1zcol83.jpg)

Once you’ve rooted an Amazon Kindle Fire and installed the FireFireFire bootloader and TWRP custom recovery, installing custom software such as CyanogenMod 7 or Android 4.0 is incredibly easy. Unfortunately installing TWRP (http://www.jayceooi.com/2011/12/29/how-to-install-twrp-2-0-recovery-on-kindle-fire-video/) and FireFireFire (http://forum.xda-developers.com/showthread.php?t=1369405) can be a little bit of a headache — especially if you’re using a Windows computer.
 
If I had a nickle for everyone who had sent me a message in the last two months saying their Fire won’t boot past the FireFireFire logo (a yellow triangle with a fire icon), I’d have… a lot of nickels.
 
For the most part, this happens when your Windows drivers for the Kindle Fire in fastboot mode aren’t installed properly. There are ways to fix the problem, but it sometimes takes a little trial and error.
 
Fortunately two developers have released new tools designed to take some of the guesswork out of the process.

Kindle Fire Unbrick Utility (http://forum.xda-developers.com/showthread.php?t=1428428)

This is a Windows application that attempts to help you recover from a few common problems. You can try this tool if:
 
 • Your Kindle get stuck at the FireFireFire boot logo and doesn’t go any further
 
 • You can boot into TWRP, but whenever you reboot you end up back in TWRP instead of Android

 • You’ve modified \system\app permissions, wallpapers, themes, or other items
 
In order to use the utility, you’ll also need to download the Kindle Fire Utility (http://forum.xda-developers.com/showthread.php?t=1399889) so that you can use some of the included files if necessary.
 
Once you’re ready, just double-click on the KindleUnbrick.bat file to get started and follow the on-screen instructions.

FireKit LiveUSB repair kit (http://forum.xda-developers.com/showthread.php?t=1430038)
 
This tool gets around the Windows driver issue by removing Windows from the equation altogether. Instead, developer pokey9000 has put together a series of tools that work with an Ubuntu Linux LiveUSB so that you can do the following things without even booting into Windows:

 • Install FireFireFire and TWRP when you’re using the default Amazon Kindle Fire 6.2.1 software.

 • If you’re stuck at the boot logo, you can install FireFireFire and TWRP anyway.

 • You can also change the bootmode to normal to reboot into Android when you’re stuck at the boot logo.

 • Restore the stock partition tablet settings.

 • Boot into TWRP even if it’s not installed on your Kindle by using a USB connection to your PC.
 
You can find more commands at the FireKit LiveUSB repair kit thread (http://forum.xda-developers.com/showthread.php?t=1430038) in the xda-developers forum.
 
While this is probably the most powerful solution, it does take a little work to set up properly.
 
You’ll need to:

 1. Download the latest 32-bit version of Ubuntu (http://www.ubuntu.com/download/ubuntu/download).

 2. Plug in a 2GB or larger USB flash drive to your PC.

 3. Download the PenDriveLinux Universal USB Installer (http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/) and run it to load Ubuntu on your flash drive.

 4. Unzip the FireKit tools to the root directory of your USB flash drive.

 5. Reboot your computer.

 6. Choose to boot from the flash drive instead of your hard drive (by entering the BIOS or boot menu).
 
Once you’ve done that, you should be running Ubuntu Linux from the USB flash drive and you can follow pokey9000′s instructions for running the Firekit utilities to fix problems with your Kindle Fire.
 
The nice thing about the LiveUSB method is that you shouldn’t need to install any drivers, and you won’t make any changes to your Windows installation while running Ubuntu — because no data is being written to your hard drive at all.