Develop Bugs

Weird Resurrection of Device?

Ok, so I HAVE to share how strange this is, there might be something to it. Ok here we go... I used the SR Tool while I was on 8.3 to root my kindle fire and it got stuck in a boot loop that I could not get past. I used the First Aid kit and used option 7 to restore to factory settings and it didn't seem to be effective. Now, I was in a pinch for time and had to get to work so I said "Screw it, ima call Amazon and ***** at them and just get a new tablet" and left my Kindle to sit and headed to work. I called Amazon while on my way to work and they took my device off my account and sent me a new one out. Now the weird thing... I just got home and was VERY surprised to find that my device was working again even though, when I left for work, it was in the stock recovery and stuck.
Now I need to add that, when I tried to clear user data through SR Tool, Fist Aid Kit, and Stock Recovery, that it would sit on clearing user data and freeze there( I let it sit for 1 hr before giving up).
Anyone have any clue in hell what happened?

I have had the same problem when using data wipe/factory reset in recovery, last time it happened I had to do a fastboot flash of stock 8.14 image and start again - nothing else would work - just kept re-booting till I powered it off and plugged it into my laptop and ran fastboot.
I would love to know what is causing this too - doesn't happen every time - but it does make me nervous.

[Q] Stock, rooted KF2 stuck on animated boot logo after battery ran out

Hi Everyone
As a new user here, thanks in advance for any help that you can give me.
I've got a KF2, running 10.4.1 (I think, or maybe 10.4.3) - it's rooted, but generally stock apart from that (no TWRP).
It was left with something playing and the battery ran down to nothing yesterday. Initially it would charge, sometimes with the red light on and sometimes not, but then it would start up and as soon as it got to the lock screen it would give a low battery noise and shut down.
After leaving it plugged in overnight it is now charged but it is getting stuck on the animated kindle fire boot logo.
If I plug it into my PC it is detected in windows and I can connect to it with ADB with no obvious errors on logcat. Easy options like clearing the dalvik cache don't fix anything (only AmazonPlatform and atlasframework get recreated in the dalvik cache before it sets into doing nothing).
Searching the forum here, there are lots of different avenues discussed for "stuck at boot logo" problems - I'd appreciate some pointers on the most sensible things to try.
Thanks

Try a system restore with kindle fire first aid.
Sent from my Amazon Kindle Fire HD using Tapatalk

Hello, it seems that you face the same issue as I met last week with KF2 that I got for free. The KF2 got a boot problem after a low bat event and nobody was able to get him back. I seems thats the same issue. While I wasn't able to establish adb i used fastboot with a homebuild factory cable. (Forget KFfirst aid) Take a look on this thread: http://forum.xda-developers.com/showthread.php?t=2698935 - After formating cash and userdata user let him charging for a while on the pc usb port. Next day he returned booting showing a untouched KF2 with factory setup. Rootet him and gave him a CM11. Grate tablet for free. Take care, after formating cash and user he doesn't came back imidiatly Let him for some hours in the fastboot screen blinking his green led on screen. Next day he came back booting. My suspicion is a sw bug regarding low battery events. After cash and userdata format he need to develop valid boot conditions regarding the battery or other stuff. Who knows... But after the procedure he came back without further flaws.
Send via Tapatalk - HW: Kindl HD 8.9 - SW: Android 4.4.2 KitKat < CM 11.0 HC mod.

Thanks for the assistance guys. Sorry for not coming back sooner - I couldn't get my password to work this morning!
I tried restoring to 10.2.3 using KF first aide - after sitting in fastboot for ages downloading the images it flashed ok and then went back to the empty battery screen after it restarted. It stayed like that for so long I thought it was still broken, but eventually it booted back into the kindle launcher.
As I was going from 10.4 back to 10.2.3 I wiped the cache and userdata. Used ADB to get as much data off it as I could first - could I have safely used any of the KF first aide backups on it first?
One weird bit - I've rooted using bin4ry/qemu and used KF First Aide to disable OTA and install google play, maps etc, and now location services don't seem to work any more. Maps, Chrome, Silk, BBC Weather - they all give the location icon in the notification bar but then can't get a location fix.

This is why I don't use Amazon os... Seems like small things like this happen because we either forget to put something on the device that is needed or the os just breaks something like this out of nowhere. In my opinion its easier to avoid these kinda problems altogether by flashing cm but that's just my take, if you want amazon os then keep it. That sounded grouchier than I intended.
Sent from my Amazon Kindle Fire HD using Tapatalk

Stunts513, yes, AOS stucks out of nothing and your gone. On that way a got a kindle for free that entered in a boot loop after a low bat event and even USB recovery doesn't worked worked out by failing and access. Only fastboot and a CM makes that tablet working for real
Send from HTC Sensation - Android 4.4.3 - CM11 - Kitkat

Unbrick a FireTV

So, I've been trying to fix my Netflix playback issue. I uninstalled Netflix before I started this process.
My FireTV was running 51.1.6.0 rooted, the boot loader was unlocked, I had the boot menu installed, etc.
From what I'd read, it looked like I may have installed a pre-rooted version some time back that had an issue with Netflix, that was corrected in the "updated" version of that release. I didn't have Netflix at the time, so I didn't know I had a problem. So, I loaded the 51.1.4.0 rooted+updated and 51.1.6.1-rooted onto my FIreTV /sdcard/ directory, ran the md5sum to make sure the files were transferred right, then loaded 51.1.4.0 via recovery. After it rebooted, things weren't quite right. I couldn't install the Netflix app (when I selected the icon, I think the screen flashed and it was back to the same screen). PlutoTV would load, but Mediaah complained. On the Apps section, it said something to the effect of "Your apps will show up here soon". I could still launch Kodi and it seemed to work fine.
Anyhow, I entered recovery mode via ADB and installed the 51.1.6.1. Now my FireTV is sitting at the animated FireTV screen. It no longer gives me the boot menu as it boots up.
What did I do wrong? Did I need to do some more steps while running 51.1.4.0 before loading 51.1.6.1? Did I need to install another version between 51.1.4.0 and 51.1.6.1?
So far, I've not been able to make any headway recovering. I can't connect to it via ADB to enter recovery mode. I don't have a USB PC keyboard to try the ALT-I-PrintScreen trick on boot. I've just ordered a USB A to USB A cable to try the fast boot recovery, but if loading 51.1.4.0 has broken by bootloader unlock, then that probably won't work either.

Installing 51.1.4.0 wipes out the boot menu. Since 51.1.6.1 requires the boot menu, you soft-bricked when you installed 51.1.6.1 without having a funcitoning boot menu.
The good news is it's a simple fix. You should be able to get into recovery using the ALT+i+PrintScreen if you can get a hold of a USB keyboard. The A-to-A USB cable will also get you back to working order if you prefer to go that route.
Just follow the instructions carefully here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
EDIT: I've added a warning to my ROM page, next to the 51.1.4.0 download, to help people avoid what you unknowingly did. If you used my ROM page, sorry the warning wasn't there earlier. Please feel free to PM or email me if you need any additional help recovering.

Thank you for the explanation. I thought it was something like that.
Is there any specific time during the boot process that I should be trying to hit ALT-i-Print Screen?

Taige said:
Thank you for the explanation. I thought it was something like that.
Is there any specific time during the boot process that I should be trying to hit ALT-i-Print Screen?
Click to expand...
Click to collapse
There isn't really any indicator. Just continue to press it repeatedly through the whole boot process. I don't mean hold it down the whole time, but rather, press, release, then repeat. If you can't get it to work, just follow the steps under the "Repair Recovery with Fastboot Mode" section of my guide. With that, there's no guess work, and you'll get into recovery immediately.

Got it with the USB keyboard!
But only after I read this link (http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/)...
Before reading that page, I assumed I just had to hit it at the right point in the boot process, like entering a computers BIOS or something. But that page explained what the system did when you hit ALT-i-PrintScreen, so I knew not to give up.
I have a USB A-to-A cable that will be here tomorrow that I don't need now, but it was cheap insurance.
Thanks again! Your web site is a very valuable resource! Not to take anything away from all the hard work of the guys who frequent these forums, but having everything curated in one place, with instructions for mere-mortals is great.

Rooted FTV2 - Wiped System, Bricked?

Hey guys,
So it's been a while since updated my rooted FTV2 but decided to updated it to the latest prerooted image found on XDA. It had some freezing issue and I wiped the system and rebooted (didn't know I shouldn't reboot after a wipe). Now the fire tv is stuck on the white amazon logo with the black background. I can't access TWRP.
Is it bricked? Is there anyway I can restore it (considering I had TWRP on it before)? I tried connecting it via a USB A-A and on my Mac, with the android file transfer application, it would show could not connect to device. I tried listing the devices through "fastboot devices" but nothing shows up.
Is there any hope? Thank you.

DVO99 said:
Hey guys,
So it's been a while since updated my rooted FTV2 but decided to updated it to the latest prerooted image found on XDA. It had some freezing issue and I wiped the system and rebooted (didn't know I shouldn't reboot after a wipe). Now the fire tv is stuck on the white amazon logo with the black background. I can't access TWRP.
Is it bricked? Is there anyway I can restore it (considering I had TWRP on it before)? I tried connecting it via a USB A-A and on my Mac, with the android file transfer application, it would show could not connect to device. I tried listing the devices through "fastboot devices" but nothing shows up.
Is there any hope? Thank you.
Click to expand...
Click to collapse
It has been discovered that It is almost impossible to completely brick these devices by software only.
There is always a way to revive these devices and methods to recover them are becoming easier.
So don't throw them away and keep an eye on the other thread, there is hope.
.:HWMOD:.

hwmod said:
It has been discovered that It is almost impossible to completely brick these devices by software only.
There is always a way to revive these devices and methods to recover them are becoming easier.
So don't throw them away and keep an eye on the other thread, there is hope.
.:HWMOD:.
Click to expand...
Click to collapse
Thank you for the reply. I will definitely not throw them away. It was my fault that I didn't re-read all the warnings (lesson learned). Hopefully something comes up for it soon.

DVO99 said:
Thank you for the reply. I will definitely not throw them away. It was my fault that I didn't re-read all the warnings (lesson learned). Hopefully something comes up for it soon.
Click to expand...
Click to collapse
I did the same thing last night, not paying attention. I have two FTV2 though, managed not to mess up the other one. Here's hoping one day we can bring them back to life. :highfive:

Seriiez said:
I did the same thing last night, not paying attention. I have two FTV2 though, managed not to mess up the other one. Here's hoping one day we can bring them back to life. :highfive:
Click to expand...
Click to collapse
Haha, yeah it sucks. The worst part is in Canada there is only fire tv sticks, so I'm kinda stuck unless I get another android tv box.

Me too,
i tried to install Gapps, but with no success, the AFTV gen2 was rooted and working nice.
To eliminate the leftovers i tried to restore a /System and /Data backup with TWRP, but the system was wiped and the partitions was not maked again.
now i have a brick, with no fastboot and only amazon black&white logo
Any Ideas?

FireTV box 2nd gen in endless boot - Amazon logo then "no signal"

Hello
I have a Fire TV box 2nd gen (not stick).
Yesterday the hdmi signal suddenly showed white noise for 2-3 seconds. Then the menu again. (Then I think it froze, not sure...) I remeber I turned it off, took it from power and tried to boot again. But it did not.
It shows the white amazon logo for a moment, then "no signal" on any TV or HDMI I try.
The white LED is pulsing slowly.
I tried << and UP to change resolution, nothing.
Customer service thinks there is a HDMI-HDCP Problem(?) and white LED means it tries to boot.
Question:
Is there any way to re-set the whole thing, make a clear fresh installation via USB?
Or is this thing a brick now?
(I did many things, turned it off for hours, let it try to boot for 1 hour. Changed HDMI cables and HDMI slots and changed from TV to a beamer ..it just always does the same. I have no idea if the remote really reacts on << [UP] cause there is no light indicator)
What I did not do: Connect via USB to a computer (cant find a old standard USB cable at the moment)
Thanks
Bodo

bodomalo said:
Is there any way to re-set the whole thing, make a clear fresh installation via USB?
Click to expand...
Click to collapse
Take a look into this thread... Maybe you find in this 'unbrick thread' an answer

Sus_i said:
Take a look into this thread... Maybe you find in this 'unbrick thread' an answer
Click to expand...
Click to collapse
I guess that means no....
That thread is too long to read everything, the solution is first from 2016, and the last message 22 pages later from June 2019

bodomalo said:
I guess that means no....
That thread is too long to read everything, the solution is first from 2016, and the last message 22 pages later from June 2019
Click to expand...
Click to collapse
I guess that nobody reads the thread for you
From what I've read, a pulsing light and stuck at amazon logo/black screen is a brick, maybe a hardware failure.
You can place your question in detail in the suggested thread, maybe you get there an answer. Or sell the item on ebay

The exact same thing just happened to me this morning. Worked perfect last night.... then turn it on this morning and nothing... after power cycling just the white Amazon logo then goes black then slow pulsing light. Tried to reset via the remote with the back & forward and held until orange light then it just went back to doing the same thing.
Dominic

I just ran into this issue myself. My 2nd Gen is running a rooted rom and has worked fine for a couple years but tonight we were watching some Hulu and the screen went blank in the middle of a show. I did a power cycle and it boots to the TWRP boot screen, then I get the white amazon logo. After which, the TV loses signal. The device seems to boot for a short while before getting the pulsing white LED.
I can still go into TWRP and access everything so I've performed a full reset which changed nothing. I also downloaded and installed an updated ROM July 4, 2020 - 5.2.7.3_r1 but it responds exactly the same after the update.
Fortunately I have a spare Fire TV 2 (thanks ebay) so I was able to swap things over pretty quick. This also confirmed the power adapter was not the issue as the replacement seems to be working fine with the same adapter. I also tested the original one with a 15.5v, 3.4amp adapter and no change. I feel like maybe the video processor may have burned up at this point.
Still open to any suggestions though.

Hannover2k said:
I just ran into this issue myself. My 2nd Gen is running a rooted rom and has worked fine for a couple years but tonight we were watching some Hulu and the screen went blank in the middle of a show. I did a power cycle and it boots to the TWRP boot screen, then I get the white amazon logo. After which, the TV loses signal. The device seems to boot for a short while before getting the pulsing white LED.
I can still go into TWRP and access everything so I've performed a full reset which changed nothing. I also downloaded and installed an updated ROM July 4, 2020 - 5.2.7.3_r1 but it responds exactly the same after the update.
Fortunately I have a spare Fire TV 2 (thanks ebay) so I was able to swap things over pretty quick. This also confirmed the power adapter was not the issue as the replacement seems to be working fine with the same adapter. I also tested the original one with a 15.5v, 3.4amp adapter and no change. I feel like maybe the video processor may have burned up at this point.
Still open to any suggestions though.
Click to expand...
Click to collapse
Idk if it helps, but I would try a format data in wipe section of TWRP.
Could be that the eMMC died, i.e. at an unknown point, the storage switches to readonly, especially if the eMMC is a samsung chip.
Booting TWRP still works, in that case.
This happend to @Rortiz2 fireTV2 development box, maybe ask him for details.
What kind of errors are in the recovery log?

Sus_i said:
Idk if it helps, but I would try a format data in wipe section of TWRP.
Could be that the eMMC died, i.e. at an unknown point, the storage switches to readonly, especially if the eMMC is a samsung chip.
Booting TWRP still works, in that case.
This happend to @Rortiz2 fireTV2 development box, maybe ask him for details.
What kind of errors are in the recovery log?
Click to expand...
Click to collapse
I don't know how to get to the logs but happy to post if you can tell me.
On another note, I noticed the replacement device, while just recently connected and has also been rooted, tried to download the 5.2.7.4 update today. Typically my rooted devices never updated so this is a new discovery. I pulled the plug on it before it finished downloading but I'm worried I'll loose root if it updates. There's no pre-rooted ROM for 5.2.7.4 yet so I'm afraid to plug the power back in for fear it will update and unroot/brick like the 1st one.

Hannover2k said:
I don't know how to get to the logs but happy to post if you can tell me. .
Click to expand...
Click to collapse
Boot into TWRP, click mount and mount system, start the filemanager (in advanced tab), then go to /tmp, in there should be a recovery.log file, copy this file to your ext. sd or adb pull it to your PC.
Edit your serials in the file and upload it on mega, gdrive or so.
Hannover2k said:
On another note, I noticed the replacement device, while just recently connected and has also been rooted, tried to download the 5.2.7.4 update today. Typically my rooted devices never updated so this is a new discovery. I pulled the plug on it before it finished downloading but I'm worried I'll loose root if it updates. There's no pre-rooted ROM for 5.2.7.4 yet so I'm afraid to plug the power back in for fear it will update and unroot/brick like the 1st one.
Click to expand...
Click to collapse
For the sloane (aka fireTV second gen box), the prerooted rom installer disables the stock recovery, so nothing should happen if you let the ota updater do its thing...
But its best to disable the ota process with that:
Code:
adb shell
su
pm disable com.amazon.device.software.ota
pm disable com.amazon.device.software.ota.override
pm disable com.amazon.tv.forcedotaupdater.v2
pm clear com.amazon.device.software.ota
exit
exit