yashsingh1/xdaforums huggingface dataset:
[Magisk] saiki47:
When I updated the magisk app to 22.1, safetynet basic integrity and cts both are false now. Earlier with 22.0, it worked with magisk hide props config with universal safetynet fix. What to do now?

No, I did not follow up previous conversations. My phone is rmx2027 color os a.59 . Also , when I try to completely uninstall magisk, it does nothing. Restore images seems to work though. So are you saying I have to install canary now ?
[Magisk] Didgeridoohan:
No, you don't have to do anything. SafetyNet is still passing, but the app is no longer able to perform a SafetyNet check due to the API key that was being used has been revoked. It'll be fixed in the next release, but it's purely cosmetical and has no actual implications on SafetyNet passing or not.
[Magisk] Doto143:
Please help. My phone is bootloop, when I flash it with Odin it fails and it says sw rev check fail bootloader device -1. Please help which firmware should I use? Does firmware -1 exist?
[Magisk] zgfg:
I have asked you does SN in Magisk show API error - and so again

And if yes, then read the previous posts in this thread (why API error, about the fix Canary 22104, etc)
[Magisk] saiki47:
Thank you. I just checked with an app from play store. Safety net test passed.

Yes it shows API error.
[Magisk] zgfg:
Strange how people think they don't need to read the other posts but expect that their questions should be addressed and answered😌
[Magisk] pndwal:
Ok, brief search shows:

Test module works for newer Sammy, but not S9.

Some report older USNF version 1.0.2 working, but other issues (GPS etc).

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-84444859

Another user has modified/ made his own working module for Samsung - probably S10, but reported working for S9 (works on Android 10 only).

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-84330523

His binary-patched keystore has some downsides, as he mentions in GitHub issue however.

https://github.com/kdrag0n/safetynet-fix/issues/6#issuecomment-764129632

May pay to search the USNF thread for other S9 (& S8/S10) related feedback. PW
[Magisk] Elcosomalo:
hi all!

Do you know if it is possible to configure something to make the Samsung Note 10 boot straight into magisk mode? (N970F variant)

The new UI3 makes it a pain in the a** to boot into magisk because you have to plug the phone into the usb.
[Magisk] dope77:
your device model and model number?
[Magisk] lhooipg:
okay, will do that and tqvm for the replied...(y)(y)(y)
[Magisk] supersemar:
Magisk working fine with debug canary / canary release

I get pass check safetynet in magisk or with safetynet app

When i install Riru and edxposed safetyNet broken in magisk and safetynet app to.. 2 hours try set up Edexposed sometime i get pass sometime i get failed

Look like a traffic light 🤣 Green red green red 😂
[Magisk] HippoMan:
I've had better SafetyNet luck with LSPosed ... and still better luck than that with TaiChi.

SafetyNet consistently passes with TaiChi ... however, I only have used TaiChi on Android 10, and I'm not sure it works on A11.
[Magisk] martyfender:
Yes, I for one have gotten extremely frustrated with these kind of inconsiderate users, to the point of stopping responding to their laziness and not following xda user agreed rules. WTF?
[Magisk] drewcu:
Have LSposed and upgraded to Canary 22104 and all of a sudden Safetynet FAILS (have tried multiple times).

Was on Canary 22103 also with LSposed and SN passed just like on 22.1 before the API change.

Without LSposed 22104 passes SN so anything I can do to get LSposed not to be detected by Safetynet?
[Magisk] pndwal:
Am I right to assume this is a Ramdisk = no device, and you have Magisk in Recovery (Magisk patched Recovery image)?

I understand you may be able to RE-BOOT to system with root in recovery partition from Magisk App Reboot menu, but I'm fairly sure you'll always need Recovery key combo after complete shutdown. Some have reported otherwise, but John Wu said:

https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

It's not clear why you need to plug in USB. Are you saying key combo changed (or became unavailable) with OS update?

Have you tried reported key combos like:

https://www.thecustomdroid.com/boot-samsung-galaxy-note-10-plus-recovery-download-mode-guide/

but IMMEDIATELY releasing both buttons at vibration / splash screen to bypass Recovery mode and boot to System with Magisk root? PW
[Magisk] pndwal:
I have no experience with rooted Samsung, but if you have SAR = Yes device, John's Installation Instruction, Samsung (SAR), Additional Notes will apply:

https://topjohnwu.github.io/Magisk/install.html#additional-notes

So seems you may need full Odin restore with data wipe (ie. Factory Reset), and (I'm guessing), this may include relocking, to restore. ☹️

Regarding which ROM package to use, this really isn't the best forum for that, but likely others in XDA forums for your device will know. 🤠 PW
[Magisk] wfred:
Thanks, this solved my problem yesterday 👏
[Magisk] wfred:
Unhide Magisk -> install Magisk Canary from GitHub -> rehide Magisk -> restart

Or wait a little while for a new stable release.

There's no real urgency. Phone still passes gpay, credit cards, banks, etc. The Check fails, not the hide.
[Magisk] wfred:
Went to Canary to solve the API issue.

App shows I'm running 22104 and that I'm on the Stable update channel.

Will Magisk just install the stable when the next stable update is released?
[Magisk] zgfg:
Supposidely, next Stable will be 22200, hence higher than Canary 2210x

In that case, Magisk will first ask you to update (Install) Magisk app to that new Stable 22200, and afterwards you will update the Magisk itself
[Magisk] wfred:
Just a suggestion.

Check USB & ADB debugging. I have two apps that need Magisk hide, but will still refuse to load of debugging is turned on

Never mind, I see you find the solution
[Magisk] alexandarpb:
I have a problem here.

Xiaomi Мi А3, still on andorid 10 ( V11.0.10.0.QFQEUXM).

Today I saw that I have an Magisk update. As before, direct installation, but instead of the usual, just black screen was displayed. 10 minutes later I tried to go back in some way, but it was not possible, I decided to clear it from the recent apps, I started again, but only the magisk logo appears and nothing else. I tried to install the recently updated application again, but there was no change. I'm a little scared to restart the phone, because doesn't want it to go into a bootloop or anything like that. I integrated the flash log, but it is literally empty. Should i delete the app data? What should I do? I still have root access.
[Magisk] J.Michael:
Did you have Magisk app hidden / renamed?

You should unhide / unrename.

Check app drawer for multiple copies / versions of Magisk Manager app. Uninstall every copy.
[Magisk] alexandarpb:
No copies, no hiden apps or changed names.
[Magisk] lhooipg:
May I know is anyone able to help me to create a zip file for my patch.boot.img file as my phone does not support adb or fastboot to flash it? I tried TWRP or Flashify app not working.

If yes, please PM me and will send the patch.boot.img file...tqvm in advance.
[Magisk] hachamacha:
Not enough info, but I just made one that's working on my global op7t but made it from the international global 11.0.0.2 payload dumper from lastest Magisk. So that's op7t 1903 and was from the complete source for Global International. What's your model and other versions I mentioned?

magisk: v22104

OS: 11.0.0.2

Flavor: HD1903 or 7
[Magisk] zgfg:
There is no magic in the zip file for TWRP. It will contain your patched img and a command for TWRP to flash to the Boot partition. The same you (supposidely) are doing manually.

If it fails manually, it will also fail from the zip

What exactly are you trying in TWRP, and what/how it fails?

Take screenshots in TWRP by simultaneously pressing Vol- and Pow buttons
[Magisk] lhooipg:
Sorry I am not a tech savvy. May I know model you are referring is handset? If yes I am using SM-N910C (Note 4). Version wise is 6.0.1

Magisk: fb8000b5(22104)
[Magisk] lhooipg:
I boot into TWRP & select img instead of zip to flash
[Magisk] hachamacha:
Oh -- sorry, For some reason I thought you were on an OP7T - I'm not familiar with the note line. Good luck!
[Magisk] J.Michael:
If your device is a Samsung, you probably need to use Odin. Except you talk like you have TWRP.

How did you put TWRP on your device?

You would probably do better in a forum specific to your device.
[Magisk] zgfg:
Ok, does it ask you and do you choose Boot partition for the image to be flashed there?

And how it fails?

Again, make screenshots in TWRP and attach here

EDIT:

If you are using Samsung, then please carefully read Magisk guide on Github - AFAIK (but I have no Sammy and cannot guide you), you should be using ODIN and the tar img, not the boot.img, not TWRP, etc

Search also on XDA for your phone model, there should be a section Guides and Q/A and check or ask there how the other users install Magisk to the same phone
[Magisk] pndwal:
Unless you change channel!

Update Channel now only affects the App version shown as Latest (more specifically, Latest for selected channel), ie. App version to be installed if App Install (or Update) is selected.

Whatever is shown for App Installed will be flashed as Magisk Mask since first single-package version, 21402.

Nb. Post stand-alone builds (21402+), the update Channel NO LONGER determines Magisk Mask to flash. This is now set by App version installed.

Full explanation:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84863037 🤠 PW
[Magisk] wfred:
Now I'm more confused

The app is set to the stable update channel. Will I auto update to the next stable or the next canary?
[Magisk] zgfg:
I've answered you earlier today what will happen when Stable will be released with the build number 22200, higher than your installed Canary 22104

Magisk app will offer you to install/update to 22200 and after that you will also smoothly update the Magisk itself to 22200 (Stable)

Higher number will rule.

And next Stable will not be 22101 or anything lower than your installed 22104 (Canary)

And since you already put the Channel to Stable, further Canary updates will not bother you. At the time when TJW relesses his next Stable it will for sure be higher number than all previous Canaries and Betas - this is the procedure going on at least for the last two years
[Magisk] drewcu:
Have LSposed and upgraded to Magisk Canary 22104 due to the Safetynet API changes, and all of a sudden Safetynet FAILS (have tried multiple times).

Anyone else in a similar situation?

Was on Canary 22103 also with LSposed and SN passed just like on 22.1 before the API change.

Without LSposed enabled, Magisk 22104 passes SN so anything I can do to get LSposed not to be detected by Safetynet?
[Magisk] pndwal:
Not sure what you mean by auto update... I don't think you can!

Channel determines only App to be installed and App listed as Latest (ie. Latest for THAT CHANNEL, not necessarily latest Magisk build).

App Update will only appear when a later build is available for channel set (ie. You WON'T see Canary updates is Stable is set).

App Installed ALONE determines what will be flashed as Magisk Mask.

Magisk [the actual 'mask'] Update will only appear when the Installed version is OLDER than the binary contained in the installed APP. (Again, this is NO LONGER affected by the channel set, or by any newer App shown as latest.)

Things were quite different before first single-package version, 21402.

Nb. If you click Magisk Install NOW, with things as per screenshot, you will be prompted to re-install current 22104, since that is current app installed, and this now (since 21402) contains the Magisk Mask binary.

Nb.2. Since single-package builds were introduced, you can upgrade OR downgrade easily by observing these rules.

To downgrade App however, you will probably need to uninstall the previous app to avoid 'app not installed' error. The app will be found in Download path folder set in Magisk Settings from previous unsuccessful attempt.

Hope it's clear as mud now! 😛 PW
[Magisk] pndwal:
This is at least the second report of this issue. (Read back recent posts). It clearly appears to be a regression.

However, LSposed / riru / EDXposed compatibility was likely the catalyst for the SafetyNet API key change (to the one now causing SafetyNet test errors) in the first place, so it may be a complex fix.

Perhaps you or another LSposed user will / should open an issue (bug report) regarding this. PW
[Magisk] drewcu:
Thanks; I tried submitting an Issue on LSposed's GitHub and I was told to stop asking about SafetyNet and immediately closed my Issue... Kind of rude. My first time asking and aren't EdXposed / LSposed based on the premise that they circumvent Xposed SafetyNet detection? Oh well... guess I don't really need it to pass for most of the stuff I use my phone for anyway.
[Magisk] ipdev:
I thought I read something about Xposed recently. ;)

From the Update snet.jar extension commit message.

Magisk - GitHub - Commit

Maybe LSposed was not circumventing SafetyNet ?

¯\_(ツ)_/¯

Cheers. :cowboy:
[Magisk] drewcu:
I think that is talking about a specific Xposed module doing the faking rather than EdXposed/LSposed themselves... Could be wrong, but at least with EdXposed, you had to exclude certain Google apps to get SafetyNet to pass. So it wasn't like EdXposed is designed to pass SN by default.
[Magisk] supersemar:
For Now Edxposed can't pass Savetynet by default.. LS give me blink status in SN app.. just Taichi give a stable pass in SN app 🤣
[Magisk] alexandarpb:
P.S. Uninstalling the app manager and reinstalling it does not change anything. Still stuck at magisk logo .
[Magisk] J.Michael:
How do you have root access? What can you do that proves you have root access?

Is your root access by way of Magisk?

Have you tried booting into Safe Mode? Or disabling Magisk modules?

How did you install Magisk the first time? Is it installed in the boot partition, or in the recovery partition?

Do you have the "stock" firmware? Can you flash the "stock" firmware? (You will not have Magisk. You might be back to being able to use your device. You might lose all data. Can you back up any data with a black screen?)

EDIT: I think I misunderstood. Do you have a black screen all the time? Or only when you run the Magisk app?
[Magisk] wfred:
Thanks, I understood your clear answer. It was pndwal's that confused me 😐
[Magisk] Nanolo:
Hello everyone :)

I have a problem with Magisk 22.1, here the whole situation:

- Redmi Note 7 (Lavender), MIUI Global 12.0.3 stock (QFGEUXM), Android Version 10 QKQ1.190910.002

- Unlocked bootloader, recovery stock, root with Magisk V22.1 (22100)

After unlocking bootloader, flashing TWRP and installing the Orange Fox, I decided to go for Magisk, therefore I downloaded it, installed the apk and flashed the same file (edited with .zip) through OF.

Everything was looking fine, I had root access to several apps and I also managed to properly hide Magisk to the banking apps, which are working indeed.

Anyway, I don't manage to have SafetyNet passed, and when I run the test I fail both Basicintegrity and CTSProfile, indeed the Play Store doesn't certificate the device and I don't have some of the apps that I need (Netflix for example).

I also installed the MagiskHide Props Config module in order to change the fingerprint and see whether the issue could have been fixed, but guess what, it didn't work. Though, I don't see the Play Store app in the list of checkable apps of MagiskHide (I don't know if it's normal or not).

So, thinking that something may have gone wrong, I red better the installation procedure and I realized that the ramdisk is not in the boot partition for my device and that, therefore, I should have installed the patched recovery image through terminal inputs.

I tried to unistall Magisk both through the app itself and by renaming the .apk in unistall.zip (and flashing it by recovery), but it didn't work: in the first case literally nothing happens, in the second one it seems to repeat the installation process, instead of the uninstallation one...

Therefore I tried to install it in the proper way, but nothing has changed actually, beside the fact that I have the stock recovery now, because I gave that one to Magisk to be patched.

Beside the Play Store not recognizing the device everything else seems to work fine, actually, but it's evident to me that there's something wrong and I don't like it.

So, finally my questions are:

1) Can I flash a full stock firmware through ADB in order to get rid of Magisk and try to install it again in the proper way?

2) What are the risks?

3) Would you advice to do something else before this (for example flash the SfaetyNet_fix.zip)?

4) If it's the case, would it be possible/safe to flash again a custom recovery, seen that now Magisk hijacked the recovery image?

Very sorry for the interminable post, but it's better for yo to have the full context, I think..-.-'

Thankyou very much in advance and have a nice evening! :)
[Magisk] Didgeridoohan:
@Nanolo Sounds to me like you had installed Magisk correctly (there are Xiaomi devices that will report ramdisk = no but still need to be installed to the boot image). Everything sounds like it was working as expected, so I don't think you need to uninstall anything.

You cannot check SafetyNet using the Magisk app on any release up to and including v22.1 since Google revoked the API key used (John's fixed that upstream already). It's been discussed here a lot in the past week or so... SafetyNet is probably passing, you just can't check that with the Magisk app.

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet_API_error

If you really can't pass SafetyNet you've got some tips on how to fix that if you read the rest of the above linked guide, starting here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] sk8223:
I can't seem to uninstall Magisk! I am running LineageOS 18.1 on my Pixel 4a. I installed Magisk on LineageOS and now it's interfering with my LineageOS OTA updates. LOS updates won't install as long as Magisk installed, or so it seems to be the case for me. I tried an LOS OTA update and the ROM wouldn't boot, by some stroke of luck I still managed to get back into the ROM after a reboot in spite of that.

When I try to uninstall Magisk by re-naming the Magisk zip file to "uninstall.zip" as many guides recommend, that just re-installs Magisk.

Apparently there's a Magisk uninstaller from Magisk v21.4: https://github.com/topjohnwu/Magisk/releases/tag/v21.4

None of the newer Magisk releases have any uninstaller associated with them. I am confused as to why this is the case. Anyway, I tried flashing the uninstaller from v21.4 thinking that it would work for v22 as well... it didn't. The uninstall went through but I wasn't able to boot back into LineageOS with the boot.img the uninstaller patched. I had to reflash Magisk again to get back into the ROM.

I did also try to uninstall Magisk from the Manager app but tapping the Complete Uninstall button just closes the dialogue and takes me back to the Manager app... without doing anything. Why? Should I try the "Restore Images" option instead? I'm afraid it will take me back to a bootloop. EDIT: Doesn't work, I get the error "Stock backup does not exist!".

How do you successfully uninstall Magisk? It's really strange to me that Magisk is so difficult to uninstall even on a custom ROM. I've used Magisk on older devices and uninstalled it without issues. Is this an Android 11 issue, or is the Pixel 4a's encryption really weird compared to other devices?

EDIT: I just realized my question is similar to @Nanolo's above
[Magisk] ipdev:
You can uninstall magisk manually by deleting the files related to magisk and replacing your boot image with the ROM's stock boot image.

You will need to work out the proper way for your device.

Remember to make a backup and restore plan in case everything goes wrong.

Example.

Open an adb shell connection and su.

Make sure to grant root to adb shell.

Open the Magisk app and use the uninstall option.

Use app info to Force stop, clear cache and data then uninstall the magisk app.

Use the root adb shell connection to remove the magisk files from the /data/adb directory.

You can remove the adb directory if it is not part of your stock system.

Reboot to bootloader and flash the rom's stock boot image.

Reboot.

Cheers. :cowboy:

PS.

My recovery plan(s) include being able to come back from a soft brick.

I have factory and custom roms and recoveries along with backups of critical partitions.​

- Make sure I have every file(s), program(s), driver(s), cable(s), connection(s), ...

Installed, configured and tested just in case I need any of them.​

- Knowing I could still very well HARD brick the device.

Cheers. :cowboy:
[Magisk] drewcu:
Figured out the issue with SafetyNet and LSPosed for me at least... Minminguard and hooking GooglePlayServices to block ads stemming from it.

I first disabled all Xposed modules and SN passed. Then enabled one by one until I reached Minminguard and finally SN failed. Looked through my list of checked off hooked apps within LSPosed for Minminguard, and the only one Google related was GooglePlayServices. Once I unchecked that and rebooted, SafetyNet passed again.

Guessing Google changed the SafetyNet API relating to GooglePlayServices as before these updates, I had GooglePlayServices checked off in LSPosed/Minminguard and still passed SafetyNet. Now it seems to be an issue to have that checked off. Hopefully this helps anyone else in a similar situation.
[Magisk] pndwal:
Sorry ☹️
[Magisk] pndwal:
Well, of course this will happen with an OLDER releases. These are Magisk Installation packages only, whatever you name them! That's why an uninstall.zip file is provided separately for every older build on GitHub.

Official guide says "rename the [new type] Magisk APK to uninstall.zip". NOT older Magisk zip packages!

You generally always need to use uninstaller.zip matching Magisk Installation in use, not an older one.

Newer releases don't include separate uninstaller as these are now single-package builds (ie. builds from 21402, of which first public was 22000) and now contain the Custom Recovery uninstaller code. ONLY THESE builds files can renamed for different functions (Change extension from apk to zip for custom recovery Installer, change whole file name to uninstall.zip for custom recovery Uninstaller)

All this is made clear in the Release Notes:

https://topjohnwu.github.io/Magisk/releases/22000.html

and John has been at pains to make sure these appear at least when updating Magisk through the app.

Also, it is all clearly spelled out in the Installation Instruction page:

https://topjohnwu.github.io/Magisk/install.html#custom-recovery

Nb. Only APK archive installation packages can be renamed, eg to uninstall.zip.

For OTA purposes, App's Restore Images function, if it works, is generally fine.

Alternatively, (and if App's Uninstall fails, eg No Stock Backup as in your case) you can simply restore the Magisk patched boot image (either boot.img or recovery.img) to original (extract from ROM package for ROM CURRENTLY IN USE) manually. The recommended method is to use PC / Fastboot command.

This uninstalls root / restores boot image to unpatched original version, but leaves Magisk settings, modules, etc in data partition, and these will be restored when Magisk is restored to a boot image and booted again.

It is well known that you need unaltered (unpatched) images including boot, Recovery, system, vendor and others, to take OTA!

You will also need to restore recovery.img if you changed to TWRP.

Nb. After OTA, you will need to patch a boot image from OTA package (either boot.img or recovery.img) as these may be updated (except where doing initial Magisk root using Magiskxxx.zip and Custom Recovery) unless you have Magisk in Recovery and are using patched TWRP.img. In this case only, you can simply flash that back to restore root.

See also John's official notes on taking OTA updates:

https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md 🤠 PW