yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] gururoop:
Just to offer my 2 cents. I have been on Pixel 4XL since Android 11 and participated in each of the Android 12 betas including the developer previews. The way I usually upgrade is by downloading the factory images, extracting boot.img and patching it through magisk. Then I reboot to bootloader, remove -w flag from flash-all.bat and add --skip-reboot flag, before flashing the factory image. After the image has been flashed, I reboot the bootloader and flash the patched boot image using the command: fastboot flash boot magisk_patched-xxxxxx.img.

Now my point is that I don't ever remember flashing vbmeta with --disable-verity and --disable-verification flags and have never lost data in the process. However, when I got Pixel 6 Pro, I took the OTA, extracted and patched boot.img from the available factory image and tried to flash it in fastboot mode using the above command, when I tried to reboot, it landed me in the recovery due to corrupt data error and even after erasing the data, it got stuck in the bootloader screen until I flashed vbmeta with --disable-verity and --disable-verification flags (again from the only available factory image). The phone booted fine and was rooted properly.

I guess, I will have to wait until the next factory image to see how this process could be done every month without loosing data.
[Google Pixel 6 Pro] V0latyle:
This doesn't apply to the Pixel 4 / 4XL / 4a. Only the 4a 5g, Pixel 5, and up.
[Google Pixel 6 Pro] zee3are0:
On the P6P, with 23011, hidden, successfully rooted, running zygisk (so no riru) with MHPC 136 and the USNF 2.0.0 beta (non-riru), I can get both basic integrity and response signature verification to successfully pass in SN, but CTS profile continues to fail.

In props I tried changing my fingerprint from basic to pixel 3a, then re-did basic attestation to pixel 3a, and I notice in the SN checker it's still knowing I'm "raven" (P6P); shouldn't MHPC be passing that I'm "sargo?"

I feel like this is a step that shouldn't be as difficult as the other two, but there's something I'm missing.
[Google Pixel 6 Pro] Pekempy:
I think we need to wait for USNF non-riru to be released again, the beta doesn't seem to work with the CTS profile as I'm in the same place as you
[Google Pixel 6 Pro] V0latyle:
I've said it several times...Just use Magisk 23001 + Riru + USNF 2.1.1 + MHPC 6.1.1. This is what I'm using on my Pixel 5 (build SP1A.210812.015) and have no issues...except the Play Store thinks Hulu isn't compatible with my device for some odd reason. Make sure MagiskHide is enabled on the Google Play Store, too.

Newer isn't always better, and if SafetyNet passing is important to you, you should use the last known configuration that works.

I know there's always a desire to run the latest and greatest, but remember that with Magisk we are dealing with a lot of experimental stuff, and when something changes that breaks the "old" way that works...don't be surprised if things don't work right anymore.
[Google Pixel 6 Pro] Lughnasadh:
Just curious, has anyone here been able to root WITHOUT having to factory reset or wipe data? I think the answer is no but just want to make sure nothing has slipped through the cracks.

If Google releases their security updates for this phone on Monday (not sure if the release will be higher than .036 though), may give us another chance to see if factory resetting/wiping data is needed on a previously rooted (or previously wiped vbmeta) device while updating.
[Google Pixel 6 Pro] Zilla0617:
Something is off with my installation of Magisk, I am unable to check for Safetynet. Any suggestions on how to fix?
[Google Pixel 6 Pro] V0latyle:
This problem began with the 12 Beta on the 4a 5g, 5, and 5a. We didn't have to wipe data, however.

According to @ipdev , it may be because Android 12 uses Boot Header v4; Android 11 used Boot Header v3. That may be the issue we are dealing with; it's entirely possible that Magisk does not properly patch the v4 boot images. That's just an educated guess, we don't know for sure what is causing the problem.

Thus far, we have only found one way that seems to allow update and root without wipe, but even then, it's not completely reliable. Basically, you sideload the OTA in recovery, then WITHOUT REBOOTING, you then enter fastboot, and reflash /vbmeta and /boot from there.

If you take the automatic OTA, or you dirty flash the factory image, then reflash vbmeta, you'll get dumped into Rescue Party until you wipe.

It's not off. Magisk 23010 removed that function; you'll have to use a separate app.

I STRONGLY recommend that if you need SafetyNet to pass, use Magisk 23001.
[Google Pixel 6 Pro] Lughnasadh:
Yep. Been following all this. Read through the links about the new boot headers that ipdev posted. If it is indeed caused by these, would hope tweaks in Magisk might be able to work around this. I think he mentioned he might open an issue in GitHub. Hopefully John can take a look.

I just wanted to make sure everyone has to wipe data and we didn't miss someone doing something that didn't require wiping.

Hopefully Monday we'll be able to see if the manual OTA method you have mentioned that works on the other devices works on the Pixel 6 Pro.
[Google Pixel 6 Pro] Cares:
Newest Magisk isn't able to check anymore. Get another app.
[Google Pixel 6 Pro] diosvany:
where you able to pass safety net
[Google Pixel 6 Pro] niko26:
Which one do you suggest?

Does anyone know the reason why this function has been removed from Magisk?
[Google Pixel 6 Pro] V0latyle:
So far, it seems no one has been able to pass SafetyNet using Magisk 23010 or 23011.

I would recommend using 23011 ONLY to manually patch the boot image, then remove Magisk and install 23001. I'm passing SafetyNet using that version + MagiskHide + Riru + Universal SafetyNet Fix.
[Google Pixel 6 Pro] plasticarmyman:
Just to be clear, 23001 is the stable release right?
[Google Pixel 6 Pro] V0latyle:
No, that's 23000. From what I hear, this version fails to patch the P6 boot image. Worth a try tho.
[Google Pixel 6 Pro] Nekromantik:
not sure if anyone has passed saftynet on P6/P6 Pro even on 23001 with the modules.
[Google Pixel 6 Pro] switchy85:
So I tried this on my P6P and both magiskhide and hide magisk options don't do anything in 23001. I'm rooted just fine, but magiskhide immediately disables itself when you leave the settings screen and hide magisk just locks the app up, doesn't hide it, and goes back to the magisk main page.

Currently still not passing cts or root check.
[Google Pixel 6 Pro] Pekempy:
Yeah 23001 doesn't work on P6P for hiding root + passing SN. MagiskHide isn't functional - you can toggle it on but it turns itself off. there might be some difference with the Pixel 5 and 6 that makes it not work, but as far as I know nobody has SafetyNet passing with any version of Magisk on P6P
[Google Pixel 6 Pro] Nekromantik:
yup

I hope this is not the end of SaftyNet and Rooting together. Might sell my phone if it is haha
[Google Pixel 6 Pro] plasticarmyman:
are you using Riru too?
[Google Pixel 6 Pro] V0latyle:
I've been told that Magisk 23011 + DenyLIst + Universal SafetyNet Fix 2.0.0 + MagiskHide Props Config can be used to fix SafetyNet, but results have been mixed.

I believe Magisk may not yet be able to appropriately patch Boot Image Header v4 yet, so this may be related to the data wipe issue.

As for the other modules, USNF will have to be updated to work with Zygisk instead of Riru.
[Google Pixel 6 Pro] snovvman:
This clarifies my confusion. My experience was that I 23001 could not patch boot from P6, but using 23011 to only patch and then going back to 23001 for root and SN makes sense. However, reading below it seems like even 23001 + MH + USNF does not work on P6. I presume your recommendation above (23001 ++) worked with P5?

Did you use 2301x to patch the boot?

Yea, so far I've only read one claim that it worked to pass SN from a Reddit post. The USFN 2.0.0 version has to be the "test" version.
[Google Pixel 6 Pro] Pekempy:
I've tried every combination I can think of. Using 2301x to patch boot leaves you rooted of course but no magiskhide features work on 23001 APK due to magiskhide not existing in 2301x (which remains your installed Magisk version since that's what the boot img was patched with, regardless of which APK you use)

There's zero conceivable way of getting SafetyNet passing on the 6 Pro currently, until changes are made to USNF and released.

Also I think that Reddit post was likely on a 5, as the 6 wasn't out then
[Google Pixel 6 Pro] V0latyle:
Yes. Currently using 23001. SafetyNet passes.

As far as patching the boot image, we have to be clear:

The issue with using 23011 to patch the image, then running 23001, seems to be MagiskHide doesn't work.
[Google Pixel 6 Pro] Quinny899:
Yeah, I've even tried a modified version of USNF 1.2.0 (the one that keeps being mentioned but actually fails to install on a release build of 12 - you can just rename 31-b2 to 31 in the zip), and it still fails w/ Zygisk and GMS on the denylist. Also tried + props set to the Nexus 5, no dice. CTS is failing, basic is fine.

Either we just need something that's been added to USNF since 1.2.0 (most likely) or something else has changed, perhaps something new that needs modifying in the keystore. I'm sure kdrag0n will get it figured out.
[Google Pixel 6 Pro] Quinny899:
Which makes sense, because the magisk binary that's installed doesn't have magiskhide, and therefore it can't be enabled. You can verify it by doing /data/adb/magisk/magisk64, there's no magiskhide applet.

What would work would be to somehow use 23011 to patch an image to run 23001, but I'm not sure how or if that's even possible.
[Google Pixel 6 Pro] snovvman:
Someone tried a Magisk fork without positive results, but perhaps it's worth another look. The fork is here:

vvb2060 - Overview

vvb2060 has 20 repositories available. Follow their code on GitHub.

github.com

https://xdaforums.com/t/solved-vvb2060s-magiskdetector-beats-magisk-hide.4305217/
[Google Pixel 6 Pro] Pekempy:
Yep, I tried the one in their magisk_files repo, though I've not built from source.

We still need something to pass CTS which I think would be module based rather than Magisk itself, but we'll see what the Devs can do
[Google Pixel 6 Pro] V0latyle:
I'm pretty much an idiot when it comes to Github. How in the world do you look at all the forks off a main project?
[Google Pixel 6 Pro] DespairFactor:
here you go

Forks · topjohnwu/Magisk

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

github.com
[Google Pixel 6 Pro] Quinny899:
Tried simply replacing magiskboot in the APK, and patching the boot.img from file, it patches it but Magisk doesn't start on boot. I presume something has changed with the init, and therefore the idea of a mix and match won't work.
[Google Pixel 6 Pro] snovvman:
I'm no expert whatsoever, but here is the link for the forked Magisk and download links on the page:

GitHub - vvb2060/Magisk: A Magic Mask to Alter Android System Systemless-ly

A Magic Mask to Alter Android System Systemless-ly - vvb2060/Magisk

github.com

Link for MagiskDetector (which I think it's included in the forked Magisk)

GitHub - vvb2060/MagiskDetector

Contribute to vvb2060/MagiskDetector development by creating an account on GitHub.

github.com

Typically, you click on the "Code" button and download zip. It should contain the apk.

Edit, see @Quinny899's post below.

Hope this helps.
[Google Pixel 6 Pro] Quinny899:
Nah, that downloads the repo as a zip - no APK. There is a telegram that seems to be alpha builds though: https://t.me/magiskalpha
[Google Pixel 6 Pro] almahix:
All I care about is Titanium Backup. I feel more comfortable being able to backup and restore

I am reluctant to abandon rooting, as I've done it since 2009. But all I need is to run Titanium Backup just for comfort in case I do something stupid. TiBu requires rooting so if I can find a reliable way to backup and restore apps and their data I'll be happy without root.
[Google Pixel 6 Pro] Quinny899:
Alright, so it's possible. Props to @snovvman for linking the vvb2060 repo, because if you read into the bits in English on the telegram, you'll discover that it has MagiskHide still, as an option.

So:

Download the latest alpha build from https://t.me/magiskalpha

Install it by patching the boot image and flashing in fastboot. You might be able to do a direct install, but I patched it manually and checked it booted with fastboot first first to be safe.

After it boots, you may need to uninstall a hidden Magisk manager if you didn't already - at this point the alpha build will take over, and tell you it needs to install some files and reboot, allow it.

After rebooting, go into the Magisk settings and disable Zygisk. A magisk hide option will magically appear. Reboot.

Install Riru and the latest Universal SafetyNet Fix. There's no repo in the build, so you need to get these from GitHub. I also have MagiskHide Props Config installed, but not with any BASIC spoofing enabled, just installed - not sure if that's required. Doesn't seem to be required.

Reboot.

Make sure you have Play Services unstable and snet added to your DenyList (it's still called DenyList, but it's Hide)

Job done!

View attachment 5444427
[Google Pixel 6 Pro] Cares:
I guess I have to install Telegram to be able to download Magisk Alpha.

Testing right now. Just to be clear, you're using USNF v2.1.1 and Riru v26.1.3?
[Google Pixel 6 Pro] Quinny899:
View attachment 5444433

Yes. Unfortunately yeah you have to make a Telegram and join the channel to download the files. It might be worth it regardless as it'll give you notifications for new alpha builds.
[Google Pixel 6 Pro] Pekempy:
@V0latyle this is the one!

Please update the OP with these instructions.

I'm now passing SafetyNet. Who knew you could disable Zygisk and get magiskhide working! (Using the alphabuild from telegram)

Thank you so much Quinny -

EDIT, had to do this for banking app to workhttps://xdaforums.com/t/santander-app-is-not-working-on-custom-rom-or-root-device.3794753/page-5#post-77321403
[Google Pixel 6 Pro] Quinny899:
But only on the alpha builds from that telegram!
[Google Pixel 6 Pro] zee3are0:
The problem is, 23001 won't work with the P6P. Won't patch the stock boot img. I've even tried patching the stock img with 23011, uninstalling 23011, rebooting to fastboot, loading the patched boot.img, then installing 23001 manually, and it won't allow me to do basically anything. Hide immediately resets when leaving the menu, none of the modules will install successfully, and no root request notifications (such as from an su command in adb shell) will work, even though 23001 shows as "installed."

A full 23011 will root, but none of the known workarounds for SN function, no hide, no riru.

Kind of a catch-22 right now.
[Google Pixel 6 Pro] Nekromantik:
Hmm mine still not passing

Running alpha with Hide enabled and Riru and SaftyNet fix installed
[Google Pixel 6 Pro] Cares:
Brilliant! I have Pass on Basic and CTS with this method.

Unfortunately Chase Bank still somehow detects root and won't let me use biometrics. I added Chase to the block list too.
[Google Pixel 6 Pro] Pekempy:
My banks also still detecting it, but gpay set up successfully, so I'm in some weird middle ground
[Google Pixel 6 Pro] Cares:
Yea I'm able to add my credit cards to GPay. I think I'm happy with this as long as I'm not required to wipe every update or have this cat and mouse game every month of GPay breaking.
[Google Pixel 6 Pro] Pekempy:
Give this a try, it's worked for me (the second, third, and fourth domains in adaway blocklist. I haven't added the top one. Then cleared data for my banking app and it's worked!

https://xdaforums.com/t/santander-a...m-or-root-device.3794753/page-5#post-77321403
[Google Pixel 6 Pro] V0latyle:
Yeah, I'm not really going to post a root app from a questionable source in one of my guides. It's already getting rather dangerous with lots of fake websites hosting "Magisk". Fortunately, the Github is still the first result on Google, but it's immediately followed by 3-4 questionable sites.

I'm glad it worked for you though, feel free to share the news.

Yeah I see a few others are having that same issue. It looks like beyond basic root access, Magisk is kinda useless on the P6 until it's updated.
[Google Pixel 6 Pro] Cares:
Just tried, didn't work for Chase bank.

To be clear my banking app works 100% fine. It's just that they decide to disable face/finger unlock when root is detected for some reason. Even passing SN and MagiskHide it still can be detected.
[Google Pixel 6 Pro] Nekromantik:
i installed riru and saftynet fix both and then rebooted. could that been my issue?
[Google Pixel 6 Pro] V0latyle:
Reboot is generally required after installing modules.
[Google Pixel 6 Pro] Quinny899:
To be fair, the vvb2020 builds are open source: https://github.com/vvb2060/Magisk
[Google Pixel 6 Pro] Lughnasadh:
Just passing along info in case you didn't know, but vvb2060 is the 3rd leading contributor to John's Magisk (at least he was, may be 2nd by now), only behind John himself and John's designer I believe. You can see all he's done in John's Github.
[Google Pixel 6 Pro] plasticarmyman:
i do not f**king recommend this new process...i haven't been able to get it to stick after rebooting....

this is with the Alpha from the telegram
[Google Pixel 6 Pro] EtherealRemnant:
Umm... that's why it's called an alpha... because there are issues to be worked out...
[Google Pixel 6 Pro] plasticarmyman:
i'm aware of why it's an alpha and why the issue exists...just making other people aware of a pretty glaring issue
[Google Pixel 6 Pro] Nekromantik:
im not having that issue

all set up now with banking app and gpay :)

i think using direct install on alpha maybe hit and miss so boot the img and if all ok flash via fastboot
[Google Pixel 6 Pro] Cares:
Yep my root and SN pass sticks through reboot with alpha build.
[Google Pixel 6 Pro] diosvany:
can confirm that safety net passes on my pixel 6 pro as well with this method
[Google Pixel 6 Pro] craznazn:
Root + SN works with the vvb2026 release, but play store still says Not Certified. Any idea?

Edit: deleting play store data and rebooting solved it.
[Google Pixel 6 Pro] Cares:
Just for good measure I did the same method on my 4XL and I'm passing SN checks.
[Google Pixel 6 Pro] Zilla0617:
I'm rooted on .019c2 firmware with Magisk 23011. What's the best way to go about rooting with Magisk alpha on the .36 firmware? I currently have the .36 ota waiting for me. Thanks
[Google Pixel 6 Pro] Cares:
I don't know about the best way but I just ran flash all bat with -w deleted. Then flashed from there.
[Google Pixel 6 Pro] Zilla0617:
But the ota image is not available yet. Did you have to reflash vbmeta?
[Google Pixel 6 Pro] abalam:
Rename the magisk app into a other name
[Google Pixel 6 Pro] Pekempy:
I got it sorted a couple of comments below that, but thanks :)
[Google Pixel 6 Pro] zee3are0:
Had to edit my last post because I felt like a true idiot.

All fixed. vvb2060's MagiskAlpha with Riru and USNF is working flawlessly on P6P Android 12 on Fi. Couldn't be happier.
[Google Pixel 6 Pro] Olorin92:
Safetynet passing as well?
[Google Pixel 6 Pro] Lughnasadh:
I'm curious, has anyone tried this when updating to new build?

1. Take boot image from new factory image and patch it in Magisk Manager

2. Manually install OTA via sideloading in recovery (without rebooting)

3. Boot into fastboot

4. Flash vbmeta.img with flags disabled (fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img)

5. Boot (not install) the patched boot.img (fastboot boot <nameofpatchedimage.img> (Because you mentioned you could live boot the patched image)

6. When booted I would assume you would be rooted but not permanently after a reboot??, but then...

7. Do a direct install in Magisk Manager

8. Reboot

Wondering if after this it will boot without having to factory reset/wipe data and be rooted???
[Google Pixel 6 Pro] Olorin92:
Ah just saw this thread: https://xdaforums.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/. Seems there'sa way to get SN working currently by using the Magisk Alpha builds by vvb2060
[Google Pixel 6 Pro] Zilla0617:
What's the zip file associated with Magisk alpha apk in the telegram channel?
[Google Pixel 6 Pro] V0latyle:
When you use

fastboot boot boot.img

ADB sends the boot image via USB to the phone, and the phone loads it instead of what's in the /boot partition. Therefore if you boot a patched image, you should have root.

However, following the instructions above, you'll still have to wipe. There is an as yet unidentified issue with rooted boot images tripping something (probably the kernel) into thinking data is corrupted.

Here is something you can try however:

1. Download the OTA and the factory image to your computer

2. Patch the boot image from the factory zip

3. Sideload the OTA:

adb reboot sideload
adb sideload ota.zip

4. When the update completes, you will be in recovery. DO NOT REBOOT.

5. Select "enter fastboot"

6. Flash vbmeta and boot:

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash boot magisk_patched-23xxx_xxxxx.img

7. Reboot your device
[Google Pixel 6 Pro] Lughnasadh:
Yes, I was talking about the same procedure as you listed except in 6. instead of flashing the boot.img, just booting it and then direct install in Magisk Manager for permanent root. But you're saying that you still have to wipe, either before originally booting or after a reboot following a direct install?

I'm asking b/c I though you had said earlier that you could flash the vbmeta.img with the flags disabled but still boot (without flashing) a patched boot image without wiping. Just couldn't boot if you flashed the patched boot image without wiping.

I updated my original post b/c I had 1. and 2. reversed.
[Google Pixel 6 Pro] V0latyle:
If you have just unlocked your bootloader and have not done anything else, you should be able to boot a patched image for temporary root, if you don't want to lose data.

If you FLASH the patched image (and disable verity/verification) you have to wipe data, or the phone will boot into Rescue Party.

The only possible alternative is to sideload the OTA EXACTLY as I posted above, meaning you have to flash vbmeta and boot in fastboot.

If you flash the images in bootloader, you will have to wipe.
[Google Pixel 6 Pro] Cares:
Source code. You just need the apk.
[Google Pixel 6 Pro] Cares:
Renaming doesn't work for Chase bank app.
[Google Pixel 6 Pro] Zilla0617:
Ok thanks
[Google Pixel 6 Pro] cd993:
Hello mate, I updated to the OTA but not bothered about losing data. Which instructions am I best following for permanent root?

Many thanks
[Google Pixel 6 Pro] zee3are0:
Yes. Google Pay and USAA apps working, as is Netflix, Peacock, etc.
[Google Pixel 6 Pro] Zilla0617:
I am unable to update to the day 1 Nov firmware .36 update. I initially was on .19 rooted tried to update to .36 after removing Magisk but it didn't work. So I factory reset my phone and tried to perform ota install but it fails to install. How can I install .36 ota?
[Google Pixel 6 Pro] cd993:
Which instructional steps would you suggest I use for being on the latest update and not bothered about losing data, to get permanent root (not lost on reboot)?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Probably need to re-enable these, might have to reflash again after.

(these are the OP's instructions to disable them. Adjust accordingly to re-enable:

You already asked this question just a few posts up from this. :) Wait for an answer.
[Google Pixel 6 Pro] Zilla0617:
That sucks I hope i don't have to wipe my phone again when the images come out
[Google Pixel 6 Pro] snovvman:
These two posts contain very important information for those who want to update future patches without wiping. At this time, it's probably the best chance we have. @V0latyle, to date, have you observed success with these procedures in avoiding the need to wipe? Thank you.
[Google Pixel 6 Pro] V0latyle:
It's hit or miss honestly.