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:
Alright guys, so I tried using KFU on my 1gen Kindle Fire. I selected option 2 right off the bat and I'm guessing I should have hit option 1 and booted into fastboot first lol sorry I'm a noob.
Well now the Kindle will turn on but it will go directly to the "Kindle Fire" white and orange logo and do nothing else. I've let it sit here for like 10-20 min and still nothing. I've also tried using a couple different tools and methods (firekit being the last I tried) to no avail.
Any help would be amazing guys! Thanks so much for everything you do already.
rcarlson21 said:
Alright guys, so I tried using KFU on my 1gen Kindle Fire. I selected option 2 right off the bat and I'm guessing I should have hit option 1 and booted into fastboot first lol sorry I'm a noob.
Well now the Kindle will turn on but it will go directly to the "Kindle Fire" white and orange logo and do nothing else. I've let it sit here for like 10-20 min and still nothing. I've also tried using a couple different tools and methods (firekit being the last I tried) to no avail.
Any help would be amazing guys! Thanks so much for everything you do already.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2166668
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2166668
Click to expand...
Click to collapse
Yeah, I'm actually reading that right now haha. I believe I'm stuck in fastboot but I don't think my computer has the fasboot drivers so I'm looking to get those, download those and see what happens from there.
I'm not looking for a hand out , I'm working on it myself as much as I'm asking for help I promise.
rcarlson21 said:
Yeah, I'm actually reading that right now haha. I believe I'm stuck in fastboot but I don't think my computer has the fasboot drivers so I'm looking to get those, download those and see what happens from there.
I'm not looking for a hand out , I'm working on it myself as much as I'm asking for help I promise.
Click to expand...
Click to collapse
UPDATE! Alright I got it back into Normal mode !!! All by my self too really. Thanks for that little link though, if I hadn't already been searching that would have helped me out a freaking ton! Now it's time to get down to business.
UPDATE 2! Haha, alright well I'm trying to use KFU but it doesn't seem to be working well. I just put it back into fastboot mode and now it's pulling the same **** over again. All I wanna do is root this thing... Any help?
UPDATE 3! So not that any of you really care but I got a new recovery on it now ! Working on FFF and then rooting it!
Are you just trying to root it or do you want to install a custom ROM? If you want to install a custom ROM, rooting it beforehand is a waste of time.
rcarlson21 said:
So not that any of you really care but I got a new recovery on it now !
Click to expand...
Click to collapse
I'm offended. I do care.
soupmagnet said:
Are you just trying to root it or do you want to install a custom ROM? If you want to install a custom ROM, rooting it beforehand is a waste of time.
I'm offended. I do care.
Click to expand...
Click to collapse
No I do want to root it. I like having access to all the abilities of the device. Right now I'm having TWRP creating a backup before I go any father. It's taking forever though .
I kid I kid . You wouldn't be trolling the forums with your knowledge if you didn't haha.
Alright, so I've got FFF on there now. I'm just waiting for KFU to do it's thing and hopefully root this thing ><. Thanks for nothing yet really
rcarlson21 said:
No I do want to root it. I like having access to all the abilities of the device. Right now I'm having TWRP creating a backup before I go any father. It's taking forever though .
I kid I kid . You wouldn't be trolling the forums with your knowledge if you didn't haha.
Click to expand...
Click to collapse
All custom ROMs are rooted anyway, which is why I say if you are going to install a custom ROM, rooting it again is pointless.
You guys are way too advanced for me
I'm just a newbie and I try to make my life with KF easier, not more complicated by reading and reviewing how to use the KFU tools.
First, I download the zip file then I unzip it then I install drivers as instructed then start using the beautiful useful tools.
Second, I make sure it reads 4000 and Online by pressing "0" key then press 2 if just want rooting with stock OS. It will automatically install TWRP and FFF. Follow the instruction and it should be done by then.
Nandroid backup with COTR.
Installing custom ROM? read the instruction again on that thread.
Well I got tired of modifying my stock Kindle OS and getting wierd results so I tried a Second Time to Install CM10 on my KFHD 8.9 (FW 8.1.4) Followed this guide: http://forum.xda-developers.com/showthread.php?t=2100963 Got to step 4 and at this point the damn thing hard bricked. No fast boot, No Safe boot, No boot at all just a black screen. How come everyone else can seem to get it right but me? Anyway I have already recieved 1 replacement device from Amazon, and I am quite poor and cannot afford expensive tools or another system. So My question here is 2 fold. Is there any fix for this? and if so what is the safest way to attempt TWRP and CM10? Thanks and hope to hear from somebody.
JonnyLawless said:
Well I got tired of modifying my stock Kindle OS and getting wierd results so I tried a Second Time to Install CM10 on my KFHD 8.9 (FW 8.1.4) Followed this guide: http://forum.xda-developers.com/showthread.php?t=2100963 Got to step 4 and at this point the damn thing hard bricked. No fast boot, No Safe boot, No boot at all just a black screen. How come everyone else can seem to get it right but me? Anyway I have already recieved 1 replacement device from Amazon, and I am quite poor and cannot afford expensive tools or another system. So My question here is 2 fold. Is there any fix for this? and if so what is the safest way to attempt TWRP and CM10? Thanks and hope to hear from somebody.
Click to expand...
Click to collapse
Unfortunately that Kindle is more than likely done for good. What you flashed was for a Kindle Fire 2 to your Kindle Fire HD 8.9.
Look I really need help. When I was trying to install a rom on my kindle i accidentally wiped the system. I wiped everything!!! And i'm sure of it!!! And so i looked up what to do and it said I need to Update My Kindle again so i loaded the update with twrp and I rebooted and It made it worse!!! My kindle is just stuck at the logo screen and I have no idea what to do. I've looked up unbricking tools but they always say "Device Not Found". I've alway been kind of a jailbreak/rooting person but this is new to me. Please explain as best as you can because i'm only a kid and i'm new to the whole rooting or installing android on your kindle kind of thing. I also don't know if this is the right place to post this but if it isnt please don't get mad.
Please if you can give specific instruction on what to do. If you can also please give me instructions on how to install cyanogen on my kindle so I don't mess up again.
I have the first Kindle Fire and I want to install CM11.0 on my kindle.
Read This
elmolisa885 said:
Look I really need help. When I was trying to install a rom on my kindle i accidentally wiped the system. I wiped everything!!! And i'm sure of it!!! And so i looked up what to do and it said I need to Update My Kindle again so i loaded the update with twrp and I rebooted and It made it worse!!! My kindle is just stuck at the logo screen and I have no idea what to do. I've looked up unbricking tools but they always say "Device Not Found". I've alway been kind of a jailbreak/rooting person but this is new to me. Please explain as best as you can because i'm only a kid and i'm new to the whole rooting or installing android on your kindle kind of thing. I also don't know if this is the right place to post this but if it isnt please don't get mad.
Please if you can give specific instruction on what to do. If you can also please give me instructions on how to install cyanogen on my kindle so I don't mess up again.
I have the first Kindle Fire and I want to install CM11.0 on my kindle.
Click to expand...
Click to collapse
Read This :good:
I Looked at it and it doesn't seem to solve my problem
serendipityguy said:
Read This :good:
Click to expand...
Click to collapse
I read the unbricking section of the guide and it doesn't help me very much. I think the one I need to do Is buy the special usb cable and I don't want to do that....I there another way? I'm so confused....
elmolisa885 said:
I read the unbricking section of the guide and it doesn't help me very much. I think the one I need to do Is buy the special usb cable and I don't want to do that....I there another way? I'm so confused....
Click to expand...
Click to collapse
I could be wrong, but it sounds like you are stuck in fastboot mode after flashing twrp. I don't think you are bricked. You can confirm this by using fastboot from your pc.
FWIW, wiping system is ok when flashing a rom - but wiping internal storage before flashing will leave you without any file to flash. Simply push the rom to the sd card on kindle (google it). You may have to reboot recovery for twrp to show the newly added file.
So bottom line - change the bootmode from fastboot to normal. Boot into recovery. Push new rom/gapps using adb. Reboot recovery. Flash new rom and gapps.
I think with so many threads like this folks are just sick of directing people to all the other multiple threads that would tell you how to fix this. Next time please use the 'search' feature (not trying to be rude here, but the first rule of XDA is to search).
elmolisa885 said:
Look I really need help. When I was trying to install a rom on my kindle i accidentally wiped the system. I wiped everything!!! And i'm sure of it!!! And so i looked up what to do and it said I need to Update My Kindle again so i loaded the update with twrp and I rebooted and It made it worse!!! My kindle is just stuck at the logo screen and I have no idea what to do. I've looked up unbricking tools but they always say "Device Not Found". I've alway been kind of a jailbreak/rooting person but this is new to me. Please explain as best as you can because i'm only a kid and i'm new to the whole rooting or installing android on your kindle kind of thing. I also don't know if this is the right place to post this but if it isnt please don't get mad.
Please if you can give specific instruction on what to do. If you can also please give me instructions on how to install cyanogen on my kindle so I don't mess up again.
I have the first Kindle Fire and I want to install CM11.0 on my kindle.
Click to expand...
Click to collapse
If you flashed update.zip sounds to me like you have a broken or missing shell. In which cases you will need a factory cable found here post 9 http://forum.xda-developers.com/showthread.php?t=1392693 . This will force it into fastboot so you can reflash fff and twrp then add a running OS.
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.