yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S8 Questions & Answers] YasharF:
Has anyone looked into potentially using ODIN to use AT&T's firmware on the unbranded G950U1 without rooting to see if it adds the VoLTE software feature? Does anyone know if that flashing will disable (permanently break) samsung pay? I don't want any rooting since that will permanently break samsung pay on the hardware.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Official updates for this device ended February 2024.

If you are looking for my guide on a different Pixel, find it here:

Pixel 3

Pixel 3XL

Pixel 3a

Pixel 3aXL

Pixel 4

Pixel 4XL

Pixel 4a

Pixel 4a (5G)

Pixel 5a

Pixel 6

Pixel 6 Pro

For best results, use the latest stable Magisk release.

Discussion thread for migration to 24.0+.

Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.

WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.

Prerequisites:

Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!

USB Debugging enabled

Google USB Driver installed

I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.

Make sure the Command Prompt is running from your Platform Tools directory!

Android Source - Setting up a device for development

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Points of note:

The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.

While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:

"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.

"App" simply shows the version of the app itself.

If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.

If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.

Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.

Credits:

Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
You Sir are all over these forums spreading helpful advice, and knowledge. I would just like to say Thank You for all you do here. It's so greatly appreciated. You are one of the many people who make this place so special.

Also, Thank You for your service to our country.
[Google Pixel 5 Guides, News, & Discussion] elong7681:
@V0latyle can you link me to a web page that would list every adb and fastboot command that we as android modders would use. What I mean is I couldn't find a Google search that listed the fastboot command with --slot=all among other adb and fastboot commands
[Google Pixel 5 Guides, News, & Discussion] elong7681:
I agree with @Krsmqn, @V0latyle THANK YOU FOR YOUR SERVICE !!!!! in the military and for your service in the xda community
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
I used the Android Flash Tool method to update to the November build, and followed the instructions precisely. It worked flawlessly. My deny list is exactly the same in Magisk, and all my modules are working perfectly. I didn't even have to disable them. I think I will use this method from now on.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Thanks guys, I appreciate it.

Boy, I wish I had that handy, because I could sure use it too! I don't have your answer but hopefully someone else does, because believe me I'll be bookmarking it!
[Google Pixel 5 Guides, News, & Discussion] Rafiul Bari Chowdhury:
Will this work on Android Pixel 5a?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yes. The root process is exactly the same for the 4a 5g, 5, and 5a. The update process is the same across all Pixel devices.
[Google Pixel 5 Guides, News, & Discussion] nostromo12:
I patched the boot.img. Magisk 23 did not report errors. But size of the patched file is zero. This looks not promising...
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
What version of Magisk did you use?
[Google Pixel 5 Guides, News, & Discussion] nostromo12:
The stabil one
[Google Pixel 5 Guides, News, & Discussion] Rafiul Bari Chowdhury:
Will this work on Android Pixel 5a?

Okay. But Should I Remove Magisk Fully before upgrading through ADB/Fastboot/AFT?
[Google Pixel 5 Guides, News, & Discussion] Regys:
H,

I'm on Android 11 pixel 5, can I use this tutorial ?
[Google Pixel 5 Guides, News, & Discussion] thecompany:
I think it's safer to unroot/remove Magisk and modules when going from 11 to 12 right? Some modules might not be compatible with 12 causing bootloops.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
You're going to have to wipe /data anyway if you intend to root on Android 12. Unless you're willing to try an idea I have.
[Google Pixel 5 Guides, News, & Discussion] nico22320:
Thanks V0latyle !!

I follow the flash tool method for update from october to november on my pixel 5

Perfect update, no issues and all data ok 👍
[Google Pixel 5 Guides, News, & Discussion] nostromo12:
Did you use Magisk canary? It is not necessary to check wipe in the android flash tool?

I use standard Magisk and can not change the update path to canary
[Google Pixel 5 Guides, News, & Discussion] nico22320:
No i use the beta version of magisk.

You need wipe only for update from Android 11 to Android 12.

Just follow the guide for update to november and enjoy 👍
[Google Pixel 5 Guides, News, & Discussion] nostromo12:
I want to upgrade from 11 (oktober) to 12

In the first message from this thread concerning the flash tool there was no wipe mentioned.

I want to update keeping my data ! How to proceed?
[Google Pixel 5 Guides, News, & Discussion] nico22320:
The best way: save yours photos etc with your Google account and make a fresh install with Factory image on Android 12 ( with disable verity and vérification)

It's long for set up device but 100% of chance of work with no issues for futurs update 👍

Sûre you Can try to update without wipe and disable verity and vérification but maybe bootloops or not 🤷
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
Is that version linked in the op?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
No, the link always points to the latest Canary, currently 24301.

Here is 24201 although given that the changes are minimal, I doubt it will work any differently

I went back and read your post; how exactly did you update?

The "missing cmdline or OS version" doesn't affect everything, I always get that notice too but I'm still able to boot and flash patched images

For what it's worth, I have not yet tried updating via OTA. I have always updated by dirty flashing the factory image (NOT OTA)

Also, I am on SP2A.220305.012....is this considered 12L? Tried to find the 12L downloads but it just pointed me back to the factory images page
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
I updated using your method in the op. I've used that method many times, always without issues. No clue what happened this time. Ty for the link.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Which method though? There are 4 different methods posted, in addition to the initial root instructions.
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
I used the "update and root OTA Sideload" method.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Ah, okay.

So to make sure I'm clear on this issue, you're able to boot the unpatched image, but a patched image causes a bootloop, correct?
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
Yes. It tries to boot, and when the boot animation has the "G" with the loading line under it, it reboots back to the working unpatched slot. Or at least that's what I think is happening.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Hmm.

And you are using the boot image from the factory update that's the same version as the OTA you sideloaded?

I would recommend dirty flashing the factory image and see if that works. Make sure your Platform Tools are up to date, and just to be safe, re-patch the boot image. Make sure you don't have extras laying around, go ahead and delete the old ones.
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
I am definitely using the same boot.img version from the factory image zip as the OTA. I've triple checked. I've already done the dirty flash from Android Flash Tool. Not sure how to update the sdk tools from windows 11. I guess I download the latest and reinstall. I have a dedicated folder for current flash stuff, so there's no chance of a mix-up. I will try latest sdk tools, re-patch and report back.

Attached are some screenshots, and hopefully a viewable video. The magisk app says the ramdisk is patched, but magisk not installed? idk. Video is weird. And what's with the double storage? ... check 'em out.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Nothing appears amiss from your screenshots.

Try re-sideloading the OTA. Let it boot when it's done, don't try to flash or patch the boot image. Reboot a couple times, then try to boot the patched image.

The download link for Platform Tools is in the OP. Current version is 33.0.0
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
No luck. Same results. Just gonna bite the bullet, back-up, and wipe.
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
This worked.... Updated, rooted... and reconfiguring... 😒
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Sorry you had to wipe. It's never fun.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
If it makes you feel any better...I spent the evening replacing the GPU in my 9 yr old Alienware laptop, only to have it not power on after I put everything back together. I have no idea what could be wrong - all I did was replace the GPU MXM card, and blow out some dust. I'm guessing the new GPU was bad and fried the main board. Really depressing, that thing has been a tough soldier.
[Google Pixel 5 Guides, News, & Discussion] Krsmqn:
Turns out that my issue was a magisk module that's not compatible with the latest update. When I tried to install it on a clean install, I experienced the exact same issues. 🤷🏻‍♂️
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
So maybe there is some truth to disabling modules before an update. It just depends on which modules.
[Google Pixel 5 Guides, News, & Discussion] omartins:
I second that line of thinking. In case of doubt and / or if playing safe is the way to be followed, disabling all modules before update, takes only a few seconds and might avoid some headaches...
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yeah. In my case, I'm only using 3 modules - MHPC, USNF, and Systemless Hosts. I don't disable them before I update.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
For those of you running custom kernels: DO NOT attempt to update via OTA, and DO NOT try to reflash the custom kernel after OTA.

The best way to update while running a custom kernel is by dirty flashing the factory image. The OTA process checks to make sure the kernel matches the system; a custom kernel won't match, and you'll get the corrupted error.
[Google Pixel 5 Guides, News, & Discussion] tainvst:
Unfortunately, I missed this end of the thread before the March update. I got stuck not booting into the patched boot image. For what it's worth, I had to boot back into the stock boot image, then safe mode. After that I was able to boot into the patched image and activate each module individually. No wipe needed. Hope this helps.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Very helpful. I forget, how exactly does one boot into safe mode?
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

Why are there 2 guides ? yours and @Homeboy76 ?

Thx !
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Some people like to create their own guides. TBH I don't see the point in redundant threads but if he wants to help people his own way, he's more than welcome to
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
Just Curious

You wrote "I don't believe in redundant threads..." If that is true, you wouldn't have created the redundant thread. :ROFLMAO:

Glad you're helping XDA members your own way.(y)
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
It was originally just focused on the issue with the boot image headers under older versions of Magisk.

Your thread was indeed here first, at least for this device.
[Google Pixel 5 Guides, News, & Discussion] yurisan:
hi,

i haven't been able to apply last (March 5) OTA by using 'no reboot/install to inactive slot' method so i lost magisk/root after reboot - it was the only way to install the update (was jumping from last years September update).

i patched boot.img from the latest factory image (redfin-sp2a.220305.012-factory-49873101.zip) and applied fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img. ended up with 'your data may be corrupt' message. i am on magisk 24.3 stable and used platform-tools r31 (maybe this was the issue). i tried to flash unpatched boot.img and unmodified (without disable verification arguments) vbmeta.img but still getting 'your data may be corrupt'. i am ok with clean flashing latest factory image and wiping data - was goig to do this anyway but i have some doubts:

1) is fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img still deprecated ? the official magisk instructions still mention it (screenshot of magisk 24.0 so i guess it is quite recent) on https://topjohnwu.github.io/Magisk/install.html

2) what about step 8b (fastboot boot magisk_patched.img) here - https://www.droidwin.com/how-to-root-pixel-devices-via-magisk-on-android-12/ i recon this guide is from 10.21 but this guy specifically mentions the 'your data may be corrupt' message. the problem is fastboot boot magisk_patched.img also ends up in 'your data may be corrupt' :)

thanks in advance
[Google Pixel 5 Guides, News, & Discussion] yurisan:
update:

i manage to boot correctly using fastboot boot (into both, clean or magisk patched) but only after i flashed clean boot.img and vbmeta.img. booting into permanently flashed images (clean or patched and using direct install from temporarily booted magisk patched boot) ends up in 'your data may be corrupt'

also updated to latest canary magisk app and latest platform-tools
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

Ok, I just wanted to know, thanks for the answer !

Thx !
[Google Pixel 5 Guides, News, & Discussion] yurisan:
i stumbled upon the this post - https://xdaforums.com/t/guide-root-pixel-5-android-12-with-magisk.4187609/post-86056561 and yeah it is confusing lol.

i think my scenario was 3 and it still failed not 100% sure though...

anyway, i am going to clean flash the factory image - the question stands - should i pass --disable-verity --disable-verification after flashing magisk patched boot and before reboot or should i leave the vbmeta clean ?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Why did you disable verity and verification? This should only be necessary with a custom kernel, or older versions of Magisk prior to 24.

Yes, those instructions are out of date, that's why they're struck through.

It's best to ask questions before you do things you don't fully understand, because of the potential to cause more problems for yourself.

At this point, I would suggest you clean flash the factory image. Follow the instructions in the OP and don't deviate; if you have questions about something, ask before experimenting. You're 100% at your own risk here.

NO. No need to disable verity and verification if you are not using a custom kernel. Did you not read the OP?

I don't know what all has changed with recent versions of Magisk, but I had absolutely zero trouble with the March update. I dirty flashed the factory image and patched using Magisk 24.2. Currently using Canary 24304 with no issues.

I believe the problem is with the OTA method. Any version of Magisk Stable from v24, or Canary from v23106 should work. If you have Magisk modules installed, you are responsible for knowing how to troubleshoot.
[Google Pixel 5 Guides, News, & Discussion] yurisan:
thanks for the answer - already after a clean flash, with magisk rooted and safetynet passed. i assure you i did read the instructions.

in this case i just followed the instructions from the official magisk site (https://topjohnwu.github.io/Magisk/install.html) and i think they should be updated specifying that vbmeta should only be modified for custom kernels.

not sure what has failed this time - i guess the problem was somewhere in between android 11>12 update and lots of magisk updates during last period.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
A lot of that information is out of date. I've been working pretty hard at keeping my guides up to date. Next edit is probably going to address Magisk modules, as many of these can cause a bootloop
[Google Pixel 5 Guides, News, & Discussion] Toronadian:
So I tried the "dirty flash" method with removing the "-w" from the flash.bat file in the factory image zip for my wife's Pixel 5. That went fine. Unfortunately, I could not use a patched image from Magisk Canary 24301. I have checked and I had removed all modules first (Systemless Hosts, and Universal SafetyNet Fix). It would cause the phone to bootloop and then go back into fastboot mode. I did the same thing with my Pixel 6 and there were no issues. To get out of bootloop, I had to flash the stock boot image for March.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Try a previous version of Magisk
[Google Pixel 5 Guides, News, & Discussion] Toronadian:
Figured out the issue. WIfe's Pixel 5 was on an earlier version of Magisk Canary, but I patched it with Magisk Canary 24301 on my phone. Therefore, the patched boot file was I guess newer than the app version on the Pixel 5 thus it was causing issues. Re-patched the boot image with the Pixel 5 on the older version of Magisk and things worked out.
[Google Pixel 5 Guides, News, & Discussion] a4abbas:
@V0latyle

I had system auto updates turned on so I just lost the root today, I have Pixel 5 its was on Android 12 I was rooted using your OTA method. How do I root again without losing my data and apps? Please advice

View attachment 5570545
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Patch and flash the boot image.
[Google Pixel 5 Guides, News, & Discussion] a4abbas:
Shall i go for either Pixel OTA Images or Pixel Factory Images ?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Please read the OP. Follow the instructions under "Initial Root"
[Google Pixel 5 Guides, News, & Discussion] eriks0n:
Before I try the "Update and Root Automatic OTA" approach, is there anything to watch out for?

The instructions say to uninstall magisk before downloading the OTA.

I haven't asked the Android device to update but I am seeing the prompt to restart to install the OTA. Does this mean it's too late for me to take this approach as the OTA has already downloaded and I have yet to uninstall magisk?

When I updated the last two times I did a factory update, I want to try to avoid that as I don't want to reset up all my two-factor authentications in Google Authenticator.
[Google Pixel 5 Guides, News, & Discussion] eriks0n:
Also will updating with Factory Images without a data wipe clear out my 2FA entries in the Google Authenticator?
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

I would like to understand the part "Initial Root / Create Master Root Image"

Is it compulsory ? because last time I had to use the phone.

I'm updating with Android Flash Tool.

Thx !
[Google Pixel 5 Guides, News, & Discussion] eriks0n:
I ending up just updating with factory images.

My SafetyNet check continued to pass and root is working flawlessly with this method.

This process works well, just need to create a new "master boot.img" file with the updated factory files before following the instructions, this part is implied in the instructions.

But doing this I didn't lose my Google Authenticator entries.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Don't uninstall, just restore images - but this shouldn't be necessary because of the below:

No. It apparently already passed block verification. Just open Magisk, disable any modules you have installed, then tap Install > Install to Inactive Slot. Magisk will patch the boot image in the other slot then force a reboot to that slot.

Just follow the instructions and you'll be fine. Make sure you disable modules just to be safe. If for whatever reason you get a boot loop, flashing the factory boot image should get you running while you figure out the problem.
[Google Pixel 5 Guides, News, & Discussion] AnyNameYouWish:
Anyone else having issue with google pay?

I just rooted with latest factory image and the wallet tile is disabled...

All I have done after root is add modules

- MagiskHide Props Config 6.1.2-v137

- Universal SafetyNet Fix 2.2.1

I pass safetynet attestation in YASNAC

And add followings in Magisk DenyList (all sub-component for each) :

- Google Play Protect Service

- Google Play Store

Google Play Service as well, but it doesnt stay after reboot (I saw on page 9 that it's normal behaviour)

Am I missing something or is it related to latest firmware update?

Edit : maybe some more details can be interesting:

- Magisk canary

- in Settings / Google / Settings for Google Apps / Google Pay : my bank card is set and seem to be operational (bank validated it and the NFC logo isnt greyed or crossed)
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Initial Root essentially describes the process to root your device, coming from unrooted factory firmware. A patched boot image is required for root. An unpatched boot image does not have root.

Make sure you've enabled DenyList on GPay as well. There do seem to be some occasional quirks upon initial root, but generally GPay continues to work as long as everything is set up correctly. I'm able to add/remove cards and use NFC without a problem.
[Google Pixel 5 Guides, News, & Discussion] AnyNameYouWish:
Can you share what's on your DenyList? I don't see any GPay while searching for it in Magisk...

Here's mine (and yes, I have a nice butt thanks to the 30 days challenge app)

And the wallet tile
[Google Pixel 5 Guides, News, & Discussion] eriks0n:
It's called "Google Pay"
[Google Pixel 5 Guides, News, & Discussion] AnyNameYouWish:
I don't have any "Google Pay" app in the deny list entries, but I found the sneaky bastard so now my denied apps are

- Google Play Store

- my banks apps

- this com.....wallet app

Doing a clear cache and data of Google Play service and reboot solved the problem

Thanks for your answers and digging!
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
View attachment 5581321

Google Pay has been superseded by GPay. The only important items on the list are Play Store and GPay, and honestly if you already have GPay installed, you don't even need to block Play Store. I simply did because of Play Protect.

I've blocked the other apps for various reasons - all payment and DRM apps (Venmo is also on the list), social media (observed odd behaviour from Facebook with unblocked root), and for some reason the smart home stuff doesn't work properly with root either

View attachment 5581327