[Q] No fastboot/ADB unauthorized/TWRP loop = Bricked? - 8.9" Kindle Fire HD Q&A, Help & Troubleshooting

Hi all,
I apologize in advance, but I was unsure if there was another thread my issue would best be posted. I have a kindle hd 8.9 32gb that is now stuck in a boot loop at the twrp (2.8.3.0) splash screen (after installing the new Candy5 5.1.1 rom). The rom installed fine and ran perfectly the 1st time, but upon the next device restart it entered the recovery loop and never gets past the splash screen. The kindle itself is recognized by my pc while the screen is looping, but adb shows the device as "unauthorized" and of course with the looping issue I am never prompted to enable. With the 8.9 and no ADB, I also am also unable to enter fastboot mode. Any thoughts or suggestions, or am I bricked with the only possibility being a direct e-MMC restoral? *my soldering kung-fu is extremely weak*
Thanks in advance for any answers!

I have the same problem as you. I updated CM to 12.1, perform a factory reset and I got stuck on twrp screen which is blinking...

Possible Solution
I did something similar but with latest CM nightly rom and got stuck in the twrp recovery mode as a continuos loop, but mine was detected with the status "recovery" via adb;
Check if your adb /fastboot drivers are correctly installed and your not pluggin your kindle to a usb 3 port, then try this:
adb reboot bootloader
It will order the kindle to reboot in fastboot, after that you can just reflash the kindle to its original state with the fastboot commands from your backup.
Dont forget to erase the userdata, cache and all that stuff, you can do it with kindle firstaide
After that just redo all the process of rooting and install a Custom Rom.
Note: I got stucked on a loop of the kindle fire logo, cuz i didnt erase the userdata, but I was able to enter fastboot after the restore, thats why i suggest you delete the cache and other stuff

EDIT: Nevermind. Managed to resolve the issue by booting into fastboot mode, erasing cache and userdata using SR Tool from the KFHD_SRTv1.3.5 and then sideloading the ROM and GAPPS. I lost everything but it means i do not have to buy another KFHD.
Really grown attached to it, especially when the guys at Cyanogenmod keep on releasing updated OS's every year or so, making my tablet feel new every time.
Good work fellers.
I have a Kindle Fire HD with the CM12.1 ROM installed. After installing a nightly i did a factory reset from within the OS and it is stuck in a bootloop occasionally flashing on the teamwin splash screen.
Have i bricked my system or is there a solution.
I posted here because it appears that the op and myself have the same issue.
I tried ADB method but when i use the command "adb device" it shows as unauthorized so it will not allow me to run the adb shell or reboot command.
Any solutions will be much appreciated.

Hi to all
I have the same problem with twrp blinking after a factory reset on cm 12.1 ... I tried adb or fastboot commands (with KFHD_SRT_v2.1 or latest android sdk tools) but I cannot see my device. Consider that I installed adb drivers on a win 8.1 pc with 2.0 and 3.0 usb ports and I am using the standard cable included in the kindle fire hd 8.9 package.
Where I am wrong? A fastboot cable can solve the problem? Sorry for this question but I read many threads and there are different opinions about that...
Thanks in advance for any help.

KFHD 8.9 stuck in bootloop
hey guys,
im need of help a few days ago i tried installing a 2nd bootloader and rom to my kindle fire hd 8.9 i used the wrong files which were the ones for the hd 7 i believe i rooted my kindle succesfuly but the problem came once i flashed it, it just rebooted and now its stuck in a bootloop i have android sdk installed and the kindle fire adb drivers installed i try to put my kindle into fastboot mode by typing in this code: fastboot -i 0x1949 getvar product. once i type that into the cmd it says waiting for device i plug in my turned off kindle and it just turns on and goes into the bootloop and doesn't go into fastboot mode can anyone help me figure out why it won't go into fastboot mode thank you.

albertferrari_1995 said:
hey guys,
im need of help a few days ago i tried installing a 2nd bootloader and rom to my kindle fire hd 8.9 i used the wrong files which were the ones for the hd 7 i believe i rooted my kindle succesfuly but the problem came once i flashed it, it just rebooted and now its stuck in a bootloop i have android sdk installed and the kindle fire adb drivers installed i try to put my kindle into fastboot mode by typing in this code: fastboot -i 0x1949 getvar product. once i type that into the cmd it says waiting for device i plug in my turned off kindle and it just turns on and goes into the bootloop and doesn't go into fastboot mode can anyone help me figure out why it won't go into fastboot mode thank you.
Click to expand...
Click to collapse
When it's in the TWRP bootloop, the device should be in adb mode, so you can flash recovery, erase cache, etc..
I'd start off with a "adb erase cache", and that should get you past the TWRP bootloop.
---------- Post added at 03:21 PM ---------- Previous post was at 03:15 PM ----------
jstevensaz said:
Hi all,
I apologize in advance, but I was unsure if there was another thread my issue would best be posted. I have a kindle hd 8.9 32gb that is now stuck in a boot loop at the twrp (2.8.3.0) splash screen (after installing the new Candy5 5.1.1 rom). The rom installed fine and ran perfectly the 1st time, but upon the next device restart it entered the recovery loop and never gets past the splash screen. The kindle itself is recognized by my pc while the screen is looping, but adb shows the device as "unauthorized" and of course with the looping issue I am never prompted to enable. With the 8.9 and no ADB, I also am also unable to enter fastboot mode. Any thoughts or suggestions, or am I bricked with the only possibility being a direct e-MMC restoral? *my soldering kung-fu is extremely weak*
Thanks in advance for any answers!
Click to expand...
Click to collapse
I'm in this same situation... BUT, I finally got into TWRP and was starting to restore the ROM, but then my battery died... while i was in TWRP recovery.
Now my device won't power on (won't get to the Kindle Fire boot logo). I can't adb or fastboot, since the device won't power on, even when I plug it into the computer. I've tried charging it overnight, hoping that would help.
Nothing.
Do any of you Android gods (@Hashcode) have anything else I can try? Anything in the Android SDK that might help and at least allow the device to accept a charge?
Thanks!

Same problem
I'm in the same situation as the OP. Unfortunately, my device is unauthorized in ADB and since I'm stuck in the TWRP loop, there's not much else I can do. I wondered if it was perhaps the drivers causing the issue, so I fuddled around uninstalling and reinstalling to no avail. One thing to note is I'm using Windows 10, not sure if that could be causing any issues.

adb devices - Unauthorized - Amazon Jem- TWRP swithed to Cyanogen Recovery
I have similar issue. I have a kindle hd 8.9 16gb.I had 2nd boot loader installed with TWRP recovery. One day, I rebooted at it and it rebooted into cyanogen recovery for some reason (after installing the new CROM 5 5.1.1 rom). The rom installed fine and ranOK the 1st time, but upon the next device restart it entered the cyanogen recovery loop which has some options i.e. 1. Reboot system 2 apply update, wipe data /factory reset 3. wipe partition, 4. wipe media 5. reboot to bootloader ( fast boot mode)6. Power down and 7.view recovery logs,. The kindle itself is recognized by my pc while the screen is looping, but adb shows the device as "unauthorized" and of course with the looping issue I am never prompted to enable. adb devices results into xxxxxx ( some number ) unauthorized. I have tried all the options. No. 5 takes me to fast boot mode. but I can’t go any farther. The boot loop is driving me crazy . Can anyone help me? Thanks in advance.

tukky52xda said:
I have similar issue. I have a kindle hd 8.9 16gb.I had 2nd boot loader installed with TWRP recovery. One day, I rebooted at it and it rebooted into cyanogen recovery for some reason (after installing the new CROM 5 5.1.1 rom). The rom installed fine and ranOK the 1st time, but upon the next device restart it entered the cyanogen recovery loop which has some options i.e. 1. Reboot system 2 apply update, wipe data /factory reset 3. wipe partition, 4. wipe media 5. reboot to bootloader ( fast boot mode)6. Power down and 7.view recovery logs,. The kindle itself is recognized by my pc while the screen is looping, but adb shows the device as "unauthorized" and of course with the looping issue I am never prompted to enable. adb devices results into xxxxxx ( some number ) unauthorized. I have tried all the options. No. 5 takes me to fast boot mode. but I canâ??t go any farther. The boot loop is driving me crazy . Can anyone help me? Thanks in advance.
Click to expand...
Click to collapse
when in fastboot mode, hook the kindle up to a PC with a terminal/command prompt (also make sure the kindle drivers are installed if you're running Windows) and enter fastboot -i 0x1949 oem idme bootmode 4000. you should see successful text on both the kindle and your terminal after running that command. if that's true, just do fastboot -I 0x1949 reboot afterwards to reboot the kindle.

monster1612 said:
when in fastboot mode, hook the kindle up to a PC with a terminal/command prompt (also make sure the kindle drivers are installed if you're running Windows) and enter fastboot -i 0x1949 oem idme bootmode 4000. you should see successful text on both the kindle and your terminal after running that command. if that's true, just do fastboot -I 0x1949 reboot afterwards to reboot the kindle.
Click to expand...
Click to collapse
Thanks Moster1612:
Just one more thing. adb devices comand gives me F:\WINDOWS\system32>adb devices
List of devices attached
B0C91004250411V7 unauthorized
can you help me with that. I think i am close to solving this issue.
I did follw your instruction and here is what i git
F:\WINDOWS\system32> fastboot -i 0x1949 oem idme bootmode 4000
< waiting for any device >
...
OKAY [ 0.050s]
finished. total time: 0.058s
F:\WINDOWS\system32>fastboot -I 0x1949 reboot
fastboot: unknown option -- I
F:\WINDOWS\system32>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.006s
My device went back to cyanogen recovery boot cycle again. Is it because adb devices not recognizing the device?

tukky52xda said:
Thanks Moster1612:
Just one more thing. adb devices comand gives me F:\WINDOWS\system32>adb devices
List of devices attached
B0C91004250411V7 unauthorized
can you help me with that. I think i am close to solving this issue.
I did follw your instruction and here is what i git
F:\WINDOWS\system32> fastboot -i 0x1949 oem idme bootmode 4000
< waiting for any device >
...
OKAY [ 0.050s]
finished. total time: 0.058s
F:\WINDOWS\system32>fastboot -I 0x1949 reboot
fastboot: unknown option -- I
F:\WINDOWS\system32>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.006s
My device went back to cyanogen recovery boot cycle again. Is it because adb devices not recognizing the device?
Click to expand...
Click to collapse
No, that's a separate issue. What I would suggest right now is for you to download the bootloader, freedom-boot, and TWRP 2.8.7.0 from Hashcode's thread, reboot to the bootloader from CM recovery, and flash the files as directed to in step 5. However, don't power off the kindle - it's already in fastboot mode, so there's no need to turn it off and tell it to reboot into the bootloader. Also, ignore the post warning about flashing the freedom-boot image - we're only using it temporarily.
Once you have the files flashed, reboot into recovery. If you're in TWRP, go ahead and flash CM or another ROM. Just avoid booting into system until you do so.

Flashing files in Flashboot mode.
monster1612 said:
No, that's a separate issue. What I would suggest right now is for you to download the bootloader, freedom-boot, and TWRP 2.8.7.0 from Hashcode's thread, reboot to the bootloader from CM recovery, and flash the files as directed to in step 5. However, don't power off the kindle - it's already in fastboot mode, so there's no need to turn it off and tell it to reboot into the bootloader. Also, ignore the post warning about flashing the freedom-boot image - we're only using it temporarily.
Once you have the files flashed, reboot into recovery. If you're in TWRP, go ahead and flash CM or another ROM. Just avoid booting into system until you do so.
Click to expand...
Click to collapse
Hi Monster 1612! Thank you very much for helping me out. Please bare with me b/c I am a newbee. Should I download File no.2 & 3 from Step 2 or more. Can you explain a little more about "reboot to the bootloader from CM recovery" . If I do that it takes my device to fastboot mode. What is flash the files as directed to in step 5. How to flash the files in flashboot mode". Is there a link about this? Are you talking about codes in the box in Hashcode's thread? I really appreciate your help.

The files and instructions should be located in this thread.
As for booting into fastboot mode on the kindle, this should be easy - in its current state, it just boots into Cyanogen Recovery, right? Anyway, you just need to choose option 5 in that recovery menu to enter fastboot mode.

monster1612 said:
The files and instructions should be located in this thread.
As for booting into fastboot mode on the kindle, this should be easy - in its current state, it just boots into Cyanogen Recovery, right? Anyway, you just need to choose option 5 in that recovery menu to enter fastboot mode.
Click to expand...
Click to collapse
Thanks Sir!
I will follow the instructions and report back later!

KDHD recovery stuck in yeloow/white logo
tukky52xda said:
Thanks Sir!
I will follow the instructions and report back later!
Click to expand...
Click to collapse
I downloaded the bootloader, freedom-boot, and TWRP 2.8.7.0 from Hashcode's thread, reboot to the bootloader from CM recovery, and flashed the files as directed to in step 5 from Hashcode link.. Didn't power off the kindleas at it was already in fastboot mode as you said. Once I had the files flashed, rebooted into recovery. Wow, it rebooted into TRWP recovery mode. with 8 buttons (reboot,advance,mount,setting,restore backup,isnstall, wipe). I was so happy because of your help. Then I did the stupid thing. I rebooted probably into the system. Now My device is stuck in Kindle fire Yellow/white logo. Now ADB command works but adb devices dont bring anything ( waiting for devices). The driver is installed but my PC does not see it device manager. I lost fastboot mode too. I was so close sir because your help. I remember you telling me to flash into a ROM and not boot into system.
That makes me a real noob. Now please help me if you can. What is next? Is thre still a hope?

tukky52xda said:
I downloaded the bootloader, freedom-boot, and TWRP 2.8.7.0 from Hashcode's thread, reboot to the bootloader from CM recovery, and flashed the files as directed to in step 5 from Hashcode link.. Didn't power off the kindleas at it was already in fastboot mode as you said. Once I had the files flashed, rebooted into recovery. Wow, it rebooted into TRWP recovery mode. with 8 buttons (reboot,advance,mount,setting,restore backup,isnstall, wipe). I was so happy because of your help. Then I did the stupid thing. I rebooted probably into the system. Now My device is stuck in Kindle fire Yellow/white logo. Now ADB command works but adb devices dont bring anything ( waiting for devices). The driver is installed but my PC does not see it device manager. I lost fastboot mode too. I was so close sir because your help. I remember you telling me to flash into a ROM and not boot into system.
That makes me a real noob. Now please help me if you can. What is next? Is thre still a hope?
Click to expand...
Click to collapse
The bootloader should still be responsive regardless of what's been flashed onto the kindle. Go ahead and completely turn off the kindle (hold the power button down for 10 seconds till the screen turns off), and then open a terminal on your PC. Type in fastboot -i 0x1949 getvar product , and plug in the kindle when you see <waiting for device>. After a few seconds, the kindle should be in fastboot, and the prompt should have outputted something like "jem-pvt-prod-04". Now repeat that flashing process again, and type fastboot -i 0x1949 reboot when done. Press and hold the recovery key (the one closest to the camera) until you're in TWRP, then flash CM or another chosen ROM from TWRP.
Happy to help!

monster1612 said:
The bootloader should still be responsive regardless of what's been flashed onto the kindle. Go ahead and completely turn off the kindle (hold the power button down for 10 seconds till the screen turns off), and then open a terminal on your PC. Type in [fastboot -i 0x1949 getvar product [/I], and plug in the kindle when you see <waiting for device>. After a few seconds, the kindle should be in fastboot, and the prompt should have outputted something like "jem-pvt-prod-04". Now repeat that flashing process again, and type fastboot -i 0x1949 reboot when done. Press and hold the recovery key (the one closest to the camera) until you're in TWRP, then flash CM or another chosen ROM from TWRP.
Happy to help!
Click to expand...
Click to collapse
My friend , you are becoming a saviour. Have you got any donate button for support? I would like to contribute. This time I am not going to rush. Want to make sure I undestand everything. What is [/I] before / after fastboot -i 0x1949 reboot and fastboot -i 0x1949 getvar . I hope its not any part of command. BTW, I dont see any key near the camera ( recovery Key?). I have kindle fire HD 8.9. This has power key and up and down volume key.

tukky52xda said:
My friend , you are becoming a saviour. Have you got any donate button for support? I would like to contribute. This time I am not going to rush. Want to make sure I undestand everything. What is [/I] before / after fastboot -i 0x1949 reboot and fastboot -i 0x1949 getvar . I hope its not any part of command. BTW, I dont see any key near the camera ( recovery Key?). I have kindle fire HD 8.9. This has power key and up and down volume key.
Click to expand...
Click to collapse
So far, I don't have a donate button - I'm worried about its legality, cause I'm not 18 for at least another year.
Anyway, the button we're talking about is volume up. It's the one closest to the camera, and the boot partition's programmed to boot into recovery when this button is pressed and held during initial boot (I.e.: when the Kindle Fire logo appears and changes from orange to blue). The fastboot flashing process I described above goes like this:
1) Power the kindle off completely, type fastboot -i 0x1949 getvar product, plug in kindle when prompted.
2) Kindle should boot into fastboot, and "jem-pvt-prod-04" or similar text will appear.
3) Flash TWRP, freedom-boot, and the 8.1.4 bootloader as you did before.
4) Type fastboot -i 0x1949 reboot when you're done flashing, then immediately press and hold volume up as soon as you see the kindle fire logo. Keep holding until you're in TWRP.
5) Flash a ROM, as well as gapps if desired.
6) Profit
Hopefully, this clears up any confusion.

monster1612 said:
So far, I don't have a donate button - I'm worried about its legality, cause I'm not 18 for at least another year.
Anyway, the button we're talking about is volume up. It's the one closest to the camera, and the boot partition's programmed to boot into recovery when this button is pressed and held during initial boot (I.e.: when the Kindle Fire logo appears and changes from orange to blue). The fastboot flashing process I described above goes like this:
1) Power the kindle off completely, type fastboot -i 0x1949 getvar product, plug in kindle when prompted.
2) Kindle should boot into fastboot, and "jem-pvt-prod-04" or similar text will appear.
3) Flash TWRP, freedom-boot, and the 8.1.4 bootloader as you did before.
4) Type fastboot -i 0x1949 reboot when you're done flashing, then immediately press and hold volume up as soon as you see the kindle fire logo. Keep holding until you're in TWRP.
5) Flash a ROM, as well as gapps if desired.
6) Profit
Hopefully, this clears up any confusion.
Click to expand...
Click to collapse
Hi Moster 1612!
I followed step by step evrything went by the book in fastboot mode ( see below). You are great. However, I cant understand for some reason, it did not boot into TWRP recovery and went back to Kindle fire logo. I did press the volume up key As soson as KF yellow logo came in but it stayed yellow. . I can turn it off by pressing for 10 secs. Now what my young friend?
Here are the illustrations:
F:\Users\Irtafa\AppData\Local\Android\sdk\platform-tools\KF\2nd Boot Loader>fastboot -i 0x1949 getvar product
< waiting for any device >
product: Jem-PVT-Prod-04
finished. total time: 0.034s
F:\Users\Irtafa\AppData\Local\Android\sdk\platform-tools\KF\2nd Boot Loader>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.024s]
writing 'bootloader'...
OKAY [ 0.048s]
finished. total time: 0.079s
F:\Users\Irtafa\AppData\Local\Android\sdk\platform-tools\KF\2nd Boot Loader>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.457s]
writing 'boot'...
OKAY [ 1.524s]
finished. total time: 1.997s
F:\Users\Irtafa\AppData\Local\Android\sdk\platform-tools\KF\2nd Boot Loader>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.454s]
writing 'recovery'...
OKAY [ 1.056s]
finished. total time: 1.517s
F:\Users\Irtafa\AppData\Local\Android\sdk\platform-tools\KF\2nd Boot Loader>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.006s

Related

[recovery] twrp2 install on windows

okay, this is to try to simplify the install for most windows users...
for starters get over to the teamwin website and download the official rc0 which comes with firefirefire bootloader so you can easily get into recovery with our 1 power button.
after youve downloaded the recovery file, put this file in the directory that your adb and fastboot is in, connect your device and open a cmd window
cd to the directory adb and fastboot is in, for me i typed
cd c:\sdk_tools (enter)
c:\sdk_tools becomes the directory, so now
adb shell (enter)
su (enter)
idme bootmode 4002 (enter)
so now your bootmode is set. now type in:
exit (enter)
exit (enter)
adb reboot (enter)
it should reboot to the splash screen of kindle fire in fastboot mode, now type in
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img (enter)
it should install, show team wins image, then reboot to the yellow triangle of firefirefire...
this is okay. from here, on windows, my computer did NOT read the device anymore and it was stuck in fastboot and wouldn't take commands. this issue is related to the drivers for some reason... what i did was reboot my pc, reconnected my device and it came up as a unknown device. this is okay!
go to devices and right click the one with an xclimation mark and click update drivers. choose manually and then choose out of available drivers. you need to select android phone or something android related depending on what drivers you had installed previously. i chose my asus android device since thats what i had when i first got adb working. after u choose android device choose adb generic and it should install fine.
after this get back in ur cmd prompt, cd to the proper directory and type this in
fastboot devices (enter)
u should get a listed device.
from here you can then change bootmode to properly reboot ur device
fastboot oem idme bootmode 4000 (enter)
fastboot reboot (enter)...
should be done! enjoy!
After the fastboot of the img file, I also had it just stick. I didn't have to reboot the PC though, I just reinstalled the device. As soon as the device was installed (I still had the cmd box open), it output:
Code:
downloading 'boot.img'... OKAY [ 3.053s]
booting... OKAY [ 0.013s]
finished. total time: 3.085s
and finished that process. The screen did some stuff, and then sat at a Reboot button... I finished the steps without any issues.
SUCCESS!!!
I've used the app Quick Boot a couple times now to go into Recovery Works great.
krelvinaz said:
After the fastboot of the img file, I also had it just stick. I didn't have to reboot the PC though, I just reinstalled the device. As soon as the device was installed (I still had the cmd box open), it output:
Code:
downloading 'boot.img'... OKAY [ 3.053s]
booting... OKAY [ 0.013s]
finished. total time: 3.085s
and finished that process. The screen did some stuff, and then sat at a Reboot button... I finished the steps without any issues.
SUCCESS!!!
I've used the app Quick Boot a couple times now to go into Recovery Works great.
Click to expand...
Click to collapse
when using apps to boot to recovery, can u get out of recovery without issue? someone said it gets stuck in the wrong bootmode?
Sent from my HTC Glacier using xda premium
I just tell TWRP to reboot and don't touch anything... it ends up booting into the OS normally (takes a while).
krelvinaz said:
I just tell TWRP to reboot and don't touch anything... it ends up booting into the OS normally (takes a while).
Click to expand...
Click to collapse
Yep, if you do everything right and have FFF and TWRP installed correctly, you should be able to flip between ROMS without too much trouble, and without have to use fastboot again.
Hmm...while attempting to reinstall the drivers for the Fire, I'm at a road block.
I see the kindle in device manager, and am informed that it's not installed correctly, but while manually choosing the drivers I'm greeted with the following (attached).
This is after choosing Android Phone from the available drivers.
Any ideas, guys?
reboot ur device and reconnect to ur PC.
Sent from my HTC Glacier using xda premium
Bricked?
Ive looked all over for a solution and cant find one anywhere. right after i did adb reboot, the device hung on the kindle fire screen, ive turned it off and back on, and nothing, ive restarted the computer, but adb just wont see the device, ive even tried reinstalling the drivers, and it went from unknown device to android adb interface, but adb still doesnt recognize it. ive rooted many devices, but this kindle fire is throwing me for a loop, please help
ur device is in fastboot, its time to do the fastboot commands to flash twrp.
Sent from my HTC Glacier using xda premium
leglerreddin said:
Ive looked all over for a solution and cant find one anywhere. right after i did adb reboot, the device hung on the kindle fire screen, ive turned it off and back on, and nothing, ive restarted the computer, but adb just wont see the device, ive even tried reinstalling the drivers, and it went from unknown device to android adb interface, but adb still doesnt recognize it. ive rooted many devices, but this kindle fire is throwing me for a loop, please help
Click to expand...
Click to collapse
when the device is in fastboot it is unrecognizable with adb, just enter the fastboot commands and you'll be fine.
smirkis said:
ur device is in fastboot, its time to do the fastboot commands to flash twrp.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I wish that was the case, i have tried a million different fastboot and adb commands, ive rebooted, used another os, the drivers are installed as an android composite adb interfaced, its still not registering as an adb or fastboot device.
EDIT: FORGET WHAT I SAID!!!
just go here http://rootzwiki.com/topic/12363-how-to-windows-install-twrp-20-on-your-kindle-fire/ that will fix everything just have to add a couple things to the original way of installing drivers
CrackMonkey91 said:
EDIT: FORGET WHAT I SAID!!!
just go here http://rootzwiki.com/topic/12363-how-to-windows-install-twrp-20-on-your-kindle-fire/ that will fix everything just have to add a couple things to the original way of installing drivers
Click to expand...
Click to collapse
I still had issues installing drivers after it booted to the yellow fire triangle (on Win7 x64 - even after adding the other device id to both x86 and x64 sections of the inf and ini of the drivers). Rebooting my computer with the Kindle plugged in caused the Kindle to reboot normally after which I used a terminal to set the boot mode to 4000:
Steps I took after doing step 'fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img' (enter):
- Reboot computer with Kindle plugged in. (Causes it to reboot normally)
- Open the terminal app. (I used Terminal Emulator)
- Type 'su', press enter. (Superuser will pop-up - select allow)
- Type 'idme bootmode 4000', press enter.
After this I was able to reboot normally without getting stuck on the yellow fire triangle and boot into recovery by pressing power on the fire icon.
uunnzz said:
- Reboot computer with Kindle plugged in. (Causes it to reboot normally)
After this I was able to reboot normally without getting stuck on the yellow fire triangle and boot into recovery by pressing power on the fire icon.
Click to expand...
Click to collapse
this my friend, is interesting.

[Q] Kindle Fire Bricked: exec "system/bin/sh": No such file or directory

I've looked everywhere for an answer to my question and have yet to find an answer. Probably because my Kindle Fire is truly bricked for good. But here is the series of events that lead to my current predicament.
1. I used Kindle Fire Utility 0.9.1 to root and install TWRP.
2. I was ignorant of the uses of TWRP so when I wanted to restore the Kindle to factory settings I did it within the kindle.
3. I ended up in TWRP so I looked up how to force the amazon update to the kindle. I cleared both caches and factory restore and then installed update.zip.
4. When I rebooted I am now stuck on the boot up screen with no access to TWRP. My computer still recognizes the kindle fire, but I can't access the directory of the kindle.
5. I've tried to use fastboot, Kindle Fire Utility, and anything else to knock it out of the boot logo, but I always am stopped by the error: exec "system/bin/sh": No such file or directory
i think you should try to reinstall twrp eighter with kfu or manually
kfu is the easier way - if you will try it manually this would be a good point to start: http://forum.xda-developers.com/showthread.php?t=1414832
then flash one of the prerooted stock images or cm7
b63 said:
i think you should try to reinstall twrp eighter with kfu or manually
kfu is the easier way - if you will try it manually this would be a good point to start: http://forum.xda-developers.com/showthread.php?t=1414832
then flash one of the prerooted stock images or cm7
Click to expand...
Click to collapse
I´m in the same situation. We can´t use kfu because everyrthing it does needs adb shell, wich isn´t working.
I´d love to be wrong, but the only solution we have is getting a factory cable.
adb is'nt working in fastboot - could you give this a try?
fastboot -i 0x1949 getvar product
it should return "kindle"
btw. twrp installation of kfu don't use adb - it works with fastboot
b63 said:
adb is'nt working in fastboot - could you give this a try?
fastboot -i 0x1949 getvar product
it should return "kindle"
btw. twrp installation of kfu don't use adb - it works with fastboot
Click to expand...
Click to collapse
The problem is we are not in fastboot mode. We have normal boot enabled.
your in normal boot and don't have adb available ?
sounds bad - maybe your only solution is really the factory cable !
would you try my last idea ?
do
fastboot -i 0x1949 getvar product
should say <waiting for device>
and power off (hold ~20sec) and power back on before the command times out (~1min)
if we are lucky we should get a response
try it more than one times
b63 said:
your in normal boot and don't have adb available ?
sounds bad - maybe your only solution is really the factory cable !
would you try my last idea ?
do
fastboot -i 0x1949 getvar product
should say <waiting for device>
and power off (hold ~20sec) and power back on before the command times out (~1min)
if we are lucky we should get a response
try it more than one times
Click to expand...
Click to collapse
Thanks, but it doesn´t work. Factory cable is the last hope.
Its not bricked, only missing the .sh in the bin directory. Try these commands from the bootloop screen.
./ adb devices
If device is listed
./ adb reboot recovery
qv775219 said:
Its not bricked, only missing the .sh in the bin directory. Try these commands from the bootloop screen.
./ adb devices
If device is listed
./ adb reboot recovery
Click to expand...
Click to collapse
It reboots the device but not to recovery.
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
osozraz said:
It reboots the device but not to recovery.
Click to expand...
Click to collapse
It looks like flashing the stock rom erases FireFireFire and recovery
osozraz said:
It reboots the device but not to recovery.
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
It looks like flashing the stock rom erases FireFireFire and recovery
Click to expand...
Click to collapse
OK, what you need is a recovery .img file. Once you have the .Ingram file type these commands.
From bootloop screen
./adb reboot bootloader
From bootloader screen
./fastboot flash recovery recovery.img
(Recovery image needs to be named recovery.img)
After flash is done
./fastboot reboot recovery
If have issues from fastboot, reboot the device and from bootloop screen
./adb reboot recovery
qv775219 said:
OK, what you need is a recovery .img file. Once you have the .Ingram file type these commands.
From bootloop screen
./adb reboot bootloader
From bootloader screen
./fastboot flash recovery recovery.img
Click to expand...
Click to collapse
First of all, thank you very much for your help.
I type
adb reboot bootloader
and the device reboots, but
fastboot flash recovery recovery.img
gives the same result as before
< waiting for device >
just a suggestion:
fastboot -i 0x1949 flash recovery recovery.img
or
fastboot -i 0x18d1 flash recovery recovery.img
b63 said:
just a suggestion:
fastboot -i 0x1949 flash recovery recovery.img
or
fastboot -i 0x18d1 flash recovery recovery.img
Click to expand...
Click to collapse
If I am not mistaken, to execute fastboot you have to boot in fastboot mode. My fire is always booting in Normal mode so all fastboot commands i execute have the same result:
< waiting for device >
the adb command suceeded
maybe this helps to get to fastboot:http://forum.xda-developers.com/showthread.php?t=1414832
allthrough i doubt
edit: i saw - we have allready tried - but adb was'nt working before - now it's working ?
edit2: just for info: kfu uses this to switch to fastboot:
adb shell "idme bootmode 4002"
adb shell "reboot"
don't think that this works
b63 said:
the adb command suceeded
maybe this helps to get to fastboot:http://forum.xda-developers.com/showthread.php?t=1414832
allthrough i doubt
edit: i saw - we have allready tried - but adb was'nt working before - now it's working ?
Click to expand...
Click to collapse
Adb works. If I type adb devices it shows my Kindle is connected. BUT when executing adb shell or commands that use the sh like adb logcat it fails with the message from the topic title.
If adb shell were working i could use pokey9000´s program to boot in fastboot.
would need a command like "adb reboot bootloader" but never saw such one
could be creative and try "adb reboot fastboot" but it's a shot in the blue ...
sorry
I think we have the same problem
I think we have the same problem @osozraz. I'll share my experience and add more information that I feel is relevant.
1. I also used Kindle Fire Utility to root my Kindle and install TWRP 2.0.
2. I tried installing CM7, it worked, but figured I'd like to get back to stock firmware.
3. In TWRP, I too cleared both caches, factory restored and then proceeded to install update.zip.
4. When the Kindle rebooted it was stuck on the Kindle Fire boot screen.
Now, I researched and tried a couple of unbricking/debricking methods and failed. Here is what I've observed:
a. My device drivers are fine. If I do 'adb devices' it's recognized by the PC. However if I try 'fastboot devices' it returns nothing at all. I assume
b. I also tried the Kindle Fire Utility. Any command I try to do gets stuck on <waiting for device>. I figured that while KFU commands work on the PC's end, it doesn't work on the Kindle Fire. It's basically as if the Kindle is not connected to the computer (try running some of the commands in KFU with the Kindle disconnected, such as changing the bootmode. It'll still say <waiting for device>).
c. I can't to 'adb root' as it will say I don't have permission. Same with adb 'remount' or even 'adb shell', which from what I've gathered is crucial to this process. I can do 'adb reboot' though. I haven't tried rebooting into restore mode but I will try when I get a new MicroUSB B cable.
d. I can't change the bootmode, it gets stuck on <waiting for device> as I've said in point b. Is there a way to actually know what bootmode your device is in? I'm just assuming it's in normal bootmode because I can get fastboot.exe to detect it on the PC. In addition, KFU returns 'unknown'.
Factory Cable
Of course, there's the method of using a factory cable. I'm trying to create one and from what I've gathered there are two ways to do so: 1) use a breakout board (this one I think is the safest way to go) or 2) hack together one using your existing cable: http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html. I'm also still scouring the forums for additional information that may help debrick/unbrick my device without the use of the cable. I'm afraid that I might end up damaging my PC or Kindle if I create the cable incorrectly. I've been following this thread though http://forum.xda-developers.com/showthread.php?t=1392693 because I'm thinking of actually just buying one.
Hopes these all help.
You are probably out of luck and need a factory cable at the moment.
You wiped /system/ or killed its permissions, and thus it is unable to load shell.
@osozraz and @jkspn looks like we all have the same problem. Thanks for all the suggestions. I've tried everything. Looks like the only option left is the factory wire. Only problem is that I have 0 skills with smoldering. I guess I could buy one but the site doesn't look like it will be restocking anytime soon. I'll see if I can't return it to Best Buy.
shop.teamblackhat.info/Factory-style-programming-cable-for-Motorola-FactCable.htm
When it says waiting for device, what happens when you unplug and plug in the device?

[Q] kindle stuck in fastboot mode but won't accept commands

I tried to install CM9 to my kindle, but I didn't realize I was supposed to install TWRP first. I am stuck at the yellow triangle, can't get into recovery (of any sort).
When I plug in the USB cable I type in
Code:
fastboot getvar product
which returns: kindle.
I tried to push TWRP using
Code:
fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
and it returns: sending 'recovery' (5568 KB) but nothing ever happens.
I have tried draining the battery and recharging it completely. I have been able to get into recovery before by tapping the power button but don't seem to be able to do it anymore.
adb doesn't work at all. I should mention I am on a mac so KFU didn't work for me either.
I promise to be more careful in the future, can someone please help me save my kindle?
Try omitting the "-i 0x1949" from your command and flash it again.
EDIT: While you're at it, download TWRP again and confirm its md5 checksum before flashing it again.
md5 is ok, I tried without the switch as well still nothing
whtmgcwmn said:
md5 is ok, I tried without the switch as well still nothing
Click to expand...
Click to collapse
What recovery did you use to flash CM9 in the first place? What happens when you try to boot into the system?
I'm starting to recall some people having problems with the mac version of fastboot. Do you have another OS available just to compare things?
in my case the commands only return "is <waiting device>"
I had CWM I believe it's still in there somewhere. But I can't get to it anymore. Sometimes I think CM9 is going to start up because I do get the splash screen but it just goes on for like 15 minutes then the kindle restarts and goes back to the yellow triangle of doom.
EDIT: No unfortunately all I have is the mac
nailanb13 said:
in my case the commands only return "is <waiting device>"
Click to expand...
Click to collapse
If you're using Windows, read the first three posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
and make sure your drivers are working properly.
whtmgcwmn said:
I had CWM I believe it's still in there somewhere. But I can't get to it anymore. Sometimes I think CM9 is going to start up because I do get the splash screen but it just goes on for like 15 minutes then the kindle restarts and goes back to the yellow triangle of doom.
EDIT: No unfortunately all I have is the mac
Click to expand...
Click to collapse
I hope you weren't using Hashcode's CWMR...
In any case, I believe I've seen another user struggle with fastboot on the mac. You might be having the same problem, but I can't find that thread. You might want to look into building Ubuntu Linux on a USB stick and try running that on your mac. Otherwise, you'll have to wait for someone who's used those tools on the mac to chime in here. I've never played around with it.
kinfauns said:
I hope you weren't using Hashcode's CWMR...
In any case, I believe I've seen another user struggle with fastboot on the mac. You might be having the same problem, but I can't find that thread. You might want to look into building Ubuntu Linux on a USB stick and try running that on your mac. Otherwise, you'll have to wait for someone who's used those tools on the mac to chime in here. I've never played around with it.
Click to expand...
Click to collapse
I have no idea which CWM I have. I couldn't find the mac fastboot thread either, I guess I will just put it away for now until I get access to a pc.
Looking above there is a good chance twrp sent I'm pretty sure now all you need to do is reset your bootmode
fastboot oem idme bootmode 4000
fastboot reboot
Do you try use factory cable? If not, let factory cable and run command
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
chamnv said:
Do you try use factory cable? If not, let factory cable and run command
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Click to expand...
Click to collapse
Not to just sit here and tromp on your toes chamnv but the title of this thread is "kindle stuck in fastboot mode but wont accept commands" my impression of a factory cable is that it puts you in fastboot and secondly above he has attempted to send a new recovery why would he then send an old one?
Thepooch said:
Not to just sit here and tromp on your toes chamnv but the title of this thread is "kindle stuck in fastboot mode but wont accept commands" my impression of a factory cable is that it puts you in fastboot and secondly above he has attempted to send a new recovery why would he then send an old one?
Click to expand...
Click to collapse
sorry to laugh but hehehe
whtmgcwmn said:
I tried to install CM9 to my kindle, but I didn't realize I was supposed to install TWRP first. I am stuck at the yellow triangle, can't get into recovery (of any sort).
When I plug in the USB cable I type in
Code:
fastboot getvar product
which returns: kindle.
I tried to push TWRP using
Code:
fastboot -i 0x1949 flash recovery openrecovery-twrp-blaze-2.1.1.img
and it returns: sending 'recovery' (5568 KB) but nothing ever happens.
I have tried draining the battery and recharging it completely. I have been able to get into recovery before by tapping the power button but don't seem to be able to do it anymore.
adb doesn't work at all. I should mention I am on a mac so KFU didn't work for me either.
I promise to be more careful in the future, can someone please help me save my kindle?
Click to expand...
Click to collapse
Just unplug the KF from the USB, hold the power button and turn it back on. Repeat the process.
fastboot -i 0x1949 flash bootloader <name of firefirefire image here>
fastboot -i 0x1949 flash recovery <name of recovery image here>

Please Explain Red Wipe Screen

I have tried several times to get CM 10.1 installed on my Kindle Fire 8.9 and every time I get the red wipe screen trying to install the 2nd boot loader. After searching through the forums I have not found a definitive explanation (not that its not out there, but i didn't find one) of what causes the red screen, just how to recover from it.
I have tried using HashCode's process
http://forum.xda-developers.com/showthread.php?t=2128175
and also Option (41) in KFFirstAide
Can someone please explain what the red wipe screen indicates on the Kindle Fire 8.9, so I can avoid it and get the 2nd boot loader installed?
My Kindle is currently running Version 8.1.4 installed from the latest KFFirstAide (option 7). I have successfully rooted the device and I have been able to recover after the red screen each time.
Device Status before attempting to install 2nd boot loader
- Rooted using B4nary's Tool (v18.5.1)
- Erased Kindle Cache and User Data
- Enabled ADB on Kindle
- Enabled Allow 3rd party software
- Verified ADB Commands can be executed
- Verified Fastboot Commands can be executed
Thank You in Advance!
Derek
drockmd said:
I have tried several times to get CM 10.1 installed on my Kindle Fire 8.9 and every time I get the red wipe screen trying to install the 2nd boot loader. After searching through the forums I have not found a definitive explanation (not that its not out there, but i didn't find one) of what causes the red screen, just how to recover from it.
I have tried using HashCode's process
http://forum.xda-developers.com/showthread.php?t=2128175
and also Option (41) in KFFirstAide
Can someone please explain what the red wipe screen indicates on the Kindle Fire 8.9, so I can avoid it and get the 2nd boot loader installed?
My Kindle is currently running Version 8.1.4 installed from the latest KFFirstAide (option 7). I have successfully rooted the device and I have been able to recover after the red screen each time.
Device Status before attempting to install 2nd boot loader
- Rooted using B4nary's Tool (v18.5.1)
- Erased Kindle Cache and User Data
- Enabled ADB on Kindle
- Enabled Allow 3rd party software
- Verified ADB Commands can be executed
- Verified Fastboot Commands can be executed
Thank You in Advance!
Derek
Click to expand...
Click to collapse
Can anyone help with this? I have been through the process numerous times and i still get the red wipe screen.
drockmd said:
Can anyone help with this? I have been through the process numerous times and i still get the red wipe screen.
Click to expand...
Click to collapse
I used this tool KFHD_SRTv2.1- 8.1.4 To get into fastboot when I had the solid red screen then used option 7 to completely wipe and restore their is probably another way to just do the boot but it did work for me (did it today even)
Turn the kindle off (hold power down)
Load the KFHD_SRTv2.1- 8.1.4 tool using run as administrator
then use option 1
once your kindle says its in fastboot then close that utility and run the First aid
drockmd said:
I have tried several times to get CM 10.1 installed on my Kindle Fire 8.9 and every time I get the red wipe screen trying to install the 2nd boot loader. After searching through the forums I have not found a definitive explanation (not that its not out there, but i didn't find one) of what causes the red screen, just how to recover from it.
I have tried using HashCode's process
http://forum.xda-developers.com/showthread.php?t=2128175
and also Option (41) in KFFirstAide
Can someone please explain what the red wipe screen indicates on the Kindle Fire 8.9, so I can avoid it and get the 2nd boot loader installed?
My Kindle is currently running Version 8.1.4 installed from the latest KFFirstAide (option 7). I have successfully rooted the device and I have been able to recover after the red screen each time.
Device Status before attempting to install 2nd boot loader
- Rooted using B4nary's Tool (v18.5.1)
- Erased Kindle Cache and User Data
- Enabled ADB on Kindle
- Enabled Allow 3rd party software
- Verified ADB Commands can be executed
- Verified Fastboot Commands can be executed
Thank You in Advance!
Derek
Click to expand...
Click to collapse
I know you said you aren't on 8.3, but it sounds like the bootloader issue Hash talks about in step 4.5 of his post. You could try flashing the bootloader he posts in that step to see if that fixes your issue. I had the same problem, until I flashed it.
Just an idea, I am in no way an expert just a tinkerer.
lizzord30 said:
I used this tool KFHD_SRTv2.1- 8.1.4 To get into fastboot when I had the solid red screen then used option 7 to completely wipe and restore their is probably another way to just do the boot but it did work for me (did it today even)
Turn the kindle off (hold power down)
Load the KFHD_SRTv2.1- 8.1.4 tool using run as administrator
then use option 1
once your kindle says its in fastboot then close that utility and run the First aid
Click to expand...
Click to collapse
I too have the red screen, I tried to use the SRtool but was unsuccessful in recovering, can u provide anymore information? i'm really freaking out a little because i'm new to this stuff
I think fattire said Amazon enabled fastboot in this state. On KF2 and KFHD7, this is possible with a factory cable. I guess it's also possible that they have enabled the use of the factory cable for the KFHD8.9, but I'm only speculating.
Before the update, flashing unsigned boot and recovery partitions without the 2nd bootloader properly functioning, the device just wouldn't turn on. Now, not only will the device turn on, but some are even fixable in this state. I'm wondering if Amazon realized that wasn't cost effective to send every broken modified device to a specific secure location to get reflashed.
I don't quite remember what I did, but I was able to fix the "red wipe" screen on my Kindle 8.9.
I think I got this when I first tried installing 8.9StariROM when it was first posted on the forum. I did not know that the red screen could appear if TWRP was not installed already, and I think that's why I got the red screen error.
I didn't really know what it was all about, but somehow I was able to make my kindle go into the fastboot using this command (fastboot -i 0x1949 getvar product) and basically followed the instruction here: http://forum.xda-developers.com/showthread.php?t=2128175
I kept getting device not found error on ADB commands, so I skipped to STEP 4.5 and ran below commands in order: (of course, I downloaded all those files as well)
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.3.0.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.4.4.0-recovery.img
then I think I ran fastboot -i 0x1949 flash system starirom-system.img to load the system image and I was able to have a working kindle 8.9 again.
I hope this helps.
Here is what I did to get myself out of trouble after screwing around with my KFHD 8.9 and getting a red screen (NOTE: I am assuming you have already installed the proper drivers so your PC can recognize the Kindle Fire HD):
1) Downloaded the above-mentioned KFHD SRT tool from here: https://docs.google.com/open?id=0B4lZEJI5lYeMR1YteUt2MGxZTGM) and the boot.img and recovery.img from here: https://drive.google.com/folderview?id=0B4lZEJI5lYeMNGdXMHI3T3pKM2c&usp=sharing
2) Unzipped the SRT tool into a folder on my Windows 7 boot drive (C:\KFHD_SRT_v2.1), and copied over the two .img files to the /images sub-folder.
3) Ran SR Tool.bat in Admin mode (right-click, Run As Administrator, click Yes to accept)
4) Turned off my Kindle by holding the power button 10 seconds until the screen was off
5) Chose option 1. Enable Fastboot, chose "n" when the tool asks if the device is turned on, then pressed the power button once on the Kindle to turn the screen on. Voilà, I was in Fastboot mode.
6) From a command line prompt (started in Admin mode as always), went to the /images sub-folder of the KFHD SRT tool and typed in the following commands, one at a time (just press Enter at the end of each, and wait until done):
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img (note: this may take a few minutes, depending on the speed of your USB port)
7) Still from the same command prompt, rebooted the tablet using the following command (type it in and press Enter):
fastboot -i 0x1949 reboot
I was back in business from there.
Can we get this as a sticky in the Dev Section? it took me 2 weeks to get my system back from a red screen that the below was able to do.
GenghisKhan67 said:
Here is what I did to get myself out of trouble after screwing around with my KFHD 8.9 and getting a red screen (NOTE: I am assuming you have already installed the proper drivers so your PC can recognize the Kindle Fire HD):
1) cant post this but look at above post.
2) Unzipped the SRT tool into a folder on my Windows 7 boot drive (C:\KFHD_SRT_v2.1), and copied over the two .img files to the /images sub-folder.
3) Ran SR Tool.bat in Admin mode (right-click, Run As Administrator, click Yes to accept)
4) Turned off my Kindle by holding the power button 10 seconds until the screen was off
5) Chose option 1. Enable Fastboot, chose "n" when the tool asks if the device is turned on, then pressed the power button once on the Kindle to turn the screen on. Voilà, I was in Fastboot mode.
6) From a command line prompt (started in Admin mode as always), went to the /images sub-folder of the KFHD SRT tool and typed in the following commands, one at a time (just press Enter at the end of each, and wait until done):
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img (note: this may take a few minutes, depending on the speed of your USB port)
7) Still from the same command prompt, rebooted the tablet using the following command (type it in and press Enter):
fastboot -i 0x1949 reboot
I was back in business from there.
Click to expand...
Click to collapse

[Q] TWRP flash failed but firefirefire installed, now I can't get to fastboot mode

I've been trying to root my Kindle Fire running 6.3.3. I bought a fastboot cable and got it to boot into fastboot mode to flash TWRP and firefirefire. I ran the commands and TWRP failed but firefirefire installed. Now when the kindle boots I get the firefirefire bootloader but it cant boot into the recovery because the TWRP never installed. Also, I can't get it to fastboot anymore, not even with the cable. Can anyone please help me get TWRP installed? I've read many forums and tried about everything I found.
kas782000 said:
I've been trying to root my Kindle Fire running 6.3.3. I bought a fastboot cable and got it to boot into fastboot mode to flash TWRP and firefirefire. I ran the commands and TWRP failed but firefirefire installed. Now when the kindle boots I get the firefirefire bootloader but it cant boot into the recovery because the TWRP never installed. Also, I can't get it to fastboot anymore, not even with the cable. Can anyone please help me get TWRP installed? I've read many forums and tried about everything I found.
Click to expand...
Click to collapse
FFF bootloader supports fastboot commands, but the flash command is now
fastboot flash recovery file name
ie drop the -i 0x1949
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img
because the fastboot mode window is short
with kindle connected to pc, power off kindle, enter commands, then power on kindle
sd_shadow said:
FFF bootloader supports fastboot commands, but the flash command is now
fastboot flash recovery file name
ie drop the -i 0x1949
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img
because the fastboot mode window is short
with kindle connected to pc, power off kindle, enter commands, then power on kindle
Click to expand...
Click to collapse
I've been trying this for about 30 minutes or so with no luck...I even downloaded a different version of the twrp image. Do I have to wait for the fastboot screen to start the command or do I start the process before powering on the device? I'm not really sure what I'm doing wrong here.
kas782000 said:
I've been trying this for about 30 minutes or so with no luck...I even downloaded a different version of the twrp image. Do I have to wait for the fastboot screen to start the command or do I start the process before powering on the device? I'm not really sure what I'm doing wrong here.
Click to expand...
Click to collapse
Should be able to do it either way but I press enter, before the power button
This will not work if drivers are not correct
could try
Code:
fastboot devices
as a test should get something like
Code:
123456789 bootloader
back in command prompt
I finally got it to work and I can't thank you enough. You were right. I knew my computer recognized the device with adb in normal boot but my computer wouldn't recognize the device in fastboot mode until i reinstalled the android driver while it was in fastboot mode. Now I have a custom ROM running Google Play apps! Again, thank you!
Hey, I don't know if this will help others, but I had a hell of a time trying to get my kindle to recognize while in the bootloader/fastboot mode... It frustrated me so much that I had to write about it.
I recently switched to Windows 10, so it seems like my computer is relearning drivers and stuff...
My kindle was fine when on, and I could issue adb commands from the main screen, but when in fastboot mode, I couldn't get it detected. I knew the drivers were an issue, but I couldn't figure out how to do it. I looked at Amazon's support pages, went through the SDK route, tinkered with the adb.ini and so forth... to no avail.
Post after post said that the easiest way to install the drivers was through the Kindle Fire Utility, but for some reason, the drivers in the .bat file kept failing and would not load. It took a good few hours to figure out the solution.
When I asked the Web why the drivers kept failing, I came across a post that said Windows was actually blocking unknown drivers from loading onto my system. I really wish Windows had told me that instead of just saying "Fail"...
I had to hold down the shift button and click restart on the start menu, and when the computer restarted, I when through: troubleshoot -> advanced options -> startup settings and clicked on Restart. It eventually gave me the option to disable that signature verification [F7]
My explanation is crude, because I want you to look it up properly. Just search for "disable driver signature enforcement" and you should be fine.
Hope this helps others out. I may have to revisit my own post just to see how to do this again.

Categories

Resources