yashsingh1/xdaforums huggingface dataset:
[Magisk] westeight:
Hoping someone can help ...

I'm having trouble installing Magisk after updating my S20 Ultra to Android 11.

Steps:

1. Extracted the boot.img.lz4 from the AP file.

2. Used 7-Zip to create a tar archive which contains boot.img.lz4.

3. Transferred the tar archive to the phone.

4. Magisk Manager > Click top-right "Install" button.

5. "Next" and "Select and Patch a File".

6. Transferred the patched file (in Download/magisk_patched.tar) to my computer.

7. Rebooted to DOWNLOAD mode.

8. Odin > put the file 'magisk_patched.tar' to AP slot and then clicked "Start".

But after reboot, Magisk is not installed ...

Can anyone please help? I did this many times before the upgrade to 11, so I'm guessing there might be a new method and/or version of Magisk?

Thanks :)
[Magisk] exnokiafan:
Hi people I just want to report what happened after rooting my Galaxy Tab S4 updated to its latest Android 10 release.

Well, let's go in order. I had to flash the latest 21.1 beta version, since the latest stable was only apparently flashed correctly.

When I try to verify safetynet and cstprofile: safetynet passes, cstprofile does not pass becasue of the HARDWARE CHECK.

I just use this tablet to play a couple of games and to stream contents on my Chromecast, so I should not worry about this issue.
[Magisk] pndwal:
Find Magisk version required (click history/clock symbol) here:

GitHub - topjohnwu/magisk_files: (Deprecated) Magisk File Host

(Deprecated) Magisk File Host. Contribute to topjohnwu/magisk_files development by creating an account on GitHub.

github.com

Click 'browse files', then 'go to file'

Select a .json file

Click 'raw' button

Copy url for this from browser address bar

Select 'Update channel' in Magisk Manager and paste url in 'Custom Channel'.

Selected legacy version should now appear on Manager home page, and will be used for patching or direct Install.

Use appropriate Installation options for your device... 👍 PW
[Magisk] pndwal:
So long as you have basicIntegrity, to fully pass you likely only need to install MagiskHide Props Config Magisk module, and configure Force BASIC key Attestation option.

Best to manually select a close/similar model to spoof from same Manufacturer for compatibility with model/OEM specific functionality. (Nb. it must NOT be actual model as it's the mismatch that causes fallback to BASIC Attestation.) PW
[Magisk] exnokiafan:
Thanks for the hint mate! Should I use the guide by Didgeridoohan? Which model should I pick from the list in order to pass the check? Another random Samsung smartphone with the same Snapdragon 835, maybe, even if it's not a tablet?
[Magisk] pndwal:
Absolutely! This is his baby... And the boomerang won't fall far from the didgeridoo...

Because this fix works only by messing with model prop(s), select a closely related model for OEM specific/special features to work also as said, eg Galaxy Store, high-end camera functions etc.

It's not about passing only; that's the easy part. Using anything other than actual model will achieve pass (simple mismatch causes fallback to BASIC Attestation), even 'creamcheese'! ...

Other Sammy users may know what's affected by altered model prop(s)... may require trial and error if you encounter any issues. PW
[Magisk] exnokiafan:
I Will try to do what you suggest, since with the other guide I still cannot pass the cst. I will pick the model that the tool automatically suggests.
[Magisk] pndwal:
Try that... And see extra/edited info. in my post above. 👍

Are you using Force BASIC option only? (Not fingerprint)... and entering model DIFFERENT to yours?

Are you still getting evalType HARDWARE (after reboot)?

If you're still not passing ctsProfile with BASIC evalType you may have other issues to address. PW
[Magisk] sillyfox:
Hello, hope someone could point me to the right direction on how to completely uninstall magisk since one of my banking apps keeps detecting magisk now after recent update.

Im on realme-x2pro device

custom recovery: orangefox

custom rom: lineage-OS

Heres what I've try to uninstall

1.

boot to recovery

flash magisk-uninstaller.zip from github

reboot system

after reboot there is still magiskboot file in my /sbin (even when I try to delete manually with adb shell the bin file magiskboot keeps on spawning after every restart)

2.

wipe everything (cache+dalvik, data, internal storage, system, vendor)

flash vendor+rom+gapps

wipe cache

flash magisk-uninstaller.zip from github

wipe cache

reboot system

same as first try:

after reboot there is still magiskboot file in my /sbin (even when I try to delete manually with adb shell the bin file magiskboot keeps on spawning after every restart)
[Magisk] born2bkilled:
Has anyone got the latest build of magisk (21.1 or canary) working on a Sony phone with android 11?

I am running lineageos 18 on an xperia 10 and i cant get magisk to boot after install. it seems to install with no issues but will just bootloop after reboot to system.

Iam running twrp 3.4.0.1 and recovery works fine, but if Iapply the bootloop fix in twrp it wipes magisk patch from the ramdisk.

restoring the stock boot image in twrp works fine so I can keep trying different magisk builds.

any help would be appreciated.
[Magisk] Didgeridoohan:
Sounds like your ROM or kernel is the one using magiskboot. If you've wiped everything and fully flashed the stock ROM there is no way that there are any Magisk leftovers, unless they're included in the ROM.

On A11, that's usually a TWRP issue:

Magisk - Installation and troubleshooting:Magisk and MagiskHide Installation and Troubleshooting guide

www.didgeridoohan.com
[Magisk] catdogmause:
Hi, my parents use old OptimusG with updated android 6.1 pacrom. Lately, banking apps started to fail root chek. So Magisk shows basic integrity OK but ctsProfile fail.

I tried props config module but installing that module breaks also basic integrity checks! The only way to fix that again is to uninstall magisk completely and install it again. So back to square one.

Oh - and changing fingerprint with props config also did not help with ctsProfile fail. (There is no OptimusG fingerprint available but according to readme u can use any fingerprint.)

any help?
[Magisk] Didgeridoohan:
Doesn't sound like the average issues... Logs are often a good starting point.
[Magisk] catdogmause:
Did Magisk install uninstall about 10 times. Installed beta, now installed canary build for log purpouses and everything works. Safety net pass! Dont now why, but I have feeling that phone just does not have resources to handle all the stuff same time.

Whatever difference the builds have, for me at the moment it works.

If somebody still wants to have some logs let me know.
[Magisk] born2bkilled:
Thanks very much. installing 21.1 in a stock boot image without twrp installed worked perfectlty.

now running lineageos 18 rooted with 21.1 on an xperia 10 :)
[Magisk] westeight:
Just in case anyone enounters this problem, the fix was simple:

1. Uninstall the existing Magisk Manager.

2. Switch to the Beta Channel and download and install the latest Magisk Manager.

3. Install the latest Magisk.

4. Reboot.

Device is now certified and passes SafetyNet.

:)
[Magisk] pndwal:
Yeah, sorry no-one picked up on your issue.

Latest Stable 20.4 was released in March, long before any Android 11 compatibility was added to Magisk. So it follows that anyone using A11 must update Magisk to public Beta or debug Canary builds for now. PW
[Magisk] bartleby999:
No. You'll want to pick something as close to your device as possible or you may experience some strange issues. My YouTube stopped showing HDR content when I changed to a device without HDR capabilities.

For example - My device is SM-T860 (Tab S6 WIFI) the best change for me was SM-T865 (Tab S6 LTE).
[Magisk] krs360:
Is there any plan to bring install to other partition back to Pixel phones? It's a pain to have to manually flash every month.

Thanks.
[Magisk] digger16309:
I'm curious about this as well. Does this post not cover Android 11?

OTA Upgrade Guides

The Magic Mask for Android

topjohnwu.github.io
[Magisk] IanWorthington:
I've rooted my zenfone 7 pro with Magisk, but get ATTESTATION FAILED when I run the safetynet check:

basicIntegrity: tick

ctsProfile: minus

evalType: HARDWARE

Is there anything at all I can do to get it working, or is this, as I understand it, the end of the road?

If the latter, is there any way back? Or, having unlocked the bootloader, is that too it?
[Magisk] pndwal:
The Twitter reference in that post is your clue... PW
[Magisk] pndwal:
You need MagiskHide Props Config Magisk module configured for Force Basic Attestation. PW
[Magisk] IanWorthington:
Many thanks, I'll check that out.
[Magisk] eraser0:
my bank app (updated version) is detecting root on lineage os

BankMuscat Mobile banking - Apps on Google Play
[Magisk] zgfg:
So you have Wiki pages (go to Github directly from MM), with the whole chapter devoted to that topic, what to do/try, etc
[Magisk] eraser0:
nothing helped
[Magisk] freshkidd:
how do i get safetynet working on google pixel 2 xl ?? please help !1
[Magisk] FivEawE:
Hello, I have Xiaomi Redmi Note 8 Pro with a custom Android 11 ROM. I patched Magisk to TWRP recovery since my phone doesn't have Ramdisk. Magisk worked but I couldn't enter recovery anymore, despite me holding the Volume Up button the whole time. Has anyone encountered anything similiar?
[Magisk] MoL_82:
I did not know MagiskHide Props Config has this feature. Thank you for mentioning that here!

Edit: It worked!
[Magisk] francwalter:
Is there any way to enforce enabling screenshots with Magisk?

I have some apps which disable the Android default screenshot function, I know that on Xposed there was a module to kick that garbage, but is there some way with Magisk too?

The Google Assistant way ("Ok, Google" and: "Take screenshot") doesnt work.

Thanks.

Xiaomi Mi A1 with Android 9 and root.

frank
[Magisk] bartleby999:
Smali Patcher has that function.
[Magisk] glhelinski:
Hi

I've rooted my oneplus 8 pro on Android 11 using magisk 8.0.3 apk. I do have root according to root checker and titanium backup. But in the magisk app it says magisk was denied superuser rights and at the top it says Installed N/A. I would like to do magisk hide but the option isn't there.

Can anyone tell me what went wrong and how to fix?

Thanks
[Magisk] Didgeridoohan:
Take a look here:

Magisk - Installation and troubleshooting:Magisk and MagiskHide Installation and Troubleshooting guide

www.didgeridoohan.com
[Magisk] Didgeridoohan:
That's too little information to go on, but you've got lots of tips on how to pass SafetyNet here:

Hiding root and passing Safety Net:Magisk and MagiskHide Installation and Troubleshooting guide

www.didgeridoohan.com

Generally it's a bad idea to have TWRP and Magisk installed at the same time these days. Causes all kinds of issues... If you really need to use TWRP it's better to just boot it, not to install it.
[Magisk] glhelinski:
Yes i had seen that link in my own search but didn't lead me to a solution
[Magisk] Didgeridoohan:
So you mean that you do

not

have two Managers installed (one regular and one hidden with a custom name)?
[Magisk] glhelinski:
I don't think so. Here is what has happened :

After i rooted and restarted I went into Magisk and told it to hide magisk (at this point it did not say Installed N/A to my knowledge). It showed me a box that it was working on the hiding. 25 minutes later it was still working on it... So i killed it. I read somewhere that maybe Play protect had something to do with it hanging so i turned off play protect...and rebooted. Still it said Installed N/A and the hide magisk option had disappeared.

Then i started researching for a couple hours. I uninstalled the 8.0.3 apk and reinstalled... Still no change. Uninstalled apk again and tried most recent canary build. Still same situation... I am rooted... It still says Installed N/A and have no option to hide magisk
[Magisk] pndwal:
Guess you've read key-combo instructions here:

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

I haven't done this despite having 'no ramdisk' on RN8T because:

1) I haven't installed TWRP as many are experiencing compatibility problems w/ A11 & TWRP. Nb. Latest TWRP is only officially compatible w/ devices updated to A10 (ie not devices w/ LV - Launch Version A10) at best.

2) I used normal Patching Boot Image method, which is much simpler. Why does this work?...

Well, while Type III (method B) device's have no ramdisk set up in boot.img, if boot.img is patched with Magisk (SU), an effective ramdisk space is now created. This would normally be of no benefit on these devices, but many (including Xiaomi) devices have retained bootloader/ramdisk compatibility despite no stock ramdisk being present, and therefore created ramdisk space will work.

Magisk Manager has no way to determine bootloader compatibility, so the only way to know is to try, and see whether you get bootloop or working root by standard (boot image) patching. Reading here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-83987947

I'd be unsurprised if this works for you. 🤠 PW
[Magisk] Didgeridoohan:
From that description I'm quite positive that you do have a second Manager installed. Otherwise you wouldn't have functioning superuser requests...

Take a good look in your app drawer. If you didn't change the hidden apps name it'll be "Manager", and if you did change it it'll be found under whatever name you gave it. It will have the default generic Android icon.

If nothing else works, you can always delete /data/adb/magisk.db. You'll lose Magisk settings (superuser permissions, MagiskHide list, etc), but that way Magisk will not look for the random package name that was generated during the hiding process (that partially failed) and you should be able to have the regular Manager recognise your installation.
[Magisk] glhelinski:
I definitely do have a generic Manager app that does nothing except flash a magisk logo screen and then closes itself. Are you saying i should first follow the link you sent earlier to delete magisk via adb? And then reinstall the apk? (I never did flash a zip file as I've done in past phones). And then if that doesn't work delete the magisk.db file?

Ps. Oh and do you have any idea if i should have the Canary version or not?
[Magisk] Didgeridoohan:
That's the second Manager I'm talking about (and since the hiding of the Manager failed it's not working properly). You need to remove that and probably also the regular Manager, and then install the apk again (as mentioned in the text I linked previously).

After that things should work as normal again.

You don't have to uninstall Magisk or delete the db file, just uninstall the two Managers.

The Canary builds can be quite unstable sometimes, so unless you really need a feature that's not available elsewhere and are ready to help work out the kinks it's better to stay with stable (or beta if you prefer that, but there might be bugs there as well).
[Magisk] pndwal:
@glhelinski Of course, you no doubt selected Beta Channel (won't see Canary channel in public Stable / Beta Magisk Manager, 8.0.3) to have the Android 11 compatibility present in 21000 series builds, so won't be able to use public Stable for now.

Also, Canary and Beta builds are practically Identical at present:

PW
[Magisk] glhelinski:
This has cleared up my issue...thanks so much. Just as it says in here https://www.didgeridoohan.com/magisk/ManagerIssues I had two 'magisks' installed. One came from crashing when trying to hide it. I actually did read your page first but couldn't connect the dots on what I was looking at. Anyway much appreciated!
[Magisk] logo20heli:
With the latest security patch from Google ( RQ1A.201205.003, Dec 2020 ), my WiFi will no longer turn on on my Pixel 3 XL. I am using the latesst Magisk Canary 21101 w/ Manager 315. I looked at the Magisk troubleshooting wiki and it mentioned reinstalling your custom kernel. I am not using a custom kernel, but am using stock. If I flash the stock boot image, WiFi works once again. It only fails with the Magisk patched boot image. This also worked with the November 2020 patch and Magisk. Any ideas? Could it be modules? Thanks in advance.
[Magisk] sereksim:
Does uninstalling Magisk affect the user data on my device? I want to uninstall (and then reinstall) Magisk because of some issues, but i would prefer to not wipe any user data...
[Magisk] zgfg:
AFAIK, uninstalling Magisk should delete db, therefore modules, root grants, apps set for Magisk hide

Instead, I always patch and flash boot images. That way I go between Magisk versions if needed, boot without Magisk, and next time again with Magisk - always keeping the database and everything
[Magisk] logo20heli:
After troubleshooting some more by disabling some of my Magisk modules, I found out that it is related to the built-in Magisk module for the EDS app. I've contacted the author before and will send a request to see if he can debug it.
[Magisk] sereksim:
Okay, thx. So Magisk settings/databases/... will be affected, but the normal user data on my phone will stay undeleted, right?
[Magisk] Didgeridoohan:
There shouldn't be any worries.

With the caveat that if you've used Magisk (or another tool) to disable forced encryption and decrypted your device, uninstalling Magisk will restore the stock boot image and the device will encrypt on the next reboot. There have been users that interpret the encryption process (that can take some time) as the device being stuck during boot and forces a reboot. That will definitely destroy your data... Don't do that.

Other than that you should probably be fine.
[Magisk] skastream:
where do I download magisk.zip files? I know stupid question#
[Magisk] Golf c:
The only trusted place is

Releases · topjohnwu/Magisk

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Magisk] arik100:
how magisk updates the different apps it install?

does it update about it? i didn't see any update of apps feature in magisk library
[Magisk] zgfg:
Magisk has nothing with your apps and their updates

If you meant updating Magisk Manager - MM itself will note you about

If you meant Magisk modules (they are not apps), open the modules tab in MM, on top you will see if any module you have installed got an update available for download/install
[Magisk] sporc10:
Where do I get the Magisk Manager Canary version?

Or what url/link do I have to type in as update channel to get the latest canary? Right now i installed the 8.0.3 manager
[Magisk] zgfg:
You download everything from Github (Guide, Wiki pages, everything is also there) - link to Github is on your main screen in Magisk Manager
[Magisk] DiamondJohn:
Maybe @arik100 wasnt clear and @zgfg is correct in that Magisk does not really "do" apps. However, apps can be installed VIA Magisk. For example Vanced YouTube Root version. Magisk will "install" the app to the system partition. If a YouTube update is on the playstore, the update will be installed to the data partition (ie /data/app)

i.e. the playstore does the update.

The one on the data partition is the one that will run. And hence it needs to be "detached" to stop the update.
[Magisk] J.Michael:
On a white background, the word "VIA" is almost invisible.
[Magisk] Serial Kazama:
Hello, I have a Pixel 5 with a bad Magisk Modul. How can I flash the Magisk Uninstaller Zip without Twrp? Because there is no Recovery for Android 11.
[Magisk] Didgeridoohan:
Magisk - Installation and troubleshooting:Magisk and MagiskHide Installation and Troubleshooting guide

www.didgeridoohan.com
[Magisk] pndwal:
Wonder about the future for Magisk?

Well, here's the rub... and a roadmap... and possibly an exciting new focus:

PW
[Magisk] multiversepersona:
Hey guys new here I have some questions so pls read & clear my confusions.

1. Does Magisk work in old Mediatek Android?

2. TWRP is not officially supported in the mtk device(micromax a106). Will it work?

3. Does magisk work with other old recoveries that I've found? Here's the link of some recoveries - (https://xdaforums.com/t/micromax-unite-2-custom-recoveries.2809372/)

Note - many links are dead so can you tell me out of available which will work with magisk?

Also I've found another old ClockWorkMod recovery for A106 in the original post here - https://xdaforums.com/t/micromax-un...s-recoveries-tweaks-mods-discussions.2792954/

4. https://www.xda-developers.com/how-to-install-magisk/

- in the guide it says custom recovery needed as requirements. Does it mean I have to flash custom recovery before flashing magisk?

5. https://www.xda-developers.com/how-to-flash-install-custom-recovery/

Then again to install custom recoveries rooted phone is required. What's that? Isn't magisk supposed to do the rooting?

Pls educate me pls. I'm confused
[Magisk] Dr. Neuhaus:
Hello. I need some help.

I'm using Oneplus5 with OOS 10.0.1, stock kernel, Magisk 20.4, Manager 8.0.3.

Module installing stucks on "Flashing" (see screenshot), no matter what module.

Please tell me what should I do to solve it.
[Magisk] Didgeridoohan:
You should be able to save the log (disk icon, top right) even during flashing. That would likely be the easiest way to figure out what's going on.
[Magisk] sdeft:
I have a question for Magisk installation.

When you dirty flash a ROM do you need to re-install Magisk or it survives ?
[Magisk] Didgeridoohan:
Depends on if the ROM can use the addon.d script to reflash Magisk after. Otherwise the boot image will be replaced with the untouched one from the ROM and Magisk will be disabled (unless the ROM doesn't actually have it's own boot image, for whatever reason).
[Magisk] Dr. Neuhaus:
There is nothing in log except those two strings from screenshot.

Could you please suggest me something else.
[Magisk] Didgeridoohan:
Suggestions:

Clear data for the Manager and try again.

Logcat
[Magisk] Dior DNA:
Has anyone tried Magisk v21.1 on (e.g. Phh AOSP) Android 11 (R) GSI ?

I have used Magisk upto v20.4 on Phh AOSP upto Android 10 (Q) GSI ...

But now I upgrade to a Android 11 GSI, and, I would be interested to hear about experiences of others.
[Magisk] BostonDan:
I am holding off on updating because I use Screen2Auto and AAMirror to mirror my phone screen on my infotainment unit on my car. Magisk 21.x does not work with these two programs. As a result, I am stuck at Magisk 20.4 until a solution comes out, and since Magisk 20.4 is not compatible with Android 11, I am holding off on the OS update.

Cheers,

B.D.
[Magisk] Dior DNA:
OK, but I do not use Screen2Auto or AAMirror, if those are the only issues, I may perhaps try 21.x with a 11 R GSI. I hoped someone did so already.