yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I don't know the command to disable rollback protection. I don't know if it's actually the problem here.

Yes, you could dirty flash beta 5 over stable, then upgrade via OTA sideload and keep root.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
Ok tks
[Google Pixel 5 Guides, News, & Discussion] elong7681:
I found this https://android.googlesource.com/platform/external/avb/+/master/README.md about AVB 2.0 and rollback protection being included together. There might also be something in this link that may help us with the wipe data for permanent root.
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
@Anonshe posted ths method in the Pixel 6 Pro thread. Does this work for the Pixel 4a 5(G), Pixel 5 or the Pixel 5a?
[Google Pixel 5 Guides, News, & Discussion] Anonshe:
Just updated my Pixel 5 to the November Sec Patch without any data loss. Since I'd disabled vbmeta before, steps were simple:

- Used Payload Dumper to extract the boot and vbmeta images. Patched the former.

- Rebooted to Recovery

- Sideloaded the OTA package

- Reboot to bootloader from the recovery menu

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

fastboot boot magisk_patched.img

After it booted up, opened Magisk Manager, installed via Direct Install. All works fine.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I did the same, except I extracted the images from the factory zip.

I successfully did both OTA sideload and dirty factory flash with no issues.

Oddly, I'm still seeing a software update available...
[Google Pixel 5 Guides, News, & Discussion] prgopala:
Assume this only works where you have wiped and clean installed android 12 for the first time.

I had updated from Android 11 -> Android beta 12.5 -> Android 12 and had those 'data corrupt' warnings. I have not wiped my phone yet and was using temp root by booting the magisk boot image.

I followed the above steps with the Nov security update and alas the 'data corrupt' warnings still pop up.

So i think a wipe is required at some point.
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
Nevermind, I found the answer I needed. :)
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yes - if boot verification was not disabled the last time Android System was running, a data wipe is required.
[Google Pixel 5 Guides, News, & Discussion] State.of.mind:
Are you all able to get the Magisk repo to load on the Canary build? Also, does the magisk hide function no longer work?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
MagiskHide has been deprecated for DenyList on Magisk 23010+.
[Google Pixel 5 Guides, News, & Discussion] State.of.mind:
Thanks, and I'm assuming that older versions of Magisk are not compatible with Android 12
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Not true, I'm using 23001 on my Pixel 5 with MagiskHide, Riru and Universal SafetyNet Fix 2.1.1 for Safetynet pass.

23010 is the first build that "officially" supports Android 12, though.

Also please refer to @topjohnwu 's State of Magisk. He details some of the changes that are happening and why. This includes the module repo.
[Google Pixel 5 Guides, News, & Discussion] State.of.mind:
Thanks this is great info. I'm on Magisk 23012. If I want to downgrade to 23001 is it as simple as flashing the patched boot image or would I have to uninstall Magisk?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I would recommend restoring the boot image (do this in Magisk) then a complete uninstall (also do this in Magisk); only then should you install 23001. It's not as simple as the boot image and the app.
[Google Pixel 5 Guides, News, & Discussion] State.of.mind:
Thanks. Final question.. How did you find the APK for 23001? The APK I'm using keeps defaulting to 23012
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
It's not easy, you basically have to look at the canary channel commits, and they're all named "app-debug"

Magisk 23001
[Google Pixel 5 Guides, News, & Discussion] pershoot:
Monitor this and you should be able to keep privy of releases (aside from the app notifying you of such).

History for gradle.properties - topjohnwu/Magisk

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

github.com
[Google Pixel 5 Guides, News, & Discussion] pershoot:
Odd issue, Zygisk was showing: No. I had patched before that was enabled. I repatched while it was on, then reflashed, and now showing Yes, as it should.
[Google Pixel 5 Guides, News, & Discussion] xstrifey:
Really noob question sorry - first pixel device, I'm used to using Odin on Samsungs.

I have bootloader unlocked

PS C:\adb> fastboot flash boot magisk_patched.img

target reported max download size of 268435456 bytes

sending 'boot' (98304 KB)...

OKAY [ 2.419s]

writing 'boot'...

FAILED (remote: Failed to write to partition Not Found)

finished. total time: 2.565s

Anyone know the reason this would be happening?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Did you previously have a custom ROM on the device? It sounds like you should use Android Flash Tool and force flash all partitions.
[Google Pixel 5 Guides, News, & Discussion] xstrifey:
thanks for the response.

The phone is 100% stock, running 12.0 (current firmware), only thing I’ve done so far is unlock the boot loader and create the patched boot file.

I’ll reflash the current firmware using the web-ui and force flash all partitions, and report back.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Make sure you check "Disable Verity" and "Disable Verification" too.
[Google Pixel 5 Guides, News, & Discussion] xstrifey:
No success unfortunately
[Google Pixel 5 Guides, News, & Discussion] ggkameleon:
Hi ! I have a mistake Yesterday with LSPosed Zygist Riu when flash the last update my Pixel stay only on black screen or power off/restart/shut down. After test to start on safe mod I can't and flash the boot modified backup and data corrupt. Rrrrr. I do a clean install with Android flash tool with disable verity etc.. And root it no mistake.

But this day after install mod again I loose the root after restart !?

How can to root it again correctly please I don't want to make a clean install again.

Thanks
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
You might have a corrupted device.

One more thing to try though. When in bootloader, use the volume buttons to change to Rescue Mode, then select that. Then, go here: Pixel Repair Tool

Select "Other" for the carrier.

If that doesn't work...your device is probably corrupted.

If you don't mind, explain how you got to the point where you couldn't write to /boot. Did this device work before? What happened between the point where it worked and now?
[Google Pixel 5 Guides, News, & Discussion] xstrifey:
Thanks for the help.

As alternative test I successfully installed graphene OS this morning which went smoothly.

Ill revert back to stock tonight and try the above suggestion. Appreciate the help!
[Google Pixel 5 Guides, News, & Discussion] ggkameleon:
Hi ! I loose the root just magisk manager on my pixel after install a mod.

For root again do flash stock boot.img and patch it again with magisk after just flash the modified boot.img or do flash vmbeta disable verity... . Before ? Thanks.
[Google Pixel 5 Guides, News, & Discussion] ggkameleon:
Hi ! Please help me 🤪 I have mistake after flash module and loose Root Magisk. I'm on November update wipe data and root but loose it after install a module !? Don't know which module.

I have flash again Magisk boot modified after flash vmbeta (verity & verification) but boot loop ?

I have flash stock boot img after flash vmbeta (verity & verification) and restart.

But I can't root it ? I don't understand ? Do dirty flash Rom for root it ?

Resolve 😄 I can flash Magisk again but without "--slot=all" and all module are uncheck I remove it and install one by one but I think this is the last LSPosed Riru Zygist or Magisk Hide. Don't install MagiskHide I have USN 2.2 and Install stable LSPOSED not the last. 😊

Hi think is MagiskHide make bootloop with last USN & LSPOSED Zygist and not necessary for pass safetynet
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
If you have questions about a Magisk module, please post in the Magisk General Support Discussion thread or contact the developer of the module.
[Google Pixel 5 Guides, News, & Discussion] ggkameleon:
Good evening.

Yes I would do it like that next time.

It's just that I wanted to explain the situation well and especially to know if it was necessary to flash the "vbmeta.img & verity & verification" to return to the original Boot.img and same for Re-Root and flash the "modified Boot.img".

But you answered my question and thank you. it's not necessary ! only for an update.

Have a good day thanks again
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Restoring the boot image does not require that you do anything with vbmeta. In fact I would recommend that you don't.
[Google Pixel 5 Guides, News, & Discussion] xstrifey:
All resolved now. Updated the platform tools folder and followed same process and worked this time.

Now just to remove replace google apps with micro-g and enjoy!
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Universal SafetyNet Fix 2.2.0 is out on public release for those of you who want to use the new Zygisk.
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
Most recent Canary update is giving me this issue where no matter what I do, when I reboot, it goes right back to the same screen, asking me to download additional stuff. Is anyone else having this issue?

On another note, I am passing safety net with 2.2.0. 👍🏻
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
I had this problem before, the Magisk version was 23001 and the App version was 23014.

What I was told to do by @andybones (Staff Member) was to uninstall Magisk App: Open Settings => Apps => See all... => Scroll down to Magisk => Tap it => Tap Uninstall (

Magisk will not be uninstalled, only the Magisk 23014 app

) => Reboot => install Magisk ( app-debug_23001.apk) => reboot.

Notes:

I add the _230xx to Magisk app-debug.apk after I download them. Why? I have a habit of keeping the old and new app-debug.apk in the same folder, the added portion helps me distinguish between the two.

Make sure you have Magisk Alpha/Canary.apk 23013 stored on your phone prior to uninstalling Magisk App 23014.

Install Magisk 23013.apk after you uninstall the Magisk App.

You will not lose root

.

After, the reboot when you open Magisk, there will be an Update next to

App

.

It should be for Magisk 23014, if you want to update to that version: Tap the Update button and tap Direct install.

See what @andybones, wrote Scroll down read posts #370, 379 and 380 and thank him.
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
Thank You for the reply, however, after following your instructions, I was left with the same results.
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
Two question:

- What model phone do you have?

- Are you on Android 11 or Android 12?
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
Pixel 5

A12

I solved the issue by patching boot.img with latest app, then flashing magisk_patched-boot.img in fastboot.
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
(y)
[Google Pixel 5 Guides, News, & Discussion] Lomarnut:
work for pixel 3?
[Google Pixel 5 Guides, News, & Discussion] caretoexplain:
What I did to fix the magisk error was quite simple really and should help any one reading this thread. This is for the folks who already have TWRP installed fyi.

1. Download the Magisk apk file from github

2. Use an apk to zip converter. I use ezyZip.

3. After downloading the converted file it should look like just a File. Rename the file to a zip and accept the warning.

4.Plug your phone in and go to Developer options -> Default USB configuration -> File transfer

5. Reboot into recovery mode and move the new Magisk file into your phone.

6. Flash the file.

If yall have any questions let me know.
[Google Pixel 5 Guides, News, & Discussion] 93fuelslut:
Does anyone know how to flash the core patch so I can install Spotify which is a modded version? Supposedly a12 doesn't like different or changed signatures so it doesn't want those apps installed and the core patch deals with that.

But I'm not sure if you flash via magisk or you need riru or lsposed?

Pixel 6pro stock rom rooted
[Google Pixel 5 Guides, News, & Discussion] jons99:
you need lsposed https://t.me/LSPosed/177

core patch https://github.com/LSPosed/CorePatch/releases
[Google Pixel 5 Guides, News, & Discussion] 93fuelslut:
Where can I find install directions? Telegram just has Change logs
[Google Pixel 5 Guides, News, & Discussion] jons99:
lsposed is a magisk module
[Google Pixel 5 Guides, News, & Discussion] 93fuelslut:
Oh I didn't know that
[Google Pixel 5 Guides, News, & Discussion] kartikeya98:
OnePlus 8T, Pixel Experience Plus, Non Rooted,

Anyway to root now without loosing the data.
[Google Pixel 5 Guides, News, & Discussion] THEVAN3D:
since it worked for you i'm assuming that OTA does not do the "Disable Verity" and "Disable Verification". So I got the system with verity and verification enabled. thats why i was unable to root. any way to disable verity and verification without factory reset and re-flash? 🥺
[Google Pixel 5 Guides, News, & Discussion] badapple420:
Yeah i had to reset and re-flash is the only way to disable verity and verification that I know of
[Google Pixel 5 Guides, News, & Discussion] THEVAN3D:
and you're absolutely sure that you are rooted right? magisk, modules, root, everything works?
[Google Pixel 5 Guides, News, & Discussion] AndroidDeveloperLB:
Magisk isn't yet available for Android 12 beta 1 , right?
[Google Pixel 5 Guides, News, & Discussion] badapple420:
Fully rooted no problems
[Google Pixel 5 Guides, News, & Discussion] AndroidDeveloperLB:
Really?

Which version of Magisk do you have? I have 23.0 . I tried yesterday and got a boot loop.

For Android 11, the same procedure worked for me (patching the boot file and flashing the patched file).
[Google Pixel 5 Guides, News, & Discussion] AndroidDeveloperLB:
I see. It's not the normal version. It's canary or something.

I've now tested. Works very well:

GitHub - topjohnwu/Magisk: The Magic Mask for Android

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

github.com

https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk

Thank you very much!

My app to put WhatsApp images into address book works again (here, if you are curious), too. :)
[Google Pixel 5 Guides, News, & Discussion] Sh0X31:
I patched the image with the canary magisk apk, flash it via adb and when I enter fastboot reboot, i come to fastboot mode. Also when I naviaget to start and press power. When I flash stock boot.img no problems.

Please help guys, need AdAway working again (Internet without ad blockers is unbearable) :D
[Google Pixel 5 Guides, News, & Discussion] jons99:
you should read the first post then

spoiler alert you'll need to wipe data
[Google Pixel 5 Guides, News, & Discussion] Sh0X31:
rip I need to disable AVB & dm-verity.

So flash I Image with -w and do

or how I disable AVB & dm-verity?

Do disabled AVB & dm-verity remove encryption?

Can I downgrade to Android 11 without wiping? I forget to do a Titanium Backup :(

Do someone try to flash ANdroid 11 on 12?
[Google Pixel 5 Guides, News, & Discussion] yasinsevimli50:
First time I updated directly to A12 from the settings and flashed the patched image, but I got a bootloop.

After that I did exact what the topic says, but every time Android starts, the Pixel Launcher crashes. After a few crashes, the phone reboots itself and asks to format data. Repeating every time.

Only way to get A12 is to flash A11, and update A12 from the settings, but that way I can't root the phone.. :/

Some solutions for this?
[Google Pixel 5 Guides, News, & Discussion] THEVAN3D:
Can confirm. This method works just fine. Flashed factory image with disabled verification and verity and used canary magisk build and it is rooted just fine.

Then I installed some of my modules and after one of them system wouldnt boot and now that I think about it maybe that was the problem before too and i re-flashed system in vain :D anyways, the method works. root works. modules work (most of them).
[Google Pixel 5 Guides, News, & Discussion] ZwoelVi:
the android flash tool shows me 2 versions. Tried both. None of them were Android 12. Tried it with my pixel 5
[Google Pixel 5 Guides, News, & Discussion] theninjew:
Can someone show or say if that "bootloader" warning message is there each time you reboot the phone?
[Google Pixel 5 Guides, News, & Discussion] tauio111:
Try this link, it redirects directly to the A12 beta image where you can choose to disable verity and verification.

Android Flash Tool

flash.android.com

Once youre done you can use magisk, and you can usually find the new link for the next betas in the text on https://developer.android.com/about/versions/12/get

You will have to flash like this every time, otherwise verity and verification will trigger itself.
[Google Pixel 5 Guides, News, & Discussion] ZwoelVi:
I will try it out soon. Thanks in advance. Will my data be reset with every update?
[Google Pixel 5 Guides, News, & Discussion] theninjew:
Do we have to wipe the device every time we flash a new beta?
[Google Pixel 5 Guides, News, & Discussion] Bofahad:
GREAT WORK , ROOTED
[Google Pixel 5 Guides, News, & Discussion] sean222:
Thanks alot for sharing this. Worked perfectly! Pixel 5 / Android 12 Beta.
[Google Pixel 5 Guides, News, & Discussion] fattiusmaximus:
Pixel 4a 5g here just bricked, used flash tool said everything was fine had me relock the bootloader as usual rebooted and now says cant find valid operating system. on chat with google support let you guys know how it goes
[Google Pixel 5 Guides, News, & Discussion] theninjew:
Any update?
[Google Pixel 5 Guides, News, & Discussion] Kennyeni:
Hey,

Is there a way to from rooted A11 to rooted/non-rooted A12 without wiping? I want to see if I can finally use A12 without rooting, but I also want to keep the door open to rooting if needed. I would like to avoid wiping in any case.

My understanding so far is that I can install the beta with verity, and everything to keep my data when upgrading. And then if needed, disable verity/verfication via fastboot, and them flash magisk boot.img without loosing data?

Thanks
[Google Pixel 5 Guides, News, & Discussion] SwimDrewid:
Probably a good idea to wipe between major updates. Definitely should wipe reverting updates.

Kind of like the monkey's paw bringing data back to life
[Google Pixel 5 Guides, News, & Discussion] fattiusmaximus:
Yes, im sorry I thought I updated, so after a few hours on google support chat they said they dont support a12 so i have to send it in under warranty repair and it would take 7-10 business days so i was playing around with ADB and decided to unlock the bootloader again used fastboot flashing unlock then unlocked it on the screen restarted it and a12 setup initialized and completed, so word of advice when using this method DO NOT RELOCK THE BOOTLOADER AFTER a12 Install will say cant find valid operating system
[Google Pixel 5 Guides, News, & Discussion] theninjew:
I rooted my 3XL with no issues...except for the fact the beta throws random crashes mostly from the system settings
[Google Pixel 5 Guides, News, & Discussion] TechX1991:
There's no real reason to do the whole Google Chrome flashing thing... just get the vbmeta.img out of the fastboot zip for your device and use the command below

fastboot –disable-verity –disable-verification flash vbmeta <drag your vbmeta.img to CMD window>

Skips that long process. Have yet to have a pixel not boot on me after rooting on 12
[Google Pixel 5 Guides, News, & Discussion] kafisc:
I'm rooted and I don't want to do a full wipe in order to upgrade to the Android 12 Beta 2. Has anyone tried to use the following method yet?

Preparation:

A. Download the OTA

B. Download the Factory Image and extract vbmeta.img

1. Boot into Recovery

2. Select "Apply update from ADB".

3. From the CMD window --> adb sideload ota.zip

4. After the update go to "Enter fastboot"

5. From the CMD window --> fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img

6. Reboot
[Google Pixel 5 Guides, News, & Discussion] snovvman:
Same question. Does A12 B2 still require verity disable? I typically flash the Magisk patched bootloader to get back to root after a manual factory update flash. Thanks.
[Google Pixel 5 Guides, News, & Discussion] aquatix:
I downloaded the full install from https://developer.android.com/about/versions/12/download and fastboot flashed by hand: did recovery and radio, removed vbmeta.img from the zip, did `fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img` and then did `fastboot update image-redfin-spb2.210513.007.zip` without that file (mind that I skipped the -w). It booted fine. I let magisk patch the new boot.img and a rebooted into fastboot. Flashed the patched boot.img but seem not have gotten root.

Still trying some things :)
[Google Pixel 5 Guides, News, & Discussion] aquatix:
Oh, the 'hidden' (renamed) Magisk manager works. So, all good now! I did try renaming the resulting `magisk_patched-23000_NNNNN.img` file to `boot.img` which might also have helped.
[Google Pixel 5 Guides, News, & Discussion] mistermojorizin:
Were you coming from A11, A12 Beta 1 stock kernel, or Beta 1 patched kernel?

After removing vb meta from the zip, which vmeta did you flash? The old one?

What does hidden/renamed Magisk mean? Just select hide magisk **manager**?
[Google Pixel 5 Guides, News, & Discussion] chopt51:
Weird beta 1, I was able to patch the boot.img and flash it. no problems.

Did the exact same method on beta 2 and it won't boot. Had to flash stock boot.img to start up.
[Google Pixel 5 Guides, News, & Discussion] gerard_f:
Unfortunately not working because disable verification requires a full data wipe
[Google Pixel 5 Guides, News, & Discussion] aquatix:
Good questions, I could've told that directly :) I were coming from A12 beta 1 with Magisk patched boot.img

I let fastboot overwrite boot with the new boot.img

I moved vbmeta.img from the zip to disk and flashed this new vbmeta with the disable flags, like in the howto.

The hidden/renamed Magisk was about the manager app indeed; I had Magisk hide enabled, and the apk renamed to something unrecognisable for some apps that check for root apps. Magisk manager unhid itself when it didn't have root on the first beta 2 boot, but it also left the renamed copy, which I later used to check if I had root. That app didn't work, but I then found out that the regular (now unhidden) Magisk manager did.
[Google Pixel 5 Guides, News, & Discussion] aznriceballman:
Same thing happening to me, did you manage to fix it?
[Google Pixel 5 Guides, News, & Discussion] AndroidDeveloperLB:
From the looks of it, you guys didn't get Magisk to root beta 2, right?
[Google Pixel 5 Guides, News, & Discussion] Machuda:
If someone would like to wipe their device to see if that option works, we would all be grateful.