yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Are you talking about Magisk Hide?

Tap right to the label to disable the option (but why would you disable)

If you are talking about Hide Magisk Manager - use Restore Magisk Manager (same place, one or the other, depending in which state you are)
[Magisk] truelies1:
In the magisk manager->setting, I taped "hide magisk", now I can't find how to unhide it.
[Magisk] BrimoFan123:
The same here.

Read here: https://xdaforums.com/t/magisk-general-support-discussion.3432382/page-2185#post-84329647

You can try 20.4 - this is the latest Magisk version that works for me.
[Magisk] BrimoFan123:
Is the problem with KeePassDroid that it does not allow open keepass db with fingerprint related to Universal SafetyNet Fix?
[Magisk] zgfg:
Again, there are two fifferent options "Hide Magisk Manager" and "Magisk Hide".

There is no "Hide Magisk"

Asking you again, about which of the two above are you talking?

See the screenshot

Please, attach screenshot of your Settings in Magisk Manager
[Magisk] Didgeridoohan:
Like I wrote, the new USNF is known to break fingerprint authentication. So, yes probably.

Easy to test: disable the module and see if it starts working again.
[Magisk] BrimoFan123:
I have disabled Universal SafetyNet Fix, rebooted phone and now I can't logon at all!

Not with the fingerprint, not with the password.

What now?
[Magisk] truelies1:
I believe hide Magisk
[Magisk] Didgeridoohan:
No idea... Try the USNF module thread or your device's forum.
[Magisk] Didgeridoohan:
You don't have root, that's why the app is missing settings.

I'm gonna take a wild guess that when you tried to hide the Magisk app (which will be the name for the Magisk Manager moving forward) it failed somehow (possibly only partly), and you ended up with two Magisk apps installed. The one you're trying to work with now, with a regular icon and name, and the hidden app, with the name you picked and no icon.

Check your app drawer for the hidden app. If it's there, open it. That should in theory remove the regular app, but you might have to uninstall it manually. If the hidden app doesn't open, uninstall that as well and start over.

Here's a couple of resources:

https://www.didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_Managers

https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_Manager_was_denied_superuser_access

If this doesn't apply to your situation, you're gonna have to be more detailed in the description of what you've done and what is wrong...
[Magisk] BrimoFan123:
Great. Thanks
[Magisk] zgfg:
Magisk Manager main screen - does it show that Magisk is installed or N/A?

If it doesn't recognize that Magisk is installed, see the answer from @Didgeridoohan
[Magisk] truelies1:
Here it is, I don't have an idea on how to find a hidden app.
[Magisk] Didgeridoohan:
The "hidden" app will simply be in your app drawer under the name "Manager" (unless you changed it to something else when hiding, and then you'll find it under that name) with a generic android icon.

(If this is your issue, that is.)
[Magisk] truelies1:
I think I pressed cancel after hit hide Magisk, if this is the case, do I still have a hidden app? Seems I can't find Magisk app.
[Magisk] zgfg:
You should have remembered how you renamed Magisk Manager when you did hiding/repackaging

Hidden and renamed Magisk Manager should have an ugly, Android default icon - try to search by the icon

If you have TWRP, you could try to fix the problem by deleting /data/adb/magisk.db
[Magisk] hardcorehenry:
There are plenty Huawei devices that can be unlocked for free now(software and list), of course I can’t guarantee that newer models will get any luck. So DEAR DEVS don’t abandon our lovely devices yet.
[Magisk] BrimoFan123:
What about if I put "remove" file in /data/adb/modules/safetynet-fix ?

(According to: https://www.didgeridoohan.com/magisk/MagiskModuleIssues

If you create the "remove" or "disable" files, Magisk will take care of removing or disabling the module on the next reboot. Uninstalling the module this way is the preferred way, since it will also run any

uninstall script that the module is using

. )

Can you test this approach on your device for me and let me know if this way Universal SafetyNet Fix will be in correct way uninstalled and all changes in system reverted back?
[Magisk] LaurenceGough:
It says under Magisk installation:

"Since Magisk now hijacks the recovery of the device, there is a mechanism to let you actually boot into recovery mode when needed: it is determined by how long you press the recovery key combo.

Each device has its own key combo to boot into recovery, as an example for Galaxy S10 it is (Power + Bixby + Volume Up). A quick Google search should easily get you this info of your device. As soon as you press the combo and the device vibrates with a splash screen, release all buttons to boot into Magisk. If you decide to boot into actual recovery mode, continue to press volume up until you see the recovery screen.

After installing Magisk in recovery (starting from power off):

(Power up normally) → (System with NO Magisk)

(Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)

(Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Recovery Mode)

"

The problem is I cannot get back into TWRP.

I used the patched recovery method to install Magisk as this was the only option I had (no ramdisk). I used LineageOS standard boot.img for this.

I had TWRP recovery on before.

I cannot get into TWRP now even after holding volume up for a long time. Am I doing something wrong?
[Magisk] truelies1:
Just appear, don't know why.
[Magisk] truelies1:
Delete
[Magisk] Didgeridoohan:
Yes, that would work in removing all the module files and reverting those to their original state. There's no need for me to test, since I know that it works (it's my guide you're quoting after all)...

But, exactly how did uninstall the module in the first place? Uninstalling from the Magisk app, I presume, and that would be exactly the same thing...

If you're still having issues opening up your device there's a possibility that removing the lock settings files would let you open it up without authentication (a web search is your friend here). But, beware that depending on your device and setup this could very well leave your device completely unable to open up the OS... Make sure to do a lot of research first.
[Magisk] BrimoFan123:
There is no uninstall script for this module.

I'm in dialog with other helpful guys here: https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/page-19

I checked already all possible steps: rename files that are controlling lockscreen protectio by fingerprint and PIN located in /data/system, flashing back and forth patched with Magisk ramdisk.img and stock ramdisk - no avail.

It seems I'm lost with the phone and ROM reinstallation will be needed.
[Magisk] Didgeridoohan:
Looks like you guys have everything covered over there then. Good luck, I hope you get things sorted (but yes, when tinkering like this it's not uncommon to end up in a situation where you need to wipe and start over, been there done that many times).
[Magisk] Didgeridoohan:
If you're using the boot image when trying to patch the recovery, that might be the source of your problems... The recovery image is what you need.

Does the installation work though, and you have a working Magisk installation?

But also, if you are using the correct file and flashing that to your device it isn't strange that TWRP is removed when you flash the patched (stock) recovery.

Of course, I might be missing something here...
[Magisk] zgfg:
Thanks, interesting 👍

That PotatoNV supports up to Kirin 960 (three years old or so Huawei devices) but that includes Mate 9 (I could, theoretically try with)

So, is it really independent of EMUI version - i.e, does it really support Kirin 960 (Mate 9) but with EMUI 9.1?

Also, upon shortcutting Test Points and unlocking Bootloader is the phone totally wiped and requires flashing board image through Test Point or I could continue using the existing EMUI (or need to reinstall EMUI from eRecovery)?

You could answer me also through PM (that we don't spoil the thread with OT)
[Magisk] zputnyq:
Hi everyone.

this line in magisk canary 21406 if I remember correctly, should be bind_mount isn't it ?

Or am I wrong ?
[Magisk] LaurenceGough:
Well the instructions are not clear it just says use the boot img from your custom ROM so I assumed it would not work with magisk.

At first I tried patching my twrp recovery and it caused boot loop on my phone and I had to loose all data as replacing it with my ROMs original boot img, caches or twrp recovery or using magisk uninstaller did not work at all, just kept boot looping. Nor did flashing the ROM again. Not impressed really as wasted so many hours and data, luckily nothing important.

I've given up on magisk now as even after a complete format and reinstall following the instructions to the letter it was buggy, I eventually got it on and it didn't even pass CTS check which was the original issue. I then installed a build prop fix for CTS module and that fixed the issue but Google pay still did not work after clearing all cache etc.

Waste of time and I thought in the future with trying to install any magisk updates would be a nightmare so I just gave up and installed clean ROM again.
[Magisk] Didgeridoohan:
If you found the instructions unclear you can always help by submitting a PR on GitHub with suggested changes.
[Magisk] digitalhigh:
@topjohnwu Hey man, you still alive?

Got a few questions about Magisk in 2021, wondering what's the best way to get ahold of you directly. Hit me up on Hangouts if you're still using it, or send me a PM here. :D
[Magisk] mrjuniork:
As far as I remember, he turned his back on XDA. So you might reach him better via Twitter, as there he is the most active (besides github of course ..)
[Magisk] J.Michael:
@rafal.polska.b I've lost track of what you've got and where you are.

Find how to boot your device to "safe mode".

Boot your device to safe mode.

Can you "open" your device?

Reboot your device. On this first boot *after* booting to safe mode, Magisk should disable all modules.

Can you open your device?
[Magisk] zgfg:
Discussion has proceeded much further in SafetyNet-fix thread

He sad he has no Safe Mode but he disabled/removed all modules and problem did not dissapear

Find more there
[Magisk] digitalhigh:
Thanks, I'll try him elsewhere. :D
[Magisk] BrimoFan123:
Hi guys,

The story is ended. I have reset to factory and then rooted my phone, restored all apps from Titanum backup and did a lot of customizations in OS and apps that were not backed up.

I promised to myself I will not touch anything that might cause again the same issue.

In short the story was:

- I had a rooted phone with Universal SafetyNet Fix module in Magisk. Then I have disabled that module and did the reboot.

- I was no longer able to unlock the phone. PIN I have typed was the correct one but phone were not unlocking instead going back presenting the lock screen.

- I have flashed stock recovery -> the same - not possible to unlock the phone with PIN

- I have renamed files and folder (as I have adb root and using adb shell it was possible to get there):

/data/system/locksettings.db

/data/system/users/0/settings_fingerprint.xml

/data/system/users/0/fpdata

Result was that the phone were starting without the need to type the PIN but stuck with "Phone is starting" message

- I have tried also to enable back Universal SafetyNet Fix module by deleting "disable" file in /data/adb/modules/safetynet-fix/ folder and flashing again rooted ramdisk.img -> the same not possible to unlock the phone with PIN.

Lesson learnt: if your phone is your daily driver consider few times before you decide to change something in Magisk's modules or settings, lways have latest backup (TWRP or / and Titanum)

Maybe in my case the problem would not happen if I first would remove PIN and fingerprint from LineageOS? I don't know...

Thanks to all who tried to find solution for my case.

Really appreciated.
[Magisk] C5Longhorn:
All,

I'm looking for suggestions on how to restore root to my Huawei MediaPad M5. I recently updated Magisk to stable Manager 8.0.7 and Magisk build 21.4. However this caused me to lose root on the tablet. The tablet is on Android 8.0.

To restore root, I tried the following steps:

1) Downloaded Huawei tablet image 8.0.0, build 200, for the SHT-W09 (C567) USA model

2) Extracted Ramdisk image and copied over to the tablet

3) Opened Magisk and selected Download and Patch File

4) Magisk patched the file and saved it in my downloads folder

5) I then transferred the patch file back to my pc

6) Opened my Fastboot folder that had the patched image

7) Booted the tablet into fastboot mode and tested with command "fastboot devices"

8) After verifying I had a connection, I typed "Fastboot flash ramdisk patched_boot.img"

9) The file was flashed to the tablet

10) I rebooted the tablet, but I still don't have root

Any ideas, do I need to use the command "fastboot flash boot magisk_patched.img"?

Thanks,

Rick
[Magisk] pndwal:
Official instructions say to patch / flash boot.img (or recovery.img if 'Ramdisk = no'; not for you). No mention of extracting / patching Ramdisk image!

https://topjohnwu.github.io/Magisk/install.html so I'm guessing this may help. PW
[Magisk] C5Longhorn:
Thanks, I followed what is in the instructions but no luck. I wonder if I need to use an old Magisk version.

If your device has boot ramdisk, patch RAMDISK.img instead of boot.img

When flashing the image back with fastboot

If you patched RAMDISK.img, flash with command fastboot flash ramdisk magisk_patched.img
[Magisk] pndwal:
Latest Canary Changelog incl. Release Notes:

Magisk (0646f48e) (21407)

[App] Support creating shortcuts on devices older than Android 8.0

[App] Avoid Shell backed I/O for reliable installation

How to Use the APK for Recoveries

In general, it is recommended to install and uninstall Magisk through the Magisk app. However, if you insist to use custom recoveries, rename the Magisk APK's .apk file extension to .zip. TWRP should then be able to directly flash the zip file. If you have trouble renaming the file extension on PC, rename the file with TWRP's built-in file manager. To uninstall in recovery, rename the zip file to uninstall.zip before flashing it.

Diff from v21.4

[General] Magisk and Magisk Manager is now merged!

[App] Rename the app "Magisk Manager" to "Magisk"

[App] Support hiding the Magisk app with advanced technique (stub APK loading) on Android 5.0+ (it used to be 9.0+)

[App] Disallow re-packaging the Magisk app on devices lower than Android 5.0

[MagiskHide] Fix a bug when stopping MagiskHide does not take effect

PW
[Magisk] pndwal:
Seamless update for me using direct Install.

Checked SafetyNet status immediately after first reboot: Full Pass, all settings preserved and active.

Xiaomi Redmi Note 8T, Stock ROM (Magisk in boot.img despite Ramdisk = no). PW
[Magisk] pndwal:
Haven't seen that. Where are these instructions? PW
[Magisk] C5Longhorn:
In the link you gave me. They have a section for Huawei. It's weird I suddenly lost root when I've had it for over a year.

Magisk no longer officially support modern Huawei devices as the bootloader on their devices are not unlockable, and more importantly they do not follow standard Android partitioning schemes. The following are some general guidance for the few who managed to unlock their bootloader and really want to root it.

Huawei devices using Kirin processors have a different partitioning method from most common devices. Magisk is usually installed to the boot partition of the device, however Huawei devices do not have this partition.

Generally, follow Patching Images with some differences from the original instructions:

After downloading your firmware zip (you may find a lot in Huawei Firmware Database), you have to extract images from UPDATE.APP in the zip with Huawei Update Extractor (Windows only!)

Regarding patching images:

If your device has boot ramdisk, patch RAMDISK.img instead of boot.img

If your device does NOT have boot ramdisk, patch RECOVERY_RAMDIS.img (this is not a typo) instead of recovery.img

When flashing the image back with fastboot

If you patched RAMDISK.img, flash with command fastboot flash ramdisk magisk_patched.img

If you patched RECOVERY_RAMDIS.img, flash with command fastboot flash recovery_ramdisk magisk_patched.img
[Magisk] pndwal:
Ah yes! Missed that it's Huawei / Kirin. - Seems correct procedure as long as Magisk (Manager) reports SAR = Yes. If it's No, I guess you should / may still have boot.img w/ ramdisk.

If no joy on Stable build, may be worth trying latest Canary as there have now been a number of subsequent compatibility fixes that may help you. Search my recent posts re Canary Changelogs for details. PW
[Magisk] C5Longhorn:
Hmm, it does say No for SAR, so maybe I should flash the ram disk file as a boot.img.
[Magisk] frohro:
Hi All,

I updated TWRP and Magisk and then rebooted, and now I have a bootloop with my LG h918 such that I cannot boot into recovery, or download mode, or the standard OS mode. I can only boot into the fastboot mode. How can I remove the bootloop?

Thanks,

Rob
[Magisk] pndwal:
If you are meaning patch and flash boot.img (Magisk finds ramdisk and adds Magisk to it within image file, and can now even add ramdisk support where missing), that's how I read it:

Sill, it is Kirin.

I don't have such a device, but I'm assuming if John has this covered, legacy Kirin should still have ramdisk in boot.img, and you could patch this as is normally done.

Seems you should only be reading appended special instructions for Huawei if you have modern Kirin w/ System As Root, and I believe this only applies to devices launched w/ Android 9 and above. (MediaPad M5 LV = Android 8.0, Oreo.)

SAR is the criteria for special case w/ Samsung devices also, and there John states "Samsung (System-as-root): If your device is NOT launched with Android 9.0 or higher, you are reading the wrong section." I don't know why he didn't add the same clarification regarding Huawei. PW
[Magisk] Ziomus:
Please help with SM-G986B and others S21 Ive Tested many ways always with bootloop at logo
[Magisk] zgfg:
Official instructions do mention ramdisk img,

same link you provided but section for Huawei:

Installation

The Magic Mask for Android

topjohnwu.github.io

Screenshot attached

Edit: I see, it was later already discussed
[Magisk] zgfg:
If you are on EMUI 5 (A7) or earlier, patch Boot img, with Recovery option disabled and flash to Boot

If you are on EMUI 8, (A8), you won't have Boot img, patch Ramdisk img but with Recovery option disabled and flash to Ramdisk

If you are on EMUU 9 (A9) and later, patch Recovery img with Recovery option enabled and flash to Recovery.

Pay attention, it is called recovery_ramdisk, but don't mix with ramdisk or erecovery_ramdisk

It used to work that way like a year ago and earlier. If it doesn't work for you, use an older version of Magisk
[Magisk] BrimoFan123:
If you go back few pages you will find other Huawei users (including me) who reported the same: root is lost with Magisk 21.4.

Of course you are performing all steps correctly.

As someone advised: maybe worth to check Magisk Canary build?

I lost ability to use my phone since I disabled Universal SafetyNet Fix module in Magisk and as the result I had have to do reset factory and setup everything from scratch so I'm not going to check Magisk Canary as the volunteer - too much time lost for setting up phone already :-)
[Magisk] DzieX:
<solved>
[Magisk] IlConsiglieri:
Hello Friends,

I have a question. On a samsung a51 with android 10 I keep getting the super user request, even though I have set magisk to auto answer. Magisk has authorization to the filesystem and I have unset and set it to answer with grant. One thing that cought my attention is that when I first rooted the phone, all apps where fine, but one app keeps notifying me that the phone isn't rooted, although root checker verifies the root (after I manually allow super user), and in magisk it says that both magisk and magisk manager can be installed, even though they are both installed already. Any ideas?
[Magisk] M1chiel:
I can confirm the latest canary works for my P10.
[Magisk] pndwal:
I see that's a legacy Kirin Android 7 (EMUI 9.1) LV device.

Just out of curiosity, what ROM/ Android version are you running now?

...And did it NOT work using latest stable for you?

Also, did you need to patch / flash anything other than boot.img?

Thanks, PW
[Magisk] Didgeridoohan:
Could be a bug... You'd need to collect more info to say for sure though:

https://www.didgeridoohan.com/magisk/MagiskHelp

Might be that the app in question doesn't properly ask for root permission and needs an update.

Perfectly normal. You have the option to install/patch an image again, if needed. If there's an update to Magisk or the app, those buttons will change to "Update".
[Magisk] pndwal:
Wow! John's fired up and sticking it to the big 'G' foundation!

Them's fighting words John! ... Sounding very like Gaël Duval, and many on XDA love his (small) 'e' project / foundation!

...Better start by boycotting Macdonald's!

I, for one, will be watching this space... @HippoMan? 😉

Magisk project / foundation certainly has untapped potential on this front... PW

Reference: XDA article referenced by Reddit poster referenced by John Wu, which references hardware-backed attestation techniques, MagiskHide Props Config, and new Universal SafetyNet Fix:

https://www.xda-developers.com/bypa...attestation-unlocked-bootloader-magisk-module
[Magisk] M1chiel:
I am now running stock emui 9.1. I tried Openkirin AEX for a while but it lacks some features and is not as fluent as stock. Magisk did work in version 20.4, but I lost root when I updated to 21.3. I patched recovery_ramdis.img with the latest Canary version and all has been ok since.
[Magisk] Didgeridoohan:
Hm... I don't even get a mention. :p Can't say I'm in it for the fame, so doesn't really matter, but they could have at least tried to get the info regarding MHPC correct. Ah well...
[Magisk] pndwal:
Yeah, I noticed that omission and clumsy description... I did reference MHPC here at least, and we know your's is certainly the most versatile and adaptable prop tool for the ever changing Magisk mod environment...

But it is an XDA article... and who is Skanda Hazarika anyway? You're on the XDA staff!... 💪👏😬🙄😁🤐 PW
[Magisk] C5Longhorn:
Thanks, I did a search on the thread but nothing came up for me. I will go back and read.

How do I install an older version? I've downloaded Magisk Manager 7.5, but when I try to patch the file in the app, it keeps prompting me to upgrade to Manager 8.0.7, even when I'm selecting "Update Magisk" to patch my Ramdisk image. It does not give me the option to patch a file, just update the Manager.

I tried Canary, but no luck for me on EMUI 8.0. I am trying to go back to Magisk 20.4 and Manager 7.5.

Rick