Develop Bugs

Bootlooping KF, can't access recovery

So I got my Kindle Fire a few months ago, already rooted. I went from TWRP to a CWM-based recovery, and I've been installing ROMs ever since without any issues. I'm currently running a CM9-based ROM, and I decided to play around with the softkeys, because I was tired of the bland white look. So I found some custom softkeys and flashed the .zip. I made sure to make a Nandroid before flashing, of course.
Upon rebooting from the flash, my KF got stuck in a bootloop. No biggie, this has happened before. I shut it down and rebooted to recovery, to restore the backup. But when it boots into recovery, it automatically reflashes the softkeys zip, and then reboots into the never-ending bootloop.
So the KF isn't necessarily bricked, I just can't get into recovery without it flashing a corrupted zip. I've tried two different unbricking tools, neither had any effect on it. Any ideas?

Can you mount SD card in Recovery and delete the Zip file through your PC?

linktohack said:
Can you mount SD card in Recovery and delete the Zip file through your PC?
Click to expand...
Click to collapse
I only wish I could. As soon as I boot into recovery, it flashed the zip, then reboots into the bootloop. I suspect this happens because I used ROM Manager to flash the zip, and recovery hasn't reset itself because the device isn't booting up all the way. So every time I try to access recovery, it performs the last action I gave it, which was to flash the zip.

I hope you aren't using Hashcode's (older) CWMR or you might be looking at a much larger problem.
http://forum.xda-developers.com/showthread.php?t=1651413
I'm not sure what's going on with your device, but the only way I know to get the recovery to do something on start up is to create a /cache/recovery/command file. That file should be a one time use command and get deleted after use, so your report of it happening each time you boot into recovery is puzzling.
If you want to take that out of the equation, I think you should either get to a shell prompt and delete the file manually or erase the cache partition entirely. Try getting to fastboot mode, boot a copy of the TWRP image, and hopefully it won't reboot on you automatically so you can use adb shell. Alternatively, erase the cache partition entirely with fastboot. If you do the latter, you'll probably need to remake the ext4 filesystem on the cache partition. Here are some fastboot references to get you started...
http://forum.xda-developers.com/showthread.php?t=1668159
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3

kinfauns said:
I hope you aren't using Hashcode's (older) CWMR or you might be looking at a much larger problem.
http://forum.xda-developers.com/showthread.php?t=1651413
I'm not sure what's going on with your device, but the only way I know to get the recovery to do something on start up is to create a /cache/recovery/command file. That file should be a one time use command and get deleted after use, so your report of it happening each time you boot into recovery is puzzling.
If you want to take that out of the equation, I think you should either get to a shell prompt and delete the file manually or erase the cache partition entirely. Try getting to fastboot mode, boot a copy of the TWRP image, and hopefully it won't reboot on you automatically so you can use adb shell. Alternatively, erase the cache partition entirely with fastboot. If you do the latter, you'll probably need to remake the ext4 filesystem on the cache partition. Here are some fastboot references to get you started...
http://forum.xda-developers.com/showthread.php?t=1668159
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
Click to expand...
Click to collapse
Thanks for all that, but I managed to fastboot into it, and then wipe system and data. Then I rebooted to recovery and restored my backup. Never fastbooted into a device before, or done anything with adb commands, so it was a fun experience.

same symptoms: KF bootlooping, no recovery
Hi there,
I have a rooted/modded KF with MIUI, FFF 1.4a and TWRP.
After I gave it away to someone, who only "used it", it is now stuck in a bootloop.
I can get into fastboot via fastboot.exe and re-flashed FFF and TWRP, but no change: KF boots with the white/blue logo, I can press the powerbutton to get into recovery, but TWRP doesn´t show up. When I boot normally, it looks the same: Black screen after a few seconds.
I read about the battery issues, so I booted the KF with a fastboot command waiting to the device. The white/blue KF logo showd up and I left the device at the USB port at my PC for a complete night: no change
I tried to set another bootmode via fastboot.exe but the code doesn´t seem to make any difference.
I have a second KF which runs just fine (now with AOKP M5.1).
Is it bricked now?

Elviz42 said:
Hi there,
I have a rooted/modded KF with MIUI, FFF 1.4a and TWRP.
After I gave it away to someone, who only "used it", it is now stuck in a bootloop.
I can get into fastboot via fastboot.exe and re-flashed FFF and TWRP, but no change: KF boots with the white/blue logo, I can press the powerbutton to get into recovery, but TWRP doesn´t show up. When I boot normally, it looks the same: Black screen after a few seconds.
I read about the battery issues, so I booted the KF with a fastboot command waiting to the device. The white/blue KF logo showd up and I left the device at the USB port at my PC for a complete night: no change
I tried to set another bootmode via fastboot.exe but the code doesn´t seem to make any difference.
I have a second KF which runs just fine (now with AOKP M5.1).
Is it bricked now?
Click to expand...
Click to collapse
I'm not an expert on the KF, but from what you've described, I don't think it's bricked. Have you tried fastboot wiping system and data?

Mardenator said:
I'm not an expert on the KF, but from what you've described, I don't think it's bricked. Have you tried fastboot wiping system and data?
Click to expand...
Click to collapse
I just did:
D:\root>tools\fastboot erase system
erasing 'system'... OKAY [ 51.245s]
finished. total time: 51.246s
D:\root>tools\fastboot erase data
erasing 'data'... FAILED (remote: : partition doesn't exist)
finished. total time: 0.002s
D:\root>tools\fastboot erase userdata
erasing 'userdata'... OKAY [108.555s]
finished. total time: 108.577s
D:\root>tools\fastboot reboot
rebooting...
finished. total time: 0.001s
D:\root>​
I tried to get into Recovery but no change.

Maybe it's a problem with TWRP. Have you tried fastboot flashing a CWM-based recovery?

Doesnt sound like you have twrp installed or its broken just resend twrp it should overwrite whatever is there

Thepooch said:
Doesnt sound like you have twrp installed or its broken just resend twrp it should overwrite whatever is there
Click to expand...
Click to collapse
He might want to fastboot erase recovery and then reflash TWRP.

I tried CWM:
D:\root>tools\fastboot flash boot recovery\fff.bin
sending 'boot' (243 KB)... OKAY [ 0.065s]
writing 'boot'... OKAY [ 0.052s]
finished. total time: 0.117s
D:\root>tools\fastboot flash recovery recovery\cwm.img
sending 'recovery' (5198 KB)... OKAY [ 1.321s]
writing 'recovery'... OKAY [ 1.418s]
finished. total time: 2.740s
D:\root>tools\fastboot oem idme bootmode 5001
... OKAY [ 0.667s]
finished. total time: 0.668s
D:\root>tools\fastboot reboot
rebooting...
finished. total time: 0.002s
D:\root>​
No change, same behavior: Starts with white/blue letters and than "off". Entering recovery is not working.

Are you pushing the power button several times quickly when you see the white kindle blue fire and selecting recovery?
---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------
You need to select with the power button or the new fff will just tell it to boot normal also twrp is better if you intend to flash anything ics related

Thepooch said:
Are you pushing the power button several times quickly when you see the white kindle blue fire and selecting recovery?
Click to expand...
Click to collapse
Yes. I also tried to enter recovery just by setting bootmode to 5001 with fastboot. This didn´t work either.

Try setting the bootmode to normal then use the power button to toggle to recovery after reflashing twrp also how your flashing them is incorrect
---------- Post added at 12:09 PM ---------- Previous post was at 12:00 PM ----------
fastboot -i 0x1949 flash recovery <file path> <name of recovery>
fastboot -i 0x1949 flash bootloader<file path><name of bootloader>
not fff.bin to recovery as you are doing but to bootloader
D:\root>tools\fastboot flash boot recovery\fff.bin
sending 'boot' (243 KB)... OKAY [ 0.065s]
writing 'boot'... OKAY [ 0.052s]
finished. total time: 0.117s
this one is really wrong your flashing the bootloader to the recovery partition dunno your doing something strange and thats your issue
you may wanna use firekit to get your bootloader and recovery correctly sent to avoid further issues http://forum.xda-developers.com/showthread.php?t=1430038
or like this leaving the id out
fastboot flash bootloader \path\to\fff.bin
fastboot flash recovery \path\to\twrp.img

Hi,
i did flash fff.img to boot(loader) , and after that CWM.img to recovery. But the image is in a folder called "recovery", perhaps this was confusing.

you wrote that you flashed it to boot not bootloader but yes its confusing
try again after an erase I guess
fastboot erase bootloader
fastboot erase recovery
or with the id -i 0x1949

Did that, no success:
D:\root>tools\fastboot getvar product
< waiting for device >
product: kindle
finished. total time: 0.000s
D:\root>tools\fastboot erase bootloader
erasing 'bootloader'... OKAY [ 0.511s]
finished. total time: 0.512s
D:\root>tools\fastboot erase recovery
erasing 'recovery'... OKAY [ 2.429s]
finished. total time: 2.429s
D:\root>tools\fastboot flash bootloader recovery\fff.bin
sending 'bootloader' (243 KB)... OKAY [ 0.065s]
writing 'bootloader'... OKAY [ 0.052s]
finished. total time: 0.117s
D:\root>tools\fastboot flash recovery recovery\openrecovery-twrp-blaze-2.1.1.img
sending 'recovery' (5568 KB)... OKAY [ 1.404s]
writing 'recovery'... OKAY [ 0.543s]
finished. total time: 1.947s
D:\root>tools\fastboot reboot
rebooting...
finished. total time: 0.001s
D:\root>​

ok unplug it then hold your power button down for 1 min then power it on use power button to toggle to recovery option in boot menu see what you get if that doesnt work redownload twrp img and send that again without erase also there is a small chance you could be remaining in fastboot but I doubt it try select reset bootmode as well but you have no system at this point so getting to recovery is imperative

What does "fastboot boot twrp.img" do for you?

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&A] Kindle Fire 2 7" Stock Restore

Q&A for Kindle Fire 2 7" Stock Restore
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Kindle Fire 2 7" Stock Restore. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Gen2 Kindle stock restore - stuck in a boot loop - following overlode's doc
Overlode - Huge thank you for the simple list for us NOOBS of how to get a stock Kindle stuck in a boot loop back up and running. I am having some problems though and was hoping for some help.
I am running Win7 on my PC. I've installed Android SDK, I have a factory cable and my gen 2 Kindle has the pretty "Fastboot" logo with the flashing green light and a non-flashing red light. When I go into my devices manager and see the "Otter2-***.***" it does have the yellow triangle. This is where I deviate from your instructions (in your .doc file). When I right click I do not see the simple "update driver software". I have to go through several windows to finally reach that option. No big deal. But... I clicked the option to "browse my computer for driver software" then "Let me pick from a list of device drivers on my computer". I do not have the option to select "Kindle". I went to have it list ALL DRIVERS and it is not in that list either.
I'm stuck. I don't know how to get the drivers up and working so I can continue with your instruction sheet. I REALLY appreciate all your efforts (with the drop box and everything). I've been fighting this boot loop for a month now and I'm scared to make a bigger mistake. I can build a pc from scratch- no problem... programming and mobile devices just make my brain hurt. Be kind. Everyone seems to throw around abbreviations like Halloween candy and this just makes me want to run for the hills. I'm learning but please don't just assume I know what you're talking about. Thanks in Advance!!

Myth421 said:
Overlode - Huge thank you for the simple list for us NOOBS of how to get a stock Kindle stuck in a boot loop back up and running. I am having some problems though and was hoping for some help.
I am running Win7 on my PC. I've installed Android SDK, I have a factory cable and my gen 2 Kindle has the pretty "Fastboot" logo with the flashing green light and a non-flashing red light. When I go into my devices manager and see the "Otter2-***.***" it does have the yellow triangle. This is where I deviate from your instructions (in your .doc file). When I right click I do not see the simple "update driver software". I have to go through several windows to finally reach that option. No big deal. But... I clicked the option to "browse my computer for driver software" then "Let me pick from a list of device drivers on my computer". I do not have the option to select "Kindle". I went to have it list ALL DRIVERS and it is not in that list either.
I'm stuck. I don't know how to get the drivers up and working so I can continue with your instruction sheet. I REALLY appreciate all your efforts (with the drop box and everything). I've been fighting this boot loop for a month now and I'm scared to make a bigger mistake. I can build a pc from scratch- no problem... programming and mobile devices just make my brain hurt. Be kind. Everyone seems to throw around abbreviations like Halloween candy and this just makes me want to run for the hills. I'm learning but please don't just assume I know what you're talking about. Thanks in Advance!!
Click to expand...
Click to collapse
EDIT: (a day or so later) Hey.. Nevermind. I was able to finally figure things out and downloaded KindleFireFirstAid and was able to wipe it out back to stock using my factory cable. The boot loop was limiting my options. Thanks Anyway.

Fastboot
What would be stopping Fastboot from recognizing my device? I have a fastboot cable for my kindle fire 2, I plug it into my computer then into the kf2, the kf2 boots up into fastboot mode my computer see the kindle and it has the proper drivers installed, but fastboot can't see it for some reason.
I had this problem before when I installed CM10 onto my kf2 but that was a year ago and for the life of me I don't remember how I got fastboot to see my kf2.
All i want to do is downgrade my kf2 back to stock and sell it on ebay. PLEASE HELP! I'm dying here

Any other options?
Overlode-My wife;s KF2 was stuck in boot loop so I tried your stock restore method with a factory cable. Everything seemed to work fine. The drivers were installed, fastboot commands worked on the device, etc. When I did the last reboot step, the device never turned back on. Now the device will not power up with the factory cable or USB cable. Is there anything I can do to fix this KF2 or is it permanently screwed? Thanks.

Kindle Fire 2 - Bricked
Today I tried the procedure in post http://forum.xda-developers.com/kindle-fire-hd/fire-2-development/kindle-fire-2-7-stock-restore-t2840987 but as I use Linux and have the SDK installed I entered the commands from console.
A couple of days ago I flashed Cyanogenmod using very similar steps.
Here is my log for the attempt to restore the stock ROM:
Code:
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
sending 'bootloader' (227 KB)...
OKAY [ 0.060s]
writing 'bootloader'...
OKAY [ 0.060s]
finished. total time: 0.120s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash boot boot.img
sending 'boot' (4310 KB)...
OKAY [ 1.082s]
writing 'boot'...
OKAY [ 1.053s]
finished. total time: 2.134s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash recovery recovery.img
sending 'recovery' (4828 KB)...
OKAY [ 1.211s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 2.165s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 -w
erasing 'userdata'...
OKAY [114.081s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 28.939s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 143.021s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash system system.img
sending 'system' (777953 KB)...
FAILED (remote: data too large)
finished. total time: 0.004s
(1)
What is worse, after the failure I rebooted in order to restart with the procedure that worked a couple of days ago and leave Cyanogenmod in the Kindle...
but...
No reboot, no lights, no USB detected....
It seems that the tablet is hard bricked.
Is there anything that can be done except using it as a paperweight?
Thanks in advance

KF2 - hardbricked and restored.......almost!!!
Hi,
I have a KF2, which I had previously rooted and installed CM10 custom ROM. Had no problems with it, but decided to try a few more custom ROMS. Forgot about NOT using the KFU program as it was for KF1 devices, and for some stupid reason went ahead and flashed the wrong bootloader.
Result is fairly predictable - HARD BRICKED KF2!!
Thought that was it - searched the forums and everyone was saying the same - no way back from that! Then I came across Kurohyou's post and brilliant guide about hacking a card reader and attaching direct to motherboard. Followed his guide and voila - managed to boot up into recovery (TWRP). However after pushing the ROM files etc to try and install CM ROM again just kept getting "error flashing ROM" . I left the thing after trying various methods and different PC's etc to push the files across and gave up. When I went back to it this morning I couldn't get it to boot into recovery - which I thought was a bit strange. However FASTBOOT mode is ok - I have made a fastboot cable myself which works fine. Kindle was booting up with orange logo, quick flash, orange kindle logo again and repeat. It would not boot into recovery even though I had flashed the correct files via fastboot.
Again almost giving up when I came across Overlode's instructions. Followed them to the letter, and what I am left with now is the standard Kindle Fire logo (orange) which blinks after about 5 seconds and just stays there - left it for about an hour just in case....
I can post screenshots of me flashing the files as per Overlode's instructions if it helps. I get a few errors when using the wipe command, response is "erase successful, but not automatically formatting. File system type not supported" everything else is ok.
I still have the hacked card reader attached which through Ubuntu can see the EMMC directly so don't know if might be worth copying the files directly instead of flashing via fastboot?
Any suggestions gratefully received...... I'm at my wits end with this thing - I know I should have left well alone!!! but I feel like I have run a marathon with this thing only to have fallen flat on my face 5 metres from the finish line!!
Thanks in advance for any help.

lmayala said:
Today I tried the procedure in post http://forum.xda-developers.com/kin...opment/kindle-fire-2-7-stock-restore-t2840987 but as I use Linux and have the SDK installed I entered the commands from console.
A couple of days ago I flashed Cyanogenmod using very similar steps.
Here is my log for the attempt to restore the stock ROM:
Code:
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
sending 'bootloader' (227 KB)...
OKAY [ 0.060s]
writing 'bootloader'...
OKAY [ 0.060s]
finished. total time: 0.120s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash boot boot.img
sending 'boot' (4310 KB)...
OKAY [ 1.082s]
writing 'boot'...
OKAY [ 1.053s]
finished. total time: 2.134s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash recovery recovery.img
sending 'recovery' (4828 KB)...
OKAY [ 1.211s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 2.165s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 -w
erasing 'userdata'...
OKAY [114.081s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 28.939s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 143.021s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash system system.img
sending 'system' (777953 KB)...
FAILED (remote: data too large)
finished. total time: 0.004s
(1)
What is worse, after the failure I rebooted in order to restart with the procedure that worked a couple of days ago and leave Cyanogenmod in the Kindle...
but...
No reboot, no lights, no USB detected....
It seems that the tablet is hard bricked.
Is there anything that can be done except using it as a paperweight?
Thanks in advance
Click to expand...
Click to collapse
Hi - see my last post - I too have a hard bricked kindle. if you're handy with a soldering iron you can try it - I can confirm it does work.
details here -
http://forum.xda-developers.com/showthread.php?t=2415870
I managed to get my kindle from nothing (not even charging light) to back up and running with TWRP installed. I couldn't get a custom ROM installed, kept getting errors - but I think my board has other issues. While I was putting it back together I managed to stick my screwdriver through the battery (don't ask!!!) Since then I think I have caused other damage and it was never the same again I think I may have damaged the memory or the EMMC..... on the hunt for new motherboard at present!
Good luck!

registered an account just to thank you. You saved my KF2.

[Q] Fastboot isn't working, neither is recovery...

I want to return my at&t m8 back to stock (currently on stock rooted with one bad mod installed) so I can give the phone to my father. I dont have S-OFF and dont care about resetting the tamper flag. I have tried many methods to do so, the first being fastboot flashing the stock recovery, then fastboot oem lock, rebooting bootloader, then running the AT&T RUU. After i tried this several times, i noticed that the stock recovery never gets flashed even though it reports 'okay':
Code:
fastboot flash recovery recovery.img
target reported max download size of 1830723584 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.789s]
writing 'recovery'...
OKAY [ 0.896s]
Fastboot reboot-bootloader (both the cli command and if you go select reboot fastboot on the phone) also doesn't work, it reboots the phone normally.
Seems weird that the flash doesn't happen and that reboot-bootloader doesnt work, but nonetheless i try another method restoring a stock nandroid from http://forum.xda-developers.com/showthread.php?t=2701376 . I followed the steps, fastboot erase cache --> fastboot flash boot boot.emmc.win --> fastboot erase cache --> reboot to recovery and restore nandroid --> reboot phone. ANNDDD.... somehow I'm still on the same System/ROM as I was before all this. Also worth noting, any files I push with adb are gone after a reboot. Not sure what is going on but any help would be appreciated.

So you have root permission right ?
Try downloading the stock recovery to the device and flash it with an app called "Flashify" or sense you know how to fastboot maybe try the "dd" method using Terminal emulator to push the stock recovery assuming you know the block where recovery lives [ mmcblk0p43 ]

jball said:
So you have root permission right ?
Try downloading the stock recovery to the device and flash it with an app called "Flashify" or sense you know how to fastboot maybe try the "dd" method using Terminal emulator to push the stock recovery assuming you know the block where recovery lives [ mmcblk0p43 ]
Click to expand...
Click to collapse
Yes I have root.
Unfortunately anything that has to be done from the phone that isn't in the boot loader or recovery, is not an option at this point because it's in a boot loop (makes it to lock screen and then reboots). Sometimes it stops the loops and works for awhile, so if it does I'll give this a shot. However, is there any other method via adb/Fastboot over USB or TWRP?

Do you get the phone's ID (don't post it, just say yes or no) in response when you type: fastboot devices
If not, you have a fastboot connectivity issue. Try to re-install HTC Sync and HTC drivers.
You don't need to flash stock recovery to RUU. I think you might be mixing up your guides/methods. But if you don't have fastboot connectivity (which I suspect is the issue), you won't be able to relock the bootloader and RUU, anyway.
You can also use the bootable RUU here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486'
But again, you need to relock the bootloader first.

redpoint73 said:
Do you get the phone's ID (don't post it, just say yes or no) in response when you type: fastboot devices
If not, you have a fastboot connectivity issue. Try to re-install HTC Sync and HTC drivers.
You don't need to flash stock recovery to RUU. I think you might be mixing up your guides/methods. But if you don't have fastboot connectivity (which I suspect is the issue), you won't be able to relock the bootloader and RUU, anyway.
You can also use the bootable RUU here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486'
But again, you need to relock the bootloader first.
Click to expand...
Click to collapse
Device id shows when i run fastboot devices . I am Positive the fastboot connectivity is not the issue here. So i am attempting to use the bootalble RUU. Since I am S-On though, I have to relock the bootloader first. When I run fastboot oem lock I get this:
Code:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 1.126s
And then it reboots the phone normally, it goes into its loop, I go back to bootloader, and it still shows unlocked.
Just noticed that if i run "fastboot getvar all" the "version-main" is blank. Weird...?

cojomojo said:
Just noticed that if i run "fastboot getvar all" the "version-main" is blank. Weird...?
Click to expand...
Click to collapse
This is very common, usually caused by older TWRP versions. Shouldn't effect anything you are trying to do, I don't think.
Its odd that fastboot devices works, but fastboot oem lock fails.
Try re-installing HTC drivers, and maybe re-installing your fastboot/adb package.

redpoint73 said:
This is very common, usually caused by older TWRP versions. Shouldn't effect anything you are trying to do, I don't think.
Its odd that fastboot devices works, but fastboot oem lock fails.
Try re-installing HTC drivers, and maybe re-installing your fastboot/adb package.
Click to expand...
Click to collapse
Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?
EDIT:
To clarify, I have tried this both natively on a Mac and on a PC.

cojomojo said:
Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?
Click to expand...
Click to collapse
Try flashing the boot.img for your device from fastboot
https://www.androidfilehost.com/?fid=23329332407584494

jball said:
Try flashing the boot.img for your device from fastboot
https://www.androidfilehost.com/?fid=23329332407584494
Click to expand...
Click to collapse
Code:
fastboot flash boot boot.img
target reported max download size of 1830707200 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.868s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.416s
Ok... looks good.... so I reboot, try to fastboot oem lock.... same issue as before. Tried to fastboot flash the stock recovery... says successful... still have TWRP. I went into TWRP, erased system, cache, etc. Reboot the phone, and its all there still. What the heck is going on.

cojomojo said:
Code:
fastboot flash boot boot.img
target reported max download size of 1830707200 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.868s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.416s
Ok... looks good.... so I reboot, try to fastboot oem lock.... same issue as before. Tried to fastboot flash the stock recovery... says successful... still have TWRP. I went into TWRP, erased system, cache, etc. Reboot the phone, and its all there still. What the heck is going on.
Click to expand...
Click to collapse
After each flash "reboot bootloader"
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Than try booting to recovery from hboot
I don't think you can flash recoveries with the bootloader locked if its locking when you fastboot oem lock,I do believe you can lock the bootloader with a custom recovery flashed before hand.

jball said:
After each flash "reboot bootloader"
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Than try booting to recovery from hboot
I don't think you can flash recoveries with the bootloader locked if its locking when you fastboot oem lock,I do believe you can lock the bootloader with a custom recovery flashed before hand.
Click to expand...
Click to collapse
Ok so, i followed that exactly. I ended up in TWRP still. Here is what I did:
Code:
Cody-Macintosh:Downloads Cody$ fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.855s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.402s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
Cody-Macintosh:Downloads Cody$ fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.621s]
writing 'recovery'...
OKAY [ 0.897s]
finished. total time: 2.517s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
Every fastboot reboot-bootloader booted the phone normally. Even tried the "reboot fastboot" option via the device. I still did the steps as you said despite this abnormality, and I ended up in TWRP still. somehow. Tried to wipe the System, Dalvik, Cache, and Data 5 times in TWRP... the phone still boots to its old system, and all the files reappear. I also tried reflashing Chainfire's SuperSU. It reported successful, tried all the fastboot and TWRP stuff again, and the same issue prevails.
Oh, and I have tried multiple USB cables for the hell of it.

cojomojo said:
Ok so, i followed that exactly. I ended up in TWRP still. Here is what I did:
Code:
Cody-Macintosh:Downloads Cody$ fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.855s]
writing 'boot'...
OKAY [ 0.547s]
finished. total time: 2.402s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
Cody-Macintosh:Downloads Cody$ fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.621s]
writing 'recovery'...
OKAY [ 0.897s]
finished. total time: 2.517s
Cody-Macintosh:Downloads Cody$ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
Every fastboot reboot-bootloader booted the phone normally. Even tried the "reboot fastboot" option via the device. I still did the steps as you said despite this abnormality, and I ended up in TWRP still. somehow. Tried to wipe the System, Dalvik, Cache, and Data 5 times in TWRP... the phone still boots to its old system, and all the files reappear. I also tried reflashing Chainfire's SuperSU. It reported successful, tried all the fastboot and TWRP stuff again, and the same issue prevails.
Oh, and I have tried multiple USB cables for the hell of it.
Click to expand...
Click to collapse
K you said you use a type of virtual machine right.
Try installing adb/fastboot directly to your Mac and run the fastboot-mac commands and hope for a better outcome

jball said:
K you said you use a type of virtual machine right.
Try installing adb/fastboot directly to your Mac and run the fastboot-mac commands and hope for a better outcome
Click to expand...
Click to collapse
No, I dont use a virtual machine. I have adb/fastboot installed directly on my mac, and its failed. I also installed adb/fastboot on another computer I have, which runs Windows 8.1, and it fails with the same errors. I could see why you thought I meant virtual machine, so I added an edit to that post. But to clarify, I am not using a virtual machine.

cojomojo said:
No, I dont use a virtual machine. I have adb/fastboot installed directly on my mac, and its failed. I also installed adb/fastboot on another computer I have, which runs Windows 8.1, and it fails with the same errors. I could see why you thought I meant virtual machine, so I added an edit to that post. But to clarify, I am not using a virtual machine.
Click to expand...
Click to collapse
One more ridiculous question I need to ask
Do you have fastboot unchecked through your battery/power settings
---------- Post added at 10:19 AM ---------- Previous post was at 09:54 AM ----------
@cojomojo
If nothing else works maybe try what I have over in here
http://forum.xda-developers.com/showthread.php?t=2586472

cojomojo said:
Tried reinstalling drivers and fastboot/adb AND tried installing it all on a Windows box (im on a mac) and the result is the same. I think its safe to rule out an issue with fastboot/adb connection. Any other ideas?
EDIT:
To clarify, I have tried this both natively on a Mac and on a PC.
Click to expand...
Click to collapse
Strange, fastboot problems are most often a driver issue. But I agree, if you've tried it natively on Mac and PC, it would seem that drivers is not the cause.
Out of curiosity, what ROM is running on the phone currently?

jball said:
One more ridiculous question I need to ask
Do you have fastboot unchecked through your battery/power settings
Click to expand...
Click to collapse
I am trying to check to see if maybe fast boot is on. I suppose it is a possibility, now I just need the phone to stay on long enough to check.
redpoint73 said:
Out of curiosity, what ROM is running on the phone currently?
Click to expand...
Click to collapse
Running stock rooted, with one mod installed (wifi tethering). It is the 50% of the problem because it is causing the reboot loop i mentioned earlier.
******* Update **********
"Fast Boot" is turned on in battery/power settings. However, I turned it off, rebooted, and its back on. Tried multiple times and it won't stick. Thanks to all sticking with helping me out here, even as we approach 3 pages

@cojomojo
Post an update if and when you fix it and what you did to fix it so others might pass in and learn.
I'm still racking my brain thinking of any possibilities it could still be

jball said:
@cojomojo
Post an update if and when you fix it and what you did to fix it so others might pass in and learn.
I'm still racking my brain thinking of any possibilities it could still be
Click to expand...
Click to collapse
Will do for sure. Thanks for your help! I'm thinking I might try and get the phone on long enough to try flashify or something. Maybe try and get s-off???

Are you absolutely sure the bootloader is currently unlocked and you didn't previously re lock it, does it state so in the bootloader screen?
If you can still get into twrp then try flashing a nandroid back to stock from the stock backup thread. I'd also be trying a different cable regardless of whether you think the one you're using is okay.

ashyx said:
Are you absolutely sure the bootloader is currently unlocked and you didn't previously re lock it? If you can still get into twrp then try flashing a nandroid back to stock from the stock backup thread. I'd also be trying a different cable regardless of whether you think the one you're using is okay.
Click to expand...
Click to collapse
Bootloader says unlocked... so I assume it is unlocked. I suppose I could go through the unlock process again, but it definitely says "unlocked". Also TWRP flashing/restoring/anything does absolutely nothing. And I have tried 3 cables and 2 computers.
*** CLARIFICATION ****
I can get into TWRP fine, and I can restore, flash ROMS, whatever... BUT even though they report okay with 0 errors, everything stays the same, i.e. nothing in TWRP actually works. Same with Fastboot.

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----