I received this from a friend because it was bricked after an update ran against its custom ROM.
I have tried everything to restore it, but nothing seems to work. It starts up but only gets to the Amazon TV logo and just sits there. Here's what I have tried so far:
1. I connected it to my laptop via an A-A Male-Male USB cable, but my PC doesn't see it so I can't push anything to it via ADB.
2. I connected it to my network, but it doesn't pull an IP address so I can't push anything to it via ADBLink.
3. I tried using the remote to force a factory reset using back arrow and right, but it doesn't see the remote so that doesn't work either.
4. I connected a USB keyboard to it and used Alt+PrtScn+i to force it into recovery mode, but it only display a system recovery screen and doesn't give me any options and doesn't do anything when I press the "Home" key.
Any advice on restoring this Fire TV would be GREATLY appreciated:laugh:
Related
Hello, excuse my bad English, but I need emergency.
I have a KFHD by certain situation is in a loop recovery system. As you know, this loop is that the device can not boot and will only return to the menu.
I managed to do a "factory cable", but this is where the problem comes: Apparently the factory cable works well, then send my device to "fastboot mode", but my PC does not dectecta well. I mean, my PC only detects it as "unknown device". I installed the same driver offered here, and I've also installed the USB ADB drivers from SDK, but my device still does not appear to work. So I come to you, hoping you can help me, obviously I can not run any programs to my KFHD restabilizar if the PC detects me. Actually this process should be easy, since it is only a matter of using the "KFHD SRT," but before I solve the problem on the drivers.
Oh and by the way, as data when my KFHD is connected to the PC in "fastboot" mode, a constant sound is heard, that sound you hear when Windows detects a device, but repeatedly. Also, when I go to "device manager" is flashing continuously when connected my KFHD. The device I can find the part that says "Generic USB Hub", but it is listed as unknown, and I can not access it to manually assign the controller. I hope this can help as a reference, I am very desperate because I thought the factory wire going to solve everything easy. Also connected the regular cable when it's in fastboot mode, but it does not detect it.
Thanks if you are paying attention to this, and expect a response. Nice day :crying:
OK so to make this clear you can get into recovery still or are you stuck in fastboot now? If you can get into recovery it is a lot easier to fix as you just have to push a ROM onto the device assuming we can get the drivers to install. Or did you mean stock recovery?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK so to make this clear you can get into recovery still or are you stuck in fastboot now? If you can get into recovery it is a lot easier to fix as you just have to push a ROM onto the device assuming we can get the drivers to install. Or did you mean stock recovery?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for answering and for your time.
I commented . my KFHD is has the red triangle, and constantly sends me to " kindle fire recovery system " where options appear : reboot your kindle , reset to factory defaults . Neither of these options is used correctly because it always ends up making a loop to the menu. But still , you can enter this mode every time I turn off the computer, and I can also come to whenever fasboot mode with the cable. I guess it 's a good sign .
The downside is that my PC does not detect my KFHD in any way. But reality itself but only detects an unknown device in fastboot mode . But does not detect it well, and the message appears continuously me usb device not recognized .
Already tried all usb desisntalando drivers and re- install and got the same result. Now I tried to do the same with two other PCs, and continues with the same. I do not know what could be . I clarify that I built my own "cable factory" , I have reviewed in several places and it seems that I did well, ootherwise you could not put in Fastboot mode.
There's a possibility that your fastboot cable may have shorted out the USB port... If it keeps saying something like USB device not recognized that's bad. If it can't be detected in fastboot as a Tate,otter,or jem device then I would think about getting amazon to give you a free replacement.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hello, I just recently bought the Amazon Fire TV stick. When I first got it, I was able to connect it to my computer using the adbFire tool with no problem. I was able to sideload Kodi and push apps to it with no problem. Now, a couple days later, when I try to connect the same device using the same program, it keeps popping up with the message "device not connected".
I tried to connect through command prompt but it still didn't work. I also tried pinging w/ command prompt but it keeps giving me "Destination host unreachable". I turned ADB debugging off and back on, turned wi-fi off and back on, and rebooted the stick multiple times yet it still doesn't work.
Anyone have any ideas on what might be the problem? I don't understand how it was connecting just 2-3 days ago but it doesn't work when i try it now. Only other thing I can think of is a factory reset but I'm hesitant to do that in fear of me not being able to sideload everything again.
Any help is appreciated, thanks.
AlphaBee said:
Hello, I just recently bought the Amazon Fire TV stick. When I first got it, I was able to connect it to my computer using the adbFire tool with no problem. I was able to sideload Kodi and push apps to it with no problem. Now, a couple days later, when I try to connect the same device using the same program, it keeps popping up with the message "device not connected".
I tried to connect through command prompt but it still didn't work. I also tried pinging w/ command prompt but it keeps giving me "Destination host unreachable". I turned ADB debugging off and back on, turned wi-fi off and back on, and rebooted the stick multiple times yet it still doesn't work.
Anyone have any ideas on what might be the problem? I don't understand how it was connecting just 2-3 days ago but it doesn't work when i try it now. Only other thing I can think of is a factory reset but I'm hesitant to do that in fear of me not being able to sideload everything again.
Any help is appreciated, thanks.
Click to expand...
Click to collapse
Make sure fire tv stick has not been assigned the primary IP address for your modem typically 192.168.1.100 if this is the case than simply get a new IP address. I wasn't able to connect adb when for some reason my fire tv grabs ip address 192.168.1.100.
Thanks
ashsha7877 said:
Make sure fire tv stick has not been assigned the primary IP address for your modem typically 192.168.1.100 if this is the case than simply get a new IP address. I wasn't able to connect adb when for some reason my fire tv grabs ip address 192.168.1.100.
Thanks
Click to expand...
Click to collapse
I tried changed the IP address on the FireTV and I am still getting the error when I try to connect it . However I am getting results when trying to ping so at least there's some progress. I'm going to play around with it more in a bit and see if I can get it to work. Thanks for the tip!
it's working again
just to update i reset my connection as well as rebooted my FireTV stick (once again) and now it's finally working. Thanks again for the help!
AlphaBee said:
just to update i reset my connection as well as rebooted my FireTV stick (once again) and now it's finally working. Thanks again for the help!
Click to expand...
Click to collapse
Same experience - couldn't connect to or ping the Fire Stick at first, then restarted it, the router and my computer, and it worked.
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
I sideloaded settings.apk to my Fire Stick 2.
I opened it up, & accidently disabled wifi.
Now the stick barely boots past the logo, and displays a no network WiFi error message. It wants to connect to a network, but won't since Wifi is off. Rebooting has no effect.
Worst of all: the remote will no longer communicate with the stick. I guess that connects over wifi too.
I need to enable wifi again to unbrick my device. Or factory reset. But I can't use the remote. I have no way to input commands, that I know of. So the remote reset is a no go.
I will try to reset using adb commands over windows, connected via micro usb.
And/Or find a way to reflash the stock rom, or a custom one. I don't care about root. My stick is not rooted, runs some version of Fire OS, and its got Kodi and a few other apps sideloaded. Install Unknown Sources and Adb debug should both still be enabled.
Please help me guys! I need my tv back. What's my best course of action? Anyone got any steps, instructions or helpful links? I'm no expert, and I'd love experienced input.
If you can connect via ADB, then see this guide on how to control it: http://www.aftvnews.com/how-to-remotely-control-an-amazon-fire-tv-or-fire-tv-stick-via-adb/
Your other option is to use an OTG cable with a USB keyboard. See here: http://www.aftvnews.com/amazon-fire...d-ethernet-adapters-via-usb-otg-without-root/
Hi All,
I started a factory reset on my 2nd gen firestick and it has failed leaving it unable to boot. It is stuck at the colourful fire tv logo (just after the white logo). When I first got it about 3 years ago I disabled updates using adb commands found on here as well as disabling adverts on the home screen. I assume this is what has caused it to fail.
I've tried to get in to the recovery screen with the remote and also with the alt-i-prtscrn via usb keyboard and none have any affect. I have also tried the method posted here:
https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-tv-stick-2nd-gen-tank.3907002/ but still without success.
I used an Ubuntu live USB and get as far as where the script says "waiting for bootrom" when I do the short and connect the firestick nothing happens. If I connect the firestick without the short it shows up in "files" as "fire" but won't mount ("unable to open MTP device..."). When I type lsusb it lists various items including "Lab126, Inc.".
I'm a noob when it comes to linux but I can type commands in a terminal window and I have quite a bit of experience rooting and playing with android devices.
Does anyone have any ideas or suggestions?
TIA
nathanjuk said:
Hi All,
I started a factory reset on my 2nd gen firestick and it has failed leaving it unable to boot. It is stuck at the colourful fire tv logo (just after the white logo). When I first got it about 3 years ago I disabled updates using adb commands found on here as well as disabling adverts on the home screen. I assume this is what has caused it to fail.
I've tried to get in to the recovery screen with the remote and also with the alt-i-prtscrn via usb keyboard and none have any affect. I have also tried the method posted here:
https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-tv-stick-2nd-gen-tank.3907002/ but still without success.
I used an Ubuntu live USB and get as far as where the script says "waiting for bootrom" when I do the short and connect the firestick nothing happens. If I connect the firestick without the short it shows up in "files" as "fire" but won't mount ("unable to open MTP device..."). When I type lsusb it lists various items including "Lab126, Inc.".
I'm a noob when it comes to linux but I can type commands in a terminal window and I have quite a bit of experience rooting and playing with android devices.
Does anyone have any ideas or suggestions?
TIA
Click to expand...
Click to collapse
Like you said you got this stick 3 years ago, great, it can be rooted.
And you are not shorting the stick properly and its booting up, that's why you see Lab126 Inc.
You have to short the stick then plug usb in while the device is shorted.
You can use
watch -n 0.2 lsusb
to check when the device gets connected, if it says mediatek then you are good to go. If it says Lab126, unplug the device short it again and plug it in.
You have to keep the short for more then 10 sec after connecting, when it says mediatek leave the short and open bootrom script.
Suggestions,
Change the wire for shorting.
Disable ModemManager if you haven't already done.
If you are still having trouble, Download and use live version of FireISO, its already patched.
Thanks for your suggestion, and sorry for the delay in responding.
You were right that I wasn't shorting the pin correctly. I tried it again and everything went to plan.