I have a ftv rooted with version 51.1.4.0, but am unable to update kodi beyond 16.1
All the attempts fail and some have said an OS update is needed to do that upgrade of KODI 17.
I also cannot install SPMC, also fails using abdfire.
any ideas?
tia
ant17 said:
I have a ftv rooted with version 51.1.4.0, but am unable to update kodi beyond 16.1
All the attempts fail and some have said an OS update is needed to do that upgrade of KODI 17.
I also cannot install SPMC, also fails using abdfire.
any ideas?
tia
Click to expand...
Click to collapse
SPMC should work. Last I checked it was still mostly based on Kodi v16.1. Install AppStarter & try to install SPMC from there. Or from Downloader thru FireTVGuru.net.
I would recommend you research the upgrade process & once you understand it & have meet all requirements. Make it so.
Right now upgrading from FireOS 3 might be a bit complicated since an update cycle just started today. And there is no PreRooted ROM for the latest yet. You will need to make sure you TWRP block updates using the 5th method if you upgrade to the current PreRooted ROM.
Y314K said:
SPMC should work. Last I checked it was still mostly based on Kodi v16.1. Install AppStarter & try to install SPMC from there. Or from Downloader thru FireTVGuru.net.
I would recommend you research the upgrade process & once you understand it & have meet all requirements. Make it so.
Right now upgrading from FireOS 3 might be a bit complicated since an update cycle just started today. And there is no PreRooted ROM for the latest yet. You will need to make sure you TWRP block updates using the 5th method if you upgrade to the current PreRooted ROM.
Click to expand...
Click to collapse
Is it advised to move up to the most current prerooted FireOS 5 when it becomes available? I have a gen1 box on the last prerooted FireOS 3, and a prerooted gen 1 stick. Is holding either of these back on 5.0.5 a good idea? I suspect the new interface updates will include some amount of performance penalty.
Axecaster said:
Is it advised to move up to the most current prerooted FireOS 5 when it becomes available? I have a gen1 box on the last prerooted FireOS 3, and a prerooted gen 1 stick. Is holding either of these back on 5.0.5 a good idea? I suspect the new interface updates will include some amount of performance penalty.
Click to expand...
Click to collapse
The update to FireOS 5 is mostly recommended for App comparability. More & more apps in the PlayStore & Amazon have lollipop as the starting point.
I did learn to live with the no Home button detection for AppStarter. I still use AppStarter 90% of the time. I just keep AppStarter as the only app in recent. So it has just added a couple of presses to what I was use to with FireStarter. But if the HOME button detection is a huge deal for you. You should stay there.
As for the updates. I have not seen any performance hits. The only major problem might be bugs. But the tier rollout of the update usually takes care of that. I tried the new UI on a couple of FTVS2's & they weren't laggy at all. I usually find the latest FW to be as fast or faster of prior onces. But that might be because I prefer to do clean installs when upgrading FW. Specially on an update as big as the one that just started to rollout. The new update includes more stuff but luckily it comes with options to turn some of that stuff off.
We can also always downgrade PreRooted Rom's. So it's fine to take things for a spin. As long as you have a good install of TRWP. There shouldn't be a problem. Other the user error or power outage.
I wouldn't care about the KODI update, but a message from tv addons says streams are more often using the https: for shows and 16.1 doesn't support that.
Axecaster said:
Is it advised to move up to the most current prerooted FireOS 5 when it becomes available? I have a gen1 box on the last prerooted FireOS 3, and a prerooted gen 1 stick. Is holding either of these back on 5.0.5 a good idea? I suspect the new interface updates will include some amount of performance penalty.
Click to expand...
Click to collapse
Is there a OS prerooted 5 out? I have 2 FTV boxes rooted that won't take spmc or 17.1 kodi.
ant17 said:
Is there a OS prerooted 5 out? I have 2 FTV boxes rooted that won't take spmc or 17.1 kodi.
Click to expand...
Click to collapse
Yes, but which version are they. So I can give you the right guide link. FTV1 or FTV2 ?
It all starts with the recovery...
(Make sure you install the right version 7 (aka v3.0.0-7) of TWRP depending on your locked or unlocked bootloader on FTV1's)
FTV1: http://www.aftvnews.com/how-to-install-twrp-custom-recovery-on-a-rooted-fire-tv-1/
FTV2: http://www.aftvnews.com/how-to-install-twrp-custom-recovery-on-a-rooted-fire-tv-2/
http://www.aftvnews.com/how-to-root...covery-and-a-pre-rooted-rom-all-without-a-pc/
FTVS1: http://www.aftvnews.com/how-to-inst...d-an-initial-rom-on-a-rooted-fire-tv-stick-1/
Just make sure you follow the requirements. A good install of TWRP is key.
Axecaster said:
Is it advised to move up to the most current prerooted FireOS 5 when it becomes available? I have a gen1 box on the last prerooted FireOS 3, and a prerooted gen 1 stick. Is holding either of these back on 5.0.5 a good idea? I suspect the new interface updates will include some amount of performance penalty.
Click to expand...
Click to collapse
Y314K said:
Yes, but which version are they. So I can give you the right guide link. FTV1 or FTV2 ?
It all starts with the recovery...
(Make sure you install the right version 7 (aka v3.0.0-7) of TWRP depending on your locked or unlocked bootloader on FTV1's)
FTV1: http://www.aftvnews.com/how-to-install-twrp-custom-recovery-on-a-rooted-fire-tv-1/
FTV2: http://www.aftvnews.com/how-to-install-twrp-custom-recovery-on-a-rooted-fire-tv-2/
http://www.aftvnews.com/how-to-root...covery-and-a-pre-rooted-rom-all-without-a-pc/
FTVS1: http://www.aftvnews.com/how-to-inst...d-an-initial-rom-on-a-rooted-fire-tv-stick-1/
Just make sure you follow the requirements. A good install of TWRP is key.
Click to expand...
Click to collapse
I think they're ver. 2 but unknown OS.
One is 51. 1. 1. 0, the other is 51. 1. 4. 0 Both are rooted.
ant17 said:
I think they're ver. 2 but unknown OS.
One is 51. 1. 1. 0, the other is 51. 1. 4. 0 Both are rooted.
Click to expand...
Click to collapse
v2 AFTV's are the only current devices with both a USB & SDCard slot. So easy to tell. As for OS there are only two types. Either Amazon Original ROM or RBox's PreRooted ROM. Both would show same version numbers in System/About info menu.
Since you say they are Rooted. Then u very likely have a PreRooted ROM install. And when using Apps that use root it will ask you for permission the first time that App or option runs. Like in the case of ES File Explorer Root option. If you had already given it permission then you would see a notification letting you know Root access has been activated/granted to ES File Explorer.
Y314K said:
v2 AFTV's are the only current devices with both a USB & SDCard slot. So easy to tell. As for OS there are only two types. Either Amazon Original ROM or RBox's PreRooted ROM. Both would show same version numbers in System/About info menu.
Since you say they are Rooted. Then u very likely have a PreRooted ROM install. And when using APS that use root it will ask you for permission the first time that App or option runs. Like in the case of ES File Explorer Root option. If you had already given it permission then you would see a notification letting you know Root access has been granted to ES File Explorer.
Click to expand...
Click to collapse
OK, been a long time since I rooted these so I'm assuming its a pre-rooted rom. Both boxes have just the usb and no sd slot.
ant17 said:
OK, been a long time since I rooted these so I'm assuming its a pre-rooted rom. Both boxes have just the usb and no sd slot.
Click to expand...
Click to collapse
Then you have FTV1's like I do. Go thru the requirements check list from the FTV1 TWRP guide I linked above. And make sure you understand what you are doing before updating. I usually keep everything. Files, APK's, Rom's in a USB to flash & install & I verify MD5 hash's to make sure I copied the files correctly. Specially the recovery/TWRP file & PreRooted ROM.
Y314K said:
v2 AFTV's are the only current devices with both a USB & SDCard slot. So easy to tell. As for OS there are only two types. Either Amazon Original ROM or RBox's PreRooted ROM. Both would show same version numbers in System/About info menu.
Since you say they are Rooted. Then u very likely have a PreRooted ROM install. And when using APS that use root it will ask you for permission the first time that App or option runs. Like in the case of ES File Explorer Root option. If you had already given it permission then you would see a notification letting you know Root access has been granted to ES File Explorer.
Click to expand...
Click to collapse
Y314K said:
Then you have FTV1's like I do. Go thru the requirements check list from the FTV1 TWRP guide I linked above. And make sure you understand what you are doing before updating. I usually keep everything. Files, APK's, Rom's in a USB to flash & install & I verify MD5 hash's to make sure I copied the files correctly. Specially the recovery/TWRP file & PreRooted ROM.
Click to expand...
Click to collapse
Is there a way to see which recovery is already on the box? like cmod? I assume I would need to get twrp on there but didn't want to cause a problem by just puting it on there without knowing if cmods there.
Deleted
ant17 said:
Is there a way to see which recovery is already on the box? like cmod? I assume I would need to get twrp on there but didn't want to cause a problem by just puting it on there without knowing if cmods there.
Click to expand...
Click to collapse
The only method is to connect a keyboard to your FTV1 & choose to boot into recovery at startup. You should see the exact version on the lower left hand side.
If your going to be using a USB drive to flash things. You will need a USB hub to have both the USB Keyboard & USB drive hooked up to the device at the same time.
Those guides are the most complete ones. But they are some what old & also each FTV has it's own history of what has been done to it. So make sure you modify accordingly. I thought about making a post with my notes regarding this updating guide but I thought everybody's starting point is probably to different & I don't want to be responsible for bricking any FTV1's.
Y314K said:
Then you have FTV1's like I do. Go thru the requirements check list from the FTV1 TWRP guide I linked above. And make sure you understand what you are doing before updating. I usually keep everything. Files, APK's, Rom's in a USB to flash & install & I verify MD5 hash's to make sure I copied the files correctly. Specially the recovery/TWRP file & PreRooted ROM.
Click to expand...
Click to collapse
Is there a need to flash the stock recovery in order to get rid of twrp/unroot the fire TV 1 and allow it to update itself back to stock? Is flashing cwm over twrp the only way?
I unblocked updates and they get downloaded but after it reboots twrp blocks the update process.
I am trying to get the device back to stock per buyer's request
Y314K said:
SPMC should work. Last I checked it was still mostly based on Kodi v16.1. Install AppStarter & try to install SPMC from there. Or from Downloader thru FireTVGuru.net.
I would recommend you research the upgrade process & once you understand it & have meet all requirements. Make it so.
Right now upgrading from FireOS 3 might be a bit complicated since an update cycle just started today. And there is no PreRooted ROM for the latest yet. You will need to make sure you TWRP block updates using the 5th method if you upgrade to the current PreRooted ROM.
Click to expand...
Click to collapse
Tried to install spmc 16.6 via adb fire, ES file explorer, and total commander (which happens to be WAY better than ES file explorer) and I get parsing error. Never does install.
evaporic said:
Is there a need to flash the stock recovery in order to get rid of twrp/unroot the fire TV 1 and allow it to update itself back to stock? Is flashing cwm over twrp the only way?
I unblocked updates and they get downloaded but after it reboots twrp blocks the update process.
I am trying to get the device back to stock per buyer's request
Click to expand...
Click to collapse
There is no guide on how to go back to stock FW on a FTV1 once TWRP is install. This is due to the version of FW & TWRP that the FTV1's where first updated to FireOS 5. That was FW v5.0.5 & TWRP v6. So the TWRP had matured enough to fully block updates.
The only info regarding downgrading can be found in the TWRP thread. Folks that failed @ updating to TWRP correctly where able downgrade back to CWM. I think you also need to downgrade the FW to a PreRooted FireOS 3 too but I could be wrong. Once on CWM you should be able to allow updates since CWM won't block those updates.
Look/search for more info on the few folks that where able to go from TWRP to CWM here:
https://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286
Also once your fully on CWM/FireOS 3 you might be able to use this guide to downgrade too:
http://www.aftvnews.com/how-to-unroot-a-fire-tv-and-switch-back-to-stock-updates-from-amazon/
All of the above is theory for me. Since I've never had to dealt with this. And there are no guides for this specific scenario. So make sure you look thru the TWRP thread to find the folks that actually mention going back to CWM. Although most of them did so just to reflash TWRP.
Search example: https://forum.xda-developers.com/search/thread/3383286?query=back to cwm
ant17 said:
Tried to install spmc 16.6 via adb fire, ES file explorer, and total commander (which happens to be WAY better than ES file explorer) and I get parsing error. Never does install.
Click to expand...
Click to collapse
Note 1: As of 16.5.0, Android lollipop (API 21) is required
_____________________________________
16.5.0 (2016/11/30):
CHG: API 21+ (Android 5.0) only, sorry.
ADD: 4K on AFTV2
ADD: refresh rate sync on AFTV
ADD: DASH support (aka 1080p/4K youtube)
ADD: Builtin log (Settings-System-Logging-Upload…)
ADD: crash handler (no need for logcat)
ADD: rendercapture (boblight, Hue, …) support for Surface
FIX: Only stop Surface when really necessary
CHG: Revert to Surface as standard
ADD: acceleration setting for hevc
16.4.2 (2016/08/15):
REVERT: crash when enumerating sound devices during a refresh rate change
FIX: Missing start of video with large buffer
You will need to find SPMC v16.4.2 for FireOS 3.
You can find it from source here: https://github.com/koying/SPMC/releases?after=17.0b3-Krypton
Y314K said:
SPMC should work. Last I checked it was still mostly based on Kodi v16.1. Install AppStarter & try to install SPMC from there. Or from Downloader thru FireTVGuru.net.
I would recommend you research the upgrade process & once you understand it & have meet all requirements. Make it so.
Right now upgrading from FireOS 3 might be a bit complicated since an update cycle just started today. And there is no PreRooted ROM for the latest yet. You will need to make sure you TWRP block updates using the 5th method if you upgrade to the current PreRooted ROM.
Click to expand...
Click to collapse
Y314K said:
There is no guide on how to go back to stock FW on a FTV1 once TWRP is install. This is due to the version of FW & TWRP that the FTV1's where first updated to FireOS 5. That was FW v5.0.5 & TWRP v6. So the TWRP had matured enough to fully block updates.
The only info regarding downgrading can be found in the TWRP thread. Folks that failed @ updating to TWRP correctly where able downgrade back to CWM. I think you also need to downgrade the FW to a PreRooted FireOS 3 too but I could be wrong. Once on CWM you should be able to allow updates since CWM won't block those updates.
Look/search for more info on the few folks that where able to go from TWRP to CWM here:
https://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286
Also once your fully on CWM/FireOS 3 you might be able to use this guide to downgrade too:
http://www.aftvnews.com/how-to-unroot-a-fire-tv-and-switch-back-to-stock-updates-from-amazon/
All of the above is theory for me. Since I've never had to dealt with this. And there are no guides for this specific scenario. So make sure you look thru the TWRP thread to find the folks that actually mention going back to CWM. Although most of them did so just to reflash TWRP.
Search example: https://forum.xda-developers.com/search/thread/3383286?query=back to cwm
Note 1: As of 16.5.0, Android lollipop (API 21) is required
_____________________________________
16.5.0 (2016/11/30):
CHG: API 21+ (Android 5.0) only, sorry.
ADD: 4K on AFTV2
ADD: refresh rate sync on AFTV
ADD: DASH support (aka 1080p/4K youtube)
ADD: Builtin log (Settings-System-Logging-Upload…)
ADD: crash handler (no need for logcat)
ADD: rendercapture (boblight, Hue, …) support for Surface
FIX: Only stop Surface when really necessary
CHG: Revert to Surface as standard
ADD: acceleration setting for hevc
16.4.2 (2016/08/15):
REVERT: crash when enumerating sound devices during a refresh rate change
FIX: Missing start of video with large buffer
You will need to find SPMC v16.4.2 for FireOS 3.
You can find it from source here: https://github.com/koying/SPMC/releases?after=17.0b3-Krypton
Click to expand...
Click to collapse
thanks dl'd it.
Y314K said:
There is no guide on how to go back to stock FW on a FTV1 once TWRP is install. This is due to the version of FW & TWRP that the FTV1's where first updated to FireOS 5. That was FW v5.0.5 & TWRP v6. So the TWRP had matured enough to fully block updates.
The only info regarding downgrading can be found in the TWRP thread. Folks that failed @ updating to TWRP correctly where able downgrade back to CWM. I think you also need to downgrade the FW to a PreRooted FireOS 3 too but I could be wrong. Once on CWM you should be able to allow updates since CWM won't block those updates.
Look/search for more info on the few folks that where able to go from TWRP to CWM here:
https://forum.xda-developers.com/fire-tv/development/firetv-1-bueller-twrp-recovery-t3383286
Also once your fully on CWM/FireOS 3 you might be able to use this guide to downgrade too:
http://www.aftvnews.com/how-to-unroot-a-fire-tv-and-switch-back-to-stock-updates-from-amazon/
All of the above is theory for me. Since I've never had to dealt with this. And there are no guides for this specific scenario. So make sure you look thru the TWRP thread to find the folks that actually mention going back to CWM. Although most of them did so just to reflash TWRP.
----------------------------------------------------------------------------------------------------------------------------------------
It worked exactly as your theory described.
you can consider this the official intructions to revert back to stock.
I was able to flash CWM, Rbox boot manager and fireos 3 via TWRP
once I was fully on CWM/FireOS 3 I was able to push the the stock recovery via ADB then the updates downloaded automatically until I got to the latest version.
I also found out If you flash the old firmwares you can only register the device with a code from amazon that they send via email.
Click to expand...
Click to collapse
evaporic said:
It worked exactly as your theory described.
you can consider this the official intructions to revert back to stock.
I was able to flash CWM, Rbox boot manager and fireos 3 via TWRP
once I was fully on CWM/FireOS 3 I was able to push the the stock recovery via ADB then the updates downloaded automatically until I got to the latest version.
I also found out If you flash the old firmwares you can only register the device with a code from amazon that they send via email.
Click to expand...
Click to collapse
Great, glad there is now tested method for this. :highfive:
Can you please be a bit more detail in your steps... Please fill in the blanks below. That way other folks don't have to guess.
My FTV1 started from PreRooted FW v________ & TWRP v___.
Use a Fat32 formatted USB Stick.
Download & add the following files to the USB Stick (Check hash's):
CWM Recovery 6.0.5.1.4a - (md5sum: 67b1a13b7bec645cb9291e80478d4635)
FireTV Boot Menu 1.0 - (md5sum: a8a3c28baafe43f354d92e6cc8b392d3)
FireTV 1 (bueller) Prerooted Stock Images [51.1.6.3_516012020] - (md5sum: fcf1a8ddf2f3bc93280af03dcf408ac8)
Connected a USB Keyboard & boot to TWRP recovery.
First wipe __________. (None if you didn't wipe anything first)
Using TWRP flash ____________________.
_________________________________________.
Please provide as much detail as possible. Thanks
Related
I have two FTVs both running old 51.1.1.0. Both of them have Kodi 14.2 and both crash shortly after I launch Kodi. They were both working fine and then both stopped working the same day. I thought there may have been an update, but that didn't happen. I can't figure it out and I'm really frustrated with these boxes. I'm ready to sell them and get something better. I can't even update them. Every way I try to update fails.
Any suggestions?
madtork said:
I have two FTVs both running old 51.1.1.0. Both of them have Kodi 14.2 and both crash shortly after I launch Kodi. They were both working fine and then both stopped working the same day. I thought there may have been an update, but that didn't happen. I can't figure it out and I'm really frustrated with these boxes. I'm ready to sell them and get something better. I can't even update them. Every way I try to update fails.
Any suggestions?
Click to expand...
Click to collapse
You have to provide a lot more info regarding your boxes. I am assuming your boxes are rooted or you blocked updates in your router because this is a very old firmware and if so you will not be able to update them over the air without enabling OTA updates.
Start here and read before you do anything (you can still keep root and update to latest OS3 s/w): http://www.aftvnews.com/start/
bula1ca said:
You have to provide a lot more info regarding your boxes. I am assuming your boxes are rooted or you blocked updates in your router because this is a very old firmware and if so you will not be able to update them over the air without enabling OTA updates.
Start here and read before you do anything (you can still keep root and update to latest OS3 s/w): http://www.aftvnews.com/start/
Click to expand...
Click to collapse
They both are rooted. I'm just trying to update Kodi. I thought it would be best to keep the old firmware. I've used the Windows utility app to try and install the new version of Kodi as well as the fire installer on an android phone. Nothing seems to work. This is the way I've always done it. Let me know what other information I can provide.
Not sure why you want to keep an older firmware (newer versions bring fixes and improvements) but that is up to you. Have you installed something on both units that lead to the system crash? It is very weird that both units stopped working at the same time. Have you try to clean cache (not data) and run kodi again? If this does not work do a back up, uninstall kodi, reset firetv, reinstall whatever version of kodi you like and run it (do not restore you back up yet) if all is good (opens up) exit kodi and restore your back up. If it still does not open then something got corrupted in your data files and you will have to reinstall everything from scratch.
bula1ca said:
Not sure why you want to keep an older firmware (newer versions bring fixes and improvements) but that is up to you. Have you installed something on both units that lead to the system crash? It is very weird that both units stopped working at the same time. Have you try to clean cache (not data) and run kodi again? If this does not work do a back up, uninstall kodi, reset firetv, reinstall whatever version of kodi you like and run it (do not restore you back up yet) if all is good (opens up) exit kodi and restore your back up. If it still does not open then something got corrupted in your data files and you will have to reinstall everything from scratch.
Click to expand...
Click to collapse
I've tried clearing cash. The reason I didn't take an OTA update for firmware is because I thought I couldn't root the newer versions.
madtork said:
I've tried clearing cash. The reason I didn't take an OTA update for firmware is because I thought I couldn't root the newer versions.
Click to expand...
Click to collapse
You can still update to latest firmware (using rbox prerooted images). Follow link I posted above and read, read, read before you do anything.
I think the same as bula1ca write down here.
First update to the last availible prerooted rom. Read it here how to do: http://www.aftvnews.com/start/
Another question from my side is: Why did you use kodi 14.2.
kodi 16 jarvis is availible and you can use it as launcher too with a pythin script here from the board.
Feel free to ask your question but please read enough before
Greetings by Idijt
I have a rooted AFTV1 with RBox's boot menu and root installed. I had all Amazon updates blocked via my router's firewall, but when I did a firmware upgrade on it.......it reset my configuration and the FTV was exposed to the update servers. When I realized this, I went to my FTV and it said that it was ready to install an update with a countdown. I was indeed lucky I caught it, and I immediately pulled the power. I was wondering how I should proceed to prevent this update that had been downloaded from running? Will a re-flashing of Rbox's pre rooted rom through the boot menu delete the Amazon update or where are the update files held (located) so I can find and delete them before they have a chance to execute?
I did power back on to be sure the boot menu was still there, but I don't want to fully boot this box again until I know how to prevent losing root & open bootloader for good. I know I should have disabled the update service in the firetv as a backup, but hindsight is 20/20. Thanks in advance.
This fellow deleted his.
HTML:
http://forum.xda-developers.com/fire-tv/general/firmware-update-5-0-5-1-t3351203#6
Adaptel said:
I have a rooted AFTV1 with RBox's boot menu and root installed. I had all Amazon updates blocked via my router's firewall, but when I did a firmware upgrade on it.......it reset my configuration and the FTV was exposed to the update servers. When I realized this, I went to my FTV and it said that it was ready to install an update with a countdown. I was indeed lucky I caught it, and I immediately pulled the power. I was wondering how I should proceed to prevent this update that had been downloaded from running? Will a re-flashing of Rbox's pre rooted rom through the boot menu delete the Amazon update or where are the update files held (located) so I can find and delete them before they have a chance to execute?
I did power back on to be sure the boot menu was still there, but I don't want to fully boot this box again until I know how to prevent losing root & open bootloader for good. I know I should have disabled the update service in the firetv as a backup, but hindsight is 20/20. Thanks in advance.
Click to expand...
Click to collapse
If you have the boot menue installed correct and running a pre-rotted image it should fail installation. Rbox build in stock image installation protection in his released pre-rooted images.
bula1ca said:
If you have the boot menue installed correct and running a pre-rotted image it should fail installation. Rbox build in stock image installation protection in his released pre-rooted images.
Click to expand...
Click to collapse
There is a post on AFTVnews that says that is not the case.
HTML:
http://www.aftvnews.com/twrp-custom-recovery-will-not-reject-a-stock-amazon-update/
2WhlWzrd said:
There is a post on AFTVnews that says that is not the case.
HTML:
http://www.aftvnews.com/twrp-custom-recovery-will-not-reject-a-stock-amazon-update/
Click to expand...
Click to collapse
You are confused, bud. This tread is about a Firetv 1st gen.
Post from AFTVnews is referring to a rooted Firetv 2 not 1 what I posted was regarding 1st gen Firetv. FYI rbox fixed recovery for FireTv2 as well in his latest TWRP release.
Adaptel said:
I have a rooted AFTV1 with RBox's boot menu and root installed. I had all Amazon updates blocked via my router's firewall, but when I did a firmware upgrade on it.......it reset my configuration and the FTV was exposed to the update servers. When I realized this, I went to my FTV and it said that it was ready to install an update with a countdown. I was indeed lucky I caught it, and I immediately pulled the power. I was wondering how I should proceed to prevent this update that had been downloaded from running? Will a re-flashing of Rbox's pre rooted rom through the boot menu delete the Amazon update or where are the update files held (located) so I can find and delete them before they have a chance to execute?
I did power back on to be sure the boot menu was still there, but I don't want to fully boot this box again until I know how to prevent losing root & open bootloader for good. I know I should have disabled the update service in the firetv as a backup, but hindsight is 20/20. Thanks in advance.
Click to expand...
Click to collapse
If you have ClockworkMod installed, the update should fail to install. That said, to be extra safe, I would boot into ClockworkMod and then connect to the device via ADB to have access to the file system. Then, with ADB shell, look for a .bin file in /cache or in /sdcard/Android/data/com.amazon.device.software.ota/files/
If you find one, delete it with the "rm" command.
I got a Fire TV Gen 2 rooted Firmware is 5.04 536116920. I need to upgrade the firmware and want to keep root Mainly because of the the Netflix glitch. I tried to follow the the guide http://www.aftvnews.com/how-to-upda...tv-to-the-latest-version-without-losing-root/ but I am getting nowhere
I do not think I got ClockworkMod installed but even for this I got permission error Chmod seems to be applied but no luck!
guliver365 said:
I got a Fire TV Gen 2 rooted Firmware is 5.04 536116920. I need to upgrade the firmware and want to keep root Mainly because of the the Netflix glitch. I tried to follow the the guide http://www.aftvnews.com/how-to-upda...tv-to-the-latest-version-without-losing-root/ but I am getting nowhere
I do not think I got ClockworkMod installed but even for this I got permission error Chmod seems to be applied but no luck!
Click to expand...
Click to collapse
Head over to AFTVnews.com again and look for his guide on fire tv 2.
You probably be best to install TWRP recovery and then the latest pre rooted ROM. Making sure after all steps you wont update it. As soon as your back into the os run the command to block updates.
Another good suggestion is to make a backup (preferably to micros sd card for space reasons) as soon as you can. Then after you have everything setup.
I just updated my fire tv 2 earlier today very simple to do when you have TWRP. The pre rooted roms are linked in his guide also.
The link you have been looking for is not what is used.
sconnyuk said:
Head over to AFTVnews.com again and look for his guide on fire tv 2.
You probably be best to install TWRP recovery and then the latest pre rooted ROM. Making sure after all steps you wont update it. As soon as your back into the os run the command to block updates.
Another good suggestion is to make a backup (preferably to micros sd card for space reasons) as soon as you can. Then after you have everything setup.
I just updated my fire tv 2 earlier today very simple to do when you have TWRP. The pre rooted roms are linked in his guide also.
The link you have been looking for is not what is used.
Click to expand...
Click to collapse
Yes you got it right I Finally updated to 5.2.1.0 and added TWRP following this guide http://www.aftvnews.com/how-to-root-the-amazon-fire-tv-2 for a while I was scared since the amazon app was saying update in progress I even rebooted several time to prevent it and stop my rooter but everything is fine and I added the "pm disable com.amazon.device.software.ota"
I Just need to install fire starter if it is working with this version
I just updated today from the out-of-box (i think 5.0.1) version that I rooted to the latest images from April 2016 (TWRP as well), and firestarter has been lost for me. I ran a suggested adb line to enable the app (apparently the OS blocks firestarter by name, and has the ability to blacklist/block apps like that without OTA updates). Even though the app showed back up, it's functionality is lost. I've tried firestopper as well, but the FireOS seems to break the homebutton detection, which is why I used the app. Fortunately, I enjoy the new FireOS ability to double-tap home button and see a list of apps, which is where Kodi actually shows up for me, since it won't show in the Recent Apps. Good luck, just wanted to post my anectdote!
I've seen that some people were able to successfully downgrade AFTV1 after rooting with Dirtycow. I'm able to get root, but downgrade doesn't seem to work and I don’t know what I’m doing wrong.
I have an amazon fire TV V1 with 51.1.4.0_User_514006420 software version. I downloaded the 51.1.0.2_user_510058520 update, renamed it to update.zip, followed the guide (here: http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/) for changing the ROM. When I do adb reboot recovery I get this message:
“System update was not successful. Your amazon fire tv will restart in a few minutes and should resume normal operation.”
When it restarts, it’s still on the same version I had. I’ve tried pushing the stock recovery image like the bottom of the upgrade/downgrade guide suggested, but it doesn’t seem to work. Does someone have any other ideas on how to get this to work?
I checked that the update checks out with the md5 hash. I just can’t get it to work. What should I try to do next? Is there a better guide? I'd like to install a pre-rooted ROM.
On the off chance that Amazon changed the 51.1.0.2 image they are serving, try downloading and using the one from here. Then follow my guide here to install it. You should also check the md5 hash value of the 51.1.0.2 image AFTER it has been transferred to the FTV1 by following this guide.
If you still have problems, copy and paste your entire ADB/shell text here so I can see if you did anything wrong.
@AFTVnews.com thanks for the response! I checked the md5 and it seemed to have matched. I re-ran through the steps an it appears I may have put command in cache instead of cache/recovery. It pushed successfully.
Now... it seems like that version of AFTV is strange. It has a lock screen and my aftv remote won't allow me to unlock it. Here is an image of what I see: Locked Amazon fire TV Screen so I can't open it to run towel root. Any ideas?
Update: I was able to get passed the lock screen by clicking a bunch of buttons on the remote at the same time. I'm rooted again! I'll continue the guide! Thanks for your work on this!
Update2: I'm running the latest version of the rooted software. Thanks for the guides!
uofirob said:
@AFTVnews.com
Update2: I'm running the latest version of the rooted software. Thanks for the guides!
Click to expand...
Click to collapse
Awesome. Glad it worked out.
Last night, I stopped after the custom latest rooted version of the ROM was installed. I keep getting "Amazon is unable to connect to the service" when going to the different menu options. Do I have to disable my firewall rules on my router, or was it just an oddity?
AFTVnews.com said:
Awesome. Glad it worked out.
Click to expand...
Click to collapse
I confirmed that I'm still getting the unable to connect to service last night. Should I just do a factory reset? Would that help? At this moment, the only way for me to launch apps is to go through System -> Manage Applications and it's really annoying. I was able to confirm that Kodi was able to connect to the internet, so I know that it's not the connection.
uofirob said:
I confirmed that I'm still getting the unable to connect to service last night. Should I just do a factory reset? Would that help? At this moment, the only way for me to launch apps is to go through System -> Manage Applications and it's really annoying. I was able to confirm that Kodi was able to connect to the internet, so I know that it's not the connection.
Click to expand...
Click to collapse
Since you're rooted and on the latest prerooted ROM, you should remove the domain blocks on your router/firewall. It sounds like that's the issue. Just be sure you have done method 1 at the very least from my update blocking guide. You can also do method 5 to be extra safe.
I tried removing the firewall blocks but I still get "We are currently unable to contact our servers." Should I re-add the firewall blocks and factory reset?
UPDATE: I was able to resolve this by signing in to my amazon account. Apparently for some reason it signed me out. Thanks for all of your help!
AFTVnews.com said:
Since you're rooted and on the latest prerooted ROM, you should remove the domain blocks on your router/firewall. It sounds like that's the issue. Just be sure you have done method 1 at the very least from my update blocking guide. You can also do method 5 to be extra safe.
Click to expand...
Click to collapse
Filmstruck app on FTV1 rooted with 5.2.4.1r2 rom - 573210720
Menu selections starts at top (Filmstruck) goes down to browse, then settings. Going back up, it goes to browse, then to Criterion Channel. So can not access Watchlist or Search, and can only access Filmstruck after first opening the app. If you have already gone down a menu selection, you can't go back up to it. I don't remember which version this issue started with but I tried going back a couple rom versions with the same results.
Can anyone else confirm this on theirs or have any idea how to fix it? I have 2 FTV1 boxes and an FTV Stick 1, all rooted. I'd hate to have to go back to stock for one app but since I'm paying for the service (Filmstruck) I may have to.
Video of how it is not working https://youtu.be/uz_JEjfbv18
For what it's worth I did try older versions of the app as well as side loading the app from my kindle fire HD 8 tablet (rooted) where it works just fine. Also works fine on my phone running android nougat and PC. The side loaded app would just start to open and then close.
New versions for Amazon and Google Play - no fix
So there was an update to the Filmstruck app 3.1.1 on Amazon Appstore and 3.1.0 on the Google Play Store. Same results exactly. Both versions work fine on the tablet. Both versions have same exact menu navigation issues on the FTV 1. I'm about to throw in the towel and just give up being rooted and go back to stock. I'd really like to confirm that would be the solution before I go that route though. Can anyone else confirm they do or don't have this issue on their rooted FTV1 or if it works fine on unrooted? Right now all I can do is play it on my tablet and cast to the TV which is pretty frustrating. Thanks in advance for any thoughts on this.
Works fine on new unrooted FTV STick 2
OK, the suspense was killing me so I went and bought a Fire TV Stick 2 for testing. Opened up network so it would take updates if it needed them, set it up, installed the Filmstruck app, and everything worked perfectly. (Except I couldn't adjust the video scaling, but that's just because I have an old TV)
So I guess this confirms there is an issue with the Filmstruck app and the latest prerooted rom versions for the FTV1 and FTV1 Stick.
Finally decided to pull the trigger on unrooting and going back to stock on the FTV Stick 1 that I had. Now the Filmstruck app works perfectly as it should. Hopefully someone can figure this out before I just give up and toss root out the window on my other two FTV 1 boxes.
drewb0y said:
Finally decided to pull the trigger on unrooting and going back to stock on the FTV Stick 1 that I had. Now the Filmstruck app works perfectly as it should. Hopefully someone can figure this out before I just give up and toss root out the window on my other two FTV 1 boxes.
Click to expand...
Click to collapse
One option is to keep TWRP & root access but remove the SU folder from the PreRooted ROM before flashing. This will have u running unRooted (no SU manager) with the option to flash SU or root access in the future. Just make sure you are still blocking updates probably thru Method 2.
Y314K said:
One option is to keep TWRP & root access but remove the SU folder from the PreRooted ROM before flashing. This will have u running unRooted (no SU manager) with the option to flash SU or root access in the future. Just make sure you are still blocking updates probably thru Method 2.
Click to expand...
Click to collapse
I will try that out while I'm in the process of unbricking one of my other FTV 1 boxes. Didn't realize it would be as simple as removing the su folder. I'll report back with my findings. I'm surprised no one else had this issue reported yet. There's an awesome library of movies available with that app.
drewb0y said:
I will try that out while I'm in the process of unbricking one of my other FTV 1 boxes. Didn't realize it would be as simple as removing the su folder. I'll report back with my findings. I'm surprised no one else had this issue reported yet. There's an awesome library of movies available with that app.
Click to expand...
Click to collapse
Will have to try that App out. Thanks for the heads up. RBox mentioned that was possible even before the PreRooted FireOS 5 Rom's started to come out. And a few folks have mention success. As long as the updates are blocked. You should be able to keep updating the ROM as long as you remove the SU folder. Best of both worlds.
Y314K said:
Will have to try that App out. Thanks for the heads up. RBox mentioned that was possible even before the PreRooted FireOS 5 Rom's started to come out. And a few folks have mention success. As long as the updates are blocked. You should be able to keep updating the ROM as long as you remove the SU folder. Best of both worlds.
Click to expand...
Click to collapse
Well it took some major convolutions on my part but that was mostly because the box I was working with was on old CWM with the boot menu and stuck in a reboot loop. After finally getting the zip without su pushed over, TWRP would say the file was corrupt. I originally used the windows built in zip manager. After redoing it with WinRAR it all loaded perfectly. On reboot I had to reregister, reinstall the app, and guess what? It works perfectly now. So I'm on the latest ROM 5.2.4.1r2 minus the su folder. Thanks a ton!
drewb0y said:
Well it took some major convolutions on my part but that was mostly because the box I was working with was on old CWM with the boot menu and stuck in a reboot loop. After finally getting the zip without su pushed over, TWRP would say the file was corrupt. I originally used the windows built in zip manager. After redoing it with WinRAR it all loaded perfectly. On reboot I had to reregister, reinstall the app, and guess what? It works perfectly now. So I'm on the latest ROM 5.2.4.1r2 minus the su folder. Thanks a ton!
Click to expand...
Click to collapse
Did u used a MD5 file for verification of the modded zip? That never worked for me last time I tried. Guess something was hard coded.
Make sure you verify you got at least the Method 2 of update blocking working. TWRP should also block updates. But at least one extra Method is good for piece of mind.
And don't forget to share the knowledge...
Fixed
Y314K said:
Did u used a MD5 file for verification of the modded zip? That never worked for me last time I tried. Guess something was hard coded.
Make sure you verify you got at least the Method 2 of update blocking working. TWRP should also block updates. But at least one extra Method is good for piece of mind.
And don't forget to share the knowledge...
Click to expand...
Click to collapse
No MD5 file as it would not match with the SU folder removed. It would be a different size. I do have the update domains blocked through the router as well as through my Pi-Hole network wide ad blocker. So two layers there. That and there may not be any updates for FTV1 any time soon. Thanks again!
I could create an MD5 file and post that as well as the zip with the SU folder removed if you want to try it out.
drewb0y said:
No MD5 file as it would not match with the SU folder removed. It would be a different size. I do have the update domains blocked through the router as well as through my Pi-Hole network wide ad blocker. So two layers there. That and there may not be any updates for FTV1 any time soon. Thanks again!
Click to expand...
Click to collapse
drewb0y said:
I could create an MD5 file and post that as well as the zip with the SU folder removed if you want to try it out.
Click to expand...
Click to collapse
No problem. I tried to create a new MD5 file before to match the modded ROM. But there seem be something hard coded. Since it would still fail in TWRP. That is why I asked.
Y314K said:
No problem. I tried to create a new MD5 file before to match the modded ROM. But there seem be something hard coded. Since it would still fail in TWRP. That is why I asked.
Click to expand...
Click to collapse
Gotcha. It seemed to load just fine without the MD5.
Well it worked for a few weeks and then back to the same behavior as before. Going to try unrooting again.