Develop Bugs

magisk support on miui 10

Hi, I've recently installed miui global beta 8.6.14 on my RN5 pro. Will magsik v16 work on this rom?

Yes it perfectly working in miui 10 ROM but if u want magsik hide u have to active fingerprint using terminal emulator

varunkumar007 said:
Yes it perfectly working in miui 10 ROM but if u want magsik hide u have to active fingerprint using terminal emulator
Click to expand...
Click to collapse
Howm can I do?

Follow this thread to pass safety net of magisk it helps to hide magisk root
https://forum.xda-developers.com/redmi-note-5-pro/how-to/passing-safetynet-using-tez-whyred-t3800575

zakariya tomal said:
Hi, I've recently installed miui global beta 8.6.14 on my RN5 pro. Will magsik v16 work on this rom?
Click to expand...
Click to collapse
I am using magisk 16.3, it have not any problem
With dev 8.6.21 can use magisk 16.4

Could you elaborate the requirement of safetynet and magisk hide? I'm a tyro here.

Please elaborate .I m also having same problem

Usually the only reason why magisk SafetyNET fails is that Xposed is installed in SYSTEM or in SYSTEM-LESS mode. If you want to pass SafetyNET, you have to remove xposed from the device itself, bc xposed is a framework modification and the framework is included in the SYSTEM, any modification of it would trigger SafetyNET Fingerprint check. Just like rooting a Samsung and triggering Knox, only safteynet fail can be reversed unlike Knox.

Hello, i tried to install Magisk and xposed, but i have bootloop ...
How to fix it, it is possible to install them on miui 10 last stable ?
Link for magisk, xposed framework ?

varunkumar007 said:
Yes it perfectly working in miui 10 ROM but if u want magsik hide u have to active fingerprint using terminal emulator
Click to expand...
Click to collapse
Can you please send an active fingerprint.

Any news about Edxposed Framework on samsung s20+ ?

hi any one know pliz if i can install edxposed framework on samsung galaxy s20+ rooted with lineage recovery ? Thanks
And another question if after rooted with lineage recovery i can update magisk manager and magisk directly with magisk manger ? Thanks

Edxposed works since magisk root... for magisk update you need to flash it with odin.

chieco said:
Edxposed works since magisk root... for magisk update you need to flash it with odin.
Click to expand...
Click to collapse
Thanks . Have u tested install edxposed on s20 series . There is no bootloop problem ?

the new said:
Thanks . Have u tested install edxposed on s20 series . There is no bootloop problem ?
Click to expand...
Click to collapse
No bootloop

chieco said:
No bootloop
Click to expand...
Click to collapse
Ok thanks will test

I had an issue with random reboots. Once they started it seemed like it would reboot 4 or 5 times and then it would stop. Did it once a day at least. Installed Vanced and removed Edxposed. No issues since. Could've been the app to go along with getting Vanced working but i froze it and it still happened so i dont know. Removing Edxposed completely and the apps to get Vanced working stopped the random reboots though.

@Fuzzy13
you must have done something wrong... everything works flawless with those xposed magisk modules + xposed manager + vanced from magisk repo.

need help installing edxposed s20 ultra snapdragon oneui 2.5 rom
magisk 21.1 stable and manager 8.0.3
i tried sandhook and yahfh both give me bootloop after installing last core
any tips ?

MaZaGnGy said:
need help installing edxposed s20 ultra snapdragon oneui 2.5 rom
magisk 21.1 stable and manager 8.0.3
i tried sandhook and yahfh both give me bootloop after installing last core
any tips ?
Click to expand...
Click to collapse
Install Riru Core v21.3 and YAHFA EdXposed build from > here < (official alpha builds from EdXposed devs).
And ofc latest EdXposed Manager.

serajr said:
Install Riru Core v21.3 and YAHFA EdXposed build from > here < (official alpha builds from EdXposed devs).
And ofc latest EdXposed Manager.
Click to expand...
Click to collapse
thank you mate for your reply but i also tried this without luck
and i searched about this problem and i found it is because the kernel enforce selinux so i flashed the custom kernel (jimbok) and turned it to permissive and it worked now without any issue .
i need a way to change stock kernel to permissive because the way i use didn't work
i use terminal command ''setenforce 0'' it doesn't change anything in stock kernel but it worked with the custom one

MaZaGnGy said:
thank you mate for your reply but i also tried this without luck
and i searched about this problem and i found it is because the kernel enforce selinux so i flashed the custom kernel (jimbok) and turned it to permissive and it worked now without any issue .
i need a way to change stock kernel to permissive because the way i use didn't work
i use terminal command ''setenforce 0'' it doesn't change anything in stock kernel but it worked with the custom one
Click to expand...
Click to collapse
That's weird I gotta say.
I have the setup I mentioned and everything works flawlessly (along with latest magisk canary). My SM-G985F with stock firmware is running on enforcing selinux, as it should.

serajr said:
That's weird I gotta say.
I have the setup I mentioned and everything works flawlessly (along with latest magisk canary). My SM-G985F with stock firmware is running on enforcing selinux, as it should.
Click to expand...
Click to collapse
i think your device not a snapdragon version so you dont have this issue
because i saw in https://github.com/ people like me using snapdragon fold 2 and tab s7+
im not good enough to understanding why but i found this
(The interesting thing about the failure on the Fold2, a Snapdragon device, is that a dependent feature of RKP, namely CONFIG_KDP_CRED, stops 2020 Samsung Snapdragon devices from booting when the EdXposed Magisk module is enabled.
My hope is that fixing this RKP patch in Magisk will have the side-effect of allowing 2020 Samsung Snapdragon devices to boot EdXposed with the device's stock kernel.)
and in the end someone said you must use permissive to fix the boot loop
im waiting a fix for that or someone guide me to make the stock kernel permissive because it is not easy like before

MaZaGnGy said:
i think your device not a snapdragon version so you dont have this issue
because i saw in https://github.com/ people like me using snapdragon fold 2 and tab s7+
im not good enough to understanding why but i found this
(The interesting thing about the failure on the Fold2, a Snapdragon device, is that a dependent feature of RKP, namely CONFIG_KDP_CRED, stops 2020 Samsung Snapdragon devices from booting when the EdXposed Magisk module is enabled.
My hope is that fixing this RKP patch in Magisk will have the side-effect of allowing 2020 Samsung Snapdragon devices to boot EdXposed with the device's stock kernel.)
and in the end someone said you must use permissive to fix the boot loop
im waiting a fix for that or someone guide me to make the stock kernel permissive because it is not easy like before
Click to expand...
Click to collapse
Yep mate, exynos!
I didn't know snapdragon devices were facing such issue. I've searched on this now and found this, but I guess you already saw it.
Hopefully a fix will come out soon!

It totally works!I tried it in July/August

Custom rom - google safety net, Google pay

I have xiaomi redmi note 8t, running Evolution X (Android 10) magisk and edxposed. I installed hiddencore (edxposed), set props (magisk, redmi note 8 fingerprint), gpaysqlfix module and everything worked, but after while safety net triggered for some reason. I removed edxposed, reseted props and set it again, reinstalled magisk, nothing helped.
I've hidden all the Google play services and Google play app in magisk hide. What could i do? The hiddencore module shows both ticks in magisk, but the Google pay shows that my device doesn't meet the security requirements.
Thanks for help.

Flashing a custom ROM onto the "T" version of the redmi note 8 results in future problems, many users are complaining saying that it breaks the NFC module if you ever try to return to miui

jiriks74 said:
I have xiaomi redmi note 8t, running Evolution X (Android 10) magisk and edxposed. I installed hiddencore (edxposed), set props (magisk, redmi note 8 fingerprint), gpaysqlfix module and everything worked, but after while safety net triggered for some reason. I removed edxposed, reseted props and set it again, reinstalled magisk, nothing helped.
I've hidden all the Google play services and Google play app in magisk hide. What could i do? The hiddencore module shows both ticks in magisk, but the Google pay shows that my device doesn't meet the security requirements.
Thanks for help.
Click to expand...
Click to collapse
Try hiding the Magisk Package Name in Magisk Settings

jiriks74 said:
I have xiaomi redmi note 8t, running Evolution X (Android 10) magisk and edxposed. I installed hiddencore (edxposed), set props (magisk, redmi note 8 fingerprint), gpaysqlfix module and everything worked, but after while safety net triggered for some reason. I removed edxposed, reseted props and set it again, reinstalled magisk, nothing helped.
I've hidden all the Google play services and Google play app in magisk hide. What could i do? The hiddencore module shows both ticks in magisk, but the Google pay shows that my device doesn't meet the security requirements.
Thanks for help.
Click to expand...
Click to collapse
Go to magisk>settings>clear repo cache>set magisk core only mode>reboot>then uncheck core only mode and see if problem fixed.

devaponnadsm said:
Try hiding the Magisk Package Name in Magisk Settings
Click to expand...
Click to collapse
I tried, still nothing.

I confirm - Magisk manages LineageOS 17.1 to pass CTS checks (and I can install Netflix app) but Google Pay will not allow to use NFC.

Same here with miui 11 .eu

SafetyNet Bypass - Basic Integrity Check fails? (ROOT / Custom ROM: iodéOS 2.1 / LineageOS / Android 11) - SM-G960F/DS

Hello,
I've installed iodeOS on my Samsung S9 SM-G960F/DS with Android 11 which is basicly a pre-configured LineageOS.
Additionally i've installed TWRP and Magisk 23.0 and rooted my phone.
Bootloader is unlocked ofc.
In the SafetyNet, i cant even bypass the simple Basic Integrity check, let alone the CTS Profile.
So my Question is, are there routines to try? does someone have a idea how i could get this working?
Or is it simply just not possible on the S9 to bypass SafetyNet?
I've tried "universal-safetynet-bypass-fix.zip" but i cant seem to flash it from TWRP or Magisk.
Thanks in advance!

Turns out it was a Dev User Build that doesnt work with SafetyNet.
Instead, i've installed LineageOS 17.1 with Android 10 and im ok wiht it.
I've passed Basic Integrity that way and with the following instruction the CTS Profile:
Download this Magisk Module (For Android 7.0/7.1 to Android 12 Beta 4 and future versions) – SAFETYNET-FIX-v2.1.0
Open Magisk and go to the Modules tab
Install the Magisk Module that you downloaded
Reboot your phone, and that’s it.

Question Can anyone point me in the direction of a magisk version that passes safetynet on the oneplus 9 pro?

Can anyone point me in the direction of a magisk version that passes safetynet on the oneplus 9 pro?
I've rooted my phone and the version of magisk i have doesn't have safetynet. I haven't been able to use google pay.

It's not the version of Magisk that's the issue. Magisk by itself generally cannot pass Safetynet, mostly because the CTS profile SafetyNet depends on will fail if the bootloader is unlocked and reports "insecure".
What you need is a module like Universal Safetynet Fix that can spoof hardware attestation, and MagiskHide Props Config to fix everything else.
Keep in mind that Magisk Canary 23010 or newer uses Zygisk and won't work with modules that depend on Riru. Magisk Stable on the other hand has not been updated yet.

As mentioned above, Universal Safetynet Fix is what worked for me. Assuming you're on Magisk Alpha or Canary, you'll want version 2.2.1 (Zygisk). I didn't have to do anything with props config.
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com

Thank you that worked for me, i now have working google pay again.