Hi. I've installed and used magisk. then I've repacked magisk manager to hide it. then it has gotten removed. Now I've reinstalled magisk manager but it is not detecting magisk. Other root app are working.
lordkian2000 said:
Hi. I've installed and used magisk. then I've repacked magisk manager to hide it. then it has gotten removed. Now I've reinstalled magisk manager but it is not detecting magisk. Other root app are working.
Click to expand...
Click to collapse
It isn't as simple as reinstalling, you might have to reverse the process of whatever you did to hide it.
Or, you can try going to system settings>applications>magisk manager and wipe the app's data and cache then reboot the device.
Or, a step further would be to boot into recovery and wipe only the cache partition(s). Factory reset is not required, just wiping cache should work if the issue is due to conflicting cached system data.
By the way, anytime you add/remove/modify anything in/to/from the system partition or any app that is a system app, it is always best to boot into recovery and wipe the cache partition to remove any conflicting cached system data from before the addition/removal/modification.
Sent from my SM-S767VL using Tapatalk
Related
Hi, I have a Samsung Admire and have been using Adfree perfectly fine before. However, after upgrading Android from 2.3.4 to 2.3.6 to fix the WIFI error, I can't seem to get Adfree to work again.
I get the following error message when trying to install the Hosts:
java.io.IOException: Error running exec(). Command: [su] Working Directory: null Environment: null
How do I get this app to work again?
Uninstall & reinstall. Try to clear cache & dalvik cache in recovery. Worst case scenario, I think, is to wipe everything and install from scratch.
post-mortem said:
Uninstall & reinstall. Try to clear cache & dalvik cache in recovery. Worst case scenario, I think, is to wipe everything and install from scratch.
Click to expand...
Click to collapse
I tried uninstalling, reinstalling, and wiping cache in recovery before, but to no avail. I didn't try wiping dalvik cache before. After uninstalling, wiping out cache and dalvik cache in recovery, and reinstalling, the error is still there.
I am not sure what you mean by "wipe everything and install from scratch". I would understand how to do that if it was on my PC, but not on my smartphone.
By that I meant, as a last-resort option, to completely wipe everything as if you're gonna flash a new ROM. Format everything through recovery, flash ROM, kernel (if applicable), gapps, whatever else. Then set up your google acct. & restore apps from titanium backup, or reinstall all apps from scratch.
BTW, you shouldn't restore Adfree, it should definitely be installed fresh from Google Play.
post-mortem said:
By that I meant, as a last-resort option, to completely wipe everything as if you're gonna flash a new ROM. Format everything through recovery, flash ROM, kernel (if applicable), gapps, whatever else. Then set up your google acct. & restore apps from titanium backup, or reinstall all apps from scratch.
BTW, you shouldn't restore Adfree, it should definitely be installed fresh from Google Play.
Click to expand...
Click to collapse
As much as I would like to give your method a try, it seems too complicated to do. First of all, I never format my phone before. Even though I know how to format a PC, doing the same thing on the phone seems to be new and unfamiliar to me.
Second of all, it seems to be quite a lot of troubles just to fix that error. I wonder if there is a manual method of removing the ads.
Ok, just to be sure you don't have a problem with su, go into the Superuser app, check for updates, and force an update even if there's no new version (it also makes sure the file has the proper permissions).
post-mortem said:
Ok, just to be sure you don't have a problem with su, go into the Superuser app, check for updates, and force an update even if there's no new version (it also makes sure the file has the proper permissions).
Click to expand...
Click to collapse
Yay! That was the problem. Thank you so much! Wow, AdFree app didn't get rid of most of the ads as it used to, but oh, well...it is better than nothing.
I want to switch from supersu to superuser, and having an interesting problem that supersu somehow covered up. I have a Nexus 5x running the stock rom. With every months upgrade I would flash using fastboot, go into twrp recovery before first full boot and remove a bunch of unneeded applications in /system/app. When I would boot up those applications would be gone. Somehow this isn't the case with superuser. I can still go into recovery and remove them, but when I boot up all the applications are still in /system/app. If I go back into twrp they are still shown as being missing. I've tried installing es file explorer, but it's unable to delete the applications once the system is up. remounting /system doesn't work either. Any help?
Unrooting supersu caused all the applications to come back; so does supersu not really delete them either, but somehow prevents them from showing up following the recovery scheme or something?
bsd1101 said:
I want to switch from supersu to superuser, and having an interesting problem that supersu somehow covered up. I have a Nexus 5x running the stock rom. With every months upgrade I would flash using fastboot, go into twrp recovery before first full boot and remove a bunch of unneeded applications in /system/app. When I would boot up those applications would be gone. Somehow this isn't the case with superuser. I can still go into recovery and remove them, but when I boot up all the applications are still in /system/app. If I go back into twrp they are still shown as being missing. I've tried installing es file explorer, but it's unable to delete the applications once the system is up. remounting /system doesn't work either. Any help?
Unrooting supersu caused all the applications to come back; so does supersu not really delete them either, but somehow prevents them from showing up following the recovery scheme or something?
Click to expand...
Click to collapse
You aren't doing something right or you don't have something setup correctly. With root, you should be able to unintelligible them completely.
When you removed them, did you wipe cache and dalvik/ART cache before rebooting? If not then the system probably still thinks they are there because they still have data loaded into cache.
I recommend sticking with SuperSU, superuser doesn't work as well as SuperSU
Sent from my SM-S903VL using Tapatalk
I've been googling a bit more. As it turns out there are two system partitions for nougat; in nexus 5x and some other devices apparently. This became more apparent when the file recovery-from-boot.p; which I rename in order to prevent recovery from being overwritten is not renamed when booting the OS. Nougat apparently pulls the system files from somewhere else. So whatever Chainfire did makes it boot the same partition as visible in recovery. Fully unrooting brings all those apps/system partition back. Haven't been able to find a good post that tells me how to to circumvent this without SuperSU; or exactly how this works.
I have tried rooting using both Magisk and Supersu. I've not had luck passing safety net checks. I've uninstalled Magisk. The specific problem I'm having is that I'm trying to remove all the supersu files. When I get into recover mode using twrp, I can see a /supersu folder. I delete it, or at least it acts like it deletes it but when I reboot into recovery, it's still there. When I use a root explorer app, the folder is nowhere to be found.
rwmappraisal said:
I have tried rooting using both Magisk and Supersu. I've not had luck passing safety net checks. I've uninstalled Magisk. The specific problem I'm having is that I'm trying to remove all the supersu files. When I get into recover mode using twrp, I can see a /supersu folder. I delete it, or at least it acts like it deletes it but when I reboot into recovery, it's still there. When I use a root explorer app, the folder is nowhere to be found.
Click to expand...
Click to collapse
Have you wiped cache after removing the supersu files? Any time you remove apps/files from /system, you have to wipe cache and/or Dalvik/ART cache or it thinks it's still there when it isn't.
Why didn't you just use SuperSU's app settings to unroot and uninstall SuperSU then use Magisk?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
use the unsu script and flash a unrooted boot.img from your rom
Try kingroot
Sent from my SHV-E210S using Tapatalk
I uninstalled Google Playstore using ES file explorer's root uninstaller and rebooted my phone. Then I reinstalled Google Playstore with an apk file (now shown as user app. The re-installation was success but the app keeps crashing after I tried to download an app with it.
I uninstalled Google Playstore in the first place because I encountered the "waiting for download" bug (apps stuck on that messages without downloading at all).
I cannot flash GApps in TWRP because it says /system partition not found.
I'm using Rooted Asus ROG phone, stock ROM 15.1630.1903.89, magisk
Please help
GphonePrince said:
I uninstalled Google Playstore using ES file explorer's root uninstaller and rebooted my phone. Then I reinstalled Google Playstore with an apk file (now shown as user app. The re-installation was success but the app keeps crashing after I tried to download an app with it.
I uninstalled Google Playstore in the first place because I encountered the "waiting for download" bug (apps stuck on that messages without downloading at all).
I cannot flash GApps in TWRP because it says /system partition not found.
I'm using Rooted Asus ROG phone, stock ROM 15.1630.1903.89, magisk
Please help
Click to expand...
Click to collapse
Anytime you uninstall/remove system files and apps or anytime you reinstall/replace system files and apps, it is best to boot into recovery then wipe cache and dalvik cache then reboot. The reason why this must be done is because when you remove/add stuff from/to system, the OS is looking for stuff that is there when it shouldn't be or is not finding stuff that should be there but isnt.
Wiping cache and dalvik then rebooting allows the device to rebuild cache as it should be for what is currently in system.
The most effective fix with the least possible issues in your situation is to reflash your stock firmware then flash TWRP on the device again then root the device again using Magisk.
Next time, before you add/remove system files/apps, boot into TWRP and create a nandroid backup of your current ROM, then, if you encounter issues when you add/remove system files/apps, you can boot into TWRP and restore the backup and you'll be restored to exactly what you had before you added/removed the system files/apps.
The ability to create and restore backups via TWRP is the main purpose for using TWRP, the ability to flash ROMs and such is a minor secondary feature or purpose of TWRP.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Anytime you uninstall/remove system files and apps or anytime you reinstall/replace system files and apps, it is best to boot into recovery then wipe cache and dalvik cache then reboot. The reason why this must be done is because when you remove/add stuff from/to system, the OS is looking for stuff that is there when it shouldn't be or is not finding stuff that should be there but isnt.
Wiping cache and dalvik then rebooting allows the device to rebuild cache as it should be for what is currently in system.
The most effective fix with the least possible issues in your situation is to reflash your stock firmware then flash TWRP on the device again then root the device again using Magisk.
Next time, before you add/remove system files/apps, boot into TWRP and create a nandroid backup of your current ROM, then, if you encounter issues when you add/remove system files/apps, you can boot into TWRP and restore the backup and you'll be restored to exactly what you had before you added/removed the system files/apps.
The ability to create and restore backups via TWRP is the main purpose for using TWRP, the ability to flash ROMs and such is a minor secondary feature or purpose of TWRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the detailed reply. I have re-flashed the stock ROM and re-rooted the phone now.
Now, I am just wondering why I am still encountering the "/system partition not mounted" error in TWRP for both (now and the previous time) rooting procedures? This prevents me from installing busybox and flash anything with TWRP.
PS: I am following the rooting guide here, since it is the most detailed one for newbies like myself. According the the screenshots shown in this guide, the OP also encountered the "/system partition not mounted" error in TWRP (system shown as 0MB, and before booting to system with TWRP, the message "no OS found" appeared). Hence I suspect his guide was not perfect despite getting root successfully. Mind having a look at the guide for me to see whether you could spot any missing/wrong steps please? (I know it is in Chinese but it does have loads of screenshots) I would really appreciate it. Thanks so much!
GphonePrince said:
Thanks for the detailed reply. I have re-flashed the stock ROM and re-rooted the phone now.
Now, I am just wondering why I am still encountering the "/system partition not mounted" error in TWRP for both (now and the previous time) rooting procedures? This prevents me from installing busybox and flash anything with TWRP.
PS: I am following the rooting guide here, since it is the most detailed one for newbies like myself. According the the screenshots shown in this guide, the OP also encountered the "/system partition not mounted" error in TWRP (system shown as 0MB, and before booting to system with TWRP, the message "no OS found" appeared). Hence I suspect his guide was not perfect despite getting root successfully. Mind having a look at the guide for me to see whether you could spot any missing/wrong steps please? (I know it is in Chinese but it does have loads of screenshots) I would really appreciate it. Thanks so much!
Click to expand...
Click to collapse
Is your device an A/B partition device?
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Is your device an A/B partition device?
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
It's Asus ROG phone. seems like it is according to here: https://www.xda-developers.com/list-android-devices-seamless-updates/
GphonePrince said:
It's Asus ROG phone. seems like it is according to here: https://www.xda-developers.com/list-android-devices-seamless-updates/
Click to expand...
Click to collapse
That is the problem then, the process of rooting and flashing TWRP on A/B devices is very much different than how it is done on other non A/B devices.
Look for instructions on how to use TWRP on devices that have A/B partitions.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
That is the problem then, the process of rooting and flashing TWRP on A/B devices is very much different than how it is done on other non A/B devices.
Look for instructions on how to use TWRP on devices that have A/B partitions.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I will look into it thanks
after updating to pie some of my apps (Google photos, xda labs, edxposed manager) can't save files. other apps (like Chrome) can save files without issue. I've checked and all of them have storage permissions on.
I've tried uninstalling magisk and edxposed and neither helped.
I'm not sure what else to do other than a factory reset, which I'd like to avoid.
if I can't get this fixed can I downgrade back to oreo?
You have to wipe data in TWRP
That's how I've solved this same problem
brashmadcap said:
You have to wipe data in TWRP
That's how I've solved this same problem
Click to expand...
Click to collapse
i did that and now i keep rebooting to twrp :/
edit: fixed that by restoring a backup (i'm an idiot and forgot to turn off passcode) but i'm still having issues