yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] roirraW "edor" ehT:
The URLs are working now.
[Google Pixel 6 Pro] Dataman100:
I'm sure this question has been asked, but I can't seem to find it anywhere, at least it's not obvious. If it has, please reply with the link.

I purchased my P6P through the Google Store at launch, but I use it on the T-mobile network. I've only ever updated it with the Global image. For this update, do I use the T-mobile one, or is that for people who purchased through T-mobile?

Thanks!
[Google Pixel 6 Pro] Nergal di Cuthah:
Either will work but tmo build likely has fixes for tmo network or tmo apps
[Google Pixel 6 Pro] Fry-kun:
<removed redundant question>
[Google Pixel 6 Pro] Nergal di Cuthah:
Probably the former and not the latter as it's for MVNOs too
[Google Pixel 6 Pro] Dataman100:
I checked the radios and they are the same for both. They haven't even been updated since the last update. My only issue is that 5G sucks on this phone. It works great on my Tmo iPhone 13PM but I get really crappy speeds on the P6P. If the radio hasn't been updated, I probably don't care what Tmo specific things might be in there. Probably just going to use the Global one unless someone says what the differences are.
[Google Pixel 6 Pro] roirraW "edor" ehT:
@Displax Universal SafetyNet Fix v2.3.1-MOD_3.0 on GitHub - I haven't followed if the changes are applicable to Stable Android as well, or if they are geared towards DP1. I'm also not sure I can find @Displax' sub/temp OP in @kdrag0n's Universal SafetyNet Fix thread.

Edit: @Displax's XDA OP here.
[Google Pixel 6 Pro] roirraW "edor" ehT:
ADB/Fastboot (SDK Platform Tools) updated to v34.0.0, as @Lughnasadh hinted we would be getting soon.

No changelog at https://developer.android.com/studio/releases/platform-tools yet - I'll update when it has.

Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip

Mac: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip

Linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
[Google Pixel 6 Pro] roirraW "edor" ehT:
SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
FYI, several users are experiencing problems when trying to flash with the new Platform-Tools v34.0.0, so possibly best to stick with 33.0.3 for now.

@Displax Universal SafetyNet Fix v2.4.0-MOD_1.0 on XDA or GitHub - besides the single fix listed in this version on GitHub, this should take care of Fox's Mmm (Magisk Module Updater) from popping up that there's a new version of USNF, since @Displax' 2.3.1-MOD_3.0 is considered older than @kdrag0n's official v2.4.0.
[Google Pixel 6 Pro] biTToe:
v34.0.0 did NOT work for me. (WIN 10)

It failed and froze mid-load with some error about not enough space or something.

THEN... adb couldn't find the device

AND... I was soft-bricked.

THEN... I went to Android Flash Tool

AND... Android Flash Tool did find the device

BUT... half-way through the process it told me a re-connect was necessary

AND... AFT no longer saw the device with the warning to NOT do anything on the phone

BUT... I did anyway and managed to get it into fastboot mode.

AND... took several attempts,

BUT... as soon as the device popped-up in AFT I clicked connect

AND... the process completed.

biTT☼e
[Google Pixel 6 Pro] biTToe:
Also, I now get a message at start-up that says:

Your device is corrupt. It can't be trusted and may not work properly.

I have to press to power button to continue.

Then I get the usual message and can push the power button to pause.

I also fail CTS profile match even with latest USNF 2.4.0

Thanks in advance

biTT☼e
[Google Pixel 6 Pro] roirraW "edor" ehT:
Regarding USNF - @Displax Universal SafetyNet Fix v2.4.0-MOD_1.0 on XDA or GitHub - besides the single fix listed in this version on GitHub, this should take care of Fox's Mmm (Magisk Module Updater) from popping up that there's a new version of USNF, since @Displax' 2.3.1-MOD_3.0 is considered older than @kdrag0n's official v2.4.0.

See @Lughnasadh's post below regarding Platform-Tools v34.0.0 issue(s).

To fix the corruption issue, you may have to factory reset, although @Lughnasadh you might have to remind me, but I think some people were able to fix corruption issues by first flashing an old kernel and then re-updating to the latest kernel, correct?
[Google Pixel 6 Pro] roirraW "edor" ehT:
@Lughnasadh I just added the edit to my post above:
[Google Pixel 6 Pro] biTToe:
Shiny

That worked!!
[Google Pixel 6 Pro] badabing2003:
Just re-flashing to both slots might fix it too.
[Google Pixel 6 Pro] roirraW "edor" ehT:
@biTToe, let us know if you fix the corruption issue via any of our recommendations, factory reset being the last resort:
[Google Pixel 6 Pro] roirraW "edor" ehT:
@Displax Universal SafetyNet Fix v2.4.0-MOD_1.1 on XDA or GitHub.
[Google Pixel 6 Pro] biTToe:
Here's a question:

Since I put the new bootloader on both partitions, what would happen if I

fastboot --set-active=other

and then just booted into that partition?

I don't know what version is on that partition (probably the latest A12)
[Google Pixel 6 Pro] roirraW "edor" ehT:
Just in general, I wouldn't recommend booting into the other partition unless the same Android firmware was flashed to both slots, not just the bootloader. To the apps, app data, and system app data, it would look like you dirty-flashed an older version of Android, which often doesn't work as expected. It might quasi-work, or even partially work, but some apps might not behave correctly.

Specific to your situation, once you upgraded to Android 13 on one slot, Android 12 will never fully work again on that phone. Several users tested this scenario when Android 13 went final. It might boot, but you'll definitely find some things will not work correctly.

The only exception to Android 12 not working after upgrading is using the Developer Support Android 12 images from Google, however, in your case it still wouldn't be the solution since again, you'd have newer app and system data on your phone than Android 12, so the OS and apps would be confused about that once you booted into it.
[Google Pixel 6 Pro] Lughnasadh:
Some people were able to flash an old boot image (phone probably won't boot but that's ok) and then flash a newer boot image to get rid of the corruption message when they got it after flashing a custom kernel. This was a while ago and Freak07 put it in his OP/FAQ. Not sure if it still holds.

The most successful way to get rid of the message is to update to a new monthly build (as I recall you did a long time ago) because the bootloader is waiting for a new OS without any dm-verity corruption errors so it can switch from eio mode to restart mode.
[Google Pixel 6 Pro] Lughnasadh:
You can't do that. You can only boot the slot on which the last firmware was flashed. For example, if your active slot is slot A and you switch slots to make slot B your active slot, you would have to first flash the firmware to slot B before it would boot. You can't just switch slots and then boot the slot you just switched to.
[Google Pixel 6 Pro] biTToe:
Fair enough.

I was on the Dec A13 firmware. I skipped the Jan update.

My inactive slot, however, is still likely on the latest A12

So...

IF i switch to the inactive slot (B in my case) then flash the Feb firmware to B, then boot to B, shoud that fix my problem?

Or will I still have the corruption issue even though I'm with the latest firmware for slot B?

Or do I just live with it until the March firmware arrives?
[Google Pixel 6 Pro] Lughnasadh:
That might fix it.
[Google Pixel 6 Pro] roirraW "edor" ehT:
It wouldn't hurt anything to try, at least. As @Lughnasadh pointed out, when I had my corruption issue maybe a year ago, I just dealt with the extra power button press until the next month's firmware came out, and then once I flashed that new firmware, the corruption issue went away.

As @Lughnasadh also said, it definitely was the solution for some people to flash an older boot.img temporarily, even if the phone won't boot with the older boot.img (I would still choose one of the Android 13 ones, could be January's or December's), then re-flash the February boot.img.

And as @badabing2003 said, re-flashing the full firmware to both slots might also fix it.
[Google Pixel 6 Pro] biTToe:
OK,

Switching to, and flashing firmware to, slot B didn't fix my corruption issue.

so I switched back to slot A and re-flashed, but still corrupted.

I re-rooted with magisk and, except for the additional step at start-up, everything else is normal.

I guess I'll wait until March

Thanks again all for the help.

I'll keep watch to see if anyone else finds a way.

bitt☼e
[Google Pixel 6 Pro] roirraW "edor" ehT:
Sorry that what you tried didn't help yet. You can still try the flash old boot.img and then re-flash the new boot.img trick.
[Google Pixel 6 Pro] biTToe:
Do you mean to say:

"fastboot flash boot boot.img" of the December image i was using (OR maybe the Dec Magisk image?)

then boot the phone normally

then

"fastboot flash boot boot.img" back to the Feb image (or perhaps Feb Magisk image)?

or should I skip rebooting normally between flashing?
[Google Pixel 6 Pro] roirraW "edor" ehT:
You don't have to even try to boot the phone. An old kernel with new firmware has the chance it wouldn't even work, and it's not necessary to boot it for the fix to take place.

I would use the total stock boot.img of both the old and new boot.img initially, and then lastly flash the Magisk'd new boot.img.

I would:

fastboot flash boot DecemberStockBoot.img
fastboot reboot bootloader
fastboot flash boot FebruaryStockBoot.img
fastboot reboot bootloader
fastboot flash boot Magisk'dFebruaryBoot.img
fastboot reboot

The reboots between each one might not be needed, but won't hurt.
[Google Pixel 6 Pro] biTToe:
No luck
[Google Pixel 6 Pro] roirraW "edor" ehT:
Too bad. Oh, well. Like you said, hopefully next month's firmware does the trick like it did for me and some others.
[Google Pixel 6 Pro] biTToe:
One of the "fixes" i saw suggested this:

adb reboot "dm-verity enforcing"

apparently with the quotes

I may try this tonight unless someone thinks it's a bad idea
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'd wait for @Lughnasadh or anyone else who's knowledgeable to chime in on that.
[Google Pixel 6 Pro] Lughnasadh:
I have heard that worked in the past for others (non-Pixels), but can't comment from personal experience.

For what it's worth, disabling verity and verification seems to prevent getting the corrupt message. This might also get rid of the corruption message. I can tell you that I've had verity and verification disabled since the Pixel 6 Pro came out and continue to do so on my Pixel 7 Pro and have never gotten the corruption message, even when I was similarly situated to others who did get it (aside from having verity and verification disabled).

This will cause you to have to reset/wipe...

fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img

To keep these flags disabled you have to disable during every monthly update.

So if adb reboot "dm-verity enforcing" doesn't work, you may want to try disabling verity and verification.
[Google Pixel 6 Pro] badabing2003:
One other thing that is easier than going the wipe route is to flash (sideload) the full OTA, I know the only one time I encountered this message, I recall resolving it via flashing OTA.

Honestly I'm not sure why that would be the case, but I'd be curious to see what prop values these hold on your phone.

(bootloader) slot-count:
(bootloader) current-slot:
(bootloader) slot-retry-count:b:
(bootloader) slot-unbootable:b:
(bootloader) slot-successful:b:
(bootloader) slot-retry-count:a:
(bootloader) slot-unbootable:a:
(bootloader) slot-successful:a:

You would see them in bootloader mode with the command

fastboot getvar all
[Google Pixel 6 Pro] biTToe:
As long as it is unlikely that adb reboot "dm-verity enforcing" won't force a wipe, I'll try that. But if you're pretty sure it will. I will hold off until March.

Thanks for the insight
[Google Pixel 6 Pro] biTToe:
I will run this tonight and post.

I have read a little about this issue and some takl about sideloading, but I am not really sure how that is done.
[Google Pixel 6 Pro] Lughnasadh:
Yeah, from my observation sideloading the full OTA doesn't always work for getting rid of the corruption message, but that person can certainly try.

(bootloader) slot-count:2
(bootloader) current-slot:b
(bootloader) slot-retry-count:b:2
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:2
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
[Google Pixel 6 Pro] Lughnasadh:
Here's a good tutorial...
[Google Pixel 6 Pro] biTToe:
here it is, and then some

(bootloader) secure:yes

(bootloader) secure-boot:pRODUCTION

(bootloader) slot-count:2

(bootloader) slot-fastboot-ok:a:yes

(bootloader) slot-fastboot-ok:b:yes

(bootloader) slot-retry-count:a:2

(bootloader) slot-retry-count:b:2

(bootloader) slot-successful:a:yes

(bootloader) slot-successful:b:yes

(bootloader) slot-suffixes:_a,_b

(bootloader) slot-unbootable:a:no

(bootloader) slot-unbootable:b:no

(bootloader) snapshot-update-status:none

hahahaha.... I like that it turned the : & P into the smiley :P
[Google Pixel 6 Pro] badabing2003:
Thanks, looks normal.

Nothing is out of place.
[Google Pixel 6 Pro] biTToe:
I appreciate the look.

THere is a lot of info there. Nothing looks out of place. No "corrupt" or "error"

I'm going to try and d/l the firmware from google again and extract the boot.img. maybe there was in issue there. I did not run a checksum
[Google Pixel 6 Pro] biTToe:
at the bottom of the fastboot mode screen it does say UART: Disabled
[Google Pixel 6 Pro] djo_5296:
i too have the corruption message (didn't see the v34 warning in time) but i'll wait for your findings as i am not confident/experienced enough to be tinkering this much with my own main driver phone.

edit: i got it to patch and boot but would like to have the corrupt message removed without wiping. at least not till the weekend
[Google Pixel 6 Pro] djo_5296:
nvm , i just flashed my magisk patched boot, then flashed the latest Kirisakura kernel (4.4.2) and the message disappeared. Restarted just now to confirm and it's not there anymore
[Google Pixel 6 Pro] roirraW "edor" ehT:
That is normal. Mine's disabled too.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Glad you got it solved easy.
[Google Pixel 6 Pro] biTToe:
Hmmm.... that begs the question: is there a stock android kernel I can patch?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Apologies, I'm not understanding the question. The stock Android kernel is in the inner zip of the full firmware zip.
[Google Pixel 6 Pro] biTToe:
Yeah, so @djo_5296 Flashed the Kirisakura kernel and "fixed" his corruption issue.

Is there a separate kernel file I might try flashing, and if so, which file is it (I don't see a kernel.img file)

android-info.txt

boot.img

dtbo.img

product.img

pvmfw.img

super_empty.img

system.img

system_ext.img

system_other.img

vbmeta.img

vbmeta_system.img

vbmeta_vendor.img

vendor.img

vendor_boot.img

vendor_dlkm.img
[Google Pixel 6 Pro] roirraW "edor" ehT:
I think I see. boot.img is the stock kernel. Specifically, flash an old kernel (boot.img), such as from January or February, then flash the Stable February boot.img.

Edit: If you were rooted, you'll want to finally flash the Magisk'd Stable February boot.img before you boot into Android.
[Google Pixel 6 Pro] biTToe:
Ahh.

I tried that and it didn't work: Flash December | reboot | Flash February | Reboot | No luck
[Google Pixel 6 Pro] biTToe:
So: Flash Dec | Flash Feb | Flash Magisk | Reboot?
[Google Pixel 6 Pro] biTToe:
this is new: "unauthorized"

C:\p6p\reco>adb devices

List of devices attached

1A041FDEE0023Q unauthorized
[Google Pixel 6 Pro] roirraW "edor" ehT:
I thought that was you (the same person), but I was too lazy to double-check. :)

Correct. You can try fastboot reboot fastboot between each flash as well, but I thought that's what you did. Not necessary to flash the Magisk'd boot.img if you don't want to be rooted - it won't be a part of the fix, I don't think, although who knows.

At this point, I would be tempted to leave it as is until next month's firmware comes out. I know it's a slight PITA when you reboot.

Just need to authorize it on the phone. If necessary, you could rescind all authorizations, and then get a fresh prompt to authorize after you plug it back in and run adb from the computer to it.
[Google Pixel 6 Pro] biTToe:
I tried it w/o reboot between also no luck

I'll just wait until MArch, but keep checking here just for fun
[Google Pixel 6 Pro] roirraW "edor" ehT:
@Displax Universal SafetyNet Fix v2.4.0-MOD_1.2 on XDA or GitHub.
[Google Pixel 6 Pro] djo_5296:
why not do it my way then re-flash the Feb update so root and custom kernel gets replaced with stock? assuming it also disappears for you after applying the custom kernel
[Google Pixel 6 Pro] biTToe:
I have never flashed another kernel. Is it as simple as

adb fastboot flash boot customKernel.img

OK I just looked at the Kirisakura page. it looks pretty simple.

I guess I am curious as the the pluses and minuses of using this (or any other ) kernel.
[Google Pixel 6 Pro] roirraW "edor" ehT:
If you didn't already have Verity and Verification disabled, you need to in order to flash a custom kernel. And disabling those will wipe your data, and there's no way around that.
[Google Pixel 6 Pro] biTToe:
I was doing that a long time ago, when we had to on this phone, but once that was "fixed" i haven't done it since.

I assume that doesn't hold-over from back in the early A12 days with this phone.

Would I have to wipe every time I i did the monthly update if I flashed a kernel?
[Google Pixel 6 Pro] roirraW "edor" ehT:
To my understanding and limited experience with disabling them - since I only disabled them for a few months on the Pixel 6 Pro before the kernels obtained the capability to not need them disabled:

If you had them disabled at one time, but you've since flashed without disabling them, re-disabling them still requires a wipe. That's the problem - you have to remember to disable them from then on each time you flash something that flashes vbmeta.img, like the factory image/flash-all.bat does, or the next time you disable them you'd have to wipe again.

You wouldn't have to wipe each month as long as you disabled them each and every time you flash anything that flashes vbmeta.img.

Note that just performing a factory reset (at least, if you return to fully stock, unrooted) would likely fix your corruption issue. It's been the assumption all along that you'd rather not wipe if you don't absolutely have to.
[Google Pixel 6 Pro] Lughnasadh:
If I'm not mistaken, you only need to disable verity and verification to flash a custom kernel on a Pixel 7 series device. While in the early days of the Pixel 6 series this was required (disabling verity alone was good enough), it is no longer required to the best of my knowledge.

EDIT: Probably a mix up in threads/device again? 😀
[Google Pixel 6 Pro] roirraW "edor" ehT:
Oh, whoops (me)! Indeed. Argh. I should probably stop replying in the Pixel 6 Pro sections. LOL! @biTToe forget all that I said - you don't need to disable Verity and Verification on the Pixel 6 Pro to flash a custom kernel. Apologies for my confusion about which device section I was posting in.
[Google Pixel 6 Pro] biTToe:
No Worries.

I greatly appreciate all the help here.

I'm just an even-Pixel guy I guess: P4, P6. probably P8...
[Google Pixel 6 Pro] roirraW "edor" ehT:
I've only had the P1 (used it for 3 1/2 years, was waiting on a 512 GB Pixel), the P6P, and P7P. I'm wondering if the P8's CPU will be ARM v9 to have the greater security features?

Arm introduces second-generation Armv9 processors, plus a ray-tracing GPU

Arm has introduced its second-generation Armv9 processors plus new GPUs, including the new Immortalis-G715, which supports ray tracing.

www.xda-developers.com

Or for the uber-technical:

Arm memory tagging extension | Android Open Source Project

source.android.com
[Google Pixel 6 Pro] biTToe:
interesting stuff.

Sadly, more "security" generally comes at the exxpense of "fun"
[Google Pixel 6 Pro] Lughnasadh:
Here's a somewhat related article about A14, ARMv9 and MTE. Hopefully the Pixel 8 will have it like most other Snapdragon 8 Gen 1 & 2 Android flagships currently do.

Android 14 may add an advanced memory protection feature to protect your device from memory safety bugs

Android 14 may add a new beta feature called "advanced memory protection" that can protect against memory safety bugs on compatible devices.

www.xda-developers.com
[Google Pixel 6 Pro] AlDollaz:
SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com

Anyone know if it's ok to upgrade with this release?
[Google Pixel 6 Pro] Lughnasadh:
Changelog doesn't mention the fastbootd issue (268872725), so it may not be ok to use the new release for flashing factory images.
[Google Pixel 6 Pro] Homeboy76:
Also, the download links are downloading SDK Platform-tools rev. 34.0.0 not

rev. 34.0.1

.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I confirm that link still only gives the v34.0.0 zip. Besides the same version number in the filename, I've checked the hash of the zip file, and it's the same as the 34.0.0 that was released on February 10th.

I have Aignes Website-Watcher set to let me know when the direct link below leads to an updated file:

https://dl.google.com/android/repository/platform-tools-latest-windows.zip

(https://dl.google.com/android/repository/platform-tools_r34.0.1-windows.zip also gives a 404 error)

Thanks for the heads-up about the possible impending release, though. Hopefully it actually fixes all the issues everyone had with using 34.0.0 once it is made available.
[Google Pixel 6 Pro] fil3s:
Google Pixel 6/6a/6 Pro | Updates

#Updates #Android SDK Platform Tools r34.0.1 has been released! Release date: March 2023 Changelog (adb): • macOS: Reverted "unstable connectivity (MacBook high speed cable)" resolution due to adb install hang. Changelog (fastboot): • Windows: Fixed "mke2fs: Illegal or malformed device name...

t.me

My mistake. I just checked the link.
[Google Pixel 6 Pro] roirraW "edor" ehT:
The download links there are still to the 34.0.0 version as well. Confirmed it's the same zip file, still today.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Oddly, even though:

Pixel Update Bulletins | Android Open Source Project

source.android.com

doesn't show the March 2023 Pixel Update Bulletin, websites have revealed that it is available here:

Android Security Bulletin—March 2023 | Android Open Source Project

source.android.com

Still no hint of the actual firmware, however.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Now Platform Tools release notes "updated" of sorts but still no updated download. Zip file still has the same hash as the original 34.0.0.

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
Ignore my previous (now deleted) post. Was from the March 2022 Pixel Update page. :D
[Google Pixel 6 Pro] roirraW "edor" ehT:
Platform-Tools v34.0.1 is up!

https://dl.google.com/android/repository/platform-tools-latest-windows.zip

https://dl.google.com/android/repository/platform-tools_r34.0.1-windows.zip
[Google Pixel 6 Pro] Nergal di Cuthah:
There's no difference between the zips in the two links, correct?
[Google Pixel 6 Pro] roirraW "edor" ehT:
That's correct, they both get you v34.0.1. When you click on the first link, it redirects to the second link.
[Google Pixel 6 Pro] rhetorician:
So does this mean Google screwed up? I went to the page directly on Tuesday night and thought I was losing it. Seems they posted was bad because all I could download was 34.0. Glad it wasn't just me.
[Google Pixel 6 Pro] Nergal di Cuthah:
Yes but now 34.0.1 was released and the links given above your post will give you the right 34.0.1