yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] roirraW "edor" ehT:
You bought a (Carrier Unlocked) phone direct from Google? Not Verizon, T-Mobile, or AT&T (if you're in the U.S.).
[Google Pixel 6 Pro] michaelrager:
Yes directly from google the unlocked one.
[Google Pixel 6 Pro] michaelrager:
Correct and I checked the box and there is no carrier info and I am in the US
[Google Pixel 6 Pro] roirraW "edor" ehT:
Very strange! It shouldn't matter but had you tried to unlock it before putting a SIM card in it or only after? If only after try removing it and rebooting. If that doesn't help I'd consider doing a factory reset, but no idea if that'll help either.
[Google Pixel 6 Pro] Maxninja:
Just to clarify, to achieve Root access, the Pixel 6 and/or Pro needs to be purchased from the Google store and not from the main US retailers (AT&T, T-Mobile, etc)?
[Google Pixel 6 Pro] Deeglifsay:
"Failure [not installed for 0]" is what i got.

oem unlock is grayed out in settings.

help :(
[Google Pixel 6 Pro] mang0:
Is it connected to the internet? I remember reading about people having problems with some previous Pixels well. I can collect some threads for you....
[Google Pixel 6 Pro] Lughnasadh:
I was just about to ask this. And also if USB debugging is enabled. If I remember correctly I had to do both, I believe. For sure connecting to the internet. It was grayed out until I did one or both of these.
[Google Pixel 6 Pro] michaelrager:
For some reason, I just walked away and just came back and now I can check the box lol! I only want to temporary root to add a gps spoofer for pokemon go then un root. Forgive me, I havent rooted in years, Do I open command prompt (as administrator from a peticularfile?)
[Google Pixel 6 Pro] roirraW "edor" ehT:
If that's a question, then yes. The only way to guarantee that you can unlock the bootloader of Pixel is buying a carrier unlocked one from the Google Store in the U.S. I don't know what options there are outside the U.S.

This doesn't mean someone won't achieve the same thing on carrier-variants, but that depends on a lot of luck and developer's ingenuity.

Sometimes it depends on paying a foreign national to unlock it if they develope a super secret method such as what exists for Verizon variants of the Pixel 1.

When I bought my Verizon Pixel 1, I got lucky because before it received the Android 7.1.1 update (so on 7.1.0 or lower) we were able to unlock the bootloader. I think it was before inserting my then-Verizon SIM card.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Awesome. You don't need to run command prompt as an administrator. You can filter for the How To guides for how to root. Here's one of them. https://xdaforums.com/t/firmware-is-out-get-your-root-on.4353565/
[Google Pixel 6 Pro] allenjthomsen:
i know i went and got a pixel 6 and canceled my pro order im currently going through apps and disabling them one at a time to see if oem unlock becomes usable
[Google Pixel 6 Pro] mang0:
This was my plan too once mine gets here. Unfortunately gotta wait till Monday 😭 so hopefully you'll find something before then! Lol.
[Google Pixel 6 Pro] allenjthomsen:
im working on it only so many system apps that it could be its got to be one of them
[Google Pixel 6 Pro] mang0:
At one point I was thinking if we could have someone with an unlocked, stock device send a list of the apps, maybe we could compare and rule out certain apps 🤷‍♀️

But I can't do anything right now anyway except sit on my butt and watch lol.
[Google Pixel 6 Pro] allenjthomsen:
i just realized something and it may work depending , you are required to download pixel only device unlock app to unlock you sim.
[Google Pixel 6 Pro] mang0:
Oh? Tmobile used to have their own tmobile device unlock app, did that change?
[Google Pixel 6 Pro] allenjthomsen:
they do have their own device unlock app for the pixel 6 and 6pro it turns out maybe a temp unlock with it will let bootloader be unlocked.

Tutorials | T-Mobile Support

As you can see here you have to dowload the pixel only version
[Google Pixel 6 Pro] michaelrager:
Thanks! I found that earlier but it doesn't tell me where to run command prompt and I an unclear as to what boot.img they are talking about as there is 3 I think in the raven file.
[Google Pixel 6 Pro] card13:
@roirraW "edor" ehT Thank you, I was just curious in case a situation appeared again where I needed to have both slots the same (I like to ask before I get stuck up a creek w/o a paddle).
[Google Pixel 6 Pro] roirraW "edor" ehT:
You're welcome. Understood.

Just at minimum do (and you should do first thing):

fastboot flash bootloader --slot all bootloader.img

And that'll prevent you from getting stuck. Not doing that, you could wind up being bricked to a point where only Google could repair the phone.
[Google Pixel 6 Pro] DanielF50:
No worries 🤙

Oh. I thought feature drops were every three months as per the past 6 months schedule (March, June both had drops) and even 9to5 Google says:

In this article about the June drop.

Did I miss a update about this? There's even a mention of it on the Pixel 6 Pro product page - I'm not fussed about new features as most of the time they're usually only available/useful to consumers in the US, but was just confused to see literally nothing about it anywhere 😅
[Google Pixel 6 Pro] roirraW "edor" ehT:
I don't have the time to (find and) quote sources right now :) but Android 13 Stable is effectively the QPR4 feature drop (or QPR0 if you prefer). QPR1 Beta 1 was definitely announced to be expected to come out this month. I can't keep track now of when it's supposed to be final. LOL!

Edit: If another QPR would've been expected this month, we would've had QPR betas in the previous months. Instead, we had Android 13 Betas. I don't know, maybe I'm confusing things slightly.

I believe they also announced they would no longer have QPR Betas running at the same time as the major Android version Betas. So once Android 14 Beta 1 comes out next year, there won't be any more QPR betas until after 14 becomes Stable.
[Google Pixel 6 Pro] Lughnasadh:
I'm guessing the first Feature Drop for A13 will be in December.
[Google Pixel 6 Pro] badabing2003:
Sure you can

fastboot --skip-reboot update image-xxx.zip
fastboot --set-active=other
fastboot reboot bootloader
ping -n 10 127.0.0.1 >nul
fastboot update image-xxx.zip
[Google Pixel 6 Pro] roirraW "edor" ehT:
That's not what they asked. :) They asked if you could use Slot All with the update.zip.
[Google Pixel 6 Pro] badabing2003:
Sorry my bad, I misunderstood, I thought they wanted to edit flash_all and achieve both slots flashing fully.
[Google Pixel 6 Pro] roirraW "edor" ehT:
No sweat. It was a multi-layered or loaded question, or at least required a complex answer. The short answer was "No, you can't use Slot All with the update.zip, but you can do the following...".
[Google Pixel 6 Pro] DanielF50:
Ah, this makes sense - thanks! I didn't realise a major Android update counted as a feature drops (especially when they usually have less new features than the drops 👀)

I'm so out of loop with the Beta update malarky now... it's just too much to keep up with unless you're in the Beta programme 😅
[Google Pixel 6 Pro] roirraW "edor" ehT:
I agree. I suspect that Department A at Google also can't keep up with what's going on at Department B, and so forth with Department B1... LOL!
[Google Pixel 6 Pro] acwcanada:
Since updated to the A13 public release, the wireless charging on my P6P was working randomly, I was told that the September update would fix this problem. Guess what? After update, the wireless charging is even worse, now it is totally not working. I tried it on 3 different wireless charger: the Google Gen 2 and two Anker chargers, none of them is working. All 3 chargers would indicate that a phone is placed on it but the phone battery is not getting any juice!!!

P.S.: I do have overheat and battery drain problems on The A13 public release but still too early to tell if these are fixed with the September update as indicated by Google.
[Google Pixel 6 Pro] acwcanada:
After a few more hours of further testing, I really don't see that Google has fixed the wireless charging issue. All of my 3 wireless chargers are behave the same in two ways:

1. Phone is put onto the Charger stands and charging light is on but the phone is not charging at all.

2. Phone is put onto the charger stands , charging light is on and the phone is really charging normally. However, after a certain period of time ( it varies from a few minutes to less than a hour), the charging would then stop without reason (at least I don't see any). I have had this similar situation when my P6P was on A13 public release (I would put my phone for wireless charging when I went to bed and normally with around 40% battery and when I woke up after 6-7 hours of charging, the phone battery would be either gained a few percent or sometimes even less than when I started the charging, so those situations are exactly as the wireless charging never worked or charging just for a short period of time than stopped).

The overheat seems has been fixed or at least been improved. Before the September update, my P6P with normal use such as listening music with Spotify or watching YT video, the CPU temp would rise up to high 70's or 80's and the battery temp would also goes up to 50's to 60's, now most of the time, CPU temp would stay between 30's to 50's, battery temp would stay below 40's most of the time.

For battery drain, I would keep on testing for a few more days before I have exact idea.
[Google Pixel 6 Pro] Ghisy:
Which apps would you guys recommend to monitor the battery temperature?

I updated my P6P to the September patch with root and Kirisakura kernel without any problem btw!
[Google Pixel 6 Pro] bush911:
I occasionally look at the ex kernel manager for the battery temperature
[Google Pixel 6 Pro] Alienex22:
I updated my pixel 6 last mounth to Android 13 (OTA Update), just after I root my phone. I'm not sure to have android 13 on both slot.

Today I have an update, did I update directly with the OTA go to magisk and restore image or I need to do it with Android Flash tool. I'm afraid to brick my phone.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hiya. You don't really need to have the full Android 13 on both slots. However, it is recommended to have the Android 13 bootloader on both slots.

You can do so at any time by (from running Android):

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

(rename the Android 13 bootloader.img to the proper one for your device and firmware release version)

Do that first before anything else.

Then, you should be able to use any method you like to update as normal, although I'll mention the caveat that I always do: I always use the (full) firmware zip, never the OTA method. Sometimes the OTA method fails to work correctly, much more often than the firmware zip. However, no matter what, after you have flashed the Android 13 bootloader to both slots, you should be very safe. You should not be able to easily hard brick your phone after that.

Good luck!
[Google Pixel 6 Pro] Alienex22:
Thanks you very much for this answer. I try this now.
[Google Pixel 6 Pro] roirraW "edor" ehT:
You're welcome! Let us know how it goes.
[Google Pixel 6 Pro] Lughnasadh:
Battery Guru will monitor current, minimum, maximum and average battery temperature, with a time chart included. Can also set a battery temperature warning if you want.
[Google Pixel 6 Pro] Alienex22:
ADB tell me that :

C:\Android>fastboot flash bootloader --slot all boot.img

fastboot: unknown option -- slot

I'm currently on slot A

C:\Android\platform-tools_r33.0.3-windows\platform-tools>fastboot flash bootloader --slot all boot.img

Sending 'bootloader_a' (65536 KB) OKAY [ 1.856s]

Writing 'bootloader_a' (bootloader) invalid packed magic

FAILED (remote: 'failed to flash partition (bootloader_a)')

fastboot: error: Command failed
[Google Pixel 6 Pro] DanielF50:
I don't own a wireless charger but a lot of the vehicles I drive at work that have built in wireless chargers built-in and my expereience is similar but throughout A12, A12.1 and A13 (on the Pixel 6 Pro). Wireless charging worked for the first few months after the phone was released, but I haven't had much luck since then.

We use a VW ID.3 as a run-around and although the car recognises and states "charging mobile device", the phone usually comes off the charger with less battery than it went on with - even after a full hour of driving. My lockscreen shows "charging slowly" message, but this only shows for a split second then disappears, then pops back up again and then off again, and so on. I recently tried to use Ampere to check charge current while on the wireless charger too and this states "not charging".

I'm yet to try September update as the OTA hasn't come down to my phone yet, but I don't expect it to be fixed. At this point I'm wondering if there's a undisclosed hardware issue with the wireless charging components, or if Google broke something software wise and are clueless to what the issue is. My other theory is that the phone is using so much battery in the background (just staying on), that it's draining quicker than it can charge - Android Auto in wireless mode drains battery so quickly that the built-in USB-C to USB-C port (on said ID.3) can't keep up.
[Google Pixel 6 Pro] Lughnasadh:
First off, you're using the wrong command with the "boot.img"

Do this:

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

Insert the name of the bootloader image or the image itself in the < >.
[Google Pixel 6 Pro] Alienex22:
Did I need to use the original bootloader or the one I modified with Magisk ?
[Google Pixel 6 Pro] Lughnasadh:
What exactly are you trying to do? Are you trying to flash the bootloader to both slots or the boot image to both slots?

You don't modify the bootloader. You modify the boot image with Magisk if you want to root.

Boot image and bootloader are two different things.
[Google Pixel 6 Pro] Alienex22:
I'm trying to not to mess up my phone.

I want my bootloader on the two slot. I don't know if it active in both.

I updated from A12 to A13 with OTA, after that I rooted my phone with Magisk modified img

I just try again (with the modified Magisk boot img) and I think it's good :

C:\Android\platform-tools_r33.0.3-windows\platform-tools> fastboot flash boot --slot=all boot.img

Sending 'boot_a' (65536 KB) OKAY [ 2.148s]

Writing 'boot_a' OKAY [ 0.294s]

Sending 'boot_b' (65536 KB) OKAY [ 2.123s]

Writing 'boot_b' OKAY [ 0.271s]

Finished. Total time: 4.850s
[Google Pixel 6 Pro] roirraW "edor" ehT:
@Alienex22,

The bootloader is not the same as boot.img. The bootloader file has "bootloader" in the name. It's contained within the further update.zip that is itself within the main full firmware zip.

You do not modify the bootloader.img. You flash it to both slots. You don't have to flash anything else to both slots. After flashing the bootloader.img to both slots, then update your phone the normal way you want to.

Bootloader is bootloader.img <- the actual filename will be different depending on your device and firmware version, but no matter which device and firmware it is, the filename will include "bootloader" in it.

Kernel is boot.img.

Please don't use profanity on XDA. It's against our rules.
[Google Pixel 6 Pro] Lughnasadh:
If you want to flash the bootloader to both slots, see my response to you in Post #1,598.
[Google Pixel 6 Pro] xterminater07:
Hello, thanks for your amazing time on here in regard to this pixel 6 pro android 13! I just got a pixel 6 pro from a friend that has a broken wifi due to a february update, I updated it to the next update via mobile data and briefly saw my wifi network, but never again. I then proceed to updating the OTA android 13 via mobile data to see if it will fix it but nothing. The phone has not been bootloader unlock at all. I want to ask your advice or other experts here, would full flashing it again to android 13 september update potentially fix it or am I out of luck?

If so how to proceed correctly to full flash for both slots? Thanks so much again!
[Google Pixel 6 Pro] shoey63:
Just a heads up for anyone who wants to try and take the OTA after restoring images with Magisk and re-root by patching boot on the other slot.

It will bootloop back to the original slot so don't bother, especially if on A12.

You need to use fastboot to flash the patched boot image.
[Google Pixel 6 Pro] xterminater07:
I have tried factory reset already even before taking that july update, and nothing. It wasnt til after the july update that I was able to get the wifi to see network. Now I dont see any network listed at all on that pixel, while my iPhone, and other devices sees a bunch of wifi networks around us.
[Google Pixel 6 Pro] roirraW "edor" ehT:
If the things I suggested, especially if the September OTA or

Official Google Android Flash Tool

don't help, then I'm almost out of ideas.

The only other desperate measure I can think to try is: Developer Support images for Pixel. That is the only way to downgrade to Android 12 from Android 13, with Android still working correctly.

I don't really expect any better result from the latter, but it's a last-ditch effort other than sending it back to Google for repair.
[Google Pixel 6 Pro] xterminater07:
I can't adb reboot bootloader on my p6 pro. Checked the driver and its the latest. Do you perhaps have telegram to help? I can access the contents inside the pixel 6 pro but i can't adb reboot bootloader to it.

Edit: Android flash tool showed SD1A.210817.015.A4 (7697517), is that the right one?
[Google Pixel 6 Pro] roirraW "edor" ehT:
I hardly touch Telegram although I am technically on it, however, I don't provide one on one technical support. I only do so in public posts so that the solution to one user's problem may benefit another user who encounters the same issue.

When you have your phone connected to your Windows computer (assuming it's Windows), what does Device Manager show for the phone? Do you have USB Debugging enabled on the phone before you connect it to the computer? You may need to install the driver while Android is running, but you definitely additionally need to install the driver when you have the phone in Bootloader mode as well.

210817.015.A4 (the 210817 means August 17th, 2021) is the first version of Android that was released for the Pixel 6 Pro and is definitely the wrong firmware version. Not only that, but it shouldn't be capable of flashing that old version due to the fact that you're already on the August Android 13 firmware, and downgrades aren't allowed except for those shown on the Developer Support images for Pixel site. It should offer you either the September TP1A.220905.004 or the August TP1A.220624.021 Android 13.

You can see the various firmware versions for the Pixel 6 Pro here:

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

developers.google.com
[Google Pixel 6 Pro] xterminater07:
It's doing its thing now on the correct public build, it's unlocking the bootloader, showing boot slot b
[Google Pixel 6 Pro] roirraW "edor" ehT:
Great, let us know if the Wi-Fi is any better or not after. Good luck!
[Google Pixel 6 Pro] xterminater07:
Crossing fingers too, but does it matter if its showing boot slot b or a, do I need to flash both slots?
[Google Pixel 6 Pro] Lughnasadh:
Just curious what Magisk version you used? For what it's worth, it's been really hit or miss when using the "Install to inactive slot method" on this device. Some have no problems doing it, while it seems most do have problems. I think some of the problems, at least, come from people modifying some partition and then not restoring it back to stock beforehand.

But yeah, it certainly isn't a reliable way to update and keep root.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Nope, doesn't matter.

No, it's normal that both slots contain different versions of Android. That's what they're made for. If you use a normal OTA process, the OTA updates the slot you're not currently using, then when you reboot, it reboots into the already updated other slot which has become your new active slot.

You *can* flash the other slot if you really, really want to. If you do, before doing anything else, then do:

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

where you replace bootloader.img with the full filename the bootloader image that is kept within the secondary update.zip that's contained within the factory image zip.
[Google Pixel 6 Pro] roirraW "edor" ehT:
@beaverhead your post above is blank other than containing a quote of another user's post. Do you want to Edit your post above, or Report it to be deleted if it was a complete mistake? Cheers!

Edit: My bad, didn't realize your post had been inserted within the quote of @Lughnasadh's post. :)
[Google Pixel 6 Pro] Lughnasadh:
That person included their reply within my quote, it seems.
[Google Pixel 6 Pro] beaverhead:
yes.blame tapatalk.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Spoiler content hidden.
[Google Pixel 6 Pro] Nergal di Cuthah:
I didn't know tapatalk still worked with xda. (obviously it doesn't fully lol)
[Google Pixel 6 Pro] shoey63:
Latest canary. Hasn't worked for the last 3 updates, even while on A12.

It has worked with some variants of Magisk in the past, but I saw on GitHub that it's no longer supported for Pixel 6/Pro
[Google Pixel 6 Pro] Lughnasadh:
I didn't realize he removed that support again. I know in, I think it was, late 2020? he removed support for Pixels because it was leading to bootloops, but then he re-added support in Jan. 2022 with the release of Magisk 24.0 when he updated the bootctl binary. In May he removed the temporary note about OTA update no longer working on Pixels in the document instructions, but I don't see that he's updated those instructions to say it no longer works on the Pixel 6 series and didn't see anything in the changelogs referencing support removal.

Interesting....Oh well.
[Google Pixel 6 Pro] Lughnasadh:
"Android 13 QPR1 beta is now available and offers Quarterly Platform Releases (QPRs) for the current stable platform that include feature drops, bug fixes, and performance improvements ahead of the public release schedule."

Don't see downloads for the factory images yet, though.

@roirraW "edor" ehT Wasn't sure if you were going to create another thread for this (I think you mentioned that you may do that) or use your old thread (I was too lazy to find it 🙃), so I just posted it here.

Android Beta Program

Android Beta Program allows you to enroll your Android device for beta releases.

www.google.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
Done, thanks! I'm just repurposing my Android 13 Developer Preview / Beta thread: Android 13 QPR1 Beta 1 (September 8, 2022) is available via (opt-in) OTA - still looking for (full) firmware image zip
[Google Pixel 6 Pro] Ghisy:
Does anyone know what happened to the MVK kernel? The thread was locked and OP was deleted.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I do not, at least any further than the statement at the end of the thread:

I am curious too, but that information would be private between the OP and @Oswald Boelcke, and I have no true "need to know" so I won't ask them.

If I did have a need to know, I wouldn't be able to share that information, though, same as my esteemed teammate.
[Google Pixel 6 Pro] roirraW "edor" ehT:
SURPRISE new Factory Image:

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

developers.google.com

13.0.0 (TP1A.220905.004.A1, Sep 2022, Verizon, Verizon MVNOs)	Flash	Link	5e431fe5b488b48c4543a22f18356d1ad45c04fdab07bfe451ca13bdf08d0039

I see the September update for the 6a also came out. :)
[Google Pixel 6 Pro] rester555:
Is the radio any different?
[Google Pixel 6 Pro] roirraW "edor" ehT:
I haven't bothered downloading it (I'm not on Verizon). You can download it, extract the radio.img, then do a MD5, SHA1, or any other hash check and compare the results with the radio.img from the non-A1 September update to see if there are any changes. I'd say it's likely there are differences in the radio.img because that's mostly what the different carrier versions are about - I think.