yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] V0latyle:
It's not really any different from the established method, we just need to be extra careful that we're using the right images...
[Google Pixel 6 Pro] kip256:
Tried this, the same result.

Can I reset it/root/boot/whatever without wiping my entire phone? Is that a thing?
[Google Pixel 6 Pro] V0latyle:
This is really weird. Far as I can tell you aren't doing anything wrong.

I'm not sure I know what you mean by reset it?
[Google Pixel 6 Pro] kip256:
I guess reset just the files that have to do with root? Without factory resetting my phone.

Something related to root is obviously not right.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Have you tried the latest Magisk Canary, just in case it helps?
[Google Pixel 6 Pro] Lughnasadh:
I'm wondering if when you changed the extension of the Magisk app from .apk to .zip and tried to flash it that it messed things up. That's really only supposed to be done when using a custom recovery. A clean flash to clean up all files may be in order.
[Google Pixel 6 Pro] kip256:
No, will tonight when I get home.
[Google Pixel 6 Pro] V0latyle:
You know what, you might be onto something. A signature mismatch with Magisk will prevent root.

First, wipe data for Magisk: long press on the icon, tap the i, go to Storage and Cache, clear storage.

Then, uninstall Magisk.

Reboot to bootloader and flash the factory image. Boot device.

Download and install Magisk 25.2.

Start over with a fresh boot image.

@kip256 how did you install Magisk initially? Are you using TWRP at all? If so, @Lughnasadh is probably right - a fresh start would be a good idea. Don't use TWRP, just stick to the methods in the OP of this thread.
[Google Pixel 6 Pro] kip256:
Will try that.

I installed via APK at first. Then tried the zip option when it wasn't working. No TWRP.
[Google Pixel 6 Pro] V0latyle:
Did you ever hide the Magisk app?
[Google Pixel 6 Pro] kip256:
Yes, I had it hidden on A12. Wasn't working when I updated to A13, so I reinstalled Magisk.
[Google Pixel 6 Pro] Lughnasadh:
Oh, if you dirty flashed to A13, then that's likely your problem.
[Google Pixel 6 Pro] V0latyle:
Yep. You probably have two Magisk installations. Try to find and uninstall the hidden one. That's causing the signature mismatch and the lack of root access. The boot images you patched should be fine.
[Google Pixel 6 Pro] CRXed:
Dirty flash with hidden Magisk is fine, as long as you flash the patched boot image afterwards (from A12 to A12 anyway)

But his .zip flash probably is messing things up, as you said.
[Google Pixel 6 Pro] Lughnasadh:
The point I was trying to make was that if he dirty flashed he would still have that Magisk app hidden so that would cause problems when installing a 2nd Magisk app, which he did at one point. If he had cleaned flash the hidden Magisk app would be gone so when he installed the Magisk app again it would actually be the only Magisk app installed.

But I do agree that flashing the .zip probably also contributed to his problems.
[Google Pixel 6 Pro] V0latyle:
Patched bootloader?

How exactly does one "flash" a Magisk zip outside of a custom recovery?
[Google Pixel 6 Pro] CRXed:
Patched boot.img, corrected

I'm not talking about a zip, you never have to flash a zip to get root working with Magisk.

If you already have Magisk, even if it's hidden, you just flash the patched boot image after an upgrade, and root comes back, with Magisk still hidden.

Of course this is all not working for kip, because he messed things up flashing that zip, but just saying.
[Google Pixel 6 Pro] Lughnasadh:
And he likely has 2 Magisk apps installed as well. That always messes things up.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I think that's what @V0latyle's talking about. We've all been wondering just how exactly they flashed a zip. The only way I can imagine, and until I hear otherwise, I assume it's in the Modules section of Magisk, or using a third-party flashing tool that is supposed to be able to flash zip files, but of course without root that won't work either. Or I suppose they could've tried flashing it in bootloader mode. Shrug!
[Google Pixel 6 Pro] V0latyle:
Not quite - dirty flashing the factory image is unlikely to have screwed things up.

If you have the Magisk app hidden, it changes the package name, so it's possible to install Magisk again because it defaults to the com.topjohnwu.magisk package name. This is why it's important to only update Magisk from within Magisk, especially if it's hidden.

With two installations of Magisk, the original one will be the only one that has root, and IIRC having a second installation can screw up signatures enough to the point where a data wipe might be necessary to regain root.
[Google Pixel 6 Pro] CRXed:
You're basically saying exactly what i am saying :D

In a normal situation, flashing dirty is fine.

But just flashing a zip randomly screwed things up probably.
[Google Pixel 6 Pro] V0latyle:
Except there's literally no way to do this without a custom recovery, which he wasn't using.
[Google Pixel 6 Pro] CRXed:
Maybe he used the Magisk Module tab and "install from storage" option?
[Google Pixel 6 Pro] biTToe:
I am a bit confused and could use a little clarification/help.

I upgrade via the flash-all.bat method. here is what is confusing me for A13

1) Are the bootloader and radio slot-independent, or do they need to be flashed to both slot A & B?

If I modify the flash-all.bat as indicated above it will flash the A13 image to both slots, but the bootloader and radio are only flashed to one slot?

...multiple edits b/c I am in idiot when it comes to quotes​
[Google Pixel 6 Pro] roirraW "edor" ehT:
Flashing the full update to both slots at the same time, at least on the Pixel 6, does not work.

You can flash the bootloader to both slots at the same time, and sure, you can flash the radio to both slots at the same time, although there's no reason to do the radio to both unless you also manually switch slots and flash the full update, but in that case, you can manually switch slots to begin with and just do the flash-all.bat to the second slot as well.

Recommendation: just do the bootloader to both slots, and stick with your fully flashed Android 13 on the slot you're already on.

You want:

fastboot flash bootloader --slot=all <bootloader image name>

And that's all you need to be "safe".

Hope this helps.
[Google Pixel 6 Pro] V0latyle:
I don't think that would do anything...trying to install Magisk as a module in Magisk...

Proved myself wrong. If you change the APK to .zip and install it as a module, it patches the boot image. Didn't break root for me though.
[Google Pixel 6 Pro] kip256:
Flash via EX Kernal Manager.

Probably the wrong way to do it, but I had to try something.

Was not able to do anything with my phone this evening. Very pregnant and sick wife had priorities, will attempt stuff tomorrow after work. Thank you all for your suggestions.
[Google Pixel 6 Pro] V0latyle:
Congratulations on the family addition! My wife and I have been trying for a couple years now.
[Google Pixel 6 Pro] kip256:
We had also been trying for a few years. Trip to a Dr changed all that.
[Google Pixel 6 Pro] jcp2:
You don't mind that the Dr. is the father? Very enlightened of you. I'm not that secure. ;). JK.
[Google Pixel 6 Pro] crisco654:
Just to make sure I have everything before I go to Android 13(Currently in the July update for 12). I usually do the Update & Root Factory Image method.

Reboot to bootloader

fastboot flash bootloader --slot=all <bootloader image>

fastboot flash radio <drag and drop radio.img here>

fastboot update --skip-reboot image-codename-buildnumber.zip

fastboot boot <patched boot image> (I will patch the image before I update)

Finally, direct magic install.

My usual steps. The only thing that's different is I should be flashing the bootloader to both slots, correct? And should I flash image zip to each slot as well? But other than that, is everything good to go for me to go to android 13?
[Google Pixel 6 Pro] CRXed:
Looks good, but I would do it differently to avoid Boot loops:

......

fastboot update --skip-reboot image-codename-buildnumber.zip

Reboot into system, let it settle. You have lost root at this point but you have a working system

Reboot to bootloader

fastboot flash boot <patched boot image>
[Google Pixel 6 Pro] WhoIsJohnGalt1979:
Only suggestion is please reboot to bootloader after flashing bootloader and modem each. So after slot all bootloader flash fastboot reboot bootloader and after modem flash fastboot reboot bootloader.
[Google Pixel 6 Pro] crisco654:
Thanks! And one more thing. Got a question, should I flash the radio to both slots as well?
[Google Pixel 6 Pro] CRXed:
Only really needed if you plan on flashing an entire build of A13 tot that slot
[Google Pixel 6 Pro] crisco654:
Ah gotcha. So

Ah I gotcha. So if I have for some reason I have to install Android 13 on that second slot as well, I should flash the radio before hand. Thanks for the help
[Google Pixel 6 Pro] Crumpylad:
If I am on stock android 13, never rooted, is the PSA on Android 13 something to worry about? Or is that just for users who have updated a rooted phone?

Thanks
[Google Pixel 6 Pro] V0latyle:
This affects ALL users, regardless of whether or not you're rooted.
[Google Pixel 6 Pro] Crumpylad:
Ok thanks for the clarification, so as I updated OTA to A13, I should flash the update manually to both slots?

Sorry if stupid questions, been out of the rooting scene for a while, a lots changed
[Google Pixel 6 Pro] V0latyle:
Since you aren't rooted, you'll have to sideload the OTA.
[Google Pixel 6 Pro] Crumpylad:
Ok thanks for the help 🙂
[Google Pixel 6 Pro] CRXed:
or just wait for the next OTA and don't do any flashing in the meantime.
[Google Pixel 6 Pro] V0latyle:
Sometimes phones fail to boot for any reason under the sun. Doing nothing is risky. Sideload the OTA anyway; it costs you nothing and will prevent your phone from becoming a brick.
[Google Pixel 6 Pro] crisco654:
Worked like a charm!
[Google Pixel 6 Pro] koobie777:
So I'm getting a new insurance claim from at&t. Last time I checked I need to boot the phone without sim first to have oem unlock available. Once I do that is is permanent or should I flash another firmware or will I have to leave the sim out every time I do a factory reset. Any help would be appreciated not sure if it's been answered yet either.
[Google Pixel 6 Pro] V0latyle:
I'd start without the SIM. Connect to the Internet via WiFi. Once you've unlocked the bootloader, it won't change until you relock it.
[Google Pixel 6 Pro] mcwups1:
I'm curious here, because I've never done this. I see you have "--skip-reboot" here, then "--slot=all". Can I replace, and does this automatically flash the Magisk patched image if I put this here, or do I have to do that later?
[Google Pixel 6 Pro] koobie777:
Awesome so safe to flash and reflash and reset. Changing bootloaders won't be an issue? I'm seeing a lot of reports of 13 bl being buggy on 12 roms. Still new into getting into pixel devices after years of oneplus and Samsung. Having a cracked screen is giving me the opportunity to get into it while still in the lease lol. Thanks for the info.
[Google Pixel 6 Pro] Nergal di Cuthah:
Yes if you've gone 13 you're stuck with 13
[Google Pixel 6 Pro] V0latyle:
This updates /system, and --skip-reboot prevents the device from automatically rebooting so that you can flash the patched boot image.

I'm not sure what you're asking. If you intend to update, simply follow the instructions in the OP but make sure you flash the bootloader to both slots. If on the other hand you don't intend on updating to Android 13, then don't update anything.
[Google Pixel 6 Pro] dilligaf56:
Anyone else noticed that battery life seems to have taken a hit on A13? I used to be able to get through a whole day of average use without recharging my P6Pro; now it's down to the mid-30s % by around 5 or 6 PM.
[Google Pixel 6 Pro] Nergal di Cuthah:
Not particularly, but a lot of AI settings on mine got defaulted, maybe something's defsult got switched on that you had off.
[Google Pixel 6 Pro] ginfest:
Went from rooted 12 to rooted 13.

Used the android flash tool on the developers page, downloaded full image and patched the Boot.img flashed it to both slots, no issues, 13 up and running.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Most users who have had battery problems found that it was one or more particular apps that are causing the drain under Android 13. The apps need to be updated for Android 13. One of the culprits was a Samsung fitness app.

I haven't had any issues.
[Google Pixel 6 Pro] crypticc:
Hi there

I had an issue flashing using the "PixelFlasher"

https://xdaforums.com/t/pixelflasher-for-google-pixel-6-pro-support-thread.4419561/post-87359767

I still had and still have fastboot so to recover reverted back to the flash_all method with -w removed and -slot=all added

But attempting that fails... I am getting error with not enough space when that script gets to step to flash vendor partition as follows.

Any ideas? if so please can you help.

Thank you

Chris

Resizing 'system_a' OKAY [ 0.008s]
Sending sparse 'system_a' 1/4 (262116 KB) OKAY [ 6.455s]
Writing 'system_a' OKAY [ 0.739s]
Sending sparse 'system_a' 2/4 (262116 KB) OKAY [ 6.249s]
Writing 'system_a' OKAY [ 0.695s]
Sending sparse 'system_a' 3/4 (262140 KB) OKAY [ 6.191s]
Writing 'system_a' OKAY [ 0.718s]
Sending sparse 'system_a' 4/4 (62708 KB) OKAY [ 1.505s]
Writing 'system_a' OKAY [ 0.214s]
archive does not contain 'system.sig'
Resizing 'system_b' OKAY [ 0.003s]
Sending sparse 'system_b' 1/4 (262116 KB) OKAY [ 6.209s]
Writing 'system_b' OKAY [ 0.734s]
Sending sparse 'system_b' 2/4 (262116 KB) OKAY [ 6.246s]
Writing 'system_b' OKAY [ 0.656s]
Sending sparse 'system_b' 3/4 (262140 KB) OKAY [ 6.172s]
Writing 'system_b' OKAY [ 0.705s]
Sending sparse 'system_b' 4/4 (62708 KB) OKAY [ 1.497s]
Writing 'system_b' OKAY [ 0.209s]
archive does not contain 'system_dlkm.img'
extracting system_ext.img (345 MB) to disk... took 1.413s
archive does not contain 'system_ext.sig'
Resizing 'system_ext_a' OKAY [ 0.006s]
Sending sparse 'system_ext_a' 1/2 (262136 KB) OKAY [ 6.260s]
Writing 'system_ext_a' OKAY [ 0.729s]
Sending sparse 'system_ext_a' 2/2 (90588 KB) OKAY [ 2.146s]
Writing 'system_ext_a' OKAY [ 0.312s]
archive does not contain 'system_ext.sig'
Resizing 'system_ext_b' OKAY [ 0.006s]
Sending sparse 'system_ext_b' 1/2 (262136 KB) OKAY [ 6.199s]
Writing 'system_ext_b' OKAY [ 0.725s]
Sending sparse 'system_ext_b' 2/2 (90588 KB) OKAY [ 2.157s]
Writing 'system_ext_b' OKAY [ 0.271s]
extracting vendor.img (490 MB) to disk... took 1.985s
archive does not contain 'vendor.sig'
R[B]esizing 'vendor_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed[/B]

Referring to another thread I've tried removing and recreating the logical partitions for system, system_ext, product and vendor and then recreate and reflash each partition manually, but still when I flash vendor I get the same error.

[B]fastboot flash vendor_b vendor.img
Resizing 'vendor_b' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed[/B]
[Google Pixel 6 Pro] roirraW "edor" ehT:
Howdy. I suggest trying

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). It's solved weird issues for many users including myself when even the factory image wouldn't solve the problem.

Otherwise, are you using the latest SDK Platform Tools? Latest Google USB Driver (install when in bootloader mode)?

You shouldn't try to remove and recreate partitions manually. That's very dangerous. Your issue seems a little familiar - I think another user in the last two weeks had the same or similar issue, but there have been so many posts since Android 13 Stable came out, that I don't recall who it was or the details, or which thread it was in (probably one of the How To Guide threads).

Good luck! Let us know how things go.
[Google Pixel 6 Pro] crypticc:
Hey

So following breadcrumb trail I did find this> Something about --slot=all breaking things.

I suspect this is the bit you're referring to.

https://xdaforums.com/t/android-fla...ader-central-repository.4352027/post-87309913

Odd when I tried both google search earlier here it didn't come up but trying separately now. Wish me luck

EDIT - > yes, confirmed. Subsequent run without --slot=all seems to have got past the flashing without error.

everyone do

NOT

use --slot=all command on Pixel6 Pro when flashing the full factory image using either modified "flash_all", or "fastboot --skip-reboot update <image.zip>" . It breaks things.

I took grab of my partition sizes first time around so will post comparison here shortly.

Partition sizes before (when not working) and after (working after flashing slot B and then Slot A separately)

Spoiler content hidden.
[Google Pixel 6 Pro] roirraW "edor" ehT:
slot=all only doesn't work to flash the full update. fastboot flash bootloader --slot all bootloader-raven-slider-1.2-8739948.img (or the correct bootloader file for your device) works fine. I haven't seen anyone report problems with that - only problems when they try --slot all with the update.zip.

Maybe you meant that since that's what the post you refer to says, but I just wanted to clarify for anyone reading this.
[Google Pixel 6 Pro] crypticc:
yes. that's correct - thanks for pointing out

clarification added
[Google Pixel 6 Pro] V0latyle:
Yes - on the Tensor devices, for some reason you can't update both slots at once. You can flash individual partitions, such as /bootloader, /radio, /boot, /vbmeta, etc...but the system update only works on one slot at a time for some odd reason

This isn't the case on any other Pixels to my knowledge, just the 6, 6 Pro, and 6a
[Google Pixel 6 Pro] Lughnasadh:
👍 (with caveats). Wonder how well they run 🤔

https://twitter.com/i/web/status/1564360254216962054
[Google Pixel 6 Pro] proac:
In addition, I also did this. At the beginning of fastboot, I added three lines of commands to update in another slot and boot to this slot, similar to the effect of ota:

fastboot set_active other

fastboot reboot bootloader

ping -n 5 127.0.0.1 >nul
[Google Pixel 6 Pro] proac:
I have repeatedly tested with pixel 2xl without any problems. Update from A Slot to B Slot and start at B Slot, or vice versa. Full code:

PATH=%PATH%;"%SYSTEMROOT%\System32"

fastboot set_active other

fastboot reboot bootloader

ping -n 5 127.0.0.1 >nul

fastboot flash bootloader bootloader-taimen-tmz30m.img

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot flash radio radio-taimen-g8998-00034-2006052136.img

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot update image-taimen-rp1a.201005.004.zip
[Google Pixel 6 Pro] dilligaf56:
I use a Samsung pedometer. Could be that's it. However, I'm on the latest version - perhaps waiting on their devs to update it for 13.

Thanks!
[Google Pixel 6 Pro] crypticc:
Hi

would someone kindly run "fastboot getvar all" and pop the partition sizes for both A and B slots here, or PM

The request is because I could see in my before and after comparison the incorrect flash attempted to resize both A and B slots for system, system_ext, product and vendor, and then runs out of space when it gets to vendor. This is like the issue in the other thread that I linked https://xdaforums.com/t/android-fla...ader-central-repository.4352027/post-87309913.

And then when done separately, when fastbootd gets to those partitions it only resized and flashed the active partition A, which is to be expected.

But then if I switch slots and flash the other slot, B for example so both have same android version, the situation is reversed with a being sizes as per B above for those partitions, and 0 size on the previous slot A.

is this normal? I thought A and B alternated for being active but otherwise full size installation in each.

My phone boots from whichever slot I make active and then flash but I want to check I'm not shoring up an issue until next OTA.

Thanks,

Chris

.
[Google Pixel 6 Pro] V0latyle:
The battery life on my P5 has been absolute canine excrement since the update. Android System Intelligence has been using the most.
[Google Pixel 6 Pro] almahix:
I'm getting really apprehensive about installing 13. I am not an expert in any of this stuff. I can barely adb sideload the ota file and use magisk for root. Isn't there a simpler way to update without all these worries?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Official Google Android Flash Tool

If you're still on Android 12, then the online flash tool will offer to flash the bootloader to both slots. Actual Android 13 in full will only be flashed to your active slot, but that's okay.

Then use Magisk on the boot.img from the Android 13 factory image, then flash it.
[Google Pixel 6 Pro] crypticc:
Odd, I've had excellent battery. The afternoon after the crap above I unplugged after finally getting FW sorted at 19:00.

I used passively, browsing, wordle, etc, on 25% and resting about 75%% until 20:30, left standby 22:00 used fully awake until 23:30. Realised tablet dead so left phone turned on and unplugged until wake-up 07:30. Then in morning commute Inc heavy browsing, breakfast for 1 and bit hours. Then work with phone mostly asleep except lunch ,20mins fully awake and browsing. Then commute home 18:30 and when I got home 19:00 phone still had 55%. That's an easy 1.5 day and maybe 2 day phone there.
[Google Pixel 6 Pro] BostonDan:
I have gotten burned in the past with re-flashing magisk. To get around this, I typically will install the unrooted update, then pull the boot from the pixel 6 pro image, patch it through magisk, and then reboot to fastboot. Then I will fastboot boot magisk_patched_boot.img (that was created by magisk). This way, if my pixel boots, I check if magisk shows root and that magisk is available.

If this is the case, I feel more confident to patch the current slot which will do the patching of the boot image.

It's a few more steps, but I haven't had an issue with re-installing root with each update.

Hope this helps someone else.

Cheers,

B.D.
[Google Pixel 6 Pro] General_Mayhem:
It took me a while to get comfortable with it myself and to figure it out, but this is what I've been doing with every update since July for my P6P (including upgrading to 13):

1. Uninstall Magisk with restore (can leave modules)

2. Hook phone to PC & switch to file transfer

3. Open cmd prompt

4. adb reboot fastboot

5. Navigate to and select recovery

6. Select apply update from adb > click power button to select

7. adb sideload ota raven-ota-<whatever>.zip

8. Reboot phone, allow setup to finish

9. Extract full zip

10. Extract boot.img from the other zip within the folder

11. Copy boot.img to the phone

12. Reinstall Magisk

13. Patch boot.img

14. Disconnect/reconnect phone from/to computer and select File Transfer again

15. Copy patched boot img back to computer

16. adb reboot fastboot

17. fastboot flash boot --slot=all magisk_patched-<whatever>.img

18. Reboot phone

Edit: In case it's not obvious, you download both the full image (since that's where you get boot.img) and the OTA.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hello! In general, your method looks fine to me just on a quick inspection - however, the main problem with Android 13 is when the bootloader (not boot) isn't installed to both slots. Until the Android 13 Stable bootloader is flashed to both slots, there is a chance that you could wind up with a fully bricked phone that can only be repaired by sending it in to Google.

The very first thing anyone (who is concerned) should do when manually updating on any Pixel 6 is:

adb reboot bootloader
fastboot --slot all flash bootloader bootloader.img

After that, all update processes can be done absolutely just like any other month - no matter what method you use.
[Google Pixel 6 Pro] General_Mayhem:
Interesting. I wasn't aware of this. THANK YOU for pointing that out.
[Google Pixel 6 Pro] roirraW "edor" ehT:
You bet, you're welcome!