Is my vanilla 2nd gen FireTV dead ? - Fire TV Q&A, Help & Troubleshooting

My FireTV is stuck in boot. I get a black screen with white amazon logo (no orange colours). The white light slowly flashes on the front box, and eventually my TV eventually gets a no signal response.
The device registers the remote, (every click gives the white light comes on) but I am unable to go into recovery (Right button + Back Button). Opening up ADBLink, I am able to connect to the device by IP address, and I can reboot the device remotely and I can enter reboot recovery. When I enter reboot recovery, the FireTV reboots and in red writing I get
"Your Amazon Firetv will restart in a few minutes, and show resume normal operation, If it does not restart please unplug the power cable and plug it back in to force a restart. If you need assistance please contact support at Amazon" .
However nothing happens, and when I restart I get stuck at the white amazon logo.
I have tried 3 separate keyboards and tried ALT + Print screen, or ALT + i + Print Screen, or ALT+ Home, or ALT + i + home. None of them worked.
It has the stock OS installed (Dont know which version but assume the latest update), and the only action beyond normal operation has been the sideloading of a couple of common APKs. (No rooting, bootloader it locked). As it is out of warrrenty Amazon are little help (15% discount on next FireTV purchase).
Is there anything I can do, or is my box now a paper weight ?

If you swear that it is an unmodified device, then there seems to be a hardware defect where you can't do anything anymore, e. g. the internal eMMC memory is broken!
However, your phenomenon still sounds like a brick through a failed root attempt or rom update or something similar.

rainman74 said:
If you swear that it is an unmodified device, then there seems to be a hardware defect where you can't do anything anymore, e. g. the internal eMMC memory is broken!
However, your phenomenon still sounds like a brick through a failed root attempt or rom update or something similar.
Click to expand...
Click to collapse
Thanks for reply, it is completely unmodified . So you are probably right about it being a hardware fault.
I have a toddler who likes to play with everything (at times even pulled out the fire TV) so guessing she did something. As a last resort I am going to take it apart. Perhaps I will be lucky and see something obvious

abfmdf said:
Thanks for reply, it is completely unmodified . So you are probably right about it being a hardware fault.
I have a toddler who likes to play with everything (at times even pulled out the fire TV) so guessing she did something. As a last resort I am going to take it apart. Perhaps I will be lucky and see something obvious
Click to expand...
Click to collapse
Good luck to you! :fingers-crossed:

Related

[Q] Remote wipe. Did it brick the phone?

Hi,
I received a LG GW910 from the DevConnections conference. I was playing with the remote services available through the live.com device center and performed a remote erase of the device. It seems like it did not complete as now all I get when powering on the device is a white LG logo, or I can enter the "connecting kitl" screen. When in either screen I cannot power off the device or anything else. Is there anything I can do to restore the device to a working condition?
Thank you!
I don't know much about how this works but I would try to remove the device from windowsphone.live.com so that your Live ID isn't associated with it anymore. Just a wild guess.
No joy, but thanks for the idea. I don't think its loading the 'OS' even. Is there a way to restore the 'OS' from anywhere?
There's usually a combination of hardware keys you need to press to do a hard reset. Check the manual for your phone.
Thanks buddy, but if there is, I haven't found them yet.
I'll keep digging..
There is a Hard Reset option:
Originally Posted by sutt359
If you hold down both Vol buttons at start-up you can hard reset
Click to expand...
Click to collapse
taken from the Tips and Tricks Thread.
Hope I could help you
L-Dani
dimitrii01 said:
Hi,
I received a LG GW910 from the DevConnections conference. I was playing with the remote services available through the live.com device center and performed a remote erase of the device. It seems like it did not complete as now all I get when powering on the device is a white LG logo, or I can enter the "connecting kitl" screen. When in either screen I cannot power off the device or anything else. Is there anything I can do to restore the device to a working condition?
Thank you!
Click to expand...
Click to collapse
I did this with the dev device I was allowed to borrow same one the GW910, I plugged it into the mains and had dinner, it was back at the OOBE screen when I got back, scared the crap outta me as the device is on loan and I thought I bricked it.
If you push both volume buttons at startup (on this device) it just takes you to the "connecting kitl" screen. At that point, what should I do to reset the device?
I tried connecting it to a kettle and a kitten and some cattle, but it didn't help, although I think I plugged it in the wrong port on the cattle
I just did this to my phone as I have to return it due to bad reception in my area.
Once reset it stayed at the HTC white boot screen. I pulled the battery and it reset just fine.
Back to setup again on the phone.
ckacey said:
I did this with the dev device I was allowed to borrow same one the GW910, I plugged it into the mains and had dinner, it was back at the OOBE screen when I got back, scared the crap outta me as the device is on loan and I thought I bricked it.
Click to expand...
Click to collapse
OK, I did this and it actually worked. Previously I had let the phone sit at the LG logo for over 20 minutes with the entire phone getting hot from driving the display and it never did anything. So I plugged it in to main power and left it while I went to lunch and low and behold it was at the OOBE screen when I returned.
Who woulda thought that it would take that long and that it wouldn't give a status message or anything...
Either way, my thanks to you for the suggestion.
My pleasure, I remember how scared I was thinking I'd have to explain to MS how I bricked their device, using Windows Live of all things. I don't think anyone should have to go through that kind of a scare.
I wonder though, could the extreme wait-time be a way to discourage "finders" in a repeat of the iPhone 4 bar situation? Nuke the device and it won't boot for quite some time while connected to wall power ...
It still wipes quickly when using the reset option on the about screen.

[Q] New AFTV stuck on amazon logo but still adb access.

Hello,
Got an AFTV at staple the other day. I tried to follow the aftvnews guide "How to setup a new AFTV...".
Apparently my AFTV was pretty old since the initial unplug/plug trick did not work and the box was always stuk on waiting to download the update. I finally let the update run through and ended up with Firmware 51.1.0.2_user_510058520.
After that I tried to root the AFTV. For this I used adbFire. I was able to connect to the box (no internet connection at that time) and click on the Towelroot option. I did click on "Make it ra1n" and wait for a very long time. I never saw any message indicating that it succeded or failed. With the remote I ended up going back to the previous menu. I tried to install SuperSu but that did not work. Su was not installed. After rebooting the box, I get the back and white Amazon logo and then the screen goes black. The TV shows the selected input as if the AFTV is not sending any signal. I tried to plug the internet cable (with the 2 domains blocked) and the AFTV finally goes from the Orange blicking led to the Blue one but it's still stuck after the amazon back and white logo. I did try the ALT-I-PrntScr (which had worked previously when I was trying to prevent the update to install, I managed to get into recovery and do a factory reset ,so I know the keyboard itself is OK). But this time ALT-I-PrntScr only get the box to restart and brings me back to the Amazon black and white logo that disappear after a minute.
Nevertheless, I can still access the box from an adb shell, adbFire can connect to the AFTV. But since I no longer see any menu on the screen I can't attempt to reroot from adb fire.
A reboot recovery does not work as it's not authorized.
su command is not found , so it would confirm supersu did not install (properly). What's weird though is that if I do a ps, I see a process "u0_a1 6199 328 476352 18640 ffffffff 00000000 S eu.chainfire.supersu"
Any idea how I can unstuck the box ?
Thank you.
Some info for people in the same situation, the issue was that Towelroot needs internet access to complete.
i have exactly the same situation here. system doing an update and the power got cut off and viola. Welcome white amazon logo and pulsing white and orange indicator light. Tried all the possible ways found on the forum and net but no joy. Now its sitting on my drawer and hoping i can still find a way to make it alive.
DhiJay23 said:
i have exactly the same situation here. system doing an update and the power got cut off and viola. Welcome white amazon logo and pulsing white and orange indicator light. Tried all the possible ways found on the forum and net but no joy. Now its sitting on my drawer and hoping i can still find a way to make it alive.
Click to expand...
Click to collapse
I have the same exact issue right now, probably that same update yours downloaded from 2 weeks ago:
https://forum.xda-developers.com/fire-tv/general/fire-tv-stuck-amazon-logo-adb-t3809305
This guy had the same problem too, and he has a big list of things to try, none of which worked for me:
https://forum.xda-developers.com/fire-tv/help/fire-tv-remains-stuck-amazon-firetv-t3561797
Mine's unrooted on the latest version, so I guess I can't root and reinstall rom. I'd hate to have to throw this away it's only 2 years old. I have a 5 year old Roku that still runs great.
"Perfect" timing I guess with Prime Day coming up?
Edit: couple more guys having the same issue recently, sounds like a mass bricking going on
https://forum.xda-developers.com/fire-tv/help/firetv-box-white-amazon-logo-blank-t3472867
https://forum.xda-developers.com/fire-tv/help/fire-tv-stucks-white-amazon-logo-t2889867
https://forum.xda-developers.com/showthread.php?t=2799779&page=7
DhiJay23 said:
i have exactly the same situation here. system doing an update and the power got cut off and viola. Welcome white amazon logo and pulsing white and orange indicator light. Tried all the possible ways found on the forum and net but no joy. Now its sitting on my drawer and hoping i can still find a way to make it alive.
Click to expand...
Click to collapse
I played with mine a bit more today and I was able to fix
I read somewhere that someone else was having the same issue and said it was a HDCP handshake issue and they were able to fix by plugging to a different HDMI port on the TV. I tried that and it booted up to the colorful Amazon logo, showed the home page for a sec, then went to a black screen. From here, it would flash the home screen really quick randomly every 30 secs or so, so I know it booted up and I'm on the home page, it's just not displaying correctly. I was then able to pair my remote (I unpaired before because I was using flirc), then us the remote shortcut to factory reset. Good to go after the reset.
TBH, I did not try turning it on before I swapped HDMI ports so I'm not 100% sure if switching ports really did help it boot past the white logo, or if it just happen to get fixed after some time.
Interestingly while on the colorful logo, the alt+i+printscreen trick did not work for me. So it took me longer before I could get to the factory reset.
johnusesandroid said:
I played with mine a bit more today and I was able to fix
I read somewhere that someone else was having the same issue and said it was a HDCP handshake issue and they were able to fix by plugging to a different HDMI port on the TV. I tried that and it booted up to the colorful Amazon logo, showed the home page for a sec, then went to a black screen. From here, it would flash the home screen really quick randomly every 30 secs or so, so I know it booted up and I'm on the home page, it's just not displaying correctly. I was then able to pair my remote (I unpaired before because I was using flirc), then us the remote shortcut to factory reset. Good to go after the reset.
TBH, I did not try turning it on before I swapped HDMI ports so I'm not 100% sure if switching ports really did help it boot past the white logo, or if it just happen to get fixed after some time.
Interestingly while on the colorful logo, the alt+i+printscreen trick did not work for me. So it took me longer before I could get to the factory reset.
Click to expand...
Click to collapse
I wish I had the same luck like you but i tried different tv's, all the ports availble and different HDMI cables but still no luck.
Anyone able to find a solution to fix it? or should I just throw it out?
DhiJay23 said:
Anyone able to find a solution to fix it? or should I just throw it out?
Click to expand...
Click to collapse
Sorry you weren't able to fix. Before you throw away, try contacting support. Not because they can fix it, they most probably can't. When I had problems with mine, I contacted them and they gave me a $15 credit off of a new one because I was out of warranty. This was a couple days before Prime Day so I was able to snag a new one for really cheap. Plus my old one started working again, so I now have 2 Fire TVs

[Q] Broke Amazon Fire Tv box?

I brought a new amazon fire tv box. I am not looking to root. I booted it up, it updated. I connected to my network. Downloaded Netflix tried to watch Netflix and it gave me a error. So I unplugged the box to reboot. Plugged it back up and nothing. The unit won't power on. So I did an RMA and got a new one.
Got the new one, powered it up, took the update, downloaded Netflix, same error on not playing. Used the remote to put unit in sleep mode. And now the unit won't come back on. Did I get two bad units? Is there any hope in getting this thing to boot back up?
Any thoughts?
nighthawk777 said:
I brought a new amazon fire tv box. I am not looking to root. I booted it up, it updated. I connected to my network. Downloaded Netflix tried to watch Netflix and it gave me a error. So I unplugged the box to reboot. Plugged it back up and nothing. The unit won't power on. So I did an RMA and got a new one.
Got the new one, powered it up, took the update, downloaded Netflix, same error on not playing. Used the remote to put unit in sleep mode. And now the unit won't come back on. Did I get two bad units? Is there any hope in getting this thing to boot back up?
Any thoughts?
Click to expand...
Click to collapse
That is some strange stuff...netflix errors are common but a reboot almost always fixes it. I don't know what's going on but amazon actually has great customer service so make a call and more than likely they'll either walk you through it or possibly send you a new one.
i have the same issue, it stopped working after a day. No power LED no nothing.
I was holding "select and play" in an attempt to restart the box because i encountered sluggish performance on Kodi.
Afterwhich, i am not able to turn it back on again despite changing socket points and random clicking on the remote.
While i am waiting for a new set from Amazon, is there anyone who has encountered the same issue but have managed to power up the box??
I am in the exact same position ....
- new out of the box
- updated as part of the install process
- side-loaded Kodi with a "success" message
- rebooted as instructed with play and select for 5 seconds ....
- nothing, dead, no reboot, nothing, no light. Seems completely dead.
As the person above - let me know if you anyone has a thought.
brickspeed said:
I am in the exact same position ....
- new out of the box
- updated as part of the install process
- side-loaded Kodi with a "success" message
- rebooted as instructed with play and select for 5 seconds ....
- nothing, dead, no reboot, nothing, no light. Seems completely dead.
As the person above - let me know if you anyone has a thought.
Click to expand...
Click to collapse
I was reading the feedback on Amazon fire tv product page, apparently we are not the only ones.
Based on the users' feedback, seems like Amazon engineers have acknowledged that it's a known issue. SCARY.
I have the exact same thing, there is definitely a bad batch going around.
My Fire TV arrived on Monday, 2/16/15. I plugged it in and took an update as part of the setup. I installed several apps and logged in to accounts, watched about 3 hours of stuff on it that night. The next day it was dead as a door nail. No lights, no amount of button mashing on the remote made any difference. I have a replacement being sent out. The AFTV is currently out of stock, I'm curious if this is related.
I read another person complaining another site. Do we have anything resembling a common link? It seems so far this is effecting non-rooted aftvs with the latest update but not all aftvs. Are all of these units relatively new? Purchase date?
I just want to figure out if it's hardware or software related. I purchased another one after Xmas and no issues so far.
Just got mine, set it up, used it maybe for 2 hours, unplugged, connected to the TV and same thing. Dead.
Haha same thing happened to me. Got Kodi and everything installed. Unplugged the Fire TV and now it's bricked.
same happened to me.
got my unit today installed kodi fine. Was using the llama method to get a kodi icon added to the home screen. needed a reboot and used the select+play method on remote and now it won't turn back on. Contacted amazon and they are sending me a new replacement.
teng247 said:
got my unit today installed kodi fine. Was using the llama method to get a kodi icon added to the home screen. needed a reboot and used the select+play method on remote and now it won't turn back on. Contacted amazon and they are sending me a new replacement.
Click to expand...
Click to collapse
Anyone who have gotten their replacement units, may i know if you guys encounter the same issue again?
I am still waiting for my replacement set.
I'm guessing from the symptoms mentioned that it is their recent efuse blow up related. Maybe recent update did not update bootloader for some reason. If that so then box is not booting bootloader and sits in qualcomm recovery mode in which you can hook up it with usb "male a - male a" cable to pc and have full emmc access for flashing correct bootloader.
Add me on the list for a broken 1 day use on the AFTV. I sideloaded Kodi and was using it last night. Put it in sleep mode and then went to sleep myself. Woke up this morning and no lights/repsonse or anything on the box. Contacted Amazon customer support. One for the first few questions they asked is if I had sideloaded anything. I of course denied I did such a thing in case they try to back out of warranty issues. Customer Service Representative talks to her supervisor and instead of issuing a replacement unit they are sending me a new power adapter instead. Customer service rep states that her supervisor says from their experience that is usually the issue. I tell her with my voltage tester that i am detecting current running through the line. They still insist on power adapter.
Just to see if there is commonality among the AFTVs, did you guys get your boxes during the Sling TV promotion? Maybe a bad production batch?
How would side load affects the ability to power the box?? *puzzled*
There are so many users who did it, why does the issue only occurs recently.
An Amazon customer service told me this is not a common issue, but I have been seeing more and more of such cases.
All,
I have rooted at least 10 boxes, none fo my family or friends have report this issues. Of course, all these AFTV has Rbox pre-rooted firmware installed so i am going to guess folks who have reported this issues are non rooted boxes running the latest Amazon firmware.
It would ideal, If users who have reported this could provide the following info, this will help to identify a patter.
1) Serial number (it generally starts with 70900xxx)
3) Purchase date
4) Box purchased from?
4) Is your box rooted? If so what is have you installed (boatloader unlock (partial or fully) CWM, prerooted rom, ect)
5) what firmware is the box running (Amazon stock or Rbox), please provide the actual firmware version.
6) Was the firmware ever updated, if so from what version to what?
6) Sideloaded app
7) how long did you use the box before it went dead.
Thank you
tylerxm84 said:
How would side load affects the ability to power the box?? *puzzled*
There are so many users who did it, why does the issue only occurs recently.
An Amazon customer service told me this is not a common issue, but I have been seeing more and more of such cases.
Click to expand...
Click to collapse
Not a "common issue" is pretty subjective. What matters is its happened to several people in a short span of time, and xda members account for a tiny percentage of aftv owners. I contacted amazon for a different issue recently and what I realized was that rep giving support has never actually used a fire TV.
I don't think its the efuse like another person mentioned here unless it blew and had unintended consequences. Efuse, I think, is supposed to put it in an "obscure recovery mode". The box should power on. It'd still be useless but the fact that it does nothing makes me think its not efuse related.
For curiosity sake I'd like to hear what happens if they try a different power supply. Not amazon stock as that's been tried. But that might be academic, those boxes seem dead and unrecoverable. Since amazon will surely send a replacement, I'd open it up and see if there's anything noticeable. You won't find a blown efuse since that's not visible to the naked eye.
KLit75 said:
I don't think its the efuse like another person mentioned here unless it blew and had unintended consequences. Efuse, I think, is supposed to put it in an "obscure recovery mode". The box should power on. It'd still be useless but the fact that it does nothing makes me think its not efuse related.
Click to expand...
Click to collapse
How you identified than box is not powering on? Front white led indicator initialized when bootloader is loaded, if bootloader blacklisted by efuse there will be no light on front panel.
Ck-NoSFeRaTU said:
How you identified than box is not powering on? Front white led indicator initialized when bootloader is loaded, if bootloader blacklisted by efuse there will be no light on front panel.
Click to expand...
Click to collapse
You could very well be right. Just from reading vaguely about refuse, it renders the device useless but you would see something on the screen. I didn't think the light indicated boot loader. I thought it was an indication of power and it turns white when an internet connection is established. As far as I know...exactly how a blown refuse manifests on aftv has yet to be described.
KLit75 said:
You could very well be right. Just from reading vaguely about refuse, it renders the device useless but you would see something on the screen. I didn't think the light indicated boot loader. I thought it was an indication of power and it turns white when an internet connection is established. As far as I know...exactly how a blown refuse manifests on aftv has yet to be described.
Click to expand...
Click to collapse
I had first hand experience with a blown efuse. After certain pre-rooted ROM was loaded, it was ON,After the first reboot, unit had no LED light, nothing on screen. Using A A USB cable I can see the file structures of the unit, I was able to partially recovered (lost root) afterward.
These new units show the exact symptoms, dead after first reboot.
Unit won't come back on
I have the same problem. I am on my second unit. It powered up correctly, I re-registered, and I re-selected my favorites, I watched one show. I finished and turned it off. Now, nothing! I cannot turn it back on. This was the same problem with the first unit. I've tried all the basic hardware fixes - new batteries, new HDMI, etc, but still nothing. I have followed all the basic troubleshooting suggestions from Amazon. Still nothing. Can someone please suggest the right fix?

Galaxy Note 10.1 2014 Edition not booting up/ firmware issue

i have this awesome tablet for a good time. it's the wifi edition with 16gb black. this week i noticed when the tablet goes on rest mode, the screen turns dark (as usual) but when i want to us the tablet, the screen remains dark. i could hear the notification. i had to restart the device and quickly start using the tablet before the screen goes dark again. i noticed the message on the screen stating "firmware upgrade encountered an issue. please select recovery mode in kies and try again." i connected my tablet to my laptop and no success. i called samsung and they told me to press the vol+, power button & home key for 40 secs and nothing happened.
i am turning to the great forum to ask for help. all my stuffed are on the tablet memory. at this point i don't care about it as long as someone can help me bring my awesome tablet back to life. i never rooted it at all.
please, help me.
I'm not the most knowledgeable when it comes to this kind of thing, but I do know that on the Galaxy Note 10.1 2014 edition booting into recovery is slightly different than it is on most other Samsung devices. Where most Samsung's are power button + volume up + home key (like Samsung rep said), with the Note 10.1 2014 edition it's just the first two, power + volume up. Here is a link that will describe step by step how to do it as getting the timing right can be a little bit tricky if you have not done it before. http://mobileaddons.blogspot.com/2014/05/how-to-hard-reset-factory-reset-samsung_9205.html There is probably the same instructions here on xda somewhere if you do a search... I just googled it and that is what it gave me. If you need end up having to boot it in download mode, thats the power and volume down keys, just push and hold both (if I remember correctly). It sounds like it may have attempted to update to lollipop but the update failed for whatever reason, but I could be wrong. What exactly did the Samsung rep tell you to do? a hard reset/factory reset (which will wipe all your stuff), or did they say to attempt the update via kies? Just curious
hi thebadwrench, i followed and tried the instructions you shared and my tablet does not respond at all it stays dark and does not even respond when i plug the charger in. there are no feedback or sounds at all. i do not know what else to do.
Hmmmm. You may have a hardware failure if it is not responding to anything at all. I know others have experienced problems with the screen flickering and/or quit working as result of a loose or disconnected electrical connection internally. It might be worth removing the rear cover of your tablet to look for something like that. I don't know how comfortable you'd be with that, but it's actually pretty easy to do. I recently replaced both the battery and charging port on mine and posted some pictures in this thread here http://forum.xda-developers.com/galaxy-note-10-2014/help/q-instructions-tips-replacing-usb-t3345093 I'd just disconnect both ribbon cables and reconnect them. While your in there (and this has worked for some people) simply unplugging the battery for a few minutes then reconnect it. Kinda resets the tablet (you shouldnt lose anything saved on tablet, assuming your able to revive it). If your not comfortable with digging into your tablet, take it to a phone/electronics repair place and for a fee they could do it for you, or better yet they may be able to diagnose the problem definitively. Other than that, I'm out of ideas. Sorry to hear that your having issues, let us know what happens
I followed the steps and my screen is back on but it is stuck in recovery mode. It shows the green Android guy and says downloading but nothing for the last 10 minutes. What do I do?
Good to hear you got your screen back on. As for it being stuck in recovery mode... just to clarify, what exactly did you do to get it to the screen its on now (i. e. did you just attempt to power it on, or pwr + vol. up buttons, etc). It might be best to just send me a personal message...
How do I send you a personal message?
Just click on my username, then click "send message"

Help with Fire tv stick 4k max do not boot up

Sure my question is not for here but to ask something. Somebody of you guys to know how to hard reset amazon fire stick 4k max. The stick get start and end up to the logo...no meaning how long I wait, no luck to go trought to the end of the process. The remote command do not work (right cycle and back button) when pressed the two buttons before start up. How to hell to try factory reset without remote and physical buttons on to device . Any advice ?
Same here, after the Saturday update... Sunday booted very slow, Monday evening only LOGO....I spoke with Amazon support and I'm returning it today
Vishnarov said:
Sure my question is not for here but to ask something. Somebody of you guys to know how to hard reset amazon fire stick 4k max. The stick get start and end up to the logo...no meaning how long I wait, no luck to go trought to the end of the process. The remote command do not work (right cycle and back button) when pressed the two buttons before start up. How to hell to try factory reset without remote and physical buttons on to device . Any advice ?
Click to expand...
Click to collapse
Try booting in safe mode
If that doesn't work, you can try to boot into recovery. The Recovery menu exists on the 4K stick and earlier FireTVs, I don't know if it still exists on the 4k Max, but worth a shot.
How to unbrick by entering Recovery Mode and Factory Reset the Amazon Fire TV
If you've managed to brick your Fire TV or for whatever reason are unable to get to the settings menu to perform a factory reset, here is how to enter recovery mode without fully booting into the Fire TV's operating system.
www.aftvnews.com
If neither of those two options work, it's time to use the 1-year warranty and get it replaced.
Both options don't work. Mine is already on the way to Amazon for repair/replacement
Is there a way to fix it without a keyboard? Heard something about ADB and connecting the Firestick to a computer, but it hasn't worked.
User authorization is needed to connect a new device via ADB. If you haven't connected your computer to your FireStick before already, and granted authorization, you won't be able to now, since the authorization screen only shows on your TV after you have already booted up.
There is also no guarantee that the system is booting far enough to start ADB on the FireTV.
Finnzz said:
User authorization is needed to connect a new device via ADB. If you haven't connected your computer to your FireStick before already, and granted authorization, you won't be able to now, since the authorization screen only shows on your TV after you have already booted up.
There is also no guarantee that the system is booting far enough to start ADB on the FireTV.
Click to expand...
Click to collapse
That sucks, although understandable. Any other ways to get out of the bootloop or an USB keyboard dongle is needed?
Leshelp said:
That sucks, although understandable. Any other ways to get out of the bootloop or an USB keyboard dongle is needed?
Click to expand...
Click to collapse
Without a keyboard the only way to influence the Stick is with your remote. And all you can do with the remote is initiate a factory reset
Press and hold the Left button, Menu button, and Back button at the same time.
But this only works if you get far enough in the boot process for the remote to connect.
Hello, a while ago a friend gave me a fire tv to see if it could be fixed, the problem is that it doesn't update, I restored it from the factory but it's still the same, any help is welcome
mclarenf195 said:
Hello, a while ago a friend gave me a fire tv to see if it could be fixed, the problem is that it doesn't update, I restored it from the factory but it's still the same, any help is welcome
Click to expand...
Click to collapse
Try a hotspot on the phone and connect the Fire TV stick to the hotspot from the phone. I had the same problem and with hotspot it worked.
Hello, tell me pliz, is there a way to fix this?
after turning it on, it immediately gets into the Recovery mod,
if you connect the keyboard, it only reacts to combinations of 5 buttons which makes the factor default, but just a quick overload and again recover
up and down buttons do not respond, input and remote too,
I tried to connect to AbdLink, it seems like the device is seen but writing unauthorized
does not respond to reboots from the application.
Is there any chance to fix this?
PS. Amazon Fire TV Stick 4K Max was bought in November, nothing was manipulated with it.
anderson_lug said:
View attachment 5810993
Hello, tell me pliz, is there a way to fix this?
after turning it on, it immediately gets into the Recovery mod,
if you connect the keyboard, it only reacts to combinations of 5 buttons which makes the factor default, but just a quick overload and again recover
up and down buttons do not respond, input and remote too,
I tried to connect to AbdLink, it seems like the device is seen but writing unauthorized
does not respond to reboots from the application.
Is there any chance to fix this?
PS. Amazon Fire TV Stick 4K Max was bought in November, nothing was manipulated with it.
Click to expand...
Click to collapse
Hi,
I've had exactly the same screen on boot, find a way to exit and recover my firestick 4K with a keyboard (not wireless connected to USB) and press Alt + Print Screen + c (not "i" as i see everywhere), depending on keyboard layout you'll have to press Fn for Print Screen.
Successfully restarted my stick without loosing any data or app.
Hope it will help ;-)

Categories

Resources