yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] roirraW "edor" ehT:
No, the Google USB driver. I found that Windows 10 was able to load the driver automatically for giving the command to reboot, but once the phone had booted into the other mode, I had to go to Windows' Device Manager, from there the devices without a driver stands out, then I pointed it to where I extracted the latest Google USB drivers.

Then you can run the command to unlock the bootloader.

I will likely make everything even more clear, but it will be as time allows me to.
[Google Pixel 6 Pro] Carousser:
I ran into something similar when I was going through the motions last night. Might be worth a shot.

When I first plugged my P6P into my desktop (Win10), it had downloaded a driver automatically and I was unable to manually update the driver through Device Manager. Windows said the most up-to-date driver (MTP) was already installed.

I uninstalled the driver through the context menu of the phone in Device Manager, unplugged and re-plugged it in, and then was able to manually install the usb_driver.

After that, fastboot was then able to see the phone. Try doing the above and when you reboot into bootloader, run

fastboot devices

to see if it is then recognized.
[Google Pixel 6 Pro] michaelrager:
also for flashboot it has two options after I select the pixel. wipe device lock bootloader then there are advanced options like force flash all partitions and disable verity. I don't know what to select so I didn't go any farther.
[Google Pixel 6 Pro] michaelrager:
in device manager what is the phone most likely under? I cannot find it.
[Google Pixel 6 Pro] Carousser:
Should be under Portable Devices

View attachment 5445995
[Google Pixel 6 Pro] michaelrager:
I found it uninstalled it like you said reconnected it but it reinstalled automatically
[Google Pixel 6 Pro] roirraW "edor" ehT:
I didn't say to uninstall it. :) I said in a roundabout way that if the driver wasn't installed that you would see it called out without manually expanding any particular section, so it would be easy to see if the driver isn't installed and right-click, tell it to install the driver you downloaded from Google (not Platform Tools).
[Google Pixel 6 Pro] michaelrager:
I clicked on update driver and it said I have the most up to date. Tried 3 times.
[Google Pixel 6 Pro] michaelrager:
yeah that was a response to carousser not you sorry.
[Google Pixel 6 Pro] michaelrager:
Thanks!! I got it to work like that and unlocked it!! Now for the purpose to install a gps spoofer (for pokemon go) as a system app then re lock it so I can use my work email, What do I do?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Great! No idea about GPS Spoofer. You'd be best to make a new Question thread to ask if you can't find a thread that already helps with that.
[Google Pixel 6 Pro] michaelrager:
No I know how to do it, I just meant ho do I proceed for temp root?
[Google Pixel 6 Pro] roirraW "edor" ehT:
For that you'll have to refer to one of the other folks' threads specifically about rooting. Just filter the 6 Pro section for How To Guides and one or more of the other threads should help you.

Eventually when there is more of an authoritive and completely stable method and versions of Magisk, then I might give the instructions on the first post, but in the meantime there's no use having one more thread specifically about rooting, so I'll leave it to the others in the meantime. 😁
[Google Pixel 6 Pro] sarabraj.singh:
has anyone gotten Viper4Android to work correctly after root and installing the apk file manually?
[Google Pixel 6 Pro] Lughnasadh:
https://twitter.com/i/web/status/1662323594427531265
[Google Pixel 6 Pro] roirraW "edor" ehT:
No update yet, but at least:

Android Security Bulletin—June 2023 | Android Open Source Project

source.android.com

Edit: And looks like two different security patch levels, unless a typo:

View attachment 5926403
[Google Pixel 6 Pro] Nergal di Cuthah:
What was the final decision on platform tools should we install latest? You changed the thread title for the "new bug" in platform-tools but i can't find the post text about it and whether we should stick with old reliable march version (also what command do i use to get platform tools version)
[Google Pixel 6 Pro] Lughnasadh:
Yeah, that's normal. 01 contains Android Framework patches and 05 contains vendor and kernel patches.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I still use 33.0.3. There are links at the top of the OP to it. :)

Edit: You can use 34.0.3 - it's just that you may have to jump through some minimal hoops for it to work completely for you. They're not huge hoops, but it's just simpler to stick with 33.0.3.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Very soon?
[Google Pixel 6 Pro] Lughnasadh:
Hands-free photos, SpO2 and more for the Pixel family

The June Feature Drop for Pixel phone, Pixel Watch and Fitbit is here.

blog.google
[Google Pixel 6 Pro] roirraW "edor" ehT:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Google Pixel Community

Android Security Bulletins | Android Open Source Project

source.android.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
@Displax has updated Universal SafetyNet Fix Mod to v2.4.0 Mod 1.3 on XDA (and on GitHub, linked to in the XDA OP, as well).
[Google Pixel 6 Pro] Nergal di Cuthah:
There seems to be a new "feature" of having wallet show on lockscreen. For anyone who has a card in theirs but don't pay with it. Setting is default on and is in lockscreen settings to remove it. Not sure if that's the june feature release or an update to wallet, but i personally don't want my card available for the public (rhough it does look like you need a fingerprint to do anything but see the last 4 digits, but still)
[Google Pixel 6 Pro] roirraW "edor" ehT:
T-Mobile June Factory Image:

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

developers.google.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
No July Stable firmware yet, but this is updated:

Pixel Update Bulletin—July 2023 | Android Open Source Project

source.android.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
July 2023 Stable firmware:

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

developers.google.com

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Google Pixel Community

Edit 3: NOW, the July page at this link is present:

Android Security Bulletins | Android Open Source Project

source.android.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
NOW, the July page at this link is present:

Google Pixel Update - July 2023 - Google Pixel Community
[Google Pixel 6 Pro] Kennyeni:
Has anyone tried the latest (july 2023) update with Magisk?
[Google Pixel 6 Pro] felek73:
All is OK with latest magisk stable
[Google Pixel 6 Pro] darkness4every1:
After this update, using any Gboard version other than the one that came with the phone (uninstall updates) will result in no search results in the app drawer search bar.

Did 2 factory resets.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Is this problem still happening?

I'm not on the 6 Pro - I'm on the 7 Pro, and I use Nova Launcher Prime normally, but I just launched the Pixel Launcher, since I opt to have an app icon for it, and I was able to search the Pixel Launcher's app drawer fine with Gboard version 13.0.07.528826899-release-arm64-v8a, from June 7, and there are no Stable Gboard updates available.

Are you opted into Gboard's Beta program, by any chance?

I'm on July Global Stable, but as I said, on the 7 Pro, so I don't know if there could be a 6 Pro-specific issue.
[Google Pixel 6 Pro] darkness4every1:
I've opted out of the beta, tried multiple gboard apks but none works other than base version. Any other keyboard from the playstore also works.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I was Googling to find anyone else who might have the same issue, and I found your Reddit post about it. :) I also found information about a similar issue from last year. About the only real applicable advice I see suggested there is:

If you haven't already. Actually, I see you can do so directly from GBoard's settings, as well - click the 3-dot menu and you can choose "Help & feedback" from there, then "Send feedback" at the bottom of the next screen.
[Google Pixel 6 Pro] Nergal di Cuthah:
I know this is basic, but did you delete data for the keyboard and see if there was a bad command in there that only triggers above that base version
[Google Pixel 6 Pro] darkness4every1:
I did delete data and/ or cache of gboard, pixel launcher etc, did 2 wipes, did a full Android installation with the flashtool.

Small note, I've updated from June update to July update with Pixel Flasher and my phone bootlooped and wouldn't get out of Fastboot, only way to fix it was to use the official flash tool.

My phone is rooted and I'm using AOSP mods, Pixel Launcher Mods and Pixelify. Despite the keyboard doing this after a fresh install I thought it would be useful to mention.
[Google Pixel 6 Pro] Nergal di Cuthah:
If you disable the mods and pixelfy and rebooot do you still have the same problem?
[Google Pixel 6 Pro] darkness4every1:
Yes

As a fix I have the base version of gboard with auto updates disabled.
[Google Pixel 6 Pro] snovvman:
For July's update, patching the boot.img with Canary 26103 fails. I thought I read that 26103 is buggy and that I should use 26102 instead. Is this correct? I've never had trouble patching before so it's new to me. Thanks!
[Google Pixel 6 Pro] Lughnasadh:
Yes, that is correct.
[Google Pixel 6 Pro] snovvman:
Thank you. Currently on the June update patched with 26103, I uninstalled the apk and installed 26102. It immediately updated itself to 26103. I suspect it's because the boot was patched with 26103?

All I need to do is to patch the July boot with 26012, but I need the app running. I found some complicated ways to downgrade, but I'm looking for the easiest way to patch the July boot. Any suggestions on how to go about it?
[Google Pixel 6 Pro] Lughnasadh:
If you are going to update to July, then uninstall the Magisk app and update (I'm assuming you are using an update method where you will lose root). Once updated, install the 26102 Magisk app, patch the boot image and flash it.
[Google Pixel 6 Pro] snovvman:
I'm trying to avoid losing root. I typically download the image, patch the boot, flash the image, flash the patched boot immediately after the image so the phone boots with the update and root is retained.
[Google Pixel 6 Pro] badabing2003:
That will work for sure, another way is to uninstall 26103, install 26102 but not launch it, then use PF to create a patch (in configuration settings enable Offer Patch Options) when patch option is offered, use Magisk application 26102 instead of recommended rooted Magisk 26103.
[Google Pixel 6 Pro] badabing2003:
If you follow my suggested way, you can avoid losing root.
[Google Pixel 6 Pro] BROKEN1981:
I had it on my lock screen since A12. Was also able to remove it.
[Google Pixel 6 Pro] BROKEN1981:
What I had to do was delete the magisk app, in Pixel Flasher download stable, then I was able to patch boot image and flash. You don't lose root and flash everything all at once.
[Google Pixel 6 Pro] snovvman:
Thanks. I will look into PF. I have always just patched and flashed manually. If I understand your suggestion correctly--I will uninstall 03 and install 02 like I did, but not launch 02, connect PF, and it can leverage the 02 that was installed to patch the boot?
[Google Pixel 6 Pro] badabing2003:
Correct,

You can create the patch in pf and if you feel more comfortable flashing manually you can still do that.
[Google Pixel 6 Pro] BROKEN1981:
Plug your phone into the PC, load up PF. On the device delete Magisk. On PF install Magisk. It will ask what version. Click stable. Get the factory image. Process it. Select boot image. Click patch. Select patched boot and hit flash pixel.
[Google Pixel 6 Pro] snovvman:
Thank you, @badabing2003, @BROKEN1981, @Lughnasadh. I have been an XDA member since 2008. I come back to this thread each time because it has been one of the most helpful and friendly thread that I've seen--I appreciate the people here. Thanks for @roirraW "edor" ehT for staring it.
[Google Pixel 6 Pro] snovvman:
All's well that ends well. Not what I intended, but I am now updated and rooted on 03.

This is what happened:

1) Uninstall 03, but not launch, install 03. Connect PF. After connecting, a message popped up on the phone asking to update Magisk. PF would not respond until I did. I was back on 03.

2) 2nd try. Connect to PF first (got warning about 03), then uninstall 03 and install 02. Selected Offer Patch Options, got the pop up on the phone to update again, but I ignored the message. Used option 2 to patch. Log read before patching:

I decided to let PF flash. It went fine and the phone booted. This is where things were strange: When I launched Magisk, the Magisk portion showed that it was patched with version 25xxxx and the app portion showed that it was 03. Magisk wanted to update boot, so I let it. Luckily, 03 had no problem doing a direct patch (as opposed to the failed file patch).

This is how I am now on July with a patched 03. I kept the log, so if there is any information you would like to see, let me know.

Thanks again for the help!
[Google Pixel 6 Pro] Suavie103:
Does anybody have a patched july 6 pro boot image?
[Google Pixel 6 Pro] badabing2003:
I see few things that I don't understand or don't make sense,

Some could just be a typo:

example:

but to to better comment on everything that went on, it's best if you launch PF, and create a support file and provide that, then I can make my observations and ask further questions if necessary.

I think it is also best that we don't pollute this thread with PF support files and discussions, hence I appreciate if you submit that to the PF thread (found in my sig). Unless OP @roirraW "edor" ehT prefers that the observations are discussed here.
[Google Pixel 6 Pro] snovvman:
Understood and it makes sense. Yes, it was a typo--it should of read "uninstall 03, install 02 but not launch". No further discussion re PF here needed. I will create a support file and post in the PF thread. Thank you!
[Google Pixel 6 Pro] snovvman:
I would think that I do, wince I just created one with PF. Let me see if I can locate it.

Edit: file is attached. All usual disclaimer applies--ymmv, at your own risk, etc. etc.

Edit 2: Thank you @badabing2003--this boot image is for Pixel 6 Pro, July 2023, patch created with Magisk 26102 Canary.
[Google Pixel 6 Pro] badabing2003:
Just to be clear to anyone who would use this,

It's a patch created with Magisk 26102 Canary.
[Google Pixel 6 Pro] Suavie103:
Thank you so much.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Platform-Tools v34.04 is out:

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

https://dl.google.com/android/repository/platform-tools_r34.0.4-windows.zip

(both links lead to that latest version).

Warning: I'd advise waiting for others to report back test results of it.

Edit: Take note, there's no changelog at the site yet:

SDK Platform Tools release notes | Android Studio | Android Developers

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

developer.android.com
[Google Pixel 6 Pro] aimsjahan:
Caution!

Android 14 Beta 4 can NOT be fastboot-flashed on Pixel 6 with v34.04

Had to revert to r33.0.3
[Google Pixel 6 Pro] badabing2003:
Will they ever get it right?
[Google Pixel 6 Pro] Lughnasadh:
Interesting....I've seen someone else who used 34.0.4 to flash A14Beta4 on their Pixel 7 Pro and it worked fine so wondering if the remaining "bug(s)" only affects the Pixel 6 series. Or maybe different OS platforms were used (Windows vs Linus, etc.) and created a different outcome? Or maybe something else...
[Google Pixel 6 Pro] Golf c:
It worked for me also.

Strangely, it did not wipe my data! I'm truly baffled. The -w is still in the flash all bat. file.

Everything working well so far. Wish I would have paid closer attention when I was flashing.
[Google Pixel 6 Pro] badabing2003:
I've seen few cases where people were trying to wipe and the phone was not wiped.

In all cases they were using 34.0.3, perhaps the problem carried over into 34.0.4

I for one will not be testing -w flag in 34.x for obvious reasons.
[Google Pixel 6 Pro] roirraW "edor" ehT:
They actually posted release notes for the broken Platform-Tools v34.0.4 after not too long a time:

SDK Platform Tools release notes | Android Studio | Android Developers

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

developer.android.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
Nearby Share for Windows is now officially available

Nearby Share for Windows makes it easier to share files between Windows PCs and Android devices.

blog.google
[Google Pixel 6 Pro] roirraW "edor" ehT:
[MODULE] [MOD] Universal SafetyNet Fix

(The -STRONG is working for me. Your mileage may vary.)
[Google Pixel 6 Pro] roirraW "edor" ehT:
Platform-Tools v34.0.4 (#2):

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

https://dl.google.com/android/repository/platform-tools_r34.0.4-windows.zip

Zip file is definitely different than the previous release of 34.0.4.

Edit #4: Every single one of the files are different than the ones from the previous release of 34.0.4.

No change to the changelog yet (from what it already said about the first release of 34.0.4).

Edit 5: Version number of ADB and Fastboot still remain the exact same, too:

Edit 6: Slight change in file sizes - and the latest package extracted with a non-2007 (2008 depending on time zone) file date (!). Weird. I extracted both with 7-Zip ("Extract Here"). I confirmed, the files inside the #2 zip, when viewed within 7-Zip, have the newer file date.:
[Google Pixel 6 Pro] Lughnasadh:
May be another version of Platform Tools 34.0.4 coming in soon

platform-tools-34.0.4 - platform/frameworks/base - Git at Google
[Google Pixel 6 Pro] roirraW "edor" ehT:
3 ways unknown tracker alerts on Android help keep you safe

Unknown tracker alerts help keep you and your loved ones safe on Android with automatic alerts and manual scan.

blog.google

"Unknown tracker alerts, which we announced at I/O 2023, are beginning to roll out to Android 6.0+ users this month. Here are three ways this new feature helps keep you safe from unwanted Bluetooth tracking on Android."

...
[Google Pixel 6 Pro] roirraW "edor" ehT:
You can now send entire folders with your Android device thanks to Nearby Share

You can use Nearby Share to transfer entire folders without disturbing their structure

www.androidpolice.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
Interesting.

Google Issue Tracker

issuetracker.google.com
[Google Pixel 6 Pro] Nergal di Cuthah:
Why aren't they increasing the version number if they're updating, makes it harder to help someone if they say they have 34.0.4 and they had updated it when first it arrived and never after because same version number. Bah
[Google Pixel 6 Pro] Lughnasadh:
If you can, make a comment stating this in the issue tracker so it grabs their attention. Two people already have. Maybe it will help.
[Google Pixel 6 Pro] Nergal di Cuthah:
Done
[Google Pixel 6 Pro] roirraW "edor" ehT:
Google's making it easier to scan distant QR codes

Google's auto-zoom for QR codes will make your life easier

www.androidpolice.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
Nice. Google Keep is adding version history, although it only looks like on the computer (for now)

Find version history for notes - Computer - Google Keep Help

You can download a text file of previous versions of your notes or lists to see changes you’ve made over time. This feature is currently rolling out and will launc

support.google.com

^ Not as handy as version history in Google Drive (especially of individual cells in Google Sheets, but Sheets in general - although that could use a lot of improvement, too)
[Google Pixel 6 Pro] Lughnasadh:
Should be getting August update soon...

Android Security Bulletin—August 2023 | Android Open Source Project

source.android.com
[Google Pixel 6 Pro] Lughnasadh:
Links are up
[Google Pixel 6 Pro] snovvman:
Before I apply the July patches, will someone please let me know if Magisk 26015 addressed the issues in 26103? I recall having to patch with 26012 because 13 did not work. I am now on 15 and would like to know if there are problems. Thanks!
[Google Pixel 6 Pro] Lughnasadh:
Canary 26105 is working fine for me, albeit on A14. Canary 26104 fixed the problems encountered with Canary 26103.
[Google Pixel 6 Pro] snovvman:
Thank you, @Lughnasadh!
[Google Pixel 6 Pro] Suavie103:
Anybody has a patched stock August 6 pro boot .img?
[Google Pixel 6 Pro] iwearthebelt:
Here you go
[Google Pixel 6 Pro] Suavie103:
Thank you
[Google Pixel 6 Pro] fillwithjoy1:
Quick question: Does the developer support images work? And what are the drawbacks of using it?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Developer Support images for Pixel | Android Developers

Instructions for downloading and installing Developer Support system images for Pixel devices

developer.android.com
[Google Pixel 6 Pro] fillwithjoy1:
all good, just wanted some first hand experiences of people using it (if there are any)
[Google Pixel 6 Pro] roirraW "edor" ehT:
Android's Nearby Share is becoming as seamless as AirDrop

Sending files with Nearby Share is already fast, but this change will make it even faster

www.androidpolice.com
[Google Pixel 6 Pro] StanWiz:
Thanks for the heads up - tested it , working as designed.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Google Contacts now shows local time and weather

Google Contacts has seen an uptick in new features this year, and it continues today with local time and weather information...

9to5google.com

Interesting...
[Google Pixel 6 Pro] roirraW "edor" ehT:
Woohoo!
[Google Pixel 6 Pro] constantin2003:
Hello can u help me please with finding .cal file for google pixel 7 pro
[Google Pixel 6 Pro] tids2k:
Hi I dont have this device now. But the easiest way to capture the file is through Google Chrome Inspect tool. You can capture the url for the file.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I'm still not enthused about potentially being forced to use eSIMs in the future, as this ease-of-transfer feature doesn't account for if a phone with an eSIM just stops working, since you have to start the transfer process on the existing phone. I'd rather avoid having to deal with the carrier in such a circumstance, unless there's also a possibility to transfer eSIMs on their website, although I doubt if my pre-pay account would implement such a feature as quickly as a regular account.

This is how Android’s eSIM transfer feature will work

The process of transferring eSIMs from your old Android phone to a new one is about to get a lot easier.

www.xda-developers.com
[Google Pixel 6 Pro] Lughnasadh:
Think this is the Beta before it's released to Stable. Thanks for the heads up!

https://twitter.com/i/web/status/1696074538390581590
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thanks! Argh. It gets me every time there's a Beta. :)

You're welcome!
[Google Pixel 6 Pro] biTToe:
Where do we stand on platform tools 34.0.4 vs. 33.0.3?

Is it now fixed?
[Google Pixel 6 Pro] HankMcCoyX:
Do the patch notes indicate that we can patch the factory image on the phone and install from there, bypassing all the steps to download the image on a computer, extract the boot.img, send it to phone, patch it with magisk, send it back to computer etc?
[Google Pixel 6 Pro] roirraW "edor" ehT:
34.0.4 still has quirks, but definitely works in some circumstances. 33.0.3 is safest to use.

That's what I always do, but I stick with Stable.
[Google Pixel 6 Pro] Lughnasadh:
You'll still have to flash the patched image in fastboot on new Magisk (root) installs.
[Google Pixel 6 Pro] HankMcCoyX:
[App] Support patching boot image from ROM zips

Just wondering what this line from the changelog means and why it's a new bullet point of note.