yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Bro you gotta read what I'm saying lol

I updated via the factory image on the 5th, as soon as it was available. Flashed it to both slots. So, both slots had Android 14.

Nope because I flashed both

Normally the system will prompt you for an update. That didn't happen - I was never notified of anything. I just found out it has rebooted overnight.

Except I do not and never have received OTA updates.
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
Sorry bro, you keep on updating posts that I read and responded to, I don't have a habit of re-reading the posts I have read. :)

Sorry if I asked questions that you have already answered.

Correct, that's normally the case, but not necessarily.

No guarantees that you won't get OTA updates, you're not an exception, many others reported similar cases, exactly what triggers it remains a mere speculation.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Right. I just don't know what could have been updated since both slots already were up to date.
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
In retrospect, we could have dumped A and B partitions (except userdata) and compared the checksum. Too late for that now.

Do you have any modules that would fool Google into thinking that you have an older firmware / OS?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Nope, just Displax's USNF fork, the Systemless Hosts module, and Google Photos Unlimited Backup
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

pixel 5 are no longer updated. which rom should I use now ?

with the same protection and security as an original version.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I don't use custom ROMs, you'll have to figure this out for yourself.

LineageOS is generally up to date.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Yes, I know. I'm asking the question for everyone ;).

And I don't understand why, after only 3 years, he stops the update
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Most manufacturers only support their phones for a few years.
[Google Pixel 5 Guides, News, & Discussion] badabing2003:
A wild Pixel 5 and Pixel 4a (5G) update appears

Google is rolling out one more update to its 2020 phones

www.androidpolice.com
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yeah I just saw that, updating now.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

They decided to go ahead with the pixel 5 after all ?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
What do you meaan?

February was the last update for the Pixel 5.
[Google Pixel 5 Guides, News, & Discussion] Regys:
they were supposed to stop in october. why did you do a last update then ?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Updates are only guaranteed through a particular date for a particular device. Oct '23 for the Pixel 5, Aug '24 for the 5a, Oct '24 for the Pixel 6 / 6 Pro. See here:

Learn when you'll get software updates on Google Pixel phones - Pixel Phone Help

Below are software update guarantees for Pixel phones. If you have another Android device, contact your manufacturer or carrier for update info. If you have a Nexus device,

support.google.com

All that means is that they've committed to providing regular updates for that time. They may, or may not, provide additional updates beyond that. The Pixel 5 received 2 updates beyond its support date, Nov '23 and Feb '24.

If you want to know "why", ask Google.

I am not a ROM builder, I don't do anything beyond providing a guide for people to use when rooting their phone, and updating their phone with root. I don't provide updates; Google does.
[Google Pixel 5 Guides, News, & Discussion] Regys:
I asked the question like this :)

Thanks !
[Google Pixel 5 Guides, News, & Discussion] NervGaz:
As I'm a stubborn bastard and really didn't want to wipe I did some thonkin' and figured I might be able to clear /data/adb from TWRP. No go as I couldn't mount /data, so I thought to myself maybe just maybe I can get a rooted adb shell from just booting the patched image. So I rebooted into the bootloader and ran "fastboot boot <magisk image>" with another command prompt open running "adb wait-for-device && adb shell" and lo and behold, adb shell up. Gained root with a simple su and cd'd to /data/adb and deleted the full contents. Rebooted to bootloader and fastbooted the magisk image again, device boots fine, direct install of magisk worked and I am now rooted. Cheers for the help man.

I hope this might help someone else in the same situation. And the usual YMMV.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Good stuff, glad you were able to fix it.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
For those who are wondering, this is how I updated my Pixel 5 (and my wife's 5a):

Download and extract the factory image

Extract boot.img from the factory update image

Copied boot.img to device, patched in Magisk, copied patched boot image back to update folder

Reboot device to bootloader

Apply update:

fastboot update device-image-buildnumber.zip

Let device boot and finish update; reboot to bootloader

Boot patched image:

fastboot boot magisk_patched-23016_xxxxx.img

Open Magisk, tap Install, Direct Install, then reboot.

Done.

You can potentially save a couple steps by using --skip-reboot when applying the update, then simply rebooting to bootloader and flashing the patched boot image.

Note: I manually patched the boot image because I didn't have a 23016 boot image handy.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
Just to confirm you did also uninstall magisk through the app and the modules as well before doing what you posted above?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
No. Why is everyone insisting on doing this? Uninstalling Magisk and removing modules is NOT NECESSARY to update. I updated exactly as I detailed above, no hidden steps.
[Google Pixel 5 Guides, News, & Discussion] Xx-Ness-xX:
Confirmed working

Just applied January update like how I have always been doing on Android 11. This wouldn't be possible without Magisk version 23016
[Google Pixel 5 Guides, News, & Discussion] AquilaDroid:
Finally, a straight forward method of updating without having to edit the flash-all.bat file, etc.! (I'm getting ready to flash my P5 from A11 (Oct) to January A12.)

Thanks @V0latyle for all your activity and guidance here!
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
When upgrading from Android 11, the safest way I think would be to OTA, because it preserves and migrates everything.

The best way is a clean start and factory flash; it's not really advisable to dirty flash Android 12 on top of Android 11, just because of the seemingly insignificant differences that can cause problems down the road. That being said, it will work.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
Thank you for your reply.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
That being said....I'm only using two modules, USNF and MHPC. It's entirely possible that anything involving modifications to /system, such as UI mods, may have to be reapplied after an update. But, that would be as simple as reinstalling them.
[Google Pixel 5 Guides, News, & Discussion] AquilaDroid:
If going the "best" way, what's the best way to backup everything. I have Google One backup on, photos synced with Google Photos, etc. (I still have vivid images of having to start all over years ago.)

With the "Update and Root Automatic OTA" approach, is it necessary to uninstall Magisk, lock the boot loader or do anything else prior to hitting "download and install"? I didn't think OTA would work on rooted device. ADB sideload???
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Swift Backup. With root it can backup app data.

This question has been answered.

No.

OTA does work on a rooted device - just not very reliably. If you absolutely have to use the OTA, sideload will always work. I personally prefer to use the factory image; if you don't already have a patched boot image handy, you will need it anyway.
[Google Pixel 5 Guides, News, & Discussion] AquilaDroid:
Thanks again. I'm all ready to flash the update, have patched the boot.img, and moved it back to the computer. Will have a go at it when I get time tomorrow. Have a good evening, thanks for taking care of us here!

BTW, in the OP:

"Spoiler: Initial Root / Create Master Root Image" should be "Boot Image"?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
You can name it whatever you want as long as you know what it is

The purpose here is to have a patched image that you can boot after every update and use it to root your phone directly with Magisk. This should work at least until Android 13, regardless of how old the image is.

That being said, you can always manually patch the new boot image if you prefer to do it that way, but that will require downloading the factory zip every time there's an update. Temp booting a master image makes it easier to re-root post OTA.
[Google Pixel 5 Guides, News, & Discussion] k1984228:
I am using stock pixel rom A12 with Dec 2021 patch

What's the steps to update to Jan 2022 patch🤔

I am using latest stable ver of Magisk and don't want to use canary Magisk
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Magisk Stable does not currently support Android 12, because it does not properly patch the boot image header. I can assure you that Canary 23016 has been quite stable, and I highly recommend you reconsider using Canary until Stable is updated with the necessary fixes.

But, just for you, here's how I would do it if I were in your shoes:

If your device bootloops twice and ends up with this warning:

Cannot load Android system. Your data may be corrupt.

You can either wipe data to continue, or you can re-flash back to stock, temp boot the patched image, update Magisk to 23016, re-patch the boot image, and continue.
[Google Pixel 5 Guides, News, & Discussion] ProjectAlly:
EDIT: I'm really slow today... I just reflashed the update without a wipe since I already had it downloaded beforehand, I'm back into my phone now, everything is fine, minus having root. Since I also updated Magisk from 23000 to 23016 today I'm gonna patch a new boot image and reflash it and see what happens.

Sorry for the earlier post!

OG:

I REALLY hate to ask this, and maybe there's no way around the issue but to wipe data now...but I forgot to create a new patched boot.img with Magisk 23016...and instead flashed boot with the image I created prior (like hours prior) with Magisk 23000...

Long story short I'm stuck at bootloader screen and can't boot into my phone now! Also I'm on vacation away from my desktop PC and good internet, I do have my not so great laptop though, so would flashing an updated boot image made with Magisk 23016 get me back into my phone without wiping data? If so, would someone perhaps be willing to share a patched image with me? If not that's fine, just asking, or perhaps if there's a way I can salvage this through ADB that would be awesome!

I just updated everything manually like I always have, and it worked perfectly until I rebooted and ADB flashed that 23000 boot image... I feel really silly right now. 😑
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Look at the bottom, you'll see a message failed to load/verify boot images

This is because Magisk 23015 and prior do not properly patch the boot image, screwing up the header.

Yes. Alternatively you can just reflash the stock boot image. You won't have root, so if you need root, you can temporarily "live boot" the patched image:

fastboot boot <magisk patched image>

This skips the verification for whatever reason

Attached, use at your own risk

It happens.
[Google Pixel 5 Guides, News, & Discussion] ProjectAlly:
Really appreciate all the help and info!

Was able to just reflash the update (with "-w" removed in the .bat) and am up and running again, rooted as well! I just patched a new image with Magisk 23016 and fastboot flashed it and all is good so far.

Just need to get familiarized with how Zygisk and the deny list works, since I'm used to MagiskHide. Also I kinda miss the repo being attached, but that's easy enough to deal with.

Sorry for OT there. Thanks again for your help! 😁
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
No problem.

So, with DenyList, only use it on Google Play Store + any apps you wish to hide root from. Due to John Wu's role at Google working on Android Security, Magisk will no longer block things from Android System.

However, there are still modules available that will facilitate this. I have been using Universal SafetyNet Fix and MagiskHide Props Config. SafetyNet passes according to YASNAC, and GPay works. No issues with financial and DRM apps, except maybe Hulu, but that has more to do with the fact I'm almost always on a VPN.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
I know we don't have to disable verity and verification but if we wanted to know if it was disabled is there any way to find out?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
There's some way to do it using ADB but there's not really any point. The only time it would ever get disabled is if you use the options to do so when flashing. And since that's not necessary as of Magisk 23016, I don't know why anyone would.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
I tried to install the Cleanslate Kernel last night using the FKM app like I always do and I ended up with the corrupted data verify boot screen and It took me forever to figure out how to get back into Android without wiping data
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
The safest way is reflash the stock boot image. That should -always- boot no matter what.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
I thought so to but it didn't and neither did flashing the factory image with -w removed and verity disabled but what did work was sideloading the OTA then booted into Android and then into bootloader and then booting patched.img and then direct install
[Google Pixel 5 Guides, News, & Discussion] ProjectAlly:
Okay awesome, for some reason all my reading about the new version of Magisk had me thinking it was gonna be harder to use. So that's good to know, thanks for the information!
[Google Pixel 5 Guides, News, & Discussion] AquilaDroid:
I'm back with a mushy head and no results to get root. I successfully updated to A12, but have been unable to flash the MagiskPatched.img which I've patched twice (and matched the checksum with one posted here). The result is always the same - boot loop (stuck at "G" logo until it reboots back into fastboot mode). I am on Magisk App 23016, Magisk shows Installed N/A, Zygisk No, Ramdisk Yes (and Update Channel is Canary). Flashing the stock boot.img always gets it started again.

In an attempt to get rid of the 7 Magisk Modules I didn't uninstall I've tried lots of things, including:

C:\Platform Tools January>adb wait-for-device shell magisk --remove-modules

adb server version (39) doesn't match this client (41); killing...

* daemon started successfully

/system/bin/sh: magisk: inaccessible or not found

Here's the last output:

C:\Platform Tools January>adb devices

List of devices attached

0B101FDD40001R device

C:\Platform Tools January>adb reboot bootloader

C:\Platform Tools January>fastboot devices

0B101FDD40001R fastboot

C:\Platform Tools January>fastboot flash boot "C:\Platform Tools January\magisk_patched-23016_IZJza.img"

Sending 'boot_b' (98304 KB) OKAY [ 2.316s]

Writing 'boot_b' OKAY [ 0.370s]

Finished. Total time: 3.768s

C:\Platform Tools January> fastboot flash boot_a "C:\Platform Tools January\magisk_patched-23016_IZJza.img"

Sending 'boot_a' (98304 KB) OKAY [ 2.328s]

Writing 'boot_a' OKAY [ 0.377s]

Finished. Total time: 3.715s

C:\Platform Tools January> fastboot reboot

Rebooting OKAY [ 0.054s]

Finished. Total time: 0.061s

Would uninstalling and reinstalling Magisk help? Uninstall via the app, then what?

Any help appreciated, as always. (It's a ***** to get old!)
[Google Pixel 5 Guides, News, & Discussion] kfhughes:
So did you wipe data when upgrading to A12? I don't think anyone has found a way to go from A11 to A12 and root without wiping data.

One other thing to try: flash the stock boot image back to boot_a, but use "fastboot flash boot_a "C:\Platform Tools January\magisk_patched-23016_IZJza.img" to boot the patched boot image, then in Magisk App do the "direct install" to get root.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
What you actually needed to do was simply reflash vbmeta without options, then boot the patched image and direct install.

That's essentially what you did by sideloading the OTA...just the long roundabout way.

Are you able to live boot the patched image?

By fastboot do you mean fastbootd, recovery, or Rescue Party (corrupted data screen)?

Did you disable verity/verification? If you did, you shouldn't have. Reflash vbmeta without disable options.

Usually a Magisk issue just means you don't have root; it shouldn't prevent the device from booting. Removing

modules should not be necessary but then again I only use two. Remember that you can always disable modules in the Magisk module manger.

The only reason this was inevitable was because disabling verity/verification was required to boot a modified image from /boot; disabling verity/verification with /data populated requires a wipe to successfully boot...for some reason.

It should no longer be an issue because of Canary 23016. The only thing you have to do after updating is let the device boot stock and complete the update, then patch and flash the boot image.

Incorrect - you don't use fastboot flash boot to boot a patched image; the context there is flash is the command, and boot is the partition you're specifying to flash.

To boot an image simply use fastboot boot.

Point of note: When updating via OTA, ALWAYS let your device boot the new untouched boot image first. The way the OTA update process works means that system compares the boot image and system versions. If they don't match, it assumes the OTA failed, and boot loops back to the last good slot (the one you were on when you installed the OTA).

Or, download the factory image and patch the new boot image - but at that point you may as well just dirty flash the factory image anyway.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
@V0latyle can I disable verity now without a data wipe?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
No.

Unless you're trying to run a custom kernel, you don't need to; and if you do need to in order to run a custom kernel, it's because the kernel dev needs to take a page from Magisk's book and ensure the boot image headers are preserved and valid.

The requirement to wipe data after disabling verity/verification has not changed. What DID change was how Magisk patches the stock boot image, so disabling verity/verification is totally unnecessary in the first place.

I have seen a few people suggest that they might keep doing it anyway. I don't know who had that idea but it needs to stop. Will it hurt anything? Most likely not, but if it isn't necessary, just don't do it!
[Google Pixel 5 Guides, News, & Discussion] elong7681:
Yes it would be for the Cleanslate Kernel
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Well, until the dev updates that kernel with the boot header fix, then yes - disabling verity/verification will be necessary.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
Ok thanks
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I think I should clarify - Android 12 uses Boot Image Header v4; any kernels built to work with stock 12 firmware should incorporate that.

For custom firmware, it shouldn't matter.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
I tried to flash Cleanslate Kernel with FKM and that's how I ended up on the corrupted data screen. For the installation of the Kernel it states that verity has to be disabled before you can boot into Android so I guess the only way to install the Kernel would be a full system wipe with the disabled flags.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Hmm. To be honest I don't know that much about the Android boot process but I still think that if the kernel is updated to Boot Image Header v4 and uses a valid header, disabling verity shouldn't be necessary.

As I posted in the dev's thread, I highly recommend anyone using a custom kernel stick to the dirty flash factory image method.
[Google Pixel 5 Guides, News, & Discussion] AquilaDroid:
Thanks for your detailed response. I remember reading something about "live boot" but am unable to find the reference now. Any further instructions?

When it fails after flashing the patched image it tries twice and goes back to fastboot (recovery) screen where I immediately flash the stock boot image.

I just tried a few more times with Fastboot boot (magisk patched image) and it still doesn't install Magisk. (What is the info below "*****......*****"???)

C:\Platform Tools January>fastboot boot "C:\Platform Tools January\magisk_patched-23016_IZJza.img"

Sending 'boot.img' (98304 KB) OKAY [ 2.268s]

Booting ******** (bootloader) boot.img missing cmdline or OS version********

OKAY [ 1.518s]

Finished. Total time: 4.195s

The last time I tried, it showed the Android Recovery screen "Cannot load Android system..." Fortunately I selected "Try again" and it came back up (still without Magisk installed).

No, I didn't disable verity/verification.

"Remember that you can always disable modules in the Magisk module manger."

Wouldn't that require having Magisk (not the app) installed?

I re-downloaded and patched the boot.img and the patched versions have the same hash.

Maybe there's something to the comment that you can't install A12 without a full wipe?

Thanks again all!
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
"Live boot" means you're loading a boot image directly via USB instead of from the boot partition - the term comes from the "live USB" method of booting an OS such as Windows or Linux from a USB device instead of the PC's internal storage.

When you use fastboot boot <image> you're telling the device to boot the specified image via USB.: fastboot is the application, boot is the command, and <image> is the image you want to boot. This does not flash it to the device, so when the device reboots it reverts back to loading the boot image from the /boot partition. This is useful when you want to temporarily load something but you don't want to actually flash it to the boot partition; on devices supported by TWRP, this is how you initially load TWRP.

On the other hand, when you use fastboot flash boot <image> you're telling fastboot to flash the specified image to the /boot partition: fastboot is the application, flash is the command, and boot is the partition you're flashing to. This is what you DON'T want to do when installing TWRP because you then overwrite /boot with TWRP, so when the device looks for an image to boot, all it finds is TWRP, no Android kernel.

To be clear, you're talking about the recovery screen that reads Cannot load Android system. Your data may be corrupt, correct? This screen is called Rescue Party. This means that the boot image failed to boot for a reason that makes Android think something is corrupted. Before Magisk 23016, we had this problem because Magisk didn't properly handle the boot image header, so when the device checks the boot image for integrity, it would see the header was messed up. This is the same reason why custom kernels require disabling verity/verification - because developers haven't yet ensured they have a valid version 4 boot image header.

Disregard this. It always appears when you boot an image, even an untouched factory image. It doesn't mean there is a problem.

Yes, but again this shouldn't be necessary when updating.

What version of Magisk are you using? Anything other than Canary 23016 will not work.

How did you initially upgrade to Android 12?