Develop Bugs

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.

Digital2 Platinum Pad 8 - D2-861G-BK

So I created this topic because there is hardly anything on the internet regarding this tablet. I just recently purchased it from Best Buy and it took me quite some time to find something that would help me root it. Finally, I tried vroot ( a rooting application) and I succeeded in rooting my tablet. I don't have the exact link I used to get vroot but a simple Google search should suffice. Anyway, I figured I'd start this topic for anyone and everyone who uses this tablet or knows of this tablet to discuss any other developments. For now, if anyone needs help rooting their tablet and getting superuser running, I'm here to help.~
For now, I hope you all can figure out how to use vroot (yes, I know it's in Chinese. I can not read Chinese but it was pretty simple to get through the process of rooting.) Anyway, I don't remember the specifics but if anyone else gets through it, I ask that you please post some details on how you did it for everyone else to get through it as well. Hopefully, with time, we can get some good stuff going with this tablet. Could anyone figure out how to get CWM Recovery running on it? I'm a bit new to this and I don't want to screw anything up.

Thanks for the heads up! I also bought this tablet about a month ago. I was impressed with how thin and light it was, and how nice and bright the (IPS) screen was, especially for a cheaper "no-name" tablet. I've since found virtually no online support for this. D2 didn't even seem to list it on their own website. Although, finally today, I found this thread, and this site: http://www.d2pad.info/index.php?option=com_content&view=frontpage&Itemid=585. Seem the model is exclusive to Best Buy.
The only problem I've had with this tablet is that on rare occasions, if the screen is left on too long, the touch controls go a bit haywire, detecting random touches all over the place, and not really responding. Simply turning the screen off and back on fixes the problem. (Also, the camera is kind of ****ty, but I don't really care about that)
Anyhow, I'll definitely be trying to root this tomorrow. I take it you didn't need any special drivers? I came across this (http://scottyzone.com/2014/03/17/connect-the-d2-961g-to-adb-using-google-usb-drivers/), which I'll try if I can't get the tablet connected to my computer properly to run Vroot.
Thanks!

arpitp said:
Thanks for the heads up! I also bought this tablet about a month ago. I was impressed with how thin and light it was, and how nice and bright the (IPS) screen was, especially for a cheaper "no-name" tablet. I've since found virtually no online support for this. D2 didn't even seem to list it on their own website. Although, finally today, I found this thread, and this site: http://www.d2pad.info/index.php?option=com_content&view=frontpage&Itemid=585. Seem the model is exclusive to Best Buy.
The only problem I've had with this tablet is that on rare occasions, if the screen is left on too long, the touch controls go a bit haywire, detecting random touches all over the place, and not really responding. Simply turning the screen off and back on fixes the problem. (Also, the camera is kind of ****ty, but I don't really care about that)
Anyhow, I'll definitely be trying to root this tomorrow. I take it you didn't need any special drivers? I came across this (http://scottyzone.com/2014/03/17/connect-the-d2-961g-to-adb-using-google-usb-drivers/), which I'll try if I can't get the tablet connected to my computer properly to run Vroot.
Thanks!
Click to expand...
Click to collapse
Thank you for bringing some needed attention to this topic! I actually used the Vroot application, rather than the software. It took a few tries but I got it to work. If you want to try the software, however, I've connected it to my computer numerous times without the need for any special drivers. Only thing I can suggest is the generic google drivers. By the way, I reverse searched the tablet's hardware and kernel and came across a duplicate device from China. It is exactly identical right down to the appearance, hardware and software to our tablet. It is called the Chuwi VX8 and the only difference is that it comes in white rather than black.
After making this discovery I came across a nice little development topic for the clone device (http://www.freaktab.com/showthread.php?16025-Chuwi-VX8-RileyROM-1-1) and it seems they've founded good amount of research into the tablet. They've come up with a rom (I've yet to test), CWM Recovery (Unable to flash. If anyone else can try, that'd be dandy.), root methods (with links), among other things. It seems that anything that would work with the Chuwi tablet SHOULD work with the Digital2 Platinum Pad 8. The same rooting method was required and everything about the two tablets is perfectly identical so I'm led to believe they're going to be able to use identical roms or recoveries. I'll look more into flashing CWM Recovery tonight and get back to you on my results.

Josh8550 said:
Thank you for bringing some needed attention to this topic! I actually used the Vroot application, rather than the software. It took a few tries but I got it to work.
Click to expand...
Click to collapse
Which app exactly are you referring to. I thought it was something in the Play Store, but no luck finding what you're referring to.

arpitp said:
Which app exactly are you referring to. I thought it was something in the Play Store, but no luck finding what you're referring to.
Click to expand...
Click to collapse
Found this link (http://products.mgyun.com/api/downjump?id=846) just for you. It should work but let me now whether or not it does. It's the exe for computers but if it doesn't work Google "vroot apk" for the app.

Josh8550 said:
Found this link (http://products.mgyun.com/api/downjump?id=846) just for you. It should work but let me now whether or not it does. It's the exe for computers but if it doesn't work Google "vroot apk" for the app.
Click to expand...
Click to collapse
As you mentioned, the link was for the (Windows) software. It requires ADB connection to a computer (usually requires special drivers).
When you said you used the application instead of the software, I assumed you used an APK. However, there is no apk of (the official) Vroot (it was designed to work through Windows). That makes me think the root app you used was something else. So I have to ask... what did you use to root this device?

vRoot is now iRoot
First off, I'd like to thank you for starting this topic. I've searched all over since I bought this tablet a couple of months ago but couldn't find any information. When I did a google search for vroot, i found http://www.mgyun.com/en/getvroot and the software is now called iRoot, and is in english. The main link on the page is for the windows ADB version, and there's a link further down the page for "iRoot for Mobile", which will give you the APK. Now that I've got root, I'll keep trying to get CWM recovery to work, and maybe we can start seeing some ROMs come out for this great device!
UPDATE: (IMPORTANT, please read): The APK does not work. or at least, I couldn't get it to work on my device. It tells you that you've got root, but doesn't really give it to you. Download the computer based exe from the link that Josh8550 posted earlier.
You will need developer permissions (Settings -> About Tablet -> tap Build Number until it tells you you're a developer).
Install ADB and Drivers on windows PC (http://forum.xda-developers.com/showthread.php?t=2588979)
Connect tablet to PC with USB cable.
Run vRoot (iRoot) on PC. Program will connect to tablet and check for root.
Click the "Get Root" button.
Wait...
Tablet will reboot.
Wait...
Program will connect to tablet and check for root.
Program should verify that you have root.
Download and Install SuperSU from the Play Store.
Open SuperSU and Update SU Binary. You will have to give SuperSU root permissions from the chinese interface (choose the box on the right, don't mark the check box).
Reboot.
Congratulations! You now have root access. Enjoy!
More info to come later...

nahrwoldinternet said:
First off, I'd like to thank you for starting this topic. I've searched all over since I bought this tablet a couple of months ago but couldn't find any information. When I did a google search for vroot, i found http://www.mgyun.com/en/getvroot and the software is now called iRoot, and is in english. The main link on the page is for the windows ADB version, and there's a link further down the page for "iRoot for Mobile", which will give you the APK. Now that I've got root, I'll keep trying to get CWM recovery to work, and maybe we can start seeing some ROMs come out for this great device!
Click to expand...
Click to collapse
Thanks man. I couldn't find the link to the apk again so that's a huge help for everyone here. I'll try to get CWM recovery working soon then I'll see about getting Cyanogenmod 11 ported over.

Rooting Digital 2 tablets
Hey everyone.
I successfully rooted with Kingo ROOT using my PC, however now Im stuck. Cant seem to find ROMs or Mods compatible with this tablet.
Any info out there would be great. Im running a 4.1.1 Jelly Bean.

Rooted now what?
Did you ever try the cwmr or cyanogen ROM you had mentioned above?

[email protected] said:
Did you ever try the cwmr or cyanogen ROM you had mentioned above?
Click to expand...
Click to collapse
I did, and ended up hard bricking it for months until I finally got it back out, fixed it and gave up.

I also have the D2-861G and ended up bricking it but have been unable to fix it, would you mind telling me how you got it back up and running.

[Q] New FTV ... Initial setup problem

So I have received a replacement FTV and I believe it to be rootable because it does not go to the German language in the beginning screen.
Problem I am having is I blocked the updates in my router and I can't complete the initial set up. It sends a lot of time on:
"We are trying to update your Amazon Fire TV but we cannot contact our services. We will keep trying. Please do not disconnect from the network or unplug the power cable."
Then it goes to a screen that says:
"Unable to update your Amazon Fire TV
Try disconnecting the power cable for a few seconds and then plugging it back in.
If that does not work, please try again later or contact us at www.amazon.com/firetvsupport."
Any idea how to get past this without the update?
Thanks for the help guys!

I got past it by using open dns to block the update urls instead of directly blocking on router. Then after I got past it, I switched back to blocking on router directly and disabled the update program on firetv itself.

I don't understand how opendns.com will work for this? If that works would privateinternetaccess.com also work? I normally am running pptp with them for added security as I browse or do whatever I do.

draky said:
So I have received a replacement FTV and I believe it to be rootable because it does not go to the German language in the beginning screen.
Problem I am having is I blocked the updates in my router and I can't complete the initial set up. It sends a lot of time on:
"We are trying to update your Amazon Fire TV but we cannot contact our services. We will keep trying. Please do not disconnect from the network or unplug the power cable."
Then it goes to a screen that says:
"Unable to update your Amazon Fire TV
Try disconnecting the power cable for a few seconds and then plugging it back in.
If that does not work, please try again later or contact us at www.amazon.com/firetvsupport."
Any idea how to get past this without the update?
Thanks for the help guys!
Click to expand...
Click to collapse
If you are blocking the update server and get this it 99% mean it's running 51.1.0 and the first update it will take is 51.1.0.2. Then it'll try to update to the latest. If that's the case, you need to unblock the servers, let it download the update, and then when it reboots to install it, reblock them.

rbox said:
If you are blocking the update server and get this it 99% mean it's running 51.1.0 and the first update it will take is 51.1.0.2. Then it'll try to update to the latest. If that's the case, you need to unblock the servers, let it download the update, and then when it reboots to install it, reblock them.
Click to expand...
Click to collapse
So I let the system download the first update, unplugged the ethernet line as it restarted. Then I blocked the updates sites and plugged it back in... Now I'm sitting at sw version 51.1.4.0. Guessing there's nothing I can do about it now...

draky said:
So I let the system download the first update, unplugged the ethernet line as it restarted. Then I blocked the updates sites and plugged it back in... Now I'm sitting at sw version 51.1.4.0. Guessing there's nothing I can do about it now...
Click to expand...
Click to collapse
Really, there is no way to bypass a forced update... but it finally looks like they've caught on to us. Doesn't seem like good news.

draky said:
Any idea how to get past this without the update?
Click to expand...
Click to collapse
Hi,
i have the same problem.
Trying to finish initial setup without updating firmware.
At first start, Network found and started downloading Update.
So i turned it off and blocked the updateserver at router.
But can´t pass setup this way...

There's a guide on AFTVNews on how to bypass the mandatory update. Does that guide no longer work?

I wiped and installed latest pre-rooted software and could not get past checking for updates using blocks on router. Switched to open dns and went right through. Then I switched back to router. Just my experience.

16Darknight said:
There's a guide on AFTVNews on how to bypass the mandatory update. Does that guide no longer work?
Click to expand...
Click to collapse
it still works,
thank you

I know this is too late for OP, but incase someone comes across this thread looking for an answer, here is my guide to bypass the forced update:
http://www.aftvnews.com/how-to-get-passed-a-forced-software-update-on-the-amazon-fire-tv/

AFTVnews.com said:
I know this is too late for OP, but incase someone comes across this thread looking for an answer, here is my guide to bypass the forced update:
http://www.aftvnews.com/how-to-get-passed-a-forced-software-update-on-the-amazon-fire-tv/
Click to expand...
Click to collapse
And looks like I may get lucky... After it was funny loaded up I immediately preformed a master reset on the device just to see if everything took or if I happened to get lucky and something didn't load right and I was right. I go in, choose my language, put in my amazon account (it knows when I put in the wrong account) and then tries to register the device and while it's doing that it's flashing back and forth with a screen that says it doesn't have network connectivity but the box still has the white light.
I plug in my old box, lights up and connects just fine. I let it sit tonight for 20 minutes and still didn't work right so I'll be calling them tomorrow to see about replacing this one. Looks like the software update maybe didn't get loaded right.

I got through the initial setup following AFTVnews guide. Unluckily my Gernan FTV was on 5.1.3.0 from the start on, so i can't root and use the update blocking tool. Still having the update servers blocked the FireTV is almost unusable since it complains about not having a network connection. XBMC works fine but i can't use Amazon instant video. I blocked amzdigitaldownloads.edgesuite.net
softwareupdates.amazon.com
via router. any advice what i can change to continue blocking updates, but still access Amazon content?
Gesendet von meinem SM-N9005 mit Tapatalk

{ParanoiA} said:
I wiped and installed latest pre-rooted software ...
Click to expand...
Click to collapse
Beginning with which version, please?

Was on whatever came before 51.1.4.0 and did full wipe and then installed 51.1.4.0 and that's when I had to use opendns. After that I just flashed 51.1.4.1 over top of it because of the requirements.

{ParanoiA} said:
Was on whatever came before 51.1.4.0 and did full wipe and then installed 51.1.4.0 and that's when I had to use opendns. After that I just flashed 51.1.4.1 over top of it because of the requirements.
Click to expand...
Click to collapse
Bummer. It was 51.1.1.0 or earlier.
Wishful thinking...

What I've discovered is in the serial number range of the units themselves. If the unit has a serial of 7090020141....anything after that from 0 to 4 will not root....it will automatically jump to the "your unit requires an update" screen...no way around it. If the serial is 7090020141.....5 and above it will root.
I have rooted almost 100 units in the past 2 weeks and it is the same every time.... Perhaps I'm wrong....but I think not.
At this point I can look at the serial and tell you if it will root or not.

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

Firestick 2nd gen 5.2.7.4?

My firestick downloaded 5.2.7.4 and its broke my accessibility and adb commands. I looked on amazon to see latest versions for their devices and none of em are listed to have 5.2.7.4. Not sure if anyone else is having this problem or if they are rolling out another update and I just got unlucky and got some of the first roll outs of it. I also had ran some debloat commands and not sure if the stick just ran some updates after that. But it was after that it broke. But I have since factory reset and its still broke adb and accessibility. Just wanted to make people aware and see if anyone else has found a fix for this version or any info on a fix.

I having this problem too, cant set custom launcher.. anyone help us??

The 5-6 domains did not block this update either! This update made it through!
I also am wondering about this. Not even the app I used to prevent standby works anymore!

I have been looking all over for any info on the .4 update and no one seems to care as if this update doesn't exist. I have found no info on any existence of .4 except for a select few people sharing the same problem. this update has broke my adb as well as accessibility. Virus scanner wont work custom launcher will work if manually loaded. any app that requires any adb or accessibility are completely broke. sm commands come back as doesnt exists as will as i believe pm commands. only a select few non important commands will work. trying to give details in case it helps at all. but for now just letting developers do their thing and not trying to bother them to much. would love to help more but my 2nd gen tank cant be rooted. so i cant pull a backup or anything from it. not to mention if it was able to be rooted id be golden. Hopefully if someone figures out this whole .4 thing they will be kind enough to post something about it.

https://www.amazon.com/gp/help/customer/display.html?nodeId=201497590
Adb works without any Problems.

dont try rooting. 5.2.7.4 wont flash twrp recovery and you are stuck in hacked bootloader.
EDIT: If you know what you are doing you can do the 2 flashes and recovery reboot from the fastboot-step.sh in Windows if you run into the above. It works, got magisk, am rooted.

Mine isnt rooted nor can it be. Its the model that was made in 2020. And I see they have updated the device to say it has 5.2.7.4 but my adb is still broke. I have tried to factory reset and my adb commands are still busted. sm command and pm commands come back as invalid or missing. Not sure whats going on. It doesnt make sense if yours works. Thank you for letting me know your adb is still functioning. I guess Im gonna have to mess with it more.

noremy said:
Mine isnt rooted nor can it be. Its the model that was made in 2020. And I see they have updated the device to say it has 5.2.7.4 but my adb is still broke. I have tried to factory reset and my adb commands are still busted. sm command and pm commands come back as invalid or missing. Not sure whats going on. It doesnt make sense if yours works. Thank you for letting me know your adb is still functioning. I guess Im gonna have to mess with it more.
Click to expand...
Click to collapse
Try toggling unkown sources and debugging in settings? Maybe they got turned off?
Oh and just straight usb, 1 cable? Mine wont do tether adb with an otg cable.

Done all that. Unfortunately Im stuck. I dont what else to do with this thing. ADB will still connect but all the important commands come back as missing or invalid. such as sm commands and pm commands.

With 5.2.7.4 , you need root for this commands!!!

Thank you for clarifying this. I appreciate that. I unfortunately can't root mine due to manufacture date and them blocking the BL from what Ive read so I guess that stick is limited on its capabilities. But thank you for your time to reply to this. Hopefully this will clear it up for others as well.

TimmyP said:
dont try rooting. 5.2.7.4 wont flash twrp recovery and you are stuck in hacked bootloader.
EDIT: If you know what you are doing you can do the 2 flashes and recovery reboot from the fastboot-step.sh in Windows if you run into the above. It works, got magisk, am rooted.
Click to expand...
Click to collapse
That is a common fastboot bug, not related to the fireOS version or the xploit.
Latest ubuntu with a full fastboot install works (fixed), on arch linux (like the 4k fire ISO) it's fixed it too, but also a full reinstall with pacman is necessary.

Sus_i said:
That is a common fastboot bug, not related to the fireOS version or the xploit.
Latest ubuntu with a full fastboot install works (fixed), on arch linux (like the 4k fire ISO) it's fixed it too, but also a full reinstall with pacman is necessary.
Click to expand...
Click to collapse
I used the FireISO booted from USB in this post (err not this post, but the root post)... It will not flash the second script, not even manually. Windows...seconds.
My 4k stick went perfect.
Just posted in case it helps anyone.

TimmyP said:
I used the FireISO booted from USB in this post (err not this post, but the root post)... It will not flash the second script, not even manually. Windows...seconds.
My 4k stick went perfect.
Just posted in case it helps anyone.
Click to expand...
Click to collapse
:good:
You can fix this issue if you connect the FireISO system to the internet and run this, in order to update fb:
Code:
pacman -Sy
pacman -Sy fastboot

Ahh where were you a couple days ago!

noremy said:
Thank you for clarifying this. I appreciate that. I unfortunately can't root mine due to manufacture date and them blocking the BL from what Ive read so I guess that stick is limited on its capabilities. But thank you for your time to reply to this. Hopefully this will clear it up for others as well.
Click to expand...
Click to collapse
So just to clarify, 5.2.7.4 OTA has taken custom launcher apart by blocking pm grant permissions in accessibility.
TechdoctorUK mentioned this too a couple of weeks back. It seems the devs at amazon have been all over him lately and have been quoting tutorials etc from his site.
I've been using the ftvlaunchx app wrote to system settings on a post Dec 2019 unrootable 2nd gen and thought I'd blocked 5.2.7.4 update but I came back in today and was fkin horrified it had updated to 5.2.7.4 (I nearly sh't myself) its still optimizing apps just now but I'm hoping, just hoping that due to the pm grant permission already being installed it maybe slip through the net. Wishful thinking I know.
Hurry up and arrive 4k firestick I NEED ROOT

Let me know what you find out with yours. I have been watching the forums to see if and when someone may find a work around. Till then I'll keep tinkering with my 4k version.

noremy said:
Let me know what you find out with yours. I have been watching the forums to see if and when someone may find a work around. Till then I'll keep tinkering with my 4k version.
Click to expand...
Click to collapse
Hi noremy, i just made a new thread there on 5.2.7.4, the cure is ftvlaunchx wrote to system settings, install atv launcher pro and set that as default launcher in the ftvlaunchx app, should work with any android tv launcher too.
Big thanks to the developers @github
Edit #### i rebooted and now the home button is not working at all
Only sending me back to amazon screen.
Regards
Sent from my SM-T580 using Tapatalk

Hi! Mine is a 2nd gen Firestick. After the 5.2.7.4 update, none of my apps are opening. It says "Amazon App Store is out of date. Please visit the Amazon website to install the latest version". When I click on the link, it says Appstore is installed & I am good to go. No matter what I do, same thing happens for each and every app. So I can't use any of the apps on my Firestick. Any suggestions on what this is? Thanks!

The only option I can think off would be to factory reset it. I know its a pain to put everything back on but not sure what else to try.