[Q] TWRP v2.5.0.0 hangs consistently - Kindle Fire Q&A, Help & Troubleshooting

My TWRP version is v2.5.0.0. I tried to follow a fallback procedure in thread
Kindle Fire Q&A, Help & Troubleshooting > Restore kindle fire after twrp2.0 to factory default without firefirefire
Click to expand...
Click to collapse
that other people succeeded with. Unfortunately, I can no longer boot into TWRP by holding down the power button (never goes orange anymore) or boot normally into Linux; regardless of mode, all I see is the yellow flame triangle with the "press power..." message down below.
I suspect that Justin's fallback recipe in that thread only works with certain versions of TWRP. I am not faulting anyone but myself. Being an experienced systems programmer and hardware assembler, I know that these things can happen.
Is there another way to recover from a looping TWRP that I may not be aware of? It seems that there is only one "override" button i.e. the power button.
I've taken hardware apart and assembled systems before many times so I'll not be shy about doing so with this tablet. I found very good how-tos on-line as a guide and I have good tools.
So, can anyone point me to any of the following?
1. Motherboard internal specifications with pictures (like you get when you buy a motherboard at Newegg or Amazon)
2. Hardware reset jumpers if there are any
3. Preferred methods for reloading storage
4. Other suggestions?
Thank you. Peace.
Richard

Reinstall twrp and install the new firefirefire
You could use kindle fire utility 0.9.9
Sent from my Amazon Kindle Fire using xda app-developers app

Related

Friend's KF - Unsure of what he's done to it...

Hello All,
A friend of mine has possibly bricked his KF - but I'm not entirely sure, as he can't adequately describe to me what he did to it (or point me to th instructions he was following). I'm trying to get it running for him again, but honestly, while I have a rooted KF running hashcode's kernal, I simply followed instructions correctly (ie: I don't have actual knowledge of the inner workings).
Here's the deal with his KF:
- Powers on, and sticks at the "kindle fire" screen ("kindle" in white, "fire" in orange)
- I can see the KF when I use the devices command from adb
I'm running the current release of ubuntu - so KFU is not an option. Please advise if you have thoughts on how I can begin to resolve this issue. And I do apologize if this has been covered, as I'm sure it has, but most posts involving restoring fuctionality seem to be using KFU/windows.
Sent you a pm I can help
Thepooch said:
Sent you a pm I can help
Click to expand...
Click to collapse
Thanks for helping buddy - I'll let you know when dude gets the factory cable.
celticGreen said:
Hello All,
A friend of mine has possibly bricked his KF - but I'm not entirely sure, as he can't adequately describe to me what he did to it (or point me to th instructions he was following). I'm trying to get it running for him again, but honestly, while I have a rooted KF running hashcode's kernal, I simply followed instructions correctly (ie: I don't have actual knowledge of the inner workings).
Here's the deal with his KF:
- Powers on, and sticks at the "kindle fire" screen ("kindle" in white, "fire" in orange)
- I can see the KF when I use the devices command from adb
I'm running the current release of ubuntu - so KFU is not an option. Please advise if you have thoughts on how I can begin to resolve this issue. And I do apologize if this has been covered, as I'm sure it has, but most posts involving restoring fuctionality seem to be using KFU/windows.
Click to expand...
Click to collapse
My girlfriends KF has done this several times. Have you tried a reset? If not, hold the power button down for 20 seconds, then wait about a minute. If the KF does not boot up automatically then turn it on yourself. hopefully after the reset it will boot up correctly. If not, maybe you will have to wait for the factory cable.
Built a factory cable, and sure enough TWRP booted up just fine. Going to revert this thing to stock and be done with it...

Is my Kindle Fire 2 gone forever?

I saw a couple similar threads recently, but my situation is a little different.
My KF2 is totally dead and nothing happens when I plug in a fastboot cable or try and charge it with a wall charger. Prior to this, I was getting the lovely orange Kindle Fire bootloop (which is why I bought the fastboot cable). If it helps, the last time it was running properly I was running 10.2.6, it was rooted and had TWRP and the Google Play store on it. I just got greedy and wanted JB and like a dope wiped everything in TWRP.
Am I totally SOL or is there something I can actually do with this potential brick?
Thanks in advance!
jjdavola said:
I saw a couple similar threads recently, but my situation is a little different.
My KF2 is totally dead and nothing happens when I plug in a fastboot cable or try and charge it with a wall charger. Prior to this, I was getting the lovely orange Kindle Fire bootloop (which is why I bought the fastboot cable). If it helps, the last time it was running properly I was running 10.2.6, it was rooted and had TWRP and the Google Play store on it. I just got greedy and wanted JB and like a dope wiped everything in TWRP.
Am I totally SOL or is there something I can actually do with this potential brick?
Thanks in advance!
Click to expand...
Click to collapse
Did you wipe everything and reboot or did you try to install JB first? What method did you use to install TWRP?
Sent from my Amazon Kindle Fire using Tapatalk 2
soupmagnet said:
Did you wipe everything and reboot or did you try to install JB first? What method did you use to install TWRP?
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply! I wiped and rebooted because I couldn't access the files I installed. I installed TWRP with the TweezerMod.apk.
jjdavola said:
Thanks for the reply! I wiped and rebooted because I couldn't access the files I installed. I installed TWRP with the TweezerMod.apk.
Click to expand...
Click to collapse
The point of Hashcode's stack override is to make it possible to install unsigned boot and recovery images for the purposes of modifying their devices, without the device's security measures having any effect. Since the stack override is installed to a certain location on the system partition, custom ROMs are made to include this necessary information. If you completely wipe the system partition without installing a ROM or replacing the stack override, there is no longer any protection from the device checking to see if those partitions have the necessary signed headers, so you may just be out of luck. Though I have seen situations, especially on my own device, where that wasn't even an issue, so who knows? The Kindle Fire 2 may be different in that regard.
Maybe, someone with a little more knowledge on the subject can shed some light on the situation.
soupmagnet said:
The point of Hashcode's stack override is to make it possible to install unsigned boot and recovery images for the purposes of modifying their devices, without the device's security measures having any effect. Since the stack override is installed to a certain location on the system partition, custom ROMs are made to include this necessary information. If you completely wipe the system partition without installing a ROM or replacing the stack override, there is no longer any protection from the device checking to see if those partitions have the necessary signed headers, so you may just be out of luck. Though I have seen situations, especially on my own device, where that wasn't even an issue, so who knows? The Kindle Fire 2 may be different in that regard.
Maybe, someone with a little more knowledge on the subject can shed some light on the situation.
Click to expand...
Click to collapse
Thanks. I'm still holding out some hope, but I tried to charge it all night with a wall charger and it did nothing.
Since there's no replies, I'm guessing I'm really SOL. Anyone want to buy a brick?
Anyone???
There is a possibility that you have drained the battery and now its dead. After doing all you did to it and rebooted did it display the logo at all and then after some time just cease to power on? If so you could order a replacement battery. If not I'm inclined to agree with Soupmagnet that its looking for a boot id and not finding therefore failing to boot at all.
Thepooch said:
There is a possibility that you have drained the battery and now its dead. After doing all you did to it and rebooted did it display the logo at all and then after some time just cease to power on? If so you could order a replacement battery. If not I'm inclined to agree with Soupmagnet that its looking for a boot id and not finding therefore failing to boot at all.
Click to expand...
Click to collapse
Thanks for the reply. The strange thing is once I got the fastboot cable the green light on the KF2 was on, so I thought I had time. Then after trying to restore everything for a few minutes, the KF2 just died and never came back to life. Although I did connect the regular USB in that short time to see what would happen and it just bootlooping.

Anyone know how to fix a bricked FTV

Hi guys,
I have a problem with my firetv where it won't boot past the Amazon logo. This happened after restarting the system when I installed firetv Boot Menu.
Any help would be welcomed
Sorry I'm not likely to have a fix, but are you sure you unlocked boot loader before attempting to install the boot menu? This could be the cause for the brick.
Are you able to boot to recovery? If so you might be ok. I VERY TENTATIVELY say that if you can get into recovery from there either a factory reset or reflashing a prerooted fw might help BUT if you're able to get there PLEASE don't proceed till someone with more experience chimes in!
I will say that there's hope if you can get to recovery... probably? But this never happened to me.
Have you tried restarting with usb keyboard attached and pressing the print alt screen? Good luck.
Phill360 said:
Hi guys,
I have a problem with my firetv where it won't boot past the Amazon logo. This happened after restarting the system when I installed firetv Boot Menu.
Any help would be welcomed
Click to expand...
Click to collapse
hi,
I am not an expert on this matter but you should provide detail info exactly what you did to your Fire TV, the exact steps and sequence so folks can help you better.
In the meantime, check these all link out before you do anything. It seems few folks has some success see link 2 and 3 as always try it on your risk. I hope someone else can provide a better solution.
http://www.aftvnews.com/top-ways-to-brick-your-fire-tv/
http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
http://forum.xda-developers.com/showthread.php?t=2799779
http://www.aftvnews.com/factory-reset-on-amazon-fire-tv-and-fire-tv-stick-explained/
btw, if you are using amazon fire tv for xbmc as it seems most folks are using it for, i would just get Raspberry PI, it is awesome never had to worry about bricking the damn thing, sure it slower than fire tv but i have use it and i love it, it plays 1080 and 3d movies and no buffering either.
I also fire tv but i am always scared this thing will brick as it seems many folks have this problem.
Thank you
KLit75 said:
Sorry I'm not likely to have a fix, but are you sure you unlocked boot loader before attempting to install the boot menu? This could be the cause for the brick.
Are you able to boot to recovery? If so you might be ok. I VERY TENTATIVELY say that if you can get into recovery from there either a factory reset or reflashing a prerooted fw might help BUT if you're able to get there PLEASE don't proceed till someone with more experience chimes in!
I will say that there's hope if you can get to recovery... probably? But this never happened to me.
Have you tried restarting with usb keyboard attached and pressing the print alt screen? Good luck.
Click to expand...
Click to collapse
Thanks for the reply Klite, I didn't unlock the bootloader before installing the menu so that must have caused the brick.
I'm only able to see the Amazon logo, it does not reach the Fire TV Logo. I have plugged in a USB keyboard but i can't seem to get to recovery.
ashsha7877 said:
hi,
btw, if you are using amazon fire tv for xbmc as it seems most folks are using it for, i would just get Raspberry PI, it is awesome never had to worry about bricking the damn thing, sure it slower than fire tv but i have use it and i love it, it plays 1080 and 3d movies and no buffering either.
I also fire tv but i am always scared this thing will brick as it seems many folks have this problem.
Thank you
Click to expand...
Click to collapse
Hi Ashsha
I do mainly use my FTV for Kodi, I did previously use a Raspberry Pi but i bought this to replace it as i wanted something more powerful due to the problems i was having with stutters during play back.
Thanks for the links too, i did try them but i have had no luck so far.
Does anyone know if it possible to unbrick my FTV via USB using Fastboot or ADB?
Phill360 said:
Hi guys,
I have a problem with my firetv where it won't boot past the Amazon logo. This happened after restarting the system when I installed firetv Boot Menu.
Any help would be welcomed
Click to expand...
Click to collapse
Phill360 said:
Does anyone know if it possible to unbrick my FTV via USB using Fastboot or ADB?
Click to expand...
Click to collapse
That's a very good question. I know it's pretty much essential to unbrick a kindle fire but can't find any info specific to aftv. But you're motivation to get an answer is greater than mine. Do you have one?
I'd be confident in trying it with a phone or tablet but I just don't know enough about the variables (like could you do more damage sending power to somewhere that has an external power source)
My best advice is to be patient, keep looking for possible fixes online, but I'd caution not to experiment. Instead keep coming back here to get thoughts on possible fixes that might work. At the very least your thread will stay high in the forum search results giving you a better chance of having the right xda member to notice it.
KLit75 said:
That's a very good question. I know it's pretty much essential to unbrick a kindle fire but can't find any info specific to aftv. But you're motivation to get an answer is greater than mine. Do you have one?
I'd be confident in trying it with a phone or tablet but I just don't know enough about the variables (like could you do more damage sending power to somewhere that has an external power source)
My best advice is to be patient, keep looking for possible fixes online, but I'd caution not to experiment. Instead keep coming back here to get thoughts on possible fixes that might work. At the very least your thread will stay high in the forum search results giving you a better chance of having the right xda member to notice it.
Click to expand...
Click to collapse
If you didn't follow the directions and didn't unlock, then it is bricked and the only way to fix it is the hw mod to write to the mmc. If you have an A to A plugged in, on boot it'll stop in the bootloader and fastboot will work, unfortunately there is no commands you can actually run that will do anything. If you don't have an A to A plugged in, it will try to load the boot image. Since you didn't unlock, it won't boot the image, and it'll just die.
if all else fails, you can always go to amazon for replacement, remember amazon fire tv hasn't been a year old yet and you still have warranty for it, thats what i did with mine, i acted i didn't know what i was doing and suddenly it wouldn't load or boot up, etc.. u will need to know ur email adress or account thats associated with ur fire tv.. op korz .. they will do it... 100%
rbox said:
If you didn't follow the directions and didn't unlock, then it is bricked and the only way to fix it is the hw mod to write to the mmc. If you have an A to A plugged in, on boot it'll stop in the bootloader and fastboot will work, unfortunately there is no commands you can actually run that will do anything. If you don't have an A to A plugged in, it will try to load the boot image. Since you didn't unlock, it won't boot the image, and it'll just die.
Click to expand...
Click to collapse
Thanks for the reply rbox.
So what your saying is my Fire TV is dead.
I might just move on then to a new device like the Razor Forge TV when that comes out.
daffung said:
if all else fails, you can always go to amazon for replacement, remember amazon fire tv hasn't been a year old yet and you still have warranty for it, thats what i did with mine, i acted i didn't know what i was doing and suddenly it wouldn't load or boot up, etc.. u will need to know ur email adress or account thats associated with ur fire tv.. op korz .. they will do it... 100%
Click to expand...
Click to collapse
I'd love to return my FTV under warranty but i live in Australia and can't be bothered paying for postage to get it replaced
Just wondering if anyone has worked out a way of fixing this type of Brick?
Not sure was version of the software on, I'm hoping that it might be on 51.1.6.1 or 54.1.2.1
thanks
Phill360 said:
Just wondering if anyone has worked out a way of fixing this type of Brick?
Not sure was version of the software on, I'm hoping that it might be on 51.1.6.1 or 54.1.2.1
thanks
Click to expand...
Click to collapse
Depending on how much of the instructions you actually followed, and if your bootloader is 51.1.0.2 or older, there is a method that @AFTVnews.com is working on a writeup for that should recover it. But if the bootloader wasn't downgraded to 51.1.0.2, then it's dead.

Hard Brick (?) KF2 2012

So, I have come into possession of a 2012 Kindle Fire 2 with an interesting story. My friend, the original owner (and as you shall find out, a complete n00b) decided to flash some ROMs and fool around with KFU (yes, the one that's NOT meant for KF2). And while panicking, he ended up booting in fastboot and erasing almost everything he saw here:
https://forum.xda-developers.com/showpost.php?p=23747804
So as a result, I have on my hands a Kindle Fire 2 with no bootloader, no recovery, no system, no cache. At this point of time, I'm trying to figure out whether there is any hope for the device if I use the shorting method and try and bring it to OMAP USBBOOT.
Suggestions are highly welcome.
MisterShakey said:
So, I have come into possession of a 2012 Kindle Fire 2 with an interesting story. My friend, the original owner (and as you shall find out, a complete n00b) decided to flash some ROMs and fool around with KFU (yes, the one that's NOT meant for KF2). And while panicking, he ended up booting in fastboot and erasing almost everything he saw here:
https://forum.xda-developers.com/showpost.php?p=23747804
So as a result, I have on my hands a Kindle Fire 2 with no bootloader, no recovery, no system, no cache. At this point of time, I'm trying to figure out whether there is any hope for the device if I use the shorting method and try and bring it to OMAP USBBOOT.
Suggestions are highly welcome.
Click to expand...
Click to collapse
Try this thread: https://forum.xda-developers.com/showthread.php?t=2011126 Power off Kindle if able. Open the tool and select option 1 to enable fastboot. A question will come up asking if your tablet is powered off or on. Select the appropriate option. If there is any hope left, this would be it. Once in fast boot, select option 2 I believe which is install SuperSU and recover image. Follow all steps in that thread. If files don't download, do a Google search for the exact names. I used this tool many of times so I know it works if you aren't perma bricked.

Testpoint / force reset

Hi
My fire stick stuck at start at the amazon logo. Nothing helps.
Before throwing it away I was thinking of opening it up if there was a way to i don't know short circuit something to force it to boot into recovery or if there was any way to recover it from the grave.
Thanks for the suggestions in advance.
It is the model LY73PR
gabor.czinege said:
Hi
My fire stick stuck at start at the amazon logo. Nothing helps.
Before throwing it away I was thinking of opening it up if there was a way to i don't know short circuit something to force it to boot into recovery or if there was any way to recover it from the grave.
Thanks for the suggestions in advance.
It is the model LY73PR
Click to expand...
Click to collapse
Unbrick:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 2nd gen (tank)
Read this whole guide before starting. This is for the 2nd gen Fire TV Stick (tank) Current relase: amonet-tank-v1.2.2.zip NOTE: Recent reports indicate a change that disables brom DL-mode The change seems to have been introduced with devices...
forum.xda-developers.com
Sus_i said:
Unbrick:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 2nd gen (tank)
Read this whole guide before starting. This is for the 2nd gen Fire TV Stick (tank) Current relase: amonet-tank-v1.2.2.zip NOTE: Recent reports indicate a change that disables brom DL-mode The change seems to have been introduced with devices...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks that's what i was looking for. Though the process runs through until point 5. Wait for the script to finish.
But the device still stuck at amazon logo unfortunately. Trash it is?
gabor.czinege said:
Thanks that's what i was looking for. Though the process runs through until point 5. Wait for the script to finish.
But the device still stuck at amazon logo unfortunately. Trash it is?
Click to expand...
Click to collapse
I thought since I'm at the point where it accepts stuff like handshake2.py stuff can't i somehow reset it to factory defaults via command line? Clear cache? Force it to load to recovery? (though i don't have a powered otg yet but I'd get one if I'd get to recovery)
gabor.czinege said:
I thought since I'm at the point where it accepts stuff like handshake2.py stuff can't i somehow reset it to factory defaults via command line? Clear cache? Force it to load to recovery? (though i don't have a powered otg yet but I'd get one if I'd get to recovery)
Click to expand...
Click to collapse
There is only one unbrick solution, see the link above.
Take a look at which step the script stalls and/or if you get an error message, search for it in the thread.

Categories

Resources