yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5 Guides, News, & Discussion] andybones:
Just a few helpful things to check, as many things can Trigger SN,

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

www.didgeridoohan.com

And it may be possible that one of the Magisk betas need to be used to get it passing, but tbh I haven't read enough about SN/A12 just quite yet, but this thread, if you haven't seen it yet, has a bunch of information on the state of Magisk, and those having issues passing SN with A12.

https://xdaforums.com/t/magisk-general-support-discussion.3432382/page-2427
[Google Pixel 5 Guides, News, & Discussion] ]grimm[:
I followed a very similar initial set of steps on my Pixel 5 that was running Android 11 with magisk prior to updating to Android 12 without wiping data.

Flashing vbmeta.img to one or both slots with the --disable- flags (or updating with the same flags and not wiping) causes my phone to enter a corrupt state. I am able to boot again if I flash vbmeta.img without any flags and ensure that I also flash stock boot.img. However, I am still able to enter a working rooted environment by booting magisk_patched_boot.img without vbmeta having been flashed with any flags. I am not able to use magisk to install directly after booting the patched image so I am effectively stuck in a state where I can boot into a rooted image using fastboot but will revert to an unrooted environment if I have to reboot my device. I have not wiped my device.

GPay worked for about a half dozen contactless transactions throughout the day while running a rooted environment (with the understanding that a few transaction over a relatively brief period of time are not strong evidence of future functionality.)
[Google Pixel 5 Guides, News, & Discussion] ZeoFateX:
Yeah not sure. Maybe I need to reflash again and make sure everything was done in the correct order. You are definitely passing. Did you have to run props config and stuff or no?

Edit: Weird. Disabled LSposed and Props Config modules, rebooted and I'm passing now. Only Riru and Universal SafetyNet Fix installed.
[Google Pixel 5 Guides, News, & Discussion] warrencoakley:
Pixel 4a 5G stock come from Android 11.

When I used adb and flashed the img and then the patched Magisk img it got stuck at the fastboot screen. The only way to get out of it was to re-flash the factory img again.

The only way i was was able to obtain root was to wipe and re-flash. Such a pain. Hours re-loading apps, logging back in etc.

I decided to try a different method so to speak so I followed this guy's way and it worked flawlessly. Took me half the time actually as I use to take the factory img, boot img, radio and bootloader out and flash individually.

Anyway I'm rooted (for now) My concern is the security updates to come if I will obtain route or need to wipe everytime (which there is no way in hell I'll be doing) Just got to wait and see.

Here is the YouTube video:
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
This data corruption issue did not appear on the 12 Beta, which is what this guy is showing. Also, if you did it exactly as he showed, you wiped data.

It's also unclear as to whether Boot Verification was implemented on the 4a.

It does seem to make a difference on the upgrade path taken. I installed the OTA yesterday on 12 beta 5. When I got home, I tried to use the Android Flash tool, and still ended up with the corrupted data error.

Magisk Canary is not necessary; I successfully rooted using Magisk 23.0.

So the remaining issue seems to be rooting without wiping data.

Who's been able to gain root on Android 12 after upgrading without a data wipe?
[Google Pixel 5 Guides, News, & Discussion] paratox:
Would it be possible to boot a patched boot.img for temporary root that i would need for app backups (swift backup) without data loss?

When i tried it i got the error "(bootloader) boot.img missing cmdline or OS version".

I´m afraid i did the OTA update without thinking about backups. 😅
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
If vbmeta and boot are untouched, then yes...just make sure it's the boot image for that build, as I tried this with the 12 Beta 5 boot image, and I got the corrupted data error.

You can potentially run your phone this way, just remember that you'll lose root if you reboot.
[Google Pixel 5 Guides, News, & Discussion] roundaway:
Pixel 4a 5G and took the OTA. Ran into the corrupt data and reflashed vbmeta.img and the boot.img. Rebooted to System. Then rebooted to bootloader and ran fastboot boot magisk_patched.img (or whatever name you gave the patched boot.img) and am temporarily rooted. This way I was able to get TitaniumBackup to do it's thing and then copied the data to a desktop.

Hoping for a no data wiping solution just to save the pain of an initial setup.
[Google Pixel 5 Guides, News, & Discussion] HumorBaby:
Pixel 5:

I have successfully (seemingly) gone from a 12b5 to release 12 without a data wipe. Root, safetynet, GPay, are unaffected after 2 reboots so far.

I went in prepared to have to wipe after flashing vbmeta with the disable flags, but I didn't need to. Maybe the trick is to sideload OTA upgrade, then flash vbmeta and patched boot image without rebooting in between??

Anyway, here are the details:

Just like @V0latyle and others , I started from 12b5 (clean wipe flash coming from Android 11), rooted, then set up Riru, LSPosed, etc. for safetynet+GPay.

Back when I did the clean wipe 11 -> 12b5, I had used --disable-verification and --disable-verity in flash-all.sh:

...
fastboot --disable-verification --disable-verity -w update image-...
...

Process to upgrade to release:

- Download release factory AND OTA images

- Extract vbmeta.img and boot.img from the factory image

- Patch boot.img using Magisk App on 12b5 phone and pull back to my PC

- sideload OTA without reboot, switch to fastboot mode

- flash vbmeta.img

- flash magisk_patched_boot.img

- reboot, breath sigh of relief after successful boot (and reboot) with root+data intact

pseudo-commands:

$ adb reboot sideload
$ adb sideload redfin-ota-sp1a.210812.015-2596fc07.zip
## Once OTA upgrade is complete, you should be dropped into recovery menu.
## Pick "Boot to fastboot"
$ fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
## Disable verity and verification for consistency
$ fastboot flash boot magisk_patched-23001_BLAHB.img
$ fastboot reboot
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Interesting. Thank you for sharing this.

I had taken the automatic OTA. So maybe you're onto something. We will have to have someone test this, as long as they're not afraid of potentially having to wipe.

Just for sh!ts and giggles, see if you can boot the patched 12b5 boot image?
[Google Pixel 5 Guides, News, & Discussion] HumorBaby:
Nope, booting the patched 12b5 gives me the "data corrupted" error during boot that I assume many others are seeing. Rebooting by choosing "Try Again" gets me back to my rooted release 12 as expected.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
But you can boot either the stock boot image, or the patched boot image, as long as they're from the new build. It almost sounds like there's a third element involved in verified boot besides dm-verity and vbmeta verification.

Looking at the details on Android Verified Boot, the only other element I can find is rollback protection - but from what I can see, that's disabled on an unlocked bootloader. There's a corrupted data screen for EIO mode, but we already get the UNLOCKED screen during boot.

Here's the odd thing:

The corrupted data message we have been seeing seems to appear in recovery - which resides in the /boot partition along with the kernel.

In the details on how dm-verity works, it says that the protection lives in the kernel.

So maybe we need to use the --disable-verity flag when flashing /boot as well? I'm just guessing here, but perhaps there's some sort of check where dm-verity looks for verification to be enabled on /vbmeta, and if it doesn't find it, goes into recovery mode with the "corrupted data" message.

The problem with this theory is that it happens with older boot images too, such as the beta, where we did NOT see this issue.

I did find this thread which details how Magisk can be used to disable dm-verity: (Magisk 23.0 does not appear to be able to do this)

Ultimately, someone is going to have to be the guinea pig and test some ideas while we try to sort this out. Volunteers?
[Google Pixel 5 Guides, News, & Discussion] HumorBaby:
The --disable-verity flag only applies when flashing vbmeta (for Pixel 5, which has a vbmeta partition)

fastboot/fastboot.cpp - platform/system/core - Git at Google

(using it when flashing boot won't do anything)
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
This is from Android 11 though.

But, the fastboot.cpp from Android 12 S1 looks identical.
[Google Pixel 5 Guides, News, & Discussion] HumorBaby:
Yeah that's just the file I quoted to find a balance between the latest platform-tools version and the version that most people are probably running.

Here is the same in the latest master version:

fastboot/fastboot.cpp - platform/system/core - Git at Google

Despite being in Android source tree, these tools are relatively independent of the android version anyway.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Well, the question still remains on disabling verity in the kernel. It sounds like the only way to do this currently is hex modification of the image itself, because I can't find the option to disable AVB in Magisk.

Boot image verity seems to be the most likely explanation, given how the device ends up in recovery mode after boot fails.

I did notice on the 12 Beta 5 that if /vbmeta was empty, bootloader would come up with the same "unable to verify/load boot images".
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
So Magisk Canary was released yesterday:

Magisk 23010

Someone who is temp rooting want to patch their boot image with this and see what happens?

Also, Magisk Hide is no longer, so here's what you have to do to pass Safetynet (the check is no longer in Magisk so you'll have to use an external app)

In Magisk:

Remove Universal Safetynet Fix and Riru, if you have them installed, Reboot.

Launch Magisk again

Settings > Magisk:

Enable Zygisk

Enable Enforce Denylist

Enable for Google Play Services components: (I just enabled for all subcomponents)

com.google.android.gms

com.google.android.gms.unstable

That should be enough to pass Safetynet. Don't forget to hide other apps such as banking, GPay, DRM (Netflix, Amazon Prime Video, etc)
[Google Pixel 5 Guides, News, & Discussion] killchain:
Tested that already yesterday, didn't work.

https://xdaforums.com/t/guide-updat...2-read-the-notes.4345627/page-7#post-85824449
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
You didn't disable verity and verification?
[Google Pixel 5 Guides, News, & Discussion] killchain:
No, I tried a direct install from within Magisk Manager (having live booted the previously patched image).
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Try this:

Patch the image file using 23010

Reflash vbmeta, disable verity and verification

Flash the patched file, see if it boots

If it doesn't, you should be able to just reflash vbmeta and stock boot image to recover.
[Google Pixel 5 Guides, News, & Discussion] killchain:
Same old, system corrupted again after trying that.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Okay. So it has nothing to do with Magisk for sure.
[Google Pixel 5 Guides, News, & Discussion] pgcranie:
So I thought i followed these steps but my safetynet check failed still.

I used this app to test it.

SafetyNet Test – Apps on Google Play

SafetyNet device compatibility test

play.google.com

Im not sure if it will matter, all my apps seem to function fine but any help with fixing this would be appreciated.

I attached a pic of the test results
[Google Pixel 5 Guides, News, & Discussion] thiago_oliv:
Is this thread only about rooting? My phone is refusing wireless charging after Android 12. It begins charging than it drops, like a failsafe or a problem. Is it the same with you guys? Tried in 3 different chargers (none is Google recommended, but of good brands)
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Universal Safetynet Fix helps fix that; unfortunately it has not yet been updated for Magisk 23010, and also depends on Riru, which is not compatible with the new version. If you want to use the newest version of Magisk, you'll have to use the older version of USNF (1.2.0) that doesn't use Riru, then you'll have to use MagiskHIde Props Config to fix CTS.

I didn't want to go through all that, so I just downgraded back to 23001 and used MagiskHide + Riru + Universal Safetynet Fix, and I'm passing Safetynet including CTS.

This thread is intended for discussion of how users upgraded to Android 12, as we are currently looking for a solution that does not require a data wipe.

If you have a question or are looking for support, please feel free to post your question in the Questions and Answers subforum; don't hijack other threads for support with an unrelated problem.
[Google Pixel 5 Guides, News, & Discussion] dlb134:
Gdamn, I really want to run lawnchair but rooting android is such a pain in the butt these days.

Also, I kinda like my gpay - wish I had sideloaded the OTA rather than clean flashed :/

Hopefully you guys can figure something out, watching this thread anxiously
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Well, wiping /data isn't the end of the world, considering how much of our data is backed up in the cloud. You'll lose anything you downloaded, but your apps and texts should all be synced with Google Drive. The biggest PITA is just having to set everything back up again.

I hope we are able to figure out the problem too. We are running out of ideas, and I think what we really need is someone much more experienced to take a look at what changed so we can figure out a workaround, or at least figure out if we are doing something wrong.
[Google Pixel 5 Guides, News, & Discussion] warrencoakley:
With the announcement of Magiskhide been removed it's looking bleak. Had mine up and running perfectly until the latest Canary update triggered all the apps I was hiding including safetynet. I'll wait until the November update but if it's a pain like it was this time I reckon it's time to lock the bootloader
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
No, just downgrade back to Magisk 23001 and you'll be fine. There's no reason why you absolutely have to use Magisk 23010 yet. I upgraded to 23010, discovered that SafetyNet no longer passes due to CTS profile mismatch, so I downgraded back to 23001, and using Magisk Hide + Riru + Universal SafetyNet Fix, I have SafetyNet pass.

A significant thought that could use some testing:

Basically, we need to determine if it matters when you flash vbmeta. Here's what needs to be tested:

- Factory flash Android 12 with a wipe; do NOT disable verity and verification

- Set up and use your device

- After everything is set up (download all your apps) attempt to reflash vbmeta with verity and verification disabled, as well as a patched boot image.

If this is successful, this means we shouldn't have to wipe every time we take a monthly update.
[Google Pixel 5 Guides, News, & Discussion] Neuken6969:
Hello all, I'm running A11 rooted. I REALLY don't want to wipe my phone, can I flash all without the -w and upgrade to A12 u rooted???
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
If you want to upgrade and keep your data, I would recommend using the OTA.

@HumorBaby has a guide on upgrading from the 12 Beta to 12 Stable without wiping data, but he did wipe when he installed the 12 Beta. You can use the OTA to upgrade from Android 11; just be aware that so far we have not found a way to upgrade AND keep data AND root.

If you choose to try this and are able to root without wiping /data, please post your results here.
[Google Pixel 5 Guides, News, & Discussion] Neuken6969:
Right now, don't care about root. I would flash the OTA? Confused how to the OTA when rooted in A11
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Download the OTA from Google and sideload it via ADB.

To everyone else:

I have bad news.

Flashed /vbmeta and /boot back to stock. Booted fine.

Flashed patched boot image. "failed to load/verify boot images" as expected.

Flashed /vbmeta with disable flags. "Cannot load Android system. Your data may be corrupt."

Uh oh...

Flashed /vbmeta and /boot back to stock, booted patched image.

Folks...I hate to say it, but unless we find a way around this, we are going to have to wipe every time we reflash /vbmeta.

TBH I kinda want to go back to the 12 Beta just because we didn't have to deal with this sh!t.

Tried dirty flashing 12 Beta. Corruption error.

OTA'd the stable and flashed vbmeta/boot in fastboot. At least I'm running again, but I've lost root, although I suspect this to be a Magisk issue. I'm pretty sure I used 23010 to patch the boot image, but even with 23010 installed, no root, so I can't clean out Magisk and start over.

Why is this such a pain in the ass? If it ain't broke don't fix it, but they had to go and make things harder for us.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Magisk was updated to 23011 in the past 24 hours....someone want to see if this makes any difference?
[Google Pixel 5 Guides, News, & Discussion] ]grimm[:
Nothing appears to have changed with respect to the issues in this thread as far as I can tell. I am now live booting a 23011 patched image and that continues to work as expected.
[Google Pixel 5 Guides, News, & Discussion] Spookymyo:
How did you disable verity and certification? I've tried using the flash tool and it always fails.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I've done it manually as well as by using the flash tool.

Manually, you just add

--disable-verity --disable-verification

when flashing vbmeta.

So like this:

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

Via Android Flash Tool, you just check the boxes.

I assume your bootloader is unlocked?
[Google Pixel 5 Guides, News, & Discussion] Neuken6969:
Ok .... Well I did not apply the OTA, for weeks my phone has an Android 12 update and always failed because I'm rooted. Well it took the update and I'm A12 not rooted. Weird
[Google Pixel 5 Guides, News, & Discussion] Neuken6969:
Now IF I want root use an older version of Magicka and still patch and flash in adb?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
That's because we have systemless root; root is patched into the boot image. When you take an update, /boot is overwritten with the new image, which is why you lose root.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
For those of you who successfully updated to and rooted the November release without wiping: How did you do it?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
We finally figured it out.

Turns out that once dm-verity and vbmeta verification are disabled, you CANNOT let the system boot with them enabled. If /vbmeta gets flashed, such as during an OTA or a factory image, and you let it boot into system, disabling verity/verification is going to require a wipe.

Unfortunately, for those of you upgrading from Android 11, there is simply no way around this - for permanent root, verity/verification must be disabled, and to disable verity/verification, /data must be clean.

I will be updating my guides shortly.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
@Anonshe any ideas for getting around the data wipe requirement when disabling verity/vbmeta, or is it simply a fact we must live with?
[Google Pixel 5 Guides, News, & Discussion] Anonshe:
It's a hard requirement just like when unlocking the BL.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Well, I just had a thought....

What if...someone were to reflash vbmeta while they're still on Android 11, then perform the update and reflash vbmeta again before booting?

We need a guinea pig
[Google Pixel 5 Guides, News, & Discussion] kroogar:
edit:

And of course I found the setting moments after asking this... It's the Accessibility Menu... sorry for the inconvenience :-(

Sorry if this has been answered... I just don't know what to search for...

After the upgrade to Android 12 on my Pixed 5, I have this little annoying green button with three dots on my home screen. I can move it around but I can't for the life of me figure out how to turn it off... It's some sort of "quick access" to settings.

Anyone?
[Google Pixel 5 Guides, News, & Discussion] Anonshe:
Do you mean having vbmeta disabled previously on A11, then flashing the factory image and disabling vbmeta before booting? That works.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
That's exactly what I mean. The question in my mind is whether disabling vbmeta would require a wipe on Android 11. It wasn't necessary to run a patched boot image, so if it doesn't require a data wipe, it may just be the ticket for those who want to upgrade from 11 to 12 and root without wiping data.
[Google Pixel 5 Guides, News, & Discussion] Anonshe:
I should've tested this but I'm 90% sure, it didn't need a wipe as encryption was not tied to verified boot on Pixels till A12.

This can be tested, I'd suggest having backups though as jumping Android versions always have the possibility of a race condition appearing.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Interesting that it still wasn't on the 4a and earlier devices even on Android 12. Hardware limitation maybe?
[Google Pixel 5 Guides, News, & Discussion] Anonshe:
SD855 devices should've similar security levels as a Sd765G so I'd speculate it's probably Google just paying attention to the most recent family before the 6 series.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yeah, it seems this doesn't affect 855 devices at all. Only 765G and Tensor.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I'm still getting an update notification...
[Google Pixel 5 Guides, News, & Discussion] thatsupnow:
Hmm that's weird I'm on the same build and rooted and haven't got that message at all
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I might have to dirty flash the factory image again, then re patch the boot image AFTER the "update".

Also, I'll compare my bootloader and baseband version to what's in the zip.
[Google Pixel 5 Guides, News, & Discussion] Spookymyo:
Thanks. I tried that. Not sure how to verify but I didn't get an error. And yes my bootloader is unlocked.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
You would know if you had a problem as soon as you tried to boot.
[Google Pixel 5 Guides, News, & Discussion] ggkameleon:
Hi ! I'm on A12 november clean install & disable verity & verification Root magisk canary.

But after flash a mod I loose the root 😔

For Root magisk again I do flash before the original boot image and restart to remove correctly the root.

But do flash disable verity & verification vmbeta before ?

And after restart install manager flash boot img. And on fastboot flash vmbeta disable verity & verification and flash boot img modified it's right ?

Thanks
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
There is a known issue where Magisk may "disconnect" from root in the kernel due to a signature mismatch; the way to avoid this is to perform "Complete Uninstall" within Magisk itself.

If root is lost because of a module or some other problem, there's no way to really clean up the Magisk installation so that root will work again, unless you perform a factory reset.

You do not have to reflash vbmeta if you're restoring the factory boot image. Vbmeta only needs to be flashed if you are updating.
[Google Pixel 5 Guides, News, & Discussion] ggkameleon:
Thanks for awnser.
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
Is anybody else getting prompts to update to Android 12 after they've already updated to Android 12?
[Google Pixel 5 Guides, News, & Discussion] kfhughes:
Yeah, it just popped up on mine an hour ago.
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
Curious. 🤔 ... Well I think I will wait on this before acting on it.