I have a Cricket branded Motorola Moto G 5G Stylus, and I'm trying to disable the system updates. I've already disabled system updates in developer options, but it still forces me to update - I can delay the update for a day, and then it forces the update with absolutely no way to stop it. I use this phone for reliability testing, so forced restarts for system updates are unacceptable. Not to mention the updates themselves often break functionality.
I tried using ADB to directly disable the system update apps. There are two, both labeled "Cricket Software Update" with package names com.motorola.android.fota and com.motorola.ccc.ota. I disabled com.motorola.android.fota, but when I try to disable, uninstall, or clear com.motorola.ccc.ota, ADB gives an error "Cannot disable a protected package" or "Failure: package is protected."
I don't need them and don't want them, so how do I disable system updates on my Motorola Moto G Stylus 5G? Or, how can I disable protected system packages/apps with ADB?
Read my guide on how to debloat. You will have to root if it is a 2022 Stylus. Method should work on the 2021 version, but use at your own risk.
Related
It seems Android pay is blocking custom ROMS and root. Hiding the SU binary and pushing a stock build.prop dont seem to alleviate the situation. Does anyone know of a workaround that allows one to keep his root and/or ROM?
I saw this pic on reddit when a user asked google http://imgur.com/FVhQPTz
It uses the SafetyNet API.
Tried setting it up on a stock / signed ROM, went through fine. Tried to backup the app+data and restore it on a custom ROM. Saw my complete account screen for a split second before the 'add new card' window came back and wouldn't go away.
This would not surprise me. Don't be surprised if you can't get around it. Root is too much of a security risk for something like that
I'm not very good with hacks and workarounds but I tried this and it didn't work.
http://androiding.how/android-pay-with-root/#comment-779
Note 2/i317 AT&T/unlocked sim/CyanideL ROM v19/Shift Kernel 5.7
SafetyNet API - fix Android Pay issue with Root / Custom ROMS / xposed
New Last Night...
http://repo.xposed.info/module/com.pyler.nodevicecheck
No luck on a Moto X (2014)...anyone else having any luck?
Nope
No luck on Safteynet API, root cloak, disabling root aps, etc. LG G3 modified stock rom and kernel.
in SuperSU i just disabled SU, NOT unroot, and then it allowed me to add card. im stock rooted s5
Same here
I'm reading that "custom ROMs are missing some proprietary files that Android Pay relies upon"
http://android.wonderhowto.com/how-to/get-android-pay-working-rooted-device-0164604/
It may allow you to add the card, but when you re-enable SU, Pay will not go through when trying to use it.
Downgrade to an 8.x version of Google Wallet. All versions in the 9.x range were preprogrammed to disable themselves when Android Pay came out. I switched back to 8.0-R190-v25 that's preinstalled on my Nexus 5 and disabled automatic updates for Android Pay on the play store.
If you have something like Titanium Backup (which most would if they're rooted), you can also detach Wallet form the Market, meaning it shouldn't know to update it.
Okay, let me start off by saying I thought I could not give up root for Android Pay. I tried workarounds, e.g., temporarily disabling supersu, which let me add cards but wouldn't actually process payment at store.
I have a Nexus 5 on Sprint, with official 6.0 factory imgs installed. I have TWRP recovery and an (obviously) unlocked bootloader. While rooted, I flashed ElementalX kernel (allowing for double-tap to wake, swipe to sleep, and under-volting--3 features I can't live without), modified build.prop to allow multi-window mode, and ran ADB commands to enable tethering (courtesy of Reddit instructions).
I then completely uninstalled SuperSU and BusyBox (no easy task--had to delete system apks and reboot numerous times). I also had to delete su and busybox entries from system/xbin for unrooting. After a reboot, I successfully installed Android Pay, added credit card, and have successfully used it at several retail outlets. More importantly, my kernel DT2W/swipe to sleep/undervolting options still work, as does tethering and multi-window. Apparently AP doesn't check for build.prop or boot mods, nor does it check for bootloader state or stock recovery. I do miss quickboot options I had with root however.
If I absolutely need something that requires root, e.g., Titanium Backup restore, etc, I can just boot into TWRP recovery through old-school holding down power/ volume button technique (hence why I miss quickboot features), flash SU and BusyBox zips I have on internal SD, reboot, do my business, and then unroot like I did above. FWIW unrooting is MUCH more difficult than rooting, but still very doable once you figure out all the steps.
Can you post the steps for cleanup? I have been trying it myself and have had no luck with getting A-Pay to actually work correctly.
How do you stop updates from automatically applying?
Dankees said:
How do you stop updates from automatically applying?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74672462&postcount=5
This worked for me, but that was in the way back of 5.6.0, good luck!
Use a firewall, and block internet access to the two OTA apps. After go to Settings 》 Apps and look for the two OTA apps. Clear cache and data.
@Dankees
TechNash said:
Use a firewall, and block internet access to the two OTA apps. After go to Settings 》 Apps and look for the two OTA apps. Clear cache and data.
@Dankees
Click to expand...
Click to collapse
Huh? How do I use a firewall?
And, which two OTA apps?
Dankees said:
Huh? How do I use a firewall?
And, which two OTA apps?
Click to expand...
Click to collapse
Try NoRoot Data Firewall from the Play Store.
There are two apps that have "OTA" in the name. I forget the full name right now.
Dankees said:
....
And, which two OTA apps?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74672462&postcount=5
Hi all. I've successfully rooted my Fire 10 (2017) using retyre's excellent offline rooting guide. I never (and still have not) connected to wifi and sideloaded 5.6.2.0 from what was previously at 5.5.0.0
After root, I've installed Google Play Store with forum.xda-developers.com/showpost.php?p=77125897&postcount=80
Installed Xposed Framework Installer APK, but have yet to install the actual Xposed SDK because that requires an internet connection to retrieve the SDK. And I haven't downloaded a root file explorer yet, either.
Anyways, I've read and read before doing all these things, but there's one more thing to figure out before I finally connect to wifi.
What's the correct way to prevent Amazon from pushing a ROM OTA? I've seen 2 different implementations posted around the forums.
THIS:
TechNash said:
Use a firewall, and block internet access to the two OTA apps. After go to Settings 》 Apps and look for the two OTA apps. Clear cache and data.
Click to expand...
Click to collapse
OR
THIS:
bibikalka said:
Code:
adb shell
su
mount -w -o remount /system
mv /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk_
ls -l /system/priv-app/DeviceSoftwareOTA/
ignore any errors you may get while doing this; after 'su', you should see root (#) prompt here
Click to expand...
Click to collapse
bibikalka follows this up by saying this
bibikalka said:
How to install Xposed & Flashfire for easy backups and ROM updates
How to enable Amazon packages (apk) updates but prevent the ROM updates (keeping root & rootable rom).
1) Edit /system/build.prop and change ro.build.version.number to have "9" as the first value instead of "5", as recommended in this link
2) Reboot
3) Enable OTA by ensuring that /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk is renamed back to apk from apk_
4) Reboot
At this point the Fire will download a lot of apk packages, and will update Amazon system components (keeping FireOS version the same).
Click to expand...
Click to collapse
-Someone help explain why one is better than the other?
-Will setting up a firewall prevent Amazon's apps as well as system firmware from being updated?
-Is the firewall implementation equally as effective as changing the DeviceSoftwareOTA.apk to DeviceSoftwareOTA.apk_?
-Is changing the build number in /system/build.prop to 987654321 all we actually need to do to protect us from firmware updates?
I did my best to compile all my relevant questions in one lengthy post hoping that it will help someone else in the same position as I am somewhere down the line.
Jned said:
https://forum.xda-developers.com/showpost.php?p=74672462&postcount=5
This worked for me, but that was in the way back of 5.6.0, good luck!
Click to expand...
Click to collapse
This method worked for me after rooting using the offline root guide. When I go into System Updates and click check, it just says "Check for updates failed." It does require root, so make sure to use the "su" command before the others or it will give you an error. I am on 5.6.0.1 by the way.
Hylex said:
Hi all. I've successfully rooted my Fire 10 (2017) using retyre's excellent offline rooting guide. I never (and still have not) connected to wifi and sideloaded 5.6.2.0 from what was previously at 5.5.0.0
After root, I've installed Google Play Store with forum.xda-developers.com/showpost.php?p=77125897&postcount=80
Installed Xposed Framework Installer APK, but have yet to install the actual Xposed SDK because that requires an internet connection to retrieve the SDK. And I haven't downloaded a root file explorer yet, either.
Anyways, I've read and read before doing all these things, but there's one more thing to figure out before I finally connect to wifi.
What's the correct way to prevent Amazon from pushing a ROM OTA? I've seen 2 different implementations posted around the forums.
THIS:
OR
THIS:
bibikalka follows this up by saying this
-Someone help explain why one is better than the other?
-Will setting up a firewall prevent Amazon's apps as well as system firmware from being updated?
-Is the firewall implementation equally as effective as changing the DeviceSoftwareOTA.apk to DeviceSoftwareOTA.apk_?
-Is changing the build number in /system/build.prop to 987654321 all we actually need to do to protect us from firmware updates?
I did my best to compile all my relevant questions in one lengthy post hoping that it will help someone else in the same position as I am somewhere down the line.
Click to expand...
Click to collapse
The methods can be ranked in terms of update prevention:
1) DeviceSoftwareOTA.apk_ blocks anything an everything, forever and ever
2) build.prop version blocks FireOS ROM updates (no threat to root), but does not block individual Amazon apk updates for various packages, so something like Amazon store may still update
3) firewall method is intermittent, and often people complain that it would still update even with the firewall blocking - this one is absolutely not recommended
I will do the build.prop edit then. Thank you!
Hylex said:
Hi all. I've successfully rooted my Fire 10 (2017) using retyre's excellent offline rooting guide. I never (and still have not) connected to wifi and sideloaded 5.6.2.0 from what was previously at 5.5.0.0
After root, I've installed Google Play Store with forum.xda-developers.com/showpost.php?p=77125897&postcount=80
Installed Xposed Framework Installer APK, but have yet to install the actual Xposed SDK because that requires an internet connection to retrieve the SDK. And I haven't downloaded a root file explorer yet, either.
Anyways, I've read and read before doing all these things, but there's one more thing to figure out before I finally connect to wifi.
What's the correct way to prevent Amazon from pushing a ROM OTA? I've seen 2 different implementations posted around the forums.
THIS:
OR
THIS:
bibikalka follows this up by saying this
-Someone help explain why one is better than the other?
-Will setting up a firewall prevent Amazon's apps as well as system firmware from being updated?
-Is the firewall implementation equally as effective as changing the DeviceSoftwareOTA.apk to DeviceSoftwareOTA.apk_?
-Is changing the build number in /system/build.prop to 987654321 all we actually need to do to protect us from firmware updates?
I did my best to compile all my relevant questions in one lengthy post hoping that it will help someone else in the same position as I am somewhere down the line.
Click to expand...
Click to collapse
I said Firewall because he didn't have root. A non-root firewall works, but isn't the most reliable.
Since you have root, go ahead and delete those two apps altogether. Use something like Titanium Backup, and then uninstall the OTA Apps. Make a backup in case you ever want automatic updates again.
Hey everyone,
I'm rooted, so obviously the OTA security update fails every time for me. Since I did a hard restart on my phone, the update tries to be applied non stop, hogging up CPU usage and slowing the phone down. It says it fails and immediately tries to apply it again, in an endless loop.
I haven't found a way to disable it. Any suggestions? I tried to delete Motorola Update Services through titanium backup but it keeps coming back after a restart.
Any suggestions? I don't really want to go through the hassle of updating for a security patch, re rooting, and setting up my highly customized device again.
Thanks in advance!
Try the following
Enable usb debugging
Connect phone to PC & run the following adb command substituting package name with the package name of the app you want to disable E.g com.xyz.myapp
Code:
adb shell pm uninstall --user 0 packagename
If you get an error about this app can't be uninstalled try
Code:
adb shell pm disable-user --user 0 packagename
I just wanted to update anyone in case they are looking at this thread.
The first command to remove it did not work. The second command to disable it DOES work, and survives a reboot. The package name is "com.motorola.ccc.ota"
I have Motorola Update Services frozen via Titanium seems to have killed that update pop up on 4 Motos i have. oh and disable updates in Dev mode too.
Bookmarked for later.
I'm going to bump this thread because the command is not working on Android 10. Any solutions? TB also just crashes for me.
adb simply returns "package non disable" or something along those lines. Meanwhile I keep getting that extremely annoying popup. Honestly, may it's worth switching to lineage. At least there I can be rooted and also get updates.
WaterMan! said:
I just wanted to update anyone in case they are looking at this thread.
The first command to remove it did not work. The second command to disable it DOES work, and survives a reboot. The package name is "com.motorola.ccc.ota"
Click to expand...
Click to collapse
i second this. the second command works in my experience too.
Just an update for anyone that finds this...
On another forum, I came across this
adb shell pm disable-user --user 0 com.motorola.ccc.ota
It worked for me on a Moto G6
Hi
It doesn't work on my device. Though I have the Moto G Power 2022 (Tonga), running A11 stock WITHOUT su (root); neither the pm uninstall or pm disable commands perform their function. Rather, it tells me the package is "non-disable" and remains installed and unable to disable. It's the motorola ota package I'm trying to freeze so it can stop with the SPAM POPUPS (no shame calling it what it is) with absolutely no option to hide or suppress them altogether. And No, going to Smart Updates and turning it off there or on Developer Options have no bearing. If anything it's become relentlessly frequent, to the point I would refer to it as spamming.
There must be something I'm missing or doing wrong. I've always been able to disable packages this way and never really encountered this problem before. Are there any other pm commands that may do the trick? Could my ADB utilities be outdated and could that be what's causing it to fail. Or have we simply reached a dead-end with software and Android 11 no longer providing a method of removing system packages WITHOUT root or unlocking bootloader.
I still have not found a way to disable this package and the popups are driving me insane!
Is there really no working method for this??
Just installed the new TB-J0606F_S320208_220719_ROW that was pushed to my P11 today. Now I've got another pre-installed app from Lenovo called “Tablet Center”. Of course, it can not be disabled and permissions can not be revoked.
Has anyone attempted to remove it via ADB as of yet?
On a p11 plus I have disabled it
ADB AppControl
great program
The new firmware seems to be causing issues - on my tablet at least. Won't wake from sleep and hard resets into factory bootloader all by itself.
I get pestered with security patch update notifications on my XT-2215-4 non stop. I am rooted, the service I need to disable (com.motorola.ccc.ota) is set as non-disable so I can't disable it via ADB.
Anyone have any magisk/lsposed modules that can help stop these annoying pop ups? Anything else I can disable?
This should work for any moto phone afaik. Disables the app under system, system_ext, and product partitions.
fddm said:
This should work for any moto phone afaik. Disables the app under system, system_ext, and product partitions.
Click to expand...
Click to collapse
Thank you. I will try this and post an update.
edit: 5 days later, not a single notification since I've installed your magisk module. Thank you so much!