yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] General_Mayhem:
Quick question: Do you know if this is the same for the 6a? My son recently got a 6a and likes to tinker with his phones as much as I do. I'm wondering if I need to send him a link to this thread/warning about flashing the bootloader to both slots.
[Google Pixel 6 Pro] Lughnasadh:
Yes, it is the same for the Pixel 6a as well.
[Google Pixel 6 Pro] zebulon17:
Hello guys,

I was rooted on android 12 and used pixel tool to upgrade to android 13. Everything was good but now i have an issue. I can't root anymore the boot img of the android 13 in magisk tool.

I have the issue below.

Someone can help me or explaine me how to root correctly this new android version? why it want to use slob B instead of slot A ?

Thanks for your help

C:\Users\Admin\Desktop\platform-tools_r33.0.0-windows\platform-tools>fastboot flash boot --slot=all magisk_patched-25200_lYRja.img

Warning: skip copying boot_a image avb footer (boot_a partition size: 67108864, boot_a image size: 100663296).

Sending 'boot_a' (98304 KB) OKAY [ 2.305s]

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

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

fastboot: error: Command failed

C:\Users\Admin\Desktop\platform-tools_r33.0.0-windows\platform-tools>fastboot flash boot magisk_patched-25200_lYRja.img

Warning: skip copying boot_b image avb footer (boot_b partition size: 67108864, boot_b image size: 100663296).

Sending 'boot_b' (98304 KB) OKAY [ 2.305s]

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

FAILED (remote: 'failed to flash partition (boot_b)')

fastboot: error: Command failed

C:\Users\Admin\Desktop\platform-tools_r33.0.0-windows\platform-tools>adb reboot bootlader

C:\Users\Admin\Desktop\platform-tools_r33.0.0-windows\platform-tools>fastboot boot magisk_patched-25200_LDJee.img

Sending 'boot.img' (98304 KB) OKAY [ 2.286s]

Booting OKAY [ 0.006s]

Finished. Total time: 2.322s
[Google Pixel 6 Pro] V0latyle:
Your Platform Tools is out of date. Current is 33.0.3.

Are you sure you're using the correct image?

Does the device successfully boot the patched image with that last command?

What version of Magisk are you using, and where did you download it from?
[Google Pixel 6 Pro] zebulon17:
Thanks for your reply.

Upgraded to 33.0.3 but i have the same issue.

I use the image from the last android 13 official rom : 13.0.0 (TP1A.220624.021, Aug 2022) and magisk apk 25.2

The last command to root from patched magisk file doesn't work :

C:\Users\Admin\Desktop\platform-tools_r33.0.3-windows\platform-tools>fastboot flash boot --slot=all magisk_patched-25200_LDJee.img

Warning: skip copying boot_a image avb footer (boot_a partition size: 67108864, boot_a image size: 100663296).

Sending 'boot_a' (98304 KB) OKAY [ 2.377s]

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

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

fastboot: error: Command failed

i have followed all steps that i usually follow to root my pixel device with magisk apk, but this time i don't understand what is going on...
[Google Pixel 6 Pro] phaino00:
The patched image should only be flashed to the active slot.
[Google Pixel 6 Pro] General_Mayhem:
Is OEM unlocking enabled in devtools?
[Google Pixel 6 Pro] Nergal di Cuthah:
This , try without --slot all
[Google Pixel 6 Pro] zebulon17:
Thanks all,

OEM is already unlocked.

with out --slot all command , i have the same issue:

C:\Users\Admin\Desktop\platform-tools_r33.0.3-windows\platform-tools>fastboot flash boot magisk_patched-25200_LDJee.img

Warning: skip copying boot_b image avb footer (boot_b partition size: 67108864, boot_b image size: 100663296).

Sending 'boot_b' (98304 KB) OKAY [ 2.306s]

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

FAILED (remote: 'failed to flash partition (boot_b)')

fastboot: error: Command failed

C:\Users\Admin\Desktop\platform-tools_r33.0.3-windows\platform-tools>

Jumped from a android 12 original rom rooted to android 13.

i have also sideloaded android 13 after applying the android 13 upgrade.
[Google Pixel 6 Pro] Lughnasadh:
Are you using the correct boot image to patch? The size seems to be off. The boot image should be around 64 MB. Looks like you may be using a boot image from a different device.
[Google Pixel 6 Pro] V0latyle:
Right, but for which device (raven, oriole, bluejay, etc) and what is the exact name of the image you are patching (boot.img, vbmeta.img, etc).

Where did you download it from? The ONLY acceptable source for Magisk APKs is the official GitHub, linked in the OP.

When you're asked specific questions, you should give specific answers. If you don't give us the information we ask for, we can't be of much help.

The image size is wrong, I think you're using the wrong image as @Lughnasadh pointed out. The size looks similar to the boot image of the 765G devices (4a 5g, 5, 5a) at 98,304KB (100,663,296 bytes). The correct boot image size for the Raven is 65,536KB (67,108,864 bytes)

Make sure you are using THIS factory package, and ONLY use the boot image from it.

The boot image you have been using is NOT from a Tensor series factory package. I don't know where you got it from, but you either took some shortcuts or ignored the instructions completely.
[Google Pixel 6 Pro] zebulon17:
Thanks for you help.

I have uninstalled magisk / installed again and dowloaded the raven android 13 firmware.

I have sucessful flashed the new boot.img patched by magisk and everything is working now.

Thanks for your support and assitance.
[Google Pixel 6 Pro] swieder711:
I'm getting ready to update my P6P from stock A12/rooted to A13. Can I update the bootloader in both slots while still on A12?
[Google Pixel 6 Pro] swieder711:
Flashed the bootloader, A13 stock software and rooted boot files to both slots. Went a smooth as butter.

Edit: I also flashed the Kiri kernel to both slots.
[Google Pixel 6 Pro] Cornloaf:
Anyone update their rooted Pixel 6 Pro with the Sept 2022 patch? I had issues with the last udpates and they are repeating with the latest update. Here are the steps I took:

Uninstalled Magisk, restore images, ran the OTA within Android, repatched, rebooted. CORRUPT.

Booted into recovery, apply OTA, CORRUPT.

Fastboot, apply full image (TP1A.220905.004, Sep 2022 removed -w from bat file), CORRUPT

Fastboot, apply full image of Android 13 (TP1A.220624.021, Aug 2022) - SUCCESS

Recovery and apply OTA (TP1A.220905.004, Sep 2022), CORRUPT.

Fastboot, apply full image of Android 13 (TP1A.220624.021, Aug 2022) - SUCCESS

Fastboot, apply full image (TP1A.220905.004, Sep 2022), CORRUPT

I am now back on Android 13, Aug 2022 and it's working fine. I have basically tried two methods of OTA and the factory image. I have tried to apply the Sept update to stock Android 13 (TP1A.220624.021, Aug 2022) and it fails.

Am I missing a new step?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yes, I updated from the August 15 Stable Android 13 release to the September firmware. I never use the OTA method, though. I use the (full) factory image zip method. You could try

Official Google Android Flash Tool

(OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own). Just make sure the following boxes are unchecked as indicated if you do that way:

Uncheck Wipe

Uncheck Force Flash All Partitions (which would also wipe)

Uncheck Re-lock Bootloader When Done.

Some or all of those options are unchecked already just depending, but I can't keep track of when they default checked and when not, so best to just make sure they're unchecked. :)

When done with the Android Flash Tool, use the boot.img from the full factory image zip as usual to create a Magisk'd boot.img. I would then:

adb reboot bootloader
fastboot boot MagiskRootedBoot.img

To live boot the Magisk'd boot.img. Once booted, use the Magisk app once more to Direct Patch the actually installed on device boot.img.

Good luck!
[Google Pixel 6 Pro] WhoIsJohnGalt1979:
This is what I use all the time for a seamless transition:

- Unhide Magisk

- Disable all magisk modules except for safetynet

- Patch the boot.img from the new image.zip with magisk and save it in platform tools folder, lets call this patchedboot.img

- adb reboot-bootloader

Check for fastboot devices detect and get-var current slot just to be sure

- fastboot flash bootloader bootloader.img

- fastboot reboot-bootloader

- fastboot flash radio radio.img

- fastboot reboot-bootloader

- fastboot --disable-verity --disable-verification --skip-reboot update image.zip

This would leave you on the fasbootd screen.

- fastboot reboot-bootloader

- fastboot boot patchedboot.img

Direct install from magisk

reboot

Re-enable Magisk modules.

You can edit the flash-all file but I prefer using the commands manually. I feel in control of each step lol.

Never once has it not worked in the last 10 months.
[Google Pixel 6 Pro] Kennyeni:
Is anyone else having issues with the September update on flashing BOTH slots?

Flash works if only was slot is flashed though (i..e, not --slot=all param sent). This definitely gave me a scare though!
[Google Pixel 6 Pro] WhoIsJohnGalt1979:
Never has been advised to flash image.zip to both slots using slot=all. Only bootloader flash through slot=all. If you want to update bootloader, radio and image on both slots, please do it one slot at time.
[Google Pixel 6 Pro] Lughnasadh:
Yeah, flashing to both slots (i.e. --slot=all) when updating the whole system doesn't work on the Pixel 6 series. It does work, however, when flashing individual images such as boot, radio & bootloader, for example.
[Google Pixel 6 Pro] Kennyeni:
Thanks both! I think that the main post in this thread has to be updated. cc @V0latyle

The instructions at:

Spoiler: Update and Root Factory Image

Suggests to flash both slots.
[Google Pixel 6 Pro] Lughnasadh:
Yeah, he does know about this. Probably just slipped his mind.
[Google Pixel 6 Pro] V0latyle:
Also been crazy busy so while I have 5 min here and there to post replies, haven't had time to edit the OP. Typing this on my phone with my cat staring at me and the shower running, less than 40 min til I have to leave for work

Edited while my breakfast cooks
[Google Pixel 6 Pro] Cornloaf:
I followed these instructions with the exception of flashing to both slots. I got an error message that there was not enough room on the partition when it got to the inactive slot. Went through the procedure again without flashing to both slots and it finally worked. Maybe something is wrong with my phone. Still can't get it to charge over 40% via wireless. Sometimes the phone will refuse to charge wired or wirelessly. This started after stable Android 13 released.
[Google Pixel 6 Pro] roirraW "edor" ehT:
fastboot --slot all flash bootloader bootloader.img

Replacing bootloader.img with the exact filename of your bootloader file (not boot.img, has bootloader in the name) should work fine. Is that what you did, or something else? Someone else had tried to flash the kernel (boot.img) to the bootloader partition and got an error too (of course). :)
[Google Pixel 6 Pro] V0latyle:
Instead of trying to perfectly type the image name, you can type the command, then after the last space, just drag and drop the image you want to flash into the command window; it'll automatically populate the file path. Since I have two different phones (redfin and barbet) I keep all the files segregated in their own folders (even though the kernel is the same)
[Google Pixel 6 Pro] roirraW "edor" ehT:
I prefer to copy-paste the filename instead. I'm more of a keyboard buff, but not nearly as much as my older brother, who is more like a keyboard hound.
[Google Pixel 6 Pro] sonice21:
Some function is lost when opening the bootloader, such as stop watching netflix in fullhd because I changed the video codec. Sorry for my bad english
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hi. Yes, "opening the bootloader" is confusing terminology. Are you running full Android 13 Stable? Or do you mean you are running Android 12 with the bootloader from Android 13 Stable flashed? If so, then that's expected behavior. If you want to use Android 12 while using a Android 13 compatible bootloader, then you should use one of the Developer Support images for Pixel, which is the only way to use stock Android 12 on an Android 13 compatible bootloader.
[Google Pixel 6 Pro] sonice21:
I'm in stable android 13, i think to open bootloader for flashing new versión more faster than OTAS
[Google Pixel 6 Pro] roirraW "edor" ehT:
Oh, I see what you mean. Unlocking the bootloader. I don't have Netflix so I have no experience with it, but have you implemented the items in the Pass Safetynet section of the OP? Also, on Android 13 a slightly different Universal SafetyNet Fix might be needed. See How To Guide Rooted, passing SafetyNet, Play Integrity, and GPay/Wallet contactless on A13 stable.

@V0latyle I don't know if you want to include links to the modded version of the SafetyNet fix as linked to from that other thread ^. Others and I found it necessary in order to pass more certification on Android 13 than the official SafetyNet Fix does. Hopefully, the official version implements the necessary fixes eventually.
[Google Pixel 6 Pro] V0latyle:
I knew there was something I was forgetting...Since I'd have to modify every single one of my 9000 guides, this may take a bit
[Google Pixel 6 Pro] TotallyAnxious:
The standard Universal SafetyNet Fix still works fine for me on A13
[Google Pixel 6 Pro] Nergal di Cuthah:
Same here i am on unmodded with no checks in deny list, and i can download and run netflix and just checked mobius streams on it. Netflix is not denied in denylist
[Google Pixel 6 Pro] Nergal di Cuthah:
Are you using Chrome if not try that, Google is notorious for not working in other browsers
[Google Pixel 6 Pro] Superxdaer:
Yes, it is Chrome (was not working as you say in Firefox). Maybe there is still ad blocking going on, I will check.

The other issue...this step where I have to edit the flash-all.bat file in the platform-tools folder. There is no such file in the latest platform tools I have for Windows. There is flash-all in the factory image zip file. What's up with that?
[Google Pixel 6 Pro] Nergal di Cuthah:
That's where flash all comes from
[Google Pixel 6 Pro] Superxdaer:
Ok thank you, just checking. On this thread:

https://xdaforums.com/t/pixel-6-pro-easy-step-by-step-unlock-root.4361847/#post-85943801

The OP says it's in the platform-tools package.
[Google Pixel 6 Pro] roirraW "edor" ehT:
It also says (near the top of the instructions):

:)
[Google Pixel 6 Pro] Superxdaer:
Doh!! Thanks backwards guy!

OK, but what about the website flash tool? I still can't get past the "select build" screen. There is no screen where you can uncheck the verity stuff like I had before.
[Google Pixel 6 Pro] Superxdaer:
Hmm....ok those instrusctions are still somewhat confusing....let me try...

you want to copy the contents of the FIRST image into the platform-tools folder if you want the flash-all to be there. Not the second. However, the second image has all the boot.img files.
[Google Pixel 6 Pro] roirraW "edor" ehT:
LOL! You're welcome. I have never actually used that method at all, so I can't help you there.

You know, at this point, you might just want to go ahead and wait until the OTA that'll come out in about 15.5 hours, otherwise you'll have to jump through some hoops again to get the latest OTA while having disabled verity and verification. You'll have to do that eventually (if you want updates) anyway, but probably not ideal to do it right away just after you (hopefully otherwise) figure out the current hoops you're jumping through.
[Google Pixel 6 Pro] Superxdaer:
ok I will take that advice.

I thought I have to do this anyway since I can't install through normal OTA process on the phone or else it will remove root. And i think that is also what you are saying....

Anyway, just got stuck on the android flash tool screen, I think everything was working. And the original root process where I used the same tool did have the options for verity. So not sure what to do.
[Google Pixel 6 Pro] Dragon Kumera:
Well the update not out yet still so guess google behind.
[Google Pixel 6 Pro] Nergal di Cuthah:
It was announced that series 6 will get its update next week
[Google Pixel 6 Pro] Dragon Kumera:
ahhh ok that makes sense. Why it so late though?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Because they're fixing a lot (and giving some benefit of the doubt that they're also testing a little).
[Google Pixel 6 Pro] galaxys:
Afraid XDA gang will be testing a lot next week 😳😉📴📱
[Google Pixel 6 Pro] Lughnasadh:
Not sure if I should laugh or be scared 😜
[Google Pixel 6 Pro] Dragon Kumera:
I do hope twrp gonna be made for p6p and lineage os?
[Google Pixel 6 Pro] V0latyle:
That's another topic; I would recommend asking in the TWRP threads.
[Google Pixel 6 Pro] Dragon Kumera:
thx! had no idea there was a topic for it. Ended up replying to the wrong thread. lol
[Google Pixel 6 Pro] essdee:
So, hypothetically... Let's say someone unwisely decided to update their Pixel 6 to the latest factory image in the same way they used to do it, by just removing the '-w' from the fastboot command in flash-all.bat, therefore allowing the phone to reboot itself prematurely and destroy any possibility of regaining root without a factory reset.

Does anyone know any way, without root, to make some kind of backup of the current data and apps that could be copied back onto the phone after a wipe to at least minimize the effort required to undo such a foolish mistake?

Or is this hypothetical person basically screwed?
[Google Pixel 6 Pro] Lughnasadh:
The need for Displax's USNF mod depends are what you are trying to do. For example, many people need that mod to use the new Google Wallet. For other things, kdragon's USNF may be sufficient.
[Google Pixel 6 Pro] Az Biker:
Since I've been out of the updating game since April (I'm super, uber busy, and even more lazy) let me confirm that prior to updating to 13, all I need to do is < fastboot --slot all flash bootloader bootloader.img > the latest 13 bootloader.img?

Then just reboot to my brand spanking new 13 bootloader and simply update to the latest 13 factory image per the usual method as the last bazillion months for the 6 PRO??? It's really that easy? No clean flash? No complete wipe? No DNA donation?

Thanks for your continued presence and support for us less motivated users :D
[Google Pixel 6 Pro] V0latyle:
Yeah...and the only reason you have to do this is because of the anti-rollback.

Yep, update works as normal; you can either update via OTA or the factory image, it doesn't matter, and a data wipe isn't necessary.
[Google Pixel 6 Pro] Az Biker:
Saweeeet!

Again, thanks for the great support and help!
[Google Pixel 6 Pro] CRXed:
So this XDA article states that you can easily go back to A12 By skipping the bootloader flashing.

Is that even a properly tested way of doing it?

How to downgrade to Android 12 from Android 13 on the Google Pixel 6 series

www.xda-developers.com
[Google Pixel 6 Pro] Nergal di Cuthah:
There's no need now that there's a 12 for the new bootloader

Edit: i reread the article and see the 12 i talk about is mentioned
[Google Pixel 6 Pro] CRXed:
You mean the the Developer one that's isn’t suitable for general use?
[Google Pixel 6 Pro] Nergal di Cuthah:
Yes though i didnot know it wasn't fit for gen use
[Google Pixel 6 Pro] digger16309:
I just ordered a Pixel 6 Pro which will come with A12. I'm thinking I should unlock the bootloader brand new (let it wipe), then take the update to A13 OTA if offered (or sideload factory image if not), and then root, etc... This makes sense?

Or, should I not take the OTA and flash Factory Image A13 to --slot all, then root?

I don't care about sticking with A12 at this point but I would like to take OTA updates without losing root.
[Google Pixel 6 Pro] V0latyle:
OTA updates by design eliminate root, unless you use Magisk's "Patch inactive slot" function.

The reason for this is the update installs a new boot image, which you have to patch for root.
[Google Pixel 6 Pro] digger16309:
I meant just take the A13 OTA update before rooting. Or should I just go straight to flashing the latest A13 factory image, and then root from there since it will come loaded with A12? Is there a difference/preference?
[Google Pixel 6 Pro] Nergal di Cuthah:
Those both sound like the same outcome. Letting it OTA i guess you'll have access to the phone while it downloads. Flashing maybe a mite faster but both will get you unrooted 13 where you'd have to root boot.img and transfer the patched file to your computer and fastboot flash it
[Google Pixel 6 Pro] Lughnasadh:
Doesn't really matter if you upgrade to A13 via OTA or flashing the factory image (However, --slot all won't work on the Pixel 6 series when flashing the whole system). What is important, is that after you do upgrade to A13, make sure you either flash the A13 bootloader to both slots or flash/install A13 to your inactive slot (e.g. via sideloading the OTA) before you do any rooting.
[Google Pixel 6 Pro] Lughnasadh:
A few people have done this but initial reports were that it was not fit to use as a daily driver due to Webview applications crashing, media DRM APEX crashing and possibly other problems.
[Google Pixel 6 Pro] digger16309:
Thanks - this was on my checklist. I have a Pixel 5 and had heard about this peripherally. I will follow the instructions on the Flash tool page before any attempt at root.
[Google Pixel 6 Pro] V0latyle:
I'd flash the factory image, because you can flash the bootloader to both slots, then update system, and flash the patched boot image in one go.

Make sure you patch the boot image before you unlock the bootloader and wipe the device :)
[Google Pixel 6 Pro] digger16309:
I don't quite follow this. In the past, I've done the opposite. Unlock the bootloader first thing on a new device. Apply latest update. Patch and flash boot image after update applied.

What's the reason for doing so before unlocking the bootloader?
[Google Pixel 6 Pro] V0latyle:
I had assumed you had already set up your device and downloaded all your apps including Magisk.

If that's not the case, and you're just going to set it up after unlocking the bootloader straight out of the box (like I did with my Pixel 5) that works too.
[Google Pixel 6 Pro] CRXed:
Exactly, that's why I find it weird that it's a recommendation in front page article...
[Google Pixel 6 Pro] tgice:
Sorry to go off-topic here a bit, but does anyone on a Pixel 6 (or 6 Pro, I suppose) have Google Wallet working for tap to pay payments with root (I'm on stock firmware, just upgraded to Android 13, but it had not been working for me the past couple of months on 12 either).

I'm on the very latest Magisk (25203), have the latest Universal SafetyNet Fix (2.3.1), have hidden Magisk and have Shamiko (I think) running blacklist for tons of apps (everything I could see that was system/OS/Google/Android) and it still doesn't work.

It *was* working for me at one point in the summer for a couple of months. Just wondering if this is a known issue or maybe I've just missed something.

One other thing to note: my Citi Mobile app has always (I think even when Wallet was (briefly) working) popped a message at opening saying:

This looks like a rooted device and certain Citi Mobile App features might not work.

I've always wondered how they're doing such robust root detection when I think I've implemented about everything I can to defeat it.
[Google Pixel 6 Pro] Lughnasadh:
You should probably refer to this thread. Much discussion about it. Also, search for USNF mod by Displax.

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/
[Google Pixel 6 Pro] V0latyle:
I also updated the OP some time ago to explain why this happens and exactly what to do to fix it.

Right here.
[Google Pixel 6 Pro] tgice:
Thanks! I'll head over there. I was in this forum trying to filter out all of the stuff not needed for Pixel 6 users, but I will tackle that thread now.