I am wondering if OTA updates will still work if I install apps as system apps. For example, Avast (anti-theft app, successor to theft aware) has an option to install as a system app on a rooted phone, thereby enabling the app to survive a factory wipe. The way I believe it does this is install in the root directory. My understanding was that OTA updates will check to see if the root directory is a recognized stock directory before installing, so this would imply at installing other apps to root will cause this check to fail. However, I believe superuser is installed to root directory as part of the rooting process, and I have been able to perform OTAs on phones with superuser installed.
Anyone have any experience with updating OTA with apps installed to the root directory?
I believe that it moves them from /data/app to /system/app, thus changing how the phone sees the app.
Rlin5741 said:
I am wondering if OTA updates will still work if I install apps as system apps. For example, Avast (anti-theft app, successor to theft aware) has an option to install as a system app on a rooted phone, thereby enabling the app to survive a factory wipe. The way I believe it does this is install in the root directory. My understanding was that OTA updates will check to see if the root directory is a recognized stock directory before installing, so this would imply at installing other apps to root will cause this check to fail. However, I believe superuser is installed to root directory as part of the rooting process, and I have been able to perform OTAs on phones with superuser installed.
Anyone have any experience with updating OTA with apps installed to the root directory?
Click to expand...
Click to collapse
Usually the system apps are only updated individually with patch files. If there were extra files under /system, I don't think the patch would fail (or even care about it). I don't have any experience with it though, but that would be my logical guess.
Sent from my XT860 running ICS
AFAIK any changes to system changes cause OTA to fail. But I could be wrong. Never tried
Sent from my XT860 using xda premium
Related
Here is a Dump from the System Apps for those who accidentally deleted some of them and can't update to OTA2. I deleted some apps, you won't need for OTA2 to make the package smaller.
Remember before updating to OTA2 to protect your superuser by downloading and applying OTA root keeper.
After the update you have to download Superuser then just reactivate root by using ota root keeper.
PW for the archive is:
tptsystemappsdump
When I rooted ,I backup and delete some some flexT9 input file, then I find out I can not recive SMS after root .
So I unroot ,now I get OTA update but it's says error about I miss some flexT9 file.I can not restore file without root.
Now I can never root again ,and I can not even UPDATE OTA because system fille ar change.
What can I do NOW ?
My TPT is rooted (Titanium Backup shows it as rooted and RomManager also) but when I try to reinstall the Browser App it says could not install the app. Also Insallation via adb didn't work.
Can I somehow copy the files manually and what files need to be copied?
Thank you for this, one of our tablets unistalled the lenovo app market while trying to update itself, only want this for the notesmobile update but your dump helped greatly and meant i didn't have to faf about pulling it from my tpt
@Atom2007:
you will have to put the Browser.apk and Browser.odex into /system/apps with i.e. Root Explorer.
delete post
I have been trying to get "gsam root companion" to work on my htc one. I've rooted my device just so i could check out the features such as wake lock, etc.
The thing is, it keep saying "The Root Companion application is not installed correctly in /system/priv-app."
I tried manually installing it by copying the "com.gsamlabs.bbm.rootcomanion-1.apk" (whether or not if its the correct file) into the system/priv-app location. That restarted my device, and the file just disappeared from the priv-app location as well, and so the problem persist.
Am i doing everything wrong manually. Wish I could find a tutorial vid =/.
Thank you in advance
elfking7 said:
I have been trying to get "gsam root companion" to work on my htc one. I've rooted my device just so i could check out the features such as wake lock, etc.
The thing is, it keep saying "The Root Companion application is not installed correctly in /system/priv-app."
I tried manually installing it by copying the "com.gsamlabs.bbm.rootcomanion-1.apk" (whether or not if its the correct file) into the system/priv-app location. That restarted my device, and the file just disappeared from the priv-app location as well, and so the problem persist.
Am i doing everything wrong manually. Wish I could find a tutorial vid =/.
Thank you in advance
Click to expand...
Click to collapse
in order to write/modify/delete file in /system, you need an unsecured kernel (/system writeable), otherwise all changes made to /system will be reverted at reboot. I'm not using and never used gsam, maybe there is another option but the only one I know is to flash a custom kernel.
Kernel for the htc one (M7) are listed here
make sure to chose one that is compatible with your rom (sense/gpe based or AOSP based)
elfking7 said:
I have been trying to get "gsam root companion" to work on my htc one. I've rooted my device just so i could check out the features such as wake lock, etc.
The thing is, it keep saying "The Root Companion application is not installed correctly in /system/priv-app."
I tried manually installing it by copying the "com.gsamlabs.bbm.rootcomanion-1.apk" (whether or not if its the correct file) into the system/priv-app location. That restarted my device, and the file just disappeared from the priv-app location as well, and so the problem persist.
Am i doing everything wrong manually. Wish I could find a tutorial vid =/.
Thank you in advance
Click to expand...
Click to collapse
I just fiddled with this the other day, but didn't use the Root Companion app. It's not the Root Companion apk that's moved to /system/priv-app. It's the actual GSam Battery Monitor apk, com.gsamlabs.bbm.apk. The Root Companion app just does the move for you. If you have a file manager with root r/w permission, you should be able to do it yourself. Just move com.gsamlabs.bbm.apk from /data/app to /system/priv-app. Then restart your phone. I actually used an app called Link2SD to convert GSam Battery Monitor from a user app to system app and it accomplished the same thing.
alray said:
in order to write/modify/delete file in /system, you need an unsecured kernel (/system writeable), otherwise all changes made to /system will be reverted at reboot. I'm not using and never used gsam, maybe there is another option but the only one I know is to flash a custom kernel.
Kernel for the htc one (M7) are listed here
make sure to chose one that is compatible with your rom (sense/gpe based or AOSP based)
Click to expand...
Click to collapse
I'm running the stock AT&T 4.4.2 ROM rooted with the stock kernel and haven't had any issues with changes reverting back after a reboot. I use ES File Explorer & set it to have R/W permissions in that app's settings, but I assume that only applies to that app. Yet I've converted a few apps from user apps to system apps (3rd party launcher GSam Battery Monitor & SuperSU are the ones I remember off the top of my head) and never noticed them switching back to user apps. That is until I update them; then they become user apps. I don't know if this is because the apps I'm using to switch them have SU permissions or what, but none have changed back by simply rebooting. And as far as I know, I haven't done anything to modify the stock kernel from the OTA. Is it even possible to unsecure a stock kernel using apps?
alray said:
in order to write/modify/delete file in /system, you need an unsecured kernel (/system writeable), otherwise all changes made to /system will be reverted at reboot. I'm not using and never used gsam, maybe there is another option but the only one I know is to flash a custom kernel.
Kernel for the htc one (M7) are listed here
make sure to chose one that is compatible with your rom (sense/gpe based or AOSP based)
Click to expand...
Click to collapse
Thank you so much. I had this problem for days. Why isn't my unlocked phone writeable in the first place...
sharksfan7 said:
I just fiddled with this the other day, but didn't use the Root Companion app. It's not the Root Companion apk that's moved to /system/priv-app. It's the actual GSam Battery Monitor apk, com.gsamlabs.bbm.apk. The Root Companion app just does the move for you. If you have a file manager with root r/w permission, you should be able to do it yourself. Just move com.gsamlabs.bbm.apk from /data/app to /system/priv-app. Then restart your phone. I actually used an app called Link2SD to convert GSam Battery Monitor from a user app to system app and it accomplished the same thing.
I'm running the stock AT&T 4.4.2 ROM rooted with the stock kernel and haven't had any issues with changes reverting back after a reboot. I use ES File Explorer & set it to have R/W permissions in that app's settings, but I assume that only applies to that app. Yet I've converted a few apps from user apps to system apps (3rd party launcher GSam Battery Monitor & SuperSU are the ones I remember off the top of my head) and never noticed them switching back to user apps. That is until I update them; then they become user apps. I don't know if this is because the apps I'm using to switch them have SU permissions or what, but none have changed back by simply rebooting. And as far as I know, I haven't done anything to modify the stock kernel from the OTA. Is it even possible to unsecure a stock kernel using apps?
Click to expand...
Click to collapse
You just used your stock kernal 0.0
Why isn't mine like that. D=
elfking7 said:
You just used your stock kernal 0.0
Why isn't mine like that. D=
Click to expand...
Click to collapse
I have no idea. I didn't even know about needing an unsecure kernel to be able to write to /system. Nor do I know how the stock kernel became unsecure in the first place. All I've done is root the ROM as I normally would by flashing SuperSU. Then grant root permission to the apps that request it. If something in that process makes the stock kernel unsecured, then I don't know what it was.
You said in your OP that you tried manually moving the com.gsamlabs.bbm.rootcomanion-1.apk to /system/priv-app. First of all, that's the wrong apk. See my original reply for the apk you need to move. Do you even have GSam Battery Monitor installed? Battery Monitor & Root Companion are two separate apps. Battery Monitor needs to be installed before Root Companion will do its thing. At least I assume that's the case, b/c like I said before, I didn't use Root Companion to move Battery Monitor. But the description in Root Companion says all it does is move the Battery Monitor apk to /system/priv-app. Secondly, how did you move the apk? What app did you use?
Like I explained previously I originally used an app called Link2SD. That gives an option to convert user apps to system apps & vice versa. Just now I used it to convert GSam back to a user app. I wanted to test if moving the apk manually made a difference. After I converted it to a user app, I used ES File Explorer to cut & paste the GSam apk from /data/app to /system/priv-app. I then restarted my phone. The apk did not disappear and the app continues to work.
sharksfan7 said:
I have no idea. I didn't even know about needing an unsecure kernel to be able to write to /system. Nor do I know how the stock kernel became unsecure in the first place. All I've done is root the ROM as I normally would by flashing SuperSU. Then grant root permission to the apps that request it. If something in that process makes the stock kernel unsecured, then I don't know what it was.
You said in your OP that you tried manually moving the com.gsamlabs.bbm.rootcomanion-1.apk to /system/priv-app. First of all, that's the wrong apk. See my original reply for the apk you need to move. Do you even have GSam Battery Monitor installed? Battery Monitor & Root Companion are two separate apps. Battery Monitor needs to be installed before Root Companion will do its thing. At least I assume that's the case, b/c like I said before, I didn't use Root Companion to move Battery Monitor. But the description in Root Companion says all it does is move the Battery Monitor apk to /system/priv-app. Secondly, how did you move the apk? What app did you use?
Like I explained previously I originally used an app called Link2SD. That gives an option to convert user apps to system apps & vice versa. Just now I used it to convert GSam back to a user app. I wanted to test if moving the apk manually made a difference. After I converted it to a user app, I used ES File Explorer to cut & paste the GSam apk from /data/app to /system/priv-app. I then restarted my phone. The apk did not disappear and the app continues to work.
Click to expand...
Click to collapse
I followed alray's advice. I installed the elementalx kernel which made my system writeable, since my stock kernel wasn't originally. I then retry using the root companion (I installed gsam battery monitor since last week) which finally worked by using the automatic option that the root companion provided. I didn't notice much difference with the app, after giving the battery monitor privileged access to the system=/.
I just rooted my htc one (att version) and i'm using superSU. I want to use BetterBatteryStats, which required to add itself as system app. I tried its own method, Titanium Backup, LuckyPacher and even move the apk myself by Root expolorer, but none of them works- It seems work, but after rebooting the apk I copied to /system/apps (or /system/priv-apps) disappeared.
So my question is, is this operation required "S-off"? I knew I can't delete bloat apps due to this, but INCREASE files into system folders is also prohibited? If so, how could SuperSU be installed into /system/apps in the first place?
I knew this question may sound stupid, please forgive my very basic knowledge about android and thanks!
fireattack said:
I just rooted my htc one (att version) and i'm using superSU. I want to use BetterBatteryStats, which required to add itself as system app. I tried its own method, Titanium Backup, LuckyPacher and even move the apk myself by Root expolorer, but none of them works- It seems work, but after rebooting the apk I copied to /system/apps (or /system/priv-apps) disappeared.
So my question is, is this operation required "S-off"? I knew I can't delete bloat apps due to this, but INCREASE files into system folders is also prohibited? If so, how could SuperSU be installed into /system/apps in the first place?
I knew this question may sound stupid, please forgive my very basic knowledge about android and thanks!
Click to expand...
Click to collapse
You need to change your kernel, the stock kernel has write protection on it, try elementalx and no you don't need s-off
Am I able to upgrade to Lollipop, when it is released, if I freeze apps such as spotlight, hangout, Google+...
I am currently on Stock 4.4.4, rooted, stock kernel and recovery.
Sent from my XT1053 using XDA Free mobile app
kenosis said:
Am I able to upgrade to Lollipop, when it is released, if I freeze apps such as spotlight, hangout, Google+...
I am currently on Stock 4.4.4, rooted, stock kernel and recovery.
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Yes.
Freezing is just a method of renaming a system app. Unfreezing ALL of them too.
Being unlocked or safe strapped I always backed up my virgin system before making any modds so an update would go with just flashing stock recovery. Hiding root is needed sometimes too.
Thanks for your answer. I will just unfreeze freezed apps once 5.0 is available.
Sent from my XT1053 using XDA Free mobile app
kenosis said:
Am I able to upgrade to Lollipop, when it is released, if I freeze apps such as spotlight, hangout, Google+...
I am currently on Stock 4.4.4, rooted, stock kernel and recovery.
Click to expand...
Click to collapse
It depends on how you freeze them.
Every OTA so far has included a pre-flash validation check for the phone. It scans the phone for particular files and parts, for their existence and to make sure their checksum or SHA hash the expected versions BEFORE the OTA will install. Any method that renames, deletes, or otherwise modifies the APK and/or ODEX file for stock apps can cause an OTA install to fail.
If you use the phone's built in App Manager (Settings -> Apps -> open the entry for the app you want, then hit DISABLE, or Uninstall Updates then Disable), you are fine.
If you use something like Titanium Backup to Freeze them, you will likely be ok, but keep in mind that when some past OTA's came out (think 4.2.2 and 4.4), using Titanium to freeze apps did cause the OTA to fail for some people.
Using a root capable file explorer to manually rename, delete, or otherwise modify the APK and/or ODEX file can also cause an OTA install to fail.
This is why you see so many say that "you need to be stock to take an OTA"
aviwdoowks said:
Yes.
Freezing is just a method of renaming a system app. Unfreezing ALL of them too.
Being unlocked or safe strapped I always backed up my virgin system before making any modds so an update would go with just flashing stock recovery. Hiding root is needed sometimes too.
Click to expand...
Click to collapse
If you RENAME a system app that the OTA's Pre-flash validation steps look for, the OTA will fail. So any method of "freezing apps" that involves renaming the APK or ODEX files certainly can cause an OTA install to fail.
But of course, if the APK/ODEX you rename is NOT looked at during pre-flash validation, then the OTA will not fail.
Hi KidJoe, thanks for your explanation. I use Android Tuner and freeze apps such as spotlight, hangout, Google+, Live Wallpaper... I can unfreeze. Is it OK to do like that?
Sent from my XT1053 using XDA Free mobile app
KidJoe said:
It depends on how you freeze them.
Every OTA so far has included a pre-flash validation check for the phone. It scans the phone for particular files and parts, for their existence and to make sure their checksum or SHA hash the expected versions BEFORE the OTA will install. Any method that renames, deletes, or otherwise modifies the APK and/or ODEX file for stock apps can cause an OTA install to fail.
If you use the phone's built in App Manager (Settings -> Apps -> open the entry for the app you want, then hit DISABLE, or Uninstall Updates then Disable), you are fine.
If you use something like Titanium Backup to Freeze them, you will likely be ok, but keep in mind that when some past OTA's came out (think 4.2.2 and 4.4), using Titanium to freeze apps did cause the OTA to fail for some people.
Using a root capable file explorer to manually rename, delete, or otherwise modify the APK and/or ODEX file can also cause an OTA install to fail.
This is why you see so many say that "you need to be stock to take an OTA"
If you RENAME a system app that the OTA's Pre-flash validation steps look for, the OTA will fail. So any method of "freezing apps" that involves renaming the APK or ODEX files certainly can cause an OTA install to fail.
But of course, if the APK/ODEX you rename is NOT looked at during pre-flash validation, then the OTA will not fail.
Click to expand...
Click to collapse
+1
kenosis said:
Hi KidJoe, thanks for your explanation. I use Android Tuner and freeze apps such as spotlight, hangout, Google+, Live Wallpaper... I can unfreeze. Is it OK to do like that?
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
I haven't used that app. Best thing to say is take an app that you know what the apk name is, use Android Tuner to freeze it, then use a root capable file explorer to look for the apk. If it's still named correctly and located in the original place on the phone, then you should be ok.
I did try the search, but the answers were not clear as to the following questions:
If I am using systemless root, and I uninstall system apps, would that effectively modify "/system" and OTA updates will fail to install?
Also, I read that Titanium Backup is unable to uninstall system apps with systemless root and I need to manually delete the "/system/app/<app name>" folder with something like Root Explorer (mount /system r/w), is that true?
Thanks in advance
poodleDoo said:
.... delete the "/system/app/<app name>" folder with something like Root Explorer (mount /system r/w)...
Click to expand...
Click to collapse
OTA will fail on rooted devices.
System apps can be disabled in Settings. When deleted wit a rootexplorer the system partition is modified.
NLBeev said:
OTA will fail on rooted devices.
System apps can be disabled in Settings. When deleted wit a rootexplorer the system partition is modified.
Click to expand...
Click to collapse
Sorry, I should've been more clear.
I just installed FlashFire, and I am running systemless root.
If I delete a system app, would it prevent FlashFire to apply a OTA update; or is this a moot point?
And, I've read that with systemless, TiB does not actually remove system apps, is that true?
As for why I want to delete instead of just disable; why not?
Thanks
poodleDoo said:
If I delete a system app, would it prevent FlashFire to apply a OTA update....
Click to expand...
Click to collapse
The OTA checks modifications of system partition.
And, I've read that with systemless, TiB does not actually remove system apps, is that true?
As for why I want to delete instead of just disable; why not?
Click to expand...
Click to collapse
There is a lot written about 'systemless'.
The idea is that system files/folders are bind/linked to a 'su' folder. Apps are thinking that system is not modified.
Not all apps can be removed. Recently also Gmail can't be deleted. Disabling is the only option.
If you physically delete or change anything OTA will not work. Systemless SuperSU works by creating a Skylink with the user data partition and a modification withing the boot.img (the kernel). Any modification of any partition causes OTA to fail. So to successfully take an OTA you need to flash back the stock boot.img at the very least. Also the system.img if you made any modifications, and recovery if you are on twrp . . And modem.img and bootloader.img if they are not the ones that match the build you are on.
Sent from my Nexus 6 using Tapatalk