Develop Bugs

towelroot support broken

Turned my Fire TV on to an update notification. Updated hoping for more features, i.e.Prime Music use but to no avail. It also had the added (dis)benefit of disabling root and preventing towelroot from reenabling. Any thoughts?
One interesting thing I found out is that it is possible to enable installation from unknown sources with out editing the original settings.apk.

halftonehero said:
Turned my Fire TV on to an update notification. Updated hoping for more features, i.e.Prime Music use but to no avail. It also had the added (dis)benefit of disabling root and preventing towelroot from reenabling. Any thoughts?
One interesting thing I found out is that it is possible to enable installation from unknown sources with out editing the original settings.apk.
Click to expand...
Click to collapse
So you're the second person to claim to have gotten an update. I still haven't gotten it. I'd be curious to see if they've patched the bootloader. I'll have to wait until @AFTVnews.com or I get the update and get the URL to examine it. It's possible you'll be able to downgrade, but without knowing what was in the update I'm not going to encourage such an action. But if you want to try it out on your own, go right ahead. There are instructions and URLs in a few posts here. Just know if they updated the bootloader and turn on anti-downgrade flags, it might brick.

rbox said:
So you're the second person to claim to have gotten an update. I still haven't gotten it. I'd be curious to see if they've patched the bootloader. I'll have to wait until @AFTVnews.com or I get the update and get the URL to examine it. It's possible you'll be able to downgrade, but without knowing what was in the update I'm not going to encourage such an action. But if you want to try it out on your own, go right ahead. There are instructions and URLs in a few posts here. Just know if they updated the bootloader and turn on anti-downgrade flags, it might brick.
Click to expand...
Click to collapse
One of my Fire TV's tends to get updates early so hopefully it'll get updated tomorrow. I'll be sure to set it up to sniff out the update URL.

Thanks for the insight. I'll wait on downgrading at the moment with no know brick recovery method. I wonder if the other numerous one clicks used the same method as geohots?

halftonehero said:
Turned my Fire TV on to an update notification. Updated hoping for more features, i.e.Prime Music use but to no avail. It also had the added (dis)benefit of disabling root and preventing towelroot from reenabling. Any thoughts?
One interesting thing I found out is that it is possible to enable installation from unknown sources with out editing the original settings.apk.
Click to expand...
Click to collapse
Do you have a new version number you can provide us?

mcsephoenix said:
Do you have a new version number you can provide us?
Click to expand...
Click to collapse
51.1.2.0_user_512073320 according AFTV.com

Downgrade To Previous Firmware
Would downgrading to previous firmware update allow for the ability to root the Fire TV?
EDIT: Will be receiving a new Fire TV from Amazon tomorrow and if it comes with the new firmware update, I'll downgrade and report on whether it works or not. Nothing to lose on my part if it bricks as I will be able to return it to Amazon.

mjbxx said:
Would downgrading to previous firmware update allow for the ability to root the Fire TV?
EDIT: Will be receiving a new Fire TV from Amazon tomorrow and if it comes with the new firmware update, I'll downgrade and report on whether it works or not. Nothing to lose on my part if it bricks as I will be able to return it to Amazon.
Click to expand...
Click to collapse
Downgrading requires the FTV to be rooted in the first place to be able to push the update.zip to the proper location.
Edit: I noticed recovery mode (following steps here) has an option to "Update from ADB" (I assume this would use ADB sideload). However, since the FTV doesn't have an accessible USB client port, I'm not sure how or if this would work (unless they build network drivers into the recovery partition).
If this was figured out, that could be a possible method of downgrading.

elmerohueso said:
Downgrading requires the FTV to be rooted in the first place to be able to push the update.zip to the proper location.
Edit: I noticed recovery mode (following steps here) has an option to "Update from ADB" (I assume this would use ADB sideload). However, since the FTV doesn't have an accessible USB client port, I'm not sure how or if this would work (unless they build network drivers into the recovery partition).
If this was figured out, that could be a possible method of downgrading.
Click to expand...
Click to collapse
If network support was available in recovery... how would we know the ip address? I am wondering if there might USB support in recovery for ADB with male/male cable.... I don't happen to have one to test... anyone else?

I imagine the IP address would be the same but it would utilize a different port

tselling said:
If network support was available in recovery... how would we know the ip address?
Click to expand...
Click to collapse
Check the DHCP tables in your router to see which IPs have been leased to which device.

tselling said:
If network support was available in recovery... how would we know the ip address? I am wondering if there might USB support in recovery for ADB with male/male cable.... I don't happen to have one to test... anyone else?
Click to expand...
Click to collapse
I have tested this with no luck. Plugging in a male/male USB cable while on that recovery screen does nothing. The Fire TV is not seen by the PC.
I may be wrong about this, but the problem is that in order to get to that recovery screen, the Fire TV has to be in USB Host Mode. This is what allows it to recognize commands from a USB keyboard. In order to use ADB via USB and transfer the update package, the Fire TV needs to be in USB Accessory Mode. When "Update via USB" is selected, the Fire TV does not switch to USB Accessory Mode. It stays in USB Host Mode.
The only way I know of for the Fire TV to be in USB Accessory mode, is to connect the Fire TV to a PC via a male/male cable while it is powered off, and then power the Fire TV on. In this setup, it sees that it's connected to a PC and enables fastboot via USB with the USB set to Accessory Mode. In this state, plugging in a keyboard does nothing which means there is no way to get to recovery.

elmerohueso said:
Check the DHCP tables in your router to see which IPs have been leased to which device.
Click to expand...
Click to collapse
I do not believe that work if it uses a default IP address like many devices do for setup rather than dhcp.

tselling said:
I do not believe that work if it uses a default IP address like many devices do for setup rather than dhcp.
Click to expand...
Click to collapse
There is no networking code in the stock recovery. DHCP or explicit ip addresses.

rbox said:
There is no networking code in the stock recovery. DHCP or explicit ip addresses.
Click to expand...
Click to collapse
I wonder if there is a way to send our own update via network by somehow spoofing the update server that amazon uses.

tselling said:
I wonder if there is a way to send our own update via network by somehow spoofing the update server that amazon uses.
Click to expand...
Click to collapse
MITM'ing an update to the firetv is easy. But making the Fire TV download it is the hard part. When it checks for updates its a complicated encrypted exchange between the firetv and the amazon servers. I tried spoofing that and it was rejected because of the hashes. So if the firetv wants to already download an update, it would be possible for it to download something else. But that something else would still need to be a valid signed update. Can't make it download and update random code.

AFTVnews.com said:
...The only way I know of for the Fire TV to be in USB Accessory mode, is to connect the Fire TV to a PC via a male/male cable while it is powered off, and then power the Fire TV on. In this setup, it sees that it's connected to a PC and enables fastboot via USB with the USB set to Accessory Mode. In this state, plugging in a keyboard does nothing which means there is no way to get to recovery.
Click to expand...
Click to collapse
Hi,
because I'm new at the AFTV and it's just ordered (I prefer to have it at my hands when I post ideas ) BUT what will happen, if you use your described way to get it to connect to PC, but not using power off/on , but using 'adb reboot recovery' via network?
BTW: OT does 'Image Verification' will stop after a count of posts or do I have to do it always?

got this update today by auto update (got the box and tried blocking domains but doesn't work)
51.1.3.0_user_513011820
any chance to root or downgrade the box now or just replace it by amazon?

Hitchi said:
got this update today by auto update (got the box and tried blocking domains but doesn't work)
51.1.3.0_user_513011820
any chance to root or downgrade the box now or just replace it by amazon?
Click to expand...
Click to collapse
I feel sorry for you Bro, same here. Hope that towelroot or an other solution will come soon.
RA

Hitchi said:
got this update today by auto update (got the box and tried blocking domains but doesn't work)
51.1.3.0_user_513011820
any chance to root or downgrade the box now or just replace it by amazon?
Click to expand...
Click to collapse
Do you have a German Fire TV? I'm trying to determine if this new update is only being pushed to German Fire TVs.

Strange happenings from the Amazon update server today!

I had 2 units that had not been programmed before and tried the trick with pulling the ethernet cable as the light turned white.....didn't work.... I tried several times and it would always come up with the message that there was no connection. I finally decided for simply chalk it up to having 2 unrooted units....no big deal..... So.... I connected directly to the internet with no blocks and let the unit go ahead and download the "latest" firmware. To my great surprise when I finally got done and went to check the version which I was certain would be the 4.0 I actually had 51.0.2.0! Both units rooted. I have no idea what was going on, but it seems as though the Amazon server was updating with that version today....or at least that's the best theory I can come up with. It did go through the entire download and installed, but I got rootable firmware out of it! Go figure. If the server is screwing up and anyone else can try it, that would confirm it. Everything loaded fine....the only thing that didn't work after all was done was that the FTV utility here didn't block updates when I selected for it to do it and ADB shows update enabled. I'm going to try again later, but xposed, supersu, stickmount, towelroot and everything else works fine. I just can't get the utility to block like it normally does. Any ideas on blocking? Any ideas on why the server might be giving out that firmware today?
I'm very puzzled over it.....but quite happy about it!

fxbill said:
I had 2 units that had not been programmed before and tried the trick with pulling the ethernet cable as the light turned white.....didn't work.... I tried several times and it would always come up with the message that there was no connection. I finally decided for simply chalk it up to having 2 unrooted units....no big deal..... So.... I connected directly to the internet with no blocks and let the unit go ahead and download the "latest" firmware. To my great surprise when I finally got done and went to check the version which I was certain would be the 4.0 I actually had 51.0.2.0! Both units rooted. I have no idea what was going on, but it seems as though the Amazon server was updating with that version today....or at least that's the best theory I can come up with. It did go through the entire download and installed, but I got rootable firmware out of it! Go figure. If the server is screwing up and anyone else can try it, that would confirm it. Everything loaded fine....the only thing that didn't work after all was done was that the FTV utility here didn't block updates when I selected for it to do it and ADB shows update enabled. I'm going to try again later, but xposed, supersu, stickmount, towelroot and everything else works fine. I just can't get the utility to block like it normally does. Any ideas on blocking? Any ideas on why the server might be giving out that firmware today?
I'm very puzzled over it.....but quite happy about it!
Click to expand...
Click to collapse
I'm sort of lost on what you are saying.
You say both units are unrooted, and you updated, got a 5.xxxx update and now both are rootable?
Nice. That being said, I'm going to point out what I got my AFTV and I blocked the update servers in my router, it still said it was updating when I first turned it on, but it wasn't.

fxbill said:
I had 2 units that had not been programmed before and tried the trick with pulling the ethernet cable as the light turned white.....didn't work.... I tried several times and it would always come up with the message that there was no connection. I finally decided for simply chalk it up to having 2 unrooted units....no big deal..... So.... I connected directly to the internet with no blocks and let the unit go ahead and download the "latest" firmware. To my great surprise when I finally got done and went to check the version which I was certain would be the 4.0 I actually had 51.0.2.0! Both units rooted. I have no idea what was going on, but it seems as though the Amazon server was updating with that version today....or at least that's the best theory I can come up with. It did go through the entire download and installed, but I got rootable firmware out of it! Go figure. If the server is screwing up and anyone else can try it, that would confirm it. Everything loaded fine....the only thing that didn't work after all was done was that the FTV utility here didn't block updates when I selected for it to do it and ADB shows update enabled. I'm going to try again later, but xposed, supersu, stickmount, towelroot and everything else works fine. I just can't get the utility to block like it normally does. Any ideas on blocking? Any ideas on why the server might be giving out that firmware today?
I'm very puzzled over it.....but quite happy about it!
Click to expand...
Click to collapse
The version on the Fire TV at the time of the update dictates what version gets pushed to it. I think for some reason, the original firmware version is unable to update directly to the latest, so they push an old one to get it ready for the latest. This has been seen multiple times before.

Sorry.....neither unit had ever bee set up, but since I couldn't disconnect the internet or have the 2 updates sites blocked and get the unit to progress with it's setup I finally just connect it directly to the internet and allowed the unit to download what I have always gotten a the 4.0 newest firmware. Today...connected directly to the internet and allowing Amazon to download the "latest" firmware and install it I ended up with very early firmware being installed to it.

Sorry....double post
Thank you for the logical answer to this. I thought I'd died and gone to heaven for a while!lol

fxbill said:
Sorry....double post
Thank you for the logical answer to this. I thought I'd died and gone to heaven for a while!lol
Click to expand...
Click to collapse
One thing that still puzzles me though... there are the only 2 rooted units that the FTV utility will not automatically block updates on when I select that option. What other way is there to do that?..( in layman terms!lol)
Never mind... I finally got it to block... I tried the command in ADB with no success and out of desperation reset the unit, started from scratch and disabled updates before loading XBMC... That worked and everything went smoothly after that. I have no idea why that worked, but it did.

Help with confusing AFTV issues

Last night I wiped data/factory reset in cwm after experiencing some issues. When the main menu returned I noticed it loaded very slow and I thought there might be other problems, but then it started to behave normally and continued to as I disabled updates, installed kodi, llama, busybox, and es explorer. All was working fine. I setup kodi very basic (just scanned in Genesis and my local library) Couple of hours later, I exited Kodi to install netflix. Mind you, this was late so I don't remember exactly what I was doing but definitely nothing nefarious.
Basically the main menu had some lag. Kodi had trouble relaunching so I thought a reboot might be helpful. I rebooted--it went from boot menu to amazon (white) to amazon (colored) and all appeared fine till the screen turned to snow. This lasted like 10 seconds then it went back to the amazon fire tv (white and yellow logo) and it hung there at least ten minutes before I pulled the plug. Tried it again and replugged it in and it did the same sequence, hanging on amazon yellow and white.
I was pretty sure I was bricked because I couldn't connect over adb, but not too freaked out because rbox boot menu was still showing up. So today the plan was to use the boot menu to get to recovery and push and older firmware, WHICH I HAVE QUESTIONS ABOUT...
BUT when I plugged the aftv back in this morning it went through a normal boot sequence and right to the main menu like normal. It's very strange I have no idea what's happening to be honest but I'd like to revert my firmware back to an earlier version. After reading some posts it seems if you skip firmwares and install a later version you might have issues so I'm hoping that's what I did here and some of the bugs might be fixed by installing older firmware.
This aftv is running the latest 51.1.4.1 It has an unlocked bootloader and as I said rbox boot menu. Is there anything I need to do to revert from here? (lock bootloader?) Or can I just push the zip according to the guide and install it?
That's my main concern since I've never gone backward with the updates. Also***Obviously***if you have any theories as to what the heck was happening with my aftv last night--please share! I know there's not much info provided but this post is already a little long. But of course if you're interested in trying to diagnose I'd be happy to provide whatever details you need. Thanks.

Simliar Situation
KLit75 said:
Last night I wiped data/factory reset in cwm after experiencing some issues. When the main menu returned I noticed it loaded very slow and I thought there might be other problems, but then it started to behave normally and continued to as I disabled updates, installed kodi, llama, busybox, and es explorer. All was working fine. I setup kodi very basic (just scanned in Genesis and my local library) Couple of hours later, I exited Kodi to install netflix. Mind you, this was late so I don't remember exactly what I was doing but definitely nothing nefarious.
Basically the main menu had some lag. Kodi had trouble relaunching so I thought a reboot might be helpful. I rebooted--it went from boot menu to amazon (white) to amazon (colored) and all appeared fine till the screen turned to snow. This lasted like 10 seconds then it went back to the amazon fire tv (white and yellow logo) and it hung there at least ten minutes before I pulled the plug. Tried it again and replugged it in and it did the same sequence, hanging on amazon yellow and white.
I was pretty sure I was bricked because I couldn't connect over adb, but not too freaked out because rbox boot menu was still showing up. So today the plan was to use the boot menu to get to recovery and push and older firmware, WHICH I HAVE QUESTIONS ABOUT...
BUT when I plugged the aftv back in this morning it went through a normal boot sequence and right to the main menu like normal. It's very strange I have no idea what's happening to be honest but I'd like to revert my firmware back to an earlier version. After reading some posts it seems if you skip firmwares and install a later version you might have issues so I'm hoping that's what I did here and some of the bugs might be fixed by installing older firmware.
This aftv is running the latest 51.1.4.1 It has an unlocked bootloader and as I said rbox boot menu. Is there anything I need to do to revert from here? (lock bootloader?) Or can I just push the zip according to the guide and install it?
That's my main concern since I've never gone backward with the updates. Also***Obviously***if you have any theories as to what the heck was happening with my aftv last night--please share! I know there's not much info provided but this post is already a little long. But of course if you're interested in trying to diagnose I'd be happy to provide whatever details you need. Thanks.
Click to expand...
Click to collapse
I am experiencing the same issue. I tried re-installing the ROM.zip file I had left on it and it installs but it still will not start up. I just keep getting stuck on the white and yellow logo. Is there anyway to install a boot.img and unzip it in recovery that you are aware of? I was running SPMC w/ boot.
I kind of feel I should of let it alone like you did, and it might have fixed itself.

Well...it didn't fix itself
Kul-Aid23 said:
I am experiencing the same issue. I tried re-installing the ROM.zip file I had left on it and it installs but it still will not start up. I just keep getting stuck on the white and yellow logo. Is there anyway to install a boot.img and unzip it in recovery that you are aware of? I was running SPMC w/ boot.
I kind of feel I should of let it alone like you did, and it might have fixed itself.
Click to expand...
Click to collapse
Yes. It was running fine. Last nite I pushed 51.1.4.0 and it installed fine. In fact this aftv ran bug free all nite. This morning I noticed it wasn't in sleep mode (typical) I just hit the home button and usually it sleeps shortly after. Not this time.
So I turned on my TV and the home screen was there but navigating Very slow so I rebooted. It hung longer than usual on amazon white then the snow screen reappeared then it went to normal colored amazon then it hung on amazon white and yellow! I left it alone 20 minutes but it remained. BTW_rbox boot menu is gone. I hope I get it back. Gonna try a keyboard to get recovery.
Edit__keyboard got me to home screen not recovery?! Weird...If anyone has a clue please chime in. My next move (logically...I guess) is to push 51.1.4.1 because that was my initial fix for Netflix but this issue started before I changed anything. 2 different firmwares--same issue. So I don't think that's it. But it possible I should've maybe cleared dalvik before flashing. However I did do a factory reset in cwm just 24 hours prior to flashing 51.1.4.0 I'm over my head as far as troubleshooting goes. I can say it ran excellent last night with 51.1.4.0 and then it wouldn't boot. Now its running excellent again. If I had to guess the bug is triggered by idle time however, the first time this occurred I was using xbmc and having issues and I rebooted to snow so its not just that.
This seems to be an uncommon issue but I've followed those guides to a tee. After wiping and flashing I have 3 apps--es file, llama and kodi. Same apps, same firmware as my other aftv that doesn't give me problems. Only difference is history. The new aftv had a much more involved process to root, downgrade and get to 51.1.4.0

Yours messed up again?
KLit75 said:
Yes. It was running fine. Last note I pushed 51.1.4.0 and it installed fine. In fact this aftv ran bug free all nite. This morning I noticed it wasn't in sleep mode (typical) I just hit the home button and usually it sleeps shortly after. Not this time.
So I turned on my TV and the home screen was there but navigating Very slow so I rebooted. It hung longer than usual on amazon white then the snow screen reappeared then it went to normal colored amazon then it hung on amazon white and yellow! I left it alone 20 minutes but it remained. BTW_rbox boot menu is gone. I hope I get it back. Gonna try a keyboard to get recovery.
Click to expand...
Click to collapse
Is your screwy again? Does this have anything to do with the new AFTV update? BC I had updates blocked on my router and device. Let me know if you figure anything out. I tried reinstalling the ROM and it said it installed but I'm still in the loop after.

Kul-Aid23 said:
Is your screwy again? Does this have anything to do with the new AFTV update? BC I had updates blocked on my router and device. Let me know if you figure anything out. I tried reinstalling the ROM and it said it installed but I'm still in the loop after.
Click to expand...
Click to collapse
I didn't block them on the router. I only did that when I was rooting my new aftv about a month ago. But I'm obsessive about making sure they're disabled on the box. If they snuck something in ota you'd think both my boxes would be messed up--not the case.
Btw--if this was deliberate its messed up and I won't be buying anything from them ever again.
But now you got me paranoid. I'll block on the router again. Kind of a hassle because my router doesn't support it with stock. I need to ping the site with my Mac and do it manually but I will. I only bought a second one because android TV is a possibility. My other amazon product is running cm 11 over clocked and its laughable how well it runs by comparisdon--good hardware/bad os. But I didn't come here to rant. Any suggestions?
Edit--sorry I sort of blew you off there. Try a keyboard. Wait for amazon then hold Ctrl alt. Print screen. I did a combo of holding a pressing the keys and it booted. But it looks like this will continue. Hopefully we find a fix.

More info
I jumped the gun a bit when I said it was working. Yes I can navigate the main menu and the few apps I have open and work fine. But this is interesting...it doesn't appear to sleep after 30 minutes or so, like usual, so I went into "Display" on the menu. Sometimes when I do this it will just open a blank window and crash menu (unresponsive, cant move) Sometimes it will let me open the window but when I press "screensaver" it crashes again. This location seems to be prohibited for some reason. BUT...it reboots normally.
Question--I had unlocked the bootloader prior to flashing 51.1.4.0 last night. As I type I don't think that has anything to do with it. And thinking about it it displayed the same behavior when I was running 51.1.4.1 the night before with bootloader unlocked so I don't think that has any relevance. You know what I've got other options for the bedroom tv. For now I'm going to keep it unplugged, block updates on the router and hope people have theories.
Although at this point blocking updates on the router seems a little like locking the door to the Hen house after the Wolf has already entered...it'll still make me feel better if for no other reason than I own another aftv (using it now and it works fine.)

Kul-Aid23 said:
Is your screwy again? Does this have anything to do with the new AFTV update? BC I had updates blocked on my router and device. Let me know if you figure anything out. I tried reinstalling the ROM and it said it installed but I'm still in the loop after.
Click to expand...
Click to collapse
You're issue may be different than mine. You're not getting the snow screen then it hangs.
Did you try to flash the later firmware without the latest version of CWM? Or try the latest with Rbox boot menu?

KLit75 said:
You're issue may be different than mine. You're not getting the snow screen then it hangs.
Did you try to flash the later firmware without the latest version of CWM? Or try the latest with Rbox boot menu?
Click to expand...
Click to collapse
I'm not sure I know what you mean, like which files to install on it or if I can. I can't ADB into it, I can only run zip files through CWM. I tried loading the last ROM I installed on it and nothing changes. I had put up a forum for it:
http://forum.xda-developers.com/fire-tv/help/aftv-bricked-reward-t3022426
I am debating trying different ROMs as well. I just don't want to lose CWM or else I'm bricked for sure.
And we might be having different issues. Bc mine loads boot loader where I can pick the boot kernel or CWM. But when it goes to boot kernel it just sits on that White and yellow Amazon screen. I don't encounter any static.

Which domains are you blocking?
Kul-Aid23 said:
Is your screwy again? Does this have anything to do with the new AFTV update? BC I had updates blocked on my router and device. Let me know if you figure anything out. I tried reinstalling the ROM and it said it installed but I'm still in the loop after.
Click to expand...
Click to collapse
Kul-Aid23 said:
I'm not sure I know what you mean, like which files to install on it or if I can. I can't ADB into it, I can only run zip files through CWM. I tried loading the last ROM I installed on it and nothing changes. I had put up a forum for it:
http://forum.xda-developers.com/fire-tv/help/aftv-bricked-reward-t3022426
I am debating trying different ROMs as well. I just don't want to lose CWM or else I'm bricked for sure.
And we might be having different issues. Bc mine loads boot loader where I can pick the boot kernel or CWM. But when it goes to boot kernel it just sits on that White and yellow Amazon screen. I don't encounter any static.
Click to expand...
Click to collapse
I just meant, some people have attempted to install roms that require boot menu and the result is a brick but that's not you I guess since you get the boot menu. Mine skips boot menu now and goes right to homescreen which i guess means boot menu is no longer present after flashing 51.1.4.0
still boots fine after at least a half dozen reboots. But i do have a question for you...which domains are you blocking? Because I used the 3 from aftvnews. First for the aftv with issues which is unplugged so I didn't notice. The other one is on and playing prime. I blocked one (not sure which) then blocked another and Ive got a toddler screaming at me...Elmo dissapeared. My son was watching prime and it turned off. This is why I didn't keep updates blocked on the router for fear it would deny access to everything. But I couldn't even get an internet connection! At least one of the domains keeps amazon content but one...or 2 cut the aftv from the network! I have a wired connection and I couldn't get it back. Granted my son was screaming so I didn't have time to thoroughly troubleshoot but it appears blocking all those domains just isnt an option even if you did go without prime. So are you able to block all 3 domains from the guide and still connect? I tried rebooting and configuring the network.
BTW--brilliant idea offering a cash reward for the fix! I never would've thought of that.
Here's one thing I just thought of regarding my issues and it may be nothing but...it seems EVERYTIME my AFTV has booted to snow and then hung, I had a flash drive plugged directly into usb with the drive mounted persistent. Now I haven't tested this thoroughly, but when it boots so far it has NO flash drive and HAS HAD a usb keyboard plugged in. CTRL, PRINT Alt doesn't get me to recovery but it just boots to homescreen normally. MAYBE pressing those buttons did nothing. MAYBE the keyboard did NOTHING. But in fact, for my troubles it has something to do with the flash drive??? Or usb port???
Obviously I'm not a programmer or software/hardware expert but there are people here that could confirm it's a possibility or that's stupid. I'm just trying to narrow it down by providing info and that hadn't occurred to me until 10 minutes ago. Unfortnately my time is running out for now. I'll check back later and hope one or both of us has a solution or something to help get us there.
Keep me posted. Sorry I'm not sure why yours won't boot. It seems your doing everything right and even took it a step further to keep updates away.
EDIT--Possible I screwed up blocking updates on router. Like I said it's very tedious and I was distracted. I MAY have selected to block all internet access to that aftv. Makes sense since no one else had an issue there. But to confirm--does blocking these domains cause any issues accessing prime? Sorry about the long post.

BINGO!
So if you read the last post you'll see I suspected my AFTV booting into snow then hanging had something to do with the usb flash drive. Correct!
I unplugged the keyboard, plugged in the flash drive, and powered it on. It went from amazon white to SNOW to hanging amazon yellow and black. Unplugged the aftv, unplug the flash drive, powered on...it booted right to the homescreen. Corrupted flash drive? Issue with samba on startup? I don't know but would love to hear ideas...
EVERYONE has had corrupted hdd, sdcards and flash drives but for me it's never affected booting. This is still weird.
Also, though the fire menu navigation is fast and fluid, all apps work properly....there's STILL the issue with the Display section of the menu. It lets me click it. It lets me click screensaver BUT when it do it still crashes (sort of). Though I can't press back to escape or directional arrows, hitting the home button brings me back and it all works again. So maybe flashing the newest firmware from here will fix it but given the issues others are having I don't want to be too hasty. I'm looking for answers. It's running fine and the boot issue seems directly tied to the flash drive but that doesn't explain the issue with the Display/screensaver options...
I feel like I should intervene but without the boot menu currently installed I think I should sit tight and search/wait for some more ideas.

KLit75 said:
I just meant, some people have attempted to install roms that require boot menu and the result is a brick but that's not you I guess since you get the boot menu. Mine skips boot menu now and goes right to homescreen which i guess means boot menu is no longer present after flashing 51.1.4.0
still boots fine after at least a half dozen reboots. But i do have a question for you...which domains are you blocking? Because I used the 3 from aftvnews. First for the aftv with issues which is unplugged so I didn't notice. The other one is on and playing prime. I blocked one (not sure which) then blocked another and Ive got a toddler screaming at me...Elmo dissapeared. My son was watching prime and it turned off. This is why I didn't keep updates blocked on the router for fear it would deny access to everything. But I couldn't even get an internet connection! At least one of the domains keeps amazon content but one...or 2 cut the aftv from the network! I have a wired connection and I couldn't get it back. Granted my son was screaming so I didn't have time to thoroughly troubleshoot but it appears blocking all those domains just isnt an option even if you did go without prime. So are you able to block all 3 domains from the guide and still connect? I tried rebooting and configuring the network.
BTW--brilliant idea offering a cash reward for the fix! I never would've thought of that.
Here's one thing I just thought of regarding my issues and it may be nothing but...it seems EVERYTIME my AFTV has booted to snow and then hung, I had a flash drive plugged directly into usb with the drive mounted persistent. Now I haven't tested this thoroughly, but when it boots so far it has NO flash drive and HAS HAD a usb keyboard plugged in. CTRL, PRINT Alt doesn't get me to recovery but it just boots to homescreen normally. MAYBE pressing those buttons did nothing. MAYBE the keyboard did NOTHING. But in fact, for my troubles it has something to do with the flash drive??? Or usb port???
Obviously I'm not a programmer or software/hardware expert but there are people here that could confirm it's a possibility or that's stupid. I'm just trying to narrow it down by providing info and that hadn't occurred to me until 10 minutes ago. Unfortnately my time is running out for now. I'll check back later and hope one or both of us has a solution or something to help get us there.
Keep me posted. Sorry I'm not sure why yours won't boot. It seems your doing everything right and even took it a step further to keep updates away.
EDIT--Possible I screwed up blocking updates on router. Like I said it's very tedious and I was distracted. I MAY have selected to block all internet access to that aftv. Makes sense since no one else had an issue there. But to confirm--does blocking these domains cause any issues accessing prime? Sorry about the long post.
Click to expand...
Click to collapse
I had these 3 blocked via my router
amzdigitaldownloads.edgesuite.net (amzdigitaldownloads.edgesuite.ne though bc router limits # of charcters)
softwareupdates.amazon.com
updates.amazon.com
But i noticed the last comment on this link: http://www.aftvnews.com/how-to-block-software-updates-on-the-fire-tv-stick/
Maybe my AFTV lost internal OTA blocking at some point then got updated, but since I was using a different boot image, it can't boot now. Does that sound possible?
---------- Post added at 08:16 PM ---------- Previous post was at 08:11 PM ----------
Kul-Aid23 said:
I had these 3 blocked via my router
amzdigitaldownloads.edgesuite.net (amzdigitaldownloads.edgesuite.ne though bc router limits # of charcters)
softwareupdates.amazon.com
updates.amazon.com
But i noticed the last comment on this link: http://www.aftvnews.com/how-to-block-software-updates-on-the-fire-tv-stick/
Maybe my AFTV lost internal OTA blocking at some point then got updated, but since I was using a different boot image, it can't boot now. Does that sound possible?
Click to expand...
Click to collapse
Actually check out the bottom of this one where everyone is commenting on http://www.aftvnews.com/how-to-block-amazon-fire-tv-update-to-ensure-rooting/
I think I may have been updated then bricked.

Kul-Aid23 said:
I had these 3 blocked via my router
amzdigitaldownloads.edgesuite.net (amzdigitaldownloads.edgesuite.ne though bc router limits # of charcters)
softwareupdates.amazon.com
updates.amazon.com
But i noticed the last comment on this link: http://www.aftvnews.com/how-to-block-software-updates-on-the-fire-tv-stick/
Maybe my AFTV lost internal OTA blocking at some point then got updated, but since I was using a different boot image, it can't boot now. Does that sound possible?
---------- Post added at 08:16 PM ---------- Previous post was at 08:11 PM ----------
Actually check out the bottom of this one where everyone is commenting on http://www.aftvnews.com/how-to-block-amazon-fire-tv-update-to-ensure-rooting/
I think I may have been updated then bricked.
Click to expand...
Click to collapse
That's not what happened to you. I know right about now you're probably frustrated but the first article you linked was for fire tv stick (not fire tv). The fire tv stick doesn't have root, therefore they need to block on router because there is no way to disable updates otherwise. We can pm disable.
The 2nd article --check out the date--it's from may. We didn't get root till like mid june. So at that point people were trying to stay on low firmware in hopes when root came they'd be able to root!
It's unlikely you got an update if you blocked them on the box and you're sure you did. Especially with custom recovery, which you have. Even if you forgot to block them it's not likely they would install. Amazon would try, your box would likely boot itself to recovery like mine did when I forgot to block them after wiping data in CWM.
This doesn't help with your issue I know but I think you can look elsewhere as to the-- why it happened? There is maybe the slimmest chance an update could sneak through BUT if it happened to you I think lots of other people would be complaining of bricked devices. Hang in there. Hopefully we find a fix soon.

Might be able to help
I'm a long time lurker on these forums for all of my devices, but I just had this happen the other night. I had downgraded firmware, installed cwm, boot menu, and fully unlocked bootloader. When I went to upgrade to the latest custom rom (51.1.5.0?), I wiped data in cwm and ended up stuck on the Fire Tv splashscreen WITH NO BOOT MENU!! Therefore I could not boot to recovery or access via ADB. I was able to recover it by splicing some usb cables together that I had laying around to make a USB A to A cable, Installing the usb drivers for the kindle fire on my PC, and connecting it before powering on. Used cmd window and fastboot erased the boot partition and fastboot flashed @rbox bootmenu.img to the partition. Disconnected the USB cable and rebooted to find the boot menu back and able to access recovery!! Hopefully this can help you, or someone else that finds themselves in a similar predicament.
Edit: Once in CWM install zip via sideload then connect to ADB from PC to push the ROM

Firetv2 help required with rooting _almost there_

Hi all,
I've followed with meticulous care the video and web page over at aftvnews for rooting my aftv2...
Everything went perfectly, up to one point,... Instead of just flashing the sloane-5.0.5-rooted_r4.zip (I also placed a check in the checksum box).... strangely it failed the checksum,.... and I decided to choose to reboot.
After checking the sloane-5.0.5-rooted_r4.zip md5 it was okay.... strangely i don't know why it failed.
But now all my firetf2 does is boot directly to the amazon home page. (I still have adb and usb debugging enabled).
All I had connected to the firetv2 was a usb mouse to enable me to click the relevant items within recovery.
Is there any way I can get back into the first TeamWin boot window so that I can actually flash the sloane-5.0.5-rooted_r4.zip file.
I did have a usb hub connected as well, with a usb keyboard just in case I needed it, but thought that it might be the problem so i just left the mouse connected.
Every single part went through perfectly installing adb and fastboot,... installing the mt6577 usb drivers.
connecting the firetv2 via a to a cable, and also running the install_firetv2_recovery.bat file.
Not one single problem until this last bit.
Could do with a couple of pointers please chaps as i can almost see the finish line.
---------------
hhmmmm I rather stupidly left the ramdisk-recovery.cpio.lzma file off the SD card when I wanted to get back into the boot menu.
This time the checksum passed, and rooted firmware went on without any problems.
about to click "reboot system" in preparation of crapping myself....
Hoping that someone can see the final screen attached and tell me if this is okay..

slackbladder said:
Hi all,
I've followed with meticulous care the video and web page over at aftvnews for rooting my aftv2...
Everything went perfectly, up to one point,... Instead of just flashing the sloane-5.0.5-rooted_r4.zip (I also placed a check in the checksum box).... strangely it failed the checksum,.... and I decided to choose to reboot.
After checking the sloane-5.0.5-rooted_r4.zip md5 it was okay.... strangely i don't know why it failed.
But now all my firetf2 does is boot directly to the amazon home page. (I still have adb and usb debugging enabled).
All I had connected to the firetv2 was a usb mouse to enable me to click the relevant items within recovery.
Is there any way I can get back into the first TeamWin boot window so that I can actually flash the sloane-5.0.5-rooted_r4.zip file.
I did have a usb hub connected as well, with a usb keyboard just in case I needed it, but thought that it might be the problem so i just left the mouse connected.
Every single part went through perfectly installing adb and fastboot,... installing the mt6577 usb drivers.
connecting the firetv2 via a to a cable, and also running the install_firetv2_recovery.bat file.
Not one single problem until this last bit.
Could do with a couple of pointers please chaps as i can almost see the finish line.
---------------
hhmmmm I rather stupidly left the ramdisk-recovery.cpio.lzma file off the SD card when I wanted to get back into the boot menu.
This time the checksum passed, and rooted firmware went on without any problems.
about to click "reboot system" in preparation of crapping myself....
Hoping that someone can see the final screen attached and tell me if this is okay..
Click to expand...
Click to collapse
Are you installing sloane-5.0.5-rooted_r4.zip from recovery?
It looks like it installed OK but even so if you already have recovery installed you still have a way back in.....so no worry.

That's what I was gonna say, seems ok to me?
If it won't boot Into recovery or won't boot follow this guide here -
http://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349
But if you can access recovery with a keyboard press or via adb just follow the guide on aftvnews but since you have already tried to root don't use the installer just flash the prerooted rom (if needed redownload the zip check the md5 checksums & flash In recovery)

Thanks for the details chaps....
I persevered and following the detailed info from aftvnews I used the cmd and typed su..... after pressing enter i had about 3 seconds before the little box that you have to press on "enable" disappeared... managed it on my third attempt. I don't remember reading that one has to use the firetv remote to click on "Enable". but it worked.
command prompt says [email protected] so it looks to be successful.
also blocked updates as well. now if only i could root my firetv v1's i could get rid of opendns.
but using the calculator over at aftvnews (when I could get on there} states that both my firetv1's are not rootable versions due to the serial numbers.
just one other thing chaps.... to be able to load rbox's twrp,.... is that only possible via an sd card plugged in and using ramdisk-recovery.cpio.lzma and then switching on firetv?
just wondering chaps.... are there any uk people here who can still access aftvnews. I only ask as the site went down last night about 3.30 am gmt.
I've had a mate whose on BT and he has full access another mate on sky tested it for me and its okay.
I can access it if I use Tor Browser but other than that it keeps timing out on me and I'm on vermin..
Another piece I almost got lost at, was where you have to click on the three arrows "Swipe to confirm" well I thought it had gone wrong on the page before that, due to another blue page with arrows on..... no mention of that in the video.
Now after all that,.. I assume I still have to sideload kodi?

slackbladder said:
Thanks for the details chaps....
I persevered and following the detailed info from aftvnews I used the cmd and typed su..... after pressing enter i had about 3 seconds before the little box that you have to press on "enable" disappeared... managed it on my third attempt. I don't remember reading that one has to use the firetv remote to click on "Enable". but it worked.
command prompt says [email protected] so it looks to be successful.
also blocked updates as well. now if only i could root my firetv v1's i could get rid of opendns.
but using the calculator over at aftvnews (when I could get on there} states that both my firetv1's are not rootable versions due to the serial numbers.
just wondering chaps.... are there any uk people here who can still access aftvnews. I only ask as the site went down last night about 3.30 am gmt.
I've had a mate whose on BT and he has full access another mate on sky tested it for me and its okay.
I can access it if I use Tor Browser but other than that it keeps timing out on me and I'm on vermin..
Another piece I almost got lost at, was where you have to click on the three arrows "Swipe to confirm" well I thought it had gone wrong on the page before that, due to another blue page with arrows on..... no mention of that in the video.
Now after all that,.. I assume I still have to sideload kodi?
Click to expand...
Click to collapse
You lost me here but glad you managed to finish the installation.
BTW if your FireTv1 is on OS5 you can rooted with kingroot. You need to provide more info to be able to help you furthermore.

Now youve rooted dont forget to block updates via adb! You need a keyboard to access twrp like I said before, no sd card In the aftv2 doesn't matter, you can still access twrp. Yes you can root the aftv gen 1 using Kingroot (please do not use super sume afterwards people have bricked after using super sume!) Block updates & wait for the recovery & prerooted rom by rbox to be released. Yes of course you need to sideload Kodi if you want to, Kodi is not suppled with any root/recovery or rom. Sideload via your phone/adb/adbfire/ftp or es file explorer.
Sent from my SM-G900F using Tapatalk

Thanks bula1ca,
I Updated one firetv1 the other day to 5.0.5 and then pulled the plug..... I'm hoping that rbox will come up with a working rom that i can use.
for the time being my other firetv1 is using 51.1.6.3. (it seems a lot smoother than 5.0.5). or maybe that's just me.
the firetv2 had two ota updates to get to 5.0.5. I had a little panic, I was expecting another update to block the rooting process.
also I was rather surprised how easy it was to root,... I think if i had to do it again,... instead of the 8 hours it took me, it would be more like 45 minutes now... lol
I must admit that I was constantly checking every little thing I was doing.... writing down notes for reference and trying to look at half a dozen open web pages to see how others had done it.
Going to be a problem for me though if I cannot access aftvnews any more....
---------------------------------
Thanks for the info deanr1977,...
I did try to use a keyboard but the firetv2 just kept on booting all the way to the home screen no matter what i did.
This was before I had actually installed the rom though, so this may well explain why I could get to the twrp recovery menu.
Is there a time limit as to how quickly you have to press a particular set of keys on a keyboard to get the recovery menu to show up?

slackbladder said:
Thanks bula1ca,
I Updated one firetv1 the other day to 5.0.5 and then pulled the plug..... I'm hoping that rbox will come up with a working rom that i can use.
for the time being my other firetv1 is using 51.1.6.3. (it seems a lot smoother than 5.0.5). or maybe that's just me.
the firetv2 had two ota updates to get to 5.0.5. I had a little panic, I was expecting another update to block the rooting process.
also I was rather surprised how easy it was to root,... I think if i had to do it again,... instead of the 8 hours it took me, it would be more like 45 minutes now... lol
I must admit that I was constantly checking every little thing I was doing.... writing down notes for reference and trying to look at half a dozen open web pages to see how others had done it.
Going to be a problem for me though if I cannot access aftvnews any more....
Click to expand...
Click to collapse
Sure it will be back up soon, I'm in the UK & can access it fine so just sure it will only be a matter of time & it will be back up & running at your end?
Sent from my SM-G900F using Tapatalk

deanr1977 may I ask are you a vermin media customer? I'm trying to find out why it's only me.

slackbladder said:
deanr1977 may I ask are you a vermin media customer? I'm trying to find out why it's only me.
Click to expand...
Click to collapse
you mean Virgin Media? yes
You have around 10 or 6 seconds to select boot normal to the left or boot to twrp to the right.
I use a Logitech K400 plus keyboard, works perfectly & also has a touch keypad which comes in very handy to those apps which need a mouse to access.
This one here -
http://www.amazon.co.uk/Logitech-Wireless-Keyboard-QWERTY-Layout/dp/B00XJ3LVPI

No honestly mate.... i really do mean vermin... ever since they took over I've had no end of problems. I'd laugh if I could but it just isn't funny.
I had a look at one of those k400's in a local pcworld.... but they were asking well over the odds. I think I might go down the amazon route. cheers also for the info on the boot timing.

slackbladder said:
No honestly mate.... i really do mean vermin... ever since they took over I've had no end of problems. I'd laugh if I could but it just isn't funny.
I had a look at one of those k400's in a local pcworld.... but they were asking well over the odds. I think I might go down the amazon route. cheers also for the info on the boot timing.
Click to expand...
Click to collapse
I'm not happy with there set top box's or interface, but the Internet been fine for me, very fast almost all the time

I gave up in the and had to call them....
basically done all i could at my end... flushdns,... checked hosts, checked opendns, turned off everything except router and new VM| router (modem only mode) and tried an ipad... nope still no good. all this after a full shut down of everything and two reboots.
tried my phone,.... yep you got it right, full access to aftvnews.
whats even more stupid is that I'm using part of my wifi to access the net due to the poor 3g signal and i can access aftvnews.
Well VM staff said there's nothing wrong with network, nothing wrong at my end, and if i want access to keep using tor browser.
that's not really what i wanted to hear.
but he did mention that my IP address may have been blocked at the other end. although I'm not to sure why.
I also read some info from Elias, owner of aftvnews here... http://www.esaba.com/blog/limitations-of-siteground-vps-cloud-hosting/
seems he's not very happy either.
I've asked a bt customer to check for me,.. all okay. a sky customer... all okay,... and also yourself....
This only ever happened to me once before and that was on a forum many years ago. The owner had to unblock me so I could access the website again.
within two weeks I had been blocked again.

firetv and firestick stuck on the the update screen. and go no further .

please help i got 1 firetv and 1 firestick used from someone on craigslist that i have no contact with .
once i connect them to tv all i get is waiting for an update . and stuck on that message .
i don't get registration screen . nothing . just keep saying waiting for an update .
unplug the power plug again the first thing i get is the update screen and stay like that .
so i have no way of registering them .
any help i can pass that or register or factory setting . and help to revive my firetv and fire stick .

I'm sure they are great genius very intelligent poeple here that knows the answer Plz help it's urgent.

this a dead forum i guess

japgeisha said:
this a dead forum i guess
Click to expand...
Click to collapse
Its pretty dead around here, but if you use the search box, you'll find the answer to your problem.

firetv and firestick stuck on the the update screen. and go no further
Try holding down Right + the back button on the firestick remote for 10 seconds. This will invoke the factory reset options on your firestick.

RelmOne said:
Try holding down Right + the back button on the firestick remote for 10 seconds. This will invoke the factory reset options on your firestick.
Click to expand...
Click to collapse
thank you for your answer and time . \
i did still after reboot pair remote conect wifi and boommm same problem stuck on updates

James101 said:
Its pretty dead around here, but if you use the search box, you'll find the answer to your problem.
Click to expand...
Click to collapse
i did search of course before asking some one like you . ik not an idiot nothing in this forum much my problem .\\
i suggest if you have nothing to say just keep quiet . be part of the solution not part of the problem .

japgeisha said:
thank you for your answer and time . \
i did still after reboot pair remote conect wifi and boommm same problem stuck on updates
Click to expand...
Click to collapse
japgeisha said:
i did search of course before asking some one like you . ik not an idiot nothing in this forum much my problem .\
i suggest if you have nothing to say just keep quiet . be part of the solution not part of the problem .
Click to expand...
Click to collapse
I think on the device you where able to boot. This guide should help.
http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
Seems it is trying to install or download an update. And getting stuck.
Then do at least Method 2 if Not Rooted or Method 1 if the device IS Rooted of this guide to block them in the future.
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
Make sure you read the comments too. I sometimes find answers there.
Try to do the same on the other device too.

Y314K said:
I think on the device you where able to boot. This guide should help.
http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
Seems it is trying to install or download an update. And getting stuck.
Then do at least Method 2 if Not Rooted or Method 1 if the device IS Rooted of this guide to block them in the future.
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
Make sure you read the comments too. I sometimes find answers there.
Try to do the same on the other device too.
Click to expand...
Click to collapse
thank you for taking time to read and try to help i appreciate that .
MY PROBLEM IS THIS :
the fire stick or fire tv both new from the box stuck on update screen
they are not registered yet .
there is no way to register them . need to pass the first screen update first which don't happen .
rooted or no rooted i did not get to that point .
just want my firestivck to boot normal and get the home screen thank you

japgeisha said:
thank you for taking time to read and try to help i appreciate that .
MY PROBLEM IS THIS :
the fire stick or fire tv both new from the box stuck on update screen
they are not registered yet .
there is no way to register them . need to pass the first screen update first which don't happen .
rooted or no rooted i did not get to that point .
just want my firestivck to boot normal and get the home screen thank you
Click to expand...
Click to collapse
Sorry, misread the Wifi part. Are you sure you are not blocking any Amazon HTTP/HTTPS addresses thru your Router ? I, in the past have had problems getting thru the first boot up & update screen when blocking Amazon addresses. You might have to try to do the disable internet for that device at a specific time if your still trying to keep a Root option.

No I'm nit blocking anything
I called amazon I gave them the serial number. I was told it's registred under different name
Even if it were. I should pass the update
My guess is that. The one who bought it maybe put the update block and o end up like this
Anyway to wipe the iOS and install custom one Like formatting a pc hhhh
Thx

japgeisha said:
No I'm nit blocking anything
I called amazon I gave them the serial number. I was told it's registred under different name
Even if it were. I should pass the update
My guess is that. The one who bought it maybe put the update block and o end up like this
Anyway to wipe the iOS and install custom one Like formatting a pc hhhh
Thx
Click to expand...
Click to collapse
Not when you don't have a custom recovery like TWRP installed. If that was possible then folks that are on stock ROMS would be able to update before it's their devices turn in the new update queue.
When you first bootup your device. After the white Amazon logo but before the color Amazon logo. Do you see any reference to TWRP or some. Like a none Amazon splashscreen ?
I would call Amazon support again & ask them if there is a way to do a full Factory Reset from before it gets to the update page. I think there must be a way since it does probably have a stock recovery. Maybe a few Factory Resets will help with things. If you have access to a different internet network. You can try to get it to boot there. Maybe there is something on your current network causing a problem.
There are so many possible reasons for you problem that at this point you are just trying to get luckly & hope something works. Good Luck.

Y314K said:
Not when you don't have a custom recovery like TWRP installed. If that was possible then folks that are on stock ROMS would be able to update before it's their devices turn in the new update queue.
When you first bootup your device. After the white Amazon logo but before the color Amazon logo. Do you see any reference to TWRP or some. Like a none Amazon splashscreen ?
I would call Amazon support again & ask them if there is a way to do a full Factory Reset from before it gets to the update page. I think there must be a way since it does probably have a stock recovery. Maybe a few Factory Resets will help with things. If you have access to a different internet network. You can try to get it to boot there. Maybe there is something on your current network causing a problem.
There are so many possible reasons for you problem that at this point you are just trying to get luckly & hope something works. Good Luck.
Click to expand...
Click to collapse
no reference to TWRP. normal boot no sign of anything .
i did many times force factory reset by remote but after the boot same error hung on update screen .

japgeisha said:
no reference to TWRP. normal boot no sign of anything .
i did many times force factory reset by remote but after the boot same error hung on update screen .
Click to expand...
Click to collapse
Previous owner must of borked the update or maybe turned off the Wifi setting some how. And since there is no ADB access there is no way to clear that. When the device stalls on update. See if your Router is still assigning an IP address for it. Then try to see if you can ADB to that IP address.
I would pester Amazon everyday to try to get some replacements. Probably your best bet.

it always connect to wifi or using ethernet but i have no way how to figure out which ip is connecting to .

japgeisha said:
it always connect to wifi or using ethernet but i have no way how to figure out which ip is connecting to .
Click to expand...
Click to collapse
Your router or modem hybrid should have a way to log into & see a list of what is connected by device & IP.

japgeisha said:
it always connect to wifi or using ethernet but i have no way how to figure out which ip is connecting to .
Click to expand...
Click to collapse
Is your router set to restrict access by MAC ? Is your router DHCP disabled?

Hello I have brought firesticks from a seller on Facebook and they are all stuck on the sorry can't find an update I have done the rest and unplug it so many times still nothing is there a way to bypass this I called Amazon and they said they wouldn't be able to do anything which sucks so is there a way to get past this or somehow update it so I can get them to work

Babydoll21188 said:
Hello I have brought firesticks from a seller on Facebook and they are all stuck on the sorry can't find an update I have done the rest and unplug it so many times still nothing is there a way to bypass this I called Amazon and they said they wouldn't be able to do anything which sucks so is there a way to get past this or somehow update it so I can get them to work
Click to expand...
Click to collapse
have you find any solution ?? not able to do nothing with this fire stick tv 2.. stuck on first setup with the update

xhostluv said:
hello, i can't bypass the first update .. unable to update your fire stick tv. i have try slow internet connection, dns domain blocking, uk and us vpn to access the internet. nothin work. My Fire Stick TV with alexa voice command is just a brick. Please guys, can you help me?
update - i have call amazon and they told me the device was reported as stolen !! this is way i can't update the device. I have buy this stick from internet and was brand new and sealed.
Click to expand...
Click to collapse
NEW INFO
Ok! I have buy a new sealed Fire TV stick 2 that was reported lost/stolen! No way to bypass the update screen after connecting to internet, the device is blocked by amazon. I find a way to go to settings and check ADB Debuging and Unknown Application.
I have installed Amazon remote on my smartphone, after connecting to internet and display the error can't update i have pair my phone with the stick and press SETTINGS on my application.
After i have connected with adb from my pc
installed Hijack V3 - https://forum.xda-developers.com/amazon-fire/general/launcher-root-launcher-hijack-v2-t3561026 ;
disable bloatware https://forum.xda-developers.com/fire-tv/general/disable-bloatware-2nd-gen-fire-tv-stick-t3674629
installed https://forum.xda-developers.com/fire-tv/development/app-leanback-launcher-fire-tv-t3750451
my stick is alive