yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] cmh714:
Yes, the radio has a different version number on it.....havent flashed it, not sure I will

***EDIT - I want to correct my comment......I was looking at the QPR.

The VZW radio is the same as the Non-VZW image radio. The QPR has a different radio. just for correctness.
[Google Pixel 6 Pro] swieder711:
Argh. Stable 13 Worldwide is running nicely on my P6P. Now there is a Verizon variant. Not sure if it worth the update. I am on Verizon's network.

I will probably dirty flash the VZ version over the WW version with the hope of better cellular coverage. Maybe I will just flash the modem file. Be nice to know if there are any other differences between the two versions.
[Google Pixel 6 Pro] hpower1:
post if you try and see any difference. Maybe i'll try using my P6P again....
[Google Pixel 6 Pro] swieder711:
I dirty flashed the VZ update over the WW and everything went to hell. Got repeated System UI crashes. Temporarily lost root. I am back on the WW release and things are stable again. I am going to just flash the Vz modem on to the WW release as an interim upgrade.

EDIT: The file names for the modem are the same in the WW and Vz versions, radio-raven-g5123b-102852-220720-b-8851166. Huh?
[Google Pixel 6 Pro] Nergal di Cuthah:
Did you try google's flash tool. I used it to convert from ww to vzw and no errors, no difference i can see, though my house sits in a low signal 4G when I'm out and about i get strong 5G and 4G signals.
[Google Pixel 6 Pro] TotallyAnxious:
Worked fine for me.
[Google Pixel 6 Pro] hpower1:
radio files have same name and md5. already off and back on the shelf.
[Google Pixel 6 Pro] swieder711:
I used the Flash-all script from my PC to my P6P to install the Sept-Vz update.
[Google Pixel 6 Pro] shag_on_e:
I just managed to flash A13 on the second slot with no issues. Since I was already set up on slot a I just rebooted to bootloader and ran the command fastboot --set-active=b then ran the modified flash-all.bat and booted up no problem. Then flashed the kernel I was running and boom good to go.
[Google Pixel 6 Pro] Nergal di Cuthah:
Figured that's why i asked if you had tried the tool, it's pretty good about stubborn installs
[Google Pixel 6 Pro] Amd4life:
Does the vzw September radio perform better?
[Google Pixel 6 Pro] roirraW "edor" ehT:
After you issued the change slot command, did you fastboot reboot bootloader again? If not, the September bootloader might not be on the new slot, although it's possibly working just fine on the August Android 13 bootloader.
[Google Pixel 6 Pro] Lughnasadh:
I think they should be fine with having the September bootloader and image on that slot without rebooting into the bootloader first before running the flash-all.bat command, although it's always good to verify that you actually switched slots beforehand:

fastboot getvar current-slot

And seeing which slot everything is flashing to while running flash-all.bat is a good confirmation as well.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Ah, interesting, thank you. I could have sworn that after issuing a change slot command that a reboot was necessary. I know the Flash-All.bat would reboot to bootloader, but only after flashing the bootloader and radio.

Edit: Unrelated - the notifications on my phone are spot-on immediate today - the exact same moment they pop up on my computer. Most of the time on my Pixel 6 Pro, there was at least a very slight delay (a minute or a few). On the Samsung Note 10+, it was utterly horrible (45 minutes to 2 hours later).
[Google Pixel 6 Pro] roirraW "edor" ehT:
https://twitter.com/i/web/status/1569645665080459265

View attachment 5710403

GitHub - topjohnwu/libsu: A complete solution for apps using root permissions

A complete solution for apps using root permissions - topjohnwu/libsu

github.com

libsu/CHANGELOG.md at master · topjohnwu/libsu

A complete solution for apps using root permissions - topjohnwu/libsu

github.com

Does anyone know if libsu is part of Magisk, or is it just part of some apps that access root? Just curious.
[Google Pixel 6 Pro] Lughnasadh:
When I first updated to A13 I flashed the flash-all.bat file to update. Then to put A13 on the other slot I just switched slots, verified it had switched slots, and then flashed the flash-all.bat file again without rebooting into the bootloader first. I did this because I didn't want to reboot into the A12 bootloader, which was still on that other slot. I then verified that the A13 bootloader was on both slots.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Makes perfect sense. Thanks.
[Google Pixel 6 Pro] Lughnasadh:
Yes, it is implemented in Magisk. Here is the commit that updated libsu within Magisk. It is also used outside of Magisk itself, for example, by developers who build root apps on top of it. That's about the extent of my knowledge of it 🙃
[Google Pixel 6 Pro] Ghisy:
No one for the contrast / saturation part? 😢
[Google Pixel 6 Pro] roirraW "edor" ehT:
I never fool with those details, so I can't make any recommendations.
[Google Pixel 6 Pro] Ghisy:
Next to my 4 XL, I find the display on the P6P a little dull for my liking...

Thanks anyway!
[Google Pixel 6 Pro] LLStarks:
Maybe my local towers changed, which seems more likely, but I'm curious as to whether the modem was tweaked in QPR1.

Seeing much higher priority for standalone 5G and I'm even seeing n41 as a primary standalone cell.

Usually had to go less than a mile and into the city for that.
[Google Pixel 6 Pro] Teet1:
I sort of noticed this as well. 5G signal still sucks but when I set my network to LTE, it is at maximum signal strength and does not cut off anymore while at work when it used to do this all the time
[Google Pixel 6 Pro] Amd4life:
Is this on QPR1 or on the Verizon rom? I want to flash whichever one has better signal strength.
[Google Pixel 6 Pro] biggiesmalls657:
I got a version after this one T1B1.220819.006 and my radio is updated for last month, The kernel was updated Aug 5th. Im also a beta tester and i need a boot.img for root :(
[Google Pixel 6 Pro] roirraW "edor" ehT:
That's QPR1 Beta 1, from Factory images for Google Pixel. I also have links to it in my thread for the Beta versions [General] Android 13 QPR1 Beta 1 (September 8, 2022 - t1b1.220819.006 for P6P) is available via Opt-In, OTA zip, or (full) firmware image zip.

Get the boot.img from the inner zip inside the factory image zip.
[Google Pixel 6 Pro] LanJie:
Hi guys, I just got my pixel 6, and updated it to android 13 with 220905.004.A1 (the latest version).

Now I try to root the system by magisk (updated to the latest version).

However, it did not work after I flash the modified boot img and said "cannot load android system. your data may be corrupt".

I try to flash back by using the default factory provided boot.img, still not working.

Is there any way to solve it please. I stuck on this issue for a long time.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hello and welcome!

Try dirty flashing the full factory image - not just the boot.img (remove the -w from the flash-all.bat so that it doesn't wipe). If that doesn't help, a wipe may be necessary. If you have to, you could try

Official Google Android Flash Tool

(OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own). It has solved things that the factory image hasn't.

FYI, I have no idea why flashing the modified boot image would cause that issue.

Also, you should do this ASAP if you haven't already:

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

Replace bootloader.img with the name of the bootloader file from the inner zip inside the factory image zip. Don't confuse it with the boot.img, which is the kernel. There are several other threads that might help you specifically with rooting. Click the yellow How To Guide quick filter at the top of the list of threads in this section. There are 2 or 3 root process-related threads.
[Google Pixel 6 Pro] LanJie:
Thanks so much, you are sosososo cool~
[Google Pixel 6 Pro] roirraW "edor" ehT:
Google mandates virtual A/B system updates for devices launching with Android 13

www.xda-developers.com
[Google Pixel 6 Pro] Doug8796:
This thread confuses me. Can one root a device that is currently sim locked?
[Google Pixel 6 Pro] Homeboy76:
I could be wrong, but I believe a

sim locked carrier

means your

bootloader is not unlockable

.
[Google Pixel 6 Pro] Nergal di Cuthah:
Verizon = Not simlocked but forever bootlocked

Att and t-mobile sim locked must be sim unlock to bootloader unlock can get sim unlock after phone is paid off or x number of days (probably which ever is longer)
[Google Pixel 6 Pro] Homeboy76:
Verizon Device Locking FAQs
[Google Pixel 6 Pro] roirraW "edor" ehT:
SIM locking, which locks your SIM card to your device, i.e. can't move that same SIM card with another device, is not the same as being Carrier locked. The ability to lock your SIM card to your device is controlled by you only - by default, SIM cards are not locked to the device. You can use the search field in the device Settings to find "SIM card lock", which is in the "More security settings" submenu.

As the others have said, Carrier unlocking and having the ability to bootloader unlock are two separate things, but typically if a device is not carrier unlocked, then you are also not able to unlock the bootloader. Being carrier unlocked does not necessarily mean you can unlock the bootloader. Example 1: Verizon. Example 2: All Samsung devices bought in the United States that can have mobile data connections. Samsung WI-Fi-only tablets can be bootloader unlocked (at the cost of tripping KNOX permanently), but obviously, in that case, there's no carrier involved.
[Google Pixel 6 Pro] roirraW "edor" ehT:
September Update For Verizon Pixel 6, Pixel 6 Pro Goes Live For Real

We still aren’t sure what happened exactly or why it has taken this long, but Google and Verizon finally fist-bumped this week and began pushing the September update for the Pixel 6 and Pixel 6 Pro. We first reported the supposed availability of the update on September 12, yet... #Google #Pixel6

www.droid-life.com

Apparently people on Verizon weren't getting the September Verizon OTA until today (not counting flashing it manually).
[Google Pixel 6 Pro] Nergal di Cuthah:
Did not know this, I've been buying unlocked for so long i missed that vzw had codified a new policy.
[Google Pixel 6 Pro] roirraW "edor" ehT:
https://twitter.com/i/web/status/1575207622189277184

https://twitter.com/i/web/status/1575210345240571904
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'm on the fully up-to-date Stable v88.x Phone app, and the Beta program is full in the Play Store. I assume you could install the Beta version from another site, but quite often these features are enabled on the server side, so just installing the Beta v90.x Phone app won't necessarily see this feature. I enabled it in Developer Options anyway.

You can test Android 13's predictive back gesture on Pixel with these Google apps

With Android 13, Google began work on the predictive back gesture, and you can now test it with the Phone app on Pixel...

9to5google.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
13.0.0 (TP1A.221005.002, Oct 2022)

Flash / Link

d61dff29d5c9ba513a959d1b87be08df59432c7c0dc17092ab462d12492adfd5
[Google Pixel 6 Pro] Ghisy:
Always on top of things I see! I was gonna post that! :P
[Google Pixel 6 Pro] roirraW "edor" ehT:
:) I try!

Google Pixel Update - October 2022 - Google Pixel Community
[Google Pixel 6 Pro] roirraW "edor" ehT:
Pixel Update Bulletin—October 2022 | Android Open Source Project

source.android.com
[Google Pixel 6 Pro] LLStarks:
No modem update. We'll see what QPR1 Beta 2 brings on Wednesday.
[Google Pixel 6 Pro] bobby janow:
How do you know it's Wednesday?
[Google Pixel 6 Pro] Lughnasadh:
I signed up for the Phone beta through this link, even though Play Store said it was full. Maybe it will work for others.

Sign in - Google Accounts
[Google Pixel 6 Pro] foobar66:
Succesfully upgraded to October release, keeping root and data,.
[Google Pixel 6 Pro] Lughnasadh:
OTA Install to inactive slot method or Pixel Flasher or modifying flash-all.bat file?
[Google Pixel 6 Pro] foobar66:
Modified flash-all.sh (just removing -w flag on the update line).
[Google Pixel 6 Pro] Lughnasadh:
Removing the -w but also adding the patched boot image I presume, since you kept root?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thank you! Worked for me immediately. Opted in using that link, right-clicked on my Phone app icon in Nova Launcher, went to the Play Store entry, and said "Beta" and an update was available. I don't see any predictive back gesture preview, yet. Maybe because I "cheated" to get into the Beta and a server-side update isn't enabled for me...
[Google Pixel 6 Pro] foobar66:
No, I first did the full upgrade, then reboot (without root), let the phone 'settle' for 2 minutes, reboot to bootloader, flash patched boot image, reboot. Then reinstall Magisk app, reboot again. Reinstall Magisk modules (USNF, Shamiko, my own module). Final reboot.
[Google Pixel 6 Pro] Lughnasadh:
Oh, it sounded like you did it all in one shot because you said you kept root. You actually just re-rooted. Gotcha.

I was asking what method because there is a question of whether the Install to Inactive Slot method still works on the Pixel 6 series.
[Google Pixel 6 Pro] Lughnasadh:
Awesome it worked. You might be able to do this with any app where the beta is full if you can get the beta link to it. My predictive back gesture for the Phone app is working on beta 90.0.477356402. It may be a server side update though, as you mentioned earlier.
[Google Pixel 6 Pro] foobar66:
Actually the updates always get installed into slot_b for me.

Only with the 12->13 upgrade, I manually flashed the bootloader, boot.img and radio to both slots A and B.

I don't think I've ever used slot A so far.

The updates and keeping root/data have always been fine for me (so far).
[Google Pixel 6 Pro] Lughnasadh:
Yeah, when you update via flashing the factory image it always stays on the same slot. Updating via OTA updates the inactive slot and switches to that slot afterward. But I was more curious if you did the Install to Inactive Slot method, which you didn't.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Also confirmed, the beta version that was installed for me is the exact same - 90.0.477356402-publicbeta.

I just tried a reboot, and I also confirmed I still had the developer option for this enabled, but no effect. Oh well, like all things Google, it'll arrive eventually, or not. Or arrive and then go away. 😁
[Google Pixel 6 Pro] almahix:
i installed the Oct 22 build and it is working fine. /I downloaded and extracted the boot image, however I cannot get magisk 25.2 to patch it. I have tried repeatedly. If anyone has been able to successfully patch, please post a link so I can root my phone. Thank you in advance.
[Google Pixel 6 Pro] cmh714:
Magisk Patched v25.2 (25200) this is from todays Image, not sure on Oct 22.....

AND the is for Raven.....not Oriole
[Google Pixel 6 Pro] awtompson:
I used PixelFlasher to patch the boot image and flash October build. Worked perfectly.
[Google Pixel 6 Pro] roirraW "edor" ehT:
You downloaded the factory image zip, extracted the boot.img file from the inner zip?

Mine patched fine. Try rebooting?
[Google Pixel 6 Pro] almahix:
Yes, exactly I tried to download and unzip on a second pc, and tried magisk on another android phone. Same results. Don't know what else to do, other than ask for a patched boot image. Pretty please!
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'm pretty sure another user a few posts up already supplied one for you. 😀

Have you done this before successfully? I feel there must be a simple reason why it's failing for you. What exactly happens? Can you take some screenshots to show us?
[Google Pixel 6 Pro] almahix:
I set the file to patch and I get I station error. Any yes, I e done this countless times before.
[Google Pixel 6 Pro] Nergal di Cuthah:
A screenshot would really help here, I've never heard of a "station error"
[Google Pixel 6 Pro] almahix:
I downloaded the patched file. I flashed it successfully. Thanks everyone for the support. You're all super and I appreciate you.
[Google Pixel 6 Pro] badabing2003:
I flashed my Pixel 6 to inactive slot using PF 4.1, it worked.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I, too, would like to see a screenshot of what a "station error" looks like.
[Google Pixel 6 Pro] Lughnasadh:
That's great! What I'm really interested in, though, is if anyone updated via OTA using the "Install to Inactive Slot" method in Magisk. There are reports that that method is no longer working for Pixels or for the Pixel 6 series, although one person last month did use it successfully but they had verity and verification disabled which makes me wonder if that may now be required to use this method.

I believe @shoey63 was maybe going to test it this month by disabling only verity beforehand.
[Google Pixel 6 Pro] badabing2003:
I personally avoid OTA.

I find it slow as hell and problematic, the only benefit I see with OTA is that you don't need a PC to do the update.
[Google Pixel 6 Pro] Lughnasadh:
I avoid it as well. I update via flash-all every month, but some people still like using that method for the reason you state so we're trying to figure out if anything has changed since John Wu re-implemented this method for Pixels earlier this year.
[Google Pixel 6 Pro] almahix:
Installation error. It was very late last night. Sorry! Coupled with the fact that I worked with computers since the 70s and I still can't type.
[Google Pixel 6 Pro] Nergal di Cuthah:
So i still vote for screengrab of your adb session failing to fastboot flash magix_patched_boot
[Google Pixel 6 Pro] almahix:
The issue was magisk not patching the boot.img, not adb
[Google Pixel 6 Pro] roirraW "edor" ehT:
https://twitter.com/i/web/status/1577787539116605442

https://twitter.com/i/web/status/1577787540190339072
[Google Pixel 6 Pro] BostonDan:
Just have to say that Oct update seemed to really help my battery life and phone temperature. Not sure why, but I'll take it.

I do the restore images in magisk, the run the OTA and let it optimize my apps (yeah, yeah, takes forever), then reboot. Meanwhile I download the image and extract the boot image. Once the phone reboots I patch the boot image with magisk.

Finally, I adb reboot to fastboot and boot (not flash) the magisk patched boot image and then once I have rebooted and unlocked the phone, I go to magisk and do a direct install of magisk (after verifying the phone is rooted through magisk) and then reboot once more. This is the only method I use after having had a number of issues with applying magisk to the alternate slot and causing the system to soft-brick with previous phones.

Cheers,

B.D.
[Google Pixel 6 Pro] HipKat:
Bug fixes and changes​

There are 9 bug fixes in this October patch. Below is the full list where you’ll find that the fixes are for all still-supported devices, except for the first issue about noise artifacts. That fix is for Pixel 4, 4a, 5, and 4a only.
[Google Pixel 6 Pro] HipKat:
BTW, I have zero of the issues this is supposed to fix....
[Google Pixel 6 Pro] shoey63:
Tried it but got the "installation problem" message, no doubt due to vbmeta partition being no longer pure stock.

Ended up sideloading the OTA and booting the extracted boot.img after patching it with Magisk, then proceeding with a direct install.

It seems root after update is no longer possible without a PC
[Google Pixel 6 Pro] Lughnasadh:
That's too bad. Still strange that that other person was able to update in September with verity and verification disabled. Oh well, things...
[Google Pixel 6 Pro] Lughnasadh:
For what it's worth...

https://twitter.com/i/web/status/1579486948263342080
[Google Pixel 6 Pro] roirraW "edor" ehT:
https://twitter.com/i/web/status/1579695277778571266

View attachment 5732187
[Google Pixel 6 Pro] diesteldorf:
Hoping someone can provide some assistance......

I updated to the latest Magisk Canary release last night. After the app was updated, I was expecting to flash the updated boot image from within the app, but I kept getting a message to " upgrade to the full Magisk Manager to finish the setup"

Similar to this thread: https://xdaforums.com/t/magisk-manager-app-refuse-to-open-after-recent-update.4252663/

I uninstalled Magisk, reinstalled, patched, and flashed a new boot image manually using fastboot, but was still getting the error.

Then I downloaded the new October Google system image, manually extracted the boot image, patched it, and flashed, along with the bootloader, radio, update.zip, using fastboot.

The update went smoothly and I am 100% rooted, but Magisk shows it is not installed, even though I pass SafetyNet.

It is annoying because I am not able to install or remove modules or manage my Zygisk Hide App List.

View attachment 5733091
[Google Pixel 6 Pro] roirraW "edor" ehT:
Now we have to wait for Android 13 support, but...

TWRP 3.7.0 lands with long-awaited Android 12 support and various other fixes

The Team Win Recovery Project (TWRP) has been updated to version 3.7.0 with Android 12 support and many other improvements. Read on!

www.xda-developers.com
[Google Pixel 6 Pro] Nergal di Cuthah:
Now that we're half way to A14

Lol
[Google Pixel 6 Pro] Nergal di Cuthah:
In case someone missed it, there was a second canary magisik pushed yesterday, my guess is that it fixes something wrong with the first release
[Google Pixel 6 Pro] roirraW "edor" ehT:
When things were working fine as is on Magisk Stable, I highly recommend not "fixing" it. :)

Try this: Flash the stock unrooted boot.img to your phone. Then with the Magisk Canary 25205 rooted boot.img on your computer:

fastboot boot boot-magisk_patched-25200_1a2B3c.img

Then when the phone boots, hopefully normally and rooted, then click Install beside Magisk in the app and choose direct install. I hope that works for you.

If that doesn't help, I'd suggest dirty flashing using the

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). The flash site can fix problems that even the factory image zip can't. Just make sure you have the following options

unchecked

:

Wipe

Force flash all partitions

Re-lock bootloader

After that, then try the directions I gave above starting with "Then with the Magisk Canary 25205 rooted boot.img on your computer".

Good luck!
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yep, SafetyNet wasn't working on 25204. Thanks!
[Google Pixel 6 Pro] diesteldorf:
Can you please look at my screen shot above and tell me if I have the latest Canary build installed? What is the build number?

When I opened Magisk recently, it wasn't prompting me to automatically update.
[Google Pixel 6 Pro] Lughnasadh:
There is an issue opened up for the "upgrade to the full Magisk Manager to finish the setup" bug. Check out the workarounds posted in there.
[Google Pixel 6 Pro] Nergal di Cuthah:
Looks like latest to me. Here's mine View attachment 5733099
[Google Pixel 6 Pro] Lughnasadh:
25205 is the latest Canary release.
[Google Pixel 6 Pro] Ghisy:
How come TWRP is always so far behind now? Is it technical difficulties? Or because people are not really asking for it nowadays?

Although I have to say I do miss it sometimes.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I don't really have any insight into it. Any combination of all of those plus that it's just voluntary work, so as time allows. Everyone has real life and real jobs. Despite that there are users who still want it, I feel that there must be less demand for it than ever. I haven't missed out on anything, not having TWRP.
[Google Pixel 6 Pro] diesteldorf:
For those that were able to install Magisk correctly, and have it hidden, can you please tell me what the hidden app is typically called and/or where it is stored?

I've received a lot of good tips, and I'll have a chance to troubleshoot tonight, but I also want to make sure Magisk, if it is still hidden, is completely uninstalled.