I'm on a non-dev Verizon and am rooted with 4.4. I don't want to upgrade and lose my root (re-enable WP, that is), so I've been delaying it by a day every time it shows. If I just want to stay on 4.4, how do I cancel the OTA notification?
Correct me if I'm wrong but... If you're not on the stock recovery, it will download the OTA but fail to flash which in return prevents it from asking for another OTA attempt. At least that's my experience from other phones.
Sent from my XT1053 using Tapatalk
I did that once, and it stopped asking. But within a day or so it had downloaded the OTA again and began notifying me again.
Freeze Motorola ota app.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
I am in a similar boat as you. My 4.4 is setup and working great. One of these days I will update to 4.4.2 through a rooted SafeStrap install. However, I don't have enough benefit at the moment to do so and risk loosing root, etc.
To disable the damn annoying update prompt I have frozen FOTA and MotorolaOTA using TitaniumBackup.
Other unrelated apps frozen is AT&T Locker, Motorola Migrate, myAT&T, Visual Voicemail.
What is FOTA?
Did you bother to search?
There are few threads I've seen about that. Search for it.
Sent from my XT1056 using xda app-developers app
If you are rooted, use a file manager/explorer with root compatibility (like Root Explorer), navigate to /system/priv-app and rename 3C_OTA.APK to something like 3C_OTA.APK.BAK and restart your phone.
If the OTA ZIP has already downloaded, you also want to navigate to /cache and find/delete the update ZIP file.
Should you ever want to take the OTA in the future, you'll just need to "undo" the rename.
Related
So I know being rooted and receiving OTAs isn't a problem, but I've read that having frozen apps can be. What happens if I/we get an OTA and an app is frozen? Does it fail gracefully or will I have a nice shiny paperweight as a result?Could we freeze/disable the update app/service until they push one out and we're ready for it?
Most likely the phone will reboot to do the update but will fail during the file system check. Your phone will then boot again and a message will pop up telling you the update has failed.
This is what happened with my D2. I would expect the same to apply to the D3.
Yes, your phone will refuse to take the update.
Nice. Sounds like it fails pretty gracefully.
Let's say your rooted but did not freeze or do anything at all will you still get a update. I've herd yes you can and no you can't. I can understand if you have froze or deleted things that you wont but if you didn't do a single thing except root that you might be able to get an update?
Sent from my DROID3 using XDA App
If you're rooted but have not frozen / deleted anything you will get the update and likely lose your root.
Getting the update to install successfully depends on what you have frozen vs. What the update tries to update. If you freeze something it wants to update, it will fail.
Root itself doesn't play a part in this.
Sent from my DROID3 using XDA App
So having the update fail because of required frozen apps may be a good thing! It will prevent unroot and prevent a fix to the root exploit on your phone.. giving you time to come back to the forum and check for other users experience.. i love XDA...
I definitely want an update when one comes out to fix the camera a the cell standby. I have froze stuff but I will unfreeze them when an update comes out. But nice to know that I don't have to do any weird stuff to take an update. Now will we be able to root again.
mkultramega said:
If you're rooted but have not frozen / deleted anything you will get the update and likely lose your root.
Getting the update to install successfully depends on what you have frozen vs. What the update tries to update. If you freeze something it wants to update, it will fail.
Root itself doesn't play a part in this.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Sent from my DROID3 using XDA App
Honestly, it's best to just wait. The update might patch root exploits and be very hard to root. If you wait just a little bit, then the devs will release a rooted and flashable update. Well, when we have recovery, that is. But recovery shouldn't be too far off.
If fixing the camera and cell standby is more important than root, then you should proceed with the update. If you want to keep your root, do not update quite yet, as GoogleAndroid said. It just might patch the exploit.
I would like to have non blue pics that would be nice. My phone ran really good before I froze stuff its a bit faster now so I would take the update and im sure someone will root that if not im still a happy droid 3 owner.
Sent from my DROID3 using XDA App
I am trying to root my att moto x (to be honest I am not a developer, so I just followed the guide 'Rockmymoto') then when I am trying to use Cydia Impactor to telnet my phone, it shows 'install parse failed no certificates'. I am using a Windows8.1 laptop, I've also got a Mac, but it seems not the computers' problem, what should I do now.
The only reason I want to root my phone is becasue I want to give it to my father, however it keeps noticing me the 4.4.3OTA, it is so annoying and I cannot turn it off. I heard that the only way to stop it is to root my phone and delet the OTA application. Please help me with it, thank you.
By the way, I am using the latest cydia impactor.
Sean-xb said:
I am trying to root my att moto x (to be honest I am not a developer, so I just followed the guide 'Rockmymoto') then when I am trying to use Cydia Impactor to telnet my phone, it shows 'install parse failed no certificates'. I am using a Windows8.1 laptop, I've also got a Mac, but it seems not the computers' problem, what should I do now.
The only reason I want to root my phone is becasue I want to give it to my father, however it keeps noticing me the 4.4.3OTA, it is so annoying and I cannot turn it off. I heard that the only way to stop it is to root my phone and delet the OTA application. Please help me with it, thank you.
By the way, I am using the latest cydia impactor.
Click to expand...
Click to collapse
RockMyMoto is for Jelly Bean 4.2.2_12.15.15 only..not KK
Also..not to delete the OTA..BUT..Freeze with Titanium Backup Pro, the MotorolaOTA 1.0
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
NWKENT said:
RockMyMoto is for Jelly Bean 4.2.2_12.15.15 only..not KK
Also..not to delete the OTA..BUT..Freeze with Titanium Backup Pro, the MotorolaOTA 1.0
Sent from my:
(Jaocagomex debloated)
4.4_19.6.3 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
Click to expand...
Click to collapse
He'd need root for titanium backup.
And to the original poster......do not try to downgrade if you're on 4.4.2 now. You will likely brick, if not now....later. Just don't try it.
Sean-xb said:
I am trying to root my att moto x (to be honest I am not a developer, so I just followed the guide 'Rockmymoto') then when I am trying to use Cydia Impactor to telnet my phone, it shows 'install parse failed no certificates'. I am using a Windows8.1 laptop, I've also got a Mac, but it seems not the computers' problem, what should I do now.
The only reason I want to root my phone is becasue I want to give it to my father, however it keeps noticing me the 4.4.3OTA, it is so annoying and I cannot turn it off. I heard that the only way to stop it is to root my phone and delet the OTA application. Please help me with it, thank you.
By the way, I am using the latest cydia impactor.
Click to expand...
Click to collapse
Your post doesn't really make sense....
You say you are using an AT&T Moto X, right? Then later you say that it keeps prompting you to install the "4.4.3" update?
AT&T never released a 4.4.3 update. The latest software version for the AT&T XT1058 is 4.4.2.
So which version are you CURRENTLY on? And what is the model of your phone? Go to Settings > About Phone > Status
The ONLY way you can use RockMyMoto is if you are currently on 4.4 or 4.2.2.
Let us know which version you are actually on, and we MAY be able to help you further.
Also, if the only reason you want to root is to disable firmware updates........why? Why not just accept the update, and then it will stop nagging you?
It sounds to me like you might have the "GSM Unlocked" version....the XT1053, and you just happen to be using it on AT&T. Please clarify.
Sorry for the incorrect information, but it is an AT&T Moto X. There is no 'simplified Chinese' in the original rom, so I swipe in a Rogers' rom which comes with the language. And then it means that it cannot accept any OTA or it will become a brick. It keeps notifying me the 4.4.3 OTA which is really annoying. And I need to root first before I can freeze that OTA app. here comes the pictures
samwathegreat said:
Your post doesn't really make sense....
You say you are using an AT&T Moto X, right? Then later you say that it keeps prompting you to install the "4.4.3" update?
AT&T never released a 4.4.3 update. The latest software version for the AT&T XT1058 is 4.4.2.
So which version are you CURRENTLY on? And what is the model of your phone? Go to Settings > About Phone > Status
The ONLY way you can use RockMyMoto is if you are currently on 4.4 or 4.2.2.
Let us know which version you are actually on, and we MAY be able to help you further.
Also, if the only reason you want to root is to disable firmware updates........why? Why not just accept the update, and then it will stop nagging you?
It sounds to me like you might have the "GSM Unlocked" version....the XT1053, and you just happen to be using it on AT&T. Please clarify.
Click to expand...
Click to collapse
In the past yearly updates to my iPhone decreased performance and slowed things down. After awhile I got tired of the decreased performance on hardware that used to run find and said "Screw It!" so I will keep it on iOS 7 forever and no update anymore.
Should I root to keep my 2013 Moto X on 4.4.3 and speedy as the day I bought it?
Or
Should I update to 4.4.4 knowing in advance I'll be forced to update to 5.0 down the line?
I don't flash or use root much at all, would just use it to simply prevent OTA automatic download.
Thank you for you thoughts
As far as I know, you don't prevent the download after root. In fact not even the installation unless you change files in the system partition.
So, you don't want to update your Android phone because you had bad experiences with your iPhone in the past with updates? That seems like great logic. I've never had any issues with updates causing the phone to run slower or worse, unless there was an inherent bug with the update, which happens occasionally, but only once or twice in the 5+ years I've had Android phones, over a wide array of devices. Based on reviews, there may be some small issues with 5.0 currently, but overall the OS should be faster than KitKat due to ART.
ap3604 said:
Should I root to keep my 2013 Moto X on 4.4.3 and speedy as the day I bought it?
Or
Should I update to 4.4.4 knowing in advance I'll be forced to update to 5.0 down the line?
Click to expand...
Click to collapse
It really depends on your device, but you certainly can't base the X updates on how it went with other phones.
You have 4.4.3 on there? Who is your carrier, or what model X is it? Have you unlocked the bootloader?
My advice, if you can unlock the bootloader, do so now. Root the phone, rename the 3C_OTA.APK and 3C_OTA.ODEX which reside in /system/priv-app. That will prevent any OTA from downloading and prompting you to install.
Then sit tight, wait for Lollipop to start being pushed, and the inevitable feed back that will come as people rush to install it.
Based on that feed back, you can stay where you are, or rename 3C_OTA.APK and 3C_OTA.ODEX back to their original names, and take the update.
KidJoe said:
It really depends on your device, but you certainly can't base the X updates on how it went with other phones.
You have 4.4.3 on there? Who is your carrier, or what model X is it? Have you unlocked the bootloader?
My advice, if you can unlock the bootloader, do so now. Root the phone, rename the 3C_OTA.APK and 3C_OTA.ODEX which reside in /system/priv-app. That will prevent any OTA from downloading and prompting you to install.
Then sit tight, wait for Lollipop to start being pushed, and the inevitable feed back that will come as people rush to install it.
Based on that feed back, you can stay where you are, or rename 3C_OTA.APK and 3C_OTA.ODEX back to their original names, and take the update.
Click to expand...
Click to collapse
KidJoe,
Since I am running stock 4.4.4, rooted, running TWRP 2.7.1.1 and using the XPosed X Tether module. Going with the current understanding that TWRP is not compatible (as of yet anyway) with 5.0 Lollipop, and to preclude from taking the 5.0 OTA, I went ahead and using root explorer, renamed the above two files in your post above by adding .bak to file extension. I also went into to etc/security and renamed the file otacerts.zip to otacerts.zip.bak. I'm thinking I should be good and that renaming these 3 files will not have any unintended consequences on the Moto X XT1060 and keep the phone from taking the OTA at this point in time. Thanks!
doiy, kid joe got you sorted, i missed that. sweet.. I did the same thing and renamed that file, I don't plan on upgrading to 5.0 OTA until after reviews etc come in for that OTA for moto x 2013.. or unless 5.0 gets xposed or something like it from chainfire
rob6909 said:
KidJoe,
Since I am running stock 4.4.4, rooted, running TWRP 2.7.1.1 and using the XPosed X Tether module. Going with the current understanding that TWRP is not compatible (as of yet anyway) with 5.0 Lollipop, and to preclude from taking the 5.0 OTA, I went ahead and using root explorer, renamed the above two files in your post above by adding .bak to file extension. I also went into to etc/security and renamed the file otacerts.zip to otacerts.zip.bak. I'm thinking I should be good and that renaming these 3 files will not have any unintended consequences on the Moto X XT1060 and keep the phone from taking the OTA at this point in time. Thanks!
Click to expand...
Click to collapse
I never touched the OTACERTS.ZIP, but you should be good to NOT get the Lollipop update until you rename those back
I am rooted on 4.4.2 on the N900A Note 3 for AT&T and I disabled the OTA notifications a long time ago to prevent breaking root and upgrading to 4.4.4. Now that the Lollipop update is available I would like to re-enable the OTA but when I go to the Application Manager then the Turned Off section, the AT&T Software update is listed but the Turn off button is greyed out and I can't turn it back on. Any suggestions? Please!
Did you freezed the app by using App Quarantine or another root app to disable it? I just re-enabled mine using App Quarantine.
Did you use Titanium Backup or something to freeze it? If so try unfreezing it there. Unless you Odin back to full stock the update will likely fail anyway though, even if you've unrooted. I would wait a day or two, there's a theoretical chance that the method of having root on 4.4.4 will work again (Be on a version Safestrap supports, flash a prerooted version of the ROM through that, then update the low level stuff via Odin)
Thank you both for replying... I have no idea what I did. I have Titanium Backup installed but I do not see a freeze feature. If I used a different app to freeze it will App Quarantine still unfreeze it? If so I'll try that. I no longer need root.
Even if you unfreeze it'll still likely fail out somewhere around 27% for ever being rooted, even if you unroot. You'll almost certainly have to Odin back to stock and take the OTAs in between, may as well wait for someone to post the Odin files for L so you can do it in one step I figure. If you do want to defrost it should work with anything that has that capability, for Titanium you click on the specific package and it should be the middle of the top row on the default Backup Properties tab, says Defrost
I can say neoman is absolutely correct. My phone is rooted and has 4.4.2. It downloaded the Lollipop 5.0 update today from AT&T but failed during installing. Main reason I rooted the phone was to overcome their Kitkat external SD Card issue. Now they fixed the issue with Lollipop but I can't update. I blame them on that .
I wonder if updating to 4.4.4 first will allow me to update to 5.0? The reason is I don't want to lose any current data or apps or settings. I still have a copy of the 4.4.4 downloaded ota earlier but never installed.
Bottomline is I want to update to 5.0 without losing data.
You'll absolutely have to Odin back to stock NC2 before trying to update to 5.0
andygev35 said:
You'll absolutely have to Odin back to stock NC2 before trying to update to 5.0
Click to expand...
Click to collapse
Is there an external download source for the Lollipop ROM to install via ODIN yet?
You can also Odin to stock NL1 http://forum.xda-developers.com/showthread.php?t=2999317
Typically if you're careful and you know everything you did with root, you can reverse and update... I did this a few times
Sent from my XT907 using XDA Free mobile app
I'm rooted and unlocked with 4.4.x XT1060 verizon
I don't want to take the OTA but i'm getting tired of being nagged to do so. I've tried moving the update file out of the 'cache' folder to somewhere else, but literally every time i turn on my phone I'm being nagged to upgrade.
Ideas?
peters4n6 said:
I'm rooted and unlocked with 4.4.x XT1060 verizon
I don't want to take the OTA but i'm getting tired of being nagged to do so. I've tried moving the update file out of the 'cache' folder to somewhere else, but literally every time i turn on my phone I'm being nagged to upgrade.
Ideas?
Click to expand...
Click to collapse
I believe using Titanium Backup to freeze the MotorolaOTA application is the usual advice. Older advice is to rename the OTAcerts.zip file in /system/etc/security but I don't know if that still works.
thanik you for the TBU freeze advice. i'll give that a try.
easier than that... go into settings>apps>all, scroll down to MotorolaOTA and untick the "show notifications" box. Done.
Thanks for this insight.
if you are rooted, to stop OTA's you can also rename 3C_OTA.APK and 3C_OTA.ODEX in either /apps or /privapp folder (using a file explorer with root abilities). Then you need to boot to recovery and clear cache..
When you are ready for OTA"s again, just rename them back, and reboot.
KidJoe said:
if you are rooted, to stop OTA's you can also rename 3C_OTA.APK and 3C_OTA.ODEX in either /apps or /privapp folder (using a file explorer with root abilities). Then you need to boot to recovery and clear cache..
When you are ready for OTA"s again, just rename them back, and reboot.
Click to expand...
Click to collapse
I did this but am still getting the OTA screen coming up. Maybe it's because the update file is already downloaded? If so, where does that hide. I've been looking but can't seem to find it. I've also been looking for the MotoOTA app to freeze that but that doesn't seem to exist anymore. I kinda wondering if I delete the update file, having the OTA.apk's renamed might stop it from trying again. Just not ready for the upgrade plus would rather have the full XML update instead of the OTA to be to fix any screw-ups I might have.
Yeah, same. The notifications can be dealt with using the "show notifications" step above. But the full screen pop-up reminder is harder to avoid. I'm surprised Moto is pushing this so hard.
What about uninstalling the Motorola update services update?
Sent from my XT1053 using Tapatalk
eldamobo said:
Yeah, same. The notifications can be dealt with using the "show notifications" step above. But the full screen pop-up reminder is harder to avoid. I'm surprised Moto is pushing this so hard.
What about uninstalling the Motorola update services update?
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Oddly enough, I only got one notification and then never again. Now it's just the full screen interrupt. It was really annoying when at a concert when trying to grab a video or two. Kept popping in and stopping the recording. If I wasn't at work I'd try to remove the update services. For now, I've gotten them frozen so let's see if it still nags like that.
I wish that once you say 'Maybe Later' at the first prompt it just leaves it to the update software menu under 'About Phone' instead of trying to force it.
dandroid213 said:
I did this but am still getting the OTA screen coming up. Maybe it's because the update file is already downloaded? If so, where does that hide. I've been looking but can't seem to find it. I've also been looking for the MotoOTA app to freeze that but that doesn't seem to exist anymore. I kinda wondering if I delete the update file, having the OTA.apk's renamed might stop it from trying again. Just not ready for the upgrade plus would rather have the full XML update instead of the OTA to be to fix any screw-ups I might have.
Click to expand...
Click to collapse
Did you boot to recovery and Erase cache?
When the OTA zip is downloaded, its stored in /cache which is only accessible if you are rooted. So booting to recovery and erasing cache will remove it from your phone.
KidJoe said:
Did you boot to recovery and Erase cache?
When the OTA zip is downloaded, its stored in /cache which is only accessible if you are rooted. So booting to recovery and erasing cache will remove it from your phone.
Click to expand...
Click to collapse
*This is on a Dev Edition if that makes a difference*
I do have access to /cache and it had the same in it as prior to clearing the cache, 3 folders (backup, lost+found, and recovery) and one text file (last_log under recovery.) This is a change from the last Moto I had. Granted that was the Droid X (damn them locked bootloaders) so older Android version. I've also looked for other ZIP's and the newest I can find is from the last time I had to update SuperSU.
I also cleared the davlik-cache on the second attempt but not sure if that would even come into play here. Unless TWRP is borked, cache has been cleared a few times now and now davlik as well.
But will say after freezing the Update Services, I haven't gotten the full screen nag again. Not sure what else is dependent on that but if it works, I'll keep it frozen for now and try breaking it more once home.
did you ever figure this out? My verizon dev edition moto x is driving me crazy with the OTA pop up...
fully rooted, unlocked over here, TWRP recovery.
I just renamed the OTAcerts.zip file in /system/etc/security and the 3C_OTA.APK and 3C_OTA.ODEX files in /system/privapp and rebooted.
I will see if that works...
So with a massive amount of thunderstorms last night I was without power (still am but at work so meh.) So I never got a change to try anything else. But I will report that freezing the Moto Update Services with TBackup worked perfectly. Haven't gotten a nag screen since. I'm just worried about other issues later down the line when trying to update other Moto services.
I'm not rooted, so for those not rooted, I'm using greenify on the update service. It also seems to shut the full screen nag off for now. That said, I think freezing would be better.
Not able to find update file to delete
Trying to get rid of nag screen for update MOTO X 2013 Sprint to version 212.144.2. Unchecked MotorolaOTA app, this did not work.
I am rooted, anyone know where to find file with Root Explorer to delete it? I don't want to accidentally install update.
On a side note, I am being asked to upgrade to v212.144.2 which I don't see anyone installing this OTA. BTW I am using my Sprint phone in South America