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.
So I thought i followed these steps but my safetynet check failed still.So Magisk Canary was released yesterday:
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)
Remove Universal Safetynet Fix and Riru, if you have them installed, Reboot.
Launch Magisk again
Settings > Magisk:
Enable Enforce Denylist
Enable for Google Play Services components: (I just enabled for all subcomponents)
That should be enough to pass Safetynet. Don't forget to hide other apps such as banking, GPay, DRM (Netflix, Amazon Prime Video, etc)
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.So I thought i followed these steps but my safetynet check failed still.
I used this app to test it.
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
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.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)
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.
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.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
Here's the link for the actual APK from Github.
When you uninstall Magisk from within the app, it restores the boot images for you; you don't have to do that manually.
You need to be familiar with Android Platform Tools (adb and fastboot), as well as where to get the factory image for your device, how to extract files, and how to copy them to/from your phone.
Here's some more detailed instructions:
- Launch Magisk. Tap Uninstall, then Restore Images. Once it finishes, go back to Uninstall, then Complete Uninstall. Let it reboot your phone.
- You will boot into unrooted Android without Magisk. Install 23001.
- If you haven't already, download the Android 12 factory zip. Extract boot.img and copy it to your phone.
- Launch Magisk, then tap Install, then Select and Patch a File. Patch the boot.img you just copied to your phone. Copy the magsik_patched-23001_xxxxx.img back to your computer.
- Reboot to bootloader (I use ADB to do this
[code[adb reboot bootloader[/code]
- Flash the patched boot image:
fastboot flash --slot=all boot magisk_patched-23001_xxxxx.img
Boot the patched image: (I like to do it this way)
fastboot boot magisk_patched-23001_xxxxx.img
- If you flashed the patched image, you're done.
- If you booted the patched image, launch Magisk, then tap Install, then Direct Install.
Basically, we need to determine if it matters when you flash vbmeta. Here's what needs to be tested:An excellent point that was brought up from a Pixel 6 user:
Data wipe is required for permanent root after upgrading to Android 12. That much we know.
But what about a device that had an original clean install of Android 12?
Who here wiped when upgrading to Android 12, and did not reflash vbmeta until AFTER you set up your device?
If you want to upgrade and keep your data, I would recommend using the OTA.
Download the OTA from Google and sideload it via ADB.
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.
How did you disable verity and certification? I've tried using the flash tool and it always fails.Well, it looks like I'm definitely not immune.
Started from 12b5 (clean flash coming from Android 11), rooted.
Took the OTA today, rebooted, no root as expected.
Got home, flashed vbmeta to both slots with boot verification disabled.
Attempted to live boot my patched boot image from the 12 Beta, got
boot.img missing cmdline or OS version
Bootlooped twice, got the "data may be corrupt" error in recovery
Reflashed vbmeta to both slots without disable flags, same result.
Dirty flashed factory image via ADB without disable flags, same result.
Dirty flashed factory image via Android Flash Tool without disable flags, same result.
Dirty flashed Beta 5 factory image via ADB, same result.
Tried to reflash vbmeta, vbmeta_system, and boot. Same result.
Now doing a CLEAN flash of the 210812.015 factory image with disable flags set. Booted and going through setup.
Patched boot image. Able to live boot patched image. Performed Magisk "direct install", about to reboot.
It worked! Now rooted on 12 Final, but had to wipe data.
Working on Safetynet now.
So to recap:
Nothing worked until I clean flashed the factory image with verity and verification disabled. I was then able to successfully root, and did not have to reflash anything. Unfortunately, it did require a data wipe.
I've done it manually as well as by using the flash tool.
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
We still don't know if this has something to do with our issue, but there's a huge chance it does.To add to V0latyle's post.
Pixel 4a [sunfish] has no issue updating and installing Magisk on Android 12.
The issue starts with Pixel 4a (5G) [bramble].
This is also the first Pixel using Boot Header v3.Boot image header, version 3 - source.android - LinkVendor boot header - source.android - Link
The 3, 3a, and 4 series along with 4a are using header v2.
4a (5G), 5 and 5a are using header v3.
Just downloaded and checked.
6 and 6 Pro are using header v4.
I am not sure if that is the problem but, it is quite a distinguishing line between Pixels that have this issue with Magisk and those that do not on Android 12.
After a little more testing on my 5 [redfin], I will open an issue on GitHub.
Magisk - GitHub - Issues - Link
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. WeirdIf 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.