Hello,
i finally got my Nexus 5 today and first thing I did was unlocking the bootloader, installed TWRP custom recovery, flashed CM11-nightly and Franco Kernel (r31).
Next thing I usually do is to uninstall some apps with Titanium Backup (Pro). But I can't uninstall any system apps (e. g. Browser.apk). Titanium says "successful" but after refreshing the application list, the app is still there.
Does anyone have an idea what is going wrong here? Is it a problem with CM11's superuser or with Titanium Backup?
Thanks.
Cloonix said:
Hello,
i finally got my Nexus 5 today and first thing I did was unlocking the bootloader, installed TWRP custom recovery, flashed CM11-nightly and Franco Kernel (r31).
Next thing I usually do is to uninstall some apps with Titanium Backup (Pro). But I can't uninstall any system apps (e. g. Browser.apk). Titanium says "successful" but after refreshing the application list, the app is still there.
Does anyone have an idea what is going wrong here? Is it a problem with CM11's superuser or with Titanium Backup?
Thanks.
Click to expand...
Click to collapse
What happens if you delete the file with a file manager and reboot?
Aerowinder said:
What happens if you delete the file with a file manager and reboot?
Click to expand...
Click to collapse
I used Solid Explorer as a file manager and tried to delete /system/app/Browser.apk. The root-confirmation (CM11 superuser) pops up, asks for superuser (i grant) and Solid Explorer deletes the file without error. But the file is still there (without reboot).
Issue with superuser?
Edit: Stop... I noticed /system is mounted as read-only.
I tried to analyze the problem... and the only conclusion is, that my superuser is not working. Also Super SU ist not working. I also flashed Omni ROM instead of CM11 with no success. I used an older version of TWRP without success. Does anybody has an idea?
Edit: Before with Stock ROM and Super SU it was working.
I don't know why I'm the only person with this issue... But I solved it with the following steps:
1. Flash CM11 (nightly)
2. Start the OS
3. Reboot to recovery and wipe cache/dalvik
4. Install "Super SU"
5. Start the OS
Titanium Backup is asking for root rights. Other apps also didn't get root in CM11. Whenever I install a new CM11 nightly root rights for TB are gone and I have to do the same steps again.
But why no one else has this problem? I googled like crazy. Is it CM11 or me?
Me to, cm11 for a850L build on crdroid nexus4
Cloonix said:
I don't know why I'm the only person with this issue... But I solved it with the following steps:
1. Flash CM11 (nightly)
2. Start the OS
3. Reboot to recovery and wipe cache/dalvik
4. Install "Super SU"
5. Start the OS
Titanium Backup is asking for root rights. Other apps also didn't get root in CM11. Whenever I install a new CM11 nightly root rights for TB are gone and I have to do the same steps again.
But why no one else has this problem? I googled like crazy. Is it CM11 or me?
Click to expand...
Click to collapse
Did you leave out Franco kernel this time?
This is the fix for your issue:
http://forum.xda-developers.com/showthread.php?t=2592456
es0tericcha0s said:
This is the fix for your issue:
http://forum.xda-developers.com/showthread.php?t=2592456
Click to expand...
Click to collapse
Thanks a lot!
Changing selinux to "permissive" did solve all my problems. I also had issues with other applications.
How can I change the selinux mode directly in the CM11-Zip? Under Redhat/CentOS is a configuration file unter /etc/selinux. In CM11 I can't find something similar.
And how it comes that this issue is not well-known? I think there are more 4.4 KK / CM11 users with problems.
Aerowinder said:
Did you leave out Franco kernel this time?
Click to expand...
Click to collapse
No I flashed Franco after CM.
Cloonix said:
Thanks a lot!
Changing selinux to "permissive" did solve all my problems. I also had issues with other applications.
How can I change the selinux mode directly in the CM11-Zip? Under Redhat/CentOS is a configuration file unter /etc/selinux. In CM11 I can't find something similar.
And how it comes that this issue is not well-known? I think there are more 4.4 KK / CM11 users with problems.
No I flashed Franco after CM.
Click to expand...
Click to collapse
No problem. I know that problem was starting to annoy me. Got the idea from playing with a new Note 3. The newer Samsung 4.3 roms are like that too. If you don't change to Permissive then Xposed and other mods won't work either.
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?
es0tericcha0s said:
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?
Click to expand...
Click to collapse
Even without Franco (which was my first guess) CM11 (my root) behaves that way.
I will look for a method to set selinux to permissive directly in the ZIP of CM11 and will update this post.
Cloonix said:
Even without Franco (which was my first guess) CM11 (my root) behaves that way.
I will look for a method to set selinux to permissive directly in the ZIP of CM11 and will update this post.
Click to expand...
Click to collapse
I'd imagine adding something like this in: http://forum.xda-developers.com/showpost.php?p=48006307&postcount=65 would do the trick, though I have not had that issue in awhile. I switch roms often.
es0tericcha0s said:
I'd imagine adding something like this in: http://forum.xda-developers.com/showpost.php?p=48006307&postcount=65 would do the trick, though I have not had that issue in awhile. I switch roms often.
Click to expand...
Click to collapse
I tried this. And it was successfully changing selinux to permissive with every reboot. But doing this I noticed that even permissive doesn't solve the problem. CM11 built-in superuser just don't work for me. Only "Super SU" by Chainfire works well. And permissive solves a few other problems besides TiBa.
Personally I've always eventually had issues with Superuser unmounting the system as rw causing issues with apps like Titanium. Had it happen many many times on my old phone as well as the Nexus 5 across multiple ROMs. I just stick with SuperSU now.
Haven't had too many issues with that part it seems, but glad you narrowed down the problems.
I find this issue sometimes on varous flashes of CM 11 on different devices.
I use ROM toolbox fo manage apps, and sometimes it just wont delete. The solution is strange: I install adaway - somehow, that "unlocks" something that lets you delete apps. You can uninstall adaway once you have run it!
Galaxy Nexus
I'm replying just to help out anyone who has this issue, but doesn't have a Nexus 5. I was trying to find a fix for me and my Galaxy Nexus running the latest Paranoid Android beta 4.4.2 because I kept having this same problem.. It wouldn't uninstall... and I would only keep getting directed to this specific post. So....
I tried the 'selinux' fix first, and that alone would not do a thing...
I then tried installing the 'Wanam Xposed' app and it worked perfectly.
Just change selinux to permissive and make sure both selinux and Wanam have SU access and then try to uninstall via Titanium... or whatever method you usually use.
Hope it's okay for me to post here. Thanks for the help, everyone!
es0tericcha0s said:
No problem. I know that problem was starting to annoy me. Got the idea from playing with a new Note 3. The newer Samsung 4.3 roms are like that too. If you don't change to Permissive then Xposed and other mods won't work either.
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?
Click to expand...
Click to collapse
Hi,
unfortunately the SElinuxModeChanger seems not to work for me (Samsung Galaxy S2, CM 11 m6) and I do not really get how I should install Supersu (the first described solution). I guess I should not just install it from the play store - right? But were do I get an installable zip-file to install it from the CWM?
Or is there anything else that might be wrong in my system - so that I do not need to install supersu at all?
regards
Daniel
daniu said:
Hi,
unfortunately the SElinuxModeChanger seems not to work for me (Samsung Galaxy S2, CM 11 m6) and I do not really get how I should install Supersu (the first described solution). I guess I should not just install it from the play store - right? But were do I get an installable zip-file to install it from the CWM?
Or is there anything else that might be wrong in my system - so that I do not need to install supersu at all?
regards
Daniel
Click to expand...
Click to collapse
If you are already using CM11, then yes, you can install SuperSu from the Play Store. Once you do and open the app, it will prompt you to update the SuperUser binary. You should be able to do the "normal" method, and then once that updates, reboot, then try the SELinux app again and then everything should start to work like you would expect. If the normal method doesn't work, then you can let it download the newest zip for you if you choose the CWM/TWRP method, and then boot to recovery and install the zip it downloads for you.
SeEsAw12 said:
I'm replying just to help out anyone who has this issue, but doesn't have a Nexus 5. I was trying to find a fix for me and my Galaxy Nexus running the latest Paranoid Android beta 4.4.2 because I kept having this same problem.. It wouldn't uninstall... and I would only keep getting directed to this specific post. So....
I tried the 'selinux' fix first, and that alone would not do a thing...
I then tried installing the 'Wanam Xposed' app and it worked perfectly.
Just change selinux to permissive and make sure both selinux and Wanam have SU access and then try to uninstall via Titanium... or whatever method you usually use.
Hope it's okay for me to post here. Thanks for the help, everyone!
Click to expand...
Click to collapse
No clue why, but this worked for me. Permissive didn't do it (was already permissive using CM 11 for tf201) and AdAway didn't do it. Didn't matter that Wanam Xposed is for Samsung devices, once given root to this app, Titanium got its head out of its rump.
UPD: So, if i uninstall Wanam Xposed then TB sticks its head back up its rump. Whatever giving root to that app does, its fixing usage issues with TB.
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
I was about to put this in the main discussion thread of FlashFire, but it was closed so i decided to post it here.
So this is what happened, i rooted my Xiaomi Redmi Go with Magisk, the latest one, and when i opened FlashFire, it basically said that i have root, but access couldn't be acquired. It added "Found root: 19.4:MAGISKSU".
It was said in the Supported roots that Magisk is included so can't i use this app? I also tried to change my SELinux to permissive mode by going to the terminal and putting "setenforce 0", and the app still won't let me.
Any solutions to this? I was about to do perform a live backup through this app because the current TWRP version for this device is defective for my phone, the Backup option doesn't work and I've been looking for ways to backup my phone without custom recovery, but still with root of course.
Any help would be appreciated, thankyou!
Flashfire is discontinued so it is no longer compatible with the latest versions of Magisk
You might try going back to a older Magisk. It's definitely going to be before 19.3 but it may need to be older than that. There are two ways of doing this.
Set a custom channel in Magisk manager (install the older manager first).
Download the older release. If you're not familiar with github, expand the assets link under the release you want. The zip files will be listed there.
Make sure to remove the newer Magisk first.
spider1163 said:
Flashfire is discontinued so it is no longer compatible with the latest versions of Magisk
Click to expand...
Click to collapse
So is there solution that i can bypass that error ?
So, I rooted my phone (Samsung A41) with magisk patch to boot.img.
On samsung phones i've alway used this method to have magisk's root.
Then I always removed some system apps packages like com.facebook.* and com.microsoft.*
But this time I got a strange issue.
When deleting the application (com.facebook.services) the phone just rebooted.
I tried with everything (Titanium Backup, SDMaid and more) with no luck, they just come back after manual reboot or automatically reboot on removal phase.
Do you have any idea/help?
And another question, is there any twrp build for A41? I've found none official nor unofficial TWRP build for this phone and i don't know how to create one.
Thanks in advance
Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.
bitblocksplicer said:
Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.
Click to expand...
Click to collapse
Which ROM are you actually running?