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.
Related
Today I tried loading 4.1 Jellybean on my fire, but it wasn't opening applications properly and being annoying so I unloaded it. I used KFU to root it, and had TWRP recovery on it. I then figured I'd revert it back to the default OS, so I grabbed a copy of the kindle fire 6.2.1 software from Amazon's page and renamed it to update.zip (it converted to a .zip with identical contents to the one directly from KFU).When I had TWRP, KFU recognized my device as online, but didn't have a version, so there was no help there. I wiped the entire thing using the recovery tool and then I hit "Install --> Update.zip". Everything seemed fine after this worked, so I rebooted the device. I thought it worked, but now it's stuck at the Kindle Fire default splash screen. When I plug iit into my computer, Windows doesn't recognize it, nor does KFU. I haven't tried letting the battery drain (since that would take awhile), but it seems like it's bricked. Please help!
EDIT: My main problem right now is that it can't even be recognized at windows. I feel like it's stuck in the wrong fastboot mode right now, but I can't even get windows to recognize it. Also, it's not running Fire fire fire, the splash screen shows the basic unanimated Kindle Fire logo. It's likely stuck on fastboot 4002 instead of 4000. I'm currently letting the battery drain so I can plug it in and see if windows will recognize it. My guess is that I can get it to work as long as windows will recognize it.
I don't have time right now to get into very much with you, so I'll have to edit my post when I can (unless someone beats me to it). For now, though...
DON'T LET YOUR BATTERY DIE!
soupmagnet said:
I don't have time right now to get into very much with you, so I'll have to edit my post when I can (unless someone beats me to it). For now, though...
DON'T LET YOUR BATTERY DIE!
Click to expand...
Click to collapse
Are you sure about that? I was just reading about how it's just stuck in the fastbooter and I have to let the battery drain, plug it into my computer to get my computer to recognize it, and then it should work. Then I just have to change the fastbooter from 4002 to 4000 and it should work. Is this wrong?
shnish said:
Are you sure about that? I was just reading about how it's just stuck in the fastbooter and I have to let the battery drain, plug it into my computer to get my computer to recognize it, and then it should work. Then I just have to change the fastbooter from 4002 to 4000 and it should work. Is this wrong?
Click to expand...
Click to collapse
You're right, I'm lying to you. I have nothing better to do than to feed you misinformation in the hopes that it will prolong your suffering.
soupmagnet said:
You're right, I'm lying to you. I have nothing better to do than to feed you misinformation in the hopes that it will prolong your suffering.
Click to expand...
Click to collapse
I know that you know more about this than me, but I feel like if it's stuck on the wrong fastboot type, preventing the battery from draining would be a bad idea (or at least slow down the "fixing" processor). Sorry, but why does that seem so wrong?
Since you are having trouble spotting the STICKY at the top of this forum, I'll help you out a bit.
http://forum.xda-developers.com/showthread.php?p=25400963
soupmagnet said:
You're right, I'm lying to you. I have nothing better to do than to feed you misinformation in the hopes that it will prolong your suffering.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11
This is what I read that might solve my problem. Does it seem incorrect? I feel like the only way to get it to recognize the kindle fire in windows is to either manually put it in USB mode by prying off the back cover, or to let the battery drain.
soupmagnet said:
Since you are having trouble spotting the STICKY at the top of this forum, I'll help you out a bit.
http://forum.xda-developers.com/showthread.php?p=25400963
Click to expand...
Click to collapse
But my Fire won't even work when plugged into my computer. Can you really quickly explain any steps I should take to at least get windows to recognize it? Thanks!
shnish said:
But my Fire won't even work when plugged into my computer. Can you really quickly explain any steps I should take to at least get windows to recognize it? Thanks!
Click to expand...
Click to collapse
umm...
soupmagnet said:
I don't have time right now to get into very much with you, so I'll have to edit my post when I can (unless someone beats me to it). For now, though...
Click to expand...
Click to collapse
soupmagnet said:
umm...
Click to expand...
Click to collapse
Alright. Looks like I might need a factory cable?
shnish said:
http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11
This is what I read that might solve my problem. Does it seem incorrect? I feel like the only way to get it to recognize the kindle fire in windows is to either manually put it in USB mode by prying off the back cover, or to let the battery drain.
Click to expand...
Click to collapse
Some of the ideas in the post are going in the right direction, but draining your battery is not one of them. That would only complicate matters.
I suggest you slow down and do some reading...
http://forum.xda-developers.com/showthread.php?t=1668159
You must first determine what state your device is in based on what happens when the device powers up. The only way you'll be able to fix this problem quickly is if you are truly in fastboot mode, but I have some doubts about that. If you do not understand the terminology used in the post above, you must read this...
http://forum.xda-developers.com/showthread.php?t=1552547
If you are going to rely on the help of others here, you are going to have to learn the jargon and understand how these parts fit together. I suggest you do that before proceeding.
The second post in that guide will help you to fix your device drivers and have the computer recognize the device.
Personally, if I were in your shoes, I'd find a way back to fastboot mode and reflash TWRP and then FFF from TWRP before trying to boot it normally. If your system partition happens to be broken and you reboot it into it, you'll be going backwards and then you'll need a factory cable or have to open up the case.
kinfauns said:
Some of the ideas in the post are going in the right direction, but draining your battery is not one of them. That would only complicate matters.
I suggest you slow down and do some reading...
http://forum.xda-developers.com/showthread.php?t=1668159
You must first determine what state your device is in based on what happens when the device powers up. The only way you'll be able to fix this problem quickly is if you are truly in fastboot mode, but I have some doubts about that. If you do not understand the terminology used in the post above, you must read this...
http://forum.xda-developers.com/showthread.php?t=1552547
If you are going to rely on the help of others here, you are going to have to learn the jargon and understand how these parts fit together. I suggest you do that before proceeding.
The second post in that guide will help you to fix your device drivers and have the computer recognize the device.
Personally, if I were in your shoes, I'd find a way back to fastboot mode and reflash TWRP and then FFF from TWRP before trying to boot it normally. If your system partition happens to be broken and you reboot it into it, you'll be going backwards and then you'll need a factory cable or have to open up the case.
Click to expand...
Click to collapse
The device ended up losing power, but it still powers on properly when I plug it in (stuck on the kindle fire logo, of course).
I suppose it's not in fastboot mode, it's just stuck on the stock loader. I'm not quite positive, but it seems like I'll need a factory cable to get this thing working again. I really don't want to have to blow any money on this, if I can revert it back to stock settings easily, I'll never mess with it again. Is there any additional help that can be given if it's stuck on an unanimated stock screen and won't be recognized by windows?
shnish said:
Is there any additional help that can be given if it's stuck on an unanimated stock screen and won't be recognized by windows?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=30629067
[Edit:] This might be helpful as well...
http://forum.xda-developers.com/showpost.php?p=31117605
soupmagnet said:
http://forum.xda-developers.com/showpost.php?p=30629067
[Edit:] This might be helpful as well...
http://forum.xda-developers.com/showpost.php?p=31117605
Click to expand...
Click to collapse
So if I install Ubuntu, I should be good to go? Ubuntu will recognize the kindle fire?
Read the post I gave you.
soupmagnet said:
http://forum.xda-developers.com/showpost.php?p=30629067
[Edit:] This might be helpful as well...
http://forum.xda-developers.com/showpost.php?p=31117605
Click to expand...
Click to collapse
Yes. He has the exact same problem as me! I did the same thing as him, and I'm really hoping I'll be able to solve this issue. All I want is the stock kindle back so I can stop worrying. I've read through tons of these posts (I have 13 xda posts open in my browser), but none of them seem too helpful as to how I can get my computer to recognize the Kindle. My guess is that Ubuntu won't recognize the Kindle either, though. In that case, would a factory cable solve all my problems? I stupidly removed root access by simply updating my kindle fire without thinking of the problems that could have come with that. I figured it would just remove root access and start booting up normally. I was very wrong.
soupmagnet said:
Read the post I gave you.
Click to expand...
Click to collapse
I'm going to try it in Ubuntu, but assuming that doesn't work, I'll need to get a factory cable. What do I do to revert to stock settings once I have a factory cable?
I'm really trying to be patient with you, but you're making it extremely difficult for me.
Your lack of attention is troubling. If you would take some time to actually read and process the information given to you, you would see that everything you need to know to fix your problem is there. Be a little less argumentative and follow direction, and you'll see that, not only are people more willing to help but you'll have your problem solved a lot easier and faster than you are now.
That being said, this will be the last bit of help you'll recieve from me...
The first link I gave you, sends you to my SoupKit thread. Read it. Ubuntu(Linux) does not detect the Kindle Fire (or any Android device) by default; it must be configured, which is why I sent you to the "Idiot-proof way to configure Linux for adb and fastboot".
While booted into Linux, run the script and reboot; that's it. You can figure out how to fix your Kindle on your own from there.
soupmagnet said:
I'm really trying to be patient with you, but you're making it extremely difficult for me.
Your lack of attention is troubling. If you would take some time to actually read and process the information given to you, you would see that everything you need to know to fix your problem is there. Be a little less argumentative and follow direction, and you'll see that, not only are people more willing to help but you'll have your problem solved a lot easier and faster than you are now.
That being said, this will be the last bit of help you'll recieve from me...
The first link I gave you, sends you to my SoupKit thread. Read it. Ubuntu(Linux) does not detect the Kindle Fire (or any Android device) by default; it must be configured, which is why I sent you to the "Idiot-proof way to configure Linux for adb and fastboot".
While booted into Linux, run the script and reboot; that's it. You can figure out how to fix your Kindle on your own from there.
Click to expand...
Click to collapse
Thanks. I normally wouldn't act this way, but I'm having trouble calming down about this (I usually get this way when technology breaks). I know that in the end everything should be fine, but for some reason I can't get myself to actually stop worrying about the damn thing. I really do appreciate all your help, and I swear I have been reading all the links that have been sent. It's just that even with what I've read, I don't 100% understand everything. I know the general problem with it, but I'm a complete noob with shell commands. Fixing it once I can actually connect should be easier, just have to put the recovery back onto it and properly set it back to stock settings, right?
shnish said:
Thanks. I normally wouldn't act this way, but I'm having trouble calming down about this (I usually get this way when technology breaks). I know that in the end everything should be fine, but for some reason I can't get myself to actually stop worrying about the damn thing. I really do appreciate all your help, and I swear I have been reading all the links that have been sent. It's just that even with what I've read, I don't 100% understand everything. I know the general problem with it, but I'm a complete noob with shell commands. Fixing it once I can actually connect should be easier, just have to put the recovery back onto it and properly set it back to stock settings, right?
Click to expand...
Click to collapse
:good:
Hi Guys,
I've been rooting android devices for a while now, and this is the first time I've had to post up a question like this... Can't seem to get the Kindle Fire 8.9 to power on. Tried holding power down for over a minute, not dice. 20 seconds, no dice.... I've done a search and can't seem to find anyone else with a 8.9 in this situation. I reached out to SkOrPn and he mentioned for the 8.9 there is NO factory cable to push into fastboot.
Hopefully someone can shed some light?
Thanks.
mcgrathpatj said:
Hi Guys,
I've been rooting android devices for a while now, and this is the first time I've had to post up a question like this... Can't seem to get the Kindle Fire 8.9 to power on. Tried holding power down for over a minute, not dice. 20 seconds, no dice.... I've done a search and can't seem to find anyone else with a 8.9 in this situation. I reached out to SkOrPn and he mentioned for the 8.9 there is NO factory cable to push into fastboot.
Hopefully someone can shed some light?
Thanks.
Click to expand...
Click to collapse
Did you brick it? Sounds like you did.
seokhun said:
Did you brick it? Sounds like you did.
Click to expand...
Click to collapse
Sure seems like I did... I was hoping someone could confirm I did or may have a solution.
If I did it's my first brick! Kind of funny actually. I bought it at best buy.... Hopefully they won't give me too much **** trying to return it.
mcgrathpatj said:
Sure seems like I did... I was hoping someone could confirm I did or may have a solution.
If I did it's my first brick! Kind of funny actually. I bought it at best buy.... Hopefully they won't give me too much **** trying to return it.
Click to expand...
Click to collapse
If you're in warranty, you're good to go. If not, you can always go the factory cable route, see the thread in my signature for the 8.9" #6 and Step 2.
mcgrathpatj said:
Hi Guys,
I've been rooting android devices for a while now, and this is the first time I've had to post up a question like this... Can't seem to get the Kindle Fire 8.9 to power on. Tried holding power down for over a minute, not dice. 20 seconds, no dice.... I've done a search and can't seem to find anyone else with a 8.9 in this situation. I reached out to SkOrPn and he mentioned for the 8.9 there is NO factory cable to push into fastboot.
Hopefully someone can shed some light?
Thanks.
Click to expand...
Click to collapse
Sorry to tell you this but if a KFHD is not powering up even when charged, It's hard bricked, But don't panic.
May i ask what tool you used to root your device, Because it seems to me that you used Kindle Fire Utility KFU, I know this because failing the rooting process can cause a bootloop but will not hard brick your device the way it happened, Only a damaged bootloader can cause the device not to power up, KFU attempts to install FFF bootloader which is designed for the original kindle fire and will damage the bootloader of any 2nd generation device and hard brick it.
What you need to do right now
Ship your device ASAP to Christian Bryant (XDA username Prokennexusa), At
Xerocomm, Inc. - 1684 Northstar Drive - Petaluma CA 94954.
I talked to him and he said if you ship it now it'll be done by the end of the week.
Chris receives many kindles so make sure you send him an email at [email protected]
Good luck
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.
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!
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?