Develop Bugs

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.

1st Gen FireTV stuck an Amazon FireTV logo

I have a rooted 1st Gen with 5.0.5.1 on it
I used software ver 51.1.4.0
Now Im suck cant connect ADB

trickyrick said:
I have a rooted 1st Gen with 5.0.5.1 on it
I used software ver 51.1.4.0
Now Im suck cant connect ADB
Click to expand...
Click to collapse
Did you try clearing cache? Maybe you need to do a factory reset?

I only know how to do that when the firetv will boot. Using the remote will not work. Clearing cache also FTC needs to boot. I'm stuck on the logo
Thanks for the suggestions

trickyrick said:
I'm stuck on the logo
Click to expand...
Click to collapse
Why you flash a fireOS 3 version over a fireOS 5?
If the FireTV Boot Menu doesn't show up at boot, your box is probably dead.
Only way to recover is with a low voltage emmc adapter soldered to the EMMC, but this costs about the same as a new stick.

You may want to give the link below a try. I did the opposite by going from fireOS3 to fireOS5 without installing bueller_recovery_v2.zip first and has a similar issue. I was able to get my box working, however there are a few issues. ADB doesn't work, supersu is still running as a service. I'm stuck on software 5.2.6.3, prime video doesn't work and it tries to install os updates every time i rebooted the box.
I eventually got prime video working by installing a newer Video_com.amazon.avod.apk from one of my other box and i broken checking for updates by installing a newer DeviceSoftwareOTA_com.amazon.device.software.ota.apk and System Updates_com.amazon.device.software.ota.override.apk.
The box is running great except for os updates and adb.
https://forum.xda-developers.com/fi...ock-images-t2882337/post56987752#post56987752

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.

AFTV 2 Sloane won't update past 5.2.6.0 How to force update adb/usb?

My friend has a fire tv 2 box sloane.
we've tried everything to update including contacting Amazon support for remote assistance and factory resetting multiple times.
We can't use YouTube TV without updating.
I'm good with Android and kkow how to use adb.
Can I force flash the stock firmware to update past 5.2.6.0? If so how?

dovedescent7 said:
My friend has a fire tv 2 box sloane.
we've tried everything to update including contacting Amazon support for remote assistance and factory resetting multiple times.
We can't use YouTube TV without updating.
I'm good with Android and kkow how to use adb.
Can I force flash the stock firmware to update past 5.2.6.0? If so how?
Click to expand...
Click to collapse
I had a box the other week that was on 5.2.7.3 so the issue isn't if it only updates to your current version.
There may be a corrupted ota update apk in your build, have you made sure that ota updates are enabled in >settings>my firetv and tried the adb commands to make sure they are actually enabled?
Sent from my SM-G935F using Tapatalk

I haven't run adb commands on it yet nor any fire device only android phones. I don't physically get the box in my possesion again until this weekend.
That's why I'm asking though...
Can I simply flash firmware in the stock recovery? Like via USB?
Whats the gist of recovering this aftv besides factory reset in settings?

dovedescent7 said:
I haven't run adb commands on it yet nor any fire device only android phones. I don't physically get the box in my possesion again until this weekend.
That's why I'm asking though...
Can I simply flash firmware in the stock recovery? Like via USB?
Whats the gist of recovering this aftv besides factory reset in settings?
Click to expand...
Click to collapse
Sorry to hear the factory reset process didn't work for you, I suspect there may be a problem with the update protocol (either system or the ota apk). Maybe someone can correct me if I'm wrong?
Please Note :This method requires a Linux installation either on a pc or live USB.
To flash firmware to your device you will have to unlock it first as per OP unlock instructions.
Here:
https://forum.xda-developers.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303
This will unlock your box bootloader and install TWRP.
After TWRP is installed you can then choose what ever firmware(s) pre rooted you want for the box.
The general unlocking process is quite simple. If your friend is game for it being opened, shorted and unlocked that is.
You will first have to get acquainted with adb and boot your pc from a Linux installation or Linux distro Live USB to complete the amonet script process.
(This is the amazing program that flashes the TWRP custom recovery to your device)
All of this may sound quite daunting and bewildering but this box is easy to unlock.
It is totally upto you but this is the only way I can see for you to gain control over your friends box and upgrade the firmware.
The guys here will be there should you need help at anytime.
Regards
R.
Sent from my SM-G935F using Tapatalk

Bertonumber1 said:
Sorry to hear the factory reset process didn't work for you, I suspect there may be a problem with the update protocol (either system or the ota apk). Maybe someone can correct me if I'm wrong?
Please Note :This method requires a Linux installation either on a pc or live USB.
To flash firmware to your device you will have to unlock it first as per OP unlock instructions.
Here:
https://forum.xda-developers.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303
This will unlock your box bootloader and install TWRP.
After TWRP is installed you can then choose what ever firmware(s) pre rooted you want for the box.
The general unlocking process is quite simple. If your friend is game for it being opened, shorted and unlocked that is.
You will first have to get acquainted with adb and boot your pc from a Linux installation or Linux distro Live USB to complete the amonet script process.
(This is the amazing program that flashes the TWRP custom recovery to your device)
All of this may sound quite daunting and bewildering but this box is easy to unlock.
It is totally upto you but this is the only way I can see for you to gain control over your friends box and upgrade the firmware.
The guys here will be there should you need help at anytime.
Regards
R.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Bummer, so the new methods referenced here in below link dont work then ?
AFTVnews is saying that i can root with new method?
Is this fake news? lol
https://www.aftvnews.com/amazon-fire-tv-2-box-running-latest-software-version-has-been-rooted/
.
.
.
.

dovedescent7 said:
Bummer, so the new methods referenced here in below link dont work then ?
AFTVnews is saying that i can root with new method?
Is this fake news? lol
https://www.aftvnews.com/amazon-fire-tv-2-box-running-latest-software-version-has-been-rooted/
.
.
.
.
Click to expand...
Click to collapse
No, it works up to 5.2.6.9

Sus_i said:
No, it works up to 5.2.6.9
Click to expand...
Click to collapse
I dont understand. Are you saying method WILL WORK for 5.2.6.0 or WILL NOT WORK for 5.2.6.0?
I am very familiar with Ubuntu Linux and adb..

dovedescent7 said:
I dont understand. Are you saying method WILL WORK for 5.2.6.0 or WILL NOT WORK for 5.2.6.0?
I am very familiar with Ubuntu Linux and adb..
Click to expand...
Click to collapse
As stated by @Sus_i the diplomatic mediatek exploit will only work upto version 5.2.6.9. Any higher version of fireos then you will have to use the hardware root, twrp method from the thread I posted above.
Good you are familiar with Ubuntu/Linux as the commands for the script will be run through terminal with the downloadable amonet script in the thread.
After you've installed/updated adb+fastboot py serial through command line of your Linux install. You're ready to open up your device, and refer to the dat0 located in the photo of OP
Sent from my SM-G935F using Tapatalk

Bertonumber1 said:
As stated by @Sus_i the diplomatic mediatek exploit will only work upto version 5.2.6.9. Any higher version of fireos then you will have to use the hardware root, twrp method from the thread I posted above.
Good you are familiar with Ubuntu/Linux as the commands for the script will be run through terminal with the downloadable amonet script in the the thread.
After you've installed/updated adb+fastboot py serial through command line of your Linux install. You're ready to open up your device, and refer to the dat0 located in the photo of OP
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Thank you. I get a little confused on version numbers with this thing. Does fire tv sw/fw go up like normal fw? Like does it go 5.2.6.0 then 5.2.6.1 and so on?
I have:
5.2.6.0 so this one can be done with software method?
5.2.7.4 this one has to be done by shorting internal stuff+linux right?

dovedescent7 said:
Thank you. I get a little confused on version numbers with this thing. Does fire tv sw/fw go up like normal fw? Like does it go 5.2.6.0 then 5.2.6.1 and so on?
I have:
5.2.6.0 so this one can be done with software method?
5.2.7.4 this one has to be done by shorting internal stuff+linux right?
Click to expand...
Click to collapse
Yes I had to edit the post there as i got confused myself, I had wrote 5.2.7.0 lol.
So just to clarify 5.2.6.9 and under you can use mediatek software root.
5.2.7.0 and over requires the hardware short method.
Sent from my SM-G935F using Tapatalk

dovedescent7 said:
I dont understand. Are you saying method WILL WORK for 5.2.6.0 or WILL NOT WORK for 5.2.6.0?
Click to expand...
Click to collapse
Lets say, it 'should' work :good:
I don't know if someone tested it on your OS version, because it's much older than the exploit itself.
The most current OS version back then was 5.2.6.8, the mtk root method came up and everybody was happy, finally a new root method for the second gen box
Big A patched it with 5.2.7.0.
Needless to say that most people tested it on 5.2.6.8 and .9.
It may be that the exploit isn't adapted to your OS version, but who knows.
Let us know what happens.
Good luck

Perfect thank you for the clarification.
One last question?
I messed up, I factory reset ftv 2 box using my tvs remote and now cannot set it up because my ftv remote is broken/or this particular ftv2 box doesn't pair with Amazon remotes.
Is it possible to somehow setup fire tv (from setup screen after factory reset) without a fire tv remote?

dovedescent7 said:
Perfect thank you for the clarification.
One last question?
I messed up, I factory reset ftv 2 box using my tvs remote and now cannot set it up because my ftv remote is broken/or this particular ftv2 box doesn't pair with Amazon remotes.
Is it possible to somehow setup fire tv (from setup screen after factory reset) without a fire tv remote?
Click to expand...
Click to collapse
Ok, I see. You could try it this way:
-remove the batteries, then press 30 seconds the home button.
-Put new fresh batterys back in.
-Try to pair the remote again, but keep pressing the home button for at least 30 seconds.Do that again and again...
Could be that it takes some time (and attempts), until the remote connects.
If it won't work and you don't know someone with a remote near to you, take a look for a guide with a usb keyboard or so at www.aftvnews.com or xda forums search.

Sus_i said:
Ok, I see. You could try it this way:
-remove the batteries, then press 30 seconds the home button.
-Put new fresh batterys back in.
-Try to pair the remote again, but keep pressing the home button for at least 30 seconds.Do that again and again...
Could be that it takes some time (and attempts), until the remote connects.
If it won't work and you don't know someone with a remote near to you, take a look for a guide with a usb keyboard or so at www.aftvnews.com or xda forums search.
Click to expand...
Click to collapse
THANKS!
NOW I NEED URGENT HELP
Rooted ftv 2 with short method now stuck at twrp.
Can i simply now install prerooted rom from within TWRP via rom on SD card?

edit
so I rooted aftv 2 box with shorting method then got into twrp. Then flashed prerooted fire tv image but when I rebooted it gets stuck on amazon fire tv splash screen and won't move.
I tried clearing cache 1x in TWRP afterwards, then reboot but still hangs at Amazon boot.
What am I missing?

dovedescent7 said:
edit
so I rooted aftv 2 box with shorting method then got into twrp. Then flashed prerooted fire tv image but when I rebooted it gets stuck on amazon fire tv splash screen and won't move.
I tried clearing cache 1x in TWRP afterwards, then reboot but still hangs at Amazon boot.
What am I missing?
Click to expand...
Click to collapse
Have you flashed this way, first the 5.2.6.7_v2 and then a later 5.2.7.x one? It's mentioned in the prerooted thread.
Wipe cache and dalvik before you reboot.
If it won't boot, you probably need to wipe data and internalsd too. Best is to use the 'format' data tab in TWRPs wipe section.
After that, the box should boot, but you need to log on at the setup, pair the remote and so on...

dovedescent7 said:
I dont understand. Are you saying method WILL WORK for 5.2.6.0 or WILL NOT WORK for 5.2.6.0?
I am very familiar with Ubuntu Linux and adb..
Click to expand...
Click to collapse
I just did this on a used device I purchased that came with 5.2.6.7 and it worked perfectly. Follow the instructions and you'll have no issues and none of that jumper stuff.