yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
How? What are your settings? Which Magisk modules did you install in addition to SafetyNet Fix 2.1.1?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Just Riru as is required for USNF. Using MagiskHide on all subcomponents of Google Play Services, Google Play Store, GPay, and other security/DRM sensitive apps.
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
I have Magisk 23001 with 3 modules installed: Riru 2.6.1.2..., Systemless host, and SafetyNet 2.1.1

Magisk fails Basic integrty and CTs Profile Match

what am I doing wrong?
[Google Pixel 5 Guides, News, & Discussion] andybones:
I am still on A11 but from looks you have 23014 installed.

Here's what mine looks like for 23000

Magisk f822ca5b beta (Android 5.0+) APK Download by topjohnwu - APKMirror

Magisk f822ca5b beta (Android 5.0+) APK Download by topjohnwu - APKMirror Free and safe Android APK downloads

www.apkmirror.com
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
Thanks for responding.

I'm on Android 12 with Magisk Canary 23001, the update is Magisk Canary 23014.

You are using Magisk Stable 23.0 it has no updates.
[Google Pixel 5 Guides, News, & Discussion] andybones:
Very welcome,

Wish I was more helpful.

It says 23014 is installed..

From this post by @V0latyle is why I bring up 23001,

"I am able to get SafetyNet to pass on my P5 with Magisk 23001 and Universal Safetynet Fix 2.1.1"

But he will be of more help when he see's this, I'm sure. :)
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
Thanks, I saw his post. I hope you're right about him being more help. I know he's more knowledge than I on the subject. :)

I think where it has Magisk is the version of Magisk, and where it has App is the version of the Magisk App that is installed.

o_O What is weird is I never updated Canary to 23014, so is the app installed?
[Google Pixel 5 Guides, News, & Discussion] andybones:
Well Magisk Manager and Magisk combined into 1 app not long ago (I'm sure you know, but for those reading that don't..),

and I've never installed a canary version, but you're probably correct.

And you have it set to canary in your settings, so it may of auto updated? I know I've had it happen before to me, and caused me a bootloop, so not I revoke the magisk permissions for installing applications.

I'd personally just try to uninstall the Magisk App in settings > apps (not Magisk entirely, just the App), and install 23001.
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
I don't think it auto updates. It just notifies when an update is available.

AFAIK, the only way to tell which version of Magisk App is installed has already been covered.

Magisk log:

...---Magisk Logs---

f822ca5b (23001)

01-18 19:30:46.743 802 802 I : Magisk f822ca5b(23001) daemon started...
[Google Pixel 5 Guides, News, & Discussion] andybones:
Your phone.. You asked the question..

I'm just trying to help, my friend.

To me it's rather obvious which version is installed.. as it says. But you can simply go into App Info, as I earlier suggested.

And since you mention it. Unless others are using your device, you updated to 23014.. unintentionally, I suppose, but you do have it set to canary, so.

To me the issue lays within the for testing purposes canary version, and again suggest to roll back to 23001. As it's been mentioned that it's working on that version. I suggest this because from my limited understanding, most the changes are to the app, at the moment (removing Magisk hide, removing modules repo, etc).

Also the answer probably already lies within the dedicated Magisk thread.
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
First, I do understand you are trying to help and I am truly appreciative of your help. My responses are feedback only.

Second the Magisk log shows I have Magisk Canary 23001 installed (see edited post above).

I missed the suggested App Info information. I'll check it and report back.
[Google Pixel 5 Guides, News, & Discussion] andybones:
I misread sorry, I edited my post.

I'm not trying to be argumentative or anything, just trying to help, and I'm sure this question and the answer will ultimately help another. :)

You do in-fact have MAGISK 23001 installed, the APP however is v23014, so v23.14?

And You can simply uninstall the APP, which doesn't remove Msgisk, and then install v23.1 (23001)

This is just my understanding of the situation/and my suggestion. :cool:
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
@andybones, you the man! :)

I checked App Info and you were right: version 7e9d4512 (Magisk 23014).

This is the first time my dumb a$$ ever checked it for Magisk. :( I just assumed, wrongly, that when I patched the boot image with Magisk Canary 23001 it would install the Magisk Canary 23001 App.

Thanks for being patient with me.

Will removing/uninstalling the Magisk App unroot my phone?

How can I install Magisk Canary Manager/app?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yes. Can't use Magisk 23010+ with USNF and MagiskHide as are currently available; Magisk 23010 introduced Zygisk, thereby rendering Riru nonfunctional, and by extension all modules that depend on it.

Root is in the boot image. The manager is separate. You can have a rooted device without a manager app, or a manager app with no root. Removing Magisk as we usually do does not remove root; to unroot, use "Complete Uninstall" within the app.

You have two options here:

1. Go back to Magisk 23001, install Riru and USNF 2.1.1, configure MagiskHide on the 2 apps I mentioned (Play Services, Play Store) as well as any others that might be security/DRM sensitive

2. Update the patch on your kernel to 23014, and support @kdrag0n via Patreon for beta access to USNF 2.2.0; no Riru required, and configure DenyList same as above.

I'm of the "if it ain't broke, don't fix it" mentality; since pre-Zygisk works fine on our devices, I don't see the need to update until USNF 2.2.0 is public. Be glad you don't have a Pixel 6...Magisk pre-23010 won't even patch the boot image.

If you wish to downgrade, I would suggest using Complete Removal, followed by a reboot. Then, install Magisk 23001, and start over with rooting.
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
No problem, I've misread on several occasions.

You're good, you answered my questions before I asked them.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Check the last post, I gave you some answers.

Good luck
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
Ok, now I'm confused. o_O According the the Magisk Log I have Magisk 23001. @andybones suggest I remove the Magisk Canary 23014 Manager/app in settings and install the Magisk Canary 23001 Manager/app.

I do not know how the Magisk Canary 23014 Manager/App got installed. I installed the Magisk Canary 23001 Manager/App, patched the boot.img and flashed it:fastboot flash boot magisk_patched...img

You are suggesting I do a complete uninstall, reboot, install Magisk Canary, and reboot.

Does that mean andybones suggestion will not work?

AFAIK, your method requires a wipe. Correct?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Your kernel is patched with Magisk 23001. But, you have the 23014 app installed.

The app is the Canary app is the Manager app. As I explained previously, the boot image patch and the app are separate. For the sake of simplicity, let's refer to the boot image patch as "Magisk root" and the app as "Magisk app. When you installed the Canary app, that IS Magisk Manager. Way back when, we used to have to flash a separate zip in recovery to patch the boot image.

No....you can certainly try uninstalling the 23014 app and installing 23001. However, the last time I tried to downgrade, I lost root when I installed the older version of Magsik - and Magisk has to have root privileges in order to clean everything up for a complete removal. I'm just suggesting this to be safe. Uninstalling Magisk through Android app manager doesn't clean everything up so there can sometimes be issues when you install a different version of Magisk, to where it won't see the kernel root.

Incorrect. I didn't say anything about a wipe. Just use Complete Uninstall within the app, then downgrade. You'll be fine. In case my instructions weren't clear:

Open Magisk. Tap "Uninstall", then "Restore Images". Once complete, tap "Complete Uninstall". Your device will reboot without root or the Magisk app.

Install Magisk 23001. Re patch the boot image the same way you did on initial root. Copy boot image back to PC and reboot to bootloader.

Flash patched boot image, and reboot device. Magisk app should show root.

Point of note: If you DON'T use Complete Uninstall, and you lose root when you reinstall Magisk, you will have to wipe data to get root back.
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
I am thoroughly Confused. o_Oo_Oo_O

Give me a moment to get it together.
[Google Pixel 5 Guides, News, & Discussion] andybones:
Please don't uninstall. Did you read my post, Sir?

I even mention to NOT.

You uninstall the Magisk app like any other App in App info..

Then, just install 23001 like normal.
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
Yes Sir, I read it thank you! :):):)
[Google Pixel 5 Guides, News, & Discussion] killchain:
No, I just followed what used to work before with Magisk. My goal is to, if possible, go forward without having to wipe.

Right now I am back with stock boot.img, phone is running fine (but without root).

If I understand you correctly, I should:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

... right?

Is my understanding correct that this disables verifications for any subsequent images I flash (and me not having done it is why it failed for me)? How do I avoid getting to a corrupt state and having to wipe (what the other dude mentioned)?

At this point, would I be able to boot with the patched boot.img from before?

If yes, will I then be able to do a direct install of Magisk?

If no, do I need to re-patch boot.img after the procedure with vbmeta.img?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Not to be rude, but it seems to me that you didn't read my instructions, tried to do it your own way, and discovered that it doesn't work the same as before. Please go back and read the guide at the beginning of the post; most of your questions have been answered.

The corruption issue is a new one and we haven't found a solution or a cause yet.
[Google Pixel 5 Guides, News, & Discussion] killchain:
No offense taken.

Went ahead again. Flashed vbmeta as per the instructions, now phone is in a corrupt state - first attempt to boot it shows the unlocked bootloader warning and everything, then Google logo shows up for a second, reboots again and then shows me the recovery screen with the corrupt state. I could go back to fastboot with holding VolDn while powering up. What are my options?

Edit: just found out that flashing vbmeta with no flags gets me out of the corrupt state, i.e.

fastboot flash vbmeta vbmeta.img
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Interesting. I will have to test when I get home from work.

I assume you're running the stock boot image? Have you tried live booting the patched image?
[Google Pixel 5 Guides, News, & Discussion] killchain:
Yes, stock boot.img. Haven't tried live booting. Right now I want to try doing something and at the same time I want to just wait a bit to see if John Wu releases a new version of Magisk dealing with these issues.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
This isn't a Magisk issue.

Try flashing the vbmeta from the beta 5 with the disable flags set.
[Google Pixel 5 Guides, News, & Discussion] killchain:
Tried that, no dice.

If it's not a Magisk issue, what kind of issue is it?

Edit: I managed to boot a patched boot.img after flashing vbmeta with no flags, then succeeded in installing Magisk directly. However, when I rebooted, I was back at the same problem from before (fastboot saying "failed to load/verify boot images"). I had to reflash vbmeta and boot to recover.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I don't really know where to place the blame, as we don't fully understand the problem.

Previously, on the 12 Beta, simply reflashing flashing vbmeta with the disable flags was enough to disable boot verification so we could flash patched images.

The problem now, at least for some users, is that flashing vbmeta with the disable flags causes a corruption error. It's unknown as to why.

Its not a Magisk issue because -any- modification to the boot image will trip the verification check, and there is literally no way to hide code that has been changed. Dm-verity was developed specifically to prevent this - the code from the actual block devices is hashed, so there's no way for any sort of agent to "spoof" a valid image.

The reason why Magisk Hide worked, at least previously, was because systemless root resides in the kernel - which is the first part of the OS to load. Therefore, Magisk would load with the kernel, with higher privileges than system processes, and could then block those system processes from detecting root.

But, because dm-verity reads the actual code on the hardware, it will always detect a modified boot image. That in of itself isn't a problem, as long as we are able to disable vbmeta verification as well, which essentially "ignores" any differences between the vbmeta image and the hash generated from /boot.
[Google Pixel 5 Guides, News, & Discussion] rester555:
@V0latyle @killchain I followed the steps that OP posted and every time I got a corrupt system message through recovery mode. What I ended up doing differently from OPs instructions was putting the following code for the step of disabling dm-verity and verification, fastboot --disable-verity --disable-verification flash --slot=all vbmeta vbmeta.img

I am not sure if this is the correct solution, but I have had bootloops before with magisk when flashing the patched image, so one example from the XDA community was to do --slot=all so that you patch the boot image on slot a and b on pixel devices. This led me to add the same line of code with the disabling flag code that OP posted. This got me out of the corrupt system recovery message on my pixel 5 and booted into A12 as rooted.
[Google Pixel 5 Guides, News, & Discussion] killchain:
So... there's something changed between Beta 5 and Stable, and it's unknown yet what exactly?

Also, is it clear what's happening "under the hood" here, i.e. what has happened differently when installing an OTA compared to flashing using Android Flash Tool? As far as I understand, disable verity and disable verification only apply to flashing vbmeta. Maybe it's done before flashing system? If that's so, would it work if I flash vbmeta with flags disabled and then dirty flash system over my current one with no wiping? Is it known why the wiping step is required, i.e. does it necessarily require wiping everything?

I'd be okay to wipe and restore my stuff afterwards if I'm sure that this method will 100% work - but at this point I'm not.

Has root persisted for you after a reboot? Can you (or anyone else) expand on why it might concern both slots?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Interesting. Using the --slot-all flag should be unnecessary, because as far as I know, using the flash command without the slot flag will flash all slots in that partition.

Also, did you actually bootloop - as in phone kept rebooting? Or did you get stuck in bootloader with an error message?

Also, I forget, did you wipe data at any point?
[Google Pixel 5 Guides, News, & Discussion] killchain:
fastboot --help says otherwise:

--slot SLOT Use SLOT; 'all' for both slots, 'other' for
non-current slot (default: current active slot).
[Google Pixel 5 Guides, News, & Discussion] hominine:
Pixel 5a here. Was rooted on the latest beta and followed OPs instructions to a corruption error during boot.

Tried reflashing a la --slot-all to the same error. Ultimately reflashed both slots with stock boot.img and vbmeta.img and booted in just fine although without root.

Looking forward to finding out what the issue is and appreciate the banter. :coffee:
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Good to know. I will add this to my instructions.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
You wouldn't have to reflash vbmeta, just use the flags when you dirty flash the system image:

fastboot --disable-verity --disable-verification update redfin-image.zip

In the off chance this gives you a data corruption error, then yes you'd reflash vbmeta, but AFTER you dirty flash the factory update - because the zip contains the stock image for vbmeta.

Wiping is required if you update from a previous version of Android using the factory image. It should not be required if you update from 12 Beta.
[Google Pixel 5 Guides, News, & Discussion] ggkameleon:
Hi ! I make all your thread but doesn't work !!! After sideload and restart it no mistake and restart to bootloader and flash vmbeta and patch boot the phone restart to "try again or wipe all"

Finaly I loose all my data and do flash factory image but big mistake I stay always on fastboot !!! Wont restart ?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Reboot to bootloader (use the buttons on the phone)

Try to reflash vbmeta

fastboot --disable-verity --disable-verification flash --slot=all vbmeta vbmeta.img

If that doesn't fix it, reflash vbmeta without disabling verification:

fastboot flash vbmeta vbmeta.img

You'll have to reflash the stock boot image too.

This will get you out of a boot loop, albeit without root, while we try to figure this out.
[Google Pixel 5 Guides, News, & Discussion] rester555:
@V0latyle I started with flashing the factory image and doing the original patched image flash with magisk and got the error message you describe in op where it says failed to load/verify boot image. I then recovered and flashed and wipred factory. I then came here and read your thread, did your steps, and it boot looped to recovery saying, and I am paraphrasing, system is corrupt, reload or factory reset? Then I went into fastboot and did adb of factory image, this time I got through initial setup and went back to fastboot and did all your steps with the --slot=all command for the flags.
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
Superb Guide

Has anyone successfully preformed this step: To update to Android 12 via ADB using the factory image: (Wipe required)?
[Google Pixel 5 Guides, News, & Discussion] creezalird:
I did, on 4a5g, but I just changed the flash-all.bat script inside the zip and add the disable flags.

So far no issue in regards to flashing/root. Working wonderfully. Many thanks @V0latyle

Besides the flags, everything else is the same with what I have been doing on Android 11 stocks
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
When I tried to downgrade from 23011 to 23001, I lost root and had to wipe...which is why I recommended doing the uninstall.
[Google Pixel 5 Guides, News, & Discussion] andybones:
Shoot sorry man, was late last night for me, didn't catch that you suggested that before I had posted.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
If someone has patched their kernel with 23014, then rolls back to 23001, they'll lose root and won't be able to get it back without a wipe. Reflashing the original boot image doesn't fix it. It has something to do with signature keys used by Magisk; if you lose root, you have no way of cleaning up so you can start over. That's not the case here, obviously, but I'm just sharing what I've learned the hard way.
[Google Pixel 5 Guides, News, & Discussion] andybones:
Definitely appreciate you sharing this man, would hate to send someone off with the wrong info, and stuck needing to wipe, as I know how rough it is. Thanks again man
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Universal SafetyNet Fix 2.2.0 is out for public access; this version has been ported to Zygisk.
[Google Pixel 5 Guides, News, & Discussion] Rumsfield:
Worked perfectly, no more having to wipe hopefully for the next year.
[Google Pixel 5 Guides, News, & Discussion] hssxda:
I just rooted my Pixel 5 Android 12 and am failing safetynet. Is there a guide / tutorial on here for fixing this?

I found this guide here is it accurate?
[Google Pixel 5 Guides, News, & Discussion] hssxda:
I followed that tutorial and installed universal safety net 2.1.2 with riru and now I pass safetynet in magisk but Google pay still doesn't work? Can I hide root from Google pay somehow?

Edit: Got it working by going to "Hide the Magisk App" in the settings menu and renaming the app
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
This is what I did to get Google Pay workingwith Magisk 23001 and USNF 2.1.1:

- Installed Riru and USNF 2.1.1.

- Enabled MagiskHide on all components of Google Play Services, Play Store, and GPay

Rebooted, everything works great.

When USNF 2.2.0 was released to public, I upgraded to Magisk 23014, enabled Zygisk, enabled DenyLIst on the same apps (all subcomponents), and installed Universal SafetyNet 2.2.0.
[Google Pixel 5 Guides, News, & Discussion] hssxda:
What are the advantages of USNF 2.2.0?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
It's been ported to Zygisk, so you can use it with Magisk 23010 or newer. USNF 2.1.1 is written for Riru, which requires Magisk 23001 or older.
[Google Pixel 5 Guides, News, & Discussion] vaibhav palande:
Hi,

I have a rooted (using this guide) Pixel 5 on Android 12 with,

Unlocked bootloader​

SP1A.211105.002.A1​

Magisk canary 23015 and USF 2.2.0​

I am looking to follow steps in the post above to install December security update SQ1A.211205.008

without having to wipe.

I have some questions:

Bootloader and radio image zip files are NOT the downloaded factory zip. These are inside the downloaded factory zip. Correct?

To check if I need bootloader and radio update, can I just compare the names of the files for bootloader and radio in the two factory zip files (current vs new) ?

If yes, I think I need to update both.

Current (SQ1A.211205.008)	New (SP1A.211105.002.A1)
bootloader-redfin-r3-0.4-7758093

radio-redfin-g7250-00161-211008-b-7807492	bootloader-redfin-r3-0.4-7617468

radio-redfin-g7250-00147-210830-b-7686829

I have a unlocked bootloader. If I update bootloader using following, will I have to unlock the bootloader again? What will it do to my root?

fastboot flash bootloader [bootloader image]

First post in this thread says,

What precaution do I have to take to avoid bricking my device?​

​

Thanks in advance
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Correct - inside the factory zip you will see radio-number.img (the radio/modem image) and bootloader-number.img (the bootloader image).

Yes.

You're on the right track.

Updating or downgrading the bootloader does not affect bootloader lock.

Make sure that you only flash the bootloader with the bootloader image - do not accidentally use any other image.

The safest and most foolproof way to update is via the Android Flash Tool - it automatically updates your bootloader and radio if necessary. However, you will still need to download the factory zip and manually patch the boot image.
[Google Pixel 5 Guides, News, & Discussion] f8lxninja:
I tried following the guide, but when I flash the patched magisk boot image it gets stuck at the G logo with the loading bar and refuses to continue. If I reflash the stock boot image it works just fine. Is it because I didn't uninstall magisk before performing the OTA update manually?