yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5 Guides, News, & Discussion] ProjectAlly:
So, question(s) for @V0latyle or anyone who knows.

Since I've owned a Pixel device (P2XL onwards, now Pixel 5), I've never taken an OTA update...until recently.

So I did a clean install of the first A12 stable release image, using the flash tool (Wipe Device, Disable Verification, and Disable Verity checked), flashed my newly patched boot image and everything worked perfectly! The problem I ran into, was with the 12.0.0 (SP1A.210812.015, Oct 2021) image, after a day or two I kept getting an OTA update nag. I disabled auto updates and all that, still it wanted to update upon reboot. I finally caved and just did it, foolishly! I knew it would cause bootloop or just wouldn't boot. And that's what happened!

So on this one, my question is, will formatting ext4 userdata, or running the flash tool with a wipe and full factory image put my phone back to before OTA status? I feel like OTA just does something different than what the full factory image flashes do (this might not be true though).

Like I stated before, I've never done an OTA as long as I've owned any Pixel phones until recently. I've reflashed in the last two days 10 times, with wipe, trying to get certain Magisk (23001) modules to work correctly, and all but Viper4Android (v2.7.2.1) will work the way it did about two days ago. V4A doesn't install the driver correctly (status, Abnormal, not enabled etc etc, if you know anything of this module). I've posted in the V4A topic by the way, no answer from anyone.

Was just curious if taking the OTA, bricking my phone, then reflashing factory images manually and with the Android Flash Tool, will allow root or my file system to work like it did before taking the OTA the other day.

Immediately after the first AFT reflash, I had root and everything was great, until the V4A install. It had all of my presets and everything from prior updates already enabled, and the driver status was abnormal, ALSO I couldn't manually copy through USB certain files (music, MAGISK stuff etc) to the Pixel 5. It's like it was "locked" or was having issues with "read-write errors" kind of behavior.

Thanks for any answers provided. After flashing 10+ times in a row and trying to get things working correctly again has been a massive time sink and pain. Just want my modules (V4A mainly) to work like they did during the Beta's and the initial A12 release again.

Sorry for the book! 😂
[Google Pixel 5 Guides, News, & Discussion] Skeetch79:
Question though, if the flash bootloader and flash radio commands are run, then the -w update command with the image***.zip is run, the phone automatically reboots. How do you propose the commands would look like to prevent rebooting after the update command is executed?
[Google Pixel 5 Guides, News, & Discussion] pershoot:
append --skip-reboot to the fastboot update command
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
As long as you disable verity and verification before the phone reboots, you're good.

fastboot update --disable-verity --disable-verification image-device-blahblah.zip

If you want to wipe, include -w. If you don't want the phone to reboot, so you can flash the patched boot image, include --skip-reboot

Or...

Use Android Flash Tool, only check Disable Verity and Disable Verification. If you want to wipe, you can check that too. However, there is no skip reboot option for AFT.
[Google Pixel 5 Guides, News, & Discussion] Skeetch79:
so this would be after the *.zip?
[Google Pixel 5 Guides, News, & Discussion] pershoot:
fastboot --disable-verity --disable-verification update image-CODENAME-sp1a.211105.003.zip --skip-reboot

edit: typo; shifted OPT before CMD
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
If you choose to update using the factory zip, preventing reboot isn't as important as it is with the OTA -- as long as you disable verity and verification.

To make it simple: Once you have disabled Verified Boot, DO NOT flash the factory image without --disable-verity --disable-verification. If you do, and you forget to skip reboot, and the device boots after writing /vbmeta without AVB disabled...you won't be able to disable it without wiping /data.

In the same grain, if you sideload the OTA, DO NOT reboot into Android before you reflash /vbmeta with the disable flags.
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
Nevermind, your answer to another post answered my question. Thanks. :)
[Google Pixel 5 Guides, News, & Discussion] cubandanger05:
I bit the bullet and upgraded from 11 to Nov 12. Wiped data, the whole 9. Got root with Canary 23001, passed safetynet, gpay works. My only concern is I'm unable to hide magisk, the permissions for magisk Manager looks like the screenshot. When I do hit the hide option within magisk, the "setting" app installs but it hangs when I try opening it and the regular magisk app is still there. The only reason I mention the permissions is because it may have something to do with it. I've tried installing the stable version, but same results
[Google Pixel 5 Guides, News, & Discussion] b_fizzle:
I was able to complete the update (through Android Flash Tool), attempted to boot (successfully), installed Magisk, patched boot (matched to the file on AFT) and when installing got the error:

C:\Users\xxx\xxx\xxx\pixel>fastboot flash boot magisk_patched.img

target reported max download size of 268435456 bytes

sending 'boot' (98304 KB)...

OKAY [ 2.301s]

writing 'boot'...

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

I've looked up the error, but with no success. I'm sure I'm missing something, but I've retraced my steps and can't figure it out.

Any ideas?

Thanks!
[Google Pixel 5 Guides, News, & Discussion] elong7681:
After sideloading the OTA then booting into bootloader flashing vbmeta with disabled flags then booting the patched .img I get Pixel is starting and nothing else. What should I do?
[Google Pixel 5 Guides, News, & Discussion] yaconsult:
After sideloading the update to 12 and then getting the error when trying to flash the magisk patched boot I was able to boot the patched image without flashing it. But then I updated magisk to the latest canary 23011, made a new magisk boot image and now I can't fastboot boot the patched image any more. I just wanted to do an app data backup before wiping but I can't without root. Any idea why the magisk patched image can't be live booted? Maybe I will try going back to the previous magisk version and trying again. Note that I'm only talking about fastboot booting the modified image, not fastboot flashing it.
[Google Pixel 5 Guides, News, & Discussion] creezalird:
Just dirty flashed pixel 4a5g to Nov update succesfully

- disable all magisk modules and restore back Magisk app name (obviously restart after that)

- Edit the command inside flash-all.bat to (without wipe -w) :

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

- put all related files in the platform tools folder (radio, image, bootloader, bat)

- adb reboot bootloader

- run "flash-all"

- once booted, just follow the usual patching boot.img for magisk

- then can enable back all magisk modules and rename back magisk app

PS: I am still using magisk 23

Pixel 4a 5(G) phone owners need to know for the subsequent update does not need to

skip the reboot

fastboot --disable-verity --disable-verification --skip-reboot update image-bramble-sp1a.999999.999.zip

or flash the vbmeta image:

fastboot flash --disable-verity --disable-verification --slot-all vbmeta vbmeta.img
[Google Pixel 5 Guides, News, & Discussion] mistermojorizin:
would this work if i never wiped data from 11-->12 beta-->12 stable? I haven't been able to get permanent root without needing to do disable verity which would force a data wipe, so i've avoided it.
[Google Pixel 5 Guides, News, & Discussion] creezalird:
I think based on OP first page, you MUST wipe at least once when upgrading from 11 to 12 (with all the disable verify/verification flags). After that one time wipe, any subsequent update from 12 to another 12, should be ok without wipe (but still needs the disable flags). For me, I find dirty flash methode with disable flags, the easiest methode.
[Google Pixel 5 Guides, News, & Discussion] Zorga:
just tried sideloading the ota and disabling flags with no luck to boot

I got the A12 OTA update and I didn't wipe so I guess we must wipe once
[Google Pixel 5 Guides, News, & Discussion] scarlion:
Since we have to wipe data no matter what, isn't there a way to backup and restore /data easily so we don't have to re-install and re-setup everything again? I have years of text messages, Xprivacy with all its settings/permissions, netguard, all my other apps, etc... Can I just "adb pull /data" and then follow the upgrade/reroot instructions and then "adb push /data" or what?
[Google Pixel 5 Guides, News, & Discussion] esta0:
I'm pretty sure this has already been asked here, but just to be safe:

I just updated from Oct to Nov A12 via OTA, flashed vbmeta and patched boot.img, root is working fine. But now I see that Magisk wants me to install a new update. What happens if I simply do direct install and not flash via fastboot? Is it risky?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Reboot and let the phone boot on its own, then let it "settle" for a bit. Then, reboot to bootloader and flash the patched image to both slots.

There is no known workaround for wiping data when disabling boot verification, especially if you're already on Android 12.

Yes - it's called the Google cloud. Text messages are backed up to your Google account as well as all the apps you have installed. Unfortunately, it does not back up app data so while all your Play Store apps will reinstall, you'll have to set everything back up again.

It's a pain in the ass but there's no way around it. I don't recommend restoring data after a wipe because of the high likelihood of corruption problems.

Not risky, you can install it if you want. Just be aware that versions newer than 23001 do not support Universal SafetyNet Fix 2.1.1; @kdrag0n is developing a Zygisk update that works with 23010/23011, but it has not been publicly released yet.
[Google Pixel 5 Guides, News, & Discussion] Skeetch79:
So, I:

- Rebooted into bootloader

- issued flash bootloader command

- rebooted into bootloader

- issued flash radio command

- reboot into boot loader

- issued: "fastboot -w update --disable-verity --disable--verification image-XXXX-XXXX.zip --skip-reboot" command

- rebooted into bootloader

- issued flash vbmeta --disable-verity --disable-verification --slot=all vbmeta.img" command

- issued flash boot --slot=all "magisk-patched.img" command

- fastboot reboot

and I got stuck in a bootloop between the Google splash screen and bootloader

what did I do wrong?

Is the reflash of vbmeta and the patched boot image done in bootloader or fastbootd?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
If you update via the factory image, reflashing vbmeta is redundant.

Does it keep boot looping, or does it end up in Rescue Party?
[Google Pixel 5 Guides, News, & Discussion] Skeetch79:
It bootlooped at least 3 or 4 times, then I powered off the phone and booted back into bootloader. Not sure how long it would have gone on for.

I just also tried "fastboot boot magisk-patched.img" after the last vbmeta step and it bootlooped once or twicer then booted normally into unrooted android.

Is the reflash of vbmeta and the patched boot image done in bootloader or fastbootd?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
You can do either, although bootloader is best. The most important thing to remember is to not let the phone boot into system without verity and verification disabled.

I don't see anything wrong with your commands. I would try this: Reflash /boot with the stock unpatched image. Let Android start and settle for a bit. Repatch the stock boot image, then reboot to bootloader and try booting it again.

I ran into a similar issue when I performed the November update; I sideloaded the OTA, then rebooted to bootloader and reflashed /vbmeta, then booted the patched boot image. It didn't bootloop, it just got stuck on the Google logo with the loading bar. Since I hadn't flashed /boot yet, I just rebooted into stock unrooted system and let it settle for a bit, then I rebooted into bootloader and tried again with the patched boot image, which worked the second time.
[Google Pixel 5 Guides, News, & Discussion] Skeetch79:
BOOM SHUCK-A-LUCKA!

Got it.

So, I followed all of these steps:

- modified Flash-All.bat file to include --disable-verity, --disable-verification and --skip=reboot. in "fastboot update" line. Also made sure it had the -w flag.

- saved as Flash-All-modified.bat

- Rebooted phone into bootloader

- executed Flash-All-modified.bat

- All proceeded fine. The phone was left in fastbootd

- reflashed vbmeta in fastbootd: fastboot flash vbmeta --disable-verity --disable-verification --slot=all vbmeta.img

- issued "fastboot reboot" command

- Went through setup steps of phone - only activated network, accepted disclaimers and chose dark theme. Did not restore app data or set up a google account.

- I then enabled developer mode and usb debugging

- I then issued "adb install magisk-f822ca5b(23001).apk"

- I copied the November Update Stock "boot.img" from my PC to the phone and patched using Magisk

- I copied the patched file back to the PC

- Issued adb reboot-bootloader command

- issued fastboot boot magisk-patched-XXX.img command

- Upon opening Magisk I saw that I was temporarily rooted

- I then "direct installed" magisk and rebooted

- The phone now has permanent root

PROFIT!

Does the patched boot image have to be created on the phone and android version/build that it will be used on?
[Google Pixel 5 Guides, News, & Discussion] Skeetch79:
This seemed to be the key.
[Google Pixel 5 Guides, News, & Discussion] Skeetch79:
Now, would it be safe to install a stable build of Magisk so the Magisk Hide features are restore? I have banking apps and gambling apps which won't run because of root.

This time I WOULD NOT install the stable build to the boot image. I would ONLY update the app.
[Google Pixel 5 Guides, News, & Discussion] hochoch:
Just wanted to say that this worked perfectly for me just now. Really appreciate you taking things step-by-step here. Only issue i had was including the word "fastboot" twice when editing the flashall.bat - stupid mistake! Otherwise was pretty quick and painless. hoping things continue this way as I can manage this on a monthly basis now. Just happy another wipe wasn't required!!! Thanks to you and everything @V0latyle has been doing for us the past few months with these updates. haven't been this into updating/rooting/xda in quite some time!
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yes and no. I do know Magisk has a signature, and a signature mismatch will prevent you from using root. I also know that you don't necessarily have to patch the boot image with the same version of Magisk you intend to use, although I would advise it. For example, you can patch with 23011, and use the 23001 Magisk Manager.

I have also been able to boot previous builds' images on newer versions of Android, although that seemed to be more successful on Android 11.

However, just because something CAN be done, doesn't mean that it SHOULD. In my example above, Magisk would not work properly because 23010 introduced Zygisk and eliminated MagiskHide, so it is best to use the same version of Magisk you used to patch.

Glad you got it.

I would not recommend this; since you've already had a different version of Magisk installed, it would be best to perform the Complete Uninstall from within the app, restore the boot image, and start over with the version you intend to use.

I am using 23001 on the latest update with no issues. SafetyNet passes, GPay works, all is well. I can't speak to 23.0; I haven't been using it because 23001 has been working great, and I'm of the "if it ain't broke, don't fix it" mentality.
[Google Pixel 5 Guides, News, & Discussion] creezalird:
For magisk, in combination with safetynet fix (riru preinstalled), i have no issue with magisk 23000.

Additionally renamed magisk app, and of course magiskhide needed apps. Working great so far with all my apps
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I forgot to mention, @kdrag0n is working on Universal SafetyNet Fix 2.2.0, which has been updated to use Zygisk instead of Riru. It's currently in beta and therefore only available through his Patreon, but we should see it released in a week or two once stable. Some folks on the Pixel 6 are using Magisk 23011 + USNF 2.2.0 and pass SafetyNet.
[Google Pixel 5 Guides, News, & Discussion] Neuken6969:
wondering why not one person commented lol, congrats.
[Google Pixel 5 Guides, News, & Discussion] Neuken6969:
i was on rooted A11 and for so long the system kept telling me to update to A12. Obviously i could not as i was rooted and would always fail. Somehow it did actually update to A12 ( SP1A.210812.016.A1 ) not rooted. I hate backing up all the movies and downloads and blah blah its a B!TCH. So since i took the OTA, can i just following the following ... and be rooted? Unless it is safer to wait for a more clear specific method that is 100%???
[Google Pixel 5 Guides, News, & Discussion] scarlion:
I don't think apps installed outside the play store are backed up, neither are text messages if you're not using google's messages.

No kidding. Android is supposd to be based on linux which in my experience is easy to upgrade. Never need to wipe anything and, if you do, just backup/restore /home and you're good to go. Might as well just stay on 11 then

What kinds of things could happen?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
One person did, albeit with a trimmed quote.

I'm not sure what you're asking. You took the OTA update to Android 12, lost root, and are now looking for a way to update and reroot?

Go to the first post in this thread. I have written clear instructions that will help you do just that. If you have any specific questions as to the process, we'd be happy to help you.
[Google Pixel 5 Guides, News, & Discussion] yaconsult:
There was another update to magisk today to 23012 so I updated it and now I am able to 'fastboot boot' the patched boot image - note: boot it, not flash it. Now that I have root again, I will back up all app data with OAndBackupX from f-droid before doing the unfortunately required wipe.

Since I already have 12 and the November update installed, do I need to do anything besides a factory reset? After that, I will be able to flash the magisk-patched boot image and be rooted without issues?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Please refer to the instructions at the beginning of this thread.

You will need to disable Android Verified Boot by reflashing /vbmeta, and if you do not factory reset, you'll boot into a recovery screen telling you that your data may be corrupted.
[Google Pixel 5 Guides, News, & Discussion] digger16309:
Strongly recommend swift backup. It is in the app store and has added functionality with root. Transfer all backups to PC. It worked flawlessly for me changing from a Pixel 4a to Pixel 5. Note that it doesn't backup photos. Just pull your DCIM folder to your PC.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
can you post the link to @kdrag0n patreon for the new snf
[Google Pixel 5 Guides, News, & Discussion] pershoot:
Universal SafetyNet Fix · 2.2.0

Changes since 2.1.1 Ported module to Zygisk Fixed screen-off Voice Match in Google Assistant Fixed poor microphone quality with Voice Match enabled on Pixel 5 Fixed At a Glance weather display on Android 12 Fixed At a Glance settings on Android 12 This version only supports Zygisk (latest...

kdrag0n.dev
[Google Pixel 5 Guides, News, & Discussion] elong7681:
@pershoot thank you
[Google Pixel 5 Guides, News, & Discussion] Skeetch79:
Can someone simply explain (in layman's terms) how Zygisk is better than Magisk Hide and what zygote is? I tried digesting info about Zygote and it went straight over my head. I am an Organic Chemist, but I could not even decipher the technical speak in the description!

Will Zygisk function similar to MagiskHide in allowing Banking apps, etc. to run without root detection?

Does the option to hide the Magisk app function in the canary 23001 build?

Thank you in advance!
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Zygote is an extension of the Julia programming language that @topjohnwu has switched to for Magisk as it is more flexible and powerful. Zygisk is the Zygote implementation in Magisk.

Magisk 23010+ no longer supports MagiskHide; it now contains a similar tool called DenyList, which functions in much the same way. As to whether it's "better", I can't really answer that; the reason for this change is because John wants to continue developing Magisk without a conflict of interest in his current role at Google, specifically because he works directly on Android platform security.

I can't really speak to -how- it works; I just know that it -does-. Magisk 23011 + DenyList + Universal SafetyNet Fiix 2.2.0 passes SafetyNet on Android 12.
[Google Pixel 5 Guides, News, & Discussion] Neuken6969:
@V0latyle thank you very much. lets see if i can do this lol. have to now backup 89 gb of data and apps

so my steps would be ..

If you update via automatic OTA:

1. Download the factory image (Yes, this is required) to your computer. Connect your device via USB.

2. Extract the contents of the factory image, then extract both boot.img and vbmeta.img from the image-[device].zip (where [device] is the codename for your device, such as Redfin for Pixel 5

2. Reboot to bootloader: With device connected via USB, Developer Options enabled and USB Debugging enabled, reboot to bootloader using ADB:

Code:

adb reboot bootloader

3. Continue to Reflash vbmeta below

Reflash VBmeta

1. Reflash vbmeta with dm-verity and boot verification disabled:

Code:

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

2. Reboot to bootloader:

Code:

fastboot reboot bootloader

Continue to Patch Boot Image below.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
What exactly are you trying to accomplish, and what is your device's current state? Start with that.
[Google Pixel 5 Guides, News, & Discussion] janvandijk:
I've rooted using this guide, but my pixel is now called."Google BASIC". Google Photos doesn't recognize is as a pixel, and thus photos are counting towards my storage. What can I do?
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
Excellent Guide: I love the news that after the first Android 12 factory image update with a wipe, subsequent updates can be done via factory image adb without a wipe.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Just so long as the phone never boots with vbmeta disabled.

For example:

You flashed vbmeta with disable flags and rooted your phone.

Next update comes and you sideload the OTA, which writes vbmeta, and you forget to disable it again. Phone then boots normally, and you don't notice anything is wrong until you see you don't have root. So you reboot to bootloader and reflash vbmeta...and get Rescue Party when you boot.

At this point you're back where you started, and to root your device, will have to wipe again.
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
I plan on using @Skeetch79 method, without the -w, to flash my sebsequent factory image:

[GUIDE] Update to and Re-Root Android 12 **READ THE NOTES** | Page 14

or

@creezalird method:

[GUIDE] Update to and Re-Root Android 12 **READ THE NOTES** | Page 14
[Google Pixel 5 Guides, News, & Discussion] b_fizzle:
Just in case anyone is having an issue - I had updated adb and fastboot and still no success. I removed it from my system completely and used hxxxx://xdaforums.com/t/tool-latest-adb-fastboot-and-usb-driver-installer-tool-for-windows.3999445/ (not sure if link will post) and it installed updated drivers. I followed the guide again and had no problems. Everything updated appropriately.