yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
It was discussed above that only Canary 20424 (much newer than Stable 20400) will work on A11

All posts before yours since yesterday, please read
[Magisk] dnsmo:
I am on 20424 and patch the boot.img

never mind, I am stupid, pulled the wrong file.
[Magisk] marc.ientilucci:
Pixel 4 running Android 11.

I used canary 20424, patched the boot.img and flashed with fastboot.

SafetyNet is failing ctsProfile

I have the GPay SQLite module installed and GPay is happy :)

Go ?
[Magisk] acidspider:
Could someone share the magisk patched boot image for working a11, mine does not boot to system but reverts straight back to fastboot not recognising a slot to boot to
[Magisk] KurashikiAzusa:
I am unable to get Magisk Canary working on my Redmi Note 7 (Android 10) but Magisk 20.4 works just fine. Symptoms of Magisk Canary breaking can be seen when MagiskHide is enabled for any application. This results in almost every application grinding to a halt, and the user is unable to start any applications or even return to Magisk Manager to disable MagiskHide. The only fix is a reboot.

The procedure taken to retrieve the logcat is as follows: Magisk is first installed and then rebooted into the system. The application "Firefox" is then started to show that it works. Magisk Manager is then opened and MagiskHide enabled in the settings and also for Firefox. Magisk Manager is exited and Firefox is started. A grey screen occurs (probably because of dark mode) and the system hangs there. You can return to the home screen, but you are unable to start any applications.

I have heard rumors about how a feature called USAP pool breaks Magisk Canary. So far, from all the ROMs that I have tried, this seems to be true. ROMs with USAP pool enabled breaks Magisk, and ROMs that used to not have it enabled but later have it enabled broke Magisk Canary when it was working before.

Logcat attached.
[Magisk] j1gga84:
RootbeerFresh does not recognise root, also the SafetyNet check goes green but when I check root with Root Checker Pro 1.6.3 it says that I am rooted.

Is there any way to hide that also or is it normal that some apps show the root?

Regards View attachment 5094561

Sent from my SM-G960F with Tapatalk
[Magisk] zgfg:
Generally, it is not required and recommended to Hide Magisk from various apps like browsers, etc - what for (and what is the purpose then of rooting)

You need to hide Magisk only from particular apps like banking and similar, that otherwise report you that they detect root and don't allow you to run them, login to their services or so
[Magisk] JudgeDread11:
I think he just used the browser as an example.

To avoid giving away sensitive data in the logcat.
[Magisk] KurashikiAzusa:
Yes, Firefox was only used as an example.
[Magisk] Alxoom33:
Pixel 2 XL running newest 11. Magisk Canary...24 flashed in booted up TWRP. Works great!
[Magisk] xer565:
New here

Im facing a problem where i cant launch magisk manager (stuck on icon screen then crashes) along with being unable to grant root permissions to apps (prompt appears but allow is grayed out)

Any idea what may be the cause, was working fine b4 latest manager update

[Solved]
[Magisk] guest4711:
Had the same issue on one device. Solved it by uninstalling manager, booting to TWRP, flashing Nagisk again, rebooting, installing Manager.

Not sure whether flashing was necessary.
[Magisk] Cares:
I'm in the same boat that SafetyNet is failing.

I only care about GPay so I'll go test it later today to see if it works for me too.
[Magisk] xer565:
Ahh. I was afraid the solution included twrp cuz i dont have it. So i cant reflash magisk.

Thanks you though
[Magisk] J.Michael:
What was your original route to having Magisk?

Can't you reinstall stock, then repeat original Magisk installation? (Being careful to use versions of stock and Magisk that worked for you.)
[Magisk] JimSmith94:
I hope you or someone else can help or point me in the right direction. I have a Pixel 2 XL and have never had a problem updating within and across versions until this one.

As I have always done, I downloaded the image, removed "-w" from flash-all.bat, did adb reboot bootloader and ran flash-all. After it rebooted and sat for a while I got back into the bootloader, did fastboot boot twrp-3.4.0-1-taimen.img, installed twrp-installer-3.4.0-1-taimen.zip, installed Magisk-v20.4(20400).zip and it bootlooped, which I guess is expected due to the need for Canary.

Then I found and followed your above steps in the Magisk Manager settings, got the Canary manager 297, but when I try to install Magisk 20424 the only options are "Download Zip Only" or "Select and Patch a File". I downloaded the zip file, installed it in TWRP, and rebooted, but it only booted into the Android Boot Manager. Is there a file I need to select and patch? If so, which one? I haven't found any instructions for that.
[Magisk] pndwal:
Did you try MagiskHide Props Config configured for passing fingerprint and/or Force Basic Attestation (if you're at least passing basicIntegrity)? PW
[Magisk] cshlcsh:
Pixel 3 always gets stuck on booting animation with all the canary builds from 20420. Noticed someone saying it's fine on their devices.

Anyone has succeeded on Pixel 3 with Android 11? Pleaser tell me how to do it.
[Magisk] Skeetch79:
I have a Pixel 2XL as well and got stuck in a boot loop dirty flashing A11, then TWRP, then Magisk. Had to reflash stock images to fix. But followed this guide and now running A11 with root and Gpay Sql lite module!

https://android.gadgethacks.com/how-to/root-android-11-using-magisk-foolproof-guide-0318066/
[Magisk] Rumsfield:
It works for me, but I had to do a clean installation of A11 first, then install Canary and proceed as usual for the Pixel 3's.

I accidentally did not uninstall Magisk the first time around and just did a normal flash of the new stock image with the -w removed from .bat like usual, and it boot looped the phone.

There is a way to remove Magisk with an .img for fastboot but it only works in A10. Flashing to A10 over A11 so I could try that just kept the phone hanging on the Google logo forever.

So, like I said I eventually backed everything up and flashed the A11 full image, then did Canary and the boot.img routine right afterwards, no issues as of yet.

Hope that helps you.
[Magisk] zgfg:
Sorry, can't help you since I'm not from Pixel community.

Before and after your post there are many success posts (Magisk Canary on Pixel 11 - this is Magisk thread), and I think I've seen some also from Pixel 2XL, please check how they did
[Magisk] xer565:
I had to downgrade to android 8 (only android version that has access to fastboot and bootloader for my device lg g7)

Where i flashed the patched android 10 boot image then upgraded to android 10 without modifying boot b and a via partition dl.

As of now i am on android 10 with no twrp or access to bootloader or fastboot. So downgrading to android 8 again would be my only hope for reflashing magisk after a clean wipe.
[Magisk] Yahoo1:
You need to extract boot.img from factory images zip file, then patch it with Magisk Manager Canary version, then flash it using "fastboot flash boot magisk_patched.img" command (with your img file name), reboot and you are good to go.
[Magisk] 73sydney:
Fwiw i cannot flash magisk via any method on Pixel 2 XL

Tried twrp and patching boot image 4 time seach, nothing but bootloops

Never had an issue ever before 11

Not a first time flasher here :) So please, dont be one of those people who reiterates the steps we all know and then ends the post with "thats all" or i will get stabby :)

p.s. Also fwiw, flashing Magisk zip from TWRP on Android 10 worked fine (ive just done it again now while reverting to 10, and patching the image file via Magisk Manager was unnecessary - it always made me wonder why people on my (new) device made it harder than it needed to be by patching the boot image manually)
[Magisk] Homeboy76:
Just a thought

Did you clean flash (with the -w in the flash-all.bat file) Android 11 (R) ?

If no and you didn't disable/remove all the modules prior to dirty flashing Android 11. The magisk module (s) could be causing the problem.

Just a thought
[Magisk] 73sydney:
Always clean flash, always

Especially a major version, what mental person would do a dirty flash from 10 to 11?

<awaits replies on that last line> :)
[Magisk] pndwal:
This user succeeded (after a mental lapse!) Maybe he can help:

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

Could be using fastboot to flash boot.img does the trick, I don't know.

Might be salt in wound to mention he's also using your G Pay module on 2XL w/ A11 also...

<Couldn't resist invitation> :laugh: PW

Edit: Custom Recovery seems to be the real problem. See below...
[Magisk] Alxoom33:
Please see below.

You cannot install TWRP and Magisk in 11 you need to first flash the A11 stock boot image. Then fastboot boot into TWRP, flash Magisk Canary v 024 and reboot. Don't install TWRP!
[Magisk] 73sydney:
I assume he was one of those people who didnt do a clean install and instead dirty flashed from 10 to 11, becuase i did a clean flash and tried flashing via zip and also patching boot image after booting into ROM....neither worked. TWRP was installed and working fine. :)
[Magisk] pndwal:
Ah yes! And that! I did read TWRP is not yet compatible with A11. That should be a great help to many!

Guess either method, yours (fastboot boot TWRP then flash Canary MagiskSU), or [MENTION=3116232]Skeetch79[/MENTION]'s (fastboot flash Magisk modified boot.img) may do the trick then!

Many thanks, PW
[Magisk] Skeetch79:
I was on rooted A10 (TWRP and Magisk). I dirty flashed the A11 image from Google and let the phone boot. I rebooted in to Fastboot mode and then flashed the TWRP image (to install it) followed by the Magisk Install ZIP. This caused a boot loop. The phone would boot to the "G" logo and then reboot.

To set things right again, I rebooted in to Fastboot mode and reflashed the A11 image which allowed the phone to boot correctly.

Following the guide I linked to in my post, with the dirty flashed A11 installed, I installed Canary Magisk Manager APK (latest at the time), extracted the boot.img from the A11 zip file and patched it. After copying the patched boot img back to my PC, I rebooted the phone in to fastboot mode, connected via USB cable and issued a command similar to this: fastboot flash boot patched_ boot_img

Since no errors were seen upon flashing the patched boot img, I rebooted the phone and A11 started up normally with root. I then proceeded to flash the GPay SQL fix module for Magisk.

Running great now! Busybox is also installed.
[Magisk] pndwal:
Well, seems he only told part of the story. I forgot TWRP is incompatible with A11 at present. Seems you also need stock Recovery w/ A11. That now appears to be your real problem, and [MENTION=4100646]Alxoom33[/MENTION] gave fuller explanation. See 2 posts above. All best, PW

---------- Post added at 04:33 PM ---------- Previous post was at 04:22 PM ----------

Great stuff!

Seems you've succeeded with DIRTY migration from A10 to A11 w/ root also... Mental!

But it seems that the real cause of bootloops was the presence of TWRP. Guessing you still have stock (not custom) Recovery. PW
[Magisk] Skeetch79:
Yes, I am still on stock recovery.

Wow, do I feel like a doofus now! It was TWRP all along!
[Magisk] pndwal:
Nah, your an inspiration... A trailblazer...

And you seem to have pulled off a DIRTY migration from A10 to A11 w/ root also... As was said, that's MENTAL!

...If all else fails, try, and try again!

Full marks for both persistence, and a great result for yourself and other 'custom'ers.

"The greatest lesson in life is to know that even fools are right... sometimes." - Winston Churchill. :D PW
[Magisk] bosox284:
Heh, this mental person would. I didn't want to go through the effort of starting fresh. So far so good with my P4XL on 20424.
[Magisk] Alxoom33:
The fact that TWRP and Magisk are incompatible on A11 is a well known issue from the date of the first A11 Developer Previews back in March. I don't believe it is something that is going to be fixed. I just fastboot boot into TWRP when I need to. Keep Stock recovery and Magisk Canary on my phone.
[Magisk] 73sydney:
Dont you encourage these guys [MENTION=7550078]pndwal[/MENTION] :) :)

Why do i get in trouble for doing things properly...this one time it didnt work :) :)
[Magisk] Skeetch79:
Guess I have not been following all of the 'beta' stuff too closely ;) Never have really been one to install the betas - I like to be 'surprised' when the official release comes out! :)

The

fastboot boot

option sure is a wonderful feature of TWRP!
[Magisk] @kitokit:
Is it safe to switch from magisk 20.4 stable to canary build? Do I need to re install my modules? Can someone walk me thru the steps

I'm running lineage 17 on my xperia z2.
[Magisk] stuzor:
I have a pixel 4xl that was on 10 rooted with magisk. I did the ota upgrade to 11 and then after switching to magisk canary e66b0bf3(298) which seems to be the latest canary I could find I am unable to boot my magisk_patched boot image. It tries, get's to the google logo and then goes back to the bootloader saying no valid boot images found or something like that. I tried reinstalling 11 without a wipe and tried booting the magisk_patched again but no dice. Is my version of canary right? I saw some different versions people mentioned but when I looked on the github this is the version I get.
[Magisk] Alxoom33:
No, that's the Magisk Manager apk, the zip you flash in booted TWRP is Canary v. 20425. Make sure that you don't install TWRP.
[Magisk] wilsonhlacerda:
Typically, yes, you can upgrade to canary without problems. BUT canary is an Alpha, bleeding edge version, keep this always in mind. Currently the one available seems very good, but...well...it's canary.

So if you decide to do it, be sure you have (nandroid) backup and/or you know how to deal with bootloops or things like that.

To upgrade to canary you only have e to go to settlings and set to use a custom channel and paste the URL of canary (see previous posts for links). Then update Manager and only then (with the new manager) update Magisk itself.

If your Manager is hidden and have any problems while upgrading, set to decrypt it before trying upgrade again.

Don't need to reinstall modules or anything else. Just the above (if everything goes the expected way).

Edit: this is the URL

https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/debug.json
[Magisk] lividhen99:
Did you make sure to hide magisk from root checker pro?
[Magisk] stuzor:
Thanks for the reply. Yeah I haven't used twrp in a while due to compatibility issues, I just boot the modified boot img that is patched from magisk manager. Then I usually patch it directly from magisk manager on the next boot. That said in this case I tried flashing it in fastboot as well as just booting but no dice either way.
[Magisk] Alxoom33:
Well now try it the right way[emoji39]
[Magisk] mhrussell1:
A11 dirty flash and canary Magisk worked with the "Select and Patch a File" method. Looks like I still need to edit the Gpay file to allow it to work. Hopefully the old method still works.

Mark

---------- Post added at 08:54 PM ---------- Previous post was at 08:54 PM ----------

A11 dirty flash and canary Magisk worked with the "Select and Patch a File" method. Looks like I still need to edit the Gpay file to allow it to work. Hopefully the old method still works.

Mark
[Magisk] jlmntl:
Might be I'm just lucky, but I was able to go from 10 to 11 on my pixel 3 via OTA using the normal Magisk OTA update procedure. First I updated both MM and Magisk to the latest Canary builds. Then I restored stock images via MM uninstall, downloaded and installed the 11 OTA, and installed Magisk to the inactive slot, not rebooting until Magisk was installed. Booted up right into 11, Magisk installed and root intact, all modules present and installed, safetynet passed, and Google pay working perfectly.
[Magisk] mhrussell1:
A11 dirty flash and canary Magisk worked on Pixel 3 with the "Select and Patch a File" method. Looks like I still need to edit the Gpay file to allow it to work. Hopefully the old method still works.

Just checked and my edits persisted. Looks like a refresh of the screen is all that was needed.

Mark
[Magisk] stuzor:
which is? As stated I am not using twrp. I didn't see the version on magisk there but the magisk manager was the latest canary and it was indeed showing 20425.
[Magisk] zgfg:
Hiding Magisk Manager works now (again) on MIUI (Xiaomi Mi 9T, MIUI 12, Android 10) with the latest Manager 298 (and Magisk 20425).

It was an interesting debugging session:

https://github.com/topjohnwu/Magisk/issues/3147

And indeed, hiding MM works now with no more the need to disable Play Protect

Edit: Successfully updated the repackaged MM 298 to 299 without a need to restore and hide it again?
[Magisk] pndwal:
Aw, you ain't in NO kinda trouble... :)

[MENTION=3116232]Skeetch79[/MENTION] bothered to post his success, even if he fluked it! Thats the spirit I enjoy at XDA!

I also needed [MENTION=4100646]Alxoom33[/MENTION]'s reminder re. incompatibility of TWRP with A11.

My dad always said 'if you don't get germs, you'll get germs!'... Mistakes are germs with a difference; they should build an immunity to making more, but the difference is that this only occurs if one becomes AWARE of the mistakes. So, it's the refusal to become aware that's most dangerous.

No danger of that for most on XDA (though some make me wonder :rolleyes: ), and your awareness has certainly protected XDA members from many 'germs'!

Hope the exchange here was productive for you too. - Got rooted A11 on Pixel 2 XL yet? PW
[Magisk] 73sydney:
[MENTION=7550078]pndwal[/MENTION]

Im pleased to report tonight i am bathing in the glow of Android 11 with root

1) flash-all.bat (with wipe enabled - because clean install)

2) Immediately on reboot from 1 and before it gets anywhere near to beginning of setup: fastboot boot twrp-3.4.0-1-taimen.img

3) adb push Magisk-e66b0bf3(20425).zip /tmp

4) adb shell twrp install /tmp/Magisk-e66b0bf3(20425).zip

5) adb reboot

6) after reboot, install canary magisk manager (for whatever reason doesnt install from TWRP flash)

7) open canary magisk manager and enable magiskhide

Safetynet pass with Basic EvalType still...party time
[Magisk] pndwal:
Wow you're quick!... I mean replied w/ heads-up and detailed 2nd successful method w/ booted TWRP, using adb commands, in 30 secs...

Impressive, and sure to be of help. :good:

Don't party to hard! PW
[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] v.k:
Even with flashing just Magisk v7 without any modules (so there is no su binary), SafetyNet validation fails. So all these nice ideas with modules controlling their "enableness" are not viable.
[Magisk] knpk13:
I noticed that too. Too bad that we can't flash them together.
[Magisk] got2best:
Magisk seems to be working properly triggers root without a problem randomly today android pay says it can't verify the android version. Anyone else have issues?
[Magisk] 4RK4N:
will this work with the safetynet update a few hours ago?
[Magisk] Dalamar666:
someone knows... if I unninstall xposed (systemless), magisk and supersu (phh+suhide), and then I flash the latest october room, I could pass safetynet? Nexus 5 xTraFactory

thanks
[Magisk] Captain_Throwback:
It seems Google is really paying attention to this thread, as SafetyNet now fails because of Magisk, not root! :eek:
[Magisk] alexpower:
I have no magisk, fails because of root, worked fine hours ago with suhide

Gesendet von meinem HTC 10 mit Tapatalk
[Magisk] garthybarthy:
Think Google is failing on everything, I didn't have magisk and it failed, either root, xposed or suhide causing it. Yours is failing because of magisk.

We're screwed.. lol
[Magisk] pjottrr:
hmm, also here problems started a few hours ago. ( pogo)

it took me a while to figure out magisk isn't working anymore... I hope there will be a fix soon because i'm not giving up on root.
[Magisk] Badger50:
I dunno Cap, if they were paying attention, they probably wouldn't have created the iPixel [emoji33]
[Magisk] mrceli:
Magisk v6 not work now, safety net is $h!??t!!! Arghh....what to do now to get root? Wanna move to aple, g00ggle is boring.
[Magisk] Captain_Throwback:
SuperSU and Magisk trip SafetyNet, but phh's hidesu works fine.

So if you just need root (not Xposed or Magisk), you can still use that.
[Magisk] IzaacJ:
Actually, you can't if you're stuck on Android 5.x like I am. No update to 6.0 and no roms that I've found with 6.0. Only found the stock rom, which is 5.0.1.

Edit: If I'm wrong, please let me know! Would love to have root again!
[Magisk] Captain_Throwback:
Not sure I understand. phh's root doesn't require 6.0, does it?
[Magisk] IzaacJ:
All information I've been able to find regarding hiding su has required Android 6.0. But I could definitively be wrong on that. Not familiar with phh's work but I've started to look through the thread now, and it does not seem like it, no.

As I've understood it, it patches the boot img, which is an issue if it uses the same way as Magisk to find the boot.img. Magisk finds a 400+mb boot "partition" when the boot.img I use to flash (in FlashTool) is ~4mb...

dumchar_info:

Part_Name	Size	StartAddr	Type	MapTo	Region
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd BOOT_1
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0 USER
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1 USER
pro_info 0x0000000000300000 0x0000000000100000 2 /dev/block/mmcblk0 USER
nvram 0x0000000000500000 0x0000000000400000 2 /dev/block/mmcblk0 USER
protect_f 0x0000000000a00000 0x0000000000900000 2 /dev/block/mmcblk0p2 USER
protect_s 0x0000000000a00000 0x0000000001300000 2 /dev/block/mmcblk0p3 USER
seccfg 0x0000000000020000 0x0000000001d00000 2 /dev/block/mmcblk0 USER
uboot 0x0000000000060000 0x0000000001d20000 2 /dev/block/mmcblk0 USER
[B]bootimg 0x0000000001000000 0x0000000001d80000 2 /dev/block/mmcblk0 USER[/B]
recovery 0x0000000001000000 0x0000000002d80000 2 /dev/block/mmcblk0 USER
sec_ro 0x0000000000600000 0x0000000003d80000 2 /dev/block/mmcblk0p4 USER
misc 0x0000000000080000 0x0000000004380000 2 /dev/block/mmcblk0 USER
logo 0x0000000000300000 0x0000000004400000 2 /dev/block/mmcblk0 USER
expdb 0x0000000000a00000 0x0000000004700000 2 /dev/block/mmcblk0 USER
tee1 0x0000000000500000 0x0000000005100000 2 /dev/block/mmcblk0 USER
tee2 0x0000000000500000 0x0000000005600000 2 /dev/block/mmcblk0 USER
kb 0x0000000000100000 0x0000000005b00000 2 /dev/block/mmcblk0 USER
dkb 0x0000000000100000 0x0000000005c00000 2 /dev/block/mmcblk0 USER
frp 0x0000000000100000 0x0000000005d00000 2 /dev/block/mmcblk0 USER
android 0x0000000076c00000 0x0000000005e00000 2 /dev/block/mmcblk0p5 USER
cache 0x0000000010000000 0x000000007ca00000 2 /dev/block/mmcblk0p6 USER
usrdata 0x0000000144100000 0x000000008ca00000 2 /dev/block/mmcblk0p7 USER
bmtpool 0x0000000001500000 0x00000000ffff0000 2 /dev/block/mmcblk0 USER
Part_Name:Partition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate

emmc:

partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00000002 "ebr1"
emmc_p2: 00004800 00005000 "protect_f"
emmc_p3: 00009800 00005000 "protect_s"
emmc_p4: 0001ec00 00003000 "sec_ro"
emmc_p5: 0002f000 003b6000 "android"
emmc_p6: 003e5000 00080000 "cache"
emmc_p7: 00465000 00a20800 "usrdata"
[Magisk] Captain_Throwback:
It's possible you'll have the same issue, but maybe not. Only way is to try it, I guess :rolleyes:.
[Magisk] 4RK4N:
tried it. phh's superuser-r266-hidesu.zip dit it.

tupac4u stock+ debloated rom. flashed rm-suhide-v51.zip to remove cf suhide. then rebooted to do full unroot (with stock boot restored) in supersu app. then back in recovery for phh hidesu root. no magisk.

safetynet helper is green now. just for how long...