Looks like I bricked my fireTV Stick today.
What i did: After i updated to 5.2.1.0 I rooted with Kingo Root. I checked if everything was still running fine, which was the case.
Then i removed Kingo Root App and the superuser app that came with Kingo Root. I installed Chainfires latest supersu.apk which did not work (immediately crashed after start). Then i downloaded older version v1.97 of chainfires supersu. This version did not crash directly after starting it. It asked to update the su binary, which I accepted. Unfortunately it did not seem to work, that's why i rebooted the stick after some minutes.
Now it stucks at the "fireTV stick" logo.
Connection to adb works if i connect the Stick to my PC.
Is there anything i can try? Is there a way to factory reset via adb or anything like that?
Bierfreund said:
Looks like I bricked my fireTV Stick today.
What i did: After i updated to 5.2.1.0 I rooted with Kingo Root. I checked if everything was still running fine, which was the case.
Then i removed Kingo Root App and the superuser app that came with Kingo Root. I installed Chainfires latest supersu.apk which did not work (immediately crashed after start). Then i downloaded older version v1.97 of chainfires supersu. This version did not crash directly after starting it. It asked to update the su binary, which I accepted. Unfortunately it did not seem to work, that's why i rebooted the stick after some minutes.
Now it stucks at the "fireTV stick" logo.
Connection to adb works if i connect the Stick to my PC.
Is there anything i can try? Is there a way to factory reset via adb or anything like that?
Click to expand...
Click to collapse
Connect your fire stick to a windows pc/laptop. (i used windows 10 64bit)
Let the drivers install.
Download the windows version of Kingo root.
Click root, try this a couple of times (it probably will fail and stick at 70 percent)
unplug the stick and try again, when it hits 70 percent again plug your hdmi lead in (already connected to tv)
It should root and write back the correct su files.
If you want to unroot, install kingo and super user again on the fire stick then either use the unroot feature in super user app (you will have to purchase mouse toggle for fire tv, if you havent got it already to navigate to the 3 little dots menu icon top right corner)
Or re plug it into windows pc/laptop and unroot through the windows tool.
Worked! Did not know, that there's also an windows application for Kingo root.
So it's better to not use another superuser app when rooting the fireTV (stick) with Kingo root?
Thanks sconnyuk. I have a bricked Stick from the Feb. KingRoot -> SuperSUMe disaster. Tried a lot of things, no luck.
But the Windows KingoRoot worked on the first try. (No 70% stoppage or anything.) I now have a root shell over adb. I'm going to wait on a rooted ROM to get it back to a normal state, but at least now I have hope.
Bierfreund said:
Worked! Did not know, that there's also an windows application for Kingo root.
So it's better to not use another superuser app when rooting the fireTV (stick) with Kingo root?
Click to expand...
Click to collapse
Just use Kingo roots superuser. Im going to try a few different su versions later see if I have any luck.
At the moment any other than kingoroots will brick, (caun unbrick if in this situation so I guess anyome can try)
---------- Post added at 05:53 PM ---------- Previous post was at 05:52 PM ----------
ftgftg said:
Thanks sconnyuk. I have a bricked Stick from the Feb. KingRoot -> SuperSUMe disaster. Tried a lot of things, no luck.
But the Windows KingoRoot worked on the first try. (No 70% stoppage or anything.) I now have a root shell over adb. I'm going to wait on a rooted ROM to get it back to a normal state, but at least now I have hope.
Click to expand...
Click to collapse
No need to wait. Try this guide ive put together, just do it over usb. Cant see why I wouldnt work.
http://forum.xda-developers.com/fire-tv/development/fire-tv-stick-downgrade-firestarter-3-2-t3399298
sconnyuk said:
Connect your fire stick to a windows pc/laptop. (i used windows 10 64bit)
Let the drivers install.
Download the windows version of Kingo root.
Click root, try this a couple of times (it probably will fail and stick at 70 percent)
unplug the stick and try again, when it hits 70 percent again plug your hdmi lead in (already connected to tv)
It should root and write back the correct su files.
If you want to unroot, install kingo and super user again on the fire stick then either use the unroot feature in super user app (you will have to purchase mouse toggle for fire tv, if you havent got it already to navigate to the 3 little dots menu icon top right corner)
Or re plug it into windows pc/laptop and unroot through the windows tool.
Click to expand...
Click to collapse
Thanks for the tutorial. But it doesn't work for me. I have and old fire stick TV with 5.0.5 that I bricked with KingRoot (not Kingo) -> SuperSUMe. I tried to follow your steps and KingoRoot goes to 100% at the first time. But when I connect the stick to my PC it's still stucks at the FireTV Logo . I don't know if I followed some step wrong.
PS: Sorry for my bad english.
SrTommy said:
Thanks for the tutorial. But it doesn't work for me. I have and old fire stick TV with 5.0.5 that I bricked with KingRoot (not Kingo) -> SuperSUMe. I tried to follow your steps and KingoRoot goes to 100% at the first time. But when I connect the stick to my PC it's still stucks at the FireTV Logo . I don't know if I followed some step wrong.
PS: Sorry for my bad english.
Click to expand...
Click to collapse
Try multiple times with Kingoroot, You can try windows version of KING root multiple times also.
Failing this you can try to run both programs simultaneously.
Good luck
sconnyuk said:
Try multiple times with Kingoroot, You can try windows version of KING root multiple times also.
Failing this you can try to run both programs simultaneously.
Good luck
Click to expand...
Click to collapse
It finally works!!!...... almost
Now the sticks pass the fire tv logo, but takes a lot of time to open the firestarter menu. And I can't do anything there. The remote doesn't response. I try to do a factory reset to the stick but I can't find the way . Thank you anyway. At least I can escape from the loop at boot.
SrTommy said:
It finally works!!!...... almost
Now the sticks pass the fire tv logo, but takes a lot of time to open the firestarter menu. And I can't do anything there. The remote doesn't response. I try to do a factory reset to the stick but I can't find the way . Thank you anyway. At least I can escape from the loop at boot.
Click to expand...
Click to collapse
Try removing the batteries and re-pairing the remote, try this multiple times as it has happened to me before.
sconnyuk said:
Try removing the batteries and re-pairing the remote, try this multiple times as it has happened to me before.
Click to expand...
Click to collapse
I thought that I had edited my previous post but it seems that it didn't save the changes. Finally I could restore my fire stick following your downgrade guide. I reinstalled the firmware 5.0.5 and everything works perfect. Thanks a million!!!
SrTommy said:
I thought that I had edited my previous post but it seems that it didn't save the changes. Finally I could restore my fire stick following your downgrade guide. I reinstalled the firmware 5.0.5 and everything works perfect. Thanks a million!!!
Click to expand...
Click to collapse
Your welcome.
Glad I could help.
Hi,
I tried to install XPosed to be able to install Google Play store later following a guide I successfully used on my rooted FTV 1st gen.
XPosed installation went fine but probably I deleted some user file I had not and box started checking for updates. I stopped the process in the meantime. Nothing seems to be affected. Root is still in place and firmware version is still 5.0.5. BUT each time a reboot my stick now it asks to pair my remote, then asks me to choose a language as it wants to complete an update. Just when I goes further it says that it has not been possibile to complete update. I tried to "downgrade" with a clear 5.0.5 firmware zip. It went fine but I had to disable OTA again to avoid the online updates. So it still fails to check for updates and each time it tries to reinitialize update process. basically default amazon launcher doesnt work anymore but it's not a issue cause I have Firestarter 3.3 which works fine. The worst issue is that each time I reboot it asks for rempote pairing and I can't use amazon video anymore. Basically I'd like to remove this "checking for update" process and return to my actual rom. Is that possibile?
Thanks.
puppinoo.
Hoping someone can help me out. My stick is bricked. I loaded up the Kingoroot and tried to run the steps to recover it. However i dont think it's recognize the device since kingoroot is stuck at the loading page. Which driver files did you install for the fire stick? thanks.
Bricked fire stick- any advice
I tried to transfer a ustv4.0 APK zip file to the firestick via USB after some extensive instructions on YouTube video but found that using Google Drive with ES File Explorer would be the quick and easy method. I also got lost in the instructions after downloading ADB and fire starter. When plugging the firestick back into the TV to go the ES file route, the firestick doesn't even show up on the TV now- the HDMI port that I had used would display 'fire stick' and display the HDMI port #, now nothing shows up and then the screen times out quickly as if nothing is plugged in. When I first plugged in the firestick to my windows 10 laptop, I checked the drives and it didn't show up although I could hear a USB connection chime as if something just was connected and if I disconnected it, it had a disconnect chime as well. I did see in device manager before unplugging it that it had shown up as 'unknown device' towards the bottom land labeled as AFTM. Can anyone tell me what they think may have gone wrong and why it no longer shows up on the TV or why it's now not starting up for that matter? Any help would be appreciated.
tjmethod said:
I tried to transfer a ustv4.0 APK zip file to the firestick via USB after some extensive instructions on YouTube video but found that using Google Drive with ES File Explorer would be the quick and easy method. I also got lost in the instructions after downloading ADB and fire starter. When plugging the firestick back into the TV to go the ES file route, the firestick doesn't even show up on the TV now- the HDMI port that I had used would display 'fire stick' and display the HDMI port #, now nothing shows up and then the screen times out quickly as if nothing is plugged in. When I first plugged in the firestick to my windows 10 laptop, I checked the drives and it didn't show up although I could hear a USB connection chime as if something just was connected and if I disconnected it, it had a disconnect chime as well. I did see in device manager before unplugging it that it had shown up as 'unknown device' towards the bottom land labeled as AFTM. Can anyone tell me what they think may have gone wrong and why it no longer shows up on the TV or why it's now not starting up for that matter? Any help would be appreciated.
Click to expand...
Click to collapse
Hi did you find a solution. I have the same problem.
Thx
Related
1) Yes I checked search results.
2) Yes I've googled.
3) Yes I've tried the Kindle Fire Utility, the http://forum.xda-developers.com/showthread.php?t=1356257... links options.
With that being said, here's my issue;
Got a KF a couple days ago...
Yesterday, followed some online instructions to put GO Launcher EX on there to replace the carousel deal.
Followed instructions to the T.
Restarted. Got to "Choose your OS" screen (or whatever it precisely says...)
Picked GO... then it froze.
Now, when it restarts (yes, its the 30 second hard restart), it gets stuck on the Kindle Fire splash screen.
I have tried the above utilities.
I have hard restarted.
I have fully charged and ran the battery dry and tried again.
When I use the utilities, the problem is, my PC will not recognize the Kindle (it see's it as a removable storage device, but it doesn't click over to 'Kindle', and thus the utilities can't interact with the device itself, I suppose).
I've tried different USB ports and connecters (I have 2 regular kindles in the house, too). But I know all the peripherals work through cross-testing.
Essentially, what else can I do? (I got it from WalMart, and they're currently out of stock, so I can't return it till next week, but I'd like it fixed before then if possible)
I've tried several different methods from these forums too, but I *always* hit the same snag... whenever any utility is 'waiting for device', it simply will not find it, because the PC doesn't see it properly. It sees *something* (removable storage) but not as a kindle, and thus won't allow the utilities to interface with it.
Are there any physical things I can do to hard reset it without destroying any warrantys?
Any help appreciated!
there is no need to return it
from what you say i think you have a bad launcher on it and the kf tries to start it but can't
first i need to know if you have fff (custom bootloader - yellow triangle) on it ?
then do you have a recovery (twrp) on it ?
what os/bit of computer ?
In kindle utility go to bootmodes and enter normal (4000). Just had that problem last night.
awidawad - I've tried that. It stays on 'waiting for device' forever. Please explain step by step what you did? At which point did you power on the KF, when did you run KFU, etc, etc.
b63 - I hope your right!
no - I do not have the yellow triangle.
no - I do not have TWRP on it, i have tried, but cannot get anything onto the kindle.
my PC is window7, 64bit
Euryon said:
awidawad - I've tried that. It stays on 'waiting for device' forever. Please explain step by step what you did? At which point did you power on the KF, when did you run KFU, etc, etc.
Click to expand...
Click to collapse
Do you have all the kf drivers installed on your computer? I know that when I unbricked mine I had all the drivers installed but I had to reinstall them for some reason. If you do not have them I can post them later on tonight when I'm at home. However, I have TWRP installed on mine, and Cyanogenmod 7.2, so hopefully yours is able to connect to your computer.
---------- Post added at 12:56 PM ---------- Previous post was at 12:50 PM ----------
b63 said:
there is no need to return it
from what you say i think you have a bad launcher on it and the kf tries to start it but can't
Click to expand...
Click to collapse
In order to remove the bad launcher, you need to have your device connected to your computer to remove it using adb.
ok so b63 helped me out big time here....
about 2 hours ago we got on a teamviewer session (download this if you want these guys to help you with serious issues!)
took me a minute to figure out how to allow him/her proper access to my screen
anyway
i don't understand the technical stuff
but
what i had done wrong is that i didnt root the KF before trying to install the GO... software (i think)
b63 had a heck of a time trying to discern the problem with me being about as useful as a dead fish, but get there he/she did
after much fanangaling, b63 managed to install the TWRP and ADP on my KF, allowing it to fastboot, and basically allowing it to be read by my PC, and so fixed.
im sure it would have taken b63 all of 5 minutes in real time, but using the quirky teamview and my slow net speed didn't help
still, thanks VERY MUCH to b63 for fixing the **** out of my KF, and being very helpful and patient all along!
thanks
Just wanted to drop b63 a note here that I "thanks"ed their post above - not necessarily for the post but for going above and beyond. The people on these forums are (for the most part) really great. (Too bad there have to be a few who are demanding of the developers to get this feature or that fix done faster without taking into account that the devs do this all in their free time.)
YES, search finally led me here!
Euryon, I have the exact same thing happening with my KF right now.
Do you remember any specifics of how b63 carried out the steps you listed?
b63, any chance you could help me with mine? My issue is identical with Euryon's down to the letter.
Same Problem
Could someone please help me i have the same problem
same problem here! please can someone give a step by step? My fire is unrooted and I did nothing to it except try to install the go launcher and after I selected it as the default launcher it got stuck at the kindke fire logo.
I tried the Kindle unbricking utility but it cannot find the device even after I installed the adb composite interface
also, my fire is not showing up as a kindle - it is showing up as an android device.
rollno88 said:
also, my fire is not showing up as a kindle - it is showing up as an android device.
Click to expand...
Click to collapse
Have you added the fires usb ID to your system?
Sent from my Amazon Kindle Fire using Tapatalk 2
thanks for replying, and I have no clue how to do that. I'll search and get back .
---------- Post added at 10:12 AM ---------- Previous post was at 09:57 AM ----------
okay, I already did that by editing the android sdk(as a prerequisite to rooting, which I planned to do eventually) - so when I connect my fire it first shows up as a kindle, and after updating the software through windows and installing drivers through KFU, it comes up as an android device and the interface is adb composite. Now if I try to install TWRP through KFU it keeps switching between adb composite interface and plain adb. And both KFU and KUFU keep waiting but are unable to find my device.
also, my fire alternately shows up as a usb composite device and an android device. PLEASE help
okay I solved it with KFU (finally!) although I have no clue how I did it as I didn'tdo anything I hadn't tried earlier so, managed to install TWRP and then wiped everything and finally my fire could be read - then I deleted go launcher and now my fire is back from the grave
A big thank you to all the helpful posts at this forum - u guys are the best
Same issue
Tried rooting my KF, but couldn't change permissions and thus could not install android market. Superuser didn't do anything other than show me a log folder that had no logs. Tried to change permissions on /system and /apps with one of the file management apps on amazon and it said the device *wasn't* rooted, despite GO launcher and android interface.
Did a factory wipe to try to reroot or fully(?) root the KF, and that's when it all went wrong. Got stuck on boot loop, but KFU helped me break out of that. Now it's stuck on the Kindle Fire splash screen with no animation. I read somewhere that this was the fastboot getting "stuck."
At any rate, i have TWRP 2.0 installed and can mount and unmount the device in its interface, but it is only recognized as ADB android device, or when mounted via TWRP, USB composite device. As such, ADB commands only work occasionally - all other times it simply says <waiting for device>.
I am running Windows 7 64 bit, and 6.3 on the KF. All restarts on the KF are hard restarts, except occasionally cmd lets me fastboot reboot.
I have spent the past 2 days trying everything I have found online (2 KF unbrick applets, 15+ tabbed browsers with different threads) to no avail. I am finally posting, pleading for assistance.
Thanks in advance for any (helpful) replies. Real thanks clicking afterwards.
edit: when rerunning KFU, i kept getting the message that many execs failed because "/system/bin/sh" directory does not exist.
I don't know if that helps narrow down what might be happening, but I saw that coming up a lot in the cmd prompt.
zeissbickham said:
Tried rooting my KF, but couldn't change permissions and thus could not install android market. Superuser didn't do anything other than show me a log folder that had no logs. Tried to change permissions on /system and /apps with one of the file management apps on amazon and it said the device *wasn't* rooted, despite GO launcher and android interface.
Did a factory wipe to try to reroot or fully(?) root the KF, and that's when it all went wrong. Got stuck on boot loop, but KFU helped me break out of that. Now it's stuck on the Kindle Fire splash screen with no animation. I read somewhere that this was the fastboot getting "stuck."
At any rate, i have TWRP 2.0 installed and can mount and unmount the device in its interface, but it is only recognized as ADB android device, or when mounted via TWRP, USB composite device. As such, ADB commands only work occasionally - all other times it simply says <waiting for device>.
I am running Windows 7 64 bit, and 6.3 on the KF. All restarts on the KF are hard restarts, except occasionally cmd lets me fastboot reboot.
I have spent the past 2 days trying everything I have found online (2 KF unbrick applets, 15+ tabbed browsers with different threads) to no avail. I am finally posting, pleading for assistance.
Thanks in advance for any (helpful) replies. Real thanks clicking afterwards.
Click to expand...
Click to collapse
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with an emphasis on post #2. You need to know what mode your device is in by looking at the device manager and make sure your drivers are loading correctly for that mode. If you can get to TWRP, you can mount your USB mass storage device, copy a new zip file of either the stock software or a custom ROM and flash it.
Thank you. I will be trying this shortly.
fully bricked
I followed the guide and got to a point where the Kindle Fire animation was playing. It loaded up to the unlock screen and then automatically shut itself down - would not stay on when either connected or disconnected. Tried installing a ROM but still shut down. Started the recovery and hit factory reset, still auto shutdown. Tried clearing a partition as described in the tutorial and now it's fully bricked. Will not turn on when connected to computer, to outlet, to another cable.
Thanks for trying to help.
Alright So i rooted my fire tv stick v5.0.5, with kingroot 4.82, everything was working perfect, i blocked ota updates, and i froze the fireTV Home, and used firestarter. I rebooted the fire tv and it rebooted perfect, still had root, everything was great! I wanted to connect my playstation controller to it, but i couldnt access the fire tv settings because i froze the fire tv home and the built in settings is part of the fire tv home, i tried to install regular settings.apk, i tried several different ones but it would just fail installing, i thought my regular settings was interfering with it, so i backed it up and froze the fire tv settings just to try to install regular android settings afterward, and i rebooted the stick. Now my stick is stuck at the fire stick logo and wont boot, im sure its because i froze the settings, since it booted fine with root before i froze that, and that was the only change i did. Anyone got any ideas on how i can fix it?
Any help is greatly appreciated!
Thanks,
Deershoot3r
I had the same issue with the FireTv Stick but another os.
I had a hardware rooted FireTv-Stick on Software: 54.1.1.0_user_110031420. That means FireOS 3, not FireOS 5.
Yesterday I let the stick push some file with ES-File-Explorer to my NAS. In this process the system restart (I think because to much power consumption and less powerfull usb port yesterday).
Now it does not start anymore. @deershoot3r
Perhaps we had a chance to get our sticks back by flashing a stock-rom from amazon.
Once I read something about fastboot and recovery possibilities.
At first you should load your stock-rom from here: http://www.aftvnews.com/software/
Perhaps we can connect a usb cable and start fastboot, see here: http://forum.xda-developers.com/showpost.php?p=57308281&postcount=6
Greetings by I_did_it_just_tmrrow
I_did_it_just_tmrrow said:
I had the same issue with the FireTv Stick but another os.
I had a hardware rooted FireTv-Stick on Software: 54.1.1.0_user_110031420. That means FireOS 3, not FireOS 5.
Yesterday I let the stick push some file with ES-File-Explorer to my NAS. In this process the system restart (I think because to much power consumption and less powerfull usb port yesterday).
Now it does not start anymore. @deershoot3r
Perhaps we had a chance to get our sticks back by flashing a stock-rom from amazon.
Once I read something about fastboot and recovery possibilities.
At first you should load your stock-rom from here: http://www.aftvnews.com/software/
Perhaps we can connect a usb cable and start fastboot, see here: http://forum.xda-developers.com/showpost.php?p=57308281&postcount=6
Greetings by I_did_it_just_tmrrow
Click to expand...
Click to collapse
Actually i tried this, i cannot connect to it through fastboot, because the fire tv will not get past the "FireTv Stick" logo, any suggestions? am i doing something wrong?
deershoot3r said:
Actually i tried this, i cannot connect to it through fastboot, because the fire tv will not get past the "FireTv Stick" logo, any suggestions? am i doing something wrong?
Click to expand...
Click to collapse
fastboot kicks in as soon as you power off your unit, if you get to the amazon logo it is already too late however fastboot will not work for you anyway as your firestick boot loader is locked.
Please push my amazon community topic:
https://www.amazon.com/forum/fire/r...orum=Fx2L8EBNTOXFSA7&cdThread=Tx2LHG0S7L0Y9MK
Perhaps amazon help us and provide a solution!
But I need you guys!
Greetings by Idijt
Edit:
By the way, here is a thread in the Amazon developer Account, asking for a way to unbrick devices in an officially way:
https://forums.developer.amazon.com/forums/thread.jspa?threadID=11981&tstart=0
We should Support it by pushing this thread.
Greetings by Idijt
Hi there
I have an Amazon Fire TV 2 (4K) which I have rooted with rbox's pre-rooted ROM with custom recovery etc. All has been going well and I have been working on perfecting my Kodi install when this morning I snagged the power cord and the Fire TV fell about two foot off my sofa on to my carpeted floor. I honestly didn't think there would be a problem, but the unit restarted and got stuck on the white Amazon logo.
I left the unit completely unplugged for an hour and tried again, but it was still stuck on the white Amazon logo. I still have recovery so I immediately backed up my system in full onto my microSD card, then tried wiping just the cache (to make my life easier if this worked). The process seemed to work except for a message in red which said "unable to locate boot partition", but sadly when I rebooted I was still stuck on the white Amazon logo. I then tried a full factory reset, which ran without error, but still left me stuck on the Amazon logo. I then flashed the pre-rooted ROM (sloane-5.0.5-rooted_r4), which also seemed to work, but still resulted in me being stuck on the white Amazon logo.
Is it possible that some small part of the machine broke in that short, fairly soft fall? Or is there something else I can try via TWRP?
If the hardware is at fault, I would prefer not to return it to Amazon rooted and with the stock firmware installed, so would I be able to wipe it 100% if necessary. I do hope it doesn't come to that, but if anyone has any ideas, I would be very (very) grateful.
Peter
In the last sentence I meant to say, "I would prefer not to return it to Amazon rooted and with the custom recovery installed..." Just in case that was confusing. Still keen to find an answer if anyone can help!
Left the Fire TV unplugged all night. No difference today. Looks like I'll have to return it to Amazon with the glaringly obvious recovery mode staring them in the face when they come to test it out. I just hope they don't balk on issuing a replacement. It would have been nice to be able to try out a few more methods before giving in, but I see my post has not rung a bell with anyone.
Now that you've flashed a pre-rooted rom over your old one, can you unplug everything (including sd card, hdmi cable, power, ethernet) and leave them unplugged for an hour or so, then try again?
Thank you for your response. I shall certainly give that a shot and report back afterwards.
Hello again. I left my Fire TV completely unhooked from all peripherals for well over an hour, but still stuck on gruesome white logo. For good measure, I tried reinstalling my backup. Ran without issue, but still stuck on logo. Then reflashing pre-rooted ROM, but again stuck on logo.
Is it possible that a tiny memory module of some kind was dislodged in the fall? It seems so strange that it still powers on and I can still reinstall from SD card etc.
I would much prefer to exhaust all options if possible. Unless there is a foolproof way to confirm hardware failure.
pfhastie said:
Hello again. I left my Fire TV completely unhooked from all peripherals for well over an hour, but still stuck on gruesome white logo. For good measure, I tried reinstalling my backup. Ran without issue, but still stuck on logo. Then reflashing pre-rooted ROM, but again stuck on logo.
Is it possible that a tiny memory module of some kind was dislodged in the fall? It seems so strange that it still powers on and I can still reinstall from SD card etc.
I would much prefer to exhaust all options if possible. Unless there is a foolproof way to confirm hardware failure.
Click to expand...
Click to collapse
Anyone have any further thoughts?
pfhastie said:
Anyone have any further thoughts?
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349
Thank you, sir. I'll be honest I came across that article on my travels in search of an answer, but assumed it was for people who didn't have recovery. I shall certainly give it a shot and let you know my results.
Good morning. I was too tired to try this out last night.
Having read through the entire FireTV 2 Unbrick Image thread it is not 100% clear exactly what steps I should take to run the process. Once I unzip all the files do I simply drop them all in the root folder on my SD card (in the Fire TV)? And do I then attach the Fire TV to my Windows PC via USB?
Lastly, if I already have recovery, do I really need to go through this process, which may very well lead to further issues, only to get me back to square one and the recovery I already have?
I'm so sorry to have to pester people about this, but without your help I would be lost.
OK, my brain is waking up. As far as the files go, I just put the unbrick.img on my SD card, then run the remaining files on my Windows PC and connect my Fire TV via A-A USB cable. OK, I can do that.
But does it all just lead to the same recovery?
pfhastie said:
Good morning. I was too tired to try this out last night.
Having read through the entire FireTV 2 Unbrick Image thread it is not 100% clear exactly what steps I should take to run the process. Once I unzip all the files do I simply drop them all in the root folder on my SD card (in the Fire TV)? And do I then attach the Fire TV to my Windows PC via USB?
Lastly, if I already have recovery, do I really need to go through this process, which may very well lead to further issues, only to get me back to square one and the recovery I already have?
I'm so sorry to have to pester people about this, but without your help I would be lost.
Click to expand...
Click to collapse
Read step 2 here (http://www.aftvnews.com/how-to-root-the-amazon-fire-tv-2/) to prepare your computer/laptop and firetv unit then download the following:
•FireTV 2 Recovery Installer
•FireTV 2 Recovery
•Unbrick Images (md5sum: 5e774497b3bad5c47d1c744410f6db12)
Extract all 3 zip files to the same directory. Follow link: http://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349
---------- Post added at 11:22 AM ---------- Previous post was at 11:19 AM ----------
pfhastie said:
OK, my brain is waking up. As far as the files go, I just put the unbrick.img on my SD card, then run the remaining files on my Windows PC and connect my Fire TV via A-A USB cable. OK, I can do that.
But does it all just lead to the same recovery?
Click to expand...
Click to collapse
READ POST: "Extract all 3 zip files to the same directory." and yes it will
I truly appreciate your help.
OK, so I have placed the file "ramdisk-recovery.cpio.lzma" on the microSD Card and returned the microSD card to the Fire TV. I ran "unbrick_firetv2.bat" on Windows, then connected my Fire TV to my PC via A-A USB cable. Windows recognised that there was a device, but did not successfully load any drivers ("Device driver was not successfully installed - MT65xx Preloader - Device Unplugged") and the Command Window in Windows simply states "Waiting for preloader" and nothing else happens.
I already have ADB drivers on my machine which was working with my Fire TV before the problem began (15 Seconds ADB Installer 1.4.2), so how can I get my Fire TV to communicate with my Windows PC in order to initiate the process? Or is the trouble I am having indicative of a hardware problem?
I await any and all input.
pfhastie said:
Good morning. I was too tired to try this out last night.
Having read through the entire FireTV 2 Unbrick Image thread it is not 100% clear exactly what steps I should take to run the process. Once I unzip all the files do I simply drop them all in the root folder on my SD card (in the Fire TV)? And do I then attach the Fire TV to my Windows PC via USB?
Lastly, if I already have recovery, do I really need to go through this process, which may very well lead to further issues, only to get me back to square one and the recovery I already have?
I'm so sorry to have to pester people about this, but without your help I would be lost.
Click to expand...
Click to collapse
1) create a folder on your desktop
2) unzip all three files in this new created folder
3) connect your firetv through an A-A cable without power cord connected
4) Run unbrick_firetv2.bat for Windows or unbrick_firetv2.sh for Linux or OSX
5) power on your firetv unit
6) let the process run
Note: you need to install the proper drivers before you do any of above steps. Follow step 2 in this link: http://www.aftvnews.com/how-to-root-the-amazon-fire-tv-2/
Hello again. I did all the steps outlined above. The main factor I was missing was installing the MTK65XX Preloader USB VCom drivers.
This proved to be the usual despairing pain, but I got there in the end, installed the unbrick image, then reconnected the Fire TV and booted into recovery without issue. I then flashed the pre-rooted ROM without issue, but - so very sadly - I am still still stuck on the white Amazon logo.
Can I safely assume now that my unit is simply broken? If so, how can I delete all signs of the recovery and root, so I might say to Amazon it didn't start after a factory refresh?
pfhastie said:
Hello again. I did all the steps outlined above. The main factor I was missing was installing the MTK65XX Preloader USB VCom drivers.
This proved to be the usual despairing pain, but I got there in the end, installed the unbrick image, then reconnected the Fire TV and booted into recovery without issue. I then flashed the pre-rooted ROM without issue, but - so very sadly - I am still still stuck on the white Amazon logo.
Can I safely assume now that my unit is simply broken? If so, how can I delete all signs of the recovery and root, so I might say to Amazon it didn't start after a factory refresh?
Click to expand...
Click to collapse
Have you used unbrick.img or unbrick+ramdisk.img? BTW what version of prerooted img did you use? Maybe that is the cause, could be corrupted.
I used "unbrick.img" because I have a microSD card and it took half an hour as opposed to two. The pre-rooted image I used was "sloane-5.0.5-rooted_r4", which I have had in a folder on my PC for over a month and have used successfully several times before so I don't think that is the issue.
If there are no other options, I think it's time to get a replacement, but how do I wipe recovery and root so I don't have to explain myself to Amazon?
pfhastie said:
I used "unbrick.img" because I have a microSD card and it took half an hour as opposed to two. The pre-rooted image I used was "sloane-5.0.5-rooted_r4", which I have had in a folder on my PC for over a month and have used successfully several times before so I don't think that is the issue.
If there are no other options, I think it's time to get a replacement, but how do I wipe recovery and root so I don't have to explain myself to Amazon?
Click to expand...
Click to collapse
Try the long way.......it is just two hours.
bula1ca said:
Try the long way.......it is just two hours.
Click to expand...
Click to collapse
I do appreciate you trying to help, but this all so tricky and time-consuming. I already had recovery, I then installed recovery again with the unboot image. What difference could installing recovery the slowest way make?
OK, I am trying the long way now. I suppose I said I wanted to exhaust the possibilities.
Ok. I've scoured the internet trying to find a solution to my issue and so far I've come up empty handed. Here's my issue:
- I bought this FTV1 on Craigslist knowing it was softbricked. I have no idea if it was unlocked or rooted or had any custom recovery installed.
- I do not have the remote as the owner wanted to keep it as a spare (I use my phone as a remote anyways).
- I've tried using the ALT+PRNT SCRN+I keys (I'm not sure I'm hitting them at the correct times) and have had no luck getting to the recovery screen.
- I ordered a USB cable to try fastboot and I had no luck there as well.
The only success I've seen is when connected to my computer via USB my computer recognizes the FTV1 via ADB. I can use ADB to reboot recovery but I only get to this screen (not my picture) and can't get anywhere from here.
Can anyone suggest something I haven't tried? Is there anyway to crack this thing open and somehow do a factory reset/stock flash? Any info would be appreciated!
Thanks in advance!
Try the PC version of Kingoroot, if the device has a rootable version of firmware you can unbrick it with Kingoroot.
Read the paragraph right after step 10 in this post:
https://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
I can confirm, it does work.
2WhlWzrd said:
Try the PC version of Kingoroot, if the device has a rootable version of firmware you can unbrick it with Kingoroot.
Read the paragraph right after step 10 in this post:
https://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
I can confirm, it does work.
Click to expand...
Click to collapse
Thanks! I'll be trying this asap!
Well, I was able to try this tonight and unfortunately it didn't work. After a few minutes I'd eventually get a "Root Fail" message on KingoRoot. It did look positive for a few minutes though!
Any other suggestions? Or am I just out the $15 I have in this thing? Like I said, I knew it was a risk when I bought it but I figured it was worth it for $15.
Thanks for any suggestions provided!
cabraswell said:
Well, I was able to try this tonight and unfortunately it didn't work. After a few minutes I'd eventually get a "Root Fail" message on KingoRoot. It did look positive for a few minutes though!
Any other suggestions? Or am I just out the $15 I have in this thing? Like I said, I knew it was a risk when I bought it but I figured it was worth it for $15.
Thanks for any suggestions provided!
Click to expand...
Click to collapse
Use adbLink to connect to the device and open "Uninstall APK" from the console, and look for APKs with instances of "king" in the name. If you see kingroot or kinguser those are related to Kingroot, not to be confused with Kingoroot. Sorry, I don't remember off hand what the one related to Kingoroot was called, other than it had "king" in the name. But if it was present on the device and "Root Failed", I uninstalled it and tried again, and the next time I would get "Root Successful".
Also, at the top of the console there is a "Reboot" feature which allows you to reboot into recovery that may be useful.
cabraswell said:
Ok. I've scoured the internet trying to find a solution to my issue and so far I've come up empty handed. Here's my issue:
- I bought this FTV1 on Craigslist knowing it was softbricked. I have no idea if it was unlocked or rooted or had any custom recovery installed.
- I do not have the remote as the owner wanted to keep it as a spare (I use my phone as a remote anyways).
- I've tried using the ALT+PRNT SCRN+I keys (I'm not sure I'm hitting them at the correct times) and have had no luck getting to the recovery screen.
- I ordered a USB cable to try fastboot and I had no luck there as well.
The only success I've seen is when connected to my computer via USB my computer recognizes the FTV1 via ADB. I can use ADB to reboot recovery but I only get to this screen (not my picture) and can't get anywhere from here.
Can anyone suggest something I haven't tried? Is there anyway to crack this thing open and somehow do a factory reset/stock flash? Any info would be appreciated!
Thanks in advance!
Click to expand...
Click to collapse
Have you tried the windows version of KingoRoot Aswell?
I never got alot of luck with King Root but KingoRoot worked quite a few times for me.
If you manage to get root, even if you can't boot it fully up you will be able to recover.
sconnyuk said:
Have you tried the windows version of KingoRoot Aswell?
I never got alot of luck with King Root but KingoRoot worked quite a few times for me.
If you manage to get root, even if you can't boot it fully up you will be able to recover.
Click to expand...
Click to collapse
I did try KingoRoot (for Windows) and kept getting "Root Fail"
Gonna try adblink as suggested by 2WhlWzrd when I get home tonight. Hoping that works. Would love to get this thing working!
Some more information that will help move things along.
First, after getting adbLink installed and connected. Open "ADB Shell" from the console and run:
Code:
getprop ro.build.version.fireos
This will tell us what version of firmware the device has, and whether or not it is even rootable.
If it is, and happens to have been rooted with Kingoroot, the APK that I mentioned uninstalling before will be listed as "com.kingouser.com".
And if it's not rootable then getting in to recovery is going to be your best bet.
Good Luck!
2WhlWzrd said:
Some more information that will help move things along.
First, after getting adbLink installed and connected. Open "ADB Shell" from the console and run:
Code:
getprop
This will tell us what version of firmware the device has, and whether or not it is even rootable.
If it is, and happens to have been rooted with Kingoroot, the APK that I mentioned uninstalling before will be listed as "com.kingouser.com".
And if it's not rootable then getting in to recovery is going to be your best bet.
Good Luck!
Click to expand...
Click to collapse
Thanks again. I look forward to trying these steps tonight!
cabraswell said:
Thanks again. I look forward to trying these steps tonight!
Click to expand...
Click to collapse
Edited the code, just "getprop" gives alot of info, we're looking for something specific.
2WhlWzrd said:
Edited the code, just "getprop" gives alot of info, we're looking for something specific.
Click to expand...
Click to collapse
Software version 5.2.1.0 not rootable by software means (from what I can find).
Getting error "Could not access Package Manager" when I click Uninstall APK in adbLink.
cabraswell said:
Software version 5.2.1.0 not rootable by software means (from what I can find).
Click to expand...
Click to collapse
Correct. Looks like Recovery is the only option.
2WhlWzrd said:
Correct. Looks like Recovery is the only option.
Click to expand...
Click to collapse
The trouble is I can't get into recovery. I've tried a couple different keyboards even. I am starting to think I'm hosed =/
cabraswell said:
The trouble is I can't get into recovery. I've tried a couple different keyboards even. I am starting to think I'm hosed =/
Click to expand...
Click to collapse
Did you try the "Reboot Recovery" option from the "Reboot" menu at the top of adbLink console?
2WhlWzrd said:
Did you try the "Reboot Recovery" option from the "Reboot" menu at the top of adbLink console?
Click to expand...
Click to collapse
Yup. Same result as using adb reboot-recovery
cabraswell said:
Yup. Same result as using adb reboot-recovery
Click to expand...
Click to collapse
i think i went through quite similar ordeal few weeks back. can you try 'fastboot devices' command to see if firetv shows up with usb cable you ordered.
also, if it doesn't show up, make sure you try few combinations as below
- 1. make sure firetv is off and you don't have command prompt window running
2. turn on firetv, wait couple seconds and turn on command prompt but make sure you run as admin( i had to do this due to work laptop)
3. try fastboot devices, if it won't show up then keep take usb cable out from either of the side, restart fire tv and hook usb back quickly...
4. play around with combination of #3 above...
YoColdRain said:
i think i went through quite similar ordeal few weeks back. can you try 'fastboot devices' command to see if firetv shows up with usb cable you ordered.
also, if it doesn't show up, make sure you try few combinations as below
- 1. make sure firetv is off and you don't have command prompt window running
2. turn on firetv, wait couple seconds and turn on command prompt but make sure you run as admin( i had to do this due to work laptop)
3. try fastboot devices, if it won't show up then keep take usb cable out from either of the side, restart fire tv and hook usb back quickly...
4. play around with combination of #3 above...
Click to expand...
Click to collapse
So far I haven't had any luck getting fastboot to recognize it but I'll give this a try tonight. Thanks!
Well, I gave up tonight. I've tried everything I could find and everything mentioned here but recovery has eluded me. I called Amazon to talk to them and after trying a few troubleshooting options they gave me a 20% discount on a Fire TV. I ordered a refurbished 2nd gen Fire TV so I'll be ready when I get a 4K tv.
Thanks for all of your help guys. I wish we had gotten it done. Maybe next time!
firetv 1 st gen was Birked only white amazon logo . ( in the past i used keyboard and manage to factory reset ) but not with this firetv .
i manage using fast boot to instal recovery .
now i can use the keyboard to have access to recovery menu
i can connect using adb .
i pushed many roms and fallow installation from scared
i get update or installation from scared complete . but with red kernel: not dispatched
when i reboot i get only white amazon logo hunging .
i do not care about rooting all i want is bring my amazon to boot again normally
please how i do .
ps i have access to recovery menu
i can connect with adb .
god bless i tried everything in this forum .
it looks like no one knows or no one gives damn
If you install kingroot on a Windows PC and then plug that into the Amazon device.
If you set kingroot to automatically root your Amazon device it should automatically reinstall the factory image if it fails to root it for you.
This is how I unbricked a fire TV stick. I understand that this is a full fire TV, however if you are stuck what have you got to lose.
Alternatively if you have installed TWRP, then you should be able to mount external devices and install the factory image from there yourself...
jeremysimons said:
If you install kingroot on a Windows PC and then plug that into the Amazon device.
If you set kingroot to automatically root your Amazon device it should automatically reinstall the factory image if it fails to root it for you.
This is how I unbricked a fire TV stick. I understand that this is a full fire TV, however if you are stuck what have you got to lose.
Alternatively if you have installed TWRP, then you should be able to mount external devices and install the factory image from there yourself...
Click to expand...
Click to collapse
hi bro
i hav now fire stick that don't update it stuck om update screen and go no further can not allow me to get to registration .
i tried to use king root but the pc dod not recognize the fire stick so the process did not happen how to do it thx
can not connect to adb or anything but can connect to a wifi
Sorry for the late reply on this, I only just saw it when I installed xda labs.
Firstly use Windows 7 or 10, which version did you use? Secondly you will need to follow the respective instructions to install kingroot. For instance Windows does not come with complete USB drivers and needs to install Android drivers for each device. You can get round part of this by installing the Android SDK which includes a repository of most drivers. Test it is working first with a phone or tablet.
I assume you have the internet enabled on both the windows device and fire TV stick? You will probably also need to ignore any false positives from virus guard software during the process and temporarily (keep it safe by avoiding doing anything else on the internet!) Turning off your firewall.
Finally kingroot has many fake copies floating around! Only follow genuine threads from xda. (I would give a link but have noticed they change from time to time because of the nature of these apps).
I have successfully un-softbricked both my fire TV sticks using this process. Good luck!