yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5 Guides, News, & Discussion] AnyNameYouWish:
I haven't installed the Gpay app since it's natively included in my P5, so I don't have anything similar to yours nor "Google Pay" as suggested by eriks0n.

Only the "systemui.plugin" wallet... I guess it's related to some local specifications...

Anyway, thanks again for prompt answers - and for the OP tutorial :)
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

In what order to do it ? As I said, last time I was afraid to lose everything :)

Sorry, but it's a bit confusing for me.

Thx !
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
If you have not unlocked your bootloader, you will be forced to wipe data when you do so. There is no way around this. Fortunately, most of your data on your device backs up to the cloud, so you won't lose everything. Keep in mind that Photos does not back up every time your system takes a snapshot, so make sure you perform a manual backup in the Photos app.

To root your device, follow the instructions under Initial Root.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I updated my P5 and my wife's P5a yesterday using the factory image method. I am running Canary 24305 on my P5, and she is running Stable 24.3 on hers. Absolutely no problems.
[Google Pixel 5 Guides, News, & Discussion] Regys:
My phone is already rooted and unlocked , I have the January version.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Okay, so you're asking how to best update without wiping data?

Any of the methods described in the OP will allow you to do this. I personally recommend dirty flashing the factory image, but you'll need to update bootloader and radio.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Yes no wiping,

just know when exactly should I install my modified boot.img

After the flash or the flash/reboot?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
After the flash, before you reboot.

This is the command I use to flash my Pixel 5:

fastboot update --skip-reboot --slot=all <update image file path>

The update package reboots the device into fastboot; when the update completes, the device is still in fastboot due to the --skip-reboot option. Then, I flash the patched boot image: fastboot flash boot --slot=all <patched boot image file path>
[Google Pixel 5 Guides, News, & Discussion] noxqzs:
I followed instructions for rooting my Pixel but absentmindedly forgot to disable automatic updates. Phone was rebooted after the update. On page 11 of this thread, I noticed a user (a4abbas) with a similar situation. Could you confirm that the steps to regain root are:

(I am on stock ROM with just magisk and no modules. )

download factory image for current update I am on.

extract boot.img

patch with magisk in phone

fastboot the updated file

reboot

I apologize if this question has been asked over and over.

thanks for your contributions to the forum.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
You're on the right track.
[Google Pixel 5 Guides, News, & Discussion] Regys:
it restarted after the update. but I patch the boot.img.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Ok, now flash the patched boot image.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Yes, is work fine.

Thx for all !
[Google Pixel 5 Guides, News, & Discussion] MpandAUS:
Great useful thread, ty! Just one question... Is it not possible to backup your data while your on stock and haven't unlocked the bootloader yet? How to backup your data when you havent unlocked the bootloader or rooted it? Surely there has be another way of do a complete backup besides the google crappy backup feature.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Not really. Android has incorporated data segregation for apps for a long time, so it's impossible for any one app to read data from another app, with the exception of "shared" data in storage. The only way around this is root, which is not possible without an unlocked bootloader.
[Google Pixel 5 Guides, News, & Discussion] omartins:
Personally, I use Swift Backup (root mode), but, according to the developer change log, it was recently included a modality without root, keeping a considerable share of the backup capabilities... give it a look.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Again, it's not possible for an app to backup other apps' data without root. This is a security feature that's been a part of Android for quite some time to prevent malicious apps from accessing sensitive information.
[Google Pixel 5 Guides, News, & Discussion] laughoutloud:
after holding off for months, I was forced to update from 11 to 12 (April patch) and attempted to use the factory img update method to do it while maintaining root. the update went smoothly and I do have root, but safetynet fails across the board. magisk is up to date and I have USNF. any ideas appreciated!
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I recommend using Canary 24306 until Stable 24.4 is released.

I also recommend against using Riru unless you are using modules that explicitly require it. You're using the wrong version of USNF.

On my Pixel 5, I'm passing SafetyNet with this configuration:

Stock ROM, stock kernel Magisk patched

Magisk Canary 24306, Zygisk and DenyList enabled

DenyList configured for Google Play Store (does not affect SafetyNet but will fail Play Protect)

Module: MagiskHide Props Config 6.1.2

Module: Universal SafetyNet Fix 2.2.1

SafetyNet confirmed passing with YASNAC
[Google Pixel 5 Guides, News, & Discussion] laughoutloud:
looks like the out of date USNF was the culprit. thanks!

magisk manager doesn't display the canary channel as an option for me, only stable and beta (and custom). should i just plug the canary channel link into custom? if so, where could i find that link?
[Google Pixel 5 Guides, News, & Discussion] AnyNameYouWish:
This post will help

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/#post-86320325
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
You'd have to uninstall Magisk, then download the canary version from the button on the Magisk page:

View attachment 5595237
[Google Pixel 5 Guides, News, & Discussion] cubandanger05:
Updated to May's release. I'm still using Magisk 23001 - don't judge me. Followed these steps, never fails:

1. Download the new full factory image

2. Extract the file. Then extract boot.img from the image zip file within.

3. Copy boot.img to your pixel 5

4. Patch it with magisk

5. Move back the patched file, rename it to boot.img

6. Update the original zip file titled image-redfin-r*.zip with the new boot.img file (override the older one)

7. Edit flash-all file by replacing -w with --disable-verification --disable-verity

so it won't wipe your device clean

8. Reboot phone to bootloader and flash with flash-all
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Here's how I updated my Pixel 5 and wife's 5a:

Downloaded and extracted May factory image.

Rebooted device to bootloader.

Bootloader and baseband versions have not changed; skipped.

Applied factory image:

fastboot update --skip-reboot --slot all <image-device-buildnumber.zip>

When update completed, rebooted to bootloader

Booted April patched image (24305) from previous update: (I cheated here and reused the Pixel 5 boot image on my wife's 5a; bramble, redfin, and barbet hardware are identical, so the kernels are too)

fastboot boot <April patched image>

Device booted into Android with root. Opened Magisk, tap Install, tap Direct Install, reboot.

Running 24.3 Stable on wife's 5a, Canary 24306 on my 5.
[Google Pixel 5 Guides, News, & Discussion] cubandanger05:
Sounds like a lot 😁
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
It's really not, it's rather straightforward especially when you've been doing it for years
[Google Pixel 5 Guides, News, & Discussion] cubandanger05:
Whatever works I guess 😉
[Google Pixel 5 Guides, News, & Discussion] DeathUp:
I've had a rooted Pixel 5 for a while, suddenly whilst using it, it rebooted and now it's stuck constantly refreshing at the bootloader is unlocked screen. I'm confused what could of caused this. I was still on android 11 at the time. Is there anything I can do to recover my data or stop it?
[Google Pixel 5 Guides, News, & Discussion] andybones:
If you are stuck and can't boot to ROM, and don't have the phone backed up.

One think you should be able to save is your Internal storage by installing TWRP and pulling the contents to a PC.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Making sure I understand this correctly, it doesn't even start to boot the kernel (Google logo), it's just bootlooping at the orange bootloader screen?

Try booting the stock boot image for your build; if you can't remember what your build number is just use the latest A11 image.
[Google Pixel 5 Guides, News, & Discussion] cubandanger05:
You know this happened to me on 12. Phone would randomly go into a bootloop. I don't know what the screen is called but it's the one when you first boot the phone and you get the option to pause the booting process. The only ways I found I could stop it was to plug the charger to it then hold the power button as it was bootlooping and that made it stop. Don't know what causes it.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I would suggest reflashing the boot image. Try unpatched first to see if it corrects the issue. If it only happens with a patched image, you are probably using the wrong version of Magisk.
[Google Pixel 5 Guides, News, & Discussion] cubandanger05:
Thank you. I am still rocking magisk 23001, which may well be the culprit. It hasn't happened again after I removed a couple of patches I didn't use, but will definitely try the latest magisk on June's update and see.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
You cannot use a lower version of Magisk than 23016 on Android 12. But yes, Stable 24.3 should work fine. Not sure if it works for delta OTAs though. I personally use the latest Canary.
[Google Pixel 5 Guides, News, & Discussion] DroidRommer:
Hello all! Sorry if this question has already been answered but I was wondering if anyone has tried to root lineage 19.1 on pixel 5 (redfin)

Thank you so much,

DroidRommer
[Google Pixel 5 Guides, News, & Discussion] Homeboy76:
Yes!

[ROM][OFFICIAL][redfin] LineageOS 19: OP, Instructions "to install".

Install LineageOS on redfin: Scroll down and read Installing LineageOS from recovery,

6. (Optionally):

... These are the instructions for sideloading

magisk alpha/beta/canary/stable.zip

to root.
[Google Pixel 5 Guides, News, & Discussion] DroidRommer:
Thanks so much! Sorry for not just simply reading the whole post
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
This thread is for rooting and updating the stock ROM and kernel, so the methods here may not work on custom ROMs.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I updated to June the way I always have:

Patched new boot image in Magisk

Reboot to bootloader

Flash bootloader and radio

Reboot to bootloader

Dirty flash factory image (--skip-reboot --slot=all)

Flash patched boot image to both slots

Reboot; update complete.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

I come to ask if the root is still ok. nothing change we can do root as usual ?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yes
[Google Pixel 5 Guides, News, & Discussion] AquilaDroid:
Any things I need to be aware of flashing this over January Android 12 Beta 2 build? Thanks for your continued support!
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Do you mean Android 13 Beta? 12 has been official release since September of last year. If you're downgrading from 13 I would strongly recommend a clean install.
[Google Pixel 5 Guides, News, & Discussion] AquilaDroid:
No, still on the Android 12 beta which I had to install to get out of a mess that you helped me with back in January (see post #128).
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Oh, okay. You should be able to update to the latest release using the method of your choice. I would personally recommend dirty flashing the factory image.
[Google Pixel 5 Guides, News, & Discussion] nalpo:
Hi there,

first of all, thanks for your work! I tried updating OTA with your suggestion, updated magisk first to v. 25101 and then followed your steps. After rebooting it seems that I lost root now. Do you have any advice on how to fix it? I still have the old, flashed boot.img available, if that helps.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Did you reboot through Magisk, or did you select Reboot now after installing the OTA update?

You should be able to temporarily boot an older patched boot image:

fastboot boot <Magisk patched boot image>

Then perform Direct Install in Magisk.
[Google Pixel 5 Guides, News, & Discussion] nalpo:
Thanks for ypur quick answer :).

I rebooted using Magisk. Rebooting using fastboot worked and I could install root with Magisk and reboot. Zygisk was not installed and the phone now wants to have the OTA update again, hm.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Did you patch inactive slot in Magisk before you rebooted?

Check your current firmware (swipe notifications all the way down, it'll be right under the quick settings). Current is SQ3A.220605.009.A1. It's possible that the device rebooted to the "old" slot.
[Google Pixel 5 Guides, News, & Discussion] nalpo:
It says SP2A.220305.012 Is there any way to boot from the other slot?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I wouldn't try without updating again.

Follow these instructions exactly:

Follow the prompts to download and install the update, or force update via Settings > System > System Update. Do not reboot.

When prompted to reboot, go into Magisk, then tap Install > Install to Inactive Slot. Magisk will prompt you to reboot; follow the prompts.

Device should reboot into updated slot with root. If you get a failure message during OTA, go into Magisk, tap Uninstall, then Restore Images, before trying to update again.
[Google Pixel 5 Guides, News, & Discussion] nalpo:
I did what it says exactly, but I always ended up with an old version. But I was able to solve it with your "Update and Root OTA Sideload" method. After flashing booting the old master-root.img, I did the described steps and now I have the newest firmware with root. Thanks :)
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Don't flash an old boot image after updating. You can temporarily boot it to give Magisk root so that it can patch the new image.
[Google Pixel 5 Guides, News, & Discussion] nalpo:
My bad, I meant booting, not flashing. I edited the mistake.
[Google Pixel 5 Guides, News, & Discussion] cubandanger05:
Updated to July's image. No issues.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
What method did you use?
[Google Pixel 5 Guides, News, & Discussion] cubandanger05:
1. Download the new full factory image

2. Extract the file. Then extract boot.img from the image zip file within.

3. Copy boot.img to your pixel 5

4. Patch it with magisk

5. Move back the patched file, rename it to boot.img

6. Update the original zip file titled image-redfin-r*.zip with the new boot.img file (override the older one)

7. Edit flash-all file by replacing -w with --disable-verification --disable-verity

so it won't wipe your device clean

8. Reboot phone to bootloader and flash with flash-all
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Disabling verification and verity is not necessary, unless you're using a custom kernel.
[Google Pixel 5 Guides, News, & Discussion] cubandanger05:
Can't be too careful.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
It has nothing to do with caution, it's completely unnecessary - unless you're using a really old version of Magisk.
[Google Pixel 5 Guides, News, & Discussion] cubandanger05:
I guess I meant if it's not hurting anything
[Google Pixel 5 Guides, News, & Discussion] contaoxxx:
Hi

I can not find July Update:

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

But I get every day an OTA update message on my phone.

Current build: SP2A.220505.002
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
It's right there...

View attachment 5656997

Here's the link for the image: 12.1.0 (SQ3A.220705.003.A1, Jul 2022

You're on the May update. 220505 = Year 2022, Month 05, Day 05....although they've been using 05 since November, even though the firmware hasn't always been released on the 5th of the month. It's typically the first Monday, sometimes Tuesday.
[Google Pixel 5 Guides, News, & Discussion] contaoxxx:
A1 is not working>boot loop
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
What method did you use to update and root? It's working great for me.

Out of band OTA patching seems to be broken with this update.
[Google Pixel 5 Guides, News, & Discussion] contaoxxx:
Unzip file:

- flash.bat (-w flag remove)

- adb reboot bootloader

- double click flash.bat

==> system broken now>reboot directly to fastboot mode.

Only images without A1 are working
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
If you currently have root, try using Pixel Flasher.

If you are not rooted, follow the instructions under Update and root factory image in the OP.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Announcement:

It appears that the July update has broken out of band update patching on the 765G devices (4a 5g, 5, and 5a).

For the time being, you can either use an alternate update method (factory image, sideload OTA, etc), or you can update and re-root following these instructions (you will temporarily lose root!):

Restore images in Magisk

Download and install the update

When prompted to reboot, do not attempt to patch alternate slot in Magisk; instead, just follow prompt to reboot normally

After system reboots, verify you're on the updated firmware (bottom of notification panel or Settings > About > Build Number)

Allow update to finish (there should be a notification and progress bar in the notification panel)

Reboot to bootloader

Live boot a previously patched Magisk image:

fastboot boot <patched image>

When system boots, open Magisk and perform Direct Install.
[Google Pixel 5 Guides, News, & Discussion] cubandanger05:
Keep telling you, my method never fails 🙃
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Your point is moot. I've always used the factory image as well, although I don't disable dm-verity or vbmeta verification, and I've never had any issues.

The majority of issues with updating seem to be associated with the OTA, and since many users still prefer to update that way, I posted the notice.
[Google Pixel 5 Guides, News, & Discussion] cubandanger05:
I understand, not need for us to get excited over it.
[Google Pixel 5 Guides, News, & Discussion] andybones:
+1, been on A12 for a little over a month. Same method I used for A11 has worked for me. I always choose to manually update using factory image. Worked great from June to July build.

Thank you for the great guide, my friend!
[Google Pixel 5 Guides, News, & Discussion] AtrixHDMan:
Can someone help me.Pixel 5 with running lasted Android 11 with magisk I installed and can't see all apps in Play Store.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Please ask this question in the Magisk discussion thread. You're probably failing Play Certification.
[Google Pixel 5 Guides, News, & Discussion] AtrixHDMan:
I got it to work somehow.Thanks.
[Google Pixel 5 Guides, News, & Discussion] andybones:
Are you guys using Magisk beta or Magisk canary?

And which do you prefer.

I've been using canary, but I've considered switching up for beta 25.2

However, canary has everything that beta does, so is it worth it?

Also how would I switch?

Uninstall Magisk, in the Magisk app, uninstall the app, reboot

Install Magisk beta 25.2, patch and flash the kernek?

Thank you, sorry if this is a bit off key.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I've been using Canary.

Switching from beta to canary is as simple as installing the app. However, since canary is usually a newer version than the beta (current 25201 vs 25200), you'd need to uninstall Canary, then install Beta. If you want to re-patch the kernel with Beta, then you'd need to perform a complete uninstall within Magisk, then boot with a rooted image and perform Direct Install once you've installed the beta. However, it's not really necessary to re-patch the kernel if it's working.

Alternatively, you could change the update channel in Canary to Stable or Beta, which means you wouldn't get an update until there's a new release on those channels. This would probably be the cleanest and most foolproof way to do it.
[Google Pixel 5 Guides, News, & Discussion] andybones:
Thank you my good Sir.

I believe I'll stick with the Canary.

Everything is working wonderfully, though I may need to do a factory reset for the August factory image because Now Playing just won't download the database fully.. it still does find songs.. sometimes, others I need to manually hit the lock screen icon, but it's very annoying to say the least.

I also pulled a very noob move and disabled all trackers in the Warden app without backing them up, thus some apps aren't sending me notifications anymore.

Sorry for the last off topic things, just angry that I goofed lol.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Relevant

Looks like Beta and Canary are pretty much the same. Debug builds are only for developers. Canary channel immediately incorporates changes that will be implemented in the next public channel release.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

The August update is not released ?

When will version 13 be released ?

thx !
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
It'll get released when it's released. No word on when Android 13 will be public.
[Google Pixel 5 Guides, News, & Discussion] Regys:
HI,

thanks for info
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Welp...

I just attempted to update to A13 using the OTA method, and bootlooped back to Android 12.

However, I had no trouble installing the factory image.
[Google Pixel 5 Guides, News, & Discussion] kfhughes:
And you were able to get root successfully?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
It's worked before on Android 12. It seems most people upgrading to 13 are experiencing boot loops when they either sideload the OTA or use the automatic install.

TBH I've found it much more time consuming to apply the OTA update, because the system has to parse, extract, and write the contents of the OTA package. On a high speed Wi-Fi connection it took about 10 minutes to download the OTA yesterday, then another 20ish to attempt to perform the update...which ended up failing anyway.

When I got home, I updated using the factory image, which took me all of 5 minutes tops.

Interesting that you were able to successfully update and root using the OTA. Others are experiencing boot loops.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

Why version 13 is dated 220624 (TP1A.220624.014, Aug 2022) ?

So the update can be done without worry in Factory Images ?
[Google Pixel 5 Guides, News, & Discussion] eriks0n:
Any issues with Root via the Factory Update method? This is also the method I prefer using.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
That's probably the build date, they just held off on releasing it until now.

Yes. This is how I updated my Pixel 5 without a problem.

See above.
[Google Pixel 5 Guides, News, & Discussion] cubandanger05:
Updated to A13 and rerooted. No issues so far.
[Google Pixel 5 Guides, News, & Discussion] digger16309:
Dirty flash or clean flash? I would prefer to dirty flash because it's faster, but know the general guidance it to clean flash when upgrading to a new version.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I performed a dirty flash with the factory image. Zero issues.
[Google Pixel 5 Guides, News, & Discussion] cubandanger05:
Dirty.
[Google Pixel 5 Guides, News, & Discussion] digger16309:
Sorry for the double ask, but for the sake of clarification, dirty flash from A12 or from A13 Beta?