URL for updates appears to have changed. Now it's HTTPS and the OTA is now being pulled from https://amzdigital-a.akamaihd.net. Unfortunately I don't have SSL sniffing enabled so I can't give you the links.
Installed the update, rooting fails with KingRoot 4.1. Reset to factory defaults, installed Kingroot 4.1, rooting failed :crying:
Old method of flashing the recovery first from rbox still works. For now you need to downgrade to pre-rooted 5.0.5.0, until rbox releases a pre-rooted 5.0.5.1:
Rooting is still possible:
- Download install_firetv2_recovery_v3.zip
- Download firetv2_recovery_v5.zip
- Extract both to same folder
- Run install_firetv2_recovery.bat
- Plug in power to AFTV2 and let it flash the recovery.
- When it's done copy ramdisk-recovery.cpio.lzma and sloane-5.0.5-rooted_r4.zip firmware to a NON corrupt usb or sdcard
- Reboot, choose recovery with a keyboard
- Install the 5.0.5.0 firmware
- Boot and bingo :good:
1st Gen?
Sent from my SM-N900V using Tapatalk
roligov said:
Some how got both URLs for the full firmware version and the OTA.
Download link:
Code:
http://amzdigitaldownloads.edgesuite.net/obfuscated-otav3-6/8921f843c5dc154a747edb468b3b773f/update-sloane_full_sloane-536116920-to-537174420.bin
Code:
http://amzdigitaldownloads.edgesuite.net/obfuscated-otav3-7/471d77e1c3ad23df4a469c8b88a0c200/update-kindle-full_sloane-36.5.3.7_user_537174420.bin
Will attempt root after it installs...
Click to expand...
Click to collapse
Do you have more then one version of a FTV device... aka Fire TV (1st Gen), Fire TV Stick, Fire TV (2nd Gen) ?
I do have multiple AFTV1s and AFTV2s, but only 1 is configured to go through my PC as a proxy. The full firmware is the one my AFTV2 is downloading. Will update in a few minutes....
roligov said:
Sorry ignore this. This thread can be trashed, this is an AFTV2 that was sitting in the cupboard not on 5.0.5.0. Still odd the full update came through? Thought all firmware updates were OTA's, Sorry guys!
Click to expand...
Click to collapse
By chance, did that AFTV2 have FireStarter installed prior to updating to 5.0.5 just now? If so, can you check to see if FireStarter is still listed in your Settings > Applications list?
I saw some strange behavior on one of my boxes that makes me think the new issues envolving FireStarter are not limited to the 5.0.5.1 update.
Sorry developing news: 1 firetv2 was on an old firmware, so it got the 5.0.5.0 update and nothing further.
Another FireTV2 of mine had the 5.0.5.1 update on the box and was ready to install it. I had to remove the update from /mnt/shell/emulated/0/Android/data/com.amazon.device.software.ota/files/update-kindle-full_sloane-36.5.3.7_user_537175520.bin
I will sniff the link again quick.
Bad news, the URL for updates has changed to HTTPS. The firmware is now being pulled from https://amzdigital-a.akamaihd.net. Unfortunately I don't have SSL sniffing enabled so I can't give you the links.
Elias: New article for you: Be aware if you haven't disabled the updates via package manager and are blocking via your router, your device will get the OTA as that site is not 1 of the 3 we currently block.
Rooting appears to be blocked on 5.0.5.1, at least with KingRoot 4.1
Tried Kingroot v4.8.5, still failed. It's official. Amazon have decided to be c*nts. Rooting is blocked in 5.0.5.1. Sound the alarm bells, run for the hills! DO NOT UPDATE if you enjoying root!
I can also confirm that Firestarter is broken and will not work after a reboot, this is the error you will get:
http://i.imgur.com/WD0dZTU.png
Image of rooting failed with KingRoot: http://i.imgur.com/2G9zHb5.png
roligov said:
Bad news, the URL for updates has changed to HTTPS. The firmware is now being pulled from https://amzdigital-a.akamaihd.net. Unfortunately I don't have SSL sniffing enabled so I can't give you the links.
Elias: New article for you: Be aware if you haven't disabled the updates via package manager and are blocking via your router, your device will get the OTA as that site is not 1 of the 3 we currently block.
Click to expand...
Click to collapse
sorry for asking but which packages do you've blocked to prevent the box updating?
I've already disabled two services with adb but now I'm not sure if I'm safe or not.
Go to http://www.aftvnews.com/block and follow method 1, that's probably your safest bet. Second just add the new URL above to method 3, even though it's https, the URL can still be blocked because only the traffic is encrypted not the URL.
Last image before I go to bed. Proof I have the 5.0.5.1 update: http://i.imgur.com/VVmdG7U.png
Just because they're using HTTPS doesn't mean blocking via DNS or router methods won't work, it just means you can't easily sniff out the full URL of the update. Something like Charles Proxy would allow you to decrypt SSL during the proxy, this assumes that the client (Fire TV) is either not validating certs or you can install the cert you're using in Charles on the device itself.
bubbanc said:
Just because they're using HTTPS doesn't mean blocking via DNS or router methods won't work, it just means you can't easily sniff out the full URL of the update. Something like Charles Proxy would allow you to decrypt SSL during the proxy, this assumes that the client (Fire TV) is either not validating certs or you can install the cert you're using in Charles on the device itself.
Click to expand...
Click to collapse
You can block via DNS, but you can't block via URL. To block via URL a router has to do packet inspection to inspect the HTTP request, and when using HTTPS, it's encrypted so the router can't do that. The FireTV does validate certificates, and you need root to be able to add one.
bubbanc said:
Just because they're using HTTPS doesn't mean blocking via DNS or router methods won't work, it just means you can't easily sniff out the full URL of the update. Something like Charles Proxy would allow you to decrypt SSL during the proxy, this assumes that the client (Fire TV) is either not validating certs or you can install the cert you're using in Charles on the device itself.
Click to expand...
Click to collapse
Correct. But it probably depends on your router, but my router is a Mikrotik and it can block at layer 7 (application layer in OSI). Because the URL request is in plain text, it can still block it. I've tested and confirms it works on the Mikrotik. The issue is that this is a new url that we have not been blocking, meaning those who are only blocking via router or dns will still get this update.
is this the way to block it? or need to put https in front of it?? thanx
So on an unrooted device this update deletes Firestarter but moves all apps to the recent section, so no big loss here. One major problem I'm having though is that DTS and Dolby Digital Audio is not working at all in Kodi (16.0)
htchd2fix said:
is this the way to block it? or need to put https in front of it?? thanx
Click to expand...
Click to collapse
http://forum.xda-developers.com/fire-tv/general/block-ota-updates-root-fire-os-5-t3183134
Bramton1 said:
http://forum.xda-developers.com/fire-tv/general/block-ota-updates-root-fire-os-5-t3183134
Click to expand...
Click to collapse
Does this method work with https?
Related
I recently decided to block to next update just in case amazon breaks my root again. I went about trying to usual, freezing the process (but I couldnt find the service with app quarantine) to redirecting the server to 127.0.0.1 in the hosts file (which I never got working either, it never blocked amazonaws.com)
What I ended up doing was blocking amazonaws.com in my router, and now everytime my fire powers up I get a dialog saying "the Wi-Fi network you are connecting to requires you to sign in before accessing the internet. Would you like to sign in" and the wifi signal icon always has an X on it now.
Question is, is this a common phenomena when blocking the server?
Do any of the other methods not pop up this dialog box?
that worked for me:
kf was and is registered
removed /system/etc/security/otacerts.zip -> update downloaded but did not install -> was automatically deleted from cache folder after failed attempt to install
no guarantee !!!
Is the update installed from cache our the kindleupdate folder? I have some other ideas on blocking, but I am notsure on this part.
Sent from my SAMSUNG-SGH-I897 using xda premium
I used app quarantine, and locked OTASilentInstall. I would provide a link, but I can't yet.
Also added:
127.0.0.1 s3.amazonaws.com
Hoping it stops the updates.
this will not work ! - allready tested and confimed
the only working and confirmed method is to deregister !
i did not deregister, watched the download ... see above
for me my method worked and i see it as confirmed for me.
btw. use the search function - there is a quite big thread about this !
So even after actually locking down the OTA app it will still update?
for shure !
Just reply when you know the update is being sent in OTA so JCase can release root.
So if anyone intends on getting the update and not rooting,give us a heads up when you receive the update.
retroben said:
Just reply when you know the update is being sent in OTA so JCase can release root.
So if anyone intends on getting the update and not rooting,give us a heads up when you receive the update.
Click to expand...
Click to collapse
Root already released by GeoHot via towelroot.com
Thanks for using this thread.
I could have also said to reply if any form of root becomes available to Fire TV before the OTA update.
I am already rooted,and have already fixed up my hosts file for blocking the OTA links using a hosts editor app from google play..
I would imagine an update must be coming soon now that a root exploit has been made public. Better make sure you're DNS settings are solid and best to root and block updates sooner rather than later.
For those who have rooted, you can run this command in adb shell to completely disable the updater:
pm disable com.amazon.dcp
You can verify in the system -> about it says "Checking now" for "Last Checked" on the update.
I just did that,and it said killed.
I still see the last date it was checked.
When should I see "checking in "last checked" option?
So in the terminal app I use to sideload other apps on my Fire TV I type:
adb shell pm disable com.amazon.dcp
Is that right?
I would try just
adb shell
and then at the prompt type
pm disable com.amazon.dcp
You might need to reboot to get the menu to change.
rbox said:
I would try just
adb shell
and then at the prompt type
pm disable com.amazon.dcp
You might need to reboot to get the menu to change.
Click to expand...
Click to collapse
Does killing the updater survive a hard reboot, for example after a power cut?
If not, how could I set the command to run at boot ?
Thanks for all the work on this great device so far :good:
can't u just rename the updater apk to something else? btw what is the name of the apk?
Yes the pm disable is permanent.
Yes you can rename the apk, but why rename the apk when the pm disable is infinitly easier? The apk is /system/app/com.amazon.dcp.apk
I am using js terminal on my android tablet to sideload everything. How can I execute this command this way?
I tried adb shell but got an error. Thanks!
Nevermind, I found some directions for that!!!
rbox said:
I would try just
adb shell
and then at the prompt type
pm disable com.amazon.dcp
You might need to reboot to get the menu to change.
Click to expand...
Click to collapse
I plan to disable updates per the above instructions, but are these commands reversible as well? If Amazon releases an update that brings additional functionality down the road, I may reconsider my decision to update (and potentially re-root with another method).
vyktym said:
I plan to disable updates per the above instructions, but are these commands reversible as well? If Amazon releases an update that brings additional functionality down the road, I may reconsider my decision to update (and potentially re-root with another method).
Click to expand...
Click to collapse
pm enable com.amazon.dcp will, well, enable it again.
JPDeckers said:
pm enable com.amazon.dcp will, well, enable it again.
Click to expand...
Click to collapse
Thanks!!
JPDeckers said:
pm enable com.amazon.dcp will, well, enable it again.
Click to expand...
Click to collapse
This made me laugh :good:
Blocking URL's
Not ready to root until ClockWorksMod Recovery is available but want to be able to root when this is true.
http://forum.xda-developers.com/showthread.php?t=2760884
Found this thread about blocking URL's. Seems like this is what is needed if we don't root until more options and tools are available for rooted FTV..
I am using Linksys E4200 and using Access Restriction > Parental Controls option. Pasted the plain text copies of URLS's which were transferred to router version below. Since URL 1's translation was too long I had to manually paste cut off ".net" in URL 1. Set access to always.Target Devices > Restrict Internet Access need to add FTV device.
Block Specific Sites
amzdigitaldownloads.edges.net ****Edit: this should be **** amzdigitaldownloads.edgesuite.net ****
firs-ta-g7g.amazon.com
Schedule Block Internet Access
Always
Target Devices Restrict Internet Access
android-c770a088dec6570f
android-f28e25ac80891726
Android_A10000138BBBB8
Two questions. Not sure what FTV is listed as. Other devices showed up with name so I know not to add them. Guessed the three "android" names above that one was FTV. Does anyone know if this is correct and if correct which one is my FTV? If not correct what is is called?
For Block Specific Sites is the first URL necessary and does blocking it cause problems with some of the current FTV apps?
You are missing part of the digital downloads site.
It should be "edgesuite" not edges.
The amzdigitaldownloads link can cause services to fail,but services do not fail when only blocking the "firs-ta-g7g" page.
Even the PolarisGo app fails to work,but the website works fine.
retroben said:
You are missing part of the digital downloads site.
It should be "edgesuite" not edges.
The amzdigitaldownloads link can cause services to fail,but services do not fail when only blocking the "firs-ta-g7g" page.
Even the PolarisGo app fails to work,but the website works fine.
Click to expand...
Click to collapse
I switched to only blocking firs-ta-g7g.amazon.com. This should be ok, right? What people at thread were blocking.
Used my router to find FireTV was 192.168.1.126. Checked Status > Local Network > DHCP Client Table
Saw that android-f28e25ac80891726 was mapped to 192.168.1.126 which FireTV said it was using. Deleted other entries.
I just bought a fire TV from best buy for my dad I'm about to set it up for the first time then root has an update that kills root came out yet or am I good to go?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
bradr00lzd00d1 said:
I just bought a fire TV from best buy for my dad I'm about to set it up for the first time then root has an update that kills root came out yet or am I good to go?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just bought a FTV last night from best buy as well. I booted it up and updated it prior to rooting it. Not sure if next week's update will patch this rooting method, but I do not want to make that mistake again. I updated my chromecast when they first came out like an idiot... and can't ever root those
Overview, Not instructions please read and do not rely on this. written just for ****s and giggles.
I haven't done a firetv since October.
Using the firetv serial decoder from aftv.news, it said that it was a 51.1.01 but it was actually 51.1.1.0. I needed to use the same method from the firetv stick to bypass updating. (quickly pulling wan network plug immediately upon a wirelesss connect to the network upon receiving"connection successful" and then blocking updates with router and reconnecting wan cable and registering when registration screen comes up)
Enable adb from settins\system\dev menu.
sideloaded towelroot.apk superuser.apk and busybox.apk and run install from within busybox.
I then rooted device with towelroot. and then blocked OTA updates with "pm disable com.amazon.dcp" command. (not needed if router blocked but done just incase)
I needed to downgrade recovery to the first stock recovery so I could downgrade the Firmware to 51.1.0.2.
After downgrade 51.1.02 re-rooted with towelroot again, blocked ota updates with "pm disable com.amazon.dcp" command.
Unlocked bootloader with "aftv-unlock unlock" command, installed clockworkmod.
Updated to rbox prerooted Oct 30, 2014 - Added 51.1.4.0_514006420+updated.zip Through clockworkmod.
Installed bootmenu.img
Updated to rbox prerooted Nov 21, 2014 - Added 51.1.4.1_514013920+fixed.zip. from clockworkmod
checked off enable unknown sources in adb enable screen.
sideloaded xposed and hdx module for playstore reboot
Installed 4 files for playstore along with the following apps:
screen oriention.apk
settings.apk
es file explorer.apk
marketsettings.apk
chrome.apk
firefox.apk
whoooo get some cold cuts, get some cold cuts. (add visual image of me doing Icky woods shuffle here)
I am now on a diet and the firetv is off my menu cause I will never want to do this again. NOT FOR THE FAINT OF HEART.
edit: i removed a comment to vpn app/provider. It seems I was mistaken about it's compatibility. I could have sworn I tested for new ip when vpn was running but now it no longer seems to be working as such. sorry for the inconvience.
rp201 said:
Overview, Not instructions please read and do not rely on this. written just for ****s and giggles.
I haven't done a firetv since October.
Using the firetv serial decoder from aftv.news, it said that it was a 51.1.01 but it was actually 51.1.1.0. I needed to use the same method from the firetv stick to bypass updating. (quickly pulling wan network plug immediately upon a wirelesss connect to the network upon receiving"connection successful" and then blocking updates with router and reconnecting wan cable and registering when registration screen comes up)
Enable adb from settins\system\dev menu.
sideloaded towelroot.apk superuser.apk and busybox.apk and run install from within busybox.
I then rooted device with towelroot. and then blocked OTA updates with "pm disable com.amazon.dcp" command. (not needed if router blocked but done just incase)
I needed to downgrade recovery to the first stock recovery so I could downgrade the Firmware to 51.1.0.2.
After downgrade 51.1.02 re-rooted with towelroot again, blocked ota updates with "pm disable com.amazon.dcp" command.
Unlocked bootloader with "aftv-unlock unlock" command, installed clockworkmod.
Updated to rbox prerooted Oct 30, 2014 - Added 51.1.4.0_514006420+updated.zip Through clockworkmod.
Installed bootmenu.img
Updated to rbox prerooted Nov 21, 2014 - Added 51.1.4.1_514013920+fixed.zip. from clockworkmod
checked off enable unknown sources in adb enable screen.
sideloaded xposed and hdx module for playstore reboot
Installed 4 files for playstore along with the following apps:
screen oriention.apk
settings.apk
es file explorer.apk
marketsettings.apk
chrome.apk
firefox.apk
I have used purevpn.com's android app which works fine with firetv. pm me if you need help for optimal settings. 49.95 per year for 5 devices and there are better deals than that on their site if you look. I saw them deals afterwards.
whoooo get some cold cuts, get some cold cuts. (add visual image of me doing Icky woods shuffle here)
I am now on a diet and the firetv is off my menu cause I will never want to do this again. NOT FOR THE FAINT OF HEART.
Click to expand...
Click to collapse
I believe you've got the series 3 which works with the removal of the Ethernet cord to register. I've done the same. I've gotten this as a rooted backup in case I need it in future.
Sorry, can you tell me which settings.apk you use and where to download ? Thanks
I just picked one up at best buy yesterday as well and it was also 51.1.1.0.
Can I ask what domains you blocked at the router?
The 3 I used did not seem to work anymore and the weird part was they have been in my access control policy on the router since the first time I rooted a fire tv back in early december.
The only way I could stop the update was to deny all internet access based on MAC Address in DD-wrt.
I blocked:
amzdigitaldownloads.edgesuite.net
softwareupdates.amazon.com
updates.amazon.com
and the firetv happily started downloading a update.
Luckily I was able to cancel it then quicky root and disable the update APK.
Thanks
snorkel01 said:
I just picked one up at best buy yesterday as well and it was also 51.1.1.0.
Can I ask what domains you blocked at the router?
The 3 I used did not seem to work anymore and the weird part was they have been in my access control policy on the router since the first time I rooted a fire tv back in early december.
The only way I could stop the update was to deny all internet access based on MAC Address in DD-wrt.
I blocked:
amzdigitaldownloads.edgesuite.net
softwareupdates.amazon.com
updates.amazon.com
and the firetv happily started downloading a update.
Luckily I was able to cancel it then quicky root and disable the update APK.
Thanks
Click to expand...
Click to collapse
As per AFTV, there are three
here are three domains to block:
amzdigitaldownloads.edgesuite.net
softwareupdates.amazon.com
updates.amazon.com
I will go home and check if you like but mine does not update. I have the netgear genie. Glad you stopped the update.
navigates said:
As per AFTV, there are three
here are three domains to block:
amzdigitaldownloads.edgesuite.net
softwareupdates.amazon.com
updates.amazon.com
I will go home and check if you like but mine does not update. I have the netgear genie. Glad you stopped the update.
Click to expand...
Click to collapse
Those are the 3 I have blocked as well. I wonder if somehow the update is using https.
The standard dd-wrt access restrictions don't block https.
In case anyone else is having trouble blocking the updates with dd-wrt see this:
http://forum.xda-developers.com/fir...es-blocked-t2920257/post56387280#post56387280
uses the dnsmasq option instead.
LOL
I agree with you...this is something I NEVER EVER want to repeat....took me about a week just to downgrade...and 3weeks to add the boot menu and update because of errors...Thanks to adb fire, Fire Tv Utility & RootJunky Fire TV Firmware Restore Tool....and yh dnsmasq is the best option to use in dd-wrt to block updates and the pulling of Ethernet cable works but it takes patience
lowbee said:
Sorry, can you tell me which settings.apk you use and where to download ? Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=57129257&postcount=20
Hey all,
Realistically speaking how long do you think they'll have a root for 5.4.0.0? I finally found of a method to block OTA updates by downloading noroot firewall and blocking any network access to OTA.
I hate to be the bearer of bad news, but there hasn't been any root progress since v5.3.1.1 - Root for 5.4.x may never happen.
It would still be a good idea to block Amazon updates (check for other threads), just in case we get a nice surprise.
Link block OTA
Eagl3007 said:
Hey all,
Realistically speaking how long do you think they'll have a root for 5.4.0.0? I finally found of a method to block OTA updates by downloading noroot firewall and blocking any network access to OTA.
Click to expand...
Click to collapse
Could you kindly link how you blocked connection to the OTA?
Thanks!
lemontrooper said:
Could you kindly link how you blocked connection to the OTA?
Thanks!
Click to expand...
Click to collapse
You can follow this method and 'uninstall' DeviceSoftwareOTA.apk and 'forced OTA' (I forget the exact name). You can use an app like App Inspector to list all installed apps, even system apps, to get the exact package names. Be advised, this MIGHT not work if you are on 5.4.0.1.
Does anyone know how to do this in ADB? Would I be able to just uninstall that way and also what is the package file name? I rather not use an app to do so.
Thanks,
I had updates blocked on my firestick (through launcher manager 1.1.6) , yet the stick downloaded and updated to 6.2.8.7 .
Could it have to do with the fact that I am always using VPN (nordvpn) , thus the launcher manager block does not work in this case ?
Does anyone know a solution on how to block future firestick updates while being connecting to a VPN ? (in my case nordvpn)
/EDIT : See solution below
Careful out there .
version 6.2.8.9 is being downloaded by my firestick as we speak . (it is a big update)
mea_pulpa said:
Careful out there .
version 6.2.8.9 is being downloaded by my firestick as we speak . (it is a big update)
Click to expand...
Click to collapse
Did you have the OTA files disabled?
mea_pulpa said:
I had updates blocked on my firestick (through launcher manager 1.1.6) , yet the stick downloaded and updated to 6.2.8.7 .
Could it have to do with the fact that I am always using VPN (nordvpn) , thus the launcher manager block does not work in this case ?
Does anyone know a solution on how to block future firestick updates while being connecting to a VPN ? (in my case nordvpn)
Click to expand...
Click to collapse
What version were you on before it did the update?
To be honest , I never actually paid attention to what version I was on since I had updates disabled through launcher manager 1.1.6 .
I felt I was safe .
I only started looking at what version I was on from the moment my Wolf launcher stopped working and I was suddenly stuck on the amazon bloated launcher .
So now the question is , how to stop the future amazon updates ?
As a start , does anyone know what IP's should be blocked ?
mea_pulpa said:
To be honest , I never actually paid attention to what version I was on since I had updates disabled through launcher manager 1.1.6 .
I felt I was safe .
I only started looking at what version I was on from the moment my Wolf launcher stopped working and I was suddenly stuck on the amazon bloated launcher .
So now the question is , how to stop the future amazon updates ?
As a start , does anyone know what IP's should be blocked ?
Click to expand...
Click to collapse
Approx what date did you disable the updates using 1.1.6?
I'm thinking maybe the update was already downloaded (but not installed) BEFORE you disabled updates, and for some strange reason that already downloaded update was activated.
mea_pulpa said:
To be honest , I never actually paid attention to what version I was on since I had updates disabled through launcher manager 1.1.6 .
I felt I was safe .
I only started looking at what version I was on from the moment my Wolf launcher stopped working and I was suddenly stuck on the amazon bloated launcher .
So now the question is , how to stop the future amazon updates ?
As a start , does anyone know what IP's should be blocked ?
Click to expand...
Click to collapse
I would use the adguard option to block updates if you set up a new firestick and skip the update via voiceover you have to clear updates downloaded via adb command which launch manager 1.16 has built in command is pm clear com.amazon.device.software.ota
mea_pulpa said:
I had updates blocked on my firestick (through launcher manager 1.1.6) , yet the stick downloaded and updated to 6.2.8.7 .
Could it have to do with the fact that I am always using VPN (nordvpn) , thus the launcher manager block does not work in this case ?
Does anyone know a solution on how to block future firestick updates while being connecting to a VPN ? (in my case nordvpn)
Click to expand...
Click to collapse
Does the pm disable-user com.amazon.device.software.ota still work? On my other post Amazon by now blocks any undoing to the system which involves blocking shell commands. Keep note that blocking updates is now or never and 6.2.8.9 is continuing to restrict the control you have over your device.
jhurtault said:
I would use the adguard option to block updates if you set up a new firestick and skip the update via voiceover you have to clear updates downloaded via adb command which launch manager 1.16 has built in command is pm clear com.amazon.device.software.ota
Click to expand...
Click to collapse
adguard is a vpn solution . Only 1 vpn can be used at a time . I am already using nordvpn so not possible for another vpn to run at the same time .
Skel40 said:
Does the pm disable-user com.amazon.device.software.ota still work? On my other post Amazon by now blocks any undoing to the system which involves blocking shell commands. Keep note that blocking updates is now or never and 6.2.8.9 is continuing to restrict the control you have over your device.
Click to expand...
Click to collapse
i currently use tduk update cleaner . I am running that program manually each time i notice the update has been downloaded .
also need to run it every time i unplug the firestick from its power or else it will update on next boot .
not an ideal situation .
every time i boot up the stick it auto downloads 6.2.8.9 immeditely .
mea_pulpa said:
i currently use tduk update cleaner . I am running that program manually each time i notice the update has been downloaded .
also need to run it every time i unplug the firestick from its power or else it will update on next boot .
not an ideal situation .
every time i boot up the stick it auto downloads 6.2.8.9 immeditely .
Click to expand...
Click to collapse
If you go into the "Block Updates" setting of Launch Manager 1.1.6, does it say that updates are currently Enabled or Disabled?
mea_pulpa said:
I had updates blocked on my firestick (through launcher manager 1.1.6) , yet the stick downloaded and updated to 6.2.8.7 .
Click to expand...
Click to collapse
Are you 100% sure that you "successfully" disabled updates?
I ask this for two reasons:
1) I caught myself thinking that when I clicked "disable updates" in LM 1.1.6, there was a slight pause and then I saw a GREEN checkmark after it completed it's operation. So I assumed that the green checkmark means that the block was "successful", but unfortunately it doesn't - a green checkmark means that updates are still "enabled". A Crossed Red Circle means that the updates have been disabled.
Another important thing to mention in case you didn't know, is that amazon recently pushed TWO updates: the first update prevented the ability to "disable" updates. The second update prevents users to select an alternative launcher.
So, since you said that you disabled the updates using launch manager 1.1.6, that version is a relatively recent version, so I am thinking that there might be the possibility that the first amazon update (that I mentioned aboce) was already installed on your stick, thereby preventing you from disabling updates. So, when you went to disable the updates in launch manager 1.1.6, you might have also assumed that the resulting green checkmark meant you successfully disabled them, but in fact you didn't because of that first update that was already installed BEFORE you tried to disable updates in LM, and that is why your stick eventually updated to 6.2.8.7. So basically, if you only recently did the "disable updates" in LM 1.1.6, then there is a chance you were too late.
2) The second reason for asking you these questions is that if in fact amazon has figured out a way to install updates even though the OTA files are disabled, this would be a major concern to many users. So, I just want to make sure that all the facts are accurate and that this really did happened exactly as you described.
JohnC said:
Are you 100% sure that you "successfully" disabled updates?
I ask this for two reasons:
1) I caught myself thinking that when I clicked "disable updates" in LM 1.1.6, there was a slight pause and then I saw a GREEN checkmark after it completed it's operation. So I assumed that the green checkmark means that the block was "successful", but unfortunately it doesn't - a green checkmark means that updates are still "enabled". A Crossed Red Circle means that the updates have been disabled.
Another important thing to mention in case you didn't know, is that amazon recently pushed TWO updates: the first update prevented the ability to "disable" updates. The second update prevents users to select an alternative launcher.
So, since you said that you disabled the updates using launch manager 1.1.6, that version is a relatively recent version, so I am thinking that there might be the possibility that the first amazon update (that I mentioned aboce) was already installed on your stick, thereby preventing you from disabling updates. So, when you went to disable the updates in launch manager 1.1.6, you might have also assumed that the resulting green checkmark meant you successfully disabled them, but in fact you didn't because of that first update that was already installed BEFORE you tried to disable updates in LM, and that is why your stick eventually updated to 6.2.8.7. So basically, if you only recently did the "disable updates" in LM 1.1.6, then there is a chance you were too late.
2) The second reason for asking you these questions is that if in fact amazon has figured out a way to install updates even though the OTA files are disabled, this would be a major concern to many users. So, I just want to make sure that all the facts are accurate and that this really did happened exactly as you described.
Click to expand...
Click to collapse
I see where you are coming from and yes indeed the interface to block updates is confusing .
I updated to 1.1.6 right after its release . Definately activated the right blocker since I was checking both options in detail to see what exactly changed (i immediately noticed the interface was confusing) .
Right now the LM unblocker can not be activated because I am running 6.2.8.7 which disables the option to stop updates entirely .
We will never know why or how it downloaded the update on my device since I did not keep a logbook about what and when things happened .
What we do know is : I am on 6.2.8.7 now , it is downloading the 6.2.8.9 update constantly in order to install it .
I already tried blocking over 30 ip addresses that I found in netstat , but it seems that none of them were blocking the update from downloading . If anyone has a working set of ip addresses/ranges to block , I will be happy to try it out .
Or another way to block it from downloading .
(not by installing a second vpn solution as that is simply not possible , and without my vpn i can not watch my content anyway . So I can as well leave it unplugged and not watch anything at that point )
I remember seeing somewhere a list of about 3 domain names to block to prevent firestick updates, but I don't remember where.
Lets see if any other user reports that they had the OTA files disabled, but it updated anyway.
JohnC said:
I remember seeing somewhere a list of about 3 domain names to block to prevent firestick updates, but I don't remember where.
Lets see if any other user reports that they had the OTA files disabled, but it updated anyway.
Click to expand...
Click to collapse
Yes many more have already reported they blocked updates yet they got updated anyway .
Anyway , I found a list with 5 dns names and created a block that works for me , while still being able to use my own vpn .
This is how I did it :
Open norvpn on the firestick . go to trusted apps and add "Downloads" (the one with the green arrow pointing downwards) to the list .
Then in your network router interface , block the following 5 url's in the Firewall - URL filter menu (I use an asus router running merlinwrt firmware , so it might and probably will be different from your setup) .
URLs :
d1s31zyz7dcc2d.cloudfront.net
amzdigital-a.akamaihd.net
amzdigitaldownloads.edgesuite.net
softwareupdates.amazon.com
updates.amazon.com
To be redundant I also added the 5 dns names in my dnsmasq .
(create a file called dnsmasq.conf.add in /jffs/configs/
Then put following lines in it :
address=/d1s31zyz7dcc2d.cloudfront.net/127.0.0.1
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
save the file and at the command line type "service restart_dnsmasq" or simply restart your router .)
As mentioned , implementing both is just to be redundant . If you implement only 1 of the 2 (either url filter or dnsmasq) it also works .
Now what happens is , the firestick will consult the router always to download anything on the firestick .
With my vpn activated , or without . Downloading an app from amazon store works , downloading system updates will not . Downloading app updates , I have not tried this yet .
Now the firestick will detect that there is a new OS version to be downloaded , but once it wants to start downloading it will face the block and it hangs and never is able to actually start downloading .
So it shows downloading infinitely in the about - download updates menu .
Before implementing this , I would recommend you install TDUK update wiper on your firestick .
This is how I tested all my scenarios , every time deleting the update with the TDUK update wiper app when it would fail to block the download .
I hope this helps someone .
Currently my 6.2.8.7 is booting into wolf launcher , and also pressing the home button goes back into wolf launcher .
All this while system updates to 6.2.8.9 or above are not coming through . (at least for now )
REMARK :
The block will stay working for as long as the 5 url's are hard coded in the fireOS itself . Which I do not know if they are .
In case they are pulled from the internet somewhere , or updated when the app Downloads updates ... amazon might force change the urls some day . So be aware .
mea_pulpa said:
Yes many more have already reported they blocked updates yet they got updated anyway .
Click to expand...
Click to collapse
I am a member of a couple different forums that discuss fire sticks, and I have not seen anyone else post that their device updated even with the OTA files disabled.
So, not that I am doubting your claim, but I would like to know about these other firestick groups so that I can join them to keep better informed about all things related to firestick.
What are these other groups?
JohnC said:
I am a member of a couple different forums that discuss fire sticks, and I have not seen anyone else post that their device updated even with the OTA files disabled.
So, not that I am doubting your claim, but I would like to know about these other firestick groups so that I can join them to keep better informed about all things related to firestick.
What are these other groups?
Click to expand...
Click to collapse
No special groups . Just here on the xda forum people reporting it happened to them too in different threads .
mea_pulpa said:
No special groups . Just here on the xda forum people reporting it happened to them too in different threads .
Click to expand...
Click to collapse
The amazon updates that disables updates and custom launchers only came out about 2 months ago and I have been subscribed to see any new threads *or* new posts in this "Fire TV General" section.
I've seen users report that Wolf stopped working, and then they realized about the new wolf-killing update.
I've seen other users who heard about the new wolf-killing update and then tried to disable updates, only to learn it was too late.
For example, the below website, which has a huge following, has many posted comments on the topic of disabling automatic updates. But there is absolutely nothing posted after 2/20/22, which I would think that if other users had updates installed after disabling updates, there would have been a few posts about that serious problem, but there isn't:
Block Amazon Firestick / Fire TV Automatic Updates
The following tutorial will show you How to Block Amazon Firestick & Fire TV automatic updates. Amazon is constantly pushing out updates that usually
troypoint.com
However, you are the first and only one (that I have seen) who reported that you successfully disabled updates and for some reason a recent update was still installed.
So, can you point me to some of these "many more have already reported..." so that I can ask those users some questions (like I did above to you) just to make sure they also were positive that they didn't get confused with the green checkmark in LM, so I can see if there are any specific conditions that is causing this to happen to you and these other users (but not to everyone), and hopefully find out a way to stop it.
So, it would be greatly appreciated if you could provide a few links to the other users who you saw reported this issue.
JohnC said:
The amazon updates that disables updates and custom launchers only came out about 2 months ago and I have been subscribed to see any new threads *or* new posts in this "Fire TV General" section.
I've seen users report that Wolf stopped working, and then they realized about the new wolf-killing update.
I've seen other users who heard about the new wolf-killing update and then tried to disable updates, only to learn it was too late.
For example, the below website, which has a huge following, has many posted comments on the topic of disabling automatic updates. But there is absolutely nothing posted after 2/20/22, which I would think that if other users had updates installed after disabling updates, there would have been a few posts about that serious problem, but there isn't:
Block Amazon Firestick / Fire TV Automatic Updates
The following tutorial will show you How to Block Amazon Firestick & Fire TV automatic updates. Amazon is constantly pushing out updates that usually
troypoint.com
However, you are the first and only one (that I have seen) who reported that you successfully disabled updates and for some reason a recent update was still installed.
So, can you point me to some of these "many more have already reported..." so that I can ask those users some questions (like I did above to you) just to make sure they also were positive that they didn't get confused with the green checkmark in LM, so I can see if there are any specific conditions that is causing this to happen to you and these other users (but not to everyone), and hopefully find out a way to stop it.
So, it would be greatly appreciated if you could provide a few links to the other users who you saw reported this issue.
Click to expand...
Click to collapse
Hey JohnC I see you are on some kind of mission .
I think most of these people will have no valuable information for you . As people and firesticks don't keep logbooks . They don't recall/remember exactly .
So remember it is your mission , not mine .
A recent post to get you started : https://forum.xda-developers.com/t/...fire-tv-stick-4k-mantis.3978459/post-86724123
I'm not personally going to re-read all threads I have read on xda , in search of the others . So I will leave that up to you my friend .
mea_pulpa said:
Hey JohnC I see you are on some kind of mission .
I think most of these people will have no valuable information for you . As people and firesticks don't keep logbooks . They don't recall/remember exactly .
So remember it is your mission , not mine .
A recent post to get you started : https://forum.xda-developers.com/t/...fire-tv-stick-4k-mantis.3978459/post-86724123
I'm not personally going to re-read all threads I have read on xda , in search of the others . So I will leave that up to you my friend .
Click to expand...
Click to collapse
Thanks for the info.