I am trying to move an app from /data/app to system/priv-app. I never encountered this issue before.
My Nexus 7 2013 LTE tablet (deb/razorg) was acting up and I had a bunch of apps on it. I figured the easiest thing to do is just wipe the thing and start fresh. So I used Nexus Root Toolkit to flash the latest version of stock OS (6.0.1 (MOB30X)) and then I rooted it using the latest Magisk (v18).
So I have root, I am able to see all the files in /. I tried using FX with mount R/W (tried mount R/W on "/", "/System" and "/system/priv-app") to copy the app folder from /data/app to /system/priv-app., however it failed.
I tried using 'App systemizer (Terminal emulator)' created by veez21 with Terminal emulator to move the app, but that didn't work either... despite App systemizer stated it was done.
I figured it could be the OS so i tried flashing it again and rerooting it again with Magisk, same issue and I tried an earlier version of the stock OS (6.0.1 (MMB30S)) same issue. Tried it again on the latest OS and this time rooted it with NRT instead of Magisk, same issue.
I clearly have root as titanium backup works fine with restoring apps.
So I think for some reason the OS is denying me write access to /system/priv-app, despite I did mount r/w.. I think I did all the steps correctly..so I am wondering if anyone can point me in the right direction. .. maybe I am missing a step somewhere..
pennywaltz said:
I am trying to move an app from /data/app to system/priv-app. I never encountered this issue before.
My Nexus 7 2013 LTE tablet (deb/razorg) was acting up and I had a bunch of apps on it. I figured the easiest thing to do is just wipe the thing and start fresh. So I used Nexus Root Toolkit to flash the latest version of stock OS (6.0.1 (MOB30X)) and then I rooted it using the latest Magisk (v18).
So I have root, I am able to see all the files in /. I tried using FX with mount R/W (tried mount R/W on "/", "/System" and "/system/priv-app") to copy the app folder from /data/app to /system/priv-app., however it failed.
I tried using 'App systemizer (Terminal emulator)' created by veez21 with Terminal emulator to move the app, but that didn't work either... despite App systemizer stated it was done.
I figured it could be the OS so i tried flashing it again and rerooting it again with Magisk, same issue and I tried an earlier version of the stock OS (6.0.1 (MMB30S)) same issue. Tried it again on the latest OS and this time rooted it with NRT instead of Magisk, same issue.
I clearly have root as titanium backup works fine with restoring apps.
So I think for some reason the OS is denying me write access to /system/priv-app, despite I did mount r/w.. I think I did all the steps correctly..so I am wondering if anyone can point me in the right direction. .. maybe I am missing a step somewhere..
Click to expand...
Click to collapse
Let's try to cover the bases and go from there.
1) root checker verifies the device is rooted?
2) you have Magisk root manager installed?
3) you have the latest version of busybox installed and have granted it root permission.
4) you have gone to system settings>developer options>root access and have set root access to "apps and adb"? (you may or may not have this setting)
5) you have set mount R/W? (you have also granted your file manager/root explorer superuser/root permissions?)
6) your bootloader is unlocked? (this may or may not be necessary)
7) you have set your SELinux polcy to "permissive" mode instead of "enforcing mode? (this may or may not be necessary)
8) have you checked to see if there are any Magisk modules that you might need?
9) you said that Titanium Backup is working, Titanium Backup has a feature that converts user apps into system apps for you, have you tried this option?
Sent from my LGL84VL using Tapatalk
REsponses below
Droidriven said:
Let's try to cover the bases and go from there.
1) root checker verifies the device is rooted? Based Root Checker I am rooted
2) you have Magisk root manager installed? Yes I have Magisk Manager installed, safetynet passed
3) you have the latest version of busybox installed and have granted it root permission. Yes, installed to /system/sbin
4) you have gone to system settings>developer options>root access and have set root access to "apps and adb"? (you may or may not have this setting) Not an option
5) you have set mount R/W? (you have also granted your file manager/root explorer superuser/root permissions?) Yes, FX has roots right based on Supersu and i have mounted R/W prior to pasting it into the director
6) your bootloader is unlocked? (this may or may not be necessary) It is unlocked
7) you have set your SELinux polcy to "permissive" mode instead of "enforcing mode? (this may or may not be necessary) Base on App Systemizer, SE Enabled is False, therefore I assume it is off
8) have you checked to see if there are any Magisk modules that you might need? Not that I know of, I have moved this app as system without it on my Nexus 7 before without any other modules and also have done it on my Pixel 1 phone without it
9) you said that Titanium Backup is working, Titanium Backup has a feature that converts user apps into system apps for you, have you tried this option? Yup tried it, it just hangs there, nothing happens
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Sounds like I covered all my bases... so I am puzzled
Related
Hi guys,
My Pixel are systemlessly rooted with Magisk since many months now, but for some reasons I'm tired by the method of Magisk: I want to touch at the /system partition, move or delete or edit system files and apps, and with Magisk I can't do it.
Okay, Magisk was pretty useful for keeping Safetynet pass, but with Xposed this ability becomes useless for me. Only things I'm still using is Magisk Hide for using Netflix or NFC paiment app, and Sony Framework module for using PS4 Remote Play.
Before I'm using Magisk and his systemless mode I was using SuperSU, and with it I had no problem with the system partition or with différents things like flashing Viper4android (didn't works whatever the way I use, magisk module or old system mode, it says the drivers need to be reinstalled), mouting partition/making file partition in Linux Deploy, stop background app, modifying the booting apps...
So I'm here now: are they exist a method for having system mode root and still using magisk modules ? Or maybe I've using the wrong way with Magisk and I've missed something for properly having root access ?
Thanks for your help ?
billiepreks said:
So I'm here now: are they exist a method for having system mode root and still using magisk modules ? Or maybe I've using the wrong way with Magisk and I've missed something for properly having root access ?
Thanks for your help ?
Click to expand...
Click to collapse
the whole point of magisk is to systemless modifications. I'm not sure that I follow all of the modifications that you want to make to the system partition?? or rather the specific apps that you want to use... but I can tell you that your /system partition (and others) are just mirrored with magisk and are tmpfs file systems...
I think the real /system lives in /dev/magisk/mirror/system, unless I'm mistaken....
question though; if you prefer SuperSU and only use magisk for safetynet, then why not just use a custom kernel that passes safetynet + SuperSU + suhide?. ... and then use that xposed or whatever....
anyhoo, you definitely have root access. but the intention with magisk and it's modules is to modify the system without actually modifying it directly....
nine7nine said:
the whole point of magisk is to systemless modifications. I'm not sure that I follow all of the modifications that you want to make to the system partition?? or rather the specific apps that you want to use... but I can tell you that your /system partition (and others) are just mirrored with magisk and are tmpfs file systems...
I think the real /system lives in /dev/magisk/mirror/system, unless I'm mistaken....
question though; if you prefer SuperSU and only use magisk for safetynet, then why not just use a custom kernel that passes safetynet + SuperSU + suhide?. ... and then use that xposed or whatever....
anyhoo, you definitely have root access. but the intention with magisk and it's modules is to modify the system without actually modifying it directly....
Click to expand...
Click to collapse
Thanks for your help ?
If Magisk create a mirror of /system as your said, this explain many things that I didn't knew since now.
This night I've made a clean installation of my Pixel, on stock 7.1.2 NJH47F with ElementalX 1.15 for hiding the unlocked bootloader, then I've flashed SuperSU 2.82 SR5. On xda I've seen that suhide 0.55 are discontinued since one year, and suhide-lite 1.09 who works with SuperSU 2.89 are uncompatible with Xposed, so I didn't flash it. There is a way to hide SuperSU with Xposed ?
For my needs with the /system partition, I'll try to explain better myself, I give you some examples:
- Uninstalling system app in ES Explorer or TiBu, it works but after reboot those apps are still here.
- Editing files like build.prop, unable to save the edited file or to replace original file by a modified one
- installing Viper4android drivers, it says "drivers needs to be reinstalled" everytime I launch it
- Linux Deploy, an app for running GNU/Linux distrib on your device, works the first time I launch it, but after reboot he said he didn't get root permission or found busybox, it's very strange.
Many things who worked before with SuperSU 2.79.
Edit : and what about SuperSU and CCMT ?
billiepreks said:
If Magisk create a mirror of /system as your said, this explain many things that I didn't knew since now.
This night I've made a clean installation of my Pixel, on stock 7.1.2 NJH47F with ElementalX 1.15 for hiding the unlocked bootloader, then I've flashed SuperSU 2.82 SR5. On xda I've seen that suhide 0.55 are discontinued since one year, and suhide-lite 1.09 who works with SuperSU 2.89 are uncompatible with Xposed, so I didn't flash it. There is a way to hide SuperSU with Xposed ?
Click to expand...
Click to collapse
You should look in Magisk's log to get a better idea of how it changes your system. trting to modify /system is pointless since it is a tmpfs mount (temperary)...
unfortunately, i can't help much with xposed. i don't use it. after it didn't work with Nougat, i ported a couple of it's modules to my rom (at the time) and then i got the pixel and i run Oreo + my own custom kernel + magisk...
xposed isn't providing any 'suhide' tyype functionality?
billiepreks said:
For my needs with the /system partition, I'll try to explain better myself, I give you some examples:
- Uninstalling system app in ES Explorer or TiBu, it works but after reboot those apps are still here.
- Editing files like build.prop, unable to save the edited file or to replace original file by a modified one
Click to expand...
Click to collapse
again, no point in editing your /system partition, it's a tmpfs mount, of course - any modifications will disappear on reboot.... you probably need to edit the real /system partition to make any change stick.
as far as the other apps, they obviously are trying to modify your aystem partition, which is why they don't work.... i think that you could install soumd mods via magisk modules?
i would recommend.consulting relevant forum threads on specific topics/apps though. u are bound to get better solutions&.
@billiepreks
Did you find the solution?
I'm in the same situation.
Did you try using TWRP's filemanager? I think it has true system access. You just need to mount the partition.
I've got my shiny new Pixel 4 XL up and running on the stock ROM after coming from a worn out Note 8. Everything is better except the new version of GMaps. I was using 9.47.x and this new 10.x.x is just awful. I want to completely delete the stub from the system so I can install the older version. I've tried several root uninstallers, even using the adb shell command. It always "uninstalls" but the stub is still there. Therefore the older APK refuses to install. I've even gone into the root/product/app/maps folder to try manually. It doesn't work, nor does changing any permissions. I have a feeling someone is going to tell me that this can't be done without installing a custom rom.
I'm guessing the culprit is not being able to remount the system with read/write permissions on newer versions of android. Unless there's something I'm missing.
iBreakStuff said:
I've got my shiny new Pixel 4 XL up and running on the stock ROM after coming from a worn out Note 8. Everything is better except the new version of GMaps. I was using 9.47.x and this new 10.x.x is just awful. I want to completely delete the stub from the system so I can install the older version. I've tried several root uninstallers, even using the adb shell command. It always "uninstalls" but the stub is still there. Therefore the older APK refuses to install. I've even gone into the root/product/app/maps folder to try manually. It doesn't work, nor does changing any permissions. I have a feeling someone is going to tell me that this can't be done without installing a custom rom.
I'm guessing the culprit is not being able to remount the system with read/write permissions on newer versions of android. Unless there's something I'm missing.
Click to expand...
Click to collapse
It may be having a conflict with cached data from the version that you installed, removing the cached data might allow you to install the version you want.
Uninstall the app from system partition, then, power the device off, then, boot into recovery and wipe the cache partition, then reboot into system and try installing the older version.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Uninstall the app from system partition, then, power the device off, then, boot into recovery and wipe the cache partition, then reboot into system and try installing the older version.
Click to expand...
Click to collapse
That is right where the issue is. I can get it to the point from being a 66mb APK down to 200k where the system; or play store, even recognizes it's installed. I need to get write access to the system partition to get rid of the "Maps" folder persistently living in the root apps folder. If that can be done on 10 in stock recovery then I've never done that. Mind you I'm rooted on Magisk with the flashed boot image, no TWRP yet.
iBreakStuff said:
That is right where the issue is. I can get it to the point from being a 66mb APK down to 200k where the system; or play store, even recognizes it's installed. I need to get write access to the system partition to get rid of the "Maps" folder persistently living in the root apps folder. If that can be done on 10 in stock recovery then I've never done that. Mind you I'm rooted on Magisk with the flashed boot image, no TWRP yet.
Click to expand...
Click to collapse
After flashing the Magisk patched boot.img, did you install the Magisk Manager app? Magisk Manager is what is used to grant root permissions to your other apps. There is more to it than just flashing the boot.img.
You can also use adb shell to remove the app as demonstrated in the second method described in the link below.
https://www.maketecheasier.com/uninstall-system-apps-without-root-android/
Sent from my SM-S767VL using Tapatalk
Droidriven said:
After flashing the Magisk patched boot.img, did you install the Magisk Manager app? Magisk Manager is what is used to grant root permissions to your other apps. There is more to it than just flashing the boot.img.
You can also use adb shell to remove the app as demonstrated in the second method described in the link below.
https://www.maketecheasier.com/uninstall-system-apps-without-root-android/
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
So I tried what you suggested, I got the same result. Maps uninstalls but still lives in the root directory. Not being an ADB expert I went into adb shell super user mode and tried the the rm command to delete the folder, also the remount system command. Neither of those worked. Trying to install the older APK results in "App not installed"
And yes I have Magisk manager. It installed the latest version automatically. I use RootExplorer and it has superuser permissions.
Would something like this work? I'm not completely clear on how this works.
https://www.isrgrajan.com/how-to-copy-and-delete-files-in-android-using-recovery-mode.html
I just installed the latest Android 10 for Pixel/Sailfish. I have use Magisk to root using the Boot Image Patching, as TWRP doesn't works yet for Android 10/Sailfish. I have enabled systemless host in Magisk and rebooted.
Now I have installed the latest version of FX File manager. When I goto root (granted root) within FX, I click mount R/W, it said that the folder is read-only. I had the same issue with EX file explorer.
I mainly want to edit a few files in /etc/permissions/ and move a few apps to system apps
What can I do to get the mount R/W to work? These are my normal steps on Android 9 to get this to work, I am unsure if I am missing anything
From my limited understanding and a few brief trawls of Google you can't write to system on 10 as you could in 9 or lower. Probably a job for a magisk module/terminal and edit it in a systemless way so to speak.
You can fastboot boot twrp 3.3.1-0, decryption works, it may show mounting errors but it does work, been using it to flash magisk and ROMs on my sailfish without problem.
junglism93 said:
From my limited understanding and a few brief trawls of Google you can't write to system on 10 as you could in 9 or lower. Probably a job for a magisk module/terminal and edit it in a systemless way so to speak.
You can fastboot boot twrp 3.3.1-0, decryption works, it may show mounting errors but it does work, been using it to flash magisk and ROMs on my sailfish without problem.
Click to expand...
Click to collapse
This is what I suspect also. I do know 10 is quite new.
I have been able to flash Magisk no issues. Root access is fine (adblock, titanium backup works). HOwever, I can't seem to mount r/w using a file explorer. I suspect this has to do with the way Google have upgraded its security, but I'm not fully sure.
pennywaltz said:
I just installed the latest Android 10 for Pixel/Sailfish. I have use Magisk to root using the Boot Image Patching, as TWRP doesn't works yet for Android 10/Sailfish. I have enabled systemless host in Magisk and rebooted.
Now I have installed the latest version of FX File manager. When I goto root (granted root) within FX, I click mount R/W, it said that the folder is read-only. I had the same issue with EX file explorer.
I mainly want to edit a few files in /etc/permissions/ and move a few apps to system apps
What can I do to get the mount R/W to work? These are my normal steps on Android 9 to get this to work, I am unsure if I am missing anything
Click to expand...
Click to collapse
You can't do anything. As you've been told before, the system partition can't be edited by the user on Android 10. Whether it is because of security or something else I don't know, but it's not possible at the moment.
Here is the explanation:
https://www.xda-developers.com/android-q-storage-access-framework-scoped-storage/
There are some workarounds detailed in this article but I haven't been able to get them to work.
Hey guys, so I tried using a system app remover to remove YouTube. On reboot, phone froze, crippled my OS. No biggie, just reflashed my rom. My question is, is freezing YouTube with titanium backup a better option or will that likely yield the same result? Making me just have to reflash my rom again anyway.
I'm running OOS beta 9.
xxx-No Limits works at doing this. As well as replacing it with You Tube vanced if wanted. I prefer NewPipe as my replacement.
Use magisk module Debloater(Terminal Emulator) to remove any system app, you also need to install magisk module busy box and Termux from the playstore.
If you want to install YouTube Vanced you can only disable official YouTube app and install non root Vanced and it will work without problems, root methods will need to disable apk verification, and magisk modules will overwrite official app so, the playstore Will update it even if you deactivated automatic updates.
Sent from my OnePlus7Pro using XDA Labs
Navigate to /System > /System > /App or /Pri-App Some apps are moved into /System > /System > /Product > /App or /Priv-App
With a file manager with root capabilities or just file manager in TWRP don't forget to mount system first. There you can delete any pre installed apps you want just careful what you remove as could lead to issue or loss of features etc. The tomato debloat script or xXx module should have a list of safe to remove apps.
twrp file manager has been the best. Just follow the confusing steps below
Reboot to twrp
Go to mount
Mount system and vendor
Go back to main page
Go to file manager
/system/system/
App
Data
Priv-app
Vendor
Product
there are several folders with these apps installed into so you'll have to go around and delete them
Only thing it doesn't delete is India.img (because oneplus has been sucking Indias dxxx while letting everywhere else struggle)
I've just rooted my 4a on Android 12 with Magisk by following this thread with the purpose of using Cerberus and having a reset protection, but to do so I have to put it in /system/priv-app and apparently you can't mount system read/write with a Magisk root .
There's the Systemizer module but as I understand system apps installed that way will be wiped after a reset.
I have also found this script Universal Mount System R/W but I'm not sure if it will do the trick.
So is there any way to accomplish what I'm trying to do? I don't mind another root method even if it doesn't bypass Safetynet as long as I can install Cerberus the right way.