FireTV box 2nd gen in endless boot - Amazon logo then "no signal" - Fire TV Q&A, Help & Troubleshooting

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

Related

[Q] Kindle Fire keeps restarting to yellow triangle

Three days ago I went through the process of rooting my kindle fire using KFU. Being a noob, this took me many many hours. I got everything to work, GO Launcher, Google Play, Amazon App store. I even used the Voodoo OTA Rootkeeper to temporily un-root so that I can watch amazon streaming videos. I was feeling pretty good about my accomplishment.
Late last night, for no apparent reason, the Kindle Fire restarted itself and got stuck on the yellow triangle (is this FireFireFire?). I got nervous, freaked out a little. I plugged into my computer and tried to restart the Kindle after selecting 'Recovery (5001)'. No luck. I then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief. It booted up just fine. This was about 2 hours ago.
But, now, my Kindle randomly goes back to the yellow triangle and hangs there. I need to go through the same process above to fix things. This has happened at least four times already. It did not seem to happen while the Kindle was "connected" to my computer. It happens once I 'disconnect'.... usually after about 10 - 20 minutes. It has happened while using both GO Launcher EX and the Amazon Launcher. Any idea?
You've got the same issue I do - the kindle keeps trying to apply the new update, and it isn't working, dumping it into recovery mode. I haven't figured out an answer to getting the update successfully applied yet (will work on that tonight), but until that happens, you should be able to remove the update from the sdcard /kindleupdates, and through something like root explorer rename /etc/security/otacerts.zip to something like /etc/security/otacerts.bak (or better yet, move it to the sdcard). That will stop it from redownloading the update and auto-rebooting.
Look Here
Have you looked at this http://forum.xda-developers.com/showthread.php?t=1417234 thread. The video explains the most common fix, and he goes through it step by step.
Also, so you grow a thick skin for posting on this forum, check out this link http://forum.xda-developers.com/showthread.php?t=1633343.
Hope this helps
Thanks for listening.
Sincerely,
William
[Kindle Fire: gedeROM v1.2 {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
Ok. I just tested it, and had it also confirmed in another thread, but here is one way to get 6.3.1 on when the update fails to apply, putting you into the recovery, force to normal boot, kindle updates, back to recovery loop:
if you have a copy on your device, copy the update to the root of the sdcard volume or download it from amazon. Rename the file update.zip, then reboot into recovery.
Under install, install the update.zip. Once it is done, you'll have 6.3.1 applied. Now, you'll have to both reroot, and reinstall recovery, but since you just did it with KFU a few days ago, it should be pretty quick. Then go move/rename the otacerts.zip file to prevent the next unexpected update.
There might be another way that doesn't blow away recovery, but this worked for me.
Thanks so much for all of the help! It looks like everything is working again. I got 6.3.1 installed (not really sure how that happened but it did!). Also got re-rooted and reinstalled TWRP and did a backup. I renamed the otacerts.zip. There is also a cacerts.bks file in the /etc/security directory... what does that do?
Also... will I ever want/need the updates? I assume renaming the otacerts.zip stops the updates indefinitely. Will this ever be a problem?
Thanks again!
Moving the otacerts.zip prevents the kindle from automatically downloading updates. When a new update has been released, you can download it from amazon's site manually, or put back the cert file to enable the download. Since updates often break root, this method will help keep you rooted until it is known how to root the new versions. As for want/needing them, it'll depend on what changes, but as long as they are rootable, they should generally bring improvements for the device.
The. bks file is a keystore for the certificate authority certs. You shouldn't need to ever touch that file.
powers down
Ok, I've got the exact same issue but one glaring difference. That after using KFU to boot to normal, it within 10-20sec powers down. Starting the bootloop all over. Don't know what to do, please help.
Does it actually fully boot into the kindle os? I haven't heard of it trying to apply the update that fast after start up, but not saying that it won't do that.
If using twrp, you can mount the kindle over usb from twrp - mount, and then move the update file out of kindleupdates. That should stop the boot cycle if it is being caused by the update. Another thing to check would be to look at the twrp console and make sure it is complaining about the update failing and not something else.
When I try to mount it ask me to format the drive, is that safe? Won't I lose everything then? Also, it won't allow me to select just the sd, it only allows me to select system.
ms6146 said:
Ok, I've got the exact same issue but one glaring difference.
Click to expand...
Click to collapse
That sounds eerily familiar...Where have I seen that before?
That after using KFU to boot to normal, it within 10-20sec powers down. Starting the bootloop all over. Don't know what to do, please help.
Click to expand...
Click to collapse
Only kidding...Actually that problem isn't the same at all and is described in detail here: http://forum.xda-developers.com/showthread.php?p=25400963
ms6146 said:
When I try to mount it ask me to format the drive, is that safe? Won't I lose everything then? Also, it won't allow me to select just the sd, it only allows me to select system.
Click to expand...
Click to collapse
Formatting your sdcard will erase everything on it. Besides trying to mount your sdcard, what are you trying to accomplish?
Well I'm stuck in bootloop with the powering off problem. The kindle is not recognized on the computer. All I want is to get the kindle back working. I have tried the unbrick utility but I think that made it worse. Getting back to a regular firmware even if its the latest would be fine. However being the noob that I am, I need step by step instructions. Thanks in advance.
ms6146 said:
Well I'm stuck in bootloop with the powering off problem. The kindle is not recognized on the computer. All I want is to get the kindle back working. I have tried the unbrick utility but I think that made it worse. Getting back to a regular firmware even if its the latest would be fine. However being the noob that I am, I need step by step instructions. Thanks in advance.
Click to expand...
Click to collapse
Your problem can still be fixed, but considering the fact you can't get the computer to recognize your device, you only have a couple of options left:
You could acquire a factory cable which would directly power your device in order to replace the bootloader.
If you don't have the means to acquire a factory cable you need to mount your sdcard in order to transfer FFF1.4 for flashing in recovery. From what I understand in your earlier post, it would in your case, require formatting your sdcard
yellow triangle and restart, please help
Jarden said:
Three days ago I went through the process of rooting my kindle fire using KFU. Being a noob, this took me many many hours. I got everything to work, GO Launcher, Google Play, Amazon App store. I even used the Voodoo OTA Rootkeeper to temporily un-root so that I can watch amazon streaming videos. I was feeling pretty good about my accomplishment.
Late last night, for no apparent reason, the Kindle Fire restarted itself and got stuck on the yellow triangle (is this FireFireFire?). I got nervous, freaked out a little. I plugged into my computer and tried to restart the Kindle after selecting 'Recovery (5001)'. No luck. I then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief. It booted up just fine. This was about 2 hours ago.
But, now, my Kindle randomly goes back to the yellow triangle and hangs there. I need to go through the same process above to fix things. This has happened at least four times already. It did not seem to happen while the Kindle was "connected" to my computer. It happens once I 'disconnect'.... usually after about 10 - 20 minutes. It has happened while using both GO Launcher EX and the Amazon Launcher. Any idea?
Click to expand...
Click to collapse
Hello Jarde, I have the same problem but I am super noob, my kindle is restarting at the yellow triangle every 3 seconds, you said " then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief", what do you mean selecting 'Normal (4000)', how can I do this?, and finally how did you solve the problem, thanks a lot and sorry for my poor english.
notforever said:
Hello Jarde, I have the same problem but I am super noob, my kindle is restarting at the yellow triangle every 3 seconds, you said " then tried the same thing after selecting 'Normal (4000)'. I could hear the USB connect/disconnect many times and then I saw the "Kindle Fire" screen and let out a sigh of relief", what do you mean selecting 'Normal (4000)', how can I do this?, and finally how did you solve the problem, thanks a lot and sorry for my poor english.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=25400963
I had the same issue - shutdown after a few seconds after boot, then the KF boots back into yellow triangle error.
I was able to get out of this loop by booting into recovery and wiping the cache partition (and the Dalvik cache for good measure) to remove the downloaded update file. After wiping the caches, my KF rebooted normally without issue. I could then us Root Explorer to rename the /etc/security/otacerts.zip file to something else as suggested in an earlier post. I have not had a problem since.

Just got Factory Cable from SKORPN, now what? Lol

I believe im having the "5 second bootloop" problem, no idea why since my KF was never rooted, flashed, or modified in any way. I plugged the Micro B in the KF (KF was off) and then plugged the Type-A end into my PC, the KF turned on in like 10 seconds (maybe less) and it isn't doing the bootloop anymore which i guess is a good thing but its been like 10 minutes and it still just says kindle fire (with a green light on the bottom). What should I do from here for my specific situation? Any help would be great! Thanks in advance!
edit: just wanted to add that before when i would plug it in, it would keep rebooting and usually not even get to the slide to unlock screen, but sometimes it would and then instantly reboot again.
First off...what bootloader do you have installed?
How could I find out? I never modified it if that helps? So it should be stock everything.
also i downloaded KFU and installed the drivers, but it does not recognize my device, altho when i first plugged it in after installing the drivers it said kindle in Device Manager, since it didnt go anywhere i unplugged the kindle and turned it off, when i tried again it installed ADB, but still doesnt recognize it (it also prompted me to restart, which i did right before i posted this reply, and still not recognized, also still at the kindle fire screen with green light on)
Untraumatized said:
How could I find out? I never modified it if that helps? So it should be stock everything.
also i downloaded KFU and installed the drivers, but it does not recognize my device, altho when i first plugged it in after installing the drivers it said kindle in Device Manager, since it didnt go anywhere i unplugged the kindle and turned it off, when i tried again it installed ADB, but still doesnt recognize it (it also prompted me to restart, which i did right before i posted this reply, and still not recognized, also still at the kindle fire screen with green light on)
Click to expand...
Click to collapse
ok so i read that sometimes it just wont read that it worked... so i check device manager, it said android phone, went to KFU, still said unknown after 0+enter, then i tried 3, it said it worked and to press any key to reboot, i pressed a key but the kindle didnt reboot, is it supposed to? also i tried 4 then like i read to do and it says the download path is incorrect so whats wrong?
Untraumatized said:
ok so i read that sometimes it just wont read that it worked... so i check device manager, it said android phone, went to KFU, still said unknown after 0+enter, then i tried 3, it said it worked and to press any key to reboot, i pressed a key but the kindle didnt reboot, is it supposed to? also i tried 4 then like i read to do and it says the download path is incorrect so whats wrong?
Click to expand...
Click to collapse
sorry for triple posting i will fix it but i dont want to confuse you on the timing of these events lol... so i figured out that CWM may be broken right now??? anyways since twrp worked i insatlled FFF with worked and now its at a menu that is kindle fire but BLUE fire text and says press power button for boot menu, but when i do that it doesnt do anything, do i need to unplug it?
Untraumatized said:
sorry for triple posting i will fix it but i dont want to confuse you on the timing of these events lol... so i figured out that CWM may be broken right now??? anyways since twrp worked i insatlled FFF with worked and now its at a menu that is kindle fire but BLUE fire text and says press power button for boot menu, but when i do that it doesnt do anything, do i need to unplug it?
Click to expand...
Click to collapse
you still there buddy? lol, i unplugged it and ya that worked, so now im at TWRP, just because it seems like a good idea i am backing up the things that were already checkmarked when i clicked backup
but now im afraid to continue without help, what step am i at exactly now? lol
EDIT: stuck at the end of the backup, been stuck there a while, will probably try to turn it off in a few minutes or so... anybody have some advice?
How about a little more information about what it is you intend to accomplish with your device?
soupmagnet said:
How about a little more information about what it is you intend to accomplish with your device?
Click to expand...
Click to collapse
i just want it to work! my power went out one day while i was sleeping and it was charging, for some reason it was dead (had been at 100% so shouldnt have drained, but the power going out messed with it) and when i tried to charge it, it bootloops
right now i have TWRP installed and FFF installed, what should i do now? i have tried booting it up and it just gets to the slide to unlock screen and then resets back to the blue kindle fire screen
i also just tried to install permanent root with superuser and it seemed to be working then said rebooting and "please wait...." and it never did anything (except the kindle booted back to the blue kind fire screen)
Untraumatized said:
i just want it to work! my power went out one day while i was sleeping and it was charging, for some reason it was dead (had been at 100% so shouldnt have drained, but the power going out messed with it) and when i tried to charge it, it bootloops
right now i have TWRP installed and FFF installed, what should i do now? i have tried booting it up and it just gets to the slide to unlock screen and then resets back to the blue kindle fire screen
i also just tried to install permanent root with superuser and it seemed to be working then said rebooting and "please wait...." and it never did anything (except the kindle booted back to the blue kind fire screen)
Click to expand...
Click to collapse
ANY help would be appreciated... im sitting here screwing with it waiting for a reply....
Untraumatized said:
ANY help would be appreciated... im sitting here screwing with it waiting for a reply....
Click to expand...
Click to collapse
well i managed to fix it by just factory resetting it with no help AT ALL
Very likely the factory reset had nothing to do with it. Just simply having it plugged in via USB may have given it enough time to charge. Questions of this nature are best handled in q & a not in development.
Untraumatized said:
well i managed to fix it by just factory resetting it with no help AT ALL
Click to expand...
Click to collapse
I'm sorry for not sitting at my computer, waiting with baited breath for you to respond, so I can devote all of my attention to your problem. I hope you can forgive me.
I wasnt trying to be offensive lol I was just proud to figure it out with NO HELP AT ALL! But anyways I am pretty sure it wasnt the charge because it was at 56% before and after i did the factory reset, and after the factory reset i backed it up and it finished that time (last time i had to unplug the KF and hard reset it)... Also I tried resetting it a couple times before the factory reset and it always rebooted once it got to the slide to unlock screen. Anyways it works, I am probably going to give it to my mom because of the simplicity (she just needs email, and internet... lol) and I might try to get my hands on a Nexus 7
AND HOW DO I DELETE ALL THOSE REPOSTS? THE DELETE BUTTON ISNT WORKING FOR ME ^__^'
Untraumatized said:
I wasnt trying to be offensive lol I was just proud to figure it out with NO HELP AT ALL! But anyways I am pretty sure it wasnt the charge because it was at 56% before and after i did the factory reset, and after the factory reset i backed it up and it finished that time (last time i had to unplug the KF and hard reset it)... Also I tried resetting it a couple times before the factory reset and it always rebooted once it got to the slide to unlock screen. Anyways it works, I am probably going to give it to my mom because of the simplicity (she just needs email, and internet... lol) and I might try to get my hands on a Nexus 7
AND HOW DO I DELETE ALL THOSE REPOSTS? THE DELETE BUTTON ISNT WORKING FOR ME ^__^'
Click to expand...
Click to collapse
Correct me if im wrong but you can't delete posts....but this thread should not be in Android Dev section, it should be in Q and A... Not to be mean or anything I am going to report this thread so it can be moved to the right section (to help the mods out)
OP, First This Thread Is In The Wrong Place. And It Appears To Me Users Where Trying To Help, On Limited Information. But You Figure It Out On Your Own Great.
Thank You And Thread Closed.

(FIXED) Samsung Galaxy Tab S 8.4 will not fully boot up.

I've had my Samsung Galaxy Tab S 8.4 (SM-T705Y) for just over two years now and it has worked brilliantly beside the odd issue here and there, including the device freezing from time-to-time. Each time that particular freezing issue has happened, I've used the 'Power and Volume Down buttons' technique and it has successfully fixed the issue.
Now, a few days ago, I was using my tablet for normal morning things; music app playing in the background, YouTube opened on the side, using the preinstalled Browser and Google Chrome apps, etc. I am not sure if it was updating any Google or Samsung apps at the time. The screen froze up so I left it for a few minutes, seeing if it would unfreeze. When it didn't, I used the same Power and Volume Down technique, which successfully forced-restarted the tablet. There was a small mistake I made doing this; I was holding down both the Power button and Volume Up button. It took me around thirty seconds to realise why the screen wasn't turning off and switched to the Volume Down button. At the time, both my earphones and the charging cord were connected.
However, upon the loading screen, I noticed that it did not pass the Samsung logo screen with the little explosion of blue circles and just kept replaying the same animation repeatedly. The Application History and Back buttons did not light up and the device did not vibrate as it normally does when it boots up. I repeated the Power-Volume Down technique to see if that would fix the issue. Once again, the tablet rebooted normally but was stuck at the logo screen playing the animation. I tried this same force-restart again, this time without the charger plugged in. No change.
So, I left it running through the animation while doing Google searches through forums and getting into contact with Samsung as to what the issue could be. I'll list down below what my tablet can and can't do at the moment and hopefully someone will have a clue as to what is going on and how to fix it. I will point out now that it was not going through a firmware update at the time, the device is not rooted and nor do I plan on taking that path with it, and I have not made any changes to it that can void the warranty.
It can:
- Recharge (The battery icon will show up if it is force-restarted and the charger is plugged in at the time.)
- Reboot (It's not exactly stuck in a bootloop, more of just the 'explosion' animation replaying over-and-over.)
- Enter Recovery Mode
It cannot:
- Enter Safe Mode
- Be Shut Down without the charger attached (As stated above, the device will only turn off with the Power-Volume Down buttons held for about 30 seconds and that causes the device to restart, not turn off. The only way for it to completely shut down is to have the charger connected and then unplug it after the battery icon appears.)
I have tried removing the SD card and placing it back in, power-cycling it, letting it run on the animation until the battery runs out and then letting it recharge to 100% before turning it on again, connecting it to Samsung Smart Switch (which recognises that there is a Samsung device connected, but not being able to register the device itself), and wiping the Partition Cache (Also note; the Recovery Mode has the 'No Command' sign with the android laying down and the red triangle with the exclamation point above it. Clearing the Partition Cache seemed to go smoothly, however when I chose the 'reboot device now' option, the 'No Command' sign changed to 'Error!' and rebooted the device anyway.) I am now currently trying another technique written on a different website (though since I am a new user, I cannot post up URLs at the moment). So far, plugging in the earphones alone hasn't worked and the device is currently connected to my laptop - which is shut off - and still has the earphones connected, but the animation is the only thing the screen is still showing.
I have important files saved in the internal storage of my Tab S and I do not have them backed up, which is the only issue that's stopping me from just going ahead and doing a Factory Reset as I cannot lose these files.
I am unsure if my Tab S is soft-bricked or if this is another issue entirely and I just missed something that could have already fixed it.
Yes, this is a long and detailed post, but hopefully with these details, someone will be able to help with this issue. If I can restore my Tab S to its condition before the freeze, that would be amazing, but I can definitely settle with only being able to salvage my files from the internal storage and then performing a Factory Reset on it.
Thank you in advance~
It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.
edan1979 said:
It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.
Click to expand...
Click to collapse
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?
AussieMouse said:
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?
Click to expand...
Click to collapse
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)
edan1979 said:
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)
Click to expand...
Click to collapse
Alright, I'll try that and let you know how it goes. Is there any specific website I should download the firmware (4.4.2 KitKat) from? (Yeah, I agree with you there! Still, just to be on the safe side~)
KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.
edan1979 said:
KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.
Click to expand...
Click to collapse
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.
AussieMouse said:
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.
Click to expand...
Click to collapse
MM is ok. I dont have any problem with it.
edan1979 said:
MM is ok. I dont have any problem with it.
Click to expand...
Click to collapse
Thank you so much for your help! I managed to find the KitKat 4.4.2 firmware on SamMobile and flashing it restored everything~

(Solved) AFTV V1 another brick?

Hi all. I'm giving this one last chance before I toss it because one of my fire sticks seems to be giving up the ghost and the box was/is a superior device to use if I can get it freed up and working again.
I've had this on the shelf for some time. Here is where I sit
Fully Unlocked
Rbox boot installed
I can't for the life of me remember what version of OS/Rom/Recovery was on it?
I believe I have CWM 6.0.5.1.4a.
I believe the rom was a 51.1.6. x x x x?
I honestly don't remember if I had updated the boot menu and rom out of order or what but here is what I'm looking at now.
I power it on and once I get to Rbox boot selection I either
1. choose boot kernal where I get a white amazon logo which does fade away and get replaced by the colorful amazon logo. The LED pulses white
2. choose launch recovery where I get the white amazon logo and the LED glows orange/yellow
I have a USB A-A bridge cable which does nothing for me. I'm never able to list my fastboot device from within ADB. Maybe my USB cable is crap? It does have the installed electronics and software for moving files to and fro.
It has been a good 18 months since I tried breaking it open last and I think I'll ask if anyone has advice before I chuck it.
I should mention I have since married the remote to my other AFTV box. F.W.I.W.
Regards
Gonk
I'm getting somewhere. I've tried some A-A cables and this new one is getting me somewhere.
Following this link at FTVnews I am finally looking at CWM.
But my problem now is how to control CWM without my remote! Install putty via these directions. This allowed me to do data wiping/factory reset and wipe the cache partition.
Next is Resetting with Recovery Model per Rbox guide of the first link.
So now I have a baby OS and trying to get past the mandatory network setup so i can sideload and move on.
This is super great news I brought it back from extinction. I'll update this post with more specifics as I get through it, though all the information IS already available. It's still nice for folks to see it's possible to bring a box back after all hope appeared to be lost.

Fire TV solid orange light, won’t boot.

Tried to sideload the google play store. Fire tv crashed and seemed to go into a boot loop. When it plugs in, there is a solid orange light, after about 10 seconds it will flag white once (looks as if it’s rebooting) and then go back solid orange.
No amazon logo and no signal. I’ve tried leaving it plugged in for a day. Also tried unplugging it for a couple days. Any thoughts or help on this?
Sounds like it's bricked. Should be recoverable if you're willing to open it up.
i got a fire tv 2 with a similar issue from trying todo the "unbrick with short" method. my devices had already had that process done successfully but along the road i did a disco at a bad time and now whenever i do the unbrick via short method i get a fail because the script says theres a GPT partition or something.
I had this happen with a firestick 2nd gen(tank) but i eventually found a comment that led to altering the script to format the partitions back to MBR.
I HAVE NOT FOUND THE SAME FOR THE FIRETV 2.
idk
bogart1117 said:
i got a fire tv 2 with a similar issue from trying todo the "unbrick with short" method. my devices had already had that process done successfully but along the road i did a disco at a bad time and now whenever i do the unbrick via short method i get a fail because the script says theres a GPT partition or something.
I had this happen with a firestick 2nd gen(tank) but i eventually found a comment that led to altering the script to format the partitions back to MBR.
I HAVE NOT FOUND THE SAME FOR THE FIRETV 2.
idk
Click to expand...
Click to collapse
The amonet gpt-fix for the FireTV2 box isn't public (til of today), you may ask in the unbrick thread for it
Been awhile Sus
Sus_i said:
The amonet gpt-fix for the FireTV2 box isn't public (til of today), you may ask in the unbrick thread for it
Click to expand...
Click to collapse
You helped me before in the unbrick thread. i got it workimg and then did some stupid mistake on the software side and never recovered. I was just snooping and found this and love the irony of you popping up with the answer.
Well thanx for the heads-up. Let me know if you come across the new gpt/mbr script in case I haven't stumbled into it.
bogart1117 said:
You helped me before in the unbrick thread. i got it workimg and then did some stupid mistake on the software side and never recovered. I was just snooping and found this and love the irony of you popping up with the answer.
Well thanx for the heads-up. Let me know if you come across the new gpt/mbr script in case I haven't stumbled into it.
Click to expand...
Click to collapse
Yeah, I was a bit surprised to see your posting
This gpt issue should be solvable, just go ahead to the sloane unbrick thread and tell it Rortiz2... :good:
---------- Post added at 10:26 AM ---------- Previous post was at 10:25 AM ----------
JonDaniels said:
Tried to sideload the google play store. Fire tv crashed and seemed to go into a boot loop. When it plugs in, there is a solid orange light, after about 10 seconds it will flag white once (looks as if it’s rebooting) and then go back solid orange.
No amazon logo and no signal. I’ve tried leaving it plugged in for a day. Also tried unplugging it for a couple days. Any thoughts or help on this?
Click to expand...
Click to collapse
What kind of FireTV box is it? The first one or the second?

Categories

Resources