Database Develop

Magisk 11.1 and ViperOne M9 ROM issues - lost root

Hi guys - I'm having trouble with the latest version of Magisk...
My ROM - ViperOne M9 (for HTC One M9) - comes packaged with Magisk 10.6 and phh's Superuser, and it seems to work ok out of the box. However, I can't get it to pass SafetyNet checks with HideMagisk enabled, which is an annoyance as I can't use certain apps (no, NOT Pokemon GO FYI ). The Magisk Manager was advising to update itself, which I thought might help - so I did. After a reboot I have now lost root on my device, and cannot get it back.
A knock-on effect seems to have taken out phh's Superuser too, as it now complains of out-of-date binaries when the phone boots up, and I'm not getting any permission requests any more. I tried revoking Magisk's permissions, but it never tried requesting them again.
I flashed the phone using the latest TWRP, and my firmware and bootloaders are up to date also.
Not sure whats going on here - any ideas?
I could re-flash the phone, as I did a complete wipe earlier today to update ViperOne to the latest version (version 6.00) - so it's not a major headache, and should give me root back. But then I'm back to a broken hide-root/SN bypass. Again, this isnt a major problem since I'm used to not using those apps - but it would be nice to have.
Cheers.

Guys, managed to resolve my problem.
I downloaded the latest ZIP for Magisk 11.6 and phh Superuser, and flashed using TWRP. Rebooted, and all working!!

Also FWIW, I solved the problem with SN failing.... well I installed Magisk 11.6 and the work you guys did obviously did it for me, so thank you!

[Q?] Android Pay 7.1.x ROM with working root?

Hello, What is the rom with working android pay?
Pure Nexus - Doesnt work with magisk
Lineage doesnt work at all - rooted or not
Dirty Unicorns works, however apps crash.
Trying nitrogen os now
Any advice?
Thanks

.me said:
Hello, What is the rom with working android pay?
Pure Nexus - Doesnt work with magisk
Lineage doesnt work at all - rooted or not
Dirty Unicorns works, however apps crash.
Trying nitrogen os now
Any advice?
Thanks
Click to expand...
Click to collapse
Works for me with PureNexus and Magisk v12. Just make sure you turn on Magisk Hide.

liquidzoo said:
Works for me with PureNexus and Magisk v12. Just make sure you turn on Magisk Hide.
Click to expand...
Click to collapse
Tried a couple of times - worked with 11.x
I have no idea what I am doing wrong.

On latest Lineage with Franco Kernel + Magisk and passing safetynet. I have my card set up successfully with Android Pay but I haven't had a chance to actually test it, but I am definitely passing SN. Netflix shows up on Play Store as well.
I did a complete wipe, installed Lineage + Gapps, booted phone, then shut down phone and installed Franco Kernel, booted, shut down and then installed Magisk. I kept booting after flashes to check if Safetynet was being passed. It was not until I installed Magisk and used Magisk hide.

Google Strock Rom + ElementalX Kernel + Magisk 12.0 with suhide also works

.me said:
Tried a couple of times - worked with 11.x
I have no idea what I am doing wrong.
Click to expand...
Click to collapse
Don't enable Magisk busybox on Pure Nexus. There'll be a conflict with the ROM's busybox and it breaks Magisk Hide.
Because of issues like this (and others), busybox will no longer be included in Magisk starting with the next version.

Didgeridoohan said:
Don't enable Magisk busybox on Pure Nexus.
Click to expand...
Click to collapse
^This! Can confirm and I am running PN with Magisk, Android Pay works, Netflix appears in Playstore.

I've been using Android Pay with Pure Nexus & magisk for the past several months w/o any issues.

Didgeridoohan said:
Don't enable Magisk busybox on Pure Nexus. There'll be a conflict with the ROM's busybox and it breaks Magisk Hide.
Because of issues like this (and others), busybox will no longer be included in Magisk starting with the next version.
Click to expand...
Click to collapse
Thanks - I am beta testing v13 - hopefully it will work.
Cheers

Works with Dirty Unicorns / Magisk 12 .... I've noticed some form of weird volume issue where my volume lowers to reallllly low levels... so I'm looking for another ROM where it works and that has SmartBar Navigation customization.

Using PN latest ROM, with Magisk Hide enabled. Never had any problems, because it passes safety net every time

[Q] Can't really activate any modules

Hi all,
I have a problem. I'm using an OnePlus 5 and I can't use Xposed. I have just tried those 2 things. I have magisk updated to 14.0
1) I installed the version 09-09-2017 by dvdandroid, then I installed 26-07-17 v87 sdk25 by PurifyOs, all seems OK xposed tells that is installed and working, so I try to download some modules, activate them, reboot, but when I try to use them they tell me "please activate the module", I tryed clearing cache and dalvik, reinstalling so many times but nothing.
2) So I removed the PurifyOs one, and wanted to try to install the systemless one. I open Xposed, press install, it auto flashes from TWRP but there is a message error "dev/magisk/mirror/bin is not setup properly". So I try to download it as a module from magisk, try to install but gives the same error.
Can you help me? Thanks

Up...

Up...

Uppppppppp

Having the same issue on Oneplus 5 running android 7.1.1.
Any solutions?

Up....

same issue oneplus 3t stock

Uppppp

I couldn't activate any modules either, even though framework was green/good.
I re-installed my ROM and re-did the Xposed setup, ensuring I was using the CORRECT files.
Such as for Magisk Xposed vs. non-Magisk Xposed.
It's working now.

CZ Eddie said:
I couldn't activate any modules either, even though framework was green/good.
I re-installed my ROM and re-did the Xposed setup, ensuring I was using the CORRECT files.
Such as for Magisk Xposed vs. non-Magisk Xposed.
It's working now.
Click to expand...
Click to collapse
Thanks for your answer, I already did but nothing changed..

If ur on oos with encryption, you need to soft reboot the phone before the modules work.

8monochrome said:
If ur on oos with encryption, you need to soft reboot the phone before the modules work.
Click to expand...
Click to collapse
Already tried, nothing happened

I'm not sure how the OnePlus works in comparison to my Moto G4, but I had the same problem with 7.1.x. I couldn't get Xposed to work on any roms running Nougat. Went and installed an AOSP marshmallow rom and Xposed is working very well. My advice would be to downgrade to marshmallow. It's definitely worth the Xposed compatibility because even if you do get that aspect of it going, many modules don't support nougat yet. I was reluctant when I first heard this, but I' don't regret my decision at all. I'm running 12 modules right now with no issues at all and loving it. Hope this helps.

Backward switching magisk 19 (beta) -> 18 (stable) caused problem.

[Problem]
I noticed google pay not working after enjoying magisk happily for two days.
[Research]
I searched the forum and found many others have issue with google pay, too.
[Trial]
I started to do something with the hope to solve this problem.
1. I changed the update channel to beta test and installed magisk v19. Google pay was not working.
2. I then changed back to stable update channel to install magisk v18. Strange thing happened.
3. Phone booted fine but magisk manager detected no trace of magisk. I re-flashed patched_boot.img. Same thing, magisk was gone.
4. I am on stock ROM (S6 edge) and installed magisk by patching boot.img. I had no TWRP recovery. I could not do much under this circumstance.
5. So, I was in a situation of missing magisk and disabled google pay.
[Final]
I flashed the stock ROM via odin.
1. The google pay was working again in stock ROM (without root).
2. I lost magisk (and root).
I will install magisk again if google pay can work with it. The problem is the security check by google. I still hope there will be some work-around method.

You can never be certain that a dirty downgrade will work. You can of course try, but be prepared for trouble.
If I remember correctly, in this case, simply uninstalling the Manager and reinstalling the apk that comes bundled with v18.1 might have fixed things.

The right A12 ROMs rooting procedure

After searching the forum thoroughly, trying multiple found solutions and trying to find the answer on my own I decided to ask here. What is the right procedure to clean flash A12 AOSP-based roms and getting root?
Some time ago, after updating to A11 rom, I noticed I can't use Magisk the way I used to to root my device - 'no ramdisk' status made me forget about rooting for a while. Now I want it back at any cost. This is why I want you to answer some of my questions, including the one above:
1. Is 'ramdisk: no' status caused by A11 and above versions?
2. Is there a way to have ramdisk status 'yes' on A12 ROM to root the device without having to patch boot.img?
3. Magisk installation doc has totally different way of rooting in my situation. According to it, for ramdisk status 'no' the only solution is 'Magisk in Recovery'. However, every time I saw someone talk about no ramdisk magisk patching, they were patching the boot image - it works fine and is even suggested by Magisk app. Who is wrong here and which solution is the right one?
4. Is there a way to get SafetyNet to pass on patched boot.img? Is there a way to get it to pass on a rooted A12 rom?
5. Some time ago, I have accidentally flashed european vendor instead of chinese one (I own chinese K20 Pro). I had no problems with it so I ran it for a few months and then flashed it back to chinese. Might this be the source of ramdisk issue?
Big thank you to anyone who replies. I have no important data on my device so there is no need for a data-safe solution. I feel like existing flashing/rooting guides seem outdated as they mention A10 at best. After more than 2 years of owning this device I still love it and am not going to replace it anytime soon and I hope there are still people like me! Cheers!

deadw0lf said:
After searching the forum thoroughly, trying multiple found solutions and trying to find the answer on my own I decided to ask here. What is the right procedure to clean flash A12 AOSP-based roms and getting root?
Some time ago, after updating to A11 rom, I noticed I can't use Magisk the way I used to to root my device - 'no ramdisk' status made me forget about rooting for a while. Now I want it back at any cost. This is why I want you to answer some of my questions, including the one above:
1. Is 'ramdisk: no' status caused by A11 and above versions?
2. Is there a way to have ramdisk status 'yes' on A12 ROM to root the device without having to patch boot.img?
3. Magisk installation doc has totally different way of rooting in my situation. According to it, for ramdisk status 'no' the only solution is 'Magisk in Recovery'. However, every time I saw someone talk about no ramdisk magisk patching, they were patching the boot image - it works fine and is even suggested by Magisk app. Who is wrong here and which solution is the right one?
4. Is there a way to get SafetyNet to pass on patched boot.img? Is there a way to get it to pass on a rooted A12 rom?
5. Some time ago, I have accidentally flashed european vendor instead of chinese one (I own chinese K20 Pro). I had no problems with it so I ran it for a few months and then flashed it back to chinese. Might this be the source of ramdisk issue?
Big thank you to anyone who replies. I have no important data on my device so there is no need for a data-safe solution. I feel like existing flashing/rooting guides seem outdated as they mention A10 at best. After more than 2 years of owning this device I still love it and am not going to replace it anytime soon and I hope there are still people like me! Cheers!
Click to expand...
Click to collapse
Although Magisk official guide on Github is not clear about, for MIUI you should patch boot.img, not recovery, and do not pay attention to Ramdisk no.
However, when patching boot.img, watch to the log window and you will see it reports there that it found Ramdisk
And that procedure works fine on A11 as well - I have it (MIUI 12.5.2 on my side)
I suppose you have the official A11 and you installed over custom A12 ROM).
Old Magisk v23 was released before A12, hence you should IMO go for the new Canary or Alpha 23016
Btw, you will be IMO better askung in the Magisk General XDA thread

zgfg said:
Although Magisk official guide on Github is not clear about, for MIUI you should patch boot.img, not recovery, and do not pay attention to Ramdisk no (when patching boot.img, watch to the log window and you will see it reports that it found Ramdisk)
And that procedure works fine on A11 as well - I have it (I suppose you have the official A11 and you installed over custom A12 ROM)
However, old Magisk v23 was released before A12, hence you should IMO go for the new Canary or Alpha 23016
Btw, you will be IMO better askung in the Magisk General XDA thread
Click to expand...
Click to collapse
Thank you for replying.
I am aware of Magisk Canary, I used it to root my current A12 rom. Yes, I flashed it over the latest chinese MIUI firmware. Is there any way to pass SafetyNet with it though?

deadw0lf said:
Thank you for replying.
I am aware of Magisk Canary, I used it to root my current A12 rom. Yes, I flashed it over the latest chinese MIUI firmware. Is there any way to pass SafetyNet with it though?
Click to expand...
Click to collapse
If you are on Canary 23016 (latest), you must enable Zygisk, and reboot
Then enable Enforce DenyList and go to Configure DenyList, enable Show System and OS apps, find Google Play Services and checkmark com.google.android.gms and
com.google.android.gms.unstable, and reboot again
If you were on the official, certified ROM, that would be enough to pass SafetyNet (since new Magisk app has no more the built-in SN checker, use one from PlayStore like YASNAC)
With your custom ROM you would probably need Universal Safety Net Fix= USNF 2.2.1 (latest).
Maybe even Magisk Hide Props Config (if USNF not enough) to spoof your unofficial/not Google certified ROM fingerprints - you will need to figure out (pain in the ass with custom ROMs)

zgfg said:
If you are on Canary 23016 (latest), you must enable Zygisk, and reboot
Then enable Enforce DenyList and go to Configure DenyList, enable Show System and OS apps, find Google Play Services and checkmark com.google.android.gms and
com.google.android.gms.unstable, and reboot again
If you were on the official, certified ROM, that would be enough to pass SafetyNet (since new Magisk app has no more the built-in SN checker, use one from PlayStore like YASNAC)
With your custom ROM you would probably need Universal Safety Net Fix= USNF 2.2.1 (latest).
Maybe even Magisk Hide Props Config (if USNF not enough) to spoof your unofficial/not Google certified ROM fingerprints - you will need to figure out (pain in the ass with custom ROMs)
Click to expand...
Click to collapse
This is exactly what I needed, thank you!

I dont have this model phone but i faced the same problem, i just flashed ArrowOS S along with magisk but i didnt realised it has now ramdisk no, before i was using AICP and it has ramdisk yes, so i installed latest version of magisk and the system updated but i dont have root anymore, what can i do?
I use OrangeBox for flashing
Edit: also it does replace the custom recovery?