Thanks for this thread. I found a 1080p TV and successfully upgraded from CWM to TWRP. I was then able to load the 5.2.1.1. Still hard to believe it was the TV that was causing all the headaches.
Some how, after successfully loading and running the new cmw and twrp and latest rooted rom, I somehow seem to have lost root! I don't know how I succeeded in doing this, but succeed I did. So, with your latest cmw (firetv cwm recovery 6.0.5.1.4a img), twrp (bueller twrp 3.0.0-6.img) and rooted rom (bueller 5.2.1.2 rooted.zip) already installed, is there anyway to reacquire root? I have and flashed a superuser zip, which flashes OK, but doesn't give superuser status. For instance, will something like Kingroot work? Any help or suggestion is appreciated. Thanks in advance.
Flash again 5.2.1.2 rooted.zip using TWRP.
If you watch closer its installation you will see that su will install as well, one more thing if you lose root you will lose TWRP as well. How did you determined that you lost root?
Thanks for getting back to me. Looking back on this episode, I know now how I may have felt like I lost root. The device works just fine right now. But, instead of doing a factory wipe, I did a format. I know, dumb. Nevertheless, twrp saved the device because when I went to reboot, it warned I had no O/S. So, I did not reboot, but went back and installed the new rooted rom. Everything seemed to work. Got back to normal, went through the AFTV set-up, got everything back to normal, and then started on trying to add Google Play store. Using the AFTV app, I got xposed installed, etc. then went to do the computer inputs, but from the adb shell, it would not go into superuser. Still doesn't. I have noticed, as you point out, the su install during the installation of the rooted rom. So, my problem with getting into su from adb remains a ???. Any suggestion for this because from the appearance it is not rooted. I am a duffer when it comes to this, as is obvious. If I'm in the wrong forum, please move, but for what its worth, the product introduced in this forum loads and works great. Thanks again for any of your suggestions.
Forgot for what reason this changed but on PreRooted FireOS 5 FW. You don't just go into SuperUser mode. You first have to input an "SU" command on your ADB window on your PC & set it to "Always Allowed" when your FireTV prompts you to grant SuperUser access to ADB on your TV. You get less then 15 seconds to do this. But you only need to do this once.Thanks for getting back to me. Looking back on this episode, I know now how I may have felt like I lost root. The device works just fine right now. But, instead of doing a factory wipe, I did a format. I know, dumb. Nevertheless, twrp saved the device because when I went to reboot, it warned I had no O/S. So, I did not reboot, but went back and installed the new rooted rom. Everything seemed to work. Got back to normal, went through the AFTV set-up, got everything back to normal, and then started on trying to add Google Play store. Using the AFTV app, I got xposed installed, etc. then went to do the computer inputs, but from the adb shell, it would not go into superuser. Still doesn't. I have noticed, as you point out, the su install during the installation of the rooted rom. So, my problem with getting into su from adb remains a ???. Any suggestion for this because from the appearance it is not rooted. I am a duffer when it comes to this, as is obvious. If I'm in the wrong forum, please move, but for what its worth, the product introduced in this forum loads and works great. Thanks again for any of your suggestions.
Forgot for what reason this changed but on PreRooted FireOS 5 FW. You don't just go into SuperUser mode. You first have to input an "SU" command on your ADB window & set it to "Always Allowed" when your FireTV prompts you to grant SuperUser access to ADB.
You can kind of see it in this guide:
http://www.aftvnews.com/how-to-inst...d-an-initial-rom-on-a-rooted-fire-tv-stick-1/
It's in steps 8-9. This is true of all three versions of Rooted FTV devices. But on FTV1's it will say "bueller:" instead of "montoya:". This must be done any time you want to enter SuperUser mode on ADB.
np, modded my prior post so it is more clear.Thanks for that info. What I found is that when I connected my laptop to the aftv via usb cable I had to actually watch the aftv screen on the TV. If I only looked at the computer screen and entered su, the computer cursor would flash for a few seconds and then go back to the prior prompt. But, if I watched the tv screen when I entered su, the tv screen would prompt me to accept or reject. As soon I clicked accept via the aftv, the computer cursor would then show and go into root. Weird, but that's how I "figured it out". It's called paying attention, a.k.a operator error. Anyway, thanks for your help. As for this original post, I also got the loop first discussed on the first page of this post. I just did a fresh reload on the CMW and then the rooted rom loaded and worked perfectly. Thanks again.
I updated the OP with 3.0.0-7 TWRP image. If things are working for you, and you install the latest ROM with 3.0.0-7, you don't need this. This is only for if you still have the looping, install this, then install the latest ROM, and you'll be good to go.
You can go from one of the two v3.0.0-7 options. Which version of the two v3.0.0-7 depends from what FW & CWM your updating from & if you have an unlocked bootloader. Go thru all the requirements to find out what applies to your situation.So just go from cwm recovery on os3 on firetv 1 to twrp 3.0.0-7, reboot into recovery and load latest prerooted rom?....
You can go from one of the two v3.0.0-7 options. Which version of the two v3.0.0-7 depends from what FW & CWM your updating from & if you have an unlocked bootloader. Go thru all the requirements to find out what applies to your situation.
Just make sure your using the v3.0.0-7 of either one that is for your situation instead of v3.0.0-6 that the guide mentions. Since v3.0.0-7 is the latest one.
Make sure you go step by step and verify on what starting point you are on. Since the most important thing is to have a good installation of TWRP. Once TWRP is correctly install on your FTV1. Your pretty much set. Since you can always go into TWRP & reflash your FTV1 if anything goes wrong.
Hi, I have an aft box v1. Just updated to twrp 3.0.0-7 and install latest rom 5.2.1.2. Went well, but now I have no amazon content on home screen?! I'm blocking amazon updates using opendns. Could this be a problem? Or do I need to go back in twrp and just wipe cache?
Never mind I needed to register amazon account! All set!
---------- Post added at 07:43 AM ---------- Previous post was at 07:27 AM ----------
You can go from one of the two v3.0.0-7 options. Which version of the two v3.0.0-7 depends from what FW & CWM your updating from & if you have an unlocked bootloader. Go thru all the requirements to find out what applies to your situation.
Just make sure your using the v3.0.0-7 of either one that is for your situation instead of v3.0.0-6 that the guide mentions. Since v3.0.0-7 is the latest one.
Make sure you go step by step and verify on what starting point you are on. Since the most important thing is to have a good installation of TWRP. Once TWRP is correctly install on your FTV1. Your pretty much set. Since you can always go into TWRP & reflash your FTV1 if anything goes wrong.
Hi, I got box up and running good now.... But Netflix won't download or load.... do I have to hide root with root hide app to install Netflix app. Amazon won't let it download and install!!
Root has never affected Neflix. I think you need to uninstall whatever current version of Netflix you have. Then try to install latest from Amazon cloud (FTV Apps section). Instead of trying to update it.Hi, I got box up and running good now.... But Netflix won't download or load.... do I have to hide root with root hide app to install Netflix app. Amazon won't let it download and install!!
Root has never affected Neflix. I think you need to uninstall whatever current version of Netflix you have. Then try to install latest from Amazon cloud (FTV Apps section). Instead of trying to update it.
humn, never had problems installing an app from my FTV so far. You might have to go into TWRP & "wipe" cache & dalvik cache. And reinstall the FW.Old app was uninstalled... never could load newer version of netflix.... I'm having amazon app store push old netflix red app to my aftv box v1. I'll keep u posted on progress. ..
humn, never had problems installing an app from my FTV so far. You might have to go into TWRP & "wipe" cache & dalvik cache. And reinstall the FW.
BTW from reading here there is only one way to verify TWRP installed correctly. That is to do a restart of the FTV. Most folks that have a bad TRWP don't know it until after a reboot of their device. I haven't had to deal with that yet.
Also make sure you do both device based OTA update blocking that is linked to on the Guide I linked to above.
If that is your only Amazon device. Then you don't need to block anything as long as you have done at least "Method 5” before first boot & then "Method 1" after first boot. The OpenDNS & router methods are not as safe since there is no full list of addresses to block that is being kept. The update address can change at anytime at Amazon's whim.I just can't get Netflix app to work, new or old app... I have open dns blocking updates. I know this because I tried to check for updates and no update information come from amazon.
Are there new links I should block in open dns?
address=/amzdigital-a.akamaihd.net/127.0.0.1
address=/amzdigitaldownloads.edgesuite.net/127.0.0.1
address=/softwareupdates.amazon.com/127.0.0.1
address=/updates.amazon.com/127.0.0.1
address=/a1896.g.akamai.net/127.0.0.1
amzdigital-a.akamaihd.net
amzdigitaldownloads.edgesuite.net
softwareupdates.amazon.com
updates.amazon.com
a1896.g.akamai.net
firs-ta-g7g.amazon.com
amzdigitaldownloads.edgesuite.net
softwareupdates.amazon.com
updates.amazon.com
atv-ext.amazon.com
a1910.d.akamai.net
amzdigital-a.akamaihd.net
amzdigital-b.akamaihd.net
amzdigital.akamaihd.net
cat /proc/cmdline
dd if=/data/media/0/bueller-twrp_3.0.0-6.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
adb reboot recovery
sh /data/media/0/bueller_recovery_vX.zip
killall recovery
This test image worked for me but my tv is only 720p so the graphics overlap and it is VERY hard to use. Any chance of getting a version with a 720p theme instead?
I can't imagine why a TV would cause TWRP to crash, but at this point I can't explain it.