yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6] V0latyle:
You don't have to restore anything. The safest way to upgrade is by sideloading the OTA; you can then re-root after the update is finished.

However, THIS IS EXTREMELY IMPORTANT: READ >>>THIS<<< BEFORE YOU UPDATE TO ANDROID 13.

No - you don't patch both slots, the boot image has nothing to do with the bootloader.

This is what you should do just to be safe:

Go into Magisk and tap Uninstall > Restore Images. Reboot.

Follow the instructions in the first post of this thread to sideload the OTA. Use the latest OTA image.

After updating using the OTA, let the device boot into Android and finish its update.

Once the update is finished, sideload the OTA one more time - the OTA method does not update both slots at the same time, so you want to make sure that both bootloader slots get updated.

Once you have updated BOTH slots, follow the instructions under Initial Root to re-root.

I would recommend going to Magisk Stable 25.2 as the canary/alpha builds have been troublesome. I would also recommend updating Universal SafetyNet Fix with this modified USNF module to pass Play Integrity.

If you feel a bit more brave, you can update using the factory images, since you'll need to download those to get the new boot image anyway. The only difference is that before you do anything else, you would want to flash both bootloader slots at the same time:

fastboot flash bootloader --slot=all <path to bootloader image or drag+drop into command line>
fastboot reboot bootloader

Verify that the bootloader version is bootloader-raven-slider-1.2-9465321
[Google Pixel 6] V0latyle:
BTW, you can use PixelFlasher to update too, it'll even patch the boot image for you. Really streamlines the process. Make sure you use the "Flash to both slots" option as it will flash both bootloader slots at the same time.
[Google Pixel 6] gazdajezda:
@V0latyle : thank you for this. I will do OTA sideload. There is just one thing I do not know what is gonna happen. You write:

Also, I have been informed by the system that after reboot update of downloaded update will be performed. So, after I will uninstall Magisk and choose Reboot, update will start? And after it finish I do a sideload? Or shall I uninstall Magisk and then boot to recovery directly with:

Sorry, if this is lame question, but I prefer to ask than sorry.
[Google Pixel 6] V0latyle:
I forgot that you have an update pending.

Just to be safe, disable the modules in Magisk. You can go ahead and reboot normally and let the automatic OTA do its thing.

Once it's done, you can sideload the OTA, but you'll only need to do this once as the system will have updated one slot.
[Google Pixel 6] gazdajezda:
So, I just disable Magisk modules and reboot for pending update do the work? Or shall I also uninstall Magisk, switch images before reboot?

And if system boots into some strange mode (as last time) I can then just do a sideload or in worst case flash/wipe (as last time)?

Ok, tommorow after work I will read all this again and do the process (I need a working phone on work, so I will do that tommorow - it's getting late here). Thank you for all!
[Google Pixel 6] V0latyle:
Just disable modules. The OTA overwrites the boot image in the other slot

Strange mode? What do you mean?

Honestly the best way to update, I think, would be using the factory method via Pixel Flasher. It'll update both bootloader slots at the beginning so at the very least that will prevent a bootloader brick.

Make sure you are using Platform Tools 33.0.3. Do not use 34.0+ yet.
[Google Pixel 6] Svensemann666:
IF anyone is struggeling to get root on his Pixel 6 on the actual DP Android 14 : bluejay_beta-upp2

Use the Pre Build from Magisk 25.2:

https://easyupload.io/u0hpgk or get offical from

https://github.com/topjohnwu/Magisk/actions/runs/4373376674#artifacts

Use the boot.img from the Pixel 7, the one i uploaded is already patched:

https://easyupload.io/4rc9lh

or get offical from https://developer.android.com/about/versions/14/download

Also dont forget to install Displax Safetynet Mod 3.0 by Displax

GitHub - Displax/safetynet-fix at integrity

Google SafetyNet attestation workarounds for Magisk - GitHub - Displax/safetynet-fix at integrity

github.com

Greetz :)
[Google Pixel 6] V0latyle:
What is the "Pre build" you posted?

I strongly advise to ONLY download Magisk from the offical Github repo.
[Google Pixel 6] Svensemann666:
Its the official Magisk Canary Build, found it on the Pixel 7 Pro Section

Here is the official Link, i wanted it to make it easy :)

Support `untrusted_app_32` · topjohnwu/Magisk@1a16467

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Google Pixel 6] gazdajezda:
I did it & all it happened was just a normal ordinary reboot, hehe. Still on A12 (june 2022 release). This phone is cursed... Do not understand nothing, really.
[Google Pixel 6] V0latyle:
Odd. This is probably because the Automatic System Updates toggle in Developer Options was turned off.

Go ahead and use Pixel Flasher + the factory update image.
[Google Pixel 6] gazdajezda:
For now I will leave it as it is. Everything works. Update will come in play on weekend, when I have a time. For now, this is it 😀
[Google Pixel 6] V0latyle:
Please post your question only once, per the Forum Rules:

Instructions for updating and rooting your device are in the first post of this thread.
[Google Pixel 6] darkerm:
Which version do I need to flash to make sure I can Downgrade to any older Android version? Please help
[Google Pixel 6] V0latyle:
I don't think you understand this whole anti-rollback thing. Once you upgrade to Android 13, you will not be able to downgrade to a previous version. You can force an Android 12 factory image to install on the Android 13 bootloader but it will not work properly. I'm not sure how this applies to custom ROMs.

The difference between the versions you pictured is only in the baseband (modem firmware). Everything else is the same.
[Google Pixel 6] darkerm:
so after I update to any A13 ROM I wont be able to go back to any older ROM at all?

I just unlocked the Bootloader and I am in A12 stock. Should I just go and update the OTA to A13? If I do so can I root A13?
[Google Pixel 6] V0latyle:
It sounds to me like you didn't do some necessary reading.

Please go back and read the original post in the warning thread where you first posted.

Remember that before you ask a question in a thread, you should read the WHOLE original post. Many of the questions you're asking have been answered, and it's rude to ask when the answers are readily available.

Once the official Android 13 update completes, the bootloader anti-rollback protection will be enabled, meaning you will not be able to flash an older bootloader version. Since the factory update images check for bootloader and baseband versions, the only way to install an Android 12 image is with the --force flag, but the official Android 12 release does not work properly on the Android 13 bootloader.

Again, I do not know how this affects custom ROMs.

That is up to you.

Yes, the instructions in the first post of this thread tell you how to do this.
[Google Pixel 6] armourer1:
So, sorry I am lost and I think it would be better to ask then lose my phone -:)

I have reading various methods to update and here my state now:

I am on Android 12, May 5 2022 (SP2A.220505.002) Canadian Version of Pixel 6

I have the latest Canary Magick installed: 25210, both app and boot image pathed.

So, what is my best route of update as I understand it:

1. open Magisk, tap Uninstall, then Restore Images.

2. reboot, I will lose my root - I undertand

3. Check for OTA and install it

4. Check what version I have after OTA (I hope it will be latest 13) and donload the same image

5. Extract bootloader and "fastboot flash bootloader --slot=all xxx"

6. Go the regular root path from the first post

Thanks a lot for any help!!!
[Google Pixel 6] Homeboy76:
If you want to root your phone after updating, follow one of the following sets of instructions in the OP

Spoiler: Update and Root Factory Image

Spoiler: Update and Root using PixelFlasher <<RECOMMENDED FOR NOVICES>>

Spoiler: Update and Root using the Android Flash Tool
[Google Pixel 6] armourer1:
@Homeboy76 Thanks for prompt reply!

I do want to root, but trying to take safest route as possible.

Do you think that one of the 3 methods you have suggested will be safer to upgrade from 12 to 13 for the first time ?
[Google Pixel 6] Homeboy76:
Spoiler: Update and Root using PixelFlasher <<RECOMMENDED FOR NOVICES>>
[Google Pixel 6] badabing2003:
OTA on the phone will be one OTA at a time, so you have almost 1 year worth of OTAs to apply, and it is very slow on the phone.

Beisdes, the bootloader flashing to both slots needs to be done when you transition from August 2022 (or earlier) to September 2022 (or later) only (not after every OTA update)

You're better off getting the factory image and flashing that.

If you're going to do it manually by modifying the flash_all script, you'd have to be careful, you can't pass the flag --slot all to the fastboot update image command as that is broken, but you definitely want to flash the bootloader to both slots, in one shot instead of flashing one and then switching and flashing again.

Like @Homeboy76 suggested, the easiest path would be with PF, but first uninstall Magisk Manager 25210

Flash stock

then install Magisk stable or 25206 and create a patch and just flash the patch.

Good luck, and if something is not clear, ask questions to avoid potential bricking, make sure you read this.

https://xdaforums.com/t/warning-read-this-before-your-initial-upgrade-to-android-13.4480307/
[Google Pixel 6] armourer1:
@Homeboy76 & @badabing2003 Thanks a lot !

Took PF route with latest image and device booted without issues, but I have lost root.

So, I have rerooted again with Magic stable 25200.

How can I verify that both my slots are 13 now ? Or just hit "Flash boot" for pathed image again in PF and check Flash to inactive slot ?
[Google Pixel 6] kiwigi:
I made some notes in a word document some time ago by copying from this forum...

Check if both bootloaders a/B have been updated to Android 13:

adb reboot bootloader(option to start this with cable to pc connected phone with oem unlock and usb debug)

or

volume down and the power

(you can enter here to unlock bootloader) fastboot flashing unlock ( wipes data+installed apps)

current-slot
fastboot getvar version-bootloader
fastboot --set-active=a or b (set to inactive slot)
fastboot getvar current-slot
fastboot getvar version-bootloader
fastboot --set-active=a or b (set to original slot)
fastboot getvar current-slot
fastboot reboot bootloader
fastboot reboot
[Google Pixel 6] armourer1:
@kiwigi Thaks a lot,

Checked and both slots returned version-bootloader: slider-1.2-9465321, so seems that everything was flashed correctly by PF...
[Google Pixel 6] pa.pn2:
Did the new magisk update fix all previous probs?
[Google Pixel 6] Lughnasadh:
Systemless Hosts module (and maybe others) still not working but a fix has been found.

I was able to patch the Pixel 6 Pro boot image (instead of the Pixel 7 Pro boot image) on A14 as well, so that bug appears to be fixed (compression issue).
[Google Pixel 6] pa.pn2:
Did Google remove the March Factory Image?

Cant find it on their Page, and is April Image delayed again?
[Google Pixel 6] phaino00:
I can see them on the download page. The links work as well.
[Google Pixel 6] pa.pn2:
Also the April build?
[Google Pixel 6] pa.pn2:
Weird, I just see the Images if I switch language from German to English haha
[Google Pixel 6] V0latyle:
Pixel 5 with 26.1, no issue with AdAway + systemless hosts on UPB1

They're visible to me....
[Google Pixel 6] Lughnasadh:
Yeah, this issue was present in previous Canary versions but has since been fixed in the latest Magisk versions with this.
[Google Pixel 6] chuppito:
Hello, on the site https://developers.google.com/android/images?hl=fr the version stops at 13.0.0 (TQ1A.230205.002, février 2023).

where can i download the latest version so i can extract the boot.img? THANKS
[Google Pixel 6] pa.pn2:
You need to switch to English, then it will show up all versions, seems to be a bug on their page
[Google Pixel 6] pa.pn2:
guys i tried to flash may build manually.

i booted into fastboot,changed to slot b, started the flash all.bat without the -w.

After flashing i booted back to bootloader and changed to slot a and used to flash the same,. but i got an error.

Now even if i type fastboot devices i just get questionsmarks ,if i use the command to change to slot a, it says Device does not support slots.

What happend here? Is it maybe the outdated platform tool 33.03?

Shall is use 34.01 or which versuion works?

Have never seen that before lol
[Google Pixel 6] badabing2003:
33.0.3 is good, 34 on the other hand is not, avoid it, would you happen to have logs from your console?
[Google Pixel 6] pa.pn2:
how can i provide logs?

im still in fastboot mode, slot A it says, can i boot the device?Flashing may update to slot b worked, but not to A

Or will it stuck?
[Google Pixel 6] badabing2003:
If you didn't close the console you were operating in, then the logs are still there.

If you lost them, then let me understand where you stand, you have fastboot access?

If you type

fastboot devices

What do you get?
[Google Pixel 6] pa.pn2:
Im in fastboot yes

If i type fastboot Devices i just get ?????? like in the screenshot
[Google Pixel 6] pa.pn2:
Weird, i restarted my PC, and now it detects the Device again, flashing to slot A is also working.

Have never seen that before, what could have been the problem?
[Google Pixel 6] badabing2003:
I see two entries, do you have one device connected or two?
[Google Pixel 6] badabing2003:
Don't know, but happy to learn that you're back operational.
[Google Pixel 6] pa.pn2:
yeah man, i almost got a shock hehe
[Google Pixel 6] Mepsipax:
Hey guys, I got a fresh Pixel 6 that I already updated via OTA to Android 13. I want to root, so before I start, I just want to check in quickly to summarize if I understood the steps correctly and make sure this works with a device that's already on 13.

What I need to do:

1. Download latest factory image: 13.0.0 (TQ2A.230505.002, May 2023)

2. Download Magisk canary (because stable doesn't work for 13, that still the case?) from OP link: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk

3. Perform unlock bootloader steps

4. extract device-image-buildnumber.zip from the factory image and extract boot.img from that.

5. push boot.img to device.

6. patch the boot.img on the device using the Magisk canary.

7. pull the patched boot.img back to the PC.

8. flash the patched boot.img. The whole factory image is never actually flashed, right?

Sorry, if this seems like rehashing the OP, but I just want to make sure I'm not missing anything. Thanks for your help!
[Google Pixel 6] badabing2003:
Steps are correct, if you are already on May release, then correct, no need to flash full factory, otherwise you need to as you're using May boot.img.

As for

I don't believe that is true, where did you read that?
[Google Pixel 6] Mepsipax:
The yellow writing in the OP: "Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+."

I don't know how the tell if these necessary fixes made it into stable in the meantime? Do you know something about that?
[Google Pixel 6] badabing2003:
We're at Magisk 26.x, 23 is long long ago
[Google Pixel 6] Mepsipax:
Okay, thanks. I wasn't sure how to interpret the canary version number. So I take it I'll go for the stable version, but apart from that, the steps are fine. Thx for the advice!
[Google Pixel 6] Lughnasadh:
In addition to what @badabing2003 said, also make sure both slots have the A13 bootloader on them before modifying your device. See this for more information. Wasn't clear how many updates you took since updating to A13 and if both slots indeed have the A13 bootloader on them already.
[Google Pixel 6] Mepsipax:
Okay, so I bought the device just over a week ago. It came with A12 and I took the OTA update to A13. I think I took one or two additional security OTA immediately after that, but I don't remember exactly. On top of that, I also just took another security OTA an hour ago.

So I definitely got at least 2 updates, maybe more.

From my understanding, 2 updates should be enough to update the bootloader on both slots so I should be fine, right?

I could check the bootloader version on both slots using the instructions from your link, but I would have to unlock the bootloader first, correct?
[Google Pixel 6] Lughnasadh:
If you've taken at least one OTA since updating to A13, you should be good 👍
[Google Pixel 6] V0latyle:
Re: Magisk version:

All official Magisk builds have a build number. 26.1 is 26100. Canary/debug builds are between the official releases. Refer to the Magisk releases page for the main releases.

25.2: 25200

Canary/debug: 25201 to 25999

26.0: 26000

Canary/debug: 26001 to 26099

26.1: 26100

If you have no reason to use a previous version of Magisk, just use 25.2 or 26.1; 26.0 is known to have problems.

If for whatever reason you use older Magisk releases, be aware that the fixes necessary for the Pixel 6 series were incorporated at 23016, meaning any version prior to those won't work properly.
[Google Pixel 6] Mepsipax:
Thanks for your help guys, I will do it tomorrow and report back when I bricked it :P
[Google Pixel 6] Mepsipax:
Root successful! Thanks to everyone!

Hopefully, I won't break it with the next OTA, :D.

Now, I'm off to restore all my app data from my old phone using Titanium Backup. Are people still using this nowadays?
[Google Pixel 6] pa.pn2:
Yeah I'm still using titanium for backup, but I noticed FC of many apps after restoring. Wiping the cache of apps helps..
[Google Pixel 6] Mepsipax:
FC means what? Fatal Crash or something? Because that's exactly what's happened to me... All apps that I restored with TB crashed immediately after launching them. I figured it's because my old OP5T was running A10, I think, and it might be too big of a version leap to be properly restored, so I manually installed most of my stuff now.

You saying I just need to clear my cache?
[Google Pixel 6] V0latyle:
FC = Force Close, basically the app keeps crashing

I used to use TB, I now use Swift Backup. No issues.

Clearing cache might help. I don't remember if TB restores cache by default or not.
[Google Pixel 6] pa.pn2:
Yes I just cleared the cache of the crashing apps, but I think you can also restore apps without cache, not sure.m
[Google Pixel 6] t-ryder:
I was on Dec. '21 update, updated to latest Magisk canary (23016), patched the boot.img again and tested my updated 0riole-Flasher_v2 (which does not flash with disable-verity & disable-verification flags) after a data backup and a full swift backup. No wipe, can confirm. 0riole-Flasher_v2 works and is even more convenient - no file renaming needed (see info textfile and screenshot).

https://github.com/ryder203/0riole_Flasher/releases
[Google Pixel 6] c19932:
I am confused about magisk 23016 and vbmeta. Are you saying that as long as I have 23016 installed, I don't ever have to deal with the vbmeta, verity/verification things anymore? Just straight update and flash magisk patched boot image?

I am on Nov update right now WITH 23016 installed. I am afraid that If I upgrade via the OTA method I will have a data wipe, so just wanna confirm with you guys =) TIA
[Google Pixel 6] jaggy989:
Does safety net passes on rooted pixel 6
[Google Pixel 6] V0latyle:
Disabling verity and verification is no longer required as of 23016. When the January update comes, you can update via OTA, then either download the factory zip and patch the boot image, or live boot the 23016 patched boot image you currently have, and use Direct Install in Magisk.
[Google Pixel 6] V0latyle:
This is my configuration on my Pixel 5. SafetyNet passes, GPay works.

Magisk 23016, Zygisk + DenyList enabled

All subcomponents of these apps hidden under DenyList:

Google Play Services

Google Play Store

GPay

Any banking/financial apps

Any DRM media apps

Modules:

MagiskHide Props Config 6.1.2

Universal SafetyNet Fix 2.2.0
[Google Pixel 6] t-ryder:
If you run Magisk canary in Zygisk mode and have Universal SafetyNet Fix 2.2.0 Zygisk module installed... yes.
[Google Pixel 6] jaggy989:
Okay,, but what is zygisk mode and how to get it ?

i have just unlocked the bootloader and in process to root it.

any heads up will be appreciated
[Google Pixel 6] t-ryder:
For Zygisk mode check the Magisk settings in the app.
[Google Pixel 6] jaggy989:
Thanks !! Got it working.

does regular magisk modules work in zygisk ?

I used to flash Viper and few other modules before, right now i am not sure if these work or not
[Google Pixel 6] V0latyle:
I believe most modules that worked with Magisk pre-Zygote will still work, provided they don't depend on anything else. Universal SafetyNet Fix for example used Riru, which is not compatible with Zygisk, so USNF had to be updated for Zygisk.
[Google Pixel 6] V0latyle:
Someone want to test this?

Requirement: Pixel 4a, 5, 5a, 6, 6 Pro rooted with Magisk 23016

Reboot into bootloader and reflash vbmeta without flags.

Reboot to system.

Reboot to bootloader again, re-reflash vbmeta with disable flags.

Reboot to system. If you get the Rescue Party corruption message, just reboot to bootloader and reflash vbmeta without flags.

Report results here.
[Google Pixel 6] rbouza1:
Did the bootloader change since oct ?
[Google Pixel 6] V0latyle:
Not sure, but that's irrelevant to my question here
[Google Pixel 6] rbouza1:
I apologize I just dropped in a post
[Google Pixel 6] V0latyle:
It's OK.

The best way to tell would be to download both the October and December factory zips, and compare the bootloader image build numbers.

Considering how new the P6 / Pro is, I would honestly be surprised if it hasn't been updated.

Edit: Confirmed, October bootloader is 1.0-7683913, December is 1.0-7892371.
[Google Pixel 6] rbouza1:
For whatever reason I can't boot after I flash boot the newest magisk patch. It'll boot , and then after logo it'll reboot. Phone works but no root. I used flash tool, have latest magisk for p6 previous had magisk hidden but force closing. Idk

Edit, I did uninstall hidden magisk before updating. Couldn't do anything as it wouldn't open for last few weeks. Patched with p6 magisk newest canary one .
[Google Pixel 6] jaggy989:
Safety net does not pass as I am not able to use gpay.

Do I have to enforce denylist in magisk settings?
[Google Pixel 6] Slim2none4u:
Yes! Any apps that detect root. Banking apps, google play services etc
[Google Pixel 6] V0latyle:
Yes.

I have DenyList enabled on all components of Google Play Services, Google Play Store, and GPay.

I am using Universal SafetyNet Fix 2.2.0 as well.
[Google Pixel 6] V0latyle:
Make sure your Platform Tools are up to date (latest version 31.0.3). Make sure you're using the correct boot image and the correct syntax for your commands.
[Google Pixel 6] Mepsipax:
Well, that didn't work for me. I tried xml and snapshot restore and I tried complete restore via TB and I tried installing via play store and then just restoring data via TB. In all cases, the app crashes on startup even after clearing its cache and even after clearing all its data again!

Only clean reinstall has it start again.
[Google Pixel 6] V0latyle:
Might be worth switching to Swift Backup.