yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] badabing2003:
Actually it is safer without --slot=all

Let me give a scenario

Let's say in April you flashed to All and it is working, so both slots are good.

In May you flash to all and it turns out to be a bad one.

Now both slots are bad

On the other hand if you only flash to one, then you can change the slot and boot to the older image, granted it will get too old over time since flash all flashes to the active slot and not inactive one, but at least you still have a bootable older option.

Of course almost always flashing stock would fix it, but why risk messing both at the same time.

A better option (however takes more time) is once you confirm that it worked, switch the slot and flash to it as well, this way both slots would be current and functional.

I personally don't bother, I just flash to the active one, but that is a personal choice.

Thinking about it, perhaps the best option would be is to mimic the OTA slot approach with flash_all

basically just change the slot first, and then flash to the active slot, if it works you're good, if it doesn't you switch back and you only go back to the last month's version.

With this approach the inactive slot will only be 1 version behind.
[Google Pixel 6] V0latyle:
I see what you're saying, and for the most part I agree. The only thing is, you'll always be flashing the factory image with a PC, so if something goes wrong you can just dirty flash the last working image.
[Google Pixel 6] badabing2003:
Yep, so true.
[Google Pixel 6] soodz:
I did the slot b trick with magisk for the July update and everything was smooth as usual for me... Passing safetynet, modules still working, all systems go
[Google Pixel 6] soodz:
Oops
[Google Pixel 6] V0latyle:
What version of Magisk?
[Google Pixel 6] V0latyle:
Do you have your Magisk app hidden? Your package name is odd.

And you said "slot B method", do you mean you downloaded the OTA then patched inactive slot in Magisk?
[Google Pixel 6] soodz:
I do have magisk hidden as 'Safari' and yes by Slot B method I mean patched inactive slot in Magisk before rebooting to complete the OTA update. 👍
[Google Pixel 6] V0latyle:
Interesting. How did you command the reboot?

When I tried to update this way on my wife's 5a, it bootlooped back to the original slot.
[Google Pixel 6] soodz:
I always follow these steps once I know the OTA is available:

1. Open Magisk and select 'Uninstall Magisk -> Restore Images'

2. Open Settings and Download/Install OTA *DO NOT REBOOT*

3. Go back to Magisk and select 'Install -> Install to Inactive Slot (After OTA)' *DO NOT REBOOT*

4. Go back to Settings and 'Reboot' to finalize the OTA
[Google Pixel 6] V0latyle:
Interesting. Maybe it's something specific to the 765G devices that broke the out of band method.
[Google Pixel 6] Uunderfire:
Just a warning with this method, I tried it myself in order to update to July's security update. The download worked correctly once Magisk was uninstalled, however after I chose to install to the inactive slot I went back to the OTA screen, pushed the "Reboot now" button and then the OTA started to install again. Then it showed a message saying that the update is impossible (as if it had detected magisk again on the current slot). I am sure that I chose the "Install to inactive slot" button and not the classic install.

I then tried to flash manually with the factory image with the --slot=all command, however I had quite a scare as the update failed due to a lack of space on slot B (I was on slot A at the beginning so slot B was the one where the OTA was performed). I tried without the --slot=all and it failed again on slot A due to an error with the product image. After another try it worked on slot A and I could boot again and then patch the boot with Magisk.

I think that the OTA temporary corrupted one of my slots, I am going to stick to the manual method from now on.
[Google Pixel 6] V0latyle:
Why did you go back to the OTA restart screen? When you patch the inactive slot in Magisk, Magisk will then prompt you for a reboot.

I don't know if it makes any difference whether you reboot via system or via Magisk.
[Google Pixel 6] Uunderfire:
Since I had an issue in May with the OTA update and since soodz succeeded in performing the update, I wanted to follow the exact steps written in his post to see if it made a difference.

Thinking about it, it may have made a difference in my case as it triggered this weird reinstall behavior of the OTA. I may try to directly reboot from magisk next time to see if it makes a difference ! And switch to a manual install again if it wreaks havok on my other slot ahah
[Google Pixel 6] airtower:
Anyone lose Google Wallet tap to pay recently?
[Google Pixel 6] torsti:
Same here. Wallet detect rooted pixel phone. I think it will take a while to "fix" this.

Fiat Ludi Incipe :)
[Google Pixel 6] PeteT:
Yes i did. Safetynet passes but google pay (wallet) won't register a new card. It detects my phone is rooted
[Google Pixel 6] V0latyle:
I used it earlier today but just now got the notification. Seems they have some other form of root detection.

I noticed mine stopped working, and I had Google Wallet installed...but tap to pay is still working on my wife's 5a, and she doesn't have Wallet installed.

For those of you whom it's stopped working for, have you been using Wallet?

Edit: Got it to work again (I think). Cleared data for both Wallet and GPay, uninstalled both. Rebooted device. The GPay tile still shows up in quick settings, but it now says "Hold to reader".
[Google Pixel 6] NCVol:
Mine seemed ok after doing something similar but when I tried to use it at a store it failed with the rooted security message. Did yours work?
[Google Pixel 6] tom1807:
My workaround: Stop the Google Wallet, clear cache. After that it worked for an hour and then back to square 1.

Cheers

Tom
[Google Pixel 6] Tscharser:
After following this:

https://xdaforums.com/t/magisk-google-wallet-pay-with-magisk.4471279/

I am using google wallet with the currently up-to-date version of google play services for two days without issues.
[Google Pixel 6] NCVol:
Which fingerprint settings did you use following the terminal steps? I followed them but it still didn't work for me.
[Google Pixel 6] Tscharser:
I just selected edit device fingerprint, picked certified fingerprint and then selected Google Pixel 6 and confirmed.
[Google Pixel 6] andreipaval:
Did you also clear data for Play Services ?

I'm reluctant to do this, because it could have bad side effects with the Google cloud messaging on the device.
[Google Pixel 6] tom1807:
I didn't, only data of Wallet.

Cheers

Tom
[Google Pixel 6] andreipaval:
I also did all those steps, changed fingerprint to Pixel 6, but I already had a P6, and cleared data of Wallet and Play Store.

But still Wallet detects root.

LE: Correction, even if initially Wallet complained the software does not meet security requirements, after 3 day of doing nothing, it seems now it's working fine.

Weird!
[Google Pixel 6] V0latyle:
I was able to get contactless pay working again by removing GPay and Wallet, and simply using embedded GPay.

The issue here isn't a configuration problem. Google is migrating away from SafetyNet and Play Protect Certification to a new API, Play Integrity. This new security implementation is able to detect root, for reasons as yet unknown, and there is no fix for it yet.

More information here
[Google Pixel 6] MatMew:
Hey OP and everyone, thanks for this awesome guide. I'm getting stuck on the SafetyNet part, I've tried every possible scenario and combination. Still can't get my Commonwealth Bank app to add a contactless card successfully, and Google Wallet says "This phone can't be set up for contactless payments".

I'm using the latest Magisk, have denied apps access and enabled this feature. Zygisk is enabled. I have the reccomended modules but still am not able to use contactless.
[Google Pixel 6] V0latyle:
I don't provide support for SafetyNet. Here is the thread on USNF
[Google Pixel 6] tom1807:
Funny observation yesterday.

After following the steps in the above link, Wallet worked from the next day. Also "survived" the recent Wallet updates (now v2.150.463719012).

However, checked my security settings and Google complained that I didn't update my P6 over 3 months and showed Security update from October 2021(!).

Rebooted the mobile and I am back on July 5, 2022.

Cheers

Tom
[Google Pixel 6] oksagi:
Pixel 6 with latest Magisk 25.2.

MagiskHide Props module.

Changed the fingerprint, cleared cache for Playstore, Play services and walled app.

I was able with these steps to pay via wallet yesterday.
[Google Pixel 6] andreipaval:
Does anyone else have trouble with the Google Play system update ?

I have the June 1 version and it says there is a 594 kB system update available,

I press Download&Install, it's installing for a few minutes then it prompts me to reboot.

But after I reboot it's the same old June 1 version with the update available prompt.

I've tried for like 7 times, on both the old 220705.003 July patch and on the new 004 July patch

but it never actually installs.

Could it be because I changed the device fingerprint with MagiskHide Props ?, but I changed it

to the same Pixel 6. I did that because Google Pay was detecting root.

It's strange that I also did not get the update prompt with the new 004 patch update,

I used to always get the monthly updates when checked for system updates.

Any ways to fix this ? Thank you.
[Google Pixel 6] tom1807:
Yeah, had the same, until yesterday, then I got a 712 kb(!) Play System update. And...

still July 1, 2022. And then no more further updates.

Cheers

Tom
[Google Pixel 6] GrandAdmiral:
Looks like the monthly update is trying to download now, but nothing's available on the image/OTA page to download yet.
[Google Pixel 6] oksagi:
Yes this is due to the MagiksPropsHide.

Just disable to module restart the device, finish the updates and enable the module back.

profit.
[Google Pixel 6] phaino00:
A13 is available.
[Google Pixel 6] torsti:
Update / Upgrade to android 13 same process as it was? Restore image in magisk, update and reboot in second slot?
[Google Pixel 6] V0latyle:
Yes, this should work. Make sure you're using the latest version of Magisk as previous versions don't support Android 13.

Worth noting:

That being said, it's usually possible to run an older version of Android on newer bootloaders.

To test this, if you're planning on updating anyway, download the factory image and update the bootloader only without updating system.
[Google Pixel 6] badabing2003:
FYI, I tried to live boot my Pixel 6 that was on A12 with A13 boot.img file, but that didn't work, then I tried to boot to patched A13, same story.

Just upgraded to A13 with PixelFlasher, that worked smoothly and kept root, at this point I have no interest of downgrading, but having that option would have been nice, I doubt that we would be able to.

By the way why is it dated June 24? two months old? does that mean that we're missing july and August security patches?
[Google Pixel 6] r00tcracker:
Any early reports on passing safetynet on 13 with USNF 2.3.1?

Any issues? Etc?
[Google Pixel 6] badabing2003:
Mine is passing with the modded 2.3.1

I have not experienced any issues yet.

Wallet is also seems to be working, I was able to add a card.
[Google Pixel 6] r00tcracker:
Thank you!

I will wait until more reports come out, see if anything is not working properly before I update.

I know this is not a module thread, but do you by any change use any modules that were working before but not now?

I use LSPOSED and was wondering if that was still ok

Thanks again!
[Google Pixel 6] V0latyle:
No idea. I believe you can downgrade /system, you just can't downgrade the bootloader.

No issues here on my Pixel 5

SafetyNet isn't really the concern anymore....Play Integrity is, and we will never be able to pass with unlocked bootloaders

More information here
[Google Pixel 6] GrandAdmiral:
If I sideload the OTA do I need to extract and create a new master boot image from the A13 factory image to boot the master image?
[Google Pixel 6] V0latyle:
Yes. The Android 12 boot image won't work.
[Google Pixel 6] :
Hey, I have sideloaded A13 and extracted the boot.img from factory zip and patched it on magisk. When i try to fastboot boot the patched img, it reboots and is infinitely loading at the Google logo. The moment i reboot the original boot img it boots up. Using latest Magisk Canary
[Google Pixel 6] snake218:
I tried to update uninstalling magisk and restoring image, but said i have no backup available.

So i used PixelFlasher to update and root again, using instructions on OP, all good.
[Google Pixel 6] V0latyle:
Yes, however users updating via OTA are experiencing bootloops. Since you're downloading the factory image anyway I recommend using it to perform the update.

Use the factory image method. For some reason the OTA updates don't like the patched image.
[Google Pixel 6] GrandAdmiral:
Done. Thanks. Will likely make the move to PixelFlasher moving forward since sideloading might no longer being an option.
[Google Pixel 6] V0latyle:
I imagine it's just something in Magisk that needs to be updated eventually.
[Google Pixel 6] hungyip84:
I forgot to patch the boot before flashing and now is stuck. Anyone can share the patched boot for 13.0?

Thanks.
[Google Pixel 6] V0latyle:
How are you stuck? You don't have to patch the boot image before flashing; it just means you'll need to boot into system without root then use Magisk to patch the boot image just as you would have done before.
[Google Pixel 6] mbonus:
Couple questions on A13 update assuming using full factory image with latest platform tools:

Is it best practice to flash both slots since there is no going back to A12 bootloader?

Is it a requirement to enable the -w flag when coming from July A12? (I understand it is probably best practice, but is it necessary?)

If both slots are A13, is it preferable to boot patched image and direct install in Majisk(25201)?
[Google Pixel 6] V0latyle:
At least the bootloader, yes.

No.

It depends. If you want to be able to update via OTA in the future, use direct install. If you flash the patched image, Magisk won't have a backup of the stock boot image.
[Google Pixel 6] airtower:
Not necessary to wipe, just update it as you would an A12 factory image.
[Google Pixel 6] pa.pn2:
Hey guys,

i updated to Android 13 today, turned off all modules before flashing.Booted fine

After I re-activated some modules, also a Font Module, but its bootlooping now.

i tried to boot into safe mode, it starts and shows safemode, but after entering the pin code its just a black screen blinking, and instantly rebooting again.

it also boots into recovery where i can choose try again or factory reset.

Tried to flash the factory image again, but no success, at some point im in revocery, try again or factory reset.

Soemthing seems to be broken or corrupted.....

Any idea how to get it back without factory reset?

And i have to to factory reset, do i still have to patch the vendor image or was it vbmeta??

Mhh even flashing vbmeta doesnt help ****...

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img is not necessary if i boot or flash the patched kernel correct?
[Google Pixel 6] Jeryhho:
I have the latest magisk canary build, and the OTA update is not working. I restore images in magisk -> OTA install -> reboot -> bootloop. I am not installing the latest android because bootloop performed on all Android 12 builds. How can I install OTA without bootloop?
[Google Pixel 6] V0latyle:
Your bootloop appears to be caused by a Magisk module. Boot into Safe Mode by holding the Volume Down button after the unlocked bootloader warning appears. Magisk should detect safe mode and suspend modules. Disable them all, and enable one at a time followed by a reboot until you discover which module is causing the problem. Modules that change system function or appearance on Android 12 may not work correctly on Android 13. For more help, post in the Magisk General Support/Discussion thread.

Neither - factory reset only wipes /data and does not restore any images.

Because this appears to be a Magisk module issue. The stock (unpatched) boot image should boot but you won't have root.

No, not necessary.
[Google Pixel 6] V0latyle:
Restore images (unless you haven't re-rooted) and install the OTA normally. Do not attempt to patch the inactive slot. Let the system boot normally (without root) and finish the update including all optimizations. Then, you can download the factory package, and extract and patch the boot image.

Alternatively, since you would need to download the factory package anyway, just update that way. Pixel Flasher makes it much easier, although you'll need to start with root so that Pixel Flasher can patch the boot image.
[Google Pixel 6] pa.pn2:
tried safemode already, phone boots up, but after entering the pin, no homescreen, phone just flickers and reboots....

have to go fresh i guess...
[Google Pixel 6] V0latyle:
Well, I'm trying to help.

What happens if you boot the stock boot image? If it's the same thing, you may have a different issue.
[Google Pixel 6] pa.pn2:
same result....

i did a clean flash now, after i just flash the patched the patched A13 kernel and im good?

didnt know that the verity stuff isnt needed anymore, makes it more easy then
[Google Pixel 6] V0latyle:
I was going to recommend sideloading the OTA (or dirty flashing the system image) to see if that fixes the stability issue. Most times, wiping your device shouldn't be necessary.

From this point, you just need to patch the A13 boot image. You can either flash it in bootloader, or if you want to be able to update via OTA, live boot it and perform Direct Install in Magisk.
[Google Pixel 6] pa.pn2:
i wrote with the creator of the font magisk module, its not compatible with A13 anymore, maybe it corrupted something...
[Google Pixel 6] V0latyle:
Entirely possible. I generally avoid modules that alter anything in /system because those are the most likely to cause boot loops.
[Google Pixel 6] gazdajezda:
After install, A13 is perfectly root-able and all works ok as it should (adaway, safety net, banking apps)? Or last A12 will do fine? 10x
[Google Pixel 6] V0latyle:
Working great for me on my Pixel 5. Magisk 25201, with systemless hosts + AdAway. Using Displax mod USNF 2.3.1, passing SafetyNet, all my banking apps work including GPay/Wallet.
[Google Pixel 6] gazdajezda:
Great 😀 Download factory image, patch boot.img, flash without -w and after that, flash patcjed boot.img - that's it, still?
[Google Pixel 6] V0latyle:
Yes, with one exception - Flash bootloader to both slots, even if you don't intend to with system.
[Google Pixel 6] gazdajezda:
Ok, thanx. Apreciated 👍
[Google Pixel 6] squidbutt:
I used the ota that the phone sent me and before rebooting,went to magisk and patched inactive slot. Root retained with modules working. BCR 1.18 working also
[Google Pixel 6] V0latyle:
Glad it worked for you. Make sure you flash the bootloader to the old slot when you get a chance.
[Google Pixel 6] mbonus:
Also, I'm sure you all know this, but use the latest AdAway from their git. (I was using an old version that didn't update to the latest and it didn't work with A13)
[Google Pixel 6] tom1807:
I don't use AdAway at all anymore. I added under private DNS in Network & Internet "dns.adguard.com" and honstly I see no difference to AdAway.

Cheers

Tom
[Google Pixel 6] V0latyle:
I use systemless hosts, and I also use the Energized host lists although they now have a Magisk module as well.
[Google Pixel 6] mbonus:
Thanks Tom! Looks like I have some research to do :D
[Google Pixel 6] Toronadian:
Alright, looking to update my phone to Android 13 some time this week or next. I just updated to the second July update, and on build number SQ3A.220705.004. How I updated to the second July update I did it my usual way of:

- disable all my Magisk Modules; the 2 that I use are: Systemless Hosts (for Adaway) and Universal SafetyNetFix v2.2.1 (I will likely be updating to the newer 2.3.1 MOD version that will allow Wallet to work; not that I even use Wallet anyways TBH)

- download the latest factory image and extract the boot.img, and patch it with the latest Magisk Canary build (which for me right now is version 25201)

- edit the "flash-all.bat" file and remove the "-w" flag so that it doesn't wipe my phone

- restart phone into fastboot mode and run "flash-all.bat" and then let the phone boot up

- go back into fastboot mode and flash the patched boot

- restart the phone, then re-enable the 2 modules I was using previously

Is this method OK for updating to stable release of Android 13?
[Google Pixel 6] V0latyle:
Yes. I use the same two modules and have never needed to disable them. Good habit though. The one thing I would add is insert --slot=all to the bootloader line at the very least.
[Google Pixel 6] Toronadian:
Thanks. the "--slot=all" comes in the following part correct?

As well, did you use the latest stable Magisk or latest Canary?

EDIT: Also wanna ask, the flashing of the bootloader to both slots is ALSO required for the Pixel 5 as well correct? Planning on doing this for my wife's phone as well on her 5.

EDIT #2: Got things working on my Pixel 6. Had "--slot=all" added to the bootloader line as I posted, and have also rooted on the latest Magisk Canary. Gonna wait for your response before I start trying this on the 5.
[Google Pixel 6] V0latyle:
Yup

Canary 25201

Nein. The ARB issue is only on the Tensor devices - Pixel 6, 6 Pro, 6a
[Google Pixel 6] Toronadian:
Thanks. Got both of our devices now on Android 13.
[Google Pixel 6] badabing2003:
Starting with root is not a requirement.

If you start with root, then patching boot.img is all automattic and non interactive, the user does not have to do anything to patch.

If you are not already rooted, or don't allow root to shell process, then PixelFlasher will still transfer the boot.img to the phone, launch magisk (if it is already installed) and interactively guide the user to do the manual patching of boot.img (telling what to click), after the patch is done and the user presses ok, the boot.img is transferred back to the PC and the rest of process continues.

What does ARB stand for?

This is confirmed to be definitely an issue on Pixel 6*?

Any detailed discussion about this in a forum thread?

Thanks.
[Google Pixel 6] V0latyle:
Good to know.

Anti-RollBack

Yes

There sure is

The gist of it is this: once Android 13 boots successfully on the new bootloader, it will increment the rollback counter which will prevent downgrading the bootloader. Older system can still be flashed with --force argument but as with all downgrades this requires a data wipe.

There is also the possibility that if only one slot is updated, and the phone later bootloops back to the non-updated slot, the device could brick because it will refuse to execute the old bootloader.
[Google Pixel 6] tensux:
i just did a clean install of A13, I am having a hell of a time rooting using the latest magisk. I tried the canary version as well. i am getting this message trying to flash the patched file:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a magisk_patched-25201_tEdrJ.img

target reported max download size of 261095424 bytes

sending 'boot_a' (98304 KB)...

OKAY [ 0.814s]

writing 'boot_a'...

(bootloader) unable to update boot image: use unmerged...

FAILED (remote: failed to flash partition (boot_a))

finished. total time: 0.863s

any help?
[Google Pixel 6] V0latyle:
What does Magisk show when you've booted with the patched image? See the OP for what it should look like for successful root.
[Google Pixel 6] tensux:
thanks its showing n/a as if it snot installed, i just slowed down and realized it wasn't actually flashing. I edited my post showing the message i was getting
[Google Pixel 6] phaino00:
Stop using minimal adb and fastboot. Use platform tools. It's out of date.