Database Develop

After installing magisk, root not working

After installing the magisk as I was rooted, I installed 2-3 mods ie flashed in twrp but after I rebooted my root is gone. Magisk manager is showing not rooted and when I re flashed supersu in twrp, installation was successful but still no root. What happened I don't know. Also I didn't install any phh supersu or busybox. Please help me regain my root.
HELP

It was a known bug in Magisk that you would lose root.
Magisk
v10.2
- [Magic Mount] Remove apps/priv-app from whitelist, should fix all crashes
- [phh] Fix binary out-of-date issue
- [scripts] Fix root disappear issue when upgrading within Magisk Manager
Click to expand...
Click to collapse
So i'd make sure you flashed the latest version ? Pretty sure you have but if not might be worth flashing supersu then magisk over it again as it should recognise supersu and not modify it.

brichardson1991 said:
It was a known bug in Magisk that you would lose root.
So i'd make sure you flashed the latest version ? Pretty sure you have but if not might be worth flashing supersu then magisk over it again as it should recognise supersu and not modify it.
Click to expand...
Click to collapse
Yeah I just installed the latest version 10.2 via play Store. Help me regain my root

Vaibhunk786 said:
Yeah I just installed the latest version 10.2 via play Store. Help me regain my root
Click to expand...
Click to collapse
After installing from play store, did you "FLASH" magisk ?

brichardson1991 said:
After installing from play store, did you "FLASH" magisk ?
Click to expand...
Click to collapse
No I didn't flash anything. It was an automatic process which installed magisk and prompted me that installation success and reboot. Then I rebooted and root was gone

Now should I run magisk unstaller zip in twrp followed by supersu and then again flash magisk v10. 2 via twrp.. Should I follow these steps to gain my root again.. Anyone please help. I'm stuck @brichardson1991

Try installing PHH superuser from play store.

I had a similar experience. Having to reflash stock now to try a different tact. I'd rather use SuperSU to be honest, rather than PHH superuser.

Same problem here, have to investigate whats going on.

MattBooth said:
I had a similar experience. Having to reflash stock now to try a different tact. I'd rather use SuperSU to be honest, rather than PHH superuser.
Click to expand...
Click to collapse
yeah flashing the stock rom was the only viable option i think .

I have the same problem with latest magisk. After i installed mods root is gone and i can not root again. Only with supersu i have root. Magisk is very bugy.

Yeah it does appear the latest version now causes you to lose supersu

Same problem with me, on the OP3 running Open Beta 11. Reflashing SuperSU did not work. Rather than extract the boot.img to reflash that, I ended up reflashing the firmware (and ended up mistakenly using the 4.0.1 file instead of the OPB11 one!) ... Yet to try SuperSU and Magisk again on this, but figured better to investigate the issue before I attempt to reinstall.
From what I understand here, v10 won't have this problem, and its only on v11 that its cropped up again? Can anybody with v10 confirm this?

How to remove SuperSU after having installed Magisk?

So here's what I did:
I have my Galaxy S7 with Android 6, rooted with SuperSU.
Upgraded it to Android 7 using Smart Switch. Root is lost, of course.
Assumed SuperSU was gone, went ahead and rooted with Magisk.
After a bit of fiddling, because the guy can't write English, I had it working perfectly.
Restored a backup of all my apps. SuperSU got installed as well, since it was part of the backup. So I deleted it again (just the app).
Decided to do the SafetyNet test. Result: CTS profile mismatch. This is usally due to remnants of SuperSU. So I guess it wasn't removed fully.
Reinstalled the SuperSU app (just the app, I don't dare installing it via TWRP).
Open SuperSU, only to find out "SU binary is occupied". So I can't let SuperSU do its automated full unroot either.
My goal is to:
Get rid of SuperSU completely
Use Magisk instead
Pass the SafetyNet check
I have tried:
I ran the Magisk uninstaller to see if I can let SuperSU do its "full unroot" thing. But it results in a boot loop. So that's a no go.
I ran this SuperSU uninstaller script through TWRP, but it doesn't appear to have done anything. The results are unchanged either way.
So, what do I do now?

Try uninstalling the one you have (I assume it's the magisk v12), install magisk v13 beta, and see what you get. Also, about the safetynet, there are plenty of others reasons that may lead it to not pass, not only supersu.

thany2 said:
So here's what I did:
I have my Galaxy S7 with Android 6, rooted with SuperSU.
Upgraded it to Android 7 using Smart Switch. Root is lost, of course.
Assumed SuperSU was gone, went ahead and rooted with Magisk.
After a bit of fiddling, because the guy can't write English, I had it working perfectly.
Restored a backup of all my apps. SuperSU got installed as well, since it was part of the backup. So I deleted it again (just the app).
Decided to do the SafetyNet test. Result: CTS profile mismatch. This is usally due to remnants of SuperSU. So I guess it wasn't removed fully.
Reinstalled the SuperSU app (just the app, I don't dare installing it via TWRP).
Open SuperSU, only to find out "SU binary is occupied". So I can't let SuperSU do its automated full unroot either.
My goal is to:
Get rid of SuperSU completely
Use Magisk instead
Pass the SafetyNet check
I have tried:
I ran the Magisk uninstaller to see if I can let SuperSU do its "full unroot" thing. But it results in a boot loop. So that's a no go.
I ran this SuperSU uninstaller script through TWRP, but it doesn't appear to have done anything. The results are unchanged either way.
So, what do I do now?
Click to expand...
Click to collapse
I used the SuperSu android app. It has a full unroot (or was it uninstall?) option.
But I am on the op3. So not a 100% sure if that'll apply for the s7.
Sent from my ONEPLUS A3003 using Tapatalk

Dirty flash should remove all su or magisk, then you can install magisk again

abacate123 said:
Try uninstalling the one you have (I assume it's the magisk v12), install magisk v13 beta, and see what you get. Also, about the safetynet, there are plenty of others reasons that may lead it to not pass, not only supersu.
Click to expand...
Click to collapse
Uninstalling Magisk results in a boot loop, like I said. So it's a no-go.
What other reasons could it have when SafetyNet doesn't pass with that error message?
tropicanapure said:
I used the SuperSu android app. It has a full unroot (or was it uninstall?) option.
But I am on the op3. So not a 100% sure if that'll apply for the s7.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
SuperSU has that option greyed out because of a locked binary, like I said, so that won't solve anything.
adekboreanaz said:
Dirty flash should remove all su or magisk, then you can install magisk again
Click to expand...
Click to collapse
Sorry, I don't understand what "dirty flash" is supposed to mean. It sounds like a risk.

thany2 said:
Sorry, I don't understand what "dirty flash" is supposed to mean. It sounds like a risk.
Click to expand...
Click to collapse
No it is not, dirty flash is flashing your rom again without deleting /system /data partition, that can replace your boot.img with the stock one, so the supersu will be disappeared

reflash boot.img from the rom you used via twrp on img mode (click zip or img to switch between modes) or reflash your desired custom kernel.

After installing latest firmware Samsung S8 fault during installing magisk again

Hi there,
I had Magisk and the Magisk manager on my S8 but after installing the latest firmware for my S8 I can not install the Magisk.zip anymore. SU and TWRP are working fine though. Does anyone knows how get magisk again on my Phone?

I found it here: https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
With SuperSU, most of the times you can simply use the full unroot option in the SuperSU app and let it restore your stock boot image, alternatively use the full unroot option and then flash the stock boot image before installing Magisk.

Installed Magisk 19.3 using TWRP, seems not installed in Magisk Manager.

Hello,
I flashed a stock ROM on my Samsung Galaxy Tab S3 running Android 7.0.
Then I installed TWRP, and with that Magisk 19.3. All were installed successful, however after rebooting there was no Magisk Manager app, so I installed this myself.
When opening the Magisk Manager app it shows that Magisk has not been installed.. how can I fix this?
I've been trying for 10 hours now, I really need help.
Before flashing the ROM I had TWRP installed with SuperSU.

NeroDePero said:
Hello,
I flashed a stock ROM on my Samsung Galaxy Tab S3 running Android 7.0.
Then I installed TWRP, and with that Magisk 19.3. All were installed successful, however after rebooting there was no Magisk Manager app, so I installed this myself.
When opening the Magisk Manager app it shows that Magisk has not been installed.. how can I fix this?
I've been trying for 10 hours now, I really need help.
Before flashing the ROM I had TWRP installed with SuperSU.
Click to expand...
Click to collapse
1. Uninstall Super SU
2. Uninstall Magisk from TWRP (using uninstall.zip)
3. Install Magisk.zip latest version in TWRP
4. Install Magisk Manager latest version using APK
Remember to use both latest versions of Magisk (zip and apk).
It should work for you.
Sent from my SM-N960F via Tapatalk

zencooler said:
1. Uninstall Super SU
2. Uninstall Magisk from TWRP (using uninstall.zip)
3. Install Magisk.zip latest version in TWRP
4. Install Magisk Manager latest version using APK
Remember to use both latest versions of Magisk (zip and apk).
It should work for you.
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
The thing is, I did a full clean stock ROM install and there is no SuperSu app left on my device.
If I download the SuperSu APK now it says I don't have ROOT access and therefore I cannot uninstall SuperSu using the APK.
I have used Root Checker Basis (app) to check if there is a ROOT available, but it says ROOT access is not properly installed on this device.
Is it still possible for SuperSu to be installed on my device while I cannot see or find it? Even after a clean install?
Also, I believe 19.3 is the latest version of Magisk. I also tried 19.2, but I am having the same problem with that version.

NeroDePero said:
The thing is, I did a full clean stock ROM install and there is no SuperSu app left on my device.
If I download the SuperSu APK now it says I don't have ROOT access and therefore I cannot uninstall SuperSu using the APK.
I have used Root Checker Basis (app) to check if there is a ROOT available, but it says ROOT access is not properly installed on this device.
Is it still possible for SuperSu to be installed on my device while I cannot see or find it? Even after a clean install?
Also, I believe 19.3 is the latest version of Magisk. I also tried 19.2, but I am having the same problem with that version.
Click to expand...
Click to collapse
I don't know what the smartphone you have but the best way is to get boot.img from stock firmware and then patch it via Magisk Manager (you can install it even if you don't have root). Then after boot.img is patched you can flash it instead of the standard boot.img (any method you are doing it now).
BTW: the latest version of Magisk is 19.4. Check it on Magisk repository.
Sent from my SM-N960F via Tapatalk

zencooler said:
I don't know what the smartphone you have but the best way is to get boot.img from stock firmware and then patch it via Magisk Manager (you can install it even if you don't have root). Then after boot.img is patched you can flash it instead of the standard boot.img (any method you are doing it now).
BTW: the latest version of Magisk is 19.4. Check it on Magisk repository.
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
I am using a Samsung Galaxy Tab S3 (T825). I used a stock firmware from SamMobile (which exists of 5 times an .tar.md5 file) and flashed it on my device using Odin.
[EDIT] So here is what I did. Made a back-up using TWRP, and used that boot.img to patch in Magisk Manager.
Now I have a patched IMG file. But when I want to install it using TWRP I have to pick a partition and I am not sure which one to pick.
[EDIT] I tried installing it, and it was successful, yet shows the Magisk manager app that there is no ROOT available.
I guess I just need to start from the very beginning over again. Can you help me with that?
I have stock firmware .zip for my T825 from SamMobile which I can install using Odin.
I also have a working TWRP .zip file that works fine with that firmware on my device.
Other than that I'll need guidance because I keep screwing up :')
Your help is much appreciated

I did a factory reset, flashed TWRP, and installed Magisk using TWRP. After rebooting there was no Magisk Manager app (but it did install a TWRP app).
I installed the Manager app with a downloaded .apk (latest version) and it shows that Magisk is not installed.
So, I want to try patching my .img file using the manager app. The only problem is that I do not have an .img file, as I used . md5 files.
Can I make a back-up with TWRP and use the .img file from there?

changing from SuperSU to magisk?

Do I have to completely re-root or is there an easy way to switch from SuperSU to magisk?

spart0n said:
Do I have to completely re-root or is there an easy way to switch from SuperSU to magisk?
Click to expand...
Click to collapse
I am not 100% sure but, I think you should completely remove SU first as it will probably cause conflicts.
Not used SU for ages now but there should be a zip file you flash in TWRP to remove SU, then you can flash Magisk.

I never installed twrp so..... Yeah I should probably before I uninstall SuperSU