Amazon Blocks Users From Blocking Updates

Search This thread

Skel40

Senior Member
Dec 27, 2019
362
195
Moto G 5G
Hello XDA users and Fire TV users, Amazon now blocked the adb shell pm disable-user command permanently. You can no longer block update packages 7.2.7.3/6.2.8.7 and higher. If you just updated your device without applying the system components updates, it should still work so avoid those incremental updates if you can while it lasts.

I'm currently running a Fire TV Stick Lite [TWRP Unlocked] (sheldon) on firmware 7.2.4.2 (PS7242/3515)

The pm disable-user is as follows from adb prompt:
pm disable-user com.amazon.device.software.ota
Security exception: cannot disable a protected package: com.amazon.device.software.ota
 

Sus_i

Senior Member
Apr 9, 2013
1,861
816
The pm disable-user is as follows from adb prompt:
pm disable-user com.amazon.device.software.ota
Security exception: cannot disable a protected package: com.amazon.device.software.ota
The command for unlocked/rooted devices is
pm disable com.amazon.device.software.ota
I guess you know that already, isn't it?

And this would be the command for the locked devices... which is blocked on the latest?
pm disable-user --user 0 com.amazon.device.software.ota
 

Skel40

Senior Member
Dec 27, 2019
362
195
Moto G 5G
The command for unlocked/rooted devices is
pm disable com.amazon.device.software.ota
I guess you know that already, isn't it?

And this would be the command for the locked devices... which is blocked on the latest?
pm disable-user --user 0 com.amazon.device.software.ota
Yes which still works with root installed. The command is blocked on latest with system components installed for locked devices. It won't work. Maybe eventually it'll be rolled out as a system update so I wouldn't update if you use the custom launchers and want updates blocked. If they can permanently block launchers they can block update blocker tools from working anymore and it'll continue with newer methods. If anyone has a Fire TV Stick Lite and wants to unlock it. Now would be your best bet before it's patched.
 
  • Like
Reactions: Sus_i

hafren

Member
Apr 18, 2018
31
9
I've enabled adb on rooted FTV2 sloane and launched adb shell (as administrator) but when I run pm disable com.amazon.device.software.ota I get an Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=9891, uid=2000, package uid=32011

I was able to run pm clear com.amazon.device.software.ota with success

How do I overcome the permissions denial
 

Rortiz2

Senior Member
I've enabled adb on rooted FTV2 sloane and launched adb shell (as administrator) but when I run pm disable com.amazon.device.software.ota I get an Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=9891, uid=2000, package uid=32011

I was able to run pm clear com.amazon.device.software.ota with success

How do I overcome the permissions denial
You need to spawn a root shell before running the pm disable cmd. In order to do so, run 'su'.
 
  • Like
Reactions: hafren

hafren

Member
Apr 18, 2018
31
9
Ok so I changed my usb a-a cable I retried su - this time I do get a flashing cursor so entered the commands but still received no feedback from device (its a ftv2 sloane rooted twrp via amonet)

Code:
C:\adb>adb devices -l
List of devices attached
G070GV146247023P       device product:full_sloane model:AFTS device:sloane transport_id:1


C:\adb>adb shell
[email protected]:/ $ su
pm disable com.amazon.device.software.ota
pm disable com.amazon.device.software.ota.override
pm disable com.amazon.tv.forcedotaupdater
pm disable com.amazon.tv.forcedotaupdater.v2
exit
exit
pm clear com.amazon.device.software.ota
 

hafren

Member
Apr 18, 2018
31
9
OK solved it - magsik had not fully loaded to allow root selection. Now working- Really appreciate learning the '$' turning to a '#' indicates you now have root privileges
 
  • Like
Reactions: Finnzz

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    The pm disable-user is as follows from adb prompt:
    pm disable-user com.amazon.device.software.ota
    Security exception: cannot disable a protected package: com.amazon.device.software.ota
    The command for unlocked/rooted devices is
    pm disable com.amazon.device.software.ota
    I guess you know that already, isn't it?

    And this would be the command for the locked devices... which is blocked on the latest?
    pm disable-user --user 0 com.amazon.device.software.ota
    1
    The command for unlocked/rooted devices is
    pm disable com.amazon.device.software.ota
    I guess you know that already, isn't it?

    And this would be the command for the locked devices... which is blocked on the latest?
    pm disable-user --user 0 com.amazon.device.software.ota
    Yes which still works with root installed. The command is blocked on latest with system components installed for locked devices. It won't work. Maybe eventually it'll be rolled out as a system update so I wouldn't update if you use the custom launchers and want updates blocked. If they can permanently block launchers they can block update blocker tools from working anymore and it'll continue with newer methods. If anyone has a Fire TV Stick Lite and wants to unlock it. Now would be your best bet before it's patched.
    1
    I've enabled adb on rooted FTV2 sloane and launched adb shell (as administrator) but when I run pm disable com.amazon.device.software.ota I get an Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=9891, uid=2000, package uid=32011

    I was able to run pm clear com.amazon.device.software.ota with success

    How do I overcome the permissions denial
    You need to spawn a root shell before running the pm disable cmd. In order to do so, run 'su'.
    1
    [email protected]:/ $ su
    Should result in
    [email protected]:/ #

    The '$' turning to a '#' indicates you now have root privileges. It looks like your device is hanging on the su command, with no confirmation the request was granted.
    1
    OK solved it - magsik had not fully loaded to allow root selection. Now working- Really appreciate learning the '$' turning to a '#' indicates you now have root privileges