Develop Bugs

[Q] Help: Failed Kindle Fire 6.3 rooting/ fastboot problems (Linux), and ROM choice

[Q] Help: Failed Kindle Fire 6.3 rooting/ fastboot problems (Linux), and ROM choice
Hello, everyone!
I have a Kindle Fire running OS 6.3, and I've decided to root it so I can use custom ROMs, and have access to the Google Market from the Caribbean.
Despite lots of reading and several attempts, I haven't been successful in my attempts to root my Kindle Fire from my Linux laptop. (Ubuntu 12.04.)
I've set up and rechecked adb and fastboot as outlined on this page:
http://androidforums.com/i7500-all-things-root/32481-howto-linux-adb-fastboot-mass-storage.html
And I've been trying the rooting method outlined in this thread:
http://forum.xda-developers.com/showthread.php?t=1568340
ADB successfully sees my device, as confirmed when I type
./adb devices
into my terminal with the KF attached to my USB cable.
The first set of adb commands seems to work fine:
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
...but the first fastboot command doesn't seem to do anything- I get "waiting for device" and nothing more.
I should note that "fastboot devices" command doesn't result in any output from the terminal.
What should I do next?
Also, what recommendations for a custom ROM can you folks suggest?
I am an avid reader and a gamer. I may watch some YouTube videos or sitcom reruns, but hi-def video isn't important to me at all; neither the Fire's storage nor my bandwidth are well suited to HD.
I'm currently looking at MoDaCo and MIUI.
thanks in advance,
adrian.

Any ideas, anyone?

Try turning your device off then restarting after you see the <waiting for device>
If that doesn't work you can still use adb to root your device before installing TWRP and FireFireFire. (just skip the fastboot steps)
After you are rooted you can use "Gscripts" to install FireFireFire and custom recovery
Sent from my Amazon Kindle Fire using xda premium

Just curious, what are the exact fastboot commands you are using; exactly how you typed them.
Sent from my Amazon Kindle Fire using xda premium

If you followed that guide to set up your udev rules, it may be insufficient to get it working with adb. Try this Kindle Fire specific guide...
http://forum.xda-developers.com/showthread.php?t=1475740
As for fastboot, you'll probably need elevated privileges to get that working. Switch to root or use sudo when executing fastboot commands.

Thanks for the replies!
I'm trying the suggestions now, detailed responses to follow.

Reply
The ADB commands went fine, as before.
The first Fastboot command
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
seemed also to succeed, giving OKAY status reports for downloading and booting, and ending with the feedback "finished".
The Kindle Fire then booted into recovery; I pressed the Reboot button, and the device was "stuck" on the Yellow Triangle. This is the first time I've seen this- I think it may be because I edited the adb_usb.ini file tonight.
Anyway, when I entered
fastboot oem idme bootmode 5002
I only got the "waiting for device" response.
Power cycling didn't make any difference.
I checked my adb_usb.ini and udev rules files, and they look fine.

guttaperk said:
Reply
The ADB commands went fine, as before.
The first Fastboot command
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
seemed also to succeed, giving OKAY status reports for downloading and booting, and ending with the feedback "finished".
The Kindle Fire then booted into recovery; I pressed the Reboot button, and the device was "stuck" on the Yellow Triangle. This is the first time I've seen this- I think it may be because I edited the adb_usb.ini file tonight.
Anyway, when I entered
fastboot oem idme bootmode 5002
I only got the "waiting for device" response.
Power cycling didn't make any difference.
I checked my adb_usb.ini and udev rules files, and they look fine.
Click to expand...
Click to collapse
Turn off the device. Run the fastboot command (you'll probably want bootmode 4000 to get to normal) just before powering the device up again. fastboot will tell you that it's waiting for device and it will send the command when FireFireFire goes into temporary fastboot mode. Then you can run the fastboot reboot command and it should boot to your system. Since you have FFF loaded, you can always get to recovery by pressing power during startup without using bootmode 5001 (not sure if 5002 will work anyway).

kinfauns said:
Turn off the device. Run the fastboot command (you'll probably want bootmode 4000 to get to normal) just before powering the device up again. fastboot will tell you that it's waiting for device and it will send the command when FireFireFire goes into temporary fastboot mode. Then you can run the fastboot reboot command and it should boot to your system. Since you have FFF loaded, you can always get to recovery by pressing power during startup without using bootmode 5001 (not sure if 5002 will work anyway).
Click to expand...
Click to collapse
It didn't work. But, I booted into Windows and got KFU to switch the KF to normal boot mode, so that's OK.
So, I now have FFF. But:
adb shell mount system
results in
Usage: mount [-r] [-w] [-o options] [-t type] device directory
and
adb push su /system/xbin/su
results in a warning that I don't have write access.
What should I do from here?

guttaperk said:
It didn't work. But, I booted into Windows and got KFU to switch the KF to normal boot mode, so that's OK.
So, I now have FFF. But:
adb shell mount system
results in
Usage: mount [-r] [-w] [-o options] [-t type] device directory
and
adb push su /system/xbin/su
results in a warning that I don't have write access.
What should I do from here?
Click to expand...
Click to collapse
That mount command should work in TWRP 2.0.0. I'm guessing that you are trying this while booted into the system or another version of TWRP. This one should work better in a wider range of situations....
Code:
adb shell mount -o remount,rw /system

The same problem
Hi, I have the same problem.
I stuck in the command
fastboot -i 0x1949 flash bootloader fire.zip
ok
fastboot -i 0x1949 flash recovery twrp.img
ok
fastboot reboot
My kindle fire reboot but i don't see any thing, the screen has not thing, not yellow triangle.
I hold on the power button 20s to restart. Then the power botton did not come red. My kindle fire not power on.
The adb command did not work.
The fastboot say: wait for devices
Please help me!

trungblc said:
Hi, I have the same problem.
fastboot -i 0x1949 flash bootloader fire.zip
Click to expand...
Click to collapse
This is where you screwed up. You need to read about what you are installing BEFORE you install it. The above named file is in .zip format. The newest version of FireFireFire was put in a .zip format for flashing in recovery.
If you use the "fastboot flash bootloader" command, you can only flash files in a .bin format. You now have a broken bootloader resulting in one of the hardest of bricks.
Research Firekit LiveUSB because that's your only hope at this point.
And let this be a lesson to anyone who wants to make ANY modification to their bootloader...Pay attention!

Thanks you so much
Thanks you so much. I will try and post the result soon.
I've owned you a beer now

Sorry to hear about your trouble trungblc at least you have two of the very best here watching your thread kinfauns and soupmagnet if anyone can get you out of a brick like this it would be them for sure good luck

Update status
I had used Firekit LiveUSB, and short the CPU method.
[email protected]:~/firekit# usb_fix_parts_and_install_fff_twrp
Loading FFF through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
Fixing partitions...
< waiting for device >
...
OKAY [ 0.073s]
finished. total time: 0.073s
Installing x-loader...
sending 'xloader' (128 KB)...
FAILED (status read failed (Protocol error))
finished. total time: 55.162s
Flash FFF...
sending 'bootloader' (211 KB)...
FAILED (status read failed (No such device))
finished. total time: 211.638s
Flash TWRP...
< waiting for device >
After that, kindle boot in TWRP, but when i reboot, it still not power on.

Have you tried holding the power button for 30 seconds and trying again?

Oh.
soupmagnet said:
Have you tried holding the power button for 30 seconds and trying again?
Click to expand...
Click to collapse
Oh holding for 30s? I had tried with 20s. But kindle fire still not power on.
I will try again now

Pls help me more.
[email protected]:~/firekit# usb_fix_parts_and_install_fff_twrp
Loading FFF through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
Fixing partitions...
< waiting for device >
...
OKAY [ 0.072s]
finished. total time: 0.072s
Installing x-loader...
sending 'xloader' (128 KB)...
OKAY [ 0.036s]
writing 'xloader'...
OKAY [ 0.279s]
finished. total time: 0.314s
Flash FFF...
sending 'bootloader' (211 KB)...
OKAY [ 0.057s]
writing 'bootloader'...
OKAY [ 0.042s]
finished. total time: 0.099s
Flash TWRP...
sending 'recovery' (5260 KB)...
OKAY [ 1.319s]
writing 'recovery'...
OKAY [ 4.118s]
finished. total time: 5.437s
Resetting bootmode to standard boot...
...
OKAY [ 0.079s]
finished. total time: 0.079s
Loading TWRP...
downloading 'boot.img'...
OKAY [ 1.319s]
booting...
OKAY [ 0.004s]
finished. total time: 1.323s
In the TWRP, I mount the SDCARD and copy the amazon update.zip (rename from update-6.2.1.bin) to sdcard. The install - Flash - Reboot.
The Kindle Fire still not power on. I really don't know why.

It appears you did all the right stuff with the firekit but then you wiped that out by installing stock 6.2.1 are you getting the fff screen ? Can you still get into twrp? Shame you got that far with the firekit only to put yourself in the same situation might wanna try the firekit again

Thepooch said:
It appears you did all the right stuff with the firekit but then you wiped that out by installing stock 6.2.1 are you getting the fff screen ? Can you still get into twrp? Shame you got that far with the firekit only to put yourself in the same situation might wanna try the firekit again
Click to expand...
Click to collapse
I had been tried to do that before. I just pressed reboot button when it gets into TWRP many times but nothing happened. After that, I had tried to flash room again but still the same.
I don't know why.

Kindle HD 8.9 recovery steps:

First off download the following files
KFHD_SRTv2.1- 8.1.4
img files
KFFirstAide32
or
KFFirstAide64
Extract KFFirstAide whichever version 32 or 64
Copy the folder to c:\
rename it to just KFFirstAide
add that to your path
Code:
;C:\KFFirstAide
Open the folder KFHD_SRTv2.1 then open images folder and copy system.img
paste it into the KFFirstAide folder
then open the two other img files you downloaded and paste them into the KFFirstAide folder as well
you should now have:
system.img
boot.img
recovery.img
All three files in the KFFirstAide folder
now
Open up an Administrative Command Prompt from within the KFFirstAide
go to the c:\ drive hold the shift key and right click on the folder KFFirstAide then select Open a command prompt here.
enter this command at the prompt
Code:
fastboot -i 0x1949 getvar product
it should come back with
< waiting for device >
If you are stuck at the red triangle screen
Make sure your device is totally off hold the power button for like 30 seconds until it turns off
next plug in your device with the usb cable
it should boot into fastboot mode
and show something like:
product: Jem-PVT-Prod-04
finished. total time: 0.009s
then type this command
Code:
fastboot -i 0x1949 devices
should come back with something like this
7EE400003C002FFF fastboot
then type this command
Code:
fastboot -i 0x1949 flash system system.img
should come back with something like
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.857s]
writing 'system'...
OKAY [ 60.331s]
finished. total time: 109.193s
next command
Code:
fastboot -i 0x1949 flash boot boot.img
should show something like
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.449s]
writing 'boot'...
OKAY [ 0.571s]
finished. total time: 1.024s
next command
Code:
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
should see something like
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.449s]
writing 'recovery'...
OKAY [ 0.565s]
finished. total time: 1.020s
these next commands take forever
Code:
fastboot -i 0x1949 erase cache
should come back with
erasing 'cache'...
OKAY [ 47.246s]
finished. total time: 47.250s
Code:
fastboot -i 0x1949 erase userdata
should come back with
erasing 'userdata'...
OKAY [2149.490s]
finished. total time: 2149.494s
and finally
Code:
fastboot reboot -i 0x1949
once it starts rebooting disconnect the USB cable
once you are back up and running you will be at version 8.1.4
to get to current version
you can use KFFirstAide and this time run
c:\KFFirstAide\RunMe.bat
use the option enable OTA updates
you will have to make sure ADB is enabled under security first on your kindle
once you enable OTA updates then unplug the USB
Next :
Charge the battery, and then connect to a Wi-Fi network.
Swipe down from the top of the screen, and then tap Sync.
The software update automatically downloads in the background and installs after the download is complete and the device is asleep.
Your Kindle Fire will restart during the software update. After the restart, the message “Kindle is updating” will appear on the screen and when it's finished you will be at the latest software version.

i ****ing love you, may you breed with amany and spread your DNA far and wide

Lamere said:
First off download the following files
KFHD_SRTv2.1- 8.1.4
img files
KFFirstAide32
or
KFFirstAide64
Extract KFFirstAide whichever version 32 or 64
Copy the folder to c:\
rename it to just KFFirstAide
add that to your path
Code:
;C:\KFFirstAide
Open the folder KFHD_SRTv2.1 then open images folder and copy system.img
paste it into the KFFirstAide folder
then open the two other img files you downloaded and paste them into the KFFirstAide folder as well
you should now have:
system.img
boot.img
recovery.img
All three files in the KFFirstAide folder
now
Open up an Administrative Command Prompt from within the KFFirstAide
go to the c:\ drive hold the shift key and right click on the folder KFFirstAide then select Open a command prompt here.
enter this command at the prompt
Code:
fastboot -i 0x1949 getvar product
it should come back with
< waiting for device >
If you are stuck at the red triangle screen
Make sure your device is totally off hold the power button for like 30 seconds until it turns off
next plug in your device with the usb cable
it should boot into fastboot mode
and show something like:
product: Jem-PVT-Prod-04
finished. total time: 0.009s
then type this command
Code:
fastboot -i 0x1949 devices
should come back with something like this
7EE400003C002FFF fastboot
then type this command
Code:
fastboot -i 0x1949 flash system system.img
should come back with something like
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.857s]
writing 'system'...
OKAY [ 60.331s]
finished. total time: 109.193s
next command
Code:
fastboot -i 0x1949 flash boot boot.img
should show something like
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.449s]
writing 'boot'...
OKAY [ 0.571s]
finished. total time: 1.024s
next command
Code:
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
should see something like
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.449s]
writing 'recovery'...
OKAY [ 0.565s]
finished. total time: 1.020s
these next commands take forever
Code:
fastboot -i 0x1949 erase cache
should come back with
erasing 'cache'...
OKAY [ 47.246s]
finished. total time: 47.250s
Code:
fastboot -i 0x1949 erase userdata
should come back with
erasing 'userdata'...
OKAY [2149.490s]
finished. total time: 2149.494s
and finally
Code:
fastboot reboot -i 0x1949
once it starts rebooting disconnect the USB cable
once you are back up and running you will be at version 8.1.4
to get to current version
you can use KFFirstAide and this time run
c:\KFFirstAide\RunMe.bat
use the option enable OTA updates
you will have to make sure ADB is enabled under security first on your kindle
once you enable OTA updates then unplug the USB
Next :
Charge the battery, and then connect to a Wi-Fi network.
Swipe down from the top of the screen, and then tap Sync.
The software update automatically downloads in the background and installs after the download is complete and the device is asleep.
Your Kindle Fire will restart during the software update. After the restart, the message “Kindle is updating” will appear on the screen and when it's finished you will be at the latest software version.
Click to expand...
Click to collapse
well this procedure saved me thanks but now using KFFaide i run diagnostics on my machine and test fastboot commands it sits at waiting for device and windows say device is not responding to simple fastboot commands check device manager no yellow triangles what to do now? I am rooted and have a 8.9 running 8.4.8 just completed recovery to 8.4.1 and updated to 8.4.8 b4 root flashed a new boot system and recovery image using command prompt but don't know why fastboot isn't working now????? Thanks

larryb1951 said:
well this procedure saved me thanks but now using KFFaide i run diagnostics on my machine and test fastboot commands it sits at waiting for device and windows say device is not responding to simple fastboot commands check device manager no yellow triangles what to do now? I am rooted and have a 8.9 running 8.4.8 just completed recovery to 8.4.1 and updated to 8.4.8 b4 root flashed a new boot system and recovery image using command prompt but don't know why fastboot isn't working now????? Thanks
Click to expand...
Click to collapse
had the same problem on windows 8.1 moved to my windows 7 box and it worked so 8.4.8 didn't kill fastboot at least

I get to.....
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.857s]
writing 'system'...
FAILED <remote: write partition>

Can anyone help?

Got my kindle back
Just want to vouch for this procedure. I followed it and got my Kindle back to its stock settings. It is 8.4.8. I was able to root it, but when I tried installing the bootloader, I must have done something wrong (wrong version maybe?). It hung on a reboot and just sat there with the orange Kindle Fire logo. Volume buttons did nothing. I was able to get it to go into fastboot, so I figured it wasn't a total loss. After trying about everything else, including using KFFirstAide just by itself, this procedure finally did the trick. I unrooted it now, and I don't think I'll make a second attempt.

what can i fix this...?
When i try to reboot my Kindle in fastboot mode, i see his logo for one second only and then the system restart normally...
Sorry for my bad english but i'm italian

I killed my KFHD8.9 by some naughty fastboot command.. Had twrp and some older CM rom but everything was buggy so I was trying to update when I did something I shouldn't have apparently (I think the last command was a fastboot command before everything died). The kindle won't boot up, no screen, nothing. It just heats up if you connect it to charge is all I can tell.
I downloaded everything per instructions in this thread but after the first fastboot command nothing happens it just stays at "< Waiting for device >". Also, 'adb devices' doesn't report anything connected. All my other devices connect fine. I have also pressed the power button for 30s to make sure the kindle is off prior to connecting for fastboot command...
Can this be fixed? Thanks!

mrgv said:
I killed my KFHD8.9 by some naughty fastboot command.. Had twrp and some older CM rom but everything was buggy so I was trying to update when I did something I shouldn't have apparently (I think the last command was a fastboot command before everything died). The kindle won't boot up, no screen, nothing. It just heats up if you connect it to charge is all I can tell.
I downloaded everything per instructions in this thread but after the first fastboot command nothing happens it just stays at "< Waiting for device >". Also, 'adb devices' doesn't report anything connected. All my other devices connect fine. I have also pressed the power button for 30s to make sure the kindle is off prior to connecting for fastboot command...
Can this be fixed? Thanks!
Click to expand...
Click to collapse
Try holding down the power button only for 2 minutes. Right around the 90 second to 120 second point, the device should reboot.

Damocles66 said:
Try holding down the power button only for 2 minutes. Right around the 90 second to 120 second point, the device should reboot.
Click to expand...
Click to collapse
Sry about the delay.. I was counting on an email notification but never got one.. Anyway.
Tried it several times and this didn't work. The tablet doesn't boot up with this 2min+ power button press. Anyone have any other ideas please?

KatanAlive said:
what can i fix this...?
When i try to reboot my Kindle in fastboot mode, i see his logo for one second only and then the system restart normally...
Sorry for my bad english but i'm italian
Click to expand...
Click to collapse
Not sure what Kindle you have since you did not say.
The HD Kindles as far as I know will not boot into fastboot using commands so, your is normal.
Regards
---------- Post added at 07:31 AM ---------- Previous post was at 07:26 AM ----------
mrgv said:
Sry about the delay.. I was counting on an email notification but never got one.. Anyway.
Tried it several times and this didn't work. The tablet doesn't boot up with this 2min+ power button press. Anyone have any other ideas please?
Click to expand...
Click to collapse
I am pretty sure your tablet is not recoverable depending on what fastboot commands you were trying when it stopped booting.
Do you remember what you were attempting to do?
If an incorrect non-signed partition was flashed to the tablet (e.g., from some other Kindle model), the tablet will be bricked.
If the wrong image was flashed to the bootloader partition, you are also bricked since the bootloader is key to turning on the tablet.
If your tablet is warm when plugged in, it means it charges at least.
Since the tablet will not turn on, or get into fastboot using the command line on your PC, there is nothing else to do.
The 8.9 tablet does not support the use of a fastboot cable.

Lamere said:
First off download the following files
KFHD_SRTv2.1- 8.1.4
img files
KFFirstAide32
or
KFFirstAide64
Extract KFFirstAide whichever version 32 or 64
Copy the folder to c:\
rename it to just KFFirstAide
add that to your path
Code:
;C:\KFFirstAide
Open the folder KFHD_SRTv2.1 then open images folder and copy system.img
paste it into the KFFirstAide folder
then open the two other img files you downloaded and paste them into the KFFirstAide folder as well
you should now have:
system.img
boot.img
recovery.img
All three files in the KFFirstAide folder
now
Open up an Administrative Command Prompt from within the KFFirstAide
go to the c:\ drive hold the shift key and right click on the folder KFFirstAide then select Open a command prompt here.
enter this command at the prompt
Code:
fastboot -i 0x1949 getvar product
it should come back with
< waiting for device >
If you are stuck at the red triangle screen
Make sure your device is totally off hold the power button for like 30 seconds until it turns off
next plug in your device with the usb cable
it should boot into fastboot mode
and show something like:
product: Jem-PVT-Prod-04
finished. total time: 0.009s
then type this command
Code:
fastboot -i 0x1949 devices
should come back with something like this
7EE400003C002FFF fastboot
then type this command
Code:
fastboot -i 0x1949 flash system system.img
should come back with something like
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.857s]
writing 'system'...
OKAY [ 60.331s]
finished. total time: 109.193s
next command
Code:
fastboot -i 0x1949 flash boot boot.img
should show something like
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.449s]
writing 'boot'...
OKAY [ 0.571s]
finished. total time: 1.024s
next command
Code:
C:\KFFirstAide>fastboot -i 0x1949 flash recovery recovery.img
should see something like
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.449s]
writing 'recovery'...
OKAY [ 0.565s]
finished. total time: 1.020s
these next commands take forever
Code:
fastboot -i 0x1949 erase cache
should come back with
erasing 'cache'...
OKAY [ 47.246s]
finished. total time: 47.250s
Code:
fastboot -i 0x1949 erase userdata
should come back with
erasing 'userdata'...
OKAY [2149.490s]
finished. total time: 2149.494s
and finally
Code:
fastboot reboot -i 0x1949
once it starts rebooting disconnect the USB cable
once you are back up and running you will be at version 8.1.4
to get to current version
you can use KFFirstAide and this time run
c:\KFFirstAide\RunMe.bat
use the option enable OTA updates
you will have to make sure ADB is enabled under security first on your kindle
once you enable OTA updates then unplug the USB
Next :
Charge the battery, and then connect to a Wi-Fi network.
Swipe down from the top of the screen, and then tap Sync.
The software update automatically downloads in the background and installs after the download is complete and the device is asleep.
Your Kindle Fire will restart during the software update. After the restart, the message “Kindle is updating” will appear on the screen and when it's finished you will be at the latest software version.
Click to expand...
Click to collapse
Amazing! THANKS!! after weeks stuck in FB and logo, I'm back. cheers

ant17 said:
Amazing! THANKS!! after weeks stuck in FB and logo, I'm back. cheers
Click to expand...
Click to collapse
Do I need to let it update before root and twrp install?

mrgv said:
Sry about the delay.. I was counting on an email notification but never got one.. Anyway.
Tried it several times and this didn't work. The tablet doesn't boot up with this 2min+ power button press. Anyone have any other ideas please?
Click to expand...
Click to collapse
Hi, my Kindle 2nd gen 8.9" HD will not power up at all either after flashing the wrong bootloader. Did you ever figure out how to start up your Kindle. Thanks.

Hi! Amazon Fire HD 8.9”. How to Install Google OS? Chromium? ArnoldTheBat? FydeOS? CloudReady?

My 8.9" gets to the TWRP 3.0.2.0 splash screen, but not past that... adb sees the device as being in recovery, but the device doesn't respond to adb commands, and fastboot doesn't see the device.
The 2-min power button trick powered the device off, but not back on.
Any recommendations?

llleonid said:
Hi! Amazon Fire HD 8.9”. How to Install Google OS? Chromium? ArnoldTheBat? FydeOS? CloudReady?
Click to expand...
Click to collapse
Hi there! Can Windows 8 be installed? As?

brilliant
ibrahimsow1 said:
i ****ing love you, may you breed with amany and spread your DNA far and wide
Click to expand...
Click to collapse
simply superb , it was brutal trying to find the recovery img as all links were to dev host mostly. i got an old recovery.img file from an old zip . hey were back to stock. time to root again . thanks m8 excellent guide and work

llleonid said:
Hi there! Can Windows 8 be installed? As?
Click to expand...
Click to collapse
Hello illeonid. Yes you have to search thread for disable driver signature enforcement. There is a thread somewhere on here with how to do windows 8 driver for firehd. I haven't time just now to find it. Will post back later
---------- Post added at 06:40 PM ---------- Previous post was at 06:38 PM ----------
llleonid said:
Hi! Amazon Fire HD 8.9”. How to Install Google OS? Chromium? ArnoldTheBat? FydeOS? CloudReady?
Click to expand...
Click to collapse
You cannot install these on the firehd the chipset just is not capable of handling such sofware with the paltry 1gb ram being main culprit. This is mostly tied up with fireOS and system apps already

[Q] KFHD 8.9 with 8.4.6

Hi guys I got 3HT7G model and I am trying to root it so I can install CM. I am having problem with getting device in to fastboot mode. I have several HTC phone and new Nexus 7 and my fastboot works perfectly, SDK is installed and all tools under C:\sdk\platform-tools
Now this is my first Kindle but from what I understand from before I had to always get in to bootloader/fastboot mode manually and only then ADB start to work. In here I see if "waiting for device" is active unit will automatically will get in to fastboot, well it does not for me. Any adias on wtf is going on here this is driving me mad. I have this Kindle drivers installed and adb is checked on in security. I am starting to think my 8.4.6 version is somehow diffirent from other. Anyone please help.
Thank you, once again other devices like Nexus 7 works and getvar command gives me needed answer ......

More details on what you have done would be nice, but basically you turn your kindle off, leave it u plugged, and on the PC run "fastboot -i 0x1949 getvar product", once it says waiting for device you plug your kindle in and it should go into fastboot. If you hear windows make a noise like something connected and disconnected very fast but it doesn't enter fastboot then you need to try to install the driver in my signature for the device as it appears on windows so you can successfully run the fastboot command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
More details on what you have done would be nice, but basically you turn your kindle off, leave it u plugged, and on the PC run "fastboot -i 0x1949 getvar product", once it says waiting for device you plug your kindle in and it should go into fastboot. If you hear windows make a noise like something connected and disconnected very fast but it doesn't enter fastboot then you need to try to install the driver in my signature for the device as it appears on windows so you can successfully run the fastboot command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yeah sorry should of known.
1. I tried adb devices
List of devices attached
B0C9100424551JHB device
2. I tried bin4ry tool v31 and instead of usual download/sending I got an path error ....
I was about to copy from prompt ...and it looks like for some reason this time it worked, I do see superuser app now but I did got an error there in the middle , don't know if it matters. I'll report if anything is messed up later on with ROM installation. Anyway to check ROOT status from stock system ? So I know this app is not just pretty face ?

managed to get everything installed here are last few output code:
C:\Users\Konstantin\Downloads\KindleFireHD89Root\stuff>fastboot -i 0x1949 flash
bootloader kfhd8-u-boot-prod-8.1.4.bin
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.019s]
writing 'bootloader'...
OKAY [ 0.035s]
finished. total time: 0.055s
C:\Users\Konstantin\Downloads\KindleFireHD89Root\stuff>fastboot -i 0x1949 flash
boot kfhd8-freedom-boot-8.4.3.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.445s]
writing 'boot'...
OKAY [ 0.562s]
finished. total time: 1.009s
C:\Users\Konstantin\Downloads\KindleFireHD89Root\stuff>fastboot -i 0x1949 flash
recovery kfhd8-twrp-2.6.0.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.445s]
writing 'recovery'...
OKAY [ 0.567s]
finished. total time: 1.014s
C:\Users\Konstantin\Downloads\KindleFireHD89Root\stuff>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.000s
C:\Users\Konstantin\Downloads\KindleFireHD89Root\stuff>[/CODE]
After reboot for about 30 mins now I see kindlefire logo (fire is blue in logo) It does not reboot or anything it just sits there. Oh man I hope I haven't screw something up. I tried to boot in to recovery, I could. I restarted again, and again I am on blue kindlefire logo. What's going on ? Anything I should try ? I don't have any roms inside device memory yet. In device manager I see Kindle with yellow mork on it (odd)

You have to put the ROM on the sdcard so you can flash it when it does this, use my tutorial to get a ROM on it, also try updating the drivers again for the device with an exclamation using the ones in my signature. http://forum.xda-developers.com/showthread.php?t=2459498
Technically you can also boot the device into stock rooted os, but you need to flash an older version from before they started making sure the boot loader was the same version as the os, otherwise when they don't match the end result is well, what you have before you right now.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

I always do this to myself, ALWAYS. I panic and think this is the problem I and only I could possibly have and about 3 posts later I found like 10 more people with exact same problem that think this is first in the world just like me, anyhow I did sideload feature and loaded cm .zip and installed sideload.zip from install. I am looking at CM logo booting, so far so good.
P.S.
I was looking at that logo for sometime now, I had to do wipe data and restart once again. All good now.
Thank you !

Hard Bricked Kindle Fire HD 8.9 jem BC09

Hello,
I've hardbricked a Kindle Fire HD 8.9 jem BC09 which was running 8.5.1 before it became a paperweight.
I successfully rooted the device with Bin4rys method, at which point I followed cyanogenmod's directions on installing the bootloader(otter2 CM install instructions on their website)
I verified the MD5 checksum for the bootloader before proceeding.
Here's the results of my mishap:
Volume in drive C is Windows7_OS
Volume Serial Number is 3A6D-6FAB
Directory of C:\Users\User\Downloads
10/10/2015 03:17 PM <DIR> .
10/10/2015 03:17 PM <DIR> ..
10/10/2015 02:29 PM <DIR> Old DLs
10/10/2015 03:17 PM 8,349,292 otter2-freedom-boot-10.4.6.img
10/10/2015 03:17 PM 8,349,292 otter2-twrp-2.6.3.1-recovery.img
10/10/2015 03:13 PM 232,908 otter2-u-boot-prod-10.2.4.bin
04/29/2007 06:12 AM 591,872 WinMD5.exe
10/10/2015 03:15 PM 268,376 winmd5free.zip
5 File(s) 17,791,740 bytes
3 Dir(s) 370,367,225,856 bytes free
C:\Users\User\Downloads>fastboot -i 0x1949 flash bootloader otter2-u-
boot-prod-10.2.4.bin
< waiting for any device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (227 KB)...
OKAY [ 0.020s]
writing 'bootloader'...
OKAY [ 0.040s]
finished. total time: 0.060s
C:\Users\User\Downloads>fastboot -i 0x1949 flash recovery otter2-twrp
-2.6.3.1-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8153 KB)...
OKAY [ 0.437s]
writing 'recovery'...
OKAY [ 0.562s]
finished. total time: 1.014s
C:\Users\User\Downloads>fastboot -i 0x1949 flash boot otter2-freedom-
boot-10.4.6.img
target reported max download size of 1006632960 bytes
sending 'boot' (8153 KB)...
OKAY [ 0.452s]
writing 'boot'...
OKAY [ 0.562s]
finished. total time: 1.014s
C:\Users\User\Downloads>fastboot -i 0x1949 oem recovery
...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\User\Downloads>fastboot -i 0x1949 getvar product
< waiting for any device >
Click to expand...
Click to collapse
At the point where I attempted to reboot into recovery, the device became completely bricked. No response to power on, etc.
As I've been browsing for the past hour it seems to me that this device is virtually unbrickable aside from sending it to Amazon. I have contacted "Chris" at [email protected] and am awaiting his response. In the meantime, if anyone else has any ideas of how to proceed please let me know!
Regards,
siriu5

You can check following options:
1. Send back to Amazon (If it's under warranty).
2. Replace the mother board (You can get at $50 online).
3. Follow this thread: http://forum.xda-developers.com/showthread.php?t=2581124 . (only if you are good at SMD soldering).

You reported this as a bug on the cyanogenmod wiki ( https://jira.cyanogenmod.org/browse/WIKI-194 ) and though the text mentions 'jem' several times, you linked to the otter2 install page.
https://wiki.cyanogenmod.org/w/Install_CM_for_jem has files for the jem (as kfhd8) in 'step 2'...
I don't know how to fix the device but perhaps knowing that the files flashed were for the "Kindle Fire 2nd gen (otter2)" instead of the "Kindle Fire HD 8.9 (jem)" will help someone else in the debugging process.

PsychoI3oy said:
You reported this as a bug on the cyanogenmod wiki ( ) and though the text mentions 'jem' several times, you linked to the otter2 install page.
x has files for the jem (as kfhd8) in 'step 2'...
I don't know how to fix the device but perhaps knowing that the files flashed were for the "Kindle Fire 2nd gen (otter2)" instead of the "Kindle Fire HD 8.9 (jem)" will help someone else in the debugging process.
Click to expand...
Click to collapse
Yeah, I just caught this. Definitely my own mistake. My problem was I google searched "cyanogenmod install kindel hd fire gen 2" and tried the first link that showed up. Dope.
Anyone want a bricked KFHD2? I'll send if you pay for shipping. Cheers!

Is this fixable? Did I brick this thing?!

Here's my problem...
My Kindle Fire HD (Jem) is stuck on the Kindle Fire boot screen (orange logo, no animation). I haven't been able to get it to mount to any of my computers running various operating systems. More details below.
Here are the steps that made my device like this...
Got root using the latest eploit for 8.5.1 successfully. I confirmed that I did have root level access.
Side loaded FireFlash11
Used FireFlash11 to try installing 2nd-bootloader, TWRP and CM. I got the files from here: http://forum.xda-developers.com/showthread.php?t=2128175
Booted into recovery mode and immediately performed a backup.
When I soft rebooted after the backup I only ever saw the Kindle Fire boot screen (orange logo, no animation).
Some other notes...
In Ubuntu when I hard shut down the device and then start it up I get the message Unable to mount JEM-etc. etc.
In Windows if I when I hard shut down the device and then start it up I see something about JEM-etc etc in device manager for a quick second and then it dissapears.
I tried SoupKit on Ubuntu with no luck. I've tried just about every option but no luck. The device never mounts.
I've never had root on this device before. I just got this device a couple of days ago.
Please help! Thanks in advance for your time and effort!

sotrite5 said:
Here's my problem...
My Kindle Fire HD (Jem) is stuck on the Kindle Fire boot screen (orange logo, no animation). I haven't been able to get it to mount to any of my computers running various operating systems. More details below.
Here are the steps that made my device like this...
Got root using the latest eploit for 8.5.1 successfully. I confirmed that I did have root level access.
Side loaded FireFlash11
Used FireFlash11 to try installing 2nd-bootloader, TWRP and CM. I got the files from here: http://forum.xda-developers.com/showthread.php?t=2128175
Booted into recovery mode and immediately performed a backup.
When I soft rebooted after the backup I only ever saw the Kindle Fire boot screen (orange logo, no animation).
Some other notes...
In Ubuntu when I hard shut down the device and then start it up I get the message Unable to mount JEM-etc. etc.
In Windows if I when I hard shut down the device and then start it up I see something about JEM-etc etc in device manager for a quick second and then it dissapears.
I tried SoupKit on Ubuntu with no luck. I've tried just about every option but no luck. The device never mounts.
I've never had root on this device before. I just got this device a couple of days ago.
Please help! Thanks in advance for your time and effort!
Click to expand...
Click to collapse
Completely power off the Kindle (hold power button for 10 seconds), and then type fastboot -i 0x1949 getvar product into the terminal. Plug in the Kindle as soon as you get the <waiting for device> message. after a few seconds, you should get a string beginning with "Jem-PVT". If you do, download the 2nd bootloader, etc. from Hashcode's thread and flash them as directed in step 5. After that, follow the directions to reboot into TWRP, and your recovery process should be complete.
Sent from my Amazon Jem using XDA Labs

monster1612 said:
Completely power off the Kindle (hold power button for 10 seconds), and then type fastboot -i 0x1949 getvar product into the terminal. Plug in the Kindle as soon as you get the <waiting for device> message. after a few seconds, you should get a string beginning with "Jem-PVT". If you do, download the 2nd bootloader, etc. from Hashcode's thread and flash them as directed in step 5. After that, follow the directions to reboot into TWRP, and your recovery process should be complete.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thanks for taking the time to post, monster. Unfortunately this doesn't work for me. In fact, before I ever changed a thing on my device fastboot wasn't working for me (just ADB), in spite of everything being properly installed on my computer. Could this be an issue with 8.5.1? Any other thoughts?

sotrite5 said:
Thanks for taking the time to post, monster. Unfortunately this doesn't work for me. In fact, before I ever changed a thing on my device fastboot wasn't working for me (just ADB), in spite of everything being properly installed on my computer. Could this be an issue with 8.5.1? Any other thoughts?
Click to expand...
Click to collapse
If you've got ADB enabled on your Kindle (settings -> security if I remember correctly?), you should be able to type adb reboot bootloader and have it boot into fastboot without a hitch.
Sent from my Amazon Jem using XDA Labs

monster1612 said:
If you've got ADB enabled on your Kindle (settings -> security if I remember correctly?), you should be able to type adb reboot fastboot and have it boot into fastboot without a hitch.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Although I did have ADB enabled on my Kindle, I am no longer able to communicate with it via ADB since using FireFlash11 to install the 2nd-bootloader, TWRP and CM. The Kindle now does not appear when I type adb devices (although it always had before using FireFlash).

Alright, I think I'm just going to return this one. I have lost all hope. Were the steps that I took above flawed? I'd consider purchasing this same device, but I need to know the mistake that I made. Can anyone tell me?

sotrite5 said:
Alright, I think I'm just going to return this one. I have lost all hope. Were the steps that I took above flawed? I'd consider purchasing this same device, but I need to know the mistake that I made. Can anyone tell me?
Click to expand...
Click to collapse
I wouldn't give up just yet. Try repeating the same directions I gave you, expect from Linux (Ubuntu) this time as opposed to Windows.
Sent from my Amazon Jem using XDA Labs

*EDIT #2 - WE DID IT, BOYS! I just want to say god bless the following:
monster
hashcode
goldenbullet
cyanogenmod
my mother
america
Monster, thanks for all of your help. I will name my first born male child after you. You earned it.
*EDIT I MADE IT INTO RECOVERY by using "fastboot -i 0x1949 oem recovery" once in fastboot mode. I'll continue with your instructions now.!
Well, fastboot worked and so I got excited for a second there but unfortunately I'm stuck again. I successfully followed all of the instructions in step 5, but unfortunately I am still stuck on the orange kindle fire boot-screen. The logo never becomes blue....
I am not able to get into recovery by holding the up and/or down volume buttons
I am not able to get into recovery via terminal yet. I can still see "fastboot mode" with the blue arrow when I issue the "fastboot -i 0x1949 getvar product" command, but it does not respond when I issue commands like "fastboot boot kfhd8-twrp-2.8.7.0-recovery.img" or fastboot flash recovery kfhd8-twrp-2.8.7.0-recovery.img" -- always just "waiting for device".
The device appears in Ubuntu's launcher as Jem PVT 04 (ONLY when in fastboot mode), but when I try to access it I get an error message about it being inaccessible.
The device still does not respond to ADB
Any other ideas?
Code:
[email protected]:~/Downloads$ fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.022s]
writing 'bootloader'...
OKAY [ 0.042s]
finished. total time: 0.063s
[email protected]:~/Downloads$ fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.546s]
writing 'boot'...
OKAY [ 0.572s]
finished. total time: 1.118s
[email protected]:~/Downloads$ fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.566s]
finished. total time: 1.097s
[email protected]:~/Downloads$ fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.050s

sotrite5 said:
*EDIT #2 - WE DID IT, BOYS! I just want to say god bless the following:
monster
hashcode
goldenbullet
cyanogenmod
my mother
america
Monster, thanks for all of your help. I will name my first born male child after you. You earned it.
*EDIT I MADE IT INTO RECOVERY by using "fastboot -i 0x1949 oem recovery" once in fastboot mode. I'll continue with your instructions now.!
Well, fastboot worked and so I got excited for a second there but unfortunately I'm stuck again. I successfully followed all of the instructions in step 5, but unfortunately I am still stuck on the orange kindle fire boot-screen. The logo never becomes blue....
I am not able to get into recovery by holding the up and/or down volume buttons
I am not able to get into recovery via terminal yet. I can still see "fastboot mode" with the blue arrow when I issue the "fastboot -i 0x1949 getvar product" command, but it does not respond when I issue commands like "fastboot boot kfhd8-twrp-2.8.7.0-recovery.img" or fastboot flash recovery kfhd8-twrp-2.8.7.0-recovery.img" -- always just "waiting for device".
The device appears in Ubuntu's launcher as Jem PVT 04 (ONLY when in fastboot mode), but when I try to access it I get an error message about it being inaccessible.
The device still does not respond to ADB
Any other ideas?
Code:
[email protected]:~/Downloads$ fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.022s]
writing 'bootloader'...
OKAY [ 0.042s]
finished. total time: 0.063s
[email protected]:~/Downloads$ fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.546s]
writing 'boot'...
OKAY [ 0.572s]
finished. total time: 1.118s
[email protected]:~/Downloads$ fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.566s]
finished. total time: 1.097s
[email protected]:~/Downloads$ fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.050s
Click to expand...
Click to collapse

Many years later and I find this post still helpful and it saved my KFHD8.9. I had this same issue with a KFHD 8.9 that I had repurposed to a photo frame. I flashed a new ROM to it, thinking it my photo frame app might run better on a different ROM. Only I hadn't flashed a ROM for a few years and got sloppy with the flashing sequence and wound up stuck at the Kindle Fire orange logo. I spent hours reading XDA posts and trying things to get fastboot and adb to get into the device during the roughly 2 or 3 second bootup window before it gets stuck. The problem is that the way windows 10 and windows 7 handle the USB drivers makes it almost impossible. I made an Ubuntu USB stick to boot from and loaded up fastboot, adb and the android usb drivers and was able to get my KFHD into fastboot mode instantly. Once there, it was simply a matter of running the fastboot commands above and I then I was in recovery and able to restore from a backup.
Many thanks!!!

---Delete----