yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Lughnasadh:
Are you actually not rooted or is the app just saying you're not rooted? Sounds like it may be the same thing I'm experiencing on my Pixel 6 Pro based on the issue you opened (assuming that was you but with a different name, lol).
[Google Pixel 7 Pro] tauio111:
I am seeing the same thing on Pix7 (with the 25209 build, 10 was bugged)
[Google Pixel 7 Pro] Schroeder09:
is there any word as to why the march update hasn't come out? is there even going to be one?
[Google Pixel 7 Pro] gpvecchi:
Deleted
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're talking about the latest Magisk Canary not working with the February (latest) Stable Pixel 7 Pro firmware, correct? Just checking.

No there hasn't. It's likely there will be, yes.

All, sorry, but can we take the DP2 stuff to the Pixel 7 Pro Android 14 thread?

Thank you!
[Google Pixel 7 Pro] simplepinoi177:
because of the delay at this point, I'm actually pretty anxious & nervous to flash the March update...

If they're doing something rather drastic/impactful to it or they've found some incompatibility/bug, I'd be anxious to see how it applies and/or messes things up when it comes to root, modules, and/or root checking...😰😭😶‍🌫️

*i mean, I normally wait a couple days for bugs or whatever to be reported and/or worked out first before flashing, but this instance even more so...!
[Google Pixel 7 Pro] otonieru:
Same here. Somehow mine also showed as Nexus 6P.

I think this is due to the USNF from Displax. Because one of the first module i install back when i purchased this phone is the USNF module by Displax, and i notice right away that Google One recognising my phone as N6P.

i moved to Kdrag0n version when it's updated, but then it broken again in past weeks, showing CTS mismatch. So i move back to Displax 1.2

not sure whether wiping play services data would help or not.
[Google Pixel 7 Pro] thereason00:
Yeah I wiped Google Play Store and Google Play Services and rebooted, didn't help with the phone still reporting it's a Nexus 6P to multiple apps. It did however clear the errors for the two apps that said they were no longer compatible with my device. Not sure if that will return or not, will have to wait and see.
[Google Pixel 7 Pro] roirraW "edor" ehT:
No sweat, I just wanted to make sure. By the way, tagging users when you edit an already existing post doesn't alert the user at all, but I happened to refresh and see your edit anyway. LOL!

Thanks for the details!

I'm definitely going to wait once it shows up, too.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Ignore my previous (now deleted) post. Was from the March 2022 Pixel Update page. :D
[Google Pixel 7 Pro] pp085ster:
It seems like the March Feature Drop isn't too ambitious/extensive. Seems to add more features to other devices, not so much the PX7/7Pro.

I wonder if the update delay is associated with issues on those devices.

Source
[Google Pixel 7 Pro] Schroeder09:
i wonder if they're releasing the March update one week late (3-13) because February is a slightly shorter month or something. If that's the case they might as well not release it at all. That's halfway through the month. I'll save the hassle of updating twice and just wait until April. Screw you, Google!
[Google Pixel 7 Pro] roirraW "edor" ehT:
I have an unsubstantiated theory that the March delay is related to the Platform Tools 34.0.0 / 34.0.1 / 34.0.0 RC2 issue(s). That March is designed to flash with 34+, but that they haven't worked out the kinks it has, and who knows why the release notes page shows those two supposed newer versions, but download links remain the same 34.0.0 zip file.
[Google Pixel 7 Pro] cmh714:
Platform update is live finally!!
[Google Pixel 7 Pro] Lughnasadh:
Can anyone get access to this issue? Keeps denying me access.

fastboot

Windows: Fixed "mke2fs: Illegal or malformed device name while trying to determine filesystem size" error introduced in Platform tools 34.0.0 (issue #271039230).
[Google Pixel 7 Pro] cmh714:
same here
[Google Pixel 7 Pro] roirraW "edor" ehT:
As cmh714 said!

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 7 Pro] b0uNz:
tried to flash the latest build of AncientOS with it, did not work. Back to r33.0.3 and it worked fine
[Google Pixel 7 Pro] Aphex13:
platform-tools_r34.0.1-windows is not functioning properly. Back to 33.0.3 we go...
[Google Pixel 7 Pro] Lughnasadh:
Is it the same issue with 34.0.0 where it won't go into fastbootd?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thank you both for reporting about it!
[Google Pixel 7 Pro] Aphex13:
I didn't try the 34.0.0 version, but once the phone goes into fastbootd, the computer doesn't recognize it anymore.
[Google Pixel 7 Pro] Lughnasadh:
Sounds like the same, or very similar, issue. Thanks!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Someone reported it (added a comment about 34.0.1 to the existing 34.0.0 report).
[Google Pixel 7 Pro] Lughnasadh:
I wonder who could have done that 🤔 🙃😉
[Google Pixel 7 Pro] roirraW "edor" ehT:
I figured it was you. 🤣
[Google Pixel 7 Pro] Schroeder09:
I'm beginning to agree with @roirraW "edor" ehT . The delay is probably related to their inability to figure out platform tools issues. Unbelievable that a software company as big and rich as google can't muster this. They should start a thread here and on Github. I bet free lance developers could figure it out!!!
[Google Pixel 7 Pro] Lughnasadh:
I'm wondering if it isn't something else since they released A14 DP2 two days ago (which interestingly enough has the March security update in it). Who knows 🤷‍♂️

Also wondering if maybe what they did here in 34.0.0 is causing the fastbootd problems...

fastboot

Improved flashing: flashall will now skip reboots to userspace if it can
[Google Pixel 7 Pro] roirraW "edor" ehT:
Or at least they should start a public beta channel for the Platform Tools.

I don't know why would they release any version to the public that can't even flash the latest Stable and Beta/DP firmware available to their most recent Pixel. Especially twice in a row. It's as if someone is merely going by the book and saying "Well, it looks like it should work," but not bother actually testing it in the way that produced the issue.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Maybe they should change the package and have the release notes say:
[Google Pixel 7 Pro] amders:
that why i still dont want to update feb and march update... :D
[Google Pixel 7 Pro] Schroeder09:
the latest rev 33.xx.x platform tools works for the february update. V34 wasn't required.
[Google Pixel 7 Pro] bird333:
Questions:

1. Is it recommended to flash both slots with new firmware?

2. If you do flash both slots, when you flash the patched boot file does it patch both slots or do you have to flash the patched boot file to each slot?
[Google Pixel 7 Pro] roirraW "edor" ehT:
The simplest answer I can give is that when your phone is brand new, it might be a good idea to manually flash the other slot when you do the first update, but that's not the same as what you're asking, since one slot would still have the old firmware.

There may be people who flash updates to both slots. I don't. I do switch slots now before manually flashing each month's new update.

Flashing init_boot.img (or boot.img for that matter) only applies to the current slot you have selected.

If you will be updating both slots to the same firmware, there's no harm whether you leave one slot unrooted and the other rooted, or you can flash the patched init_boot.img, switch slots, then flash it again. Personally, I'd boot the first updated and rooted slot before flashing the patched init_boot to the second slot, but if I were doing this, actually, I'd probably leave one slot unrooted, but that's just preference.
[Google Pixel 7 Pro] bird333:
Thanks for the reply. I do have a brand new phone btw. I have unlocked the bootloader but still haven't rooted yet. Can you clarify the first part of your reply? I have been out of the game for a long time and now there are two 'slots' and no custom recovery so bear with me. :) To hopefully cut down on confusion, let call my default currently in use slot 'A' and the other 'B'. Are you saying I should switch to 'B' and flash the new March firmware and leave it stock? Then flash 'A' and root it?
[Google Pixel 7 Pro] budmannxx:
Add me to the list of users that had a problem with platform-tools 34.0.1. I got into a bootloop after running flash-all.bat. Downgraded to 33.0.3, reran the new (old) flash-all.bat, and was all good.

Using 34.0.1, the phone never even got to the fastbootd part of the process
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're welcome. Yes, this first time you're going to manually flash a new firmware, I would do exactly what you described.

Note that there are other ways of achieving the same end result, such as updating and not rooting A, first, then switching to B and updating and rooting. That is how I have it described in Post #2 - "Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers" in Step 13 where I say

OPTIONAL: If you want to flash both slots, after this first time, then after do the following

.

I don't think I want to complicate the directions even further with the switching slots twice deal at this time, however.

When future updates arrive, I would just do exactly like the directions, switch slots and flash-all.bat the "new" slot.

If for any reason you want to flash future firmware to both slots, there's no reason to switch slots before flashing the first time.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks, added your additional confirmation to the OP. Three should be pretty convincing to anyone who doubts it. :)
[Google Pixel 7 Pro] bird333:
I'm guessing I can just root 'A' and update 'B' without root also? Just curious why do you recommend updating both slots for your first update?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes, you can.

@Lughnasadh can you confirm the reason was that on a brand-new Pixel, the other slot doesn't contain a working OS?

If that's confirmed, then my reasoning would be to as quickly as possible get any working version of the OS on the alternate slot, just in case something happens with the slot it comes active on.

It's really a low priority recommendation. There isn't likely anything going to happen with Slot A before you get the firmware on Slot B. It's really just whatever you prefer.

Edit: Argh, I'm tired. At least, I'm going to use that as my excuse for not exactly answering your question correctly. I apologize. You can update both slots to the same firmware, but it's really only important that you at least immediately flash the firmware to the slot that the phone didn't come active on.
[Google Pixel 7 Pro] Lughnasadh:
Yes. However, I'm not sure flashing to both slots would help any because only one slot at a time is bootable. For example, with flashing to both slots some would think that if your active slot is A and for some reason you get in a bootloop or A became unbootable that it would revert to B and boot up if you had previously flashed to both slots. But that's probably not the case. B, in this case, probably wouldn't boot unless you first flashed the factory image to its slot because only the last slot you flashed the factory image to is bootable, while the other slot remains unbootable until you flash the factory image to it.

This is because of AVB and system_other.img being on the inactive slot, making that slot unbootable unless you flash a factory image on that inactive slot, which would then put system_other.img on the new inactive slot and make that new inactive slot unbootable without first flashing a factory image.

At least this is the way I understand how it works. Hope this makes sense, lol.

H/T to @badabing2003 for explaining this well here.
[Google Pixel 7 Pro] bird333:
So you mean even if you flash both slots, if one won't boot you can't just use adb/fastboot to switch to the other slot and boot up?
[Google Pixel 7 Pro] Lughnasadh:
Correct. It's not like a dual boot device. You would first have to flash the factory image to that other slot before it would boot up.
[Google Pixel 7 Pro] bird333:
Wow. That doesn't make a lot of sense. You may as well have just one boot slot then.
[Google Pixel 7 Pro] Lughnasadh:
This is why...

A/B (Seamless) system updates​

A/B (seamless) system updates | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] simplepinoi177:
I was quite confused about the two slots thing as well, and these 3 posts clarified it a bit for me (although, Lughnasadh & roirraW "edor" ehT has gone over a lot of it already)...

Below is the way I went about flashing both my slots successfully. I edited the flash-all.bat in the way below so it (flash-all) automatically switched slots and flashed it all again on the other slot. It also flashes the magisk patched image to both slots, but like roirraW "edor" ehT prefers, you might want to consider whether you wish for your fallback slot to be rooted or not...

*EDIT: I must add how important it was to do the "skip rebooting" or it wouldn't apply/flash the other slot right -- because it would reboot after the first flash and load into the OS and all subsequent fastboot commands & flashing couldn't be applied!

Hope this explains it in a bit of a simpler & clearer sense and helps you flash to both slots in an automated way if you wish...
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks, @Lughnasadh and @simplepinoi177! It sounds like I should do some testing, but the most opportune time for me to do so would be when already flashing an update, since right now I have the February firmware on my current slot, and January on my other, and I don't feel like jumping through an extra hoop right now.

Once we have this settled, I'll have to post the correct information in the OP unless we figure it's something that's likely to change due to Google's whim from time to time. :D
[Google Pixel 7 Pro] cmh714:
From what I read and interpreted, the A/B thingy is ONLY for OTA based updates....
[Google Pixel 7 Pro] Ghisy:
The March update is here!

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Edit: the link gives a 404 error for now (https://dl.google.com/dl/android/aosp/cheetah-tq2a.230305.008.c1-factory-cefc4e56.zip)
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks!

That's weird. Nothing from Aignes Website-Watcher to alert me yet. I probably have something misconfigured. Nothing misconfigured but it just wasn't seeing the new version of the page until I had it change the "browser" it was using to check.

Their page isn't updated for some other devices yet.

When they start working (but for now confirming I get 404 too, @Ghisy):

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

13.0.0 (TQ2A.230305.008.A3, Mar 2023, WINDTRE/Canada)	Flash	Link	da1d99156fa03162ee8216277a8ff06b626f16efbc7e8b5d12096c5a10ede1ef
13.0.0 (TQ2A.230305.008.C1, Mar 2023)	Flash	Link	cefc4e564cb920af510a44a9cdb982ba4e8af879f6796490e03128f12f92189e

Google Pixel Update - March 2023 - Google Pixel Community

https://support.google.com/profile/79501506

Android Security Bulletin—March 2023 | Android Open Source Project

source.android.com

(revised v1.1 March 8, 2023)
[Google Pixel 7 Pro] Ghisy:
Once again, Google is trolling us with the non-working links! 😅
[Google Pixel 7 Pro] boontje3:
whats different between these 2 TQ1A TQ2A?

13.0.0 (TQ1A.230205.002,

13.0.0 (TQ2A.230305.008
[Google Pixel 7 Pro] philosoraptor7:
what does .A1 and .A3 introduce and who will get them?

will they fix 5g configuration issues with windtre italy? (band N78 won't connect as it's configured on 40MHz instead of 60MHz on pixels 7)
[Google Pixel 7 Pro] Lughnasadh:
Links are working now.
[Google Pixel 7 Pro] supermansaga:
Feb 2023 update vs Mar 2023 update
[Google Pixel 7 Pro] Namelesswonder:
https://source.android.com/docs/setup/about/build-numbers#build-ids-defined

First character is the version code of the release of Android, in this case Tiramisu (T) which is Android 13.

The second character is the branch of device platform that the build is from.

D: Device specific branch, what the device launches with until the next branch merge.

P: Primary branch, designates release branch for a successive version of Android for the device.

Q: Quarterly platform release, the feature drops that happen every quarter.

The third and fourth characters further define the subbranch. It's only well defined for QPRs, with the number defining which QPR the build is from. The number was "2" for the case of Android 12L.

The date roughly corresponds to when it was branched, but is mainly used to distinguish what the security patch level for release builds. Developers builds are closer to the true time it was branched.

The next three digits relate to versions based on that dated branch, and differ when a telecom needs a larger change, for example in the radio firmware or other larger change.

The last two characters are hotfixes, which usually include small changes for telecoms that need something like their APN changed after the date branch.

In this case TQ1A.230205.002 is Android 13 QPR1 that includes security patch 2023-02-05, and TQ2A.230305.008 is Android 13 QPR2 that includes security patch 2023-03-05.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Going to add this pupply (pupply? what the heck is a pupply?) Edit: ...puppy to one of the OPs! Thanks!
[Google Pixel 7 Pro] Dr.Pepper:
lets have fun now)

happy flashing)
[Google Pixel 7 Pro] boontje3:
thanks for the good and clear explanation
[Google Pixel 7 Pro] roirraW "edor" ehT:
If you're on WINDTRE/Canada carrier, you'll get the .A3.

Any other carrier, you'll get the TQ2A.230305.008.C1 Global.
[Google Pixel 7 Pro] Schroeder09:
does anyone feel comfortable using platform tools 34.0.1 to flash this update? Should we stay with the latest V33 platform tools?
[Google Pixel 7 Pro] Lughnasadh:
Stay on 33.0.3. Pretty sure some people already confirmed same fastbootd issue with 34.0.1.
[Google Pixel 7 Pro] Schroeder09:
yeah i saw that somewhere on XDA too. I thought maybe the new update would be released in such a way where this isn't an issue. I don't know that though. that's why i asked. I'm fine using the old ones!!
[Google Pixel 7 Pro] LLStarks:
T-Mobile n25 is still missing in this build. Wonderful.
[Google Pixel 7 Pro] boontje3:
anyone recents works ?

when i swipe app to recents and then reopen app its not in recents anymore
[Google Pixel 7 Pro] roirraW "edor" ehT:
Some apps are able to keep themselves out of Recent on purpose. Is it happening to you with every app, though? I'm guessing yes, but just checking.
[Google Pixel 7 Pro] jnss98b:
This^^^

Anyway I'll report back in a bit if I get the same issue too. Currently flashing the update rn
[Google Pixel 7 Pro] boontje3:
yes it happen to all apps , even with setting (where you to wiffi setting ,...)
[Google Pixel 7 Pro] Ghisy:
Has anyone who has updated already can check if Bromite still works? It's a couple of Chromium versions old and it seems it had some problems on QPR2 beta.

Same for AOSPMods. Thanks!
[Google Pixel 7 Pro] jnss98b:
According to their github the latest stable release is compatible

Also I'm using the canary build and from what I can tell from the change logs they've been ironing out issues with QPR2 for the past month so at the very least it's quite usable if I had to guess
[Google Pixel 7 Pro] HipKat:
This is the most informative thing I've read here in a long time!!

Good stuff, man!
[Google Pixel 7 Pro] HipKat:
Seems like carrier branded updates only come out periodically, not monthly
[Google Pixel 7 Pro] Ghisy:
I'm also on the canary builds. Should be fine but I was just looking for a confirmation.
[Google Pixel 7 Pro] LLStarks:
But it's a regression that was introduced during the QPR cycle.
[Google Pixel 7 Pro] jnss98b:
Updated and used it for a while and didn't notice this issue at all. In fact all of the apps I had opened before updating are still in the recent apps screen post-update. Maybe you can try rebooting your phone or try to flash the update again? On my first boot after updating and re-enabling magisk I did experience a lot of system app crashes but they went away after a reboot
[Google Pixel 7 Pro] jnss98b:
I see. Well I just updated and it seems fine to me. Granted I only use like around 5 settings in AOSPMods
[Google Pixel 7 Pro] boontje3:
thx for checking it , its weird for me

gone try a again to flash update and see iff it works
[Google Pixel 7 Pro] Schroeder09:
So you're using lsposed and AOSP mods? What versions of each? What versions of magisk?
[Google Pixel 7 Pro] jnss98b:
Yes I'm using the full version of AOSP mods canary-228 with zygisk lsposed 1.8.6 (6712) and official magisk stable 25.2 (25200)
[Google Pixel 7 Pro] d3xt3r:
Is the custom lockscreen shortcuts feature available in the match build. Seems unavailable for me
[Google Pixel 7 Pro] jnss98b:
I don't see it either. It's prob will be part of android 14 instead
[Google Pixel 7 Pro] Dark_Eyes_:
Anyone from Canada here can check if they have A3 or C1? The WINDTRE/Canada bit is confusing me. Does it mean WINDTRE + all Canadian carriers? I don't think we have WINDTRE in Canada but I can be wrong.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I find some reference to both Windtre and Canada in some Google search results, so there's a chance:

Spoiler content hidden.
[Google Pixel 7 Pro] swieder711:
Did my usual prep for the March update and everything went fine.

Unhid Magisk

Patched init_boot

Edited Flash-all.bat by removing -w and adding -disable-verity and -disable-verification.

Ran edited Flash-all

Flashed modified init_boot

Restored AOSPmod

Hid Magisk

=profit

Just waiting for an updated kernel from Kiri
[Google Pixel 7 Pro] Lughnasadh:
Maybe this will help......or make things more confusing 🙃

Canada

Pixel 7: TQ2A.230305.008.A1

Pixel 7 Pro: TQ2A.230305.008.A3

WINDTRE (Italy)

Pixel 7: TQ2A.230305.008.A1

Pixel 7 Pro: TQ2A.230305.008.A3

Google Pixel Update - March 2023 - Google Pixel Community
[Google Pixel 7 Pro] fkofilee:
Anybody noticed app spacing the app drawer is more condensed than before? On a 5 v 5 app grid?

Normally this is more spaced out
[Google Pixel 7 Pro] Schroeder09:
good to hear. thanks for diving in and reporting back.
[Google Pixel 7 Pro] Sh0X31:
i flashed march update like february update but I get this error

Now I get error on booting up "device is corrupt.."

whats the problem? Using stock kernel and I dont disabled " -disable-verity and -disable-verification"
[Google Pixel 7 Pro] Ghisy:
That

That's usually my exact steps. I just do a Swift Backup backup on top of that, just in case.

ll just wait for Kirisakura to be updated though, I'm not in a hurry!
[Google Pixel 7 Pro] Lughnasadh:
Use Platform Tools 33.0.3. My guess is you were using either 34.0.0 or 34.0.1. The latter two have problems with fastbootd.
[Google Pixel 7 Pro] bird333:
Is the bolded part in step 3 necessary? I didn't see those steps in the instructions. Can you post the entire instruction line with those mods? TIA
[Google Pixel 7 Pro] Sh0X31:
rip so I have to wipe my phone because of buggy Platform Tools?

With 33.03 do the regual update method work?
[Google Pixel 7 Pro] Schroeder09:
that's only necessary if you want to flash a custom kernel. The first time you flash this your phone gets wiped. If every month you update and want to update the kernel or think sometime in the future you might want to use a custom kernel you will need to keep flashing this. If you forget to flash it one month, use stock kernel, and flash the next month with this modded portion of the flash_all.bat file you will wipe your phone. That's fine- if you're prepared and backed up of course.
[Google Pixel 7 Pro] Lughnasadh:
33.0.3 will work for any flashing you are doing.
[Google Pixel 7 Pro] bird333:
So if I want a custom kernel in the future I need to flash with those options? Can you post the entire command?
[Google Pixel 7 Pro] swieder711:
Required if you want to use a custom kernel