yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Either should be fine.
[Google Pixel 5 Guides, News, & Discussion] cubandanger05:
I came from A12
[Google Pixel 5 Guides, News, & Discussion] xsR1zU:
I suspect my success was because I didn't bypass using the reboot button that is presented when the system update is ready to reboot, and I didn't flash the patched boot image until after rebooting into the newly updated version for the first time.

The process I used was similar to that of unrooting, taking the OTA, and then rooting again, except that I don't have to download a factory image in order to regain root -- I just use the boot image that is installed as part of the update.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Oh okay. So you basically did a normal OTA without using Magisk to patch the "new" slot until AFTER the update was complete. Makes sense.
[Google Pixel 5 Guides, News, & Discussion] yickhcr:
i can confirm dirty flashing from A12 to A13 works without data loss, kept root; took the same steps as i would've with any other monthly update.

One thing i did notice is that google wallet now says "phone doesn't meet security requirements" when i check "tap to pay setup", HOWEVER previously stored credit cards seems to load fine and still available? i havent had a chance to test making an actual payment yet so cant say if tap to pay is really fked or not

View attachment 5688329View attachment 5688327View attachment 5688331
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Are you using the @Displax modded Universal SafetyNet Fix module?
[Google Pixel 5 Guides, News, & Discussion] yickhcr:
Yes i am
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I don't use Wallet personally but GPay is working fine.

Installed Wallet and it seems fine too.

View attachment 5688383
[Google Pixel 5 Guides, News, & Discussion] yickhcr:
didnt google wallet replaced google pay?

anyway, i dont know why it says it doesnt meet the requirements but i can add a new payment card

i *suspect* if i clear storage&cache for wallet/play service/play store it will work... but i dont want to re add all the cards if i dont have to... will try making an actual payment and see if it works
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
No...at least not yet

There's actually 3 apps:

Embedded GPay - system app in Pixel devices and some others, cannot be replaced by Wallet

Play Store GPay - standalone app, which as I understand it is going to be updated to

Play Store Wallet - standalone app, which as I understand it is going to replace GPay

Your cards are saved to your Google account (if synced) so even if you clear storage for the app it should re-sync everything.

Clearing cache doesn't remove any configuration from the app.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

Ok, so no need to flash or wipe the device, we do as usual ?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Update as normal, as long as you don't have a Pixel 6 / 6 Pro / 6a.
[Google Pixel 5 Guides, News, & Discussion] Regys:
OK, thanks !
[Google Pixel 5 Guides, News, & Discussion] Regys:
Great fine A13, but toggles wifi+cell is back.

How to separate them ?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
What do you mean? The Internet quick settings tile is not a toggle. Tap on it, and the window that pops up allows you to toggle WiFi and/or mobile data.
[Google Pixel 5 Guides, News, & Discussion] Regys:
there was the possibility to separate the 2 like here:

How to get the old Wi-Fi toggle back on your Android 12 phone

Just a couple of minutes and two ADB commands

www.androidpolice.com
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Oh, I have no idea.
[Google Pixel 5 Guides, News, & Discussion] scootley:
Hi,

Pixel 5 running Android 12 SQ3A.220705.003.A1. Trying to go from stock to vanilla root using Magisk Canary (25202).

Patched stock boot image just fine.

I am trying to just do a temporary root for a single boot using "fastboot boot ..."

Has worked fine many times in the past.

But after fastboot, it seems to try to boot, shows the Google logo, and then shuts down and is charging and showing the percentage charged. (in other words, it won't boot and just shuts down)

Of course I can then power on the device and it boots fine back into stock.

Fastboot command:

fastboot -v boot magisk_patched-25202_eIqnE.img
Sending 'boot.img' (98304 KB) OKAY [ 2.688s]
Booting (bootloader) boot.img missing cmdline or OS version
OKAY [ 1.560s]
Finished. Total time: 4.321s

Any ideas?

Update: Actually I just got it to boot. Same exact patched image as originally. All I did was pull the USB cable out of the phone right after fastboot completed (was using Linux)

Thanks
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
How is everyone's battery life on Android 13? Mine seems to be much MUCH worse.
[Google Pixel 5 Guides, News, & Discussion] digger16309:
I wouldn't say my battery life is much worse but I do see a bit more drain than on A12. Since I did a clean install, I had to go in and change all my apps back to restricted battery, one-by-one. I have a ton of frozen Google apps and processes but I think PLAY Services is a culprit.
[Google Pixel 5 Guides, News, & Discussion] AnyNameYouWish:
Same, it's not "much" worst but I feel like it isn't as good as it used to be on A12
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

Yes me too !
[Google Pixel 5 Guides, News, & Discussion] omartins:
It is definitely worst. After a few cycles with my standard pattern of usage I see a 10% less deep sleep in CPU state stats (BBS data).

I've now disabled the Adaptive Connectivity feature, let's see if it is related or not...
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Where is that?

It's bad enough I'm considering either a full wipe or downgrading
[Google Pixel 5 Guides, News, & Discussion] omartins:
Here
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
No, I meant the Adaptive Connectivity setting. Never mind, I found it
[Google Pixel 5 Guides, News, & Discussion] doras100p:
Perhaps someone could help me with this as I can't find myself in this thread -

I have a Pixel 5 that I rooted when it was on Android 12.

Then at some point it forced an OTA security update, after which it no longer seemed rooted and Google Wallet stopped working.

Then it was OTA updated to Android 13 (this time by me, not forcefully by the device)

I no longer need it to be rooted, but I do wish to go back to using Google Wallet, is there anything I can do that doesn't require formatting my phone?

If I do format my phone, is there any special percussions I should take?

Thanks!
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
If your bootloader is still unlocked, you have two choices:

1. Lock the bootloader (which will wipe data)

2. Re-root and use the modified Universal SafetyNet Fix module by @Displax

Otherwise, the device will fail security requirements, and there is no way around it.
[Google Pixel 5 Guides, News, & Discussion] a4abbas:
Do you suggest to stay on Android 12 for now?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
It seems to have improved some with the September update.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hi,

I did the last update, perfect, but I would like to do a deep hard reset.

How do I proceed please ?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
What do you mean by "deep hard" reset?
[Google Pixel 5 Guides, News, & Discussion] Regys:
Hard Reset
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
That still doesn't answer my question.

The most you can really do is a factory reset, which wipes /data and /storage.
[Google Pixel 5 Guides, News, & Discussion] Regys:
ok only by the system, hard reset is not possible

1/ Factory Reset is deep format than Hard Reset ?

2/ Factory Reset redefines the bootloader?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I still don't quite understand what you're asking. What do you mean by a "hard reset"?

As I stated, factory reset wipes all user data and system settings. Only the critical system partitions are untouched.

There is no way to "reset" the bootloader - you can reflash it, but this is rarely necessary.

What exactly are you trying to do?
[Google Pixel 5 Guides, News, & Discussion] Regys:
I just want to reset all my phone, And make an clean installation with the last update.

I go through recovery mode and do the factory reset. I want to keep my bootloader unlocked
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Okay. Factory reset doesn't affect the bootloader at all so it won't relock your phone.

If you want, you can reflash your devices AND wipe it at the same time. Follow the instructions under "Update and Root Factory Image", but make sure you add a -w to the command when flashing the update, so it would look like this:

fastboot update -w <update image>

You can still use the other arguments at the same time, so if you wanted to flash to both slots but prevent a reboot so you can flash a patched boot image, use:

fastboot update -w --skip-reboot --slot all <update image>

There is one more option that's potentially more thorough....

You can use the Android Flash Tool and check the "Wipe device" and "Force flash all partitions" boxes. Make sure that you uncheck the "Lock bootloader" box if you want to leave it unlocked. This will reflash every partition on your device.
[Google Pixel 5 Guides, News, & Discussion] Regys:
I'm going to do it in several times, I can't with these commands.

Factory Reset

Flash last version and Root
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Okay, the commands I gave you will work. You can wipe data at the same time you're flashing the latest version.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Ok, Where exactly should the zip be extracted ? In platform-tools ?

otherwise the order will be that ?

fastboot update -w <redfin-tp1a.221005.002>
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I generally extract the factory zip to its own folder, just to keep things separate. I don't put any of the files or images in the platform-tools folder, because I can drag and drop the files into the command window.

No - you'd be flashing the zip that is inside that package: image-redfin-tp1a.221005.002.zip

See this post
[Google Pixel 5 Guides, News, & Discussion] Regys:
I understand, doing it this way is better indeed. I don't know Pixel Flasher

what do you call "both slots" ?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Pixel Flasher thread

It's a program that automates the ADB and fastboot commands. You don't have to extract anything or handle any files, the program does it for you. It's still a good idea to familiarize yourself with how ADB works as well as how to flash the phone manually, so that you understand what's going on.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Yes, I see later

last thing, what do you call "both slots" ?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Pixel devices are A/B partition layout - meaning that the critical partitions (/bootloader, /radio, /boot, /system, /vbmeta, etc) all have two slots - /boot_a and /boot_b. Normally, when you flash the factory image, it just flashes to whatever is currently the active slot (you can see this at the bottom of the bootloader screen). Sideloading the OTA on the other hand always installs to the other slot.

The A/B layout is used for seamless system updates - while the system is running on one slot, it can download and install an update package to the other slot, then schedule a reboot to that slot, so that the only "interruption" in the user experience is the reboot.

Example: You're currently on slot A, running the September update. When the October update comes available, the system can download and install it to slot B. Following a reboot, the system boots slot B, so you're now on the October update on slot B, and slot A becomes inactive. Then, when the November update drops, the system can download and install it to slot A.

It's generally not necessary to flash the factory update to both slots.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Ok, thank you for all these explanations and for your time to answer them.

I do by the cmd as you indicated. I just want to do a factory reset and remove all traces of app etc. that have been on my phone for 2 years. and do a clean install
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Okay. Are you trying to keep root?
[Google Pixel 5 Guides, News, & Discussion] Regys:
Yes !
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Okay. Then just follow the steps under "Update and Root Factory Image", and add -w to the command when you flash the update.

Alternatively....this will require more work and more steps....you could use the Android Flash Tool to force flash all partitions, then reboot the device to bootloader and flash the patched boot image.

But, factory reset (data wipe) should be sufficient.
[Google Pixel 5 Guides, News, & Discussion] Regys:
Nice ok,

I use Android Flash Tool to make update, is a good tools.

Just check "Wipe Device" and "Force Flash All Partition"
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Yup
[Google Pixel 5 Guides, News, & Discussion] Regys:
Thx !
[Google Pixel 5 Guides, News, & Discussion] Durchmesser:
Since last update of Lineagos my Pixel5 misses root. So I rebootet to recovery and detected twrp is not anymore on my phone.

I downloaded twrp and flashed it.

aftert that twrp ssems not boot and oly show the twrp logo.

Since i changed to bootloader i now stick on fastbootd and nothing wort. neither fastboot recovery nor fastboot vendor_boot.

I get permission error. and reboot every time ends in fastboot.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
This thread is for the stock firmware. If you need help with LineageOS, you need to post in the LineageOS thread for your device.

TWRP cannot be flashed on our devices...

This is why. When you flash TWRP to /boot, you overwrite the boot image, so now the only thing in /boot is TWRP. The Pixel devices do not have a discrete recovery partition, so to install TWRP, you must live boot the TWRP image, then perform Install within TWRP to patch the existing boot image.

However....

TWRP and Magisk both depend on patching the boot image, and in my experience, do not work together. I personally see little need for using TWRP on our devices because of the ability to flash individual partitions directly from fastboot.

This is why it's important to learn about how everything works before you start changing things. I have no idea what all you've done to your device so I can't very well tell you how to fix it.

If you want to start over, try using the Android Flash Tool to re-install the OEM firmware to your device. Since you had a custom ROM installed, make sure you check the Force flash all partitions and Wipe device boxes.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
That should not be necessary, but you can do it anyway to be safe. I would advise that you wait to patch the boot image until after you've updated.
[Google Pixel 5 Guides, News, & Discussion] drjat:
Hi. I have rooted for the first time on my Pixel 5 running latest Android 11 (not 12) with Magisk Canary 23016. My issues: Play Store is showing that device is not certified - so I am unable to install certain apps. Any help / advice on this please. Thanks
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Enable Zygisk and DenyList in Magisk settings. Configure DenyList for all components of Google Play Services and Google Play Store. Install Universal SafetyNet Fix 2.2.0.

Works for me.
[Google Pixel 5 Guides, News, & Discussion] TKruzze:
Are you certain about the DenyList for Google Play Services? Everything I've read says to NOT add them to the list. Besides, I think they're automatically removed if you do try and check them.

Everything works perfectly fine for me without Google Play Services added to the DenyList.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Can you link a source? I haven't had any issues.

That's entirely possible, I've gone back in several times and it does appear as though DenyList "forgets" Google Play Services.

I don't remember who, I think it may have been @Didgeridoohan , but someone had mentioned that using MHPC + USNF was sufficient for SafetyNet pass. However, I think I did have to block Play Store because Play Protect wasn't happy otherwise.
[Google Pixel 5 Guides, News, & Discussion] Didgeridoohan:
@TKruzze @V0latyle If you're using USNF it doesn't matter if you add the necessary gms components to the Deny listh. The module will always remove them since keeping them on the list will actually keep USNF from doing it's thing.

For simple SafetyNet pass Universal SafetyNet Fix is all you need (and possibly MagiskHide Props Config if you need to spoof a device fingerprint).
[Google Pixel 5 Guides, News, & Discussion] ipdev:
To expand a bit on what Didgeridoohan mentioned. ;)

From the USNF thread.

Post # 1,318 Link

Post # 1,327 Link

Cheers. :cowboy:
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Thank you, gentlemen!
[Google Pixel 5 Guides, News, & Discussion] a4abbas:
A little confused here about which method to follow for retaining root when the new update of Android 12 comes... I am already on Android 12 nonrooted and locked bootloader.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Follow the instructions under Initial Root. All you have to do is unlock bootloader, then patch and flash the boot image. Make sure you're using Magisk Canary 23016. Links are in the OP.
[Google Pixel 5 Guides, News, & Discussion] hfam:
Wow V0latyle, fantastic post and update, eternal thanks brother! I had a family tragedy and had no opportunity to do the update from 11 with M23 stable to 12, so this is great news.

Since I'm still on 11 rooted with 23 stable, and I used to perfotm the updates with factory full images (remove -w), and patch/flash new boot.img, seems we are now able to do this again, woo! I've never used any Magisk other than stable, so canary makes me a bit nervous just because its new to me.

Can you confirm my intended process is correct here? Pixel 5a5g, a11, M23:

- uninstall riru and SNF 1.x (the only 2 modules installed)

- uninstall Magisk 23 via the "uninstall" button in Magisk Manager, and reboot

- install Magisk Canary 23016

- perform update to a12 using platform-tools with factory full image for 12 using flash-all (remove -w)

- push new v12 boot.img to phone, patch with mm 23016

- pull patched boot.img from phone, push to phone as new boot image

- install SNF 2.2.0(or 2.2.1 as of today)

Voila, rooted and updated to v12 (hopefully?)

Did I miss anything, got something wrong, or is this appropriate?

Thanks again V, your dedication to XDA is beyond appreciated!

hfam
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
I believe you should be aboe to go into Magisk Settings, change your update channel to Canary, and update that way. But yes, either way will work.

Looks good to me. Good luck!

It's what I do. :cool:
[Google Pixel 5 Guides, News, & Discussion] NervGaz:
So I've been holding off rooting after accidentally accepting A12 (#brotip don't touch system updates when drunk) and this looked all well and good. Gave it a shot and I get stuck on the g logo with the progress bar with a rooted boot image. Clearly I'm being dumb and doing be something wrong, can't find anything similar while searching. Anyone wanna point out how I'm dumb or what I'm going wrong? If a quote is what I'll have to do, cool I'll do it, was just trying to avoid it. I've checked the correct version of magisk etc. I'm not missing a setting it something am I?
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
Nope, it should just work.

Are you using the latest version of Platform Tools? Make sure you aren't accidentally using an older version in a duplicate folder.

Are you running the commands in Command Prompt, not PowerShell?

Are you using the correct factory image corresponding to your current software version?

Have you tried a different USB cable and/or PC?

Magisk version is 23016?
[Google Pixel 5 Guides, News, & Discussion] NervGaz:
Yup, platform tools downloaded today as never installed on that pc before, using CMD as powershell is a pain, double checked the factory image including flashing the download without wiping just to be sure when it first failed, no other pc to try at the moment, double checked magisk version... No idea idea why it doesn't work. The only thing I can think of is that I was rooted on Android 11 and there are leftovers from that magisk install causing issues, but I have no idea how to clear that if it is the case...
[Google Pixel 5 Guides, News, & Discussion] hfam:
Perfection!! Thanks for taking time to write this up and champion the research to make it accurate! Updating worked *exactly* as it did prior to the boot loop/wipe the device first issue. Your instructions were clear and concise. SO thankful for you, and all the rest of those who keep this all so straightforward and the countless hours and days spent to provide these tuts and data.

One quick question, I no longer have a "safetynet check" button in the magisk app, used to be right there with the "uninstall" button. Should I be seeing that or was it removed from the app? If it's removed, what's your preferred method/app to do a proper SN test?

Thanks again V, eternal gratitude!!

hfam

PS. For anyone going from v11 rooted with Magisk stable 23 to 12 and Magisk canary 23016, I recommend before beginning;

- in Magisk app, remove all modules and reboot

- In Magisk app, choose "complete uninstall", it will reboot when done

- install Magisk 23016 to install the app, and go no further

- now if doing a full factory image update to 12, perform the update, push the new boot.img to your phone, patch it, pull patched back to PC and flash it to boot (I defer all to V0latyle, not trying to hijack the thread, just add a bit of what worked for me.)

TL/DR: (if using Magisk 23 stable on v11) Remove all Magisk modules, reboot, remove magisk app, reboot, prior to doing v12 update and root. It may not be a requirement but I confirm it worked super clean for me, all went 100% perfect following V0latyle's instructions.
[Google Pixel 5 Guides, News, & Discussion] V0latyle:
That shouldn't be causing a bootloop, although it is possible. The only way to completely clean up a Magisk install is by using Complete Uninstall within the app, which only works if you have working root. The only way to clean up a Magisk install without root is to wipe data. I would suggest doing just that - wipe data, then attempt to boot the patched boot image.

Thank you.

That function was removed as of Magisk 23010. You'll have to use a third party app to verify SafetyNet pass. I don't have a particular recommendation.
[Google Pixel 5 Guides, News, & Discussion] ipdev:
The one recommended in the Magisk thread is by Xingchen & Rikka.

YASNAC - Yet Another SafetyNet Attestation Checker - PlayStore - Link

YASNAC - GitHub - Link

Cheers. :cowboy:
[Google Pixel 5 Guides, News, & Discussion] hfam:
As always, ipdev brings the gimmicks to the party!! Thanks again brother, we are all so lucky to have you here, have a wonderful New Year one and all!