Well I have fooled around with this Kindle Fire for awhile and seem to be at a road block.
It is my wife's who stated she left it alone for a week or two, came back to turn it on and it locks up at the stock KF logo screen.
From what I have gathered that means the OS is toast.
Tried to get the KFU tool to work untill I found out that it needs to be forced into 'fastboot' to receive commands. So I built a debug cable and forced it. I then ran KFU to install twrp, said it installed and was rebooting. I had to force reboot the KF and then ran a KFU perm root script, rebooted.
Now I get to the white/blue kf logo and boot options for twrp, yet when it boots it hangs on the Teamwin logo screen.
Is this a boot loader malfunction that will require the shorting method to force USB rom loading? Or am I just missing something like a regular noob?
Thanks
TheInstinctz said:
Well I have fooled around with this Kindle Fire for awhile and seem to be at a road block.
It is my wife's who stated she left it alone for a week or two, came back to turn it on and it locks up at the stock KF logo screen.
From what I have gathered that means the OS is toast.
Tried to get the KFU tool to work untill I found out that it needs to be forced into 'fastboot' to receive commands. So I built a debug cable and forced it. I then ran KFU to install twrp, said it installed and was rebooting. I had to force reboot the KF and then ran a KFU perm root script, rebooted.
Now I get to the white/blue kf logo and boot options for twrp, yet when it boots it hangs on the Teamwin logo screen.
Is this a boot loader malfunction that will require the shorting method to force USB rom loading? Or am I just missing something like a regular noob?
Thanks
Click to expand...
Click to collapse
First off, have you considered installing TWRP manually? You may want to check the md5 of the recovery.img before installing though.
Hi there,
All was going well with my Fire HD 8.9, I rooted it, had the 2nd bootloader installed and was trying to install CM 11 before I got an error message saying that the jem version was the one I needed. I couldn't get my computer to recognise the the Kindle whilst in TWRP, so thought that I'd have to restore from the backup I made (of the stock Kindle OS and settings) to be able to transfer the version of CM that I needed. The backup seemed to work, but it hasn't in fact.
I turn on the Kindle and it gets stuck at the very first image of the logo, with NO animation
I'm unable to get back into TWRP
I can turn the kindle on and off but that's it
I can't use any recovery programs because my PC doesn't recognise the Kindle
I uninstalled and reinstalled the adb drivers, but when I connect the Kindle, my PC plays the 'Device Connected' then 'Device disconnected' sounds in quick succession, making the installation of any drivers fail
It's as though there's a brief second or two when USB works on the Kindle in terms of my PC knowing something is there, but then the USB disconnect noise plays
I only got it a day ago (managed to mess it up very quickly somehow!), so I could always try returning it if needs be, but hopefully that won't be necessary. Any ideas? Thanks in advance
EDIT - I can get the device to come up with fastboot mode and then the computer recognises it as an Adb device, but don't know where to go from there.
I would try to fix it from recovery if possible, it is way easier than having to do the process over again. You do know how to get it back into recovery right? Hold down volume up right after you power it on, just keep holding it even after kindle logo turns blue until you see the twrp logo. If that doesn't work, I would use kindle fire first aid to restore it and start over, but if you can get it into recovery then you can simply push a ROM onto it via adb.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
I would try to fix it from recovery if possible, it is way easier than having to do the process over again. You do know how to get it back into recovery right? Hold down volume up right after you power it on, just keep holding it even after kindle logo turns blue until you see the twrp logo. If that doesn't work, I would use kindle fire first aid to restore it and start over, but if you can get it into recovery then you can simply push a ROM onto it via adb.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I actually managed to fix it in the end by using the fast boot command and then connecting the Kindle, then using the SR tool to erase user data and cache, before flashing the boot and recovery imgs (just saying in case anyone googles and this comes up and it might help).
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 was in the process of updating both my fireTV and fireTV stick and accidentally pushed the montoya recovery meant for the stick to the firetv and ran “sh /data/media/0/montoya_recovery_v1.zip”.
Now when my FireTV boots up it I get the white Amazon logo for a bit, it then flashes a couple of times and then it reboots and repeats this process. The bootloader is fully unlocked, but I am unable to get into fastboot to try and push the correct version of TWRP back to the unit. I have a USB A-A cable connected to my PC, I have the ADB drivers installed, and I see the Android device under computer manager briefly (disappears when the unit reboots), but I am unable to issue the “fastboot devices” successfully or issue the “fastboot flash recovery.img” command successfully (hangs on waiting for device). It then continues to go into a loop.
Any ideas as to why the device is not stopping at the white logo screen and not going into fastboot?
Thanks in advance!
Landonfoot
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^/