Related
I have had a Kindle Fire since they day they came out. I immediately disliked the stock Rom so I ran the kindle fire utility and installed Fire Fire Fire and TWRP, rooted it, and installed CM7 Rom which has been working great. Transferred files and programs between my PC and Kindle with no issue for months. Now with all the ICS roms available and working I decided to try and upgrade to one of those and thats when everything went wrong. Its in a bootloop and the triangle appears, fades, lights up again and immediately boots to TWRP. I have flashed the entire kindle using TWRP trying to get everything off of it. Upon plugging it into my PC BRIEFLY when the triangle logo pops up I get a "USB device not recognized" on my PC. I have tried using KFUtility to reinstall drivers, tried uninstalling n reinstalling drivers but the same thing happens. I cannot use TWRP to mount at all, nothing happens. Kindle Fire UTility keeps saying adb offline, CMD adb devices also results in 0 devices found. I have tried putting it on normal boot using both ADB and KFUtility and it says "wait for device" and nothing ever happens. Any idea? Not even sure if I have a rom installed on my kindle anymore but my PC wontread it so I cannot push another image to it. Got a plane trip on Saturday and would love to have this working to kill the bordom lol. Any advise would be greatly appreciated.
It sounds like your bootmode is set to recovery. An easy way to fix this is download FFF1.4 to your computer and use the mount function in recovery to place it on your sdcard.
Flash it in recovery as you would a rom except don't wipe anything. When you reboot, hold the power button like you're trying to enter recovery and you'll be given the option to reset the bootmode.
Thank you so much for your advice but there in lies the problem. Inside the recovery console i choose to mount it and nothing happens. My PC will not let me access the kindle in anyway at all, either mounting the SD Card or via ADB/KFUtility.
anomiefaunus said:
Thank you so much for your advice but there in lies the problem. Inside the recovery console i choose to mount it and nothing happens. My PC will not let me access the kindle in anyway at all, either mounting the SD Card or via ADB/KFUtility.
Click to expand...
Click to collapse
Generally, the only thing that would prevent adb/kfu from communicating with the device is the drivers. Make sure they're installed properly. You may have to uninstall them (delete if applicable) and reinstall them.
Follow the instructions in this guide to install and verify your drivers.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
K heres the latest (we r making progress!)
I got my device to be detected by my PC and used KFutility to change it to normal boot. Now instead of booting into recovery everytime it boots normally.... to a black screen (guessing my rom is shot or I deleted it while playing with it). The issue is the ONLY time my PC recognizes my kindle is for a .5 second period when i first turn my KF on and the yellow triangle appears. I can use this window to change it to normal bootmode, reinstall TeamWin, stuff like that, but i cannot mount it so I can transfer or adb so I can push. You can watch device manager and it'll pop up ADB android phone or whatever it should but poof, a second later gone.
anomiefaunus said:
K heres the latest (we r making progress!)
I got my device to be detected by my PC and used KFutility to change it to normal boot. Now instead of booting into recovery everytime it boots normally.... to a black screen (guessing my rom is shot or I deleted it while playing with it). The issue is the ONLY time my PC recognizes my kindle is for a .5 second period when i first turn my KF on and the yellow triangle appears. I can use this window to change it to normal bootmode, reinstall TeamWin, stuff like that, but i cannot mount it so I can transfer or adb so I can push. You can watch device manager and it'll pop up ADB android phone or whatever it should but poof, a second later gone.
Click to expand...
Click to collapse
Get your device drivers working so you can use adb. Follow the instructions in the post below...
http://forum.xda-developers.com/showpost.php?p=26144447
That is excellent advice and I wish it would work but I cannot pull up ADB once in TeamWin. Keeps saying no devices. As i said my PC detects it and ADB will detect it for .5 seconds on the orange triangle. Once the orange triangle disappears and it either boots to blackness or boots to TeamWin ADB stops recognizing my device. But I will play around with your suggestions once I get off work and let you know what i find out. Thanks again for everyones support.
Frozen screen during rooting
Hi,
I am new to the forum. I have a kF screen stuck (where it says 'kindle fire') while I was trying to root it. I tried hard reset, charging for half hour, calling AMAZON...nothing works. The screen goes off if I hold it for 20 seconds but when I put it back on same thing. I was trying to root it with 'fastboot (?). Is there anything at all I can do? Thanks.
peredexter said:
Hi,
I am new to the forum. I have a kF screen stuck (where it says 'kindle fire') while I was trying to root it. I tried hard reset, charging for half hour, calling AMAZON...nothing works. The screen goes off if I hold it for 20 seconds but when I put it back on same thing. I was trying to root it with 'fastboot (?). Is there anything at all I can do? Thanks.
Click to expand...
Click to collapse
Don't hijack the threads please. If you have a problem or question, post it in the Q&A section.
Alright so I used KFU to root my kindle to android market then I used TWRP to install CyanogenMod 7. Everything was fine tell I wanted to restore to stock. I downloaded the Kindle Fire 6.3 installed it then my kindle rebooted. After this happened, everytime it comes on dimly lit then goes to the brightest setting then goes back to dim brightness all while remaining on the standard kindle fire load screen. The letter animation stops shortly after it goes back to dim brightness. On my computer it no longer shows up under my computer but in device manager it is called a Amazon kindle under disk drives with 0 mb of space. On KFU I can get it to show up ADB online but status is Unkown. After I try to change boot mode (normal, fastboot, and recovery) or try and install any of it the kindle turns out comes back on for 4 to 6 seconds then shuts off comes back on and freezes. Also before changing boot mode any one I click it says is no longer on the device. I have also tryed KF unbrick with no help ether.
Does anyone know how to fix this pleas and think you.
mellowboombox said:
Alright so I used KFU to root my kindle to android market then I used TWRP to install CyanogenMod 7. Everything was fine tell I wanted to restore to stock. I downloaded the Kindle Fire 6.3 installed it then my kindle rebooted. After this happened, everytime it comes on dimly lit then goes to the brightest setting then goes back to dim brightness all while remaining on the standard kindle fire load screen. The letter animation stops shortly after it goes back to dim brightness. On my computer it no longer shows up under my computer but in device manager it is called a Amazon kindle under disk drives with 0 mb of space. On KFU I can get it to show up ADB online but status is Unkown. After I try to change boot mode (normal, fastboot, and recovery) or try and install any of it the kindle turns out comes back on for 4 to 6 seconds then shuts off comes back on and freezes. Also before changing boot mode any one I click it says is no longer on the device. I have also tryed KF unbrick with no help ether.
Does anyone know how to fix this pleas and think you.
Click to expand...
Click to collapse
One of two things has probably happened here. Either you did not use the factory reset to delete the /data partition prior to flashing the stock software or the system software is damaged or missing from the /system partition. If at all possible, you will have to try to put your KF into fastboot mode using adb. Unfortunately, the odds are against you and my guess is any "adb shell" command will fail. Temporary fastboot through the bootloader is also a non-starter because you have the stock bootloader installed. That leaves the factory cable or opening the back cover as your last two options. The details are spelled out here...
http://forum.xda-developers.com/showthread.php?t=1668159
I suggest you get the factory cable, reflash TWRP, and try a factory reset. If that doesn't work, wipe the system partition as well, unmount all partitions and try flashing the stock software again.
Hi! Yesterday I rooted my Kindle Fire HD 8.9 with no problems. The problems came after I installed TWRP before installing Cyanogenmod and GApps. Long story short, I got those on there eventually, and when I rebooted my Kindle, it showed the Cyanogenmod splashscreen/ animation, so I thought everything went well. After about, probably, 8 minutes it flashed the Android lock screen, but that's it. So I turned it off, then on again. Now, when I turn it on, first it shows the regular "Kindle Fire" logo with "Fire" being in orange, and then changing to blue, then it just loops showing the Cyanogenmod animation, then flashing the Android lock screen for a split second, then repeating that from the Cyanogenmod animation. I can't get into TWRP when I press the volume up key IMMEDIATELY after I turn the Kindle on. But, I can get it into Fastboot mode, except anytime I do a command, it'll either say "error: device not found", or something like, or it'll say "List of devices connected" followed by the serial number, and next to that "offline". If anyone could help me with this, it would be GREATLY appreciated.
Or, is there a way to completely reset it? At this point, I honestly don't care if I end up with the Amazon OS again, I just want my Kindle back
Anything? I just want to be able to use my Kindle again... At this point I'd rather it have a full factory reset, and just start fresh, as if none of this happened, and leave it that way... :crying:
Fleetwood Mac & Cheese said:
Hi! Yesterday I rooted my Kindle Fire HD 8.9 with no problems. The problems came after I installed TWRP before installing Cyanogenmod and GApps. Long story short, I got those on there eventually, and when I rebooted my Kindle, it showed the Cyanogenmod splashscreen/ animation, so I thought everything went well. After about, probably, 8 minutes it flashed the Android lock screen, but that's it. So I turned it off, then on again. Now, when I turn it on, first it shows the regular "Kindle Fire" logo with "Fire" being in orange, and then changing to blue, then it just loops showing the Cyanogenmod animation, then flashing the Android lock screen for a split second, then repeating that from the Cyanogenmod animation. I can't get into TWRP when I press the volume up key IMMEDIATELY after I turn the Kindle on. But, I can get it into Fastboot mode, except anytime I do a command, it'll either say "error: device not found", or something like, or it'll say "List of devices connected" followed by the serial number, and next to that "offline". If anyone could help me with this, it would be GREATLY appreciated.
Click to expand...
Click to collapse
Are you taking care to include the "-i 0x1949" parameter in your fastboot commands? That's one of the things I would think is preventing the kindle from being recognized. Also, try downloading and installing the Kindle ADB drivers.
monster1612 said:
Are you taking care to include the "-i 0x1949" parameter in your fastboot commands? That's one of the things I would think is preventing the kindle from being recognized. Also, try downloading and installing the Kindle ADB drivers.
Click to expand...
Click to collapse
Thank you! I eventually got it fixed. Now it's just looping the regular "Kindle Fire" logo in orange :/ but I'm working on getting it back to normal.
Hi there!
I think I may have bricked my Fire TV Stick 1 (bought at launch in Germany)...
Current situation:
- stick turns on, shows white amazon logo on black background
- continuously rebooting; ~5s black screen, ~5s amazon logo
After months not having it used, I found out I may be able to root it by now. So I did research over the vast amount of threads and posts and was overwhelmed by the information... So I tried to get started but struggled to find the right steps and therefore maybe failed.
I updated it to 5.0.5 (stock) and tried King Root, then Kingo Root, which was a success.
I tried to use the TWRP 3.0.0-7 v2 zip and used the sh command from the respective thread (I thought that was it, since all my devices before used either TWRP or CWM).
To this point, all went through and I wanted to reboot into recovery, but there was only this generic (stock?) red text recovery screen. I waited to be sure, nothing happened and I unplugged it to reboot.
It booted fine and I reflashed the TWRP zip, in case I didn't do it properly. Again it did as expected.
I then pushed the latest prerooted 5.2.0.1 zip and rebooted to recovery, but again this generic screen, so I unplugged it early, I think.
From there on, I got stuck at the white amazon logo, see above.
I did not unlock the bootloader, adb shell confirmed it not being unlocked before.
During bootloops, I did not manage to get any control via adb or fastboot.
So, is it bricked once and for all? If not, how can I save it?
I don't care about anything stored on it.
I also have a Y-USB-OTG cable and connected a keyboard before, but could not interfere yet.
(If bricked, would a Teensy be of any use? I have one from CCast rooting days)
Thanks for reading and in advance.
I had same problem with my fire stick when used the USB power of my TV.
Did you try to power the fire stick TV with the power point and USB adapter?
l_aios said:
Hi there!
I think I may have bricked my Fire TV Stick 1 (bought at launch in Germany)...
Current situation:
- stick turns on, shows white amazon logo on black background
- continuously rebooting; ~5s black screen, ~5s amazon logo
After months not having it used, I found out I may be able to root it by now. So I did research over the vast amount of threads and posts and was overwhelmed by the information... So I tried to get started but struggled to find the right steps and therefore maybe failed.
I updated it to 5.0.5 (stock) and tried King Root, then Kingo Root, which was a success.
I tried to use the TWRP 3.0.0-7 v2 zip and used the sh command from the respective thread (I thought that was it, since all my devices before used either TWRP or CWM).
To this point, all went through and I wanted to reboot into recovery, but there was only this generic (stock?) red text recovery screen. I waited to be sure, nothing happened and I unplugged it to reboot.
It booted fine and I reflashed the TWRP zip, in case I didn't do it properly. Again it did as expected.
I then pushed the latest prerooted 5.2.0.1 zip and rebooted to recovery, but again this generic screen, so I unplugged it early, I think.
From there on, I got stuck at the white amazon logo, see above.
I did not unlock the bootloader, adb shell confirmed it not being unlocked before.
During bootloops, I did not manage to get any control via adb or fastboot.
So, is it bricked once and for all? If not, how can I save it?
I don't care about anything stored on it.
I also have a Y-USB-OTG cable and connected a keyboard before, but could not interfere yet.
(If bricked, would a Teensy be of any use? I have one from CCast rooting days)
Thanks for reading and in advance.
Click to expand...
Click to collapse
I guess you did not read enough.
At this point in time you can only root (kingoroot or kingroot) and replace root with SuperSu on a Firestick. TWRP (recovery) can not be installed because it was not released by rbox as of yet, that particular recovery\pre-rooted image is for firetv1 upgraded to OS5 and not for firestick.
Sorry man.
Have you tried to connect to a computer via USB and run kingoroot or kingroot for windows (whatever you used)? It is a small chance that will recover but it is a slim one....
mjnman said:
I had same problem with my fire stick when used the USB power of my TV.
Did you try to power the fire stick TV with the power point and USB adapter?
Click to expand...
Click to collapse
I could not remember, so I just retried it with two different chargers and two different cables (both used to power my Nexus 5).
Unfortunately resulting in the very same loop... But thanks nonetheless.
bula1ca said:
I guess you did not read enough.
At this point in time you can only root (kingoroot or kingroot) and replace root with SuperSu on a Firestick. TWRP (recovery) can not be installed because it was not released by rbox as of yet, that particular recovery\pre-rooted image is for firetv1 upgraded to OS5 and not for firestick.
Sorry man.
Have you tried to connect to a computer via USB and run kingoroot or kingroot for windows (whatever you used)? It is a small chance that will recover but it is a slim one....
Click to expand...
Click to collapse
Dang... Usually I don't make mistakes this dumb. Guess I learned my first lesson. I'll try to trace my mistake though, for future attempts.
I rooted it with the Kingo app, I think, and got that typical "stuck at 90%" and rebooted it like others did. It rebooted fine and Kingo verified it rooted.
I did not use Windows, I use Ubuntu, occasionally with Wine, yet I had no luck passing USB devices to it. (And always these missing libs...)
Normally, adb and fastboot (console) work fine (i.e. with my phone).
Now I have no chance to interfere with the bootloop, I think.
IIRC, sometimes I could spam commands and at one point adb was stuck at "waiting for device".
I tried to reproduce it just now, but could not get it again.
So, should I try adb or fastboot on another computer to be sure?
Would King(o) for Windows be of any help at this point? If so, what would be my best bet to catch it at some point I can recover it?
Is there any other way I could try? From my nooby perspective, could the bootsplash be an entrance for fastboot? Could it be just stuck trying to access erroneous partitions?
At this point I would try the most crazy and risky idea, since it is unusable anyway.
Thanks both of you for your answers.
l_aios said:
I could not remember, so I just retried it with two different chargers and two different cables (both used to power my Nexus 5).
Unfortunately resulting in the very same loop... But thanks nonetheless.
Dang... Usually I don't make mistakes this dumb. Guess I learned my first lesson. I'll try to trace my mistake though, for future attempts.
I rooted it with the Kingo app, I think, and got that typical "stuck at 90%" and rebooted it like others did. It rebooted fine and Kingo verified it rooted.
I did not use Windows, I use Ubuntu, occasionally with Wine, yet I had no luck passing USB devices to it. (And always these missing libs...)
Normally, adb and fastboot (console) work fine (i.e. with my phone).
Now I have no chance to interfere with the bootloop, I think.
IIRC, sometimes I could spam commands and at one point adb was stuck at "waiting for device".
I tried to reproduce it just now, but could not get it again.
So, should I try adb or fastboot on another computer to be sure?
Would King(o) for Windows be of any help at this point? If so, what would be my best bet to catch it at some point I can recover it?
Is there any other way I could try? From my nooby perspective, could the bootsplash be an entrance for fastboot? Could it be just stuck trying to access erroneous partitions?
At this point I would try the most crazy and risky idea, since it is unusable anyway.
Thanks both of you for your answers.
Click to expand...
Click to collapse
Do you still have root? Is your stick responding to the su command?
If so read this post: http://forum.xda-developers.com/fire-tv/help/guidance-recovering-bootloop-firetv-t3446902
If not:
Try kingoroot for windows however it is a slim change in my opinion as you wrote a FireTv image to your FireStick.
Copy and paste from: http://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
"IF YOU RUN INTO SOFTBRICK ISSUE (stuck at fire tv logo)
Make sure you have ADB drivers properly installed in your windows pc/laptop.
connect a genuine usb lead to the firestick/pc.
download the windows version of KINGO ROOT and install it.
open KINGO ROOT on the pc with Fire Stick connected up to pc and tv.
wait for the button to pop up and click root.
if you dont see AFTV or get enable debugging in the KINGO ROOT program on pc/laptop please unplug the stick from usb and replug it back in.
if this still wont work restart the pc/laptop or try another pc/laptop.
you should after clicking root boot back up into your homescreen, if it doesnt boot back into your homescreen automatically, wait around 5 minutes and unplug usb and re-plug it again. "
bula1ca said:
Do you still have root? Is your stick responding to the su command?
If so read this post: http://forum.xda-developers.com/fire-tv/help/guidance-recovering-bootloop-firetv-t3446902
If not:
Try kingoroot for windows however it is a slim change in my opinion as you wrote a FireTv image to your FireStick.
Copy and paste from: http://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
"[...]"
Click to expand...
Click to collapse
Thanks for the links, but from what I see, I need to get past the bootloader splash for adb to work. I'm stuck at the white "amazon" splash, not the colored "FireTV Stick" splash after the amazon one.
Sorry for not making it clear (and for that amount of text that maybe hid it)...
From what I understand and recall, I did only flash the recovery, right? Or does it automatically flash the zip I pushed to internal storage?
And what confuses me, the first attempt booting into recovery AFTER flashing the wrong one I got the former mentioned screen with red text. Reboot worked and the Stick was running. So I did retry and got the same red text after rebooting to recovery. I assumed it did not flash again and unplugged it earlier than the first attempt. Since then it got stuck at the white bootsplash.
Since I am still a noob, it seems to me the system wasn't touched, maybe a faulty recovery integrity forcing the bootloader to loop.
l_aios said:
Thanks for the links, but from what I see, I need to get past the bootloader splash for adb to work. I'm stuck at the white "amazon" splash, not the colored "FireTV Stick" splash after the amazon one.
Sorry for not making it clear (and for that amount of text that maybe hid it)...
From what I understand and recall, I did only flash the recovery, right? Or does it automatically flash the zip I pushed to internal storage?
And what confuses me, the first attempt booting into recovery AFTER flashing the wrong one I got the former mentioned screen with red text. Reboot worked and the Stick was running. So I did retry and got the same red text after rebooting to recovery. I assumed it did not flash again and unplugged it earlier than the first attempt. Since then it got stuck at the white bootsplash.
Since I am still a noob, it seems to me the system wasn't touched, maybe a faulty recovery integrity forcing the bootloader to loop.
Click to expand...
Click to collapse
I have no idea what you did however it will not automatically flash your zip, problem is you installed TRWP that was not meant for Firestick and overwrote its booting sequence. You most probably would had recover from your first attempt by re-installing a new image but once you tried to install it again it most probably finished writing the whole thing and damaged booting sequence.
bula1ca said:
I have no idea what you did however it will not automatically flash your zip, problem is you installed TRWP that was not meant for Firestick and overwrote its booting sequence. You most probably would had recover from your first attempt by re-installing a new image but once you tried to install it again it most probably finished writing the whole thing and damaged booting sequence.
Click to expand...
Click to collapse
Yeah, sad thing I got the wrong device, should have taken my time even more...
I googled the screen I got to two times before getting stuck:
http://forum.xda-developers.com/showpost.php?p=65968901&postcount=60
First time I waited approx. 15 minutes before pulling the plug to reboot. Since I noticed no difference I tried again and got the same screen. But this time I pulled the plug earlier, <1 minute.
I'd like to add that my bootloader was locked. Can I damage the booting sequence by corrupting the recovery or was my mistake that major to be able to do that?
I googled some key combinations to get into recovery or to bypass it, but I don't know if I get the right keys.
With my remote control I don't think I have enough time to hold the keys. Additionally I have a USB keyboard (Cherry KC1000; if possible, which keys btw?) and may be able to connect it via powered Y OTG cable.
So if anyone got any further input or ideas for me to rescue my FTVS, I'd be glad to receive it.
Thanks to all.
Anyone else maybe an idea?
The thing is, I cannot believe it is unsavable.
To summarize the current state (please see full details above):
- stuck in bootloop, white amazon logo
- flashed wrong recovery, after first flash the system booted, after second flash it got stuck (characteristics above)
- never flashed anything other than recovery
Strange thing it booted in first place, but now it refuses. Also I got the screen I mentioned above and unplugged as described above.
Can I possibly bypass the recovery check and try to boot directly to system? Or maybe interrupt for fastboot access?
If connected to PC, can you see it thru 'lsusb'? Or 'dmesg | tail'?
Kramar111 said:
If connected to PC, can you see it thru 'lsusb'? Or 'dmesg | tail'?
Click to expand...
Click to collapse
I tried both
watch -n 0.5 'dmesg | tail'
and
watch -n 0.5 'lsusb'
but with no identification whatsoever.
I double-checked with my Nexus 5 on the same port with the same cable, it identified fine.
One last bump for ideas before putting it into the trash.
I recently rooted and installed a custom rom on my 2011 (gen1) kindle fire.
I followed directions (https://forum.xda-developers.com/kindle-fire/development/how-to-kindle-fire-1-update-6-3-3-t2814955) to root.
Then I installed twrp latest version (older version did not accept my rom) https://twrp.me/amazon/amazonkindlefire.html
Then I installed the Infriction speed rom https://forum.xda-developers.com/showthread.php?t=2580232
I installed some apps... about 134 MB left in app install partition.
In developer settings I enabled ART, thinking, maybe this will make it faster...
Then it rebooted.
It was then stuck at a screen (not the android logo w/ words "kindle fire", but the bubbles screen of the os).
I decided, maybe I can fix with my pc.
Unplugged it - it then immediately shut off (loss of power??).
Then tried to use kindle unbrick utility, the various commands.
Now it is out of battery, but when I plug into PC or wall, it's in a boot loop, where it shows about 3 sec of the boot logo (android robot and words) and shuts off, before doing that again.
It is now undetectable by Kindle Fire Utility (just says "waiting" while the kfire reboots over and over), fastboot probably cannot detect either... (?) (worked one time but it just shut off again... and now doesn't work??), and can't boot into recovery.
Help.:crying:
So I'm assuming the partition ran out of storage?? but then what happened...
So I had a little luck trying to reset: ht tp s:// it stillworks.com/fix-kindle-fire-boot-loop-30462 .h tml
Then I got to the OS booting screen.
EDIT:
well that worked once... I tried to do adb reboot recovery after it got to OS boot screen (bubbles).
adb tells me:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Then it just fell into boot loop again. ?
So then I plug in, try again, it's just the boot loop. I'm going to try again after 30 min, but maybe need to do something different.
Cause of boot loop found
So it turns out it was just out of battery... I let it charge, did the reset thing, then was able to reboot into recovery.
\^o^/