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/
Related
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 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:
I've got a first gen fire tv box with a remote that doesn't want to detect the remote. and being as it wont let me pass the setup im looking for any fix for this ? Im still able to access the stock recovery so is their any ota's i can flash ? or any other method to root the box without being in the system ?
is the box fubar ?
Dumb question but did you put the remote in pairing mode when you are trying to connect? You can always connect a keyboard to navigate through the set up. As for rooting, you should check AFTVnews for guides if you are on a rootable software version.
Hey I just got a gen2 firestick from a friend and it didn't come with a remote is there any way to set it up without remote I have a gen 1 firestick I use the remote app on it but can't connect with the new one due to it not being set up Any suggestions
Adb probably isn't enabled, is it?
My Fire TV stick 2 suddenly refused to recognize my remote but I could send a few key presses via adb and suddenly the remote worked again.
my previously rooted Gen 1 AFTV started to have issues so I tried to update the rather old OS build - and bricked the device. no LED light, nothing.
using an A-A cable I successfully followed rbox' instructions in https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676 writing the contents of update-kindle-bueller-51.6.3.2_user_632552020.bin to the respective partitions and wohoo, the box booted again, although without rbox' bootloader which I didn't care for too much then.
worse problem was there was also no network connection - neither Ethernet (no link) nor WIFI (just kept scanning forever) worked. not really knowledgeable about the boot process of Android devices I resorted to a factory reset, which seemed to work but now I'm stuck at the Amazon setup (just after language selection) still without network and no other way to go. tried the alt-prtscr-i route but that only got me to a screen with red text saying the device would enter recovery which never happened no matter how long the wait.
thinking the bin file may have been corrupted next I attempted to dd-write the partitions again with contents from another bin file but couldn't even "see" the partitions anymore. hooked up to a knoppix box nothing shows those sdcX partitions anymore: df -h, mount, fdisk -l, cat /proc/partitions. only command - briefly - showing a Qualcomm device was lsusb.
same on a W10 machine where the booting AFTV would briefly show up as a USB mass storage class device (of course without access to it) but would then disappear again with the corresponding sound. the box still boots to the amazon setup however.
now I'm stuck and don't know what to try next. previously ADB debugging was active and I sometimes used the interface to push packages to it but now I don't even have an IP connection anymore to dig into the config files :crying:
thanks for any ideas ! would love to get the box back to life again
bikernzrh said:
my previously rooted Gen 1 AFTV started to have issues so I tried to update the rather old OS build - and bricked the device. no LED light, nothing.
using an A-A cable I successfully followed rbox' instructions in https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676 writing the contents of update-kindle-bueller-51.6.3.2_user_632552020.bin to the respective partitions and wohoo, the box booted again, although without rbox' bootloader which I didn't care for too much then.
worse problem was there was also no network connection - neither Ethernet (no link) nor WIFI (just kept scanning forever) worked. not really knowledgeable about the boot process of Android devices I resorted to a factory reset, which seemed to work but now I'm stuck at the Amazon setup (just after language selection) still without network and no other way to go. tried the alt-prtscr-i route but that only got me to a screen with red text saying the device would enter recovery which never happened no matter how long the wait.
thinking the bin file may have been corrupted next I attempted to dd-write the partitions again with contents from another bin file but couldn't even "see" the partitions anymore. hooked up to a knoppix box nothing shows those sdcX partitions anymore: df -h, mount, fdisk -l, cat /proc/partitions. only command - briefly - showing a Qualcomm device was lsusb.
same on a W10 machine where the booting AFTV would briefly show up as a USB mass storage class device (of course without access to it) but would then disappear again with the corresponding sound. the box still boots to the amazon setup however.
now I'm stuck and don't know what to try next. previously ADB debugging was active and I sometimes used the interface to push packages to it but now I don't even have an IP connection anymore to dig into the config files :crying:
thanks for any ideas ! would love to get the box back to life again
Click to expand...
Click to collapse
Only the unlocked bootloader is able to read/write to the emmc via the a-a usb cable. Adb debugging is gone due the factory reset.
What is installed on system? A prerooted rom? Then the solution is probably to boot into TWRP and wipe cache, dalvik, data, internalsd.
In case the TWRP bootmenu is gone too, there isn't much (maybe nothing) you can do...
Sus_i said:
Only the unlocked bootloader is able to read/write to the emmc via the a-a usb cable. Adb debugging is gone due the factory reset.
What is installed on system? A prerooted rom? Then the solution is probably to boot into TWRP and wipe cache, dalvik, data, internalsd.
In case the TWRP bootmenu is gone too, there isn't much (maybe nothing) you can do...
Click to expand...
Click to collapse
being a newbie to Android I'm not exactly sure. I believe it was a prerooted rom. it showed RBOX's BOOT MENU at startup and I did have root access.
according to "how-to-factory-reset-a-rooted-fire-tv-using-twrp-custom-recovery" on aftvnews the reset to factory defaults should not have removed root or TWRP, however there is no menu when booting the device and pressing right-arrow won't bring one up either. it just boots to the amazon setup
does that mean that I'll have to toss it?
bikernzrh said:
being a newbie to Android I'm not exactly sure. I believe it was a prerooted rom. it showed RBOX's BOOT MENU at startup and I did have root access.
according to "how-to-factory-reset-a-rooted-fire-tv-using-twrp-custom-recovery" on aftvnews the reset to factory defaults should not have removed root or TWRP, however there is no menu when booting the device and pressing right-arrow won't bring one up either. it just boots to the amazon setup
does that mean that I'll have to toss it?
Click to expand...
Click to collapse
Idk. If the bootmenu doesn't show, its probably gone.
About the network problem, maybe a router reset is worth a shot?
Sus_i said:
Idk. If the bootmenu doesn't show, its probably gone.
About the network problem, maybe a router reset is worth a shot?
Click to expand...
Click to collapse
thanks for your thoughts!
what has me curious still is the fact, that I no longer can access the box from Linux as I did before. wonder if the new OS is hiding TWRP info normally visible and if there is any secret way to invoke it?
the router is fine. always in use with various WIFI clients and also just successfully tested a cable connection to it with a laptop.
bikernzrh said:
thanks for your thoughts!
what has me curious still is the fact, that I no longer can access the box from Linux as I did before. wonder if the new OS is hiding TWRP info normally visible and if there is any secret way to invoke it?
the router is fine. always in use with various WIFI clients and also just successfully tested a cable connection to it with a laptop.
Click to expand...
Click to collapse
In case you are good with a solder iron, there is always the hardware option, in order to read/write to the EMMC partitions. Take a look here and here. But aside from the soldering skills, it cost some bucks to buy hardware...
Sus_i said:
In case you are good with a solder iron, there is always the hardware option, in order to read/write to the EMMC partitions. Take a look here and here. But aside from the soldering skills, it cost some bucks to buy hardware...
Click to expand...
Click to collapse
I fear my soldering expertise is not sufficient to attempt that guess I'll have to shop around for another used device instead as I need TOSLink and would also like to retain an Ethernet connection.
thank you so much for your help!