yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] roirraW "edor" ehT:
XDA Article: Android 12L brings Google’s Monet theming engine to AOSP
[Google Pixel 6 Pro] roirraW "edor" ehT:
XDA Article: Google’s Archived APK format is a new way to free up storage on Android
[Google Pixel 6 Pro] roirraW "edor" ehT:
XDA Article: Custom AOSP GSI brings Android 12L to any Project Treble-enabled device
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thanks for the news, @LLStarks.

And an XDA Article: Google starts beta testing Pixel Feature Drops with Android 12 QPR3 Beta 1
[Google Pixel 6 Pro] DanielF50:
Unsure if you can sideload OTA's with recovery, but pulled the OTA (180mb) url from logcat for anyone interested/reference:

03-09 22:13:01.064 968 968 I update_engine: initial url: https://ota.googlezip.net/packages/ota-api/package/9484825d376ff2c14dba0d4d3baabd53969ad4c3.zip

and a direct link to full factory image (2.27gb), also for reference:

https://dl.google.com/developers/android/sc/images/factory/raven-s3b1.220218.004-factory-11526368.zip

From here: https://developer.android.com/about/versions/12/download
[Google Pixel 6 Pro] roirraW "edor" ehT:
The article Google starts beta testing Pixel Feature Drops with Android 12 QPR3 Beta 1 has the links to all the OTAs and full factory images, although I'm not sure if the article originally had them from the beginning.
[Google Pixel 6 Pro] DanielF50:
Ah, I didn't see the links there when I looked. The OTA link I captured is 180mb instead of the full OTA @ 1.9gb, so might be helpful to some if you can flash via recovery, lol.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Magisk v24.3 Stable released

​
[Google Pixel 6 Pro] roirraW "edor" ehT:
https://twitter.com/i/web/status/1502026971957530639
[Google Pixel 6 Pro] znel52:
How do we update the magisk app these days? Are there any special precautions I need to take or is it straightforward just hit update through the app?
[Google Pixel 6 Pro] Nergal di Cuthah:
At least with the last few versions i just update from the app, then do a direct install to root and reboot
[Google Pixel 6 Pro] roirraW "edor" ehT:
https://twitter.com/i/web/status/1504295198200803328
[Google Pixel 6 Pro] roirraW "edor" ehT:
SDK Platform Tools updated to v33.0.1 (March 2022):
[Google Pixel 6 Pro] roirraW "edor" ehT:
IMPORTANT for this March update (12.1.0 Stable): The latest Magisk Stable is what's recommended to avoid problems that others have experienced with Magisk Canary. Get it here.

Pixel 6 Pro Factory Images are updated:

12.1.0 (SP2A.220305.013.A3, Mar 2022)	Flash	Link	87b3bf0aab411afd17220eeb06c83492613b011cb02dcbabdf4fb18df7e2d630

Don't forget:

SDK Platform Tools updated to v33.0.1 (March 2022):
[Google Pixel 6 Pro] Lughnasadh:
If you or anyone else updates, could you please post the kernel version number that comes with this build? Hoping it's 5.10.102+ because that would mean the dirty pipe fix is included in this build (unless for some reason they incorporated the fix by another means in a lower version kernel). Thanks!
[Google Pixel 6 Pro] roirraW "edor" ehT:
Answer here, if anyone else wonders:
[Google Pixel 6 Pro] DanielF50:
edit: please ignore - I am, in fact, an idiot.

Was comparing radio from Beta 3 with March... QPR3 B1 radio is the same as stable March release.

version-baseband:g5123b-97927-220225-B-8226700

I do wonder if Snapchat Night Sight is coming back though, disappeared from QPR3 a few days ago and hasn't re-appeared on release of March update.
[Google Pixel 6 Pro] jcp2:
I downloaded the March Factory zip and transferred the boot.img to my phone and then patched it with Magisk Stable v24.3 (I transferred the patched boot.img back to the Platform TooIs v33.0.1 Folder on PC) I tried to fastboot flash the March OTA (would only get to 48% and fail) So I used the Android Flash Tool and let it install the factory image without wiping. ***** Make sure you uncheck these boxes: Wipe Device, Lock Bootloader and Force flash all partitions. I am now on March build with no data loss :) I then fastboot flashed the patched boot.img and have root :) :) :)

I had the same problem with Feb v2 OTA sideload (because I had a custom kernel) anyway, I think the Android Flash Tool will be my go to for future updates :)

***** Update..... I turned my phone back on after shutting it off a few hours and it lost root.!!!! So instead of using the CMD fastboot boot "name of patched boot.img", (Remove quotation marks) I used the CMD fastboot flash boot "patchedboot.img" --slot all Now root is kept after rebooting :) :)
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yep, a custom kernel or any rooted kernel including stock could prevent an OTA from working.
[Google Pixel 6 Pro] jcp2:
Good to know. Android Flash Tool for System upgrades from now on :) Followed by Platform Tools for fastboot flashing the Magisk Patched boot.img's :)
[Google Pixel 6 Pro] roirraW "edor" ehT:
Google Pixel Update - March 2022 - Google Pixel Community
[Google Pixel 6 Pro] minhgi:
Just log in and want to said thank you. I followed you guide and it was smooth sailing from rooted FEB build with custom kernel and all the verified securities enable. I disable all Magisk modules and unhide it and then reboot before start using the Android Tool without data wipe or disabling the security.

I usually run into some kind up issue with every update except for this March build. =)
[Google Pixel 6 Pro] jcp2:
***** Update..... I turned my phone back on after shutting it off a few hours and it lost root.!!!!

So instead of using the CMD fastboot boot "patchedboot.img", I used the CMD fastboot flash boot "patchedboot.img" --slot all. Now root is kept after rebooting :) :)
[Google Pixel 6 Pro] Lughnasadh:
Yeah, fastboot boot is only temporary until the next reboot. Fastboot flash is "permanent".
[Google Pixel 6 Pro] jcp2:
Thanks for the response. I wanted to share my experience (in case it can help someone else out) because it was written in one of the rooting guides here to use the CMD fastboot boot "masterroot.img", which I had done. When I discovered that I lost root after rebooting, I followed the guide from my older 3xl A12 wich used the correct CMD. fastboot flash boot "patchedboot.img" --slot all I have now put the proper CND in a txt file in Platform Tools Folder. For future reference. :)
[Google Pixel 6 Pro] roirraW "edor" ehT:
Fastboot boot is usually used to either test a rooted boot.img to make sure it works right and/or to "live" patch the permanently flashed kernel instead of flashing the rooted boot.img that you had temporarily booted. Just a heads up there is useful purpose for doing so, and it wouldn't necessarily be an incorrect part of rooting or updating instructions.
[Google Pixel 6 Pro] jcp2:
Thanks for the clarification :) Learning new things every day.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Three new XDA Articles about Google Photos today:

Google Photos | XDA

The latest and exclusive Google Photos coverage from XDA.

www.xda-developers.com

Separately:

Google Photos will soon make it easier to manage and edit screenshots

Google Photos is getting a new screenshots shortcut and contextual suggestions to help users manage and edit screenshots. Read on to learn more.

www.xda-developers.com

The Sharing tab in Google Photos is also getting a minor design refresh

Along with the Library tab, Google is also giving the Sharing tab in Google Photos a minor design refresh. Read on to learn more.

www.xda-developers.com

Google Photos' Library tab is getting a UI overhaul & a new import photos option

Google is giving the Library tab in the Google Photos app a UI overhaul. The new changes will roll out to users over the next few weeks.

www.xda-developers.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
Sorry for the Off Topic, but wow.

The 9 year old Google Nexus 7 2013 can now run Android 12L unofficially

An unofficial port of LineageOS 19.1 based on Android 12L is now available for the Google Nexus 7 2013 tablet. Give it a go!

www.xda-developers.com
[Google Pixel 6 Pro] Sine.:
All that is missing now is the same for the venerable HP Touchpad!

Almost no chance for it to happen but let me dream a little bit ^^
[Google Pixel 6 Pro] Nergal di Cuthah:
Mines still running lol can't browse the web or do much but it works
[Google Pixel 6 Pro] DanielF50:
Seen a few posts over 3-4 threads saying people can't get Magisk to boot on March, is this just Canary (again)?

If not, I'm unsure as to where people are going wrong updating from Feb to March & being unable to boot when installing Magisk... I just used "flash-all.bat" to downgrade from QPR3 B1 to March stable - all is up and running perfectly with no data loss & Magisk 24.3 (24300), running fine so far but will update this post if I notice anything out of the ordinary.

Before flashing, I disabled all Magisk modules & patched the March boot.img with Magisk Manager, then copied that to my PC. After the factory image had finished installing, I rebooted to the OS to allow the update to completely finalise, rebooted into the bootloader again & ran "fastboot boot <magisk_patched.img>" from command prompt, then once booted with temporary root, just direct installed Magisk through the Magisk Manager.
[Google Pixel 6 Pro] roirraW "edor" ehT:
It's definitely mostly folks using Magisk Canary. Magisk Stable is fine. I've seen one person report the exact opposite, but many report that going from Canary back to Stable fixed the issue.

You already addressed this, but I kept typing (LOL): The other most common issue is incompatible Magisk Modules. Either disable all Magisk modules before updating or if you get a bootloop, use Safe Mode to disable all Magisk Modules. Always wait until there's an update for the most "invasive" (modding) Magisk Modules before using them on a brand new firmware, or wait until others report it working on the same version of firmware.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I just now updated via my usual method.

I was already on Magisk Stable v24.3 (app "hidden" / renamed)

Used the full firmware zip, extracted to the same folder as the latest Platform Tools (S:\platform-tools)

Extracted the new boot.img

Copied new boot.img to the phone

Patched the new boot.img with Magisk Stable 24.3

Renamed Magisk'd boot.img so I know what version of firmware it's for

Copied the Magisk'd boot.img back to the computer

Disabled all my Magisk Modules

Removed the "-w " from the flash-all.bat

Re-edited the flash-all.bat to verify I saved it with the "-w " taken out

Open a Command Prompt, navigated to S:\platform-tools

adb reboot bootloader

flash-all.bat

Let phone boot, unlock it, check that it's working, allow the update process to finish (gave it five minutes or so)

adb reboot bootloader

fastboot flash boot kernel.img (renamed Magisk'd boot.img)

fastboot reboot

Unlock, check everything's working

Re-enabled the most basic Magisk Modules which I was sure wouldn't cause a critical issue

Reboot, unlock, made sure everything's working

Back to modding!
[Google Pixel 6 Pro] lebigmac:
Hi are you sure about that? When disabling dm-verity and verification using the avbctl binary that's available in my SystemRW / SuperRW featuring MakeRW release (see link in my signature - also available in TWRP recovery)

it doesn't require neither a factory reset nor does it cause any noticeable corruption on my Xiaomi Poco device :unsure:

If you're a first time user the avbctl binary will ask you to reboot your device. That's all!

BTW that's the same avbctl binary that was stolen from my release the other day and re-released by a fellow forum member without permission... :cautious:

It's a very popular and useful binary for sure :ROFLMAO:

To check dm-verity and verification :

avbctl get-verity
avbctl get-verification

To disable dm-verity and verification:

avbctl --force disable-verity
avbctl --force disable-verification

To enable dm-verity and verification:

avbctl enable-verity
avbctl enable-verification

Have fun messing around with your dm-verity and verification! :LOL:(y)
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hi @lebigmac,

When I wrote that five months ago, yes, it was definitely the case on the Pixel 6 and Pixel 6 Pro, even when other phones such as older Pixels didn't even require disabling them to use the Magisk that was available at the time and/or a custom kernel if I remember correctly.

Things may have changed sometime in the last couple of months - although I wouldn't bet on it. Google has mentioned at least once or twice fixing the "corruption" problem that's happened, and I don't know if that's the corruption problem when we first disabled Verity and Verification, or only corruption problems we've had crop up under different circumstances, or both/all.

Also, disabling Verity and Verification is rarely if ever required for users of the Pixel 6 Pro anymore. There are definitely a few outlier cases of already having them disabled seeming to help some situations, but I haven't had any reason to have them disabled for a few months now, so I'm not likely to re-find out if it still causes corruption which requires wiping to solve, especially since there were details at the time such as that if you ever had disabled them, as I had long ago (and therefore wiped after), that re-disabling them didn't require re-wiping them, after having them enabled in between - and flashing the factory image by default enables them.
[Google Pixel 6 Pro] jac0b:
From what I have read these can be enabled and Magisk will still work for rooting. My question is. On previous updates that I manually flashed. I disabled Verity and Verification. When I update to the new March build do I still have to continue disabling Verity and Verification or can I just run the flash script and it won't wipe or cause any issues?

I am using Magisk Stable and Kirisakura kernel.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Edit: I can now confirm that for me, on the March P6P firmware, using Magisk Stable v24.3 with Magisk Modules that already working fine on this update and Magisk version, I was able to flash the latest Kirisakura kernel (v2.0.0) using EKM (EX Kernel Manager) and the phone is working great.

That doesn't mean you won't have any trouble, though.

Original post: I can't specifically state one way or the other regarding that while using the Kirisakura kernel. In theory, no you shouldn't have to disable them. See below.

One user asked:

And the kernel's developer said:

The post Freak07 is referencing is:

We don't know which conditions they've fixed, or if they've fixed all conditions which caused that issue. The last time I got the device corrupt error after flashing a kernel, flashing the stock rooted kernel made the phone useable again without loss of data, and then the next firmware update that came out which I manually applied via the full factory image, made my device corrupt error screen go away.

There are numerous folks in the Kirisakura kernel thread who are stating they flashed the latest version on the March update and everything's working fine. They don't specifically state disabling Verity and Verification, and I would guess the assumption is that they haven't.

Also, always be as prepared as possible for something to go wrong. Do backups.
[Google Pixel 6 Pro] jac0b:
Is there a way to full backups like the way it used to be done with TWRP recovery?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Technically yes - ways using ADB root access that always exist for most every phone that you can use ADB root access with, but it's really not that reliable and not worth the hassle.

Personally, I just use Swift Backup, backing up to the cloud - I have it set so that in the middle of the night if my battery is over 50%, Swift Backup backups any updated app and its app data to the cloud, just in case my internal storage gets wiped, and also so I can save all my storage for music. :) You might be able to use some features free or get a free trial to the app for the paid features.

And there's nothing irreplaceable on my internal storage. I've got it all elsewhere or know where I can get it again.
[Google Pixel 6 Pro] Lughnasadh:
Just to add a bit to the Rode Warrior's very thorough response and good advice...

There was a fix in the March update to address "a" corruption problem people were getting. However, I don't know what specific corruption problem they were addressing. Could really be anything, including the corruption problem people were having when entering the A13 beta program and updating to A13DP1 on a locked bootloader. So it's possible some of the corruption problems people were facing were fixed, or possible that they weren't (I know, really helpful 🙃).

As an anecdotal footnote, I've had verity and verification disabled since the beginning (and continue to) and have also been using Kirisakura throughout and have never had the corruption problem. Freak07 has done the same thing and he has never had a corruption problem either, at least when concerning his kernel. I don't know for sure, but the amount of times people are having corruption problems in a variety of scenarios leads be to believe that there is still something wonky going on with vbmeta or the like. Don't know for sure but that is just my "gut feeling" based on observations in this forum, for whatever that's worth 🙃 That being said, many people have not had any corruption problems without having verity and verification disabled, so who knows.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I can now confirm that for me, on the March P6P firmware, using Magisk Stable v24.3 with Magisk Modules that already working fine on this update and Magisk version, I was able to flash the latest Kirisakura kernel (v2.0.0) using EKM (EX Kernel Manager) and the phone is working great.

That doesn't mean you won't have any trouble, though.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Google will let some Android apps keep their own payment systems

Google has granted Spotify an exception for its upcoming Play Billing rules, which might eventually open up to other app developers.

www.xda-developers.com
[Google Pixel 6 Pro] Norma Stitz:
Edit: false alarm

--------------------------------------

Damn it, I seem to F this up every single time. I followed this exactly.

I was already on Magisk Stable v24.3 (app "hidden" / renamed)

Used the full firmware zip, extracted to the same folder as the latest Platform Tools (S:\platform-tools)

Extracted the new boot.img

Copied new boot.img to the phone

Patched the new boot.img with Magisk Stable 24.3

Renamed Magisk'd boot.img so I know what version of firmware it's for

Copied the Magisk'd boot.img back to the computer

Disabled all my Magisk Modules

Removed the "-w " from the flash-all.bat

Re-edited the flash-all.bat to verify I saved it with the "-w " taken out

Open a Command Prompt, navigated to S:\platform-tools

adb reboot bootloader

flash-all.bat

Let phone boot, unlock it, check that it's working, allow the update process to finish (gave it five minutes or so)

All good to here.

adb reboot bootloader

fastboot flash boot magisk_patched.img (what I renamed it)

fastboot reboot

Now bootlooping.

View attachment 5569501

hmmm. Got it open in safe mode. That's a new one for me. Everything appears intact still.

Another reboot seems to have fixed it.

Root intact. Safetynet passed. All seems well.
[Google Pixel 6 Pro] Nergal di Cuthah:
What you should have done is while in safemode after booting with the magisk boot is direct install root at that point not reboot out
[Google Pixel 6 Pro] Bicet:
Same. Did you ever find a solution?
[Google Pixel 6 Pro] DespairFactor:
yeah this was fixed by google now
[Google Pixel 6 Pro] Bicet:
**** I still have the problem :/
[Google Pixel 6 Pro] roirraW "edor" ehT:
https://xdaforums.com/t/google-star...-android-12-qpr3-beta-1.4413609/post-86631933

Google releases Android 12 QPR3 Beta 1.1 for the Pixel 6 series to patch some issues

Google is rolling out Android 12 QPR3 Beta 1.1 to address a few bugs that were present in the initial release. Check out the changelog!

www.xda-developers.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
Google will allow Pixel users to opt-out of Android Beta Program without wiping device

In the future, Pixel owners running the beta software will be able to opt-out to the official Android release without wiping their device.

www.xda-developers.com
[Google Pixel 6 Pro] Lughnasadh:
Hopefully this will fix a lot of problems people were having...

https://twitter.com/i/web/status/1507397884941115428
[Google Pixel 6 Pro] roirraW "edor" ehT:
Major Pixel Launcher Mods update adds “At a Glance” widget replacing, Android 12 support, and more

Pixel Launcher Mods allows you to modify the stock launcher on your Google Pixel smartphone. The latest update brings tons of new features.

www.xda-developers.com
[Google Pixel 6 Pro] name_th:
Is it possible to update from the current production factory image to the current QPR3 Beta 1.1 factory image without wiping the device (by remoiving the -w)?

Is it mandatory, recommended or simply not necessary to wipe the whole device? :D
[Google Pixel 6 Pro] Lughnasadh:
You should be okay updating without wiping. It's not mandatory to wipe. Some would say it's recommended but not necessary.
[Google Pixel 6 Pro] roirraW "edor" ehT:
"Pixel Feature Drop (currently set for July)"? I thought the next feature drop is in June.

Google Pixel 6 can use more USB devices on Android 12L QPR3

The latest Android preview build for the Pixel 6 series includes Direct USB Access support, for compatibility with more audio devices.

www.xda-developers.com
[Google Pixel 6 Pro] Lughnasadh:
Haha, you beat me to the comment section 😅
[Google Pixel 6 Pro] roirraW "edor" ehT:
April firmware is out Pixel 6 Pro Factory Images.

12.1.0 (SP2A.220405.004, Apr 2022)	Flash	Link	bce807a636fe86eea129336c6f0ddbc026fa4b0af888bc25c92ffb3d007ba543

Pixel Update Bulletin—April 2022 | Android Open Source Project

source.android.com

Google Pixel Update - April 2022 - Google Pixel Community

https://support.google.com/profile/79501506
[Google Pixel 6 Pro] LLStarks:
February modem. Checking for T-Mobile Vo5G.
[Google Pixel 6 Pro] biTToe:
Can I flash this over S2B3.220205.007.A1 (beta) w/o any problems?

-flash all.bat removing -w
[Google Pixel 6 Pro] roirraW "edor" ehT:
I honestly don't know since I was never on the beta. In theory, yes, it should be fine, but be prepared for a full wipe if it doesn't work like it should.

To be clear, the flashing itself will be fine, but the Android data might be wonky coming from a beta.
[Google Pixel 6 Pro] LLStarks:
Looks like Google is making more partitions like product.img into sparse images instead of raw images. Had to convert it before I inspected it.

But now the T-Mobile carrier settings are encoded. I'd have to use the decode tool to peek in there.

T-Mobile carrier settings are chaotic. I think still Vo5G-less except for 13 DP1.

Maybe I should flash just the whole thing and avoid all this. Would make things crystal clear.
[Google Pixel 6 Pro] Lughnasadh:
I flashed from QPR3 Beta 1.1 to the March stable build of 12.1 (with -w removed) with no problems. Possible a few of your settings "may" revert (e.g. apps that are battery optimized and some "Special App Access" settings).
[Google Pixel 6 Pro] biTToe:
Has anyone here given this a go?

https://xdaforums.com/t/pixelflashe...tates-flashing-updating-pixel-phones.4415453/
[Google Pixel 6 Pro] roirraW "edor" ehT:
That kind of thing just isn't for me, personally. I don't think it's that hard to do the steps manually, and with one less piece of software in the middle that something could go wrong with.
[Google Pixel 6 Pro] LLStarks:
I tried using it. I didn't like how it assumes I'm working with an image zip instead of the nice unzipped folder I'm already working with.

Btw, April does not include T-Mobile Vo5G. Trying to trick the phone into reading the boolean that enables the toggle.
[Google Pixel 6 Pro] biTToe:
I tend to agree with you: It's not really that much more difficult, and I retain control, so if something goes wrong I know who's to blame
[Google Pixel 6 Pro] almahix:
Got rooted April. Thanks all. But will it fix my bugs? Time will tell!