Related
CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?
RogueSly said:
CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?
Click to expand...
Click to collapse
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.
Nut_House said:
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.
Click to expand...
Click to collapse
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.
RogueSly said:
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.
Click to expand...
Click to collapse
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.
Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
I've already tried installing the latest nightly version and ran a permission fix on it, but end up with the same result. I'll try clearing cache, dalvik, and then fixing again.
gharlane00 said:
If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.
Click to expand...
Click to collapse
The file manager doesn't have any permissions in SuperSU and never asks for any since it's not in root access mode. :\
Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
Yeah, still the same result. Clearing dalvik and cache didn't work.
Just grab es file explorer.
Sent from my SPH-L720 using xda app-developers app
RogueSly said:
Yeah, still the same result. Clearing dalvik and cache didn't work.
Click to expand...
Click to collapse
same problem.
tried to install supersu, reinstall busy box on bin and xbin, fix permissions, no luck, option still greyed out.
file manager always worked for me as root, both on cm-based ROMs and aosp.
this time it is not working with the combo saberMod and matrix on N4.
(i think this is a device-independent issue)
---------- Post added at 08:20 PM ---------- Previous post was at 08:07 PM ----------
After a lot of tentatives I solved it.
I am not 100% sure of which change made it though
I think it was by using ES root manager and resetting system as R/W.
Sent from my Nexus 4 using xda app-developers app
Alternate fix
I also had the same issue and resolved it by tapping the menu button on the top left corner. when you do this, another menu button appears in the top right corner. Hit that, then settings, and choose root mode. Took me a while to figure out!!!
solved...
Installing busy box should resolve the issue...
Sorry for bumping, I have busybox and su installed, init.d support as well, but Cyanogen's File manager still cannot access root (option is grayed out). I'm on a stock Prestigio rom. It worked previously, but I reflashed firmware and now it doesn't work on this new firmware. Any thoughts?
Hi terirem and everybody,
I had this issue recently and I've managed to fix it. This is what You should do:
Short run:
Type in rooted phone terminal:
su
am start com.cyanogenmod.filemanager.ics
done
Long run:
1. Of course You need rooted phone, I've installed also BusyBox but I am not sure if it's necessary.
2. Install Terminal application
3. Install (if it's not installed yet) and run cyanogenmod file manager then minimize it by pressing home button (make sure You don't do anything else on Your phone to don't kill file manager process, it needs to be alive for 4th point)
4. I will make all commands bold for easier reading. run your terminal app and type: top -n 1 (this command will list all your running applications just once).
5. Find cyanogenmod in last "name" column, mine has name: com.cyanogenmod.filemanager.ics (if you can't find it you can try the one I had for 7th step, should probably work)
6. Type: su You will be asked to give superuser permissions to terminal, agree. Now instead of $ an # should appear, this means all commands from now on have root privilage.
7. Now we will finally rerun filemanager again with superuser permissions, type: am start com.cyanogenmod.filemanager.ics (if you had different name of filemanager just write the one you got after am start)
8. Go to cyanogenmod filemanager general settings and change access mode to root (it should be finally available, if not make sure again You typed am start with root permissions in terminal, if still doesn't work then forget about point 9).
9. Give me a beer, or actually simple thanks is enough, I need to stop drinking.
My SuperSU is kept auto-granting and system storage is kept read-written, also I cleared the every caches.
The CM file manager is still not shown a root mode to me.
I have J-rummy’s ROM toolbox as an alternative root explorer, but sometimes is less readable than CM file manager.
There is a guy forgetting to let the system storage read-written to remind him.
I did this with CM file manager - make sure you have root access not just safe mode in general settings. When you open filemanger it is granted super U access and then you can edit and save without issues
CM Dev Settings
In Dev options is Root access set to Apps and ADB?
For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode
bsevcenk said:
For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode
Click to expand...
Click to collapse
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).
passtim said:
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).
Click to expand...
Click to collapse
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
id74em8 said:
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
Click to expand...
Click to collapse
Apologies, but I'm no expert at these things. What is a 'systemless' SuperSU?
Is making a link as you suggest safe?
Xposed for Samsung Lollipop is out. But I am having trouble installing apps since I installed xposed so I decided to remove it. I restored the system partitioned with a backup I've made before the installation but looks like xposed isn't removed. I still getting "Optimising app" at every start up and I cannot install apps from Play Store. Many of users that installed xposed reported these.
I even tried to wipe system (not data) and flashing the rom I'm using on it again but xposed is still there. (Stil getting "optimising apps" and error "-504" from play store. ) What can I do to totally remove xposed without wiping data or restoring data partition?
ImjuzCY said:
Xposed for Samsung Lollipop is out. But I am having trouble installing apps since I installed xposed so I decided to remove it. I restored the system partitioned with a backup I've made before the installation but looks like xposed isn't removed. I still getting "Optimising app" at every start up and I cannot install apps from Play Store. Many of users that installed xposed reported these.
I even tried to wipe system (not data) and flashing the rom I'm using on it again but xposed is still there. (Stil getting "optimising apps" and error "-504" from play store. ) What can I do to totally remove xposed without wiping data or restoring data partition?
Click to expand...
Click to collapse
have you tried to clear the data from the playstore and let it rebuild the services ??
krazierokz said:
have you tried to clear the data from the playstore and let it rebuild the services ??
Click to expand...
Click to collapse
I did, for many times
ImjuzCY said:
I did, for many times
Click to expand...
Click to collapse
How about this?? thanks to @craigcrawford1988
Did you try this ?Simply boot into TWRP, and mount system, then Advanced -> File Manager then do the following:1.Go into /system/bin/ and delete app_process32 and app_process32_xposed
2.Rename app_process32_original to app_process32
3.Delete dex2oat and rename dex2oat.orig to dex2oat
4.Repeat the above step for oatdump and patchoat
5.Go up a directory and then into the lib directory
6.Delete libart.so and rename libart.so.orig to libart.so
7.Repeat the above step for libart-compiler.so, libart-disassembler.so and libsigchain.so
8.Delete libxposed_art.so
9.Go up a directory and delete xposed.prop
10.Go into framework directory and delete XposedBridge.jar
11.Reboot your device.
krazierokz said:
How about this?? thanks to @craigcrawford1988
Did you try this ?Simply boot into TWRP, and mount system, then Advanced -> File Manager then do the following:1.Go into /system/bin/ and delete app_process32 and app_process32_xposed
2.Rename app_process32_original to app_process32
3.Delete dex2oat and rename dex2oat.orig to dex2oat
4.Repeat the above step for oatdump and patchoat
5.Go up a directory and then into the lib directory
6.Delete libart.so and rename libart.so.orig to libart.so
7.Repeat the above step for libart-compiler.so, libart-disassembler.so and libsigchain.so
8.Delete libxposed_art.so
9.Go up a directory and delete xposed.prop
10.Go into framework directory and delete XposedBridge.jar
11.Reboot your device.
Click to expand...
Click to collapse
Tried that too but that was for the "normal" official xposed alpha. The way the devs set xposed on samsung touchwiz is different. We flash a different version of xposed framework.
Many of the original files you listed I don't find it (almost all). I think the only way to totally remove it is a full wipe
well good luck with your problem bud , i tried Sorry we could not determine the issue.... Long weekend !
Do u still need help?
From my s4 Powered by
Prism barebone v15
shiruuu.samad said:
Do u still need help?
From my s4 Powered by
Prism barebone v15
Click to expand...
Click to collapse
I already did a clean install. But help is still welcomed to help those who needs help
ImjuzCY said:
I already did a clean install. But help is still welcomed to help those who needs help
Click to expand...
Click to collapse
I had issues of FC with xposed i used this guide to disable it.https://plus.google.com/app/basic/stream/z13ecnpjtpirgbyn023sdjagnpmrzjarm04Check the last comment of google+ post it should disable it.Hope it works
From my s4 Powered by
Prism barebone v15
shiruuu.samad said:
I had issues of FC with xposed i used this guide to disable it.https://plus.google.com/app/basic/stream/z13ecnpjtpirgbyn023sdjagnpmrzjarm04Check the last comment of google+ post it should disable it.Hope it works
From my s4 Powered by
Prism barebone v15
Click to expand...
Click to collapse
I tried this but I still can't install apps larger than 1mb. Apps that are smaller than 1mb installed perfectly. I don't get fc BTW. I got error -504 from play store. I Googled about it and the error is due to lack of space in /cache partition. I checked the partitions and proved it. Only 800kb free in cache partition but play store needs to download apks to cache before installing. Even restoring titanium backups made during xposed is installed to a clean installed rom can cause that. So I did a clean install without any backups restored.
I tried clearing cache before, it's emptied when I cleared it, but it fills up when optimising app and I don't think I can skip optimising app after clearing cache.
Try formatting system, data, cache then restore system and after first boot, restore data
If didnt work (this is impossible) that means you did the backup after installing xposed
Goodluck
RubbaBand said:
Try formatting system, data, cache then restore system and after first boot, restore data
If didnt work (this is impossible) that means you did the backup after installing xposed
Goodluck
Click to expand...
Click to collapse
Yes I was lazy I backed up after installing the apk before flashing the zip. So that backup is somehow unusable. I already did a fresh install .
I managed to have magisk and magiskhide working sucessfully, with some manual tricks and workarounds
There is a bug in f2fs that prevents /data/magisk.img to me mounted writable, so the tweek is just moving that file to the /cache partition, which is ext4 and creating a symlink to the original file.
So the steps for a working magisk is.
- Unlock your bootloader
- Install Twrp
- Flash magisk without mounting data partition and boot once.
- Reboot to recovery and open terminal (advanced)
- move magisk.img to /cache partition, changing name ( example: mv /data/magisk.img /cache/magisk_2.img)
- Create a symlink between_files ( ln -s /cache/magisk_2.img /data/magisk.img)
Would be nice if anybody can try to reproduce.
Ah, so there is a way after all. I gather it works normally afterwards, with phh superuser, xposed and everything? I'm willing to try and reproduce your steps if so, maybe tweak the installer script so it does this automagically as well.
lpchaim said:
Ah, so there is a way after all. I gather it works normally afterwards, with phh superuser, xposed and everything? I'm willing to try and reproduce your steps if so, maybe tweak the installer script so it does this automagically as well.
Click to expand...
Click to collapse
I did not installed Xposed because I wanted to pass SafetyNet, but I cannot think a reason why it shouldn't work.
jblancoperez said:
I did not installed Xposed because I wanted to pass SafetyNet, but I cannot think a reason why it shouldn't work.
Click to expand...
Click to collapse
Right. I think I'll try this out today and see how things turn out. As for SafetyNet, I though the unlocked bootloader alone was enough reason for it not to work, is this only for some models?
Update: So, @jblancoperez, I've reproduced your steps and Magisk Manager tells me it's installed but root isn't activated and it doesn't let me do anything else as a result.
Things to have a look,
Please confirm in the terminal if /magisk is mounted.
Go back to TWRP terminal and also confirm if the symlink is OK.
Nice to get the output from /cache/magisk.log
It took me a while to have everything right, doing it on TWRP is not the easiest places to move things around.
So, an update. Your method just wouldn't work for me at all, no matter how many times I tried. What worked was following the first part only, as in unmounting data and then flashing Magisk afterwards. I've tried Xposed and Viper4Android; they worked, but both did have to be flashed through twrp as opposed to Magisk Manager, which would throw an error. Not sure if that's on them or on this particular method. I should mention though that SafetyNet wouldn't pass even before xposed and with the hiding settings, not sure why.
You may want to try the kernel where the f2fs bug is fixed, which may be the cause when Magisk hide is not working which would cause Safetynet to fail.
Is there anyone wanting to test brand new Magisk 11.0 if it runs fine on Moto Z Play? With and/or without that f2fs fix?
tag68 said:
Is there anyone wanting to test brand new Magisk 11.0 if it runs fine on Moto Z Play? With and/or without that f2fs fix?
Click to expand...
Click to collapse
I got bootloop when I install magiks 11.0.
Do you have a logfile of that action in /cache or /cache/recovery which we could show in the Magisk thread?
I was able to upgrade the 10.2 installation.
Will try a new clean installation on the weekend with the f2fs fixed kernel.
I think I got why my procedure is not working for other people. Please try to copy the image instead of moving with the flags preserving de selinux attributes.
jblancoperez said:
Please try to copy the image instead of moving with the flags preserving de selinux attributes.
Click to expand...
Click to collapse
Keeping attributes when copying or moving is what my guide regarding timestamp is about. It's not that easy using Android.
tag68 said:
Keeping attributes when copying or moving is what my guide regarding timestamp is about. It's not that easy using Android.
Click to expand...
Click to collapse
I used the same cp commands @topjohnwu used in the magisk script, cp -afc orig dest.
jblancoperez said:
I used the same cp commands @topjohnwu used in the magisk script, cp -afc orig dest.
Click to expand...
Click to collapse
cp -a tries to copy attributes including timestamps. But it only succeeds if you are currently running as root.
Don't ask me how, but I somehow set pattern and forgot it in one hour. I use face rec. as well but after reboot I need to unlock with pattern.
For last 10h I tried all methods how to unlock phone, but no success.
I'm using original, ROM, my G6 model is H870, running Pie, unlocked bootloader, so I can use TWRP. I spent most of my time and knowledge to unlock phone with adb/twrp. Best option I found is to delete gesture.key file which is located under /data/system.
Problem is, that /data is encrypted ...
Is there anyone who managed to remove pattern/lock without loosing data?
Thank you for your time!
akulp said:
Don't ask me how, but I somehow set pattern and forgot it in one hour. I use face rec. as well but after reboot I need to unlock with pattern.
For last 10h I tried all methods how to unlock phone, but no success.
I'm using original, ROM, my G6 model is H870, running Pie, unlocked bootloader, so I can use TWRP. I spent most of my time and knowledge to unlock phone with adb/twrp. Best option I found is to delete gesture.key file which is located under /data/system.
Problem is, that /data is encrypted ...
Is there anyone who managed to remove pattern/lock without loosing data?
Thank you for your time!
Click to expand...
Click to collapse
Maybe this will work: https://************/delete-android-security-pin/
Edit: link gets truncated... Just search 'Remove pin twrp' on Google and click the first result.
krilok said:
Maybe this will work: https://************/delete-android-security-pin/
Edit: link gets truncated... Just search 'Remove pin twrp' on Google and click the first result.
Click to expand...
Click to collapse
Non of this solutions work.
This is pretty the same as I said. My problem is that /data is encrypted and I can't find/see any .key files.
Also I can't do "su" command inside adb shell because of "insuff. privileges" ...
I tried all this solutions:
https://forum.xda-developers.com/showthread.php?p=49666433#post49666433
For method 1 -5 there is a problem with .key files which are not seen to my TWRP/Aroma browser. I don't know If I'm doing anything wrong in method 7, but also after mount I can't access /data/system (/data is empty).
In method 6 I'm stucked on
"Run pull settings.db.cmd inside By-pass security Hacks folder to pull out the setting file out of your phone." step.
I get "insuff. privileges" error.
akulp said:
Non of this solutions work.
This is pretty the same as I said. My problem is that /data is encrypted and I can't find/see any .key files.
Also I can't do "su" command inside adb shell because of "insuff. privileges" ...
I tried all this solutions:
https://forum.xda-developers.com/showthread.php?p=49666433#post49666433
For method 1 -5 there is a problem with .key files which are not seen to my TWRP/Aroma browser. I don't know If I'm doing anything wrong in method 7, but also after mount I can't access /data/system (/data is empty).
In method 6 I'm stucked on
"Run pull settings.db.cmd inside By-pass security Hacks folder to pull out the setting file out of your phone." step.
I get "insuff. privileges" error.
Click to expand...
Click to collapse
Have you tried this?
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
Basically, the files you have to delete in the /data/system folder in TWRP are:
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
It happened to me a while ago and I didn't have any '.key' files either; I just deleted the rest and when I booted up, I had no lock screen security PIN nor registered fingerprints but could re-set them again through security settings. I didn't need to flash any files nor fiddle around with adb commands, and all my data remained untouched...
If you can't find all those five files or the '.key' files, just delete the ones you can find and it should work. Otherwise, you'll probably have to do a full reset and reinstall...
krilok said:
Have you tried this?
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
Basically, the files you have to delete in the /data/system folder in TWRP are:
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
It happened to me a while ago and I didn't have any '.key' files either; I just deleted the rest and when I booted up, I had no lock screen security PIN nor registered fingerprints but could re-set them again through security settings. I didn't need to flash any files nor fiddle around with adb commands, and all my data remained untouched...
If you can't find all those five files or the '.key' files, just delete the ones you can find and it should work. Otherwise, you'll probably have to do a full reset and reinstall...
Click to expand...
Click to collapse
Problem is, that I don't have any files/folders at all in my /data. I even don't see system folder inside data.
akulp said:
Problem is, that I don't have any files/folders at all in my /data. I even don't see system folder inside data.
Click to expand...
Click to collapse
Sounds like your data folder is not mounted when you boot to TWRP... Have you checked? Reboot to TWRP, select the Mount option; data should be ticked by default. It it isn't, select it, go back to TWRP file manager, and see if you can now browse folders and files...
krilok said:
Sounds like your data folder is not mounted when you boot to TWRP... Have you checked? Reboot to TWRP, select the Mount option; data should be ticked by default. It it isn't, select it, go back to TWRP file manager, and see if you can now browse folders and files...
Click to expand...
Click to collapse
Unfortunately it's checked ... It's seems from this post:
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008/page12
nobody managed to get to (encrypted) /data on Pie.
akulp said:
Unfortunately it's checked ... It's seems from this post:
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008/page12
nobody managed to get to (encrypted) /data on Pie.
Click to expand...
Click to collapse
Last comment on that thread says the solution also works on Havoc Os 2.9, which is based on Pie... Maybe that person wasn't encrypted to begin with, but, if it doesn't work for you, I guess then the only way to go is a full reset... Good luck!
krilok said:
Last comment on that thread says the solution also works on Havoc Os 2.9, which is based on Pie... Maybe that person wasn't encrypted to begin with, but, if it doesn't work for you, I guess then the only way to go is a full reset... Good luck!
Click to expand...
Click to collapse
Yep, I saw that post ... I relly don't have any more ideas. Should be inside "mount modul" in TWRP /data listed?
I only have System, Cache and SD ... and i can check System only if i check bottom "mount system partition read-only" option.
But that's nothing to do with /data.
akulp said:
Yep, I saw that post ... I relly don't have any more ideas. Should be inside "mount modul" in TWRP /data listed?
I only have System, Cache and SD ... and i can check System only if i check bottom "mount system partition read-only" option.
But that's nothing to do with /data.
Click to expand...
Click to collapse
Data option should show. At least it does on mine... You can maybe try updating Twrp version?
I'm on last TWRP.... Meantime I already made full reset ....
If you have encrypted data partition, you're pretty much banned from messing with it, unless you manage to exploit your way through the adb, which requires you to have it enabled and in trust relation with your PC to begin with.
The way I'd go around this is to place an "always yes su" binary and perform pattern removal process through init.d or similar solution. In case if su commands are restricted, kernel with permissive SELinux needs to be flashed.
On a side note, isn't this Q&A?
I also had a problem with data folder not being mounted when booting to TWRP. I tried a full reset and immediately i have access to the Data folder (but theres nothing left inside so this is kinda useless). Then later when i did a reboot into the TWRP it happened again, couldnt access to anything even when the "mount Data" option is ticked, only until i did the full reset again that it could finally work.
It turned out the problem is with the TWRP itself, i flashed another custom recovery (OrangeFox-R10-Stable-h870, which is btw a better recovery than TWRP in my opinion) and the problem never occurred again.
So either try out that new Recovery or a different version of TWRP and see if it solves the problem. And always, ALWAYS, make a full backup of all your data before messing with anything (i had to learn that the hard way so trust me).
Do this,
- you should know that I am using "orange fox recovery" not "twrp",and stock "pie"
- reboot to recovery and go to system/data
- delete this files:
gatekeeper.password.key
gatekeeper.pattern.key
locksettings.db
-reboot the phone and that's it.
Hi, a few days ago I manually updated my OP6T to the latest version manually (I can't do it normally because I'm rooted and the system shows me an error)
I use the Cerbeus anti-theft application, I like to turn it into a system application to have full control of my phone in cases of emergency (theft, for example).
The point is that I can install magisk 20v and root perfectly, but when I try to make cerberus or any application as a system application, it shows me the error 'system' not in / proc / mounts, I use link2sd, titanium back up, root explorer all the options does not work, i cant mount rewrite to erase system apps but i can't make normal apps to system app, I tried to update the ROM stock directly from the official website, but at the end, always shows me that error, can anyone help me with this problem?
Thank you! if you need more information tell me
I'm so sorry if my English is not too good, I'm still learning
Bootloader unlocked
Recovery TWRP fajita lastest version
There's a magisk module called systemize that should be able to do what you're wanting as far as turning it into a system app
jestyr8 said:
There's a magisk module called systemize that should be able to do what you're wanting as far as turning it into a system app
Click to expand...
Click to collapse
I was try to much things, really, i never see that module and i have youtube venced module and native OS recorder
Thank you for the tip !
linkoerk said:
I was try to much things, really, i never see that module and i have youtube venced module and native OS recorder
Thank you for the tip !
Click to expand...
Click to collapse
Just search the download list for systemize.
I've used it for a few apps that need system level access and it's worked great
Yes woked perfectly thank you very much
EDIT:
I tried a few days ago, All converted applications were removed with factory reset are they not supposed to be already in the system partition?
linkoerk said:
I tried a few days ago, All converted applications were removed with factory reset are they not supposed to be already in the system partition?
Click to expand...
Click to collapse
Someone can help me with this? i already try to put manually in priv-app with a explorer an random app and worked well when i do FR but do not work properly, never open correctly, and if i try to do the same with magisk or cerberus app show me an error ''Cant complete the action''
Thank you!
linkoerk said:
Someone can help me with this? i already try to put manually in priv-app with a explorer an random app and worked well when i do FR but do not work properly, never open correctly, and if i try to do the same with magisk or cerberus app show me an error ''Cant complete the action''
Thank you!
Click to expand...
Click to collapse
AFAIK Systemize Is the easiest and recommend way. About the things being removed after factory reset, that's normal as Systemize is System-Less. All changes it makes will be reverted after a Factory Reset.
Mannan Qamar said:
AFAIK Systemize Is the easiest and recommend way. About the things being removed after factory reset, that's normal as Systemize is System-Less. All changes it makes will be reverted after a Factory Reset.
Click to expand...
Click to collapse
Another way to make a user app to system app? Link2SD is not working anymore
linkoerk said:
Yes woked perfectly thank you very much
EDIT:
I tried a few days ago, All converted applications were removed with factory reset are they not supposed to be already in the system partition?
Click to expand...
Click to collapse
Magisk modules don't touch physically system partition. It's the only way to keep security verifications green. Magisk modules are in data partition and are 'mounted' is system ram disk
Hi again guys, now im trying again to make Cerberus as system app I was able to solve the problem about mounting system, through ADB I placed the APK manually in the system / priv-app folder, I gave it permissions with CHMOD 644 i restarted and effectively became system application Up to this point everything was in order, until I did a factory reset, I got stuck in the boot animation, To solve it I had to boot TWRP and manually remove the apk from the priv-app folder, with this the system boot normally (curious because the root permission was there Despite having restarted the System)
Someone have any ideas to solve it? I don't care about magisk and if the safety net are in red
Thanks!
Help guys, any ideas ?
linkoerk said:
Help guys, any ideas ?
Click to expand...
Click to collapse
use systemize to move the app + libs to /system/priv-app
copy the folder to /system/app (you cannot delete)
uninstall Magisk to kill the module
estou com o mesmo problema no Link2