Have I bricked my fire tv? - Fire TV Q&A, Help & Troubleshooting

Hi there. My fire TV is rooted and has the following installed:
clockwork mod custom recovery
51.1.4.0_514006420 updated 10/30/2014 Custom rom
I was initially experiencing strange behaviour with my external hard drive converting to a read only drive after a while for no apparent reason so decided to do a factory restore
I tried to factory restore the device but for some reason after the factory restore and watching the funny cartoon on set up the device said I only had 2.5gb of hard drive space left of the 5.5 gb available so I decided to try formatting the data on the clockwork mod restore but it still didn't work so I then formatted the sd but as soon as I did this I thought that can't be right as surely the recovery image is on that but it was too late. After it rebooted the fire TV no longer works. It just hangs on the White amazon logo. I've tried the "ALT-PRNT SCREEN-I" option to try get it to restore but with no luck, it just constantly stays on the White amazon logo so I'm kinda thinking I've totally wiped the fire TV and have therefore bricked it. It does respond to "control-alt-delete" but that just reboots the device.
Can anyone advise if this is indeed the case so I don't waste any of my time trying to fix this. I can't return the product as I purchased it on a recent holiday to usa and I'm from uk so a bit gutted.
Many thanks in advance
Paul1672

Sounds like you wiped your /system. If so, then yes you are soft bricked.

I have soft bricked this unit before and managed to restore it but that was before I installed the clockwork mod and custom rom.
If it is soft bricked surely I would be able to restore it still? I have tried several times to get it to return to the clockwork mod restore using the "ALT-PRINTSCREEN-i" method but all I get is the constant white Amazon logo. It feels like I've totally wiped the entire system including all sign of clockwork mod
Can anyone advise if I have indeed totally messed it up or is there any hope for me?
Paul

Anybody got any advice or opinion be it good or bad?
Before I bin the unit
Paul

Paul1672 said:
Anybody got any advice or opinion be it good or bad?
Before I bin the unit
Paul
Click to expand...
Click to collapse
Yes, I have some advice. Don't do that crap again. Be smart. And I'm a bit curious, you talk about an external harddrive and you then talk about wiping the SD card. You mean the /sdcard directory in the AFTV? Seriously? If that is the case, I have some better advice for you. Don't tinker with stuff you don't understand.

So I can assume from your reply I have indeed wiped the entire system and there is in fact no way to repair/restore the device? Totally agree with all you said and I did realise my error literally as soon as I did it a harsh lesson learnt I think and believe me it's not one I will be repeating.
Was just hoping I may be lucky and find someone who has a way of solving my issue but it appears not
Paul

Hi
What's your suggestion or advice be to resolve the problem that was presented.
Cheers
nyder said:
Yes, I have some advice. Don't do that crap again. Be smart. And I'm a bit curious, you talk about an external harddrive and you then talk about wiping the SD card. You mean the /sdcard directory in the AFTV? Seriously? If that is the case, I have some better advice for you. Don't tinker with stuff you don't understand.
Click to expand...
Click to collapse

Paul1672 said:
So I can assume from your reply I have indeed wiped the entire system and there is in fact no way to repair/restore the device? Totally agree with all you said and I did realise my error literally as soon as I did it a harsh lesson learnt I think and believe me it's not one I will be repeating.
Was just hoping I may be lucky and find someone who has a way of solving my issue but it appears not
Paul
Click to expand...
Click to collapse
Naw, you didn't brick you device. Sorry, was in some sort of mood when posted.
http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
That link gives information. You need to get into recovery mode and a factory restore. If the factory restore doesn't work, then just use the same firmware you had before you deleted the stuff. You can put any firmware on a usb stick and read it from that.
Most of this has been covered in the various threads, I suggest you browse thru them, lots of good stuff.
good luck, and sorry I didn't include this in my last post, i should of.

Are u sure mate? I've tried the Alt-prntscreen-I method without any success. The fire tv won't boot into the clockwork mod recovery at all and I'm wondering if I've formatted it somehow. I guess until I get into the restore screen I can't do a thing I did have clockwork mod installed and a custom rom, wud that make a difference as I did indeed format the fire tv sd partition.
Appreciate your help
Paul

Paul1672 said:
Are u sure mate? I've tried the Alt-prntscreen-I method without any success. The fire tv won't boot into the clockwork mod recovery at all and I'm wondering if I've formatted it somehow. I guess until I get into the restore screen I can't do a thing I did have clockwork mod installed and a custom rom, wud that make a difference as I did indeed format the fire tv sd partition.
Appreciate your help
Paul
Click to expand...
Click to collapse
You should be able to get to a recovery screen from what you did, I would think, unless maybe if you deleted everything from the root directory, not the sdcard directory. I am not an expert on that though. It's our thanksgiving holiday here in the states, so the peeps that know might not be around.
Sorry I can't be more helpful then that.

You copy your recovery.img to the sdcard only as an interim step for flashing. It then gets stored in a separate partition that CWM won't wipe. If you have done the changes you mention from CWM, then CWM is still present on the device. I had to get in to my system with the alt-prtscreen-I method as well, and it took a few tries, spamming the keeps after unplugging and replugging the device. Also if you are using a k400 or some other keyboard with a FN key you may have to push that as well to make sure it gets the proper key sequence. I'm fairly confident your device is only softbricked and can be recovered. you may need to adb sideload or copy a zip to usb to load the firmware, but it should be doable.

well, I've tried constantly rebooting and pressing alt-printscreen-I simultaneously for the last half hour with no luck wotsoever all I get is the constant white amazon logo. in fact, the logo appears as soon as I connect the power lead and just hangs there until I either remove the lead or press control-alt-delete at which point the device reboots.
something tells me I've done something a lot more serious than just wipe the sd partition but I'm a little surprised if clockwork mod would allow it.
kinda giving up now as I have soft bricked the device before but that was before I installed clockwork mod and it went to factory restore just fine doing the alt-printscreen-i method that time.
thanks for all the advice guys. I really do appreciate any help I have had. I'm willing to try anything to try get this unit to work. the way I see it, I have nothing to lose right now. just seems strange the unit no longer shows any sign of changing from the constant white amazon logo. there's definitely no sign of the colourful amazon logo that usually appears at some point during the boot process which kinda gives me the impression I've somehow completely wiped the whole system.
is that even possible guys?

If you are saying that ctrl-alt-del reboots your box then the alt -sysrq-i should get you to recovery. Try using a wired keyboard and maybe a different keyboard than you have been using.

Ive tried a wired keyboard and now when I press ALT-PRNTSCREEN-i the fire tv just reboots. I've followed the guide that is in a previous reply which I have been able to do on a previous unrelated soft brick I managed but this time each time I do the ALT-PRINTSCREEN-i combo it just reboots and nothing else. Just a white AMAZON logo. I have done the method like 5 times and still no joy

Paul1672 said:
Ive tried a wired keyboard and now when I press ALT-PRNTSCREEN-i the fire tv just reboots. I've followed the guide that is in a previous reply which I have been able to do on a previous unrelated soft brick I managed but this time each time I do the ALT-PRINTSCREEN-i combo it just reboots and nothing else. Just a white AMAZON logo. I have done the method like 5 times and still no joy
Click to expand...
Click to collapse
Call Amazon and play stupid saying it just hangs at the logo, I did that once and they send me a replacement free of charge.

Wish I could but i purchased it whilst on holiday in Florida and I'm from the uk

Anybody got any more advice? It seems really strange that I can't get the factory reset to work. Still stuck on the White Amazon logo which boots instantly as soon s I power the device. I've managed to get the device to power cycle using ALT-PRNTSCREEN-i method bit it's does it going on 20 times with absolutely no sign of the failed update screen so it looks like the device just doesn't have anything on it. Is it possible I've somehow completely wiped the clockwork mod recovery? And if I have shud the device revert back to factory restore or may I of wiped that too?

Paul1672 said:
Anybody got any more advice? It seems really strange that I can't get the factory reset to work. Still stuck on the White Amazon logo which boots instantly as soon s I power the device. I've managed to get the device to power cycle using ALT-PRNTSCREEN-i method bit it's does it going on 20 times with absolutely no sign of the failed update screen so it looks like the device just doesn't have anything on it. Is it possible I've somehow completely wiped the clockwork mod recovery? And if I have shud the device revert back to factory restore or may I of wiped that too?
Click to expand...
Click to collapse
no its not possible that you wiped recovery from what you did in cwm.. its located on a different partition, if you cant connect via ADB or cant get recovery to load your out of luck.. so did you install the newest prerooted rom? what about the boot menu?

I had the following pre-rooted rom installed:
51.1.4.0_514006420 updated
Sounds like I've messed it up then

Paul1672 said:
I had the following pre-rooted rom installed:
51.1.4.0_514006420 updated
Sounds like I've messed it up then
Click to expand...
Click to collapse
no need for the boot menu on that update iirc. i think you need to just keep trying to get to recovery, i think its still there.. the key command is just not registering.. keep trying i guess.

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.

A100 bricked, possibly even dead, need help

Okay so I'm running stock ICS without root or any custom stuff, everything just stock, today I was listening to music and decided to change the songs, so I pressed the power button but the screen didn't come on, tried a few more times, the screen didn't come on but the music kept going, so out of desperation I held down the power button and after 3 seconds or so it sounded like a BSOD, sound repeated quickly for a second then just nothing.
So after that I tried starting it up back again, here we go, acer logo....aaaannnddd.......nothing.
Tried a few more times and left it over 30 minutes yet nothing. just that acer logo.
so finally I though I could flash a stock rom file, so I grabbed the .014 ics file and put it in my freshly formatted micro sd under the name update.zip (and no I didn't have the double .zip), then I went to recovery, it came up with the familiar android with his chest open and the spinning cube thingy in front of him, then after 5 seconds it came up with the android and the red warning sign above him, which usually meant either SD card not found or update.zip not found, tried a few more times and NOTHING.
FINALLY, I tried the volume down and rotation lock method to try factory reset, it erased userdata and cache and fingers crossed...yet nothing.
am I SOL? Or is there any hope at all, I tried connecting to a computer while it's at the Acer logo screen, you can hear the USB connect and disconnect sound, but adb won't detect it, please help, I love this thing too much and Acer wants me to pay 100 dollars to fix it, I'll die before I do that.
ANY HELP will be appreciated, any suggestions are welcome.
Bump, anyone please??
I love this tablet too much
Try update.zip again on a different SD card. Not all of them work in all devices. Also doubt check its formatted fat32 not something else. Are you sure you have the proper drivers installed for adb?
Tapatalked from my Galaxy S II.
pio_masaki said:
Try update.zip again on a different SD card. Not all of them work in all devices. Also doubt check its formatted fat32 not something else. Are you sure you have the proper drivers installed for adb?
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
I have proper drivers installed and I tried with 2 sd cards, one was almost full but on FAT32, and one was freshly formatted to FAT, I'll try format to FAT32 and report back
I tried formatting to FAT32, placing the update.zip
Sadly, didn't work
Any other suggestions anyone?
Metallica 4 Life said:
I tried formatting to FAT32, placing the update.zip
Sadly, didn't work
Any other suggestions anyone?
Click to expand...
Click to collapse
What does didn't work mean? The answers are in the details, we need them or we're just guessing at random things. Any text, vibrations, lights, pictures all that.
Try adb from a different cable, port, computer? Try hard reset again, hell try 3-4 times, sometimes it takes some persistence.
Oh also plug it into power supply, low battery can cause issues too.
Tapatalked from my A100 - Flex Reaper RF1.
I've been trying for a few days with almost everything, tried APX mode but apparently it doesn't work since you need the CPU ID
and by "doesn't work", I mean I get the vibration, the acer logo pops up, then at the top it starts saying the loading update.zip stuff, then it goes to the green android with it's chest opened and a small blue link ball rotating beside him, after 7-8 seconds, it just shows a dead android, with his chest open and a red triangle with an ! in it.
So yeah, ADB doesn't work, as it never goes past the acer screen.
OK have you managed or tried fastboot? If you can manage that then you should be able to get adb up.
This is basically what I mean about fast boot
http://forum.xda-developers.com/showthread.php?p=27015316
Tapatalked from my Galaxy S II.
Only if I can get to fastboot from stock bootloader, everything I had was stock, OTA ICS, stock bootloader, and no root
Metallica 4 Life said:
Only if I can get to fastboot from stock bootloader, everything I had was stock, OTA ICS, stock bootloader, and no root
Click to expand...
Click to collapse
You can that's how you unlock the boot loader, check out that post and give it a shot.
Tapatalked from my Galaxy S II.
Can you maybe link me or if you know tell me how to get to it? I'm kind of new to all of this :/, I tried searching with no results
Take a read through this thread
http://forum.xda-developers.com/showthread.php?t=1655945
It discusses a slightly different scenario but the techniques attempted are what I mean to try.
Post #3 gives a good outline of steps to try. Also 14 25 31 maybe 27 if it goes south.
I've never personally experienced this so I have no experience however the process in that thread is the same I would attempt if it happened to me. Basically it will attempt to unlock the boot loader then flash a custom recovery which you can then install a new rom. It will turn it into a modded device BUT it will unbrick you and make repairing this issue a lot easier in the future.
Tapatalked from my Galaxy S II.
Gave up
Update:
So yeah i've tried everything and nothing seemed to work, all it shows is that acer logo
Gave it to my sister, she said she'd send it back to the acer facility, hope for best.

[Q] Think I bricked it from flashing!! Please help!!

Pretty sure that I screwed things up pretty good and its either bricked or I think stuck in fastboot every time it turns on!! Here's what I did:
So I downloaded the newest rooted rom (51.1.4.0_514006420 updated) from aftvnews.com...
not very patient so put it on an external drive and copied it to internal sd on the FireTV...
went into CWM (6.0.5.1.4a) and tried to flash it but got an error that it failed, wiped cache/dalvik just because and rebooted...
It kept on booting into CWM and finally realized I had another file on the sd just named rom - assuming that it was the version I was on before (51.1.3...) so wiped data/factory reset and flash that...
Immediately tried to flash the 51.1.4 over that - like an idiot - and that failed again...
wiped data/factory reset and tried to flash 51.1.3 and that failed...
wiped data/factory reset and rebooted...
Now I'm stuck on white Amazon logo and cant do anything with it!!
Any ideas would be greatly appreciated!!!! Is there any way to force it into recovery when it starts up
Mike3.14159 said:
Now I'm stuck on white Amazon logo and cant do anything with it!!
Any ideas would be greatly appreciated!!!! Is there any way to force it into recovery when it starts up
Click to expand...
Click to collapse
Does anyone know if the plain white amazon logo means it's stuck in fastboot??
If so, has anyone had any luck attaching a male-to-male usb to the back and do any fastboot commands??
If I can do a "fastboot reboot recover" then I can possibly fix it from CWM...
Mike3.14159 said:
Does anyone know if the plain white amazon logo means it's stuck in fastboot??
If so, has anyone had any luck attaching a male-to-male usb to the back and do any fastboot commands??
If I can do a "fastboot reboot recover" then I can possibly fix it from CWM...
Click to expand...
Click to collapse
Have you tried this:
http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
cd2022 said:
Have you tried this:
http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
Click to expand...
Click to collapse
Yeah, tried that like a dozen times before I posted again last time. Seems like that will only work if you soft bricked and the rom just wont fully boot. They were talking about the 'color logo' which I'm not even getting that far - gets hung up on the initial white logo. Appreciate the try though, thanks!
Mike3.14159 said:
Yeah, tried that like a dozen times before I posted again last time. Seems like that will only work if you soft bricked and the rom just wont fully boot. They were talking about the 'color logo' which I'm not even getting that far - gets hung up on the initial white logo. Appreciate the try though, thanks!
Click to expand...
Click to collapse
To quote the CWM post...
[size=+2]If something fails to flash DO NOT reboot. Try again and/or retransfer the file over adb.[/size]
Click to expand...
Click to collapse
If your /system is corrupt, it's not gonna boot. You can try the sysrq trick, but I don't think anyones ever been able to make that work with a bad /system.
Not sure what the 'sysrq' trick is but I will look it up and see what I can do, thanks! Saw on aftvnews late yesterday that the newest ota - after being rooted - did something crazy to yours so was actually waiting to see what had happened to yours and if you were able to get it back right then was hoping I could maybe learn some trick from that haha
Have you managed to fix this? i'm also stuck on the white logo
Looks like white logo without going to the colored logo means hard brick. Any USB attached will not work. There is no power coming out.
I wonder if there is a way to open up the unit and reflash the hardware from there.

[Q] PLEASE HELP! Update started on rooted FTV them unplugged.

When I got home I turned on the FTV and briefly saw an update prompt, ands then I must of accidentally hit the accept button on the remote and the device started to remote and update but I immediately pulled the power cord to prevent the update.
Now I have no idea what to do next. Is there anyway to stop the update when I plug it in ands if not, will I able to get root again?
Thanks for all the help everyone.
madtork said:
When I got home I turned on the FTV and briefly saw an update prompt, ands then I must of accidentally hit the accept button on the remote and the device started to remote and update but I immediately pulled the power cord to prevent the update.
Now I have no idea what to do next. Is there anyway to stop the update when I plug it in ands if not, will I able to get root again?
Thanks for all the help everyone.
Click to expand...
Click to collapse
Do you have cwm recovery? If so you could boot to it and do a factory reset, then be sure to pm disable updates. For now I'd block amazon domains on your router but that's not a 100% guarantee. Aftvnews should have any info you need.
I don't think I installed CMW. Is there anyway to tell at this point, and if it's installed, how do I boot into it? I blocked Amazon updates with my router but recently connected with my phone's hotspot without thinking and it must of downloaded the update then.
Anyone have any other recommendations at this point? If I don't have CWM am I out of luck?
madtork said:
Anyone have any other recommendations at this point? If I don't have CWM am I out of luck?
Click to expand...
Click to collapse
If you do have ClockworkMod, then you're safe because it will prevent the update from installing. A Fire TV with ClockworkMod that gets an OTA update will download the update, then restart the Fire TV in recovery mode. Since stock recovery has been replaced with ClockworkMod, it will just ignore the stock update.
If you don't have ClockworkMod, you can use the ALT+PrintScreen+i method to hopefully get into stock recovery without installing the update. From there, I would clear the cache partition and do a factory reset. More info on how to do that can be found here: http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
I don not know if that will work, but it's your best bet.
AFTVnews.com said:
If you do have ClockworkMod, then you're safe because it will prevent the update from installing. A Fire TV with ClockworkMod that gets an OTA update will download the update, then restart the Fire TV in recovery mode. Since stock recovery has been replaced with ClockworkMod, it will just ignore the stock update.
If you don't have ClockworkMod, you can use the ALT+PrintScreen+i method to hopefully get into stock recovery without installing the update. From there, I would clear the cache partition and do a factory reset. More info on how to do that can be found here: http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
I don not know if that will work, but it's your best bet.
Click to expand...
Click to collapse
That's what I was hoping for. Thanks for the information!
So I connected a keyboard and tried for an hour or better to get this thing into recovery but with no success. I tried the ALT+PRT SCRN+I and it just won't work. It keeps going into the update screen and I keep unplugging the box. If someone can help me get this going I will PAYPAL YOU $20!
Otherwise I am giving this thing away.
madtork said:
So I connected a keyboard and tried for an hour or better to get this thing into recovery but with no success. I tried the ALT+PRT SCRN+I and it just won't work. It keeps going into the update screen and I keep unplugging the box. If someone can help me get this going I will PAYPAL YOU $20!
Otherwise I am giving this thing away.
Click to expand...
Click to collapse
It's thankfully never happened to me but just from reading here, it can be incredibly hard to get to recovery. They're mostly trying to get to cwm (which I believe you don't have?) But in theory I think it should work with stock...
If possible, try a different keyboard. If using a hub then connect it directly. Change your timing (when you actually press the keys) Alter between holding them down the keys and tapping them. And just for the heck of it, try working in the remote at some point (back button and right arrow for 15 seconds performs reset)
Sorry. It sounds silly but many people have needed to get to recovery and no one can definitively say what works for everyone. At least I don't think anyone can??? Good luck
AFTVnews.com said:
If you do have ClockworkMod, then you're safe because it will prevent the update from installing. A Fire TV with ClockworkMod that gets an OTA update will download the update, then restart the Fire TV in recovery mode. Since stock recovery has been replaced with ClockworkMod, it will just ignore the stock update.
If you don't have ClockworkMod, you can use the ALT+PrintScreen+i method to hopefully get into stock recovery without installing the update. From there, I would clear the cache partition and do a factory reset. More info on how to do that can be found here: http://www.aftvnews.com/how-to-unbr...ry-mode-and-factory-reset-the-amazon-fire-tv/
I don not know if that will work, but it's your best bet.
Click to expand...
Click to collapse
KLit75 said:
It's thankfully never happened to me but just from reading here, it can be incredibly hard to get to recovery. They're mostly trying to get to cwm (which I believe you don't have?) But in theory I think it should work with stock...
If possible, try a different keyboard. If using a hub then connect it directly. Change your timing (when you actually press the keys) Alter between holding them down the keys and tapping them. And just for the heck of it, try working in the remote at some point (back button and right arrow for 15 seconds performs reset)
Sorry. It sounds silly but many people have needed to get to recovery and no one can definitively say what works for everyone. At least I don't think anyone can??? Good luck
Click to expand...
Click to collapse
That's the best reply yet. Your correct, I don't have Clock work recovery. I'll try to add in the remote to the equation. Thank you for your input.
Anyone want a free Amazon FTV? I can't get it into recovery.
I'll take it!
madtork said:
Anyone want a free Amazon FTV? I can't get it into recovery.
Click to expand...
Click to collapse
I'll take it!!!! I dont know how to fix, but will try my damnedest!
Can you email [email protected]?
---------- Post added at 01:04 AM ---------- Previous post was at 01:00 AM ----------
Lowaek said:
I'll take it!!!! I dont know how to fix, but will try my damnedest!
Can you email [email protected]?
Click to expand...
Click to collapse
I will also pay shipping!

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?

Categories

Resources