I have a rooted stock ROM Pure and I want to avoid the 5.1 update for a couple of reasons.
Does anyone know how to disable the update process on these devices?
TIA
FoneWatcher said:
I have a rooted stock ROM Pure and I want to avoid the 5.1 update for a couple of reasons.
Does anyone know how to disable the update process on these devices?
TIA
Click to expand...
Click to collapse
Disable MotorolaOTA in the system apps in settings. If you're rooted, you can freeze it in the /system folder using Titanium or whatever else you use. Safest thing to do is to rename it with a .bak at the end, then when you're ready to update you just remove it and reboot.
sivarticus85 said:
Disable MotorolaOTA in the system apps in settings. If you're rooted, you can freeze it in the /system folder using Titanium or whatever else you use. Safest thing to do is to rename it with a .bak at the end, then when you're ready to update you just remove it and reboot.
Click to expand...
Click to collapse
Thanks for the reply. I froze it with Ti Backup, but I'm still able to check for updates manually and it reports normally.
Shouldn't that function be disabled if the OTA apparatus is truly disabled?
I do see in firewall a process called 'Device Management that I thought I could block MotorolaOTA from communicating, but there are other functions bundled, so I don;t want to do that.
Ideas, anyone?
FoneWatcher said:
Thanks for the reply. I froze it with Ti Backup, but I'm still able to check for updates manually and it reports normally.
Shouldn't that function be disabled if the OTA apparatus is truly disabled?
I do see in firewall a process called 'Device Management that I thought I could block MotorolaOTA from communicating, but there are other functions bundled, so I don;t want to do that.
Ideas, anyone?
Click to expand...
Click to collapse
Motorola will still be able to be communicated to, but the OTA function will be disabled, eg. no OTA will be detected. It is my understanding that blocking MororolaOTA just keeps the notification from appearing and prevents OTA downloads.
sivarticus85 said:
Motorola will still be able to be communicated to, but the OTA function will be disabled, eg. no OTA will be detected. It is my understanding that blocking MororolaOTA just keeps the notification from appearing and prevents OTA downloads.
Click to expand...
Click to collapse
Thanks again - that makes sense. I'll see the rollout on my stock Pure (if I still have it and decide not to sell it) and be able to compare in real-time if it does the trick.
Related
Hello, everyone. Long time reader, first time poster.
I just finished rooting my new Developer's Edition GSM unlocked Moto X. As I started to freeze the usual apps that are necessary in order to stop OTA notices and lessen the likelihood of sending my device into a bootloop by mistake, I noticed that the apps that I had on my Verizon Droid Maxx aren't here. I saw some threads that stated that I needed to freeze update.apk, MotorolaOTA, FOTA, and rename otacerts.zip to otacerts.zip.bak.
Of all of those steps, I've only been able to do two of them: freezing MotorolaOTA and renaming otacerts.zip.
Where can I find the other two apps to freeze? Is it even necessary if I've already frozen MotorolaOTA and renamed otacerts? When I had my Droid Maxx, I was unable to click on System Updates in About Phone without the app crashing. Here, after freezing and renaming these two apps, I can still check for updates, which leaves me a little worried.
Thank you for your help.
3C_OTA.APK is one you want to rename.. It exists in /system/apps or /system/priv-app (I forget which).
KidJoe said:
3C_OTA.APK is one you want to rename.. It exists in /system/apps or /system/priv-app (I forget which).
Click to expand...
Click to collapse
Great, I went ahead and renamed that one 3C_OTA.APK.BAK. I can still check for updates in System Updates, which is something I couldn't do on my Droid Maxx after freezing all the OTA apps.
Is that normal for this phone? Are there any other apps / files I need to take care of?
Thanks for the reply!
Any other ideas? The fact that I can still check for an update makes me nervous. I'm just trying to confirm that this was all I needed to do.
defcoalknot said:
Any other ideas? The fact that I can still check for an update makes me nervous. I'm just trying to confirm that this was all I needed to do.
Click to expand...
Click to collapse
MotorolaOTA 1.0 is what I froze on my retail X (while it was downloading an update) and as soon as it was frozen, the download icon in the status bar disappeared :good: I'm not sure where the apk is located to move/rename since I used tibu to freeze it.
defcoalknot said:
Any other ideas? The fact that I can still check for an update makes me nervous. I'm just trying to confirm that this was all I needed to do.
Click to expand...
Click to collapse
Renaming 3C_OTA.APK has worked for me and others who wanted to block OTA notifications..
here are links to just a few times before that it has been suggested...
http://forum.xda-developers.com/showpost.php?p=51038059&postcount=5
http://forum.xda-developers.com/moto-x/moto-x-qa/how-to-upgrade-to-4-4-2-t2660439
http://forum.xda-developers.com/showpost.php?p=50960313&postcount=5
I'm sure if you searched, you could find more instances of it being suggested, and successful.
bb1981 said:
MotorolaOTA 1.0 is what I froze on my retail X (while it was downloading an update) and as soon as it was frozen, the download icon in the status bar disappeared :good: I'm not sure where the apk is located to move/rename since I used tibu to freeze it.
Click to expand...
Click to collapse
That's all I froze on my phone too.
Device manager is downloading some att software update. Im assuming it will mess up my phones root and xposed settings. Is there a way to stop it by disabling the function in Titanium Backup? Or should i let it happen? Ive already disabled the push security updates (security policy spd_v2_1402) btw.
psm510 said:
Device manager is downloading some att software update. Im assuming it will mess up my phones root and xposed settings. Is there a way to stop it by disabling the function in Titanium Backup? Or should i let it happen? Ive already disabled the push security updates (security policy spd_v2_1402) btw.
Click to expand...
Click to collapse
Use tibu to freeze these system apps: AT&T update; Samsung Push Services; localfota and security policies.
That should stop the updates. If you update it breaks root.
Sent from my SAMSUNG-SM-G870A using Tapatalk
Thanks! I had to keep my phone on airplane mode until you posted the solution!
I've decided to get my phone ready to accept the (hopefully soon) OTA update for my 2013 X. Right now it's on 4.4.4, bootloader unlocked (thanks Sunshine!), and rooted. I had it rooted to take advantage of Xposed and Secure Settings with Tasker integration. I also used TitaniumBackup to freeze the Verizon and some Moto apps I never used.
Currently, I have uninstalled every Xposed module I downloaded, then unistalled Xposed itself and finally the Xposed installer app. After that I went into Titanium and defrosted everything that was frozen. Now I have a fair amount of updates coming in from the Play store for all those apps that were frozen. Should I go ahead and update them?
From what I've read, there's been talk on whether or not I have to un-root my phone. I thought I just had to use the toolkit to flash back the stock recovery? That should be the only thing left to do? What about some apps that are device administrators like Cerberus? Do I need to remove them from that list?
Thank you for any advice. I plan on flashing stock recovery when I get home this evening.
Generally speaking an OTA will probably fail if apps it expects to be present are missing or modified in the /system partition. I don't know if having additional items (like Cerberus) will halt the OTA or not. Custom recovery may also interfere with the OTA.
It sounds like you already did all the work, but I personally wouldn't have done any of that until the OTA was actually rolling out. I know they said it will be soon, but it could still be weeks away. I wouldn't give up my phone that was setup how I like it, but that's just my preference.
When the OTA drops, if you try and install it will do all of the validation before it installs anything. If the validation fails, it will tell you it has an error and it won't work. Then you'll have to fix whatever was modified, or reflash the stock firmware to be compatible with the OTA.
I don't believe updating the apps is necessary. I don't even think they need to be active (you can use the Disable function in the App Info screen to hide them), they just need to be present in your /system folder with the correct signature, is how I understand it.
2 days ago i rooted my G800F with CF-auto-root through ODIN. (Used the latest CF-auto-root from here , with ODIN v3.10.6)
But after that my device is too laggy!
Much slower as it had 512 RAM. Root success was confirmed with Root Checker
SuperSU was also installed but sometimes i get a message that SU binary isn't installed.
I 've tried with "ROM toolbox" and "System App Remover" to unistall some system apps but i got the message "Failed to Unistall xxxxxxx app". But if i entered again "ROM toolbox" i found out that the xxxxxx app wasn't there. It has been unistalled!
Once Play Store didn't let me upgrade some apps, because it said that i must logged in to my account (which i was already logged in), and others problems like that!
What shall i do now?
Root again the device? Unroot the device and root again? Unistall Knox? (i've read somewhere that Knox is responsible for problems after rooting). Find another version for CF- auto-root? (the latest is for Build ID LMY47X.G800FXXU1BPB2 but mine is LMY47X.G800FXXU1BPC4 if it matters)
Please help!
Yes, if you have root you must disable Knox. If it doesn't help, you can try go back to stock to see if it's a hardware issue (it will still lag), then root again if everything is fine for a day or two...
lfom said:
Yes, if you have root you must disable Knox. If it doesn't help, you can try go back to stock to see if it's a hardware issue (it will still lag), then root again if everything is fine for a day or two...
Click to expand...
Click to collapse
I have this device for about 2 years. These problems have begun just after rooting. So, i believe it is not a hardware problem.
By saying disable Knox you mean delete/unistall or freeze?
And how can i do that?
billphone said:
I have this device for about 2 years. These problems have begun just after rooting. So, i believe it is not a hardware problem.
By saying disable Knox you mean delete/unistall or freeze?
And how can i do that?
Click to expand...
Click to collapse
I would first use Link2SD to freeze all related to Knox and Security log first. If everything went right, backup and delete files.
lfom said:
I would first use Link2SD to freeze all related to Knox and Security log first. If everything went right, backup and delete files.
Click to expand...
Click to collapse
I freezed all apps and having the word Knox in their names. The phone isn't so laggy now but if i open some apps for rooted devices such as Busybox or Rom Toolbox they can't operate and got a message that my device isn't rooted. After that, no others apps for rooted devices are working! The SU doesn't open at all! All will work again after restart (except ofcourse Busy box Rom toolbox)
So what shall i do?
Unroot and root again? Root again over the previous root? What else?
billphone said:
I freezed all apps and having the word Knox in their names. The phone isn't so laggy now but if i open some apps for rooted devices such as Busybox or Rom Toolbox they can't operate and got a message that my device isn't rooted. After that, no others apps for rooted devices are working! The SU doesn't open at all! All will work again after restart (except ofcourse Busy box Rom toolbox)
So what shall i do?
Unroot and root again? Root again over the previous root? What else?
Click to expand...
Click to collapse
I thought that CF-Auto-Root disabled Knox protection when used, but maybe not... I think there is an option in SuperSU to disable it, you must use it as soon as you open it after using CF-Auto-Root and booting again to Android. If it doesn't have this option, it's not only Knox that makes the security system that prevents root, there is SecurityLog too (and on MM I think I've seen Rootpd that probably is a root protection daemon). Probably it removed su when you were disabling Knox. If you can root again over the current state, probably you can try disabling security system completely this time. Check other threads about rooting G800F, probably there is a list of apps you must disable.
lfom said:
I thought that CF-Auto-Root disabled Knox protection when used, but maybe not... I think there is an option in SuperSU to disable it, you must use it as soon as you open it after using CF-Auto-Root and booting again to Android. If it doesn't have this option, it's not only Knox that makes the security system that prevents root, there is SecurityLog too (and on MM I think I've seen Rootpd that probably is a root protection daemon). Probably it removed su when you were disabling Knox. If you can root again over the current state, probably you can try disabling security system completely this time. Check other threads about rooting G800F, probably there is a list of apps you must disable.
Click to expand...
Click to collapse
Thanks for your anwser.
The SU isn't permanently removed but only temporarily, because after restart it is working again
I 'll try to unroot and root again and we 'll see what happens
billphone said:
Thanks for your anwser.
The SU isn't permanently removed but only temporarily, because after restart it is working again
I 'll try to unroot and root again and we 'll see what happens
Click to expand...
Click to collapse
SuperSU is the app, su is the superuser daemon. Good luck.
billphone said:
Thanks for your anwser.
The SU isn't permanently removed but only temporarily, because after restart it is working again
I 'll try to unroot and root again and we 'll see what happens
Click to expand...
Click to collapse
So finally the problems are still here. The device is no longer laggy, but the root sometimes works sometimes doesn't.
I root again over the previous root, again the same. I unroot and again root, the same. I install a custom recovery and flash the SuperSU, the same results.
Initially working fine, giving rights to the applications but later sometime does not. With restart reverts briefly again.
What on earth has gone wrong? I have root many devices and all of them were working perfect!
I would like to avoid factory reset because i don't know how to restore my backup without problems.
Is there another solution?
Knox disables root, it can even revert custom recovery. Did you disable it, as well as Security Log (disable its updates in settings first), as suggested previously?
lfom said:
Knox disables root, it can even revert custom recovery. Did you disable it, as well as Security Log (disable its updates in settings first), as suggested previously?
Click to expand...
Click to collapse
Yes, i disable some apps with the word Knox in them. I don't know if is still a Knox app with a different name. Is there a list with Knox apps?
I didn't disable the Security Log neither its updates. Where can i find them?
So, finally i have a rooted device which randomly unroot itself!
And nothing can be done!
I am buying a unlocked note8. And I require root as a lot of my apps require it.... and it’s my understanding that I am going to need to stop the ota update in order to achieve root.
Can someone please tell me how to stop the ota update so I can root the device.
Hello,
Curious if are you going to run a custom rom or root and remove apps you don't want?
Tinythejuggalo said:
I am buying a unlocked note8. And I require root as a lot of my apps require it.... and it’s my understanding that I am going to need to stop the ota update in order to achieve root.
Can someone please tell me how to stop the ota update so I can root the device.
Click to expand...
Click to collapse
Which model do you have? Snapdragon?
Generally you can disable the software update using a Package Disabler from the Play Store, or freeze it using Titanium Backup once rooted. Simply turning off the update option in Settings will not work long-term, as it would eventually update anyways. That's why you need to disable or freeze it.
In developers options you can also turn off auto update system. Usually after you root OTA updates won't function anymore anyway after the device status changes to custom. Or does that not apply for US Snapdragons & SamFail?
Can I temporarily disable it just long enough so I can root. Via samfail
Yes, just go in settings - software updates, there change to download updates manually... Job done: nothing will be updated unless you initiate it yourself...
Can update be stopped without root?
Most package disablers are not working,dev option not working.
Have gone back to oreo from pie don't want be forced back onto pie.
I have a rooted Galaxy s10+ with android pie. Doesn't freezing "Software Update" system apps of my android by Titanium Backup make booting problems for my device? Is it safe for me to freeze those apps? I ask because I've heard freezing some system apps like "Device Care" stops the device from booting. As other fellas I get ota update notifications and I wanna get rid of them by freezing those apps.
MystaMagoo said:
Can update be stopped without root?
Most package disablers are not working,dev option not working.
Have gone back to oreo from pie don't want be forced back onto pie.
Click to expand...
Click to collapse
I am disabling apps with a package disabler for them to still keep updating! So I have gone back to the method of disabling apps via ADB (no root needed this way)
It uninstalls it for the current user, but a factory reset will bring the app back if so needed. You can uninstall the update app with this method, or any other app for that matter. (Just be careful with what you disable)
https://forum.xda-developers.com/ga...nstall-potentially-unneeded-unwanted-t3731062