Database Develop

How to reset/erase Magisk configuration?

I was using Resurrection Remix 5.8.2 with Magisk v12 without problems, until I tried to pass the SafetyNET check. I read that "you have to enable Busybox", etc... and I did it in my phone. After restarting I've lost all the Magisk config and I can't find the options to rollback my changes:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried to wipe the data and cache of Magisk Manager in Settings ==> Apps ==> Magisk Manager. Reboot. Everything it's unchanged.
I've tried to wipe Cache and Dalvik & Cache from recovery. Reboot. Everything it's unchanged.
I've tried to unistall (with the Magisk uninstaller zip), reboot, wipe Cache and Dalvik & Cache from recovery. Reboot. Again in recovery flashed the Magisk v12 install zip, reboot and everything it's unchanged.
What should I do to reset/erase the Magisk configuration so I can start over from scratch?

ochoceros said:
I was using Resurrection Remix 5.8.2 with Magisk v12 without problems, until I tried to pass the SafetyNET check. I read that "you have to enable Busybox", etc... and I did it in my phone. After restarting I've lost all the Magisk config and I can't find the options to rollback my changes:
I've tried to wipe the data and cache of Magisk Manager in Settings ==> Apps ==> Magisk Manager. Reboot. Everything it's unchanged.
I've tried to wipe Cache and Dalvik & Cache from recovery. Reboot. Everything it's unchanged.
I've tried to unistall (with the Magisk uninstaller zip), reboot, wipe Cache and Dalvik & Cache from recovery. Reboot. Again in recovery flashed the Magisk v12 install zip, reboot and everything it's unchanged.
What should I do to reset/erase the Magisk configuration so I can start over from scratch?
Click to expand...
Click to collapse
Uninstall MagiskManager, then uninstall magisk. If it still fails, reflash your rom

veez21 said:
Uninstall MagiskManager, then uninstall magisk. If it still fails, reflash your rom
Click to expand...
Click to collapse
Thanks for pointing in the right direction. I've installed previously the Magisk Manager from the Playstore, but in the last version of the ROM Magisk Manager is included into Settings.
When I disabled it in Settings ==> Apps, it asked to revert to the ROM version, and I did it.
Then rebooted in recovery, flashed the uninstaller, reboot, reflashed the ROM again and everything is working.
Thanks a lot!

Didn't work for me
I tried your way and also the uninstall option in the app. Tried with disabled app (as you did) but nothing. When I open a particular app it tells that i cannot login cause my device is rooted. (Magisk Hide doesn't work)

Nucio said:
I tried your way and also the uninstall option in the app. Tried with disabled app (as you did) but nothing. When I open a particular app it tells that i cannot login cause my device is rooted. (Magisk Hide doesn't work)
Click to expand...
Click to collapse
That wasn't my problem. My problem was related to restore the original settings after a misconfiguration of Magisk. Your problem is to hide root to an app. Try to search another thread because this isn't related at all.

Xposed framework not working on my Oneplus 5, Ressurection Remix V 5.8.4

I rooted my device,
And Installed the xposed application,
where I flashed the "sdk25 arm64" zip file.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I open for let's say Snapprefs, It tells me the module is not activated
I activated the module and rebooted,
any help?

Jonathanve said:
I rooted my device,
And Installed the xposed application,
where I flashed the "sdk25 arm64" zip file.
If I open for let's say Snapprefs, It tells me the module is not activated
I activated the module and rebooted,
any help?
Click to expand...
Click to collapse
Your problem is probably the same we encounter in stock OOS of OP5.
Try this:
boot the phone, and then do a soft reboot.
This happens because of file encryption prevents xposed from access the module list in /data/ partition at boot (because files are encrypted, meaning you haven't enter your pass/pin, when xposed tries to read them).
If you do a soft reboot (the option is available in the framework screen), then it will work.

fjsferreira said:
Your problem is probably the same we encounter in stock OOS of OP5.
Try this:
boot the phone, and then do a soft reboot.
This happens because of file encryption prevents xposed from access the module list in /data/ partition at boot (because files are encrypted, meaning you haven't enter your pass/pin, when xposed tries to read them).
If you do a soft reboot (the option is available in the framework screen), then it will work.
Click to expand...
Click to collapse
I noticed that it tells me my phone is encrypted, any idea how to decrypt?
I tryed formatting data and reinstalling the ROM,
It seems it's encrypted by standard

fjsferreira said:
Your problem is probably the same we encounter in stock OOS of OP5.
Try this:
boot the phone, and then do a soft reboot.
This happens because of file encryption prevents xposed from access the module list in /data/ partition at boot (because files are encrypted, meaning you haven't enter your pass/pin, when xposed tries to read them).
If you do a soft reboot (the option is available in the framework screen), then it will work.
Click to expand...
Click to collapse
Hello, I want to confirm that this was a temporary solution, It seems like soft rebooting device made it work,
thanks

I also use OP5 on stock Oxygen OS 4.5.10, Magisk 14 and systemless xposed 87.3 by topjohnwu. I have the same problem but it doesn't get fixed even if I soft reboot through the Material Xposed Installer app. What exactly am I supposed to do?
Στάλθηκε από το ONEPLUS A5000 μου χρησιμοποιώντας Tapatalk

Jonathanve said:
I noticed that it tells me my phone is encrypted, any idea how to decrypt?
I tryed formatting data and reinstalling the ROM,
It seems it's encrypted by standard
Click to expand...
Click to collapse
To decrypt you need to format data in TWRP then install a kernel that does not force encryption.

Face_Plant said:
To decrypt you need to format data in TWRP then install a kernel that does not force encryption.
Click to expand...
Click to collapse
Or you can run with FDE with: https://forum.xda-developers.com/showthread.php?t=3672477
You will lose the ability to boot unattended, so alarm when phone is off and scheduled boot won't work. And you'll have to format data too...
It's worth the inconvenience in my opinion. Been running this way for several days without any issues.
Full disclosure: I wrote the FDE conversion utility linked above.

Help-me Please

I used a magisk option to rename / hide it, and ended up losing root, tried to root, but to no avail, magisk manager no longer has the modules, magisk hide, or supersu option. Can someone help me ?

Simply uninstall the Manager and then reinstall it manually (apk in the Magisk zip or from @topjohnwu's Github.

Didgeridoohan said:
Simply uninstall the Manager and then reinstall it manually (apk in the Magisk zip or from @topjohnwu's Github.
Click to expand...
Click to collapse
already tried, and already tried to root again, the process happens without fail, but when you check this without
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

danyfenton said:
already tried, and already tried to root again, the process happens without fail, but when you check this without
Click to expand...
Click to collapse
Do you happen to have a second Magisk Manager in your app drawer, just named "Manager"? If so, that's likely the currently, by Magisk, recognised Manager. Uninstall both managers and try again.
If that doesn't help, you're going to have to start being more detailed:
https://didgeridoohan.com/magisk/MagiskHelp

Didgeridoohan said:
Do you happen to have a second Magisk Manager in your app drawer, just named "Manager"? If so, that's likely the currently, by Magisk, recognised Manager. Uninstall both managers and try again.
If that doesn't help, you're going to have to start being more detailed:
https://didgeridoohan.com/magisk/MagiskHelp
Click to expand...
Click to collapse
Yes, I had the manager, I also uninstalled and redo the installation, and without success.
Things I've already done:
- I uninstalled Manager.apk, and reinstalled Magisk
- Redo Root using TWRP.
- I uninstalled Magisk from TWRP via MagiskUnistall.rar file
- Installed Previous Versions of Magisk, like 17.1; 18.1; 19.4 (Beta).
and still unsuccessful, magisk looks like the image I posted above. Worst of all was that I lost root, and even trying to redo the root procedures, does not come back.
I am using google translator, I apologize if the understanding is not so good.

It's really hard to do any kind of support on this... I would start from scratch.
Uninstall any Managers that are installed, run the Magisk uninstaller (or @osm0sis unSU script) and just for good measure restore your ROM's stock boot image as well. Once that's done, try again. And make sure to save logs according to my previously posted link.

when I try to install from magisk itself, this error appears.

Didgeridoohan said:
It's really hard to do any kind of support on this... I would start from scratch.
Uninstall any Managers that are installed, run the Magisk uninstaller (or @osm0sis unSU script) and just for good measure restore your ROM's stock boot image as well. Once that's done, try again. And make sure to save logs according to my previously posted link.
Click to expand...
Click to collapse
OK, when I get home from work I'll try, thanks.

Didgeridoohan said:
It's really hard to do any kind of support on this... I would start from scratch.
Uninstall any Managers that are installed, run the Magisk uninstaller (or @osm0sis unSU script) and just for good measure restore your ROM's stock boot image as well. Once that's done, try again. And make sure to save logs according to my previously posted link.
Click to expand...
Click to collapse
unsuccessful when using unSU.
succeeded in using it on twrp, restarted the phone, and went back to TWRP, and redid the process, and to no avail.

Didgeridoohan said:
It's really hard to do any kind of support on this... I would start from scratch.
Uninstall any Managers that are installed, run the Magisk uninstaller (or @osm0sis unSU script) and just for good measure restore your ROM's stock boot image as well. Once that's done, try again. And make sure to save logs according to my previously posted link.
Click to expand...
Click to collapse
- Device platform: armeabi-v7a
- Copying image to cache
1022+1 records in
1022+1 records out
1047368 bytes transferred in 0.016 secs (65460500 bytes/sec)
- Unpacking boot image
Parsing boot image: [/mnt/expand/20683188-08c0-4603-a521-de6372bd2a29/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed

danyfenton said:
unsuccessful when using unSU.
succeeded in using it on twrp, restarted the phone, and went back to TWRP, and redid the process, and to no avail.
Click to expand...
Click to collapse
Didgeridoohan said:
Do you happen to have a second Magisk Manager in your app drawer, just named "Manager"? If so, that's likely the currently, by Magisk, recognised Manager. Uninstall both managers and try again.
If that doesn't help, you're going to have to start being more detailed:
https://didgeridoohan.com/magisk/MagiskHelp
Click to expand...
Click to collapse
I got it, I formatted the phone and redid the whole process. Thanks for the force friend.

danyfenton said:
I got it, I formatted the phone and redid the whole process. Thanks for the force friend.
Click to expand...
Click to collapse
I was just about to come in here and reply to your other message, and I find you got it sorted. Nice.
All I did was point the way, you're the one who fixed it in the end. :good:

Didgeridoohan said:
I was just about to come in here and reply to your other message, and I find you got it sorted. Nice.
All I did was point the way, you're the one who fixed it in the end. :good:
Click to expand...
Click to collapse
thank you for being willing to help, really.

[Discussion] OP8Pro - magisk notification lead to unresponsive manager

Anyone else ever have it happen where you get a magisk update prompt, thought you swiped it away only to have accidentally tapped it? It installed something. But my magisk manager stopped responding. After trying to open it a few times, my 8pro rebooted. I had to install magiskv23.apk because my manager wasn't loading and it was renamed through the magisk app (I had to rename it because I had a couple apps that saw Magisk and wouldn't load). Now I'm stuck without root, and without a stock boot image for open beta 12. Pain in the rear situation. BUT TiBu still recognizes root access. So does terminal emulator when I type su. I get a pop up that MagixMgr isn't responding. Not even sure how to get out of this situation, since I don't have twrp..

If your talking about OB1 ColorOS12, you can download the OTA.zip for it, and extract the payload.bin file from the zip using 7zip (or similar). Run the payload.bin through the payload dumper tool to get the boot.img. Than patch that and flash it.

No, I'm on open beta 12. Still oxygen OS. I extracted my boot images through terminal emulator since I still have root. Patched those with magisk 23 apk. Just have to try flashing them. But I don't think that's my issue since I still have root. The magisk manager is broken, and if I install a different magisk apk, it doesn't recognize that I have magisk installed, or root.

mattgyver said:
No, I'm on open beta 12. Still oxygen OS. I extracted my boot images through terminal emulator since I still have root. Patched those with magisk 23 apk. Just have to try flashing them. But I don't think that's my issue since I still have root. The magisk manager is broken, and if I install a different magisk apk, it doesn't recognize that I have magisk installed, or root.
Click to expand...
Click to collapse
Where is open beta for oxygen os 12 on 8 pro? There were no news or release of an oos 12 ob...

@gsser It's not OOS 12. Open beta 12 is OOS 11. And it's been available since end of July.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I thought maybe reinstalling a patched boot image would help. Extracted my boot image, patched it in Magisk 23 apk. Flashed it in fastboot. Nada. Magisk 23 doesn't recognize magisk installed. my magisk app that was renamed through it's own UI still is failing to respond. Titanium Backup, Terminal Emulator, and Solid Explorer still all have retained root access.
I guess technically I'm fine, but I can't make changes to my modules, magiskHide apps, and I'm not sure if trying to upgrade to Magisk 24.1 apk will cause issues when upgrading my Magisk install.
What's interesting is that the magisk apk that my manager tried downloading was saved as Magisk-(-1).apk instead of any version numbering. it was only 280KB in size, compared to a few MB. and if I try manually installing it, it fails to parse the package.
Update1: so I flashed the official twrp beta. Downloaded the twrp app, and it never prompts about root permission, so it can't find my recovery. I don't get a prompt about MagixMgr not responding this time. So I can't grant any new apps root access.
Update2: apparently this has killed my wifi, too. I can't get the oneplus 8 pro to start wifi. it acts like it's starting, but if I swipe away the notification shade, and bring it back down, wifi is off again. i don't want to factory reset my phone, but I have this funny feeling that it's going to be my only option....
Update3: Uninstalled my magisk proxy app. pulled the full OTA OOS11 OB12 zip file and extracted payload.bin on my linux box. patched with magisk 24.1. flashed stock boot, and stock recovery to both a/b slots. then flashed magisk patched stock boot image instead of the one that I had pulled from my phone. success. Magisk 24.1 shows as installed, and I have full superuser access again. and a few more gray hairs. but all is well, even if I wasn't too sure about upgrading to the new magisk and losing magiskHide. but I'll look into the new modules being developed...

[Discussion] OP8Pro - magisk notification lead to unresponsive manager

Anyone else ever have it happen where you get a magisk update prompt, thought you swiped it away only to have accidentally tapped it? It installed something. But my magisk manager stopped responding. After trying to open it a few times, my 8pro rebooted. I had to install magiskv23.apk because my manager wasn't loading and it was renamed through the magisk app (I had to rename it because I had a couple apps that saw Magisk and wouldn't load). Now I'm stuck without root, and without a stock boot image for open beta 12. Pain in the rear situation. BUT TiBu still recognizes root access. So does terminal emulator when I type su. I get a pop up that MagixMgr isn't responding. Not even sure how to get out of this situation, since I don't have twrp..

If your talking about OB1 ColorOS12, you can download the OTA.zip for it, and extract the payload.bin file from the zip using 7zip (or similar). Run the payload.bin through the payload dumper tool to get the boot.img. Than patch that and flash it.

No, I'm on open beta 12. Still oxygen OS. I extracted my boot images through terminal emulator since I still have root. Patched those with magisk 23 apk. Just have to try flashing them. But I don't think that's my issue since I still have root. The magisk manager is broken, and if I install a different magisk apk, it doesn't recognize that I have magisk installed, or root.

mattgyver said:
No, I'm on open beta 12. Still oxygen OS. I extracted my boot images through terminal emulator since I still have root. Patched those with magisk 23 apk. Just have to try flashing them. But I don't think that's my issue since I still have root. The magisk manager is broken, and if I install a different magisk apk, it doesn't recognize that I have magisk installed, or root.
Click to expand...
Click to collapse
Where is open beta for oxygen os 12 on 8 pro? There were no news or release of an oos 12 ob...

@gsser It's not OOS 12. Open beta 12 is OOS 11. And it's been available since end of July.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I thought maybe reinstalling a patched boot image would help. Extracted my boot image, patched it in Magisk 23 apk. Flashed it in fastboot. Nada. Magisk 23 doesn't recognize magisk installed. my magisk app that was renamed through it's own UI still is failing to respond. Titanium Backup, Terminal Emulator, and Solid Explorer still all have retained root access.
I guess technically I'm fine, but I can't make changes to my modules, magiskHide apps, and I'm not sure if trying to upgrade to Magisk 24.1 apk will cause issues when upgrading my Magisk install.
What's interesting is that the magisk apk that my manager tried downloading was saved as Magisk-(-1).apk instead of any version numbering. it was only 280KB in size, compared to a few MB. and if I try manually installing it, it fails to parse the package.
Update1: so I flashed the official twrp beta. Downloaded the twrp app, and it never prompts about root permission, so it can't find my recovery. I don't get a prompt about MagixMgr not responding this time. So I can't grant any new apps root access.
Update2: apparently this has killed my wifi, too. I can't get the oneplus 8 pro to start wifi. it acts like it's starting, but if I swipe away the notification shade, and bring it back down, wifi is off again. i don't want to factory reset my phone, but I have this funny feeling that it's going to be my only option....
Update3: Uninstalled my magisk proxy app. pulled the full OTA OOS11 OB12 zip file and extracted payload.bin on my linux box. patched with magisk 24.1. flashed stock boot, and stock recovery to both a/b slots. then flashed magisk patched stock boot image instead of the one that I had pulled from my phone. success. Magisk 24.1 shows as installed, and I have full superuser access again. and a few more gray hairs. but all is well, even if I wasn't too sure about upgrading to the new magisk and losing magiskHide. but I'll look into the new modules being developed...