Related
I saw a couple similar threads recently, but my situation is a little different.
My KF2 is totally dead and nothing happens when I plug in a fastboot cable or try and charge it with a wall charger. Prior to this, I was getting the lovely orange Kindle Fire bootloop (which is why I bought the fastboot cable). If it helps, the last time it was running properly I was running 10.2.6, it was rooted and had TWRP and the Google Play store on it. I just got greedy and wanted JB and like a dope wiped everything in TWRP.
Am I totally SOL or is there something I can actually do with this potential brick?
Thanks in advance!
jjdavola said:
I saw a couple similar threads recently, but my situation is a little different.
My KF2 is totally dead and nothing happens when I plug in a fastboot cable or try and charge it with a wall charger. Prior to this, I was getting the lovely orange Kindle Fire bootloop (which is why I bought the fastboot cable). If it helps, the last time it was running properly I was running 10.2.6, it was rooted and had TWRP and the Google Play store on it. I just got greedy and wanted JB and like a dope wiped everything in TWRP.
Am I totally SOL or is there something I can actually do with this potential brick?
Thanks in advance!
Click to expand...
Click to collapse
Did you wipe everything and reboot or did you try to install JB first? What method did you use to install TWRP?
Sent from my Amazon Kindle Fire using Tapatalk 2
soupmagnet said:
Did you wipe everything and reboot or did you try to install JB first? What method did you use to install TWRP?
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply! I wiped and rebooted because I couldn't access the files I installed. I installed TWRP with the TweezerMod.apk.
jjdavola said:
Thanks for the reply! I wiped and rebooted because I couldn't access the files I installed. I installed TWRP with the TweezerMod.apk.
Click to expand...
Click to collapse
The point of Hashcode's stack override is to make it possible to install unsigned boot and recovery images for the purposes of modifying their devices, without the device's security measures having any effect. Since the stack override is installed to a certain location on the system partition, custom ROMs are made to include this necessary information. If you completely wipe the system partition without installing a ROM or replacing the stack override, there is no longer any protection from the device checking to see if those partitions have the necessary signed headers, so you may just be out of luck. Though I have seen situations, especially on my own device, where that wasn't even an issue, so who knows? The Kindle Fire 2 may be different in that regard.
Maybe, someone with a little more knowledge on the subject can shed some light on the situation.
soupmagnet said:
The point of Hashcode's stack override is to make it possible to install unsigned boot and recovery images for the purposes of modifying their devices, without the device's security measures having any effect. Since the stack override is installed to a certain location on the system partition, custom ROMs are made to include this necessary information. If you completely wipe the system partition without installing a ROM or replacing the stack override, there is no longer any protection from the device checking to see if those partitions have the necessary signed headers, so you may just be out of luck. Though I have seen situations, especially on my own device, where that wasn't even an issue, so who knows? The Kindle Fire 2 may be different in that regard.
Maybe, someone with a little more knowledge on the subject can shed some light on the situation.
Click to expand...
Click to collapse
Thanks. I'm still holding out some hope, but I tried to charge it all night with a wall charger and it did nothing.
Since there's no replies, I'm guessing I'm really SOL. Anyone want to buy a brick?
Anyone???
There is a possibility that you have drained the battery and now its dead. After doing all you did to it and rebooted did it display the logo at all and then after some time just cease to power on? If so you could order a replacement battery. If not I'm inclined to agree with Soupmagnet that its looking for a boot id and not finding therefore failing to boot at all.
Thepooch said:
There is a possibility that you have drained the battery and now its dead. After doing all you did to it and rebooted did it display the logo at all and then after some time just cease to power on? If so you could order a replacement battery. If not I'm inclined to agree with Soupmagnet that its looking for a boot id and not finding therefore failing to boot at all.
Click to expand...
Click to collapse
Thanks for the reply. The strange thing is once I got the fastboot cable the green light on the KF2 was on, so I thought I had time. Then after trying to restore everything for a few minutes, the KF2 just died and never came back to life. Although I did connect the regular USB in that short time to see what would happen and it just bootlooping.
The Problem I am having seems to be a Infinite boot logo after Undoing a custom Otter jelly bean KF rom. I went through the motions of ADB KFU booting into recovery. I factory restored, wiped and attempted to install my back up of the stock kindle fire rom. wiped caches, and then let it do its "boot up" how ever it did not move past that point, and has been stuck at the "kindle fire" logo screen.
Is there anyway to fix what I probably broke?
KFU Utility vers 0.9.6
TWRP vers 2.4.4
OS version Windows 8 X64
Kindle fire Rom version 6.2.1
Otter jelly bean was 4.2.1 a release sometime in February is the closest I can get. I can't exactly roll back now can I?
Any other information I forgot or neglected to supply on first post was unintentional. First time I have ever had a problem.
Thanks in advance
~ Zach
I had that problem awhile back. What I ended up doing was flashed another ROM and then see if it worked(it did). Then I flashed the stock ROM again and deleted everything. Cache, SD, factory reset etc. After that it seemed to be working just fine.
Sent from my Nexus 7 using xda app-developers app
jakeyablosky said:
I had that problem awhile back. What I ended up doing was flashed another ROM and then see if it worked(it did). Then I flashed the stock ROM again and deleted everything. Cache, SD, factory reset etc. After that it seemed to be working just fine.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
My problem is, I can't get the device out of this logo "loop" it won't let me install TWRP or the other one. Let alone get into the TWRP currently installed. I wonder if I can get Screen Shots up on here.
leroy329 said:
My problem is, I can't get the device out of this logo "loop" it won't let me install TWRP or the other one. Let alone get into the TWRP currently installed. I wonder if I can get Screen Shots up on here.
Click to expand...
Click to collapse
I think you're having the same problem I'm having. If you look at my post regarding stuck at logo that I posted yesterday see if it's the same.
What is your logo doing? Does it stay bright or does it turn on and blink and then fade?
Based on what I've read we need them to get them into fastboot and then side load TWRP and FFF and start again.
I think what we've done is removed or cleared too much in TWRP and our bootloaders are broken, but I could be talking out of my you know what.
Good luck to you and I will follow your thread and you may want to follow mine.
The only thing I can think of is getting a Factory Cable and reset you Kindle Fire
Sent from my Nexus 7 using xda app-developers app
Leroy,
I think Jakey has it.
I was just about ready to pitch this thing in the trash and I decided to plug in my factory cable one last time and run KFU.
For whatever reason I decided to select the root option again even though it said status offline and it rerooted my device.
My logo is now white/blue and I think I can get a rom back onto it.
You may want to hit Skorpn up for a cable, he shipped it super fast and it's great work.
Leroy,
Since it seems you are having the same problem I was and replies are pretty slow in here these days (I'm sure most people are tired of repeat posts like mine), I thought I would post precisely what I did to fix mine.
I too had the infinite boot logo that stayed bright and tried everything from KFU, to unbrick tool, to Soupkit, nothing seemed to work. I bought a factory cable from Skorpn, but didn't really understand how to use it. I think there is so much information here and many various ways to get things fixed it takes awhile to digest it.
Right before I got ready to pitch it in the trash I figured I would try KFU one more time even though it wasn't seeing my Kindle. Device manager saw the ADB drivers in Android device though.
I plugged in the factory cable
Launched KFU
Device said "offline"
Tried various options until I finally saw the install permanent root with superuser (option 2)
That did the trick
I then unplugged my factory cable from both the PC and KF and booted the KF into recovery
I downloaded a ROM (Hashcodes and GAPPS) and side loaded them
That did it!
I'm not sure how or why since it said it was offline but it fixed it.
Again, Skorpn was awesome to work with and sent the cable to me quickly.
Good luck to you!
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.
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.
I have a perfectly working rooted AFTV1 or rather had.
I had the clockworkmod rbox installed with bootmenu.
Today I decided to upgrade doing the usual adp push. The firmware installed but after boot couldn't connect to the internet.
Therefore I rebooted with the remote and the light went off and no display on the TV.
Now there is no white led indicator. I've tried the keyboard to do the recovery but since there is no led to show there is power I feel the firetv is gone. I've also tried an alternate adapter from another room but no luck.
Anything I can try? much appreciated. I also lost out on the prime day sale
I have the exact same problem. Did you find a solution?
It seems we blew the efuse in our units.
Maybe we can recover using a A-to-A USB cable. I have two of those from external hdd, maybe I can try, just need to find a guide for that.
I connected the AFTV to my computer using the A-to-A cable.
The computer shows a storage device with some files and the device manager shows a Marshall London HS-USB Diagnostics 9006 port.
Any suggestions? ADB and fastboot do not work. There is no device connected
Same thing after sending that sequence alt pntscn i too many times. Now no light and comes up as an f drive with a a cable. ..we are screwed.
Sent from my SM-N900V using XDA-Developers mobile app
davekaz said:
Same thing after sending that sequence alt pntscn i too many times. Now no light and comes up as an f drive with a a cable. ..we are screwed.
Sent from my SM-N900V using XDA-Developers mobile app
Click to expand...
Click to collapse
It is probably possible to write to the unit using EMMCRaw. I tried to do it but screwed something up and now I can't even see the flash drive.
My idea is to download a full bin file for the AFTV, extract it using 7-zip and flash the separate boot, sbl, and other files using EMMCRaw.
I was almost there but manage to flash the full bin file in each category and now it is fully bricked, I can't see the flash drive anymore.
leo_bsb said:
It is probably possible to write to the unit using EMMCRaw. I tried to do it but screwed something up and now I can't even see the flash drive.
My idea is to download a full bin file for the AFTV, extract it using 7-zip and flash the separate boot, sbl, and other files using EMMCRaw.
I was almost there but manage to flash the full bin file in each category and now it is fully bricked, I can't see the flash drive anymore.
Click to expand...
Click to collapse
Sorry for your loss. Thanks for your reply. Is there steps in doing this written somewhere and where do you thing it went wrong for you?
davekaz said:
Sorry for your loss. Thanks for your reply. Is there steps in doing this written somewhere and where do you thing it went wrong for you?
Click to expand...
Click to collapse
I flash the full bin instead of the right files in each section in EMMCraw
You probably should extract the full bin and check the name of the files. You will see they match the categories inside EMMCraw. I read another post explaining the software, saying that you should read the categories first and then flash each file to each category.
I took some risk, but my AFTV was "dead" already so I went ahead.
My opinion is that you should flash BOOT, ABOOT and recovery and hope to get access to ADB and proceed with the already writen guides to flash and unlock the AFTV
leo_bsb said:
I flash the full bin instead of the right files in each section in EMMCraw
You probably should extract the full bin and check the name of the files. You will see they match the categories inside EMMCraw. I read another post explaining the software, saying that you should read the categories first and then flash each file to each category.
I took some risk, but my AFTV was "dead" already so I went ahead.
My opinion is that you should flash BOOT, ABOOT and recovery and hope to get access to ADB and proceed with the already writen guides to flash and unlock the AFTV
Click to expand...
Click to collapse
Are there any instructions on how to recover. Is this the efuse mess? has anyone been able to recover it from this state. No lights.. I have two dead boxes now
Looks like I am in the same boat. Pretty much the same experience. Went to update it with the pre-rooted img. Already had the boot menu etc. Did the update, rebooted and noticed I had no root (and no wifi it seems but I didn't check this in the settings).
Went to install the bueller-fixsusdcard.zip, rebooted to recovery and nothing, no logo, no LED. Plugged in via USB-A and like others I got a drive popped up.
Loaded up eMMC RAW 1.2.1.0 found online. I tried "writing" boot and recovery (boot.img from the pre-rooted rom, and recovery from CWM) and it made no difference. Not sure if I was doing it wrong or not though.
This is how I would do it:
Basically I would click browse below "write" and select the boot.img from my pre-rooted update.
I would then "read partition structure" and select only boot
Select the "boot" preset
Select "write"
I did this for both recovery & boot (with the correct selections). I restart and nothing is different. Where is the "aboot.img" file? I tried boot.img and boot_unlocked.img and no difference.
Any guidance would be great.
Tenny said:
Looks like I am in the same boat. Pretty much the same experience. Went to update it with the pre-rooted img. Already had the boot menu etc. Did the update, rebooted and noticed I had no root (and no wifi it seems but I didn't check this in the settings).
Went to install the bueller-fixsusdcard.zip, rebooted to recovery and nothing, no logo, no LED. Plugged in via USB-A and like others I got a drive popped up.
Loaded up eMMC RAW 1.2.1.0 found online. I tried "writing" boot and recovery (boot.img from the pre-rooted rom, and recovery from CWM) and it made no difference. Not sure if I was doing it wrong or not though.
This is how I would do it:
Basically I would click browse below "write" and select the boot.img from my pre-rooted update.
I would then "read partition structure" and select only boot
Select the "boot" preset
Select "write"
I did this for both recovery & boot (with the correct selections). I restart and nothing is different. Where is the "aboot.img" file? I tried boot.img and boot_unlocked.img and no difference.
Any guidance would be great.
Click to expand...
Click to collapse
Why would you need eMMC RAW 1.2.1.0? Are there any instructions you are following.? I have two of these broken ones?
In the same boat...
Hi all,
I'm in the same boat as the rest. I actually posted in Rbox's thread last night asking for help.
Like everyone, I had CWM, unlocked bootloader, bootmenu, prerooted roms.... after successful install of latest rom, could not load Home screen so I soft rebooted from the Settings menu.
After the reboot, bricked.
I don't have any Linux experience, and attaching to my Windows computer, I see the drive with a single folder.
I'll monitor here, but I think I'm SOL. So looking for a new android box. Ugh.
Thanks for any help.
~Eric
ericvangs14 said:
Hi all,
I'm in the same boat as the rest. I actually posted in Rbox's thread last night asking for help.
Like everyone, I had CWM, unlocked bootloader, bootmenu, prerooted roms.... after successful install of latest rom, could not load Home screen so I soft rebooted from the Settings menu.
After the reboot, bricked.
I don't have any Linux experience, and attaching to my Windows computer, I see the drive with a single folder.
I'll monitor here, but I think I'm SOL. So looking for a new android box. Ugh.
Thanks for any help.
~Eric
Click to expand...
Click to collapse
You should had asked questions before you did it, from what I understand from your post you installed last rooted OS5 image using CWM (OS3) without installing TWRP first even so tread specify the whole procedure on how to get there:
http://forum.xda-developers.com/fire-tv/development/prerooted-stock-images-t2882337
http://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286
bula1ca said:
You should had asked questions before you did it, from what I understand from your post you installed last rooted OS5 image using CWM (OS3) without installing TWRP first even so tread specify the whole procedure on how to get there:
http://forum.xda-developers.com/fire-tv/development/prerooted-stock-images-t2882337
http://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286
Click to expand...
Click to collapse
I think you're correct bula. the issue probably is for those many of us who used the guides on aftvnews.com, he doesn't mention twrp in the series of steps to perform the latest os update. i only had clockwork, not twrp.
many thanks to anyone who can provide assistance to those of us who are bricked.
~E
ericvangs14 said:
I think you're correct bula. the issue probably is for those many of us who used the guides on aftvnews.com, he doesn't mention twrp in the series of steps to perform the latest os update. i only had clockwork, not twrp.
many thanks to anyone who can provide assistance to those of us who are bricked.
~E
Click to expand...
Click to collapse
Point me to this link, please
bula1ca said:
Point me to this link, please
Click to expand...
Click to collapse
Hi Bula,
If you google "amazon Fire TV custom rom" first website you get is aftvnews. I believe I used his guild to root my ATV 2 years ago.
http://www.aftvnews.com/how-to-install-a-custom-rom-image-on-the-amazon-fire-tv/
He does list a good amount of procedures on the site.
CWM
http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/
Steps on how to install Rbox Boot Menu
http://www.aftvnews.com/how-to-install-a-kernel-boot-menu-on-the-amazon-fire-tv/
BusyBox, ADB, how to verify hash, ect...
I do not have TWRP on my box which seems probably the reason why it bricked following this guide.
~E
Fair enough but none of these posts mention anything regarding OS5, they are old posts that apply to OS3 only. I know this site very well ano you should had looked for latest guides on how to update to OS5 . Info was there.
http://www.aftvnews.com/how-to-install-twrp-custom-recovery-on-a-rooted-fire-tv-1/
My FireTV bricked and I had installed TWRP 3.0.0-7 and 5.2.1.1_r1 successfully. I was up and running for 15 minutes, installed Kodi via adb and took a quick break after receiving notification that the app installed successfully. I come back and notice that my WiFi is dropping out on the FireTV so I unplug the power to hard reset it. I plug the power back in and now I get no video or light.
I have two FireTV's, I followed the same process for both and the first one I updated is still working flawlessly. Not sure what happened to the 2nd one.
Please help. Killed my Firetv (AFTV1)
ericvangs14 said:
Hi all,
I'm in the same boat as the rest. I actually posted in Rbox's thread last night asking for help.
Like everyone, I had CWM, unlocked bootloader, bootmenu, prerooted roms.... after successful install of latest rom, could not load Home screen so I soft rebooted from the Settings menu.
After the reboot, bricked.
I don't have any Linux experience, and attaching to my Windows computer, I see the drive with a single folder.
I'll monitor here, but I think I'm SOL. So looking for a new android box. Ugh.
Thanks for any help.
~Eric
Click to expand...
Click to collapse
Hi, same problem here :crying:. I read the guides and bricked it by mistake. My aftv was rooted, fully unlocked and with CWM. I downloaded the needed pre-rooted roms and also TWRP. Yesterday I installed all the stuff following the guides, however, at the end my aftv stopped showing the colorful amazonfiretv logo animation. So I removed TWRP and installed CWM again, wanted to start from scratch. Probably I mixed-up the different rom files while renaming to rom.zip, I don't know, but it seems I pushed the newest via adp and installed it with CMW. The firetv was working and I saw the 5.2 was installed, damn! I knew about my mistake then.
After restart: NO BOOTING - NOT LOGO - NO WHITE LED :crying:.
So, same problem here, any idea how to bring it to life again?
Same here, installed latest rom (bueller-5.2.4.1-rooted_r1) with TWRP, was working fine until I tried Netflix, it didn't start up so I booted -> after that no white led, no power.....
Any update? It sounds like the efuse incident (wrong bootloader/ROM match up), but mine was not detected by PC using A-A cable. I'm sure the PC works with this AFTV and cable is good (used these to fastboot unbrick this ftv right before it went dead).