yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Only Magisk Canary (latest) incorporates changes for Androud 11, hence no matter do you use modules or not, etc, for A11 you must go for Magisk Canary

No questions about: Magisk Stable 20.4 is from May, way older than A11, and TJW pushed the work on A11 after the 20.4 release.

Consequently, A11 with even older Magisk 20.0 makes no sense

Or wait until new Magisk Stable to be released, based on the current Canary (that's the whole idea behind the Canary development) and then upgrade to A11 and 20.5

---------- Post added at 06:37 AM ---------- Previous post was at 05:58 AM ----------

Check open Issues on GitHub - if not reported there, slim chances that it would be debugged and fixed (specially if it wasn't for so long)
[Magisk] vinayak.s19:
Can anyone help?
[Magisk] pndwal:
March 23...

v21 promised! :D PW
[Magisk] Homeboy76:
Device Certification

Anyone else seeing this: Google Play Store App (22.0.17-21 [0] [PR] 332555730) is missing Device certification?
[Magisk] Golf c:
It's still there for me. Did you try clearing storage in the play store app?
[Magisk] Homeboy76:
Yes!
[Magisk] Golf c:
Are you passing safety net?
[Magisk] Didgeridoohan:
The certification field sometimes disappears if you've cleared data for the Play store. If you haven't done that, maybe it happened in a recent update or something like that.

It should show up again if you just wait.
[Magisk] Homeboy76:
No!
[Magisk] Golf c:
I would assume that's why.
[Magisk] Didgeridoohan:
That just means that it'll show up as uncertified when it finally does show up.
[Magisk] Homeboy76:
Maybe!

If that is true all devices failing CTS should not show Device certification on the Google Play Store App.

I'll wait 24 hours and check for Device certification on the Google Play Store App.
[Magisk] guest4711:
Whitout any loggs and a description what you are trying to do noone could help you.

Make sure you try to install a current module (not an old one designed for older versions of magisk), e.g. the (internal) systemless hosts module or busybox module from repo.

Report the errors you get and the installation logs...
[Magisk] AndreM962:
After I installed Magisk, the device started rebooting randomly. It doesn't happen often (once, maybe twice a week) but it is frustrating. I'm using the canary build.
[Magisk] zgfg:
Which device, Android version, etc

If Pixel with A11, pls go through other posts
[Magisk] AndreM962:
A Samsung Galaxy J600GT running Android 9.
[Magisk] hfam:
Perfect, [MENTION=7786725]zgfg[/MENTION] to the rescue again!! Thanks brother, as always appreciate the assist! I'm going to do exactly what you suggest; wait for the new Magisk stable release and do the update to A11 then.

Thanks again man, you have no idea how much I appreciate the help.

hfam
[Magisk] warrencoakley:
SafetyNet failing for me today. It was working perfectly for ages. I'm in canary build with Android 11. Has any experienced it today?
[Magisk] Homeboy76:
You were correct! :)
[Magisk] warrencoakley:
Anyone elses down? Got a notification from GPay saying contactless is not working
[Magisk] Didgeridoohan:
Have you turned it off and on again? MagiskHide that is... Often works wonders.
[Magisk] warrencoakley:
Yes not dice I'm afraid
[Magisk] pndwal:
basicIntegrity fail is generally a problem on phone end, MagiskHide toggled off in Magisk Manager settings, bad Magisk modules, Xposed setup, etc. And it will always, in turn, trip ctsProfile.

If that doesn't help, check here:

https://www.didgeridoohan.com/magisk/MagiskHideSafetyNet PW
[Magisk] warrencoakley:
I installed Exposed this morning to update Vanced but it's gone now from my modules list. Maybe that was the issue. If it's not there though so I need to reflash Magisk again?
[Magisk] pndwal:
I'm not sure about Xposed use or removal. I just know XPosed trips basicIntegrity, and so did several Magisk modules, Including stable EdXposed in Magisk repo. However, Canary EdXposed was fixed, and no longer tripped SafetyNet.

Not sure about Aug 2020 EdXposed modules showing in repo now - guess if you used these, they're still failing, but Canary EdXposed may fix problem.

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post82166469 PW
[Magisk] warrencoakley:
I'm not sure what's going on. I've tried reinstalling Magisk fresh and it is still not passing. All the modules pictures attached are the ones I had before it tripped so there is nothing additional there.
[Magisk] warrencoakley:
More
[Magisk] Didgeridoohan:
Clear cache for Play Services.
[Magisk] warrencoakley:
Genius man. Back working. Totally forgot to do that. BOOM!
[Magisk] AndreM962:
These fellows seem to have the same problem I have, and have installed magisk in the same way I did:

https://xdaforums.com/apps/magisk/magisk-causing-random-reboots-t3946712
[Magisk] Didgeridoohan:
Logs are usually a good idea when asking for help. Here are some tips on what logs to get:

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] Philnicolls89:
Have you tried clearing data from Google play store and Google play services? After deleting edxposed you will need to do this to pass safety net again.

Edit - I just realised your question had already been answered lol.
[Magisk] vMAC:
Currently having to problems, hoping someone can point me in the right direction.

Pixel 4XL upgraded from Android 10 to Android 11 this afternoon.

Issue #1 After upgrading (before rooting) Wi-Fi worked perfect. After loading Magisk (flashing the modified boot image) Chrome won't open, force closes when I click on it, and WiFi shows "Connected, No Internet." If I turn off mobile data I can still use DuckDuckGo to access Internet with no problem so the WiFi is definitely working in that app and other apps.

Issue #2 So I wanted to remove Magisk to start the process of determining what the problem is. Unfortunately since I could not use the upgrade from OTA (it was removed due to not working) Magisk has no image file. I used to be able to go to /sbin/.magisk/ to edit the config and drop the stock image in /data/. The sbin folder doesn't exist anymore in Android 11 apparently, didn't notice this until tonight confirmed in [MENTION=4470081]topjohnwu[/MENTION] tweet. So does anyone know where the new location of the magisk config is?

I'll start there and then hopefully I won't have to come back with more questions. ;)
[Magisk] Didgeridoohan:
[MENTION=656056]vMAC[/MENTION] I can't help with #1, but for #2 you can use the command "magisk --path" in terminal (as su) to find the tmpfs mount path.
[Magisk] oxidehaxs:
plzz can u help me thanks

i have tried to install magisk but when i flash the patch boot img it puts phone in boot loop what am i doing wrong looked every where and cant find a way to fix this issue yes boot loader is unlocked yes i changed it to .tar im using odin from u guys that been modded i asked in discord but get no reply i looked on google cant find anything to help me im using s20 sm-g981b thanks:):)
[Magisk] pndwal:
Are you on Android 11? And stable Magisk Manager (set to 'stable' channel?). PW
[Magisk] HippoMan:
I know that much of the recent dicussion here relates to Android 11, but I have a SafetyNet-related issue with my Android 10 setup:

OnePlus 7Pro (GM-1917), OOS 10.3.4, Magisk Canary 40426, Riru v21.3, EdXposed Manager v4.5.7, EdXposed framework v0.4.6.1 (4529) Sandhook.

I have renamed/repackaged MagiskManager.

In Magisk, I have success with "ctsProfile", but I am failing "basicIntegrity". RootBeer is flagging this:

ROOT CLOAKING APPS

However, RootBeer also says NOT ROOTED.

I had the same issue earlier with the non-Canary Magisk v20.4.

Does anyone know of a utility that I can run which will list the "root cloaking apps" that RootBeer might have detected? I have disabled everything I can think of in EdXposed and Magisk which might qualify as such a cloaking app, but I still get this error, and I want to try to figure out what I am overlooking.

Thank you very much in advance.

.​
[Magisk] guest4711:
EdXposed may be the culprit...
[Magisk] Brnway:
Some interesting data for the developers here:

On my HTC10 running Viper10...

I ran the Magisk uninstaller, rebooted, and SafetyNet still failed.

I then flashed back to stock Viper10, and it still failed.

I installed SuperSu and unrooted, and it still failed.

I restored a backup of boot.img from before installing Magisk, and it passed.

Could SafetyNet be checking the contents of boot.img somehow?
[Magisk] westeight:
Wondering how much fail Google can do in one week: yesterday, the ridiculously overpriced and even more ridiculously named 'Pixel' phones. Today, Magisk detection and SafetyNet.

Google is starting to really suck. Apple style.
[Magisk] Captain_Throwback:
Nope. Because SafetyNet passes fine with phh's hidesu ;).
[Magisk] 4RK4N:
http://xdaforums.com/showpost.php?p=68969947&postcount=1063

there ya go. remove anything from magisk, spersu and revert to stock boot.img, then flash r266 and u should pass safetynet.

u can flash a kernel like i did with elementalx afterwards. still green.
[Magisk] Devilix:
But with phh we can't use xposed, right?
[Magisk] Captain_Throwback:
Correct. There is currently no way to use Xposed and pass SafetyNet.
[Magisk] Blauhasenpopo:
No Busybox available

Uninstalled Magisk v6 , installed Magisk v7 and new phh su, wiped Dalvik and reboot.....no Busybox available...turned it on in Magisk but selection do not stayed "on"...so no Busybox

Someone a solution?

Thanks
[Magisk] spartan018:
[MENTION=4470081]topjohnwu[/MENTION], official sticky should be updated the mention that Moto devices don't work (at least not with stock ROMs)
[Magisk] westeight:
Other than stock, I can see no way to pass SafetyNet (with either SuperSU+suhide or phh SuperUser+phhsuperhide)

Still, Xposed and root are and always will be of far more use than SafetyNet / Android Pay :cowboy:
[Magisk] topjohnwu:
Hello everyone!

I am aware that Google has updated Safety Net that makes Magisk itself a no go for Android Pay. In fact, I witnessed the change live while I am developing the new magiskhide, which should hide all Magisk modules and Magisk installed root.

Google is serious about Safety Net now, clearly hunting down all possibility to run Xposed with Safety Net passed. I spend quite some time examining the new security measures last midnight, and fortunately it seems that it is possible to run Magisk and root along with Safety Net if no Xposed is running. I'm glad I removed the old root toggle at the right time lol, that is no longer feasible with the latest detection.

So stay tuned for the next update, it will come with bug fixes, along with the new magiskhide to bypass that Safety Net.

Google, how will a few systemless mods do any harm :p:p
[Magisk] Emiarrbe:
I'm a full dumb

Does this version of magisk works on a Moto X 2014 runnning CM13 and Xposed?

The last time that I've tried I got a bootloop :,v
[Magisk] le3xis:
Magisk v6 n' v7

Hello friends, I need a help:

After I install magisk v6 or v7, my touchscreen stops functioning

My device is a Motorola motor x1 xt1058 with cyanogenmod cm13 Android 6.0.1

Please help me! S2
[Magisk] westeight:
Exactly. Great to hear you are already thinking ahead, johnwu! REALLY appreciate your hard work, which benefits us all. :cowboy:
[Magisk] Triviox:
FIRST :THANKS!! =D

A question... Them not chance to pass safetynet with xposed systemless? =/
[Magisk] danielcr12:
Issues reported Lest wait for a fix, BTW post logs and all the information you can get, if you don't do that is nearly impossible to fix buga
[Magisk] str8str:
Can you have busy box installed to xbin

Sent from my Nexus 6
[Magisk] ameel:
So Magisk (tested for v6 and v7) fails SafetyNet (as of latest update), even without any root method installed?
[Magisk] PrincessPeach457:
We need a way of feeding safety net the legit information when it goes looking for it
[Magisk] fjdifede:
Thanks for the hard work Magisk V6 still working around other apps keeping Root undetected while using Xposed in my case I don't really care about Android pay I use my bank app and for now still working other thing is the set kernel permissive toggle That I use occasionally for other apps like TWRP manager. I pretty sure this new version will be better just be waiting for new release and bug fixes.

It is possible to detail a little more how to upgrade from V6 version for what I could see it is just a matter of update the installer do we have to remove old version or flash boot img?

Sorry to bother I have been reading but every one do something different depending on device.!

One more time thank you.!
[Magisk] HippoMan:
Thank you very much. However, EdXposed wasn't the culprit earlier (a few days ago). SafetyNet passed back then with the same setup I described above, but with the non-Canary Magisk v20.4.

I'd like to understand what app or apps that RootBeer is actually detecting now.

Also, I checked the logs, and the only RootBeer-related messages have to do with it not finding any */su instances anywhere on my device (which is why, presumably, that it states that the device is not rooted).

.​
[Magisk] Didgeridoohan:
SN passing a few days ago, but not now might just mean that Google updated something...

I'm guessing that you have HiddenCore (or a similar Xposed module installed) installed. That would explain your SN check result. Removing EdXposed and clearing cache for Play Services might make both CTS and basic integrity pass again.
[Magisk] oxidehaxs:
sorry im on android 10 and im dumb what u mean stable channel i can only find android 10 firmware for my s20 sm-g981b

i think i got it to work just had to let it reboot like 10 times hope it has worked and patched it i let u know on outcome thanks supper for quick reply
[Magisk] pndwal:
Since you didn't provide much info, I wondered if bootloop was because latest Stable MagiskSU causes bootloop w/ Android 11 (11 needs later Canary builds), but it's now clear that's not your problem.

Sounds like you may be sorted now, but here's some info that may help further:

The way you changed patched boot image may be a problem. (Does the change for Odin give successful bootup if done on unpatched boot.img, and this is flashed?) May be better to just flash otherwise unaltered Magisk patched boot image using ADB fastboot command if that's possible on your Samsung device.

Nb. Latest TWRP 3.4.0 arrived in June 2020 w/ support for devices upgraded to Android 10. See XDA article:

https://www.xda-developers.com/twrp...s-support-legacy-devices-upgraded-android-10/

There's been no further versions.

As noted, TWRP still does NOT support devices that shipped with Android 10:

So if you have unofficial TWRP, its likely to be causing instability on your phone, just as it does w/ Android 11 devices; ie, ensure you have stock Recovery...

...in other words, DON'T flash TWRP such as this (as members here warn):

https://xdaforums.com/galaxy-s20/development/recovery-twrp-3-3-1-galaxy-s20s20-pro-t4081953/

...but you could try fastboot boot TWRP then flash MagiskSU from it (if you can find working links)... if you're daring! :D PW
[Magisk] pndwal:
After [MENTION=5844839]warrencoakley[/MENTION] had basicIntegrity fail due to EdXposed module (read back here), I tried loading Riru (core) and Riru - EdXposed just for fun.

Updated in EdXposed Manager to latest Canary build, toggled on 'Pass SafetyNet' in Manager settings, rebooted, cleared Google Play / Services / Framework caches w/ Airplane mode on, rebooted, toggled off Airplane mode and checked SafetyNet. > Failed basicIntegrity (and, of course, ctsProfile as I have no 'fake pass' Xposed modules installed).

So I'm concluding Google have indeed changed something, and even 'fixed' Canary EdXposed now trips basicIntegrity! :(

Solution for SafetyNet is simple:

Remove or disable Riru - EdXposed (Riru core is ok), reboot, clear cache for Play Services. > SafetyNet Success!

Solution for Riru - EdXposed w/ SafetyNet Pass:

Wait for a fix!

Nb. Exposed modules can't create a real SafetyNet Pass (seen by Google's server end) like MagiskHide (& MagiskHide Props Config) spoofing does.

The EdXposed module itself must pass, as Canary builds w/ 'Pass SafetyNet' toggled on did till recently. So read 'Xposed SafetyNet modules produce FAKE SafetyNet Pass' at best.

Since real ctsProfile pass requires basicIntegrity, you cannot have this without basicIntegrity. (eg HiddenCore ctsProfile pass is on-device only (fake); Google's server end sees 'fail', and security centric apps still don't show in Playstore and usually don't work even if sideloaded, unless they're modded). PW
[Magisk] oneplusausage:
Good morning!!

i need some quick help if possible! You can even PM me so we can troubleshoot through discord.

TL;DR: the screen instantly goes black, restarts and returns to lockscreen the moment i unlock my device with the pattern (i suspect it's SYSTEMUI but can be 100% sure). i Can't get in now and got some work related data i need to recover from a widget that contains text along with chats from Whatsapp Plus.

stupid me did not make a nandroid backup in TWRP and now i'm screwed.

I use a Oneplus one with RR-O-v6.1.0-20180613-bacon-Official Ressurection Remix ROM based on android 8.1. Kernel is default/unchanged. Magisk is newest version (i think there were no updates for months now). I got 2 modules:

- busybox.

- Magisk Hide .Props config (a small terminal utility that can make google think i use a opo6 with android 9 [thats what is chose] so i get app updates) worked fine for half a year.

Then i took a look and saw an update for both. updating Busybox crashed magisk. Updating .props config seemed ok and just required rebooting like normal.

That's it essentially. since then i can't get past the unlock screen anymore.

I did the following:

i visited this link https://magiskroot.net/uninstall-magisk-module-twrp/ to first try to boot in core-only mode. then, with disabled modules, then i uninstalled Magisk entirely using magisk uninstaller flashable zip from magisk manager (dot) com

the problem persists. i wiped cache and Dalvik/ART cache too but still the same.

besides the obvious clean re-flash that will wipe my data Is there anything i can do to save it?

also i tried to attach a logcat but doing it just gives me one line an then nothing if doing it in ADB while the oneplus is in recovery mode.

If device is on (on lockscreen) i get 'waiting for device'. i searched and that could be because the ADB debugging checkmark is off... any way to turn it on using adb?

could wiping JUST Boot or System in TWRP do anyting?

since i got Titanium backup, can it restore app data from a TWRP backup?

I'm very stressed out by this now. please help if possible.
[Magisk] wallace108:
Hi all, just to find out if I'm not alone in this.

I have an Oukitel WP5-PRO with Android 10

I unlocked the bootloader, installed Magisk Manager (unflagged "keep AVB 2.0/dm-verity) and flashed with spflashtools the patched_boot.img and an emty vbmeta.

On reboot Magisk Manager says that Magisk is NOT installed.

I repeated the process this time using fastboot and using the --disable-verification and --disable-verity arguments for vbmeta. Again: nothing.

Is it me or the current Magisk 20.4 has problems with Android 10?

Any help is appreciated. Thank you
[Magisk] pndwal:
I would first have simply disabled busybox module from /data/adb/modules using file explorer in TWRP.

However, as you've now removed MagiskSU, I'd try simply flashing clean boot.img in TWRP. Extract that from current (RR) ROM zip. :good:

Nb. I wouldn't trust unofficial sites / links to Magisk files which are likely out of date, or worse, hacked and unsafe. All files you need, as well as official and endorsed documentation, are in John Wu's official GitHub.

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post82863085

Many Magisk files are hacked, at best to allow things like custom Repos (John is working on adding this feature officially and safely now anyway), and, at worst, to scam you! PW
[Magisk] casouzaj:
Make sure Magisk Manager is installed on the internal storage (go to Settings > Apps & notifications, slide down and tap on Magisk Manager (or whatever name you gave it whilst renaming it). Tap on Storage. If it is not stored in the internal storage, tap on Change > Internal storage > Move).
[Magisk] wallace108:
Thanks for the reply casouzaj, but Magisk Manager IS installed on the internal storage!!

Mike
[Magisk] pndwal:
Not sure you need that method (verity, vbmeta etc, mentioned in official Installation Instruction for Samsung devices), which may be causing problems.

I'd be checking official Installation Instruction, especially paying attention to 'Knowing your device' as to whether this is A/B, using system-as-root, etc. Eg. "If your device is NOT A/B, but IS using system-as-root, then you will have to install Magisk to the recovery partition of your device."

https://topjohnwu.github.io/Magisk/install.html#knowing-your-device

I'm not familiar with your device, or setting up the various configurations, but following John's specific recommendations is most likely to work. :cowboy: PW
[Magisk] oneplusausage:
hello, i also made my post here, my issue is solved.

https://xdaforums.com/oneplus-one/help/help-past-lock-screen-unlock-interface-t4168699#post83589925

but still thanks for your reply of course!
[Magisk] wallace108:
Thanks pndwal. Actually I've done that also. But rebooting to a (patched) recovery gets me into a boot loop first and then into

system with no changes. Still no joy.

Mike
[Magisk] pndwal:
Great link/find for bypass lockscreen!

Looks like you needed more than removed root/busybox anyway! Well done. :good: PW

---------- Post added at 01:51 PM ---------- Previous post was at 01:40 PM ----------

Sad.

What type is your device? (A/B? system-as-root? Did you get getprop results?)

You still have stock Recovery (no TWRP)? PW
[Magisk] wallace108:
I made a custom Recovery with (MTK) Auto TWRP recovery porter by Team Hovatek that supports Android 10. But when I rebooted into Recovery it got stuck at the logo screen and then switched into fastboot mode.:confused::confused::confused:

My device is probably A/B (not sure). When I did: getprop ro.build.system_root_image I got "false".

Mike
[Magisk] HippoMan:
Thank you very much for all of this!

I removed EdXposed and all Riru modules, and then I rebooted. I then went into airplane mode and cleared the cache for Play Store, Framework, and Play Services. I turned off airplane mode and rebooted. However, my device still doesn't pass ctsProfile nor basicIntegity, including after a second pass of airplane mode, clearing caches, etc.

My device is listed in the Play Store as "certified".

Anyway, at this point, passing SafetyNet has become less important to me. I can run most of what I need to run without it.

In the mean time, I've now made a personal commitment to move towards microg and to work to get Google out of my life as much as possible.

.​
[Magisk] zgfg:
Test A/B by

>> getprop ro.build.ab_update

Canary Manager will also show at the top of the main page
[Magisk] pndwal:
I was assuming you had stock Recovery from this!:

I think you should be following official method first.

Need to check getprop ro.build.ab_update to check if A/B as described.

Official method is to use ADB fastboot to flash patched boot or recovery (depending on A/B & system-as-root combinations described) images where no custom recovery is available.

Nb. TWRP still does NOT support devices that shipped with Android 10, like yours (I checked :) ):

So your TWRP is most likely incompatible with your phone, just as TWRP is with all devices running Android 11.

https://www.xda-developers.com/twrp...s-support-legacy-devices-upgraded-android-10/

Latest TWRP 3.4.0 arrived in June 2020 w/ support for devices upgraded to Android 10 (only). There's been no further versions.

Therefore, you need to remove TWRP, restore stock Recovery, flash Magisk patched image with fastboot.

Guess you could alternatively try fastboot boot TWRP, then flash MagiskSU from it if you need to think outside the (official) box... since you're clearly a maverick! :D PW