Hey all,
I've got a new fire tv with firmware 51.1.0.1 and in the process of rooting I had an event that pulled me away from my activity and allowed the ota update to be downloaded. It's not installed yet, and I'm wondering if anyone can point me in the right direction to prevent the install (directory where updates are stored maybe?). Any help is much appreciated, and I'm guessing I've got a pretty short fuse to pull this off before the unit decides I'm not using it, and pushes the install.
Thanks!
Not sure why that took so long for meto find, but there was a signed bueller file in the root cache directory that matched the serial that the ota updater grabbed. I killed it, and am now hoping for the best.
com.amazon.dcp is now disabled, so yay for that.
Update: Success. Rebooted the device, and no update. Win.
Related
I rooted my kindle when I got it a few months ago, and ran an OTA blocking script, but it auto-updated and removed root anyway. I tried again after the 8.3.1 release, yet I still find I'm on 8.4.1 and root is gone. Obviously, I need to do something different this time.
Can anyone point me to a successful OTA blocking update that I can run when I'm done re-rooting again, please?
And is there anyway to tell my Kindle not to put all of my books into the carousel when it's done reloading them since I don't really want to long-press, remove from carousel, another 982 times? Or is there an option for a quick empty of the carousel somewhere? I've looked and never found anything.
Thank you in advance!
Hello
I just fresh installed the latest pre-rooted firmware (thanks as always rbox.. beer on me incoming!) and I forgot to do the "yank the ethernet cable" trick to get past the initial update. My router has the domains blocked and previously they were working fine, so I would have expected the check to fail, but it happily went though to the registration screen. Of course there are no updates since this is the latest, so no harm done this time round, but just wondering if any domains may have changed?
Also checking update status in "About" and it says last checked today (normally it just says "Checking now...."). When I click on Check for Updates, it says there was an error. Which suggests nothing has changed, but I'm confused by the above.
The other possibility is that the new firmware doesn't hang on checking for updates, so if it fails it just goes through anyway (good for peeps who are having internet trouble, etc).
Anyone else have this experience? I have updates disabled so not too worried, but just wondering for future reference in case I need to fresh install and a newer update is out.
Cheers
Try downloading the update through aftvnews, it may be your firewall isn't blocking it.
I just discovered my Asus router wasn't blocking the updates until I re-enabled the firewall.
edit:
Or may because you're on the latest update it skipped the update.
eskay993 said:
Hello
I just fresh installed the latest pre-rooted firmware (thanks as always rbox.. beer on me incoming!) and I forgot to do the "yank the ethernet cable" trick to get past the initial update. My router has the domains blocked and previously they were working fine, so I would have expected the check to fail, but it happily went though to the registration screen. Of course there are no updates since this is the latest, so no harm done this time round, but just wondering if any domains may have changed?
Also checking update status in "About" and it says last checked today (normally it just says "Checking now...."). When I click on Check for Updates, it says there was an error. Which suggests nothing has changed, but I'm confused by the above.
The other possibility is that the new firmware doesn't hang on checking for updates, so if it fails it just goes through anyway (good for peeps who are having internet trouble, etc).
Anyone else have this experience? I have updates disabled so not too worried, but just wondering for future reference in case I need to fresh install and a newer update is out.
Cheers
Click to expand...
Click to collapse
Just an observation...you shouldn't need to do the Ethernet trick with custom recovery when updating prerooted firmware. It will check for updates then nothing should happen.
I've been running the same prerooted firmware for a long time so my memory isn't perfect but I thought just updating it wouldn't take you to the registration screen??? Unless maybe this new firmware isn't set up like rbox's. Are you saying you had to setup your account, check adb and unknown sources, reinstall apps, etc? This would occur if you wiped data before installing the update maybe...
Anyways. If it running OK I wouldn't worry much about it.
KLit75 said:
Just an observation...you shouldn't need to do the Ethernet trick with custom recovery when updating prerooted firmware. It will check for updates then nothing should happen.
I've been running the same prerooted firmware for a long time so my memory isn't perfect but I thought just updating it wouldn't take you to the registration screen??? Unless maybe this new firmware isn't set up like rbox's. Are you saying you had to setup your account, check adb and unknown sources, reinstall apps, etc? This would occur if you wiped data before installing the update maybe...
Anyways. If it running OK I wouldn't worry much about it.
Click to expand...
Click to collapse
Thanks for the reply. Yes I did a complete fresh install / format data etc. Wanted to start fresh. I have done full wipe install with rbox's previous firmware in the past and I did have to do the ethernet trick to get to the registration screen. But not with this latest. My guess is Amazon have changed it so that it doesn't just hang if it encounters an error at the stage. Or something else has changed.
My router is definitely blocking the servers. Once I am in KFTV launcher, it shows they are being blocked (updates just says "Checking now..."). So probably nothing to worry about, just wanted to be ready, so to speak, in case I need to do another fresh install in future.
eskay993 said:
Thanks for the reply. Yes I did a complete fresh install / format data etc. Wanted to start fresh. I have done full wipe install with rbox's previous firmware in the past and I did have to do the ethernet trick to get to the registration screen. But not with this latest. My guess is Amazon have changed it so that it doesn't just hang if it encounters an error at the stage. Or something else has changed.
My router is definitely blocking the servers. Once I am in KFTV launcher, it shows they are being blocked (updates just says "Checking now..."). So probably nothing to worry about, just wanted to be ready, so to speak, in case I need to do another fresh install in future.
Click to expand...
Click to collapse
I tested this out. With the latest firmware that was just released by rbox. The update still shows the same error as before. After every update. I ensure that I disable the update service via SU and the update links are blocked on my router anyways. I don't do opendns as I believe in manual physical blocking.
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'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
Hi guys. I have a FireTV 4k box. The 2nd gen one.
When I bought it way back upon release a few years ago, I rooted it, used it for a bit, and put it in a box. Just recently I took it back out and started using it again.
Whatever method I used to root it etc is unknown, as it was afew years ago, and I can't find anything similar anywhere online. At the time, downloader wasn't a thing, and you had to adb in and sideload apps.
I am currently on 5.2.6.3
The box won't update at all.
I adb' into the box, and found SU doesn't work. I was able to get temp root via mtk-su and successfully ran the pm unhide com.amazon.device.software.ota and pm enable com.amazon.device.software.ota commands.
The firetv will now at least SEARCH for updates (where it wouldn't before) but doesn't find any to install.
The manage_recovery command to check status won't run. Says manage_recovery not found.
I'm not sure what to do next.
I just want it back to completely stock.
I'm having issues with apps working, but upon restart of the firetv the somehow get transferred to a non-existent sd card and will no longer run.
Netflix in particular.
Can you guys give any guidance here?
zx7ninja said:
Hi guys. I have a FireTV 4k box. The 2nd gen one.
When I bought it way back upon release a few years ago, I rooted it, used it for a bit, and put it in a box. Just recently I took it back out and started using it again.
Whatever method I used to root it etc is unknown, as it was afew years ago, and I can't find anything similar anywhere online. At the time, downloader wasn't a thing, and you had to adb in and sideload apps.
I am currently on 5.2.6.3
The box won't update at all.
I adb' into the box, and found SU doesn't work. I was able to get temp root via mtk-su and successfully ran the pm unhide com.amazon.device.software.ota and pm enable com.amazon.device.software.ota commands.
The firetv will now at least SEARCH for updates (where it wouldn't before) but doesn't find any to install.
The manage_recovery command to check status won't run. Says manage_recovery not found.
I'm not sure what to do next.
I just want it back to completely stock.
I'm having issues with apps working, but upon restart of the firetv the somehow get transferred to a non-existent sd card and will no longer run.
Netflix in particular.
Can you guys give any guidance here?
Click to expand...
Click to collapse
I know you wish to go back to stock but perhaps you may wish to use the new and improved root (Magisk or Supersu) and upgrade your box that way.
The Sloane 2nd generation Firetv Box can now be fully unlocked. This will allow you to upgrade your box to a more recent firmware.
A simple step by step guide can be found here :
[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)
Read this whole guide before starting. This is for the 2nd gen Fire TV (sloane) Current relase: amonet-sloane-v1.1 NOTE: This process does not require you to open your device if you're already rooted or you have TWRP. NOTE: If something goes...
forum.xda-developers.com
Hope this helps
Regards
That is a good idea, and may work. I'll give it a shot and see what happens, thanks!
Hopefully it fixes whatever bug is causing apps to flag as installed on a non-existent SD card and no longer run.
All I'm looking for, really.
zx7ninja said:
That is a good idea, and may work. I'll give it a shot and see what happens, thanks!
Hopefully it fixes whatever bug is causing apps to flag as installed on a non-existent SD card and no longer run.
All I'm looking for, really.
Click to expand...
Click to collapse
Yeah it's just really old firmware tbh so the cert.zip and/or the ota update apks are probably deprecated.
Goto unlock root twrp unbrick Sloane thread here :
[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)
Read this whole guide before starting. This is for the 2nd gen Fire TV (sloane) Current relase: amonet-sloane-v1.1 NOTE: This process does not require you to open your device if you're already rooted or you have TWRP. NOTE: If something goes...
forum.xda-developers.com
Just have a read through the OP on page one and familiarise yourself. Follow it to the letter and you'll be able to update your box no problem.
If you need any help just ask and someone will be around to help you out if need be.
Regards
Is there an advantage of doing this over the pre-rooted rooms flashed in TWRP? I have a rooted fire TV v2 that I have done periodic updates on but it seems like it always has another update to do. Updates are blocked but it pops a message randomly saying there is and update giving 60 seconds to respond or it reboots trying to update. Would this method of root/updates be easier or more up to date?
ottoguy said:
Is there an advantage of doing this over the pre-rooted rooms flashed in TWRP? I have a rooted fire TV v2 that I have done periodic updates on but it seems like it always has another update to do. Updates are blocked but it pops a message randomly saying there is and update giving 60 seconds to respond or it reboots trying to update. Would this method of root/updates be easier or more up to date?
Click to expand...
Click to collapse
Definitely unlock Sloane with this new method.
IMO you have FULL control over the box. Also you have more easier management of your root access (Magisk Manager)
OTA can be handled easily either by adb command or use an app such as luckypatcher to disable/enable ota onscreen.
I would recommend this unlock to anyone wanting a more upto date root and fireos.