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.
Related
I have a VZW DE on 4.4.2, unlocked bootloader, rooted, no custom ROM.
Was wondering if there is any way to hide the system update prompts/notifications as I'd rather wait for a more substantial upgrade (Android L).
Using root explorer I did go to etc/security/ and renamed otacerts.zip to otacerts.zip.bak to no avail. Also, there didn't seem to be anything for me to freeze in TiBu.
Not only is this a marginal upgrade imo, I just don't want to mess with going back to stock recovery, upgrading to 4.4.4, flashing TWRP, re-root, do system tweaks (e.g. replace ugly vzw 4G Icon and bars, but first check to see if someone made one compatible to 4.4.4), research whether wifi tether from xposed module still works on 4.4.4, etc. Just plain don't have the time to do all that at the moment.
Thanks in advance!
I thought I had replied to this exact question yesterday...
use a root capable file explorer, got to /system/priv-apps and rename 3C_OTA.APK
Of course, if your phone has already downloaded the file, navigate to /cache and remove it.
Reboot after making the changes.
that has prevented getting prompted in the past.
I did what Mark said.. renamed the 3c ota apk and also 3c ota odex file and confirm it will stop download and notices. if you just rename the 3c ota apk file alone and not the odex file to, you may get the download and reboot problems.. someone will have to confirm that, I gave a Moto X to my little brother running 4.4 and only renamed the 3c ota apk file and four weeks later he gave it back to me with a cracked screen and said it kept rebooting trying to update but failed because it was rooted. that's when I opened up root file explorer and noticed I did not change the odex file, I only changed the apk file. I'm running a 4.4 rooted and change both files and I never get the updates.
on my brother's new replacement phone running 4.4.2 I have it rooted with towelPie and renamed both files and seems to not be bothering me about the update now. I did let it download the new update at first attempt I went in and deleted the two files and it interrupted the download so I can confirm it will stop the download deleting those two files even when the download has already began
Out of curiosity, why wouldn't you take the update?
Sent from my Dev Edition Moto X
Schaweet said:
Out of curiosity, why wouldn't you take the update?
Click to expand...
Click to collapse
I can say for my two Non-DE Verizon Moto X phones running 4.4.2 and TowelPieRoot that I'm not taking the update for root reasons first and foremost. Until the time when a 4.4.4 root method is developed, if ever, I'll remain on 4.4.2.
I appreciate the suggestions in this thread however because I'm looking to hide these notices myself.
doitinthedirt said:
I did what Mark said.. renamed the 3c ota apk and also 3c ota odex file and confirm it will stop download and notices. if you just rename the 3c ota apk file alone and not the odex file to, you may get the download and reboot problems.. someone will have to confirm that, I gave a Moto X to my little brother running 4.4 and only renamed the 3c ota apk file and four weeks later he gave it back to me with a cracked screen and said it kept rebooting trying to update but failed because it was rooted. that's when I opened up root file explorer and noticed I did not change the odex file, I only changed the apk file. I'm running a 4.4 rooted and change both files and I never get the updates.
on my brother's new replacement phone running 4.4.2 I have it rooted with towelPie and renamed both files and seems to not be bothering me about the update now. I did let it download the new update at first attempt I went in and deleted the two files and it interrupted the download so I can confirm it will stop the download deleting those two files even when the download has already began
Click to expand...
Click to collapse
Thanks, all! I went ahead and renamed the odex as well. Rebooted and good to go!
Schaweet said:
Out of curiosity, why wouldn't you take the update?
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Would have to do a whole mess of stuff, like:
disable xposed frameworks and gravity box, defrost certain system apps and vzw bloat from TiBu probably, re-install android sdk (since I had formatted PC since 4.4.2), flash stock recovery, take the OTA, reflash custom recovery, re-enable xposed and gravity box (only gravity box has since split from one module to an ICS and KK version and I still have the old version), then upgrade and tweak gravity box settings, get rid of ugly VZW 4GLTE icon with stock/nexus version (but first see if someone made one that works on 4.4.4), research whether the xposed wifi-tether module works on 4.4.4, and maybe one or two other things...
all that takes TIME which I don't have a whole lot of at the moment... and all that for the ability to pause video recording and a get a dialer that has a white background instead of black? and supposed tweaks under the hood like battery and performance, all unconfirmed? yeah, personally, I'd rather wait.
Fair enough. So you know if you flash system.img once you reinstall xposed all your gravity box settings are still there.
Sent from my Dev Edition Moto X
jamespark said:
Would have to do a whole mess of stuff, like:
disable xposed frameworks and gravity box, defrost certain system apps and vzw bloat from TiBu probably, re-install android sdk (since I had formatted PC since 4.4.2), flash stock recovery, take the OTA, reflash custom recovery, re-enable xposed and gravity box (only gravity box has since split from one module to an ICS and KK version and I still have the old version), then upgrade and tweak gravity box settings, get rid of ugly VZW 4GLTE icon with stock/nexus version (but first see if someone made one that works on 4.4.4), research whether the xposed wifi-tether module works on 4.4.4, and maybe one or two other things...
all that takes TIME which I don't have a whole lot of at the moment... and all that for the ability to pause video recording and a get a dialer that has a white background instead of black? and supposed tweaks under the hood like battery and performance, all unconfirmed? yeah, personally, I'd rather wait.
Click to expand...
Click to collapse
Schaweet said:
Fair enough. So you know if you flash system.img once you reinstall xposed all your gravity box settings are still there.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Why not just use the FULL FXZ? http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you flash the FXZ, (since it is a "Keep Data" FXZ), you don't need to take the OTA. You don't need to disable Xposed. You don't need to disable any modules - or subsequently set them back up. You don't need to flash stock recovery. You don't need to worry about any modifications you have made to /system.... And you DON'T NEED THE OTA!
And just like @Schaweet has advised -- once you re-flash TWRP, re-root, and re-install Xposed Framework, all of your Xposed modules and their respective settings are already set the way you had them....
It turns this in to about a 10-15 minute process from start to finish. WAYYYY Easier. I don't get it...
EDIT: I do see that you have the "Old" gravitybox installed, so this might require setting up the new version. But everything else stated is completely relevant.
I froze MotorolaOTA 1.0
samwathegreat said:
Why not just use the FULL FXZ? http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you flash the FXZ, (since it is a "Keep Data" FXZ), you don't need to take the OTA. You don't need to disable Xposed. You don't need to disable any modules - or subsequently set them back up. You don't need to flash stock recovery. You don't need to worry about any modifications you have made to /system.... And you DON'T NEED THE OTA!
And just like @Schaweet has advised -- once you re-flash TWRP, re-root, and re-install Xposed Framework, all of your Xposed modules and their respective settings are already set the way you had them....
It turns this in to about a 10-15 minute process from start to finish. WAYYYY Easier. I don't get it...
Click to expand...
Click to collapse
HUGE. I haven't been following any forums for several months and was not aware of this FXZ. Great to know, thanks!
Mayze23 said:
I froze MotorolaOTA 1.0
Click to expand...
Click to collapse
same
A thread already exists for this exact thing here. Please post question in Q&A in future and search before creating new threads.
Thread closed
Hello all. I have the VZW dev edition of the moto x with an unlocked bootloader. I am trying to update my Moto X to the latest OTA from 4.4.2 but am running into an issue.
I flashed stock recovery and downloaded the latest OTA. When flashing the OTA zip in stock recovery, the installation aborts due to a problem with vznavigator.apk. It says "/system/app/vznavigator.apk" has unexptected contents. Installation aborted.
I am guessing my vznavigator.apk is messed up for some reason. Does anyone have the stock version they can give me so I can try to get past this error? Any other tricks?
Thanks
You can always get it from the Google Play Store.
Or perform the OTA update manually.
I already tried getting from play store. Doesn't work. I don't think the play store version places vznavigator.apk in the system/apps folder.
Regarding updating manually, this is what I am doing... Flashing manually in recovery.
Sent from my Moto X
You could try using mfastboot to flash the system.img from 4.4.2 to fix any inconsistencies in system. Then try the update again.
On the phone... go App Drawer -> Settings -> Apps. Swipe to get to ALL. Scroll DOwn to VZ Navigator and tap it. Hit the button to uninstall updates.
Then try the OTA again.
KidJoe said:
On the phone... go App Drawer -> Settings -> Apps. Swipe to get to ALL. Scroll DOwn to VZ Navigator and tap it. Hit the button to uninstall updates.
Then try the OTA again.
Click to expand...
Click to collapse
I don't think disabled or non-updated apps matter. When I did my update I did reflash /system but all my apps stayed disabled when I was up and running on 4.4.4.
I also did updates on my Razr Maxx that was rooted and while I didn't flash /system, I did undo any changes I had made to it and took standard OTA without re-enabling apps that were disabled.
I'm guessing VZNav was removed or otherwise modified with a method that wasn't the stock disable option.
Flashing /system should work. I don't think installing from the Play Store will because it would be a user app, not a system app.
Just my thoughts.
Reflashing the system.img worked perfectly! Thanks guys!
fury683 said:
I don't think disabled or non-updated apps matter. When I did my update I did reflash /system but all my apps stayed disabled when I was up and running on 4.4.4.
I also did updates on my Razr Maxx that was rooted and while I didn't flash /system, I did undo any changes I had made to it and took standard OTA without re-enabling apps that were disabled.
I'm guessing VZNav was removed or otherwise modified with a method that wasn't the stock disable option.
Flashing /system should work. I don't think installing from the Play Store will because it would be a user app, not a system app.
Just my thoughts.
Click to expand...
Click to collapse
Disabled and non-updated doesn't matter.. UPDATED might. Hence why I suggested to uninstall the updates.
My thinking was that it is possible that Verizon had updated VZNav AFTER they approved the 4.4.4 update (so the update is looking for a checksum of an older version).
Yes, flashing system will always work. I just usually suggest the simple things first (I have a longer list on the pages in my signature), and with the amount of people that are flashing the WRONG system.img and other components (i.e. not paying attention and using the ROM for the carrier, model and version phone they have), and those who don't realize the difference between mfastboot and fastboot, I've been hesitant to suggest flashing system.img until other things have been tried.
I bought this for my mom and I was wondering if the tablet did regular updates, would it lose google play? What would an OTA take out other than root?
I'm currently on 5.1.1(got mine the day the update was released and updated without knowing) and I was able to install google play and services and haven't had any problems with either. As far as OTA updates, I doubt it will prevent it from working but can't say for sure because we don't know what Amazon will do.
tuckerwagner said:
I'm currently on 5.1.1(got mine the day the update was released and updated without knowing) and I was able to install google play and services and haven't had any problems with either. As far as OTA updates, I doubt it will prevent it from working but can't say for sure because we don't know what Amazon will do.
Click to expand...
Click to collapse
Others have mentioned that the Amazon updates are full images, so I would speculate that if you had root and installed to system it would probably be wiped out. If you used the script, it just installs like a regular app and should be retained through an OTA like all the other apps. That's not to say that an OS change couldn't cause the frameworks or app to crash\stop functioning.
Didn't some others say they couldn't install Play store completely on 5.1.1 ?
[PSA] Information Regarding Firmware Version 5.1.1
Vlasp said:
List of things you can't do:
Remove Amazon Bloatware
Boot a .img from Fastboot
Downgrade to an earlier release
Root
Install Custom ROMS
Remove Lockscreen Ads
List of things you can do:
Install and use the Google Play Framework and Services
Click to expand...
Click to collapse
The current update may not break google play but at any time in the future a update may come out that does indeed break it. Why risk it? Just disable OTA.
It seems a bunch of people got screwed because they failed to kill OTA & got hit by 5.1.1. It's just foolish to leave OTA enabled. You can always apply a new update manually or even temporarily re-enable OTA if a new update proves safe & you want it.
blueberry.sky said:
[PSA] Information Regarding Firmware Version 5.1.1
It's just foolish to leave OTA enabled. You can always apply a new update manually or even temporarily re-enable OTA if a new update proves safe & you want it.
Click to expand...
Click to collapse
This. Completely automatic updates are for the elderly that have to call their children to be reminded how to cut/paste in Excel.
julianpaul said:
Didn't some others say they couldn't install Play store completely on 5.1.1 ?
Click to expand...
Click to collapse
The Google Play script from 5.0.1 works just the same in 5.1.1 without issue.
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
same thing happened to me just now.
not sure what to do, not sure if i have to reinstall everything again
fmkilo said:
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
Click to expand...
Click to collapse
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
JokersWild0075 said:
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
Click to expand...
Click to collapse
Listen up folks. Do not and i repeat do not update any of samsungs apks. Until we can find out whats going on. It seems that samsung is now pushing updates thru their apks to check and get rid of SU. They are getting sneaky. So for now do not update any samsungs apk, not even thru google. Also do not update SU, this is another way to lose root. We are working on it. Please do not ask if we found anything, if a fix is found we will post our findings.
If you need shealth, iris scanner, samsung pay, android pay, or any other samsung apk, then you need to stay on stock firmware and not use root.
Also if anyone is having issue with files or odin not flashing, make sure you are not on the new PI4 stock ROM, if you are then odin will fail everytime and at this moment there is no way to root or down grade to the older firmware.
Otherwise Try to redownload all files as it seem that afh is/was having alot of issues with uploads and downloads. This not something that we can fix as we dont host or own that site.
Can you guys break down the steps to regain root without reinstalling the OS? Mine also lost root on v2.
It looks like my S-Health was automatically updated to the latest version, which has been reported to be a root of the cause.
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
elite-fusion said:
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
Click to expand...
Click to collapse
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
galaxyuser88 said:
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
Click to expand...
Click to collapse
I am currently logged into the Samsung account and have been for about 2 days now with no ill affects so far, downloaded a couple themes is all...that is with all the Sammy stuff froze and functional root.
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