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