yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] roirraW "edor" ehT:
And @Lughnasadh's suggestion of the USB driver?

But yeah, that's probably the problem right there. Don't use pre-packaged ADB/Fastboot from any source other than Google's official from here:

Platform Tools has been updated slightly to v33.0.3:

Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
[Google Pixel 6 Pro] Taker18:
yu

yup, its just the folder name, everything which was in the folder was replaced with the platform tools ..
[Google Pixel 6 Pro] roirraW "edor" ehT:
What about the USB driver?
[Google Pixel 6 Pro] Lughnasadh:
If you have all the tools installed, the files in the right places, etc., then try a different cable (preferably A to C) and use USB 2.0 port.

And, are you in fastboot and not fastbootd? Did you do adb reboot bootloader? You should be in fastboot.
[Google Pixel 6 Pro] Taker18:
I've tried all things:

have put the platform-tools on my desktop

google driver package also in the platform-tools

changes usb cable

other slot....

same again, waiting for device.

i will try tomorrow again ..

thank you guys!
[Google Pixel 6 Pro] roirraW "edor" ehT:
Okay, just so you know, you don't install USB drivers by putting them in the same folder as the platform-tools. See the page @Lughnasadh directed you to for instructions to install, and make sure your phone is in bootloader mode (adb reboot bootloader) when you install the USB driver.

Good luck tomorrow! Let us know how it goes.
[Google Pixel 6 Pro] Lughnasadh:
I think we call all use a break right now 🙃
[Google Pixel 6 Pro] CRXed:
Before trying to flash anything at all, just type when you are booted into fastboot

fastboot devices

and see if a serial number comes back.

If not, the device is not connected and it's no use to try anything else.
[Google Pixel 6 Pro] caitsith810:
I figured I'd ask this question here instead of making a new thread, but does anyone have any LDAC issues at 990kbps on 13? The June update on 12.1 helped a lot with the stuttering and intermittent disconnections with my Sony WF1000XM4s, but on 13, it still has issues for me. I don't know if its an issue with my earbuds or with the phone, but it never stuttered on my OnePlus 8 Pro.
[Google Pixel 6 Pro] Taker18:
Got this message now:

Did I forget something?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hopefully, someone else can chime in about this. I listen to my music but I haven't paid particular attention other than knowing I haven't had any issues, but at what kbps, I'm not sure.

Do you actually have "bootloader-raven-slider-1.2-8739948.img" in the same folder with adb and fastboot? Also, on a Mac do you have to put a "./" in front of "bootloader-raven-slider-1.2-8739948.img"?

Like:

./fastboot flash bootloader --slot all ./bootloader-raven-slider-1.2-8739948.img

?

I'm not very experienced with anything but Windows, but that seems like a possibility to me.
[Google Pixel 6 Pro] Taker18:
domenic@MBPvonDomenic2 platform-tools % ./fastboot flash bootloader --slot all ./bootloader-raven-slider-1.2-8739948.img

Sending 'bootloader_a' (11554 KB) OKAY [ 0.315s]

Writing 'bootloader_a' FAILED (remote: 'command (flash:) is not allowed when locked')

fastboot: error: Command failed
[Google Pixel 6 Pro] Nergal di Cuthah:
Is your bootloader unlocked ?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Your bootloader is locked? If your bootloader is locked, then don't worry about any of this.

Are you wanting to unlock your bootloader? Do you know if your particular Pixel 6 Pro is able to have its bootloader unlocked? Note that unlocking the bootloader will completely wipe/erase your user data. All your apps, your app data, all your settings, and every file you have on the internal storage will be wiped. There's no way around that if you unlock the bootloader so be cautious.

The simple thing to do is to just not worry about it, and leave things alone, unless you are determined to root your phone. The next time you receive an OTA update (either September 5th, 2022 if it comes when it normally comes, or later, if not), it'll update the bootloader of the other slot.

It's not worth unlocking the bootloader *only* to do this. If anything, it's a greater risk to unlock the bootloader at this point, unless as I said, you're wanting to do other things like root the phone.
[Google Pixel 6 Pro] Taker18:
nope, still locked :O

when I unlock my boot loader, can I still use any apps, even banking apps normal ?

or does this not effect any of this?
[Google Pixel 6 Pro] roirraW "edor" ehT:
First, to be completely clear with you. When you unlock your bootloader, your phone will be wiped completely clean, as if you just bought the phone. Everything will be gone, and anything that you don't make sure is backed up one way or another will be completely gone.

Unlocking the bootloader, alone, doesn't normally affect apps. Rooting affects apps, but there are ways around it including with banking apps, although there will remain a very select few banking apps that still detect root regardless, so as I said, be very, very cautious with this decision.

I can't stress this enough, I want to make sure you know what you're doing.
[Google Pixel 6 Pro] Taker18:
okay, I now trying to unlock the bootloader. be right back. after the boot loader is unlocked, can I proceed with the /fastboot flash bootloader --slot all ./bootloader-raven-slider-1.2-8739948.img command ? or are there any special steps after unlocking ?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Can you tell me that you're fully prepared to lose everything that's on your phone? Or that you have fully backed up everything you want to keep? I'm not clear on if you get this, and I want to be cautious with you because we have some failed communication several times already. I'm not trying to disrespect you, I just want to be sure that you're prepared for this.

You haven't answered that you already know this or understand this consequence. Also, besides unlocking the bootloader, if you root the phone, you'll have to manually update the phone every time you want the latest update, which is commonly every month.
[Google Pixel 6 Pro] Nergal di Cuthah:
Do you plan on rooting there's no need to unlock bootloader (or flash the 13 bootloader) if you don't
[Google Pixel 6 Pro] Taker18:
yes, I am. totally.
[Google Pixel 6 Pro] Taker18:
and yes, after unlocking everything, and set uo again. I would like to root ..
[Google Pixel 6 Pro] roirraW "edor" ehT:
Then yes, once you unlock the bootloader, you can flash the bootloader and everything, just like the last time you tried to that failed.
[Google Pixel 6 Pro] Lughnasadh:
If you're on A13 on 1 slot you can just sideload the OTA and it will put it on the other slot as well, so you don't have to unlock your bootloader if you don't want to. Unlocking the bootloader will make you fail the safety checks, e.g. Play Integrity API and SafetyNet Attestation API. Ironically, one way to get around some apps not working because your bootloader is unlocked and failing checks is to root. Of course, then more apps might not work because you're rooted but then there are ways around this as well with mods that are available. It's a whole thing... 🤪

The point is, you don't have to unlock your bootloader if you want to install the A13 bootloader to both slots. Sideloading the OTA will do that and you can do that with your bootloader locked. I would advise, though, to at least enable the toggle for OEM unlocking in Developer Options.

EDIT: I see about 6 additional posts as I was writing this, lol.
[Google Pixel 6 Pro] Taker18:
hmm, okay. and where do I need to put the raven.ota.zip to side load it?
[Google Pixel 6 Pro] Lughnasadh:
If you're new to this, I think it would be best if you go through this article/video. It basically gives you everything you need to know, including what tools/flashing environment, etc., you need set up. Or if you want you can go through the guides in this forum. But not knowing what "tools" you have installed, etc., I'll just give you this. Others may just hop in and just tell you but for beginners I think this is a pretty good guide.

Of course, use up-to-date files.

Android Basics: How to sideload OTA updates on your Google Pixel [Video]

We show you how to sideload OTA updates on your Google Pixel on Windows and Mac in our step-by-step Android Basics guide and tutorial.

9to5google.com
[Google Pixel 6 Pro] Taker18:
what exactly means:

error: recovery: footer is wrong

error: recover: signature verification failed

error:

recovery error: 21

Got it working now, and phone is up after side loading it.
[Google Pixel 6 Pro] roirraW "edor" ehT:
First, unfortunately, I don't know any information that can help you, but hopefully someone does.

I know this doesn't help now, but for what it's worth, I use Authy instead of Google Authenticator. Authy has encrypted cloud backups you can have it perform automatically if you want, which I have a separate password for, and plus they even have a Windows client for Authy, so I can run Authy at my convenience on any computer. I'm lucky enough to made the switch before I had many 2FA-enabled accounts, but now of course I probably have 30-40, and it's certainly harder to switch 2FA apps when you're dealing with that many.

Also, in the meantime, several 2FA apps have added their own cloud backup capability. I was under the impression that Google Authenticator had by now, but since I don't use it anymore, I could be mistaken.

I know the idea of cloud backups for a 2FA app may seem counter-intuitive, but it's still better security than not using 2FA, while being much more convenient for getting new phones, or using 2FA from any of multiple devices of my choice.
[Google Pixel 6 Pro] card13:
@roirraW "edor" ehT Understood, and to show respect for OP I will move my testing of A12 on A13 Bootloader w/changing webview convo to the other Thread that is more suited for that test.
[Google Pixel 6 Pro] User848:
WiFi pairing stopped working with latest version https://stackoverflow.com/questions...-wi-fi-this-system-does-not-meet-requirements
[Google Pixel 6 Pro] Spookymyo:
I sent it in and Google accepted it. Just came back today and there was a card in it with the repair details. It was an eFuse. So it's apparently a risk to manually flash 13 if you do it wrong and trip the eFuse.

I sent it in with Android 13 and it came back 12. So there's a way to go back to 12. And it was my actual phone because I verified the serial number and it has my same screen protector on it.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thanks for letting us know. Glad you got it fixed.

For future reference, if anyone's curious where this started (TL;DR black screen).
[Google Pixel 6 Pro] Lughnasadh:
So it sounds like when you were getting bootloops it did revert to the other slot with A12 on it.

Yep, flash the A13 bootloader to both slots before you pass go or you might not collect $200 and end up in jail 🙃

Glad you got it back and everything went well with the return 👍
[Google Pixel 6 Pro] Lughnasadh:
FYI: Since this topic has been mentioned a handful or so of times in this thread I thought I would just post this here. Regarding TWRP, bigbiff posted this in a Pixel 4 XL thread. Whether they even plan for a TWRP for the Pixel 6 series, I have no idea. They are soon planning to release TWRP support for Android 12.1 for the Pixel 4 XL so it will be interesting to see what other Pixels they give A12.1 support to (i.e. Pixel 6 series). Anyway, this may give a indication of a time frame if it ever comes to be...

"It looks like we will have to wait for a13 support since google has updated the kernel modules extensively"--bigbiff
[Google Pixel 6 Pro] Lughnasadh:
FYI: Even though Android Flash Tool does not flash the whole image to both slots, they have added an option to flash the A13 bootloader to the inactive slot. This may be the easiest option to use when updating to A13 from A12.

Just to be clear, when updating to A13 from A12 a prompt will show up asking whether you want to also flash the bootloader to the inactive slot as well. It doesn't show up in the regular tick boxes.

View attachment 5696871
[Google Pixel 6 Pro] roirraW "edor" ehT:
I think this is the first mention of Android 13 QPR1 Beta at https://www.google.com/android/beta:

(TL;DR: Beta 1 coming next month/September)
[Google Pixel 6 Pro] NonStickAtom785:
So with a currently bricked Pixel 6 there’s no way to flash with Fastboot or ADB. Only EDL. That means if the device is rebooting/swapping slots every few seconds(?), then we need to write a shell script to halt the byte code sending before the device shuts off at whatever interval it may. There was talk of using a different processors EDL tools to interface with the pixel 6 but to be completely honest it was extremely difficult to follow due to their language limitations. But it’s still very interesting none the less.

Also if we can use libUSB or WebUSB to slave the device we should be able to get some functionality…
[Google Pixel 6 Pro] Taker18:
Do you guys think we can go back to Beta 4.1 to solve the Battery Drain Issue till Google got a fix?
[Google Pixel 6 Pro] roirraW "edor" ehT:
The only battery drain issues I've heard of were caused by some apps (such as some by Samsung) which need to be updated to support Android 13 better. Beta 4.1 would likely have the exact same issue.

I haven't had any battery issues on Android 13 Stable.
[Google Pixel 6 Pro] Zaxx32:
Hmmm...This look doable? https://xdaforums.com/t/mod-xposed-...t-for-downgrading-apps-on-android-13.4485153/
[Google Pixel 6 Pro] roirraW "edor" ehT:
What are you asking exactly? Doable for what?
[Google Pixel 6 Pro] Zaxx32:
Disregard...I misread that topic...d'oh! :rolleyes:
[Google Pixel 6 Pro] Lughnasadh:
Slight change to the A13 QPR Beta Program. Seems they may be trying to avoid running the A13 QPR Beta Program alongside the A14 Beta Program.

Android 14 Beta likely starts April 2023 as Android 13 QPR period shortened

Android 13 QPR1 beta starts in Sept., with Google getting ready by updating the Beta Program with Android 14 details, like when it starts...

9to5google.com
[Google Pixel 6 Pro] Lughnasadh:
Wow. (with caveats). Wonder how well they run 🤔

https://twitter.com/i/web/status/1564360254216962054
[Google Pixel 6 Pro] LLStarks:
Google is really bending over backwards to make the best of a bad situation. I imagine dev will still be a little annoyed if they need to test something that was patch specific and can no longer roll back to it.

Cutting QPR3 is an interesting choice but probably the right one. QPR2 will still overlap with the developer previews, but nobody will ever confuse those and don't share an enrollment. Unfortunately, this might mean that firmware could effectively freeze by March or be included in future OTAs without sufficient testing.

For the Pixel 7, this could bite them in the ass if it has the same problems as the Pixel 6 did at launch.
[Google Pixel 6 Pro] Taker18:
so this means we can go back to this special Android 12?

Anyone has tried it? Any Problems ?
[Google Pixel 6 Pro] bush911:
I am going to try this to see whether the DRM issue on A12 OS plus A13 buil still there
[Google Pixel 6 Pro] Lughnasadh:
Let us know how it goes 👍
[Google Pixel 6 Pro] bush911:
Flashed over Android 12 with A13 Bootloader(I previously updated to A13 then force back to A12).

So far so good, just like the July image.

Root OK

Chrome is OK, previous my chrome keeps working for no more than 5 minutes due to DRM.

Flash will erase all user data.

just finished setup, don't install other APPs yet

First boot, we got apa_corrections and app_dictation_formatting notifications. I have never seen them before.

View attachment 5700129View attachment 5700131
[Google Pixel 6 Pro] whatsisnametake2:
interesting. so this developer image is basically the last android 12 build but modified by google to be compatible with 13 bootloader?
[Google Pixel 6 Pro] bush911:
Yes, and it contains a most updated Bootloader as well. It is obvious that Google at first forgot all Developers
[Google Pixel 6 Pro] whatsisnametake2:
I wonder if that is to do with making this build compatible with 13 bootloader
[Google Pixel 6 Pro] Grifello:
than the bootloader (bootloader-raven-slider-1.2-8831283.img) in the Developer Support images is compatible with both 12 and 13 versions?
[Google Pixel 6 Pro] roirraW "edor" ehT:
No idea. It's definitely compatible with the rest of the 12 image it comes with. Since the file is presumably a different file than Stable 13's "bootloader-raven-slider-1.2-8739948" since the filename is different, who knows? Doesn't really matter though, as there shouldn't be any advantage of running 13 with this 12 Developer Support image's bootloader rather than just running Stable 13 with Stable 13's proper bootloader.

Its quasi-main purpose is to be able to let you still run Android 12 while working correctly since Stable 13's bootloader causes Stable Android 12 to not work correctly.
[Google Pixel 6 Pro] Grifello:
Pefect explanation. Thank u very much
[Google Pixel 6 Pro] Taker18:
May I can ask which Google Play System Update you guys have ? Mine is still July 1

But many users on Android Hilfe.de have installed August 1 System Update.

May somebody can check?
[Google Pixel 6 Pro] Nergal di Cuthah:
July
[Google Pixel 6 Pro] roirraW "edor" ehT:
July 1, 2022 here too. I do see that clicking on mine, as expected, does check for updates but it doesn't show any update available for me.

I really don't concern myself much with these things, though. They'll auto-update when necessary.
[Google Pixel 6 Pro] Nergal di Cuthah:
For a while it didn't go into the update screen, but updating playstore fixed that. But it still stayed in july.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yep, I know, but thank you. The Play Store update must've happened automatically for me, - whereas some users were manually updating the Play Store to fix the ability to check for Play Services updates. There's nothing wrong with that - just making the point that the auto-update happened without my manual intervention.

Ever since I got the phone it was common that I wasn't on the very latest Play Services update that was available, but I've never had any reason to manually update, but it has automatically updated from time to time.
[Google Pixel 6 Pro] Nergal di Cuthah:
Lol that part of the reply was more aimed at the general audience who may have missed that. Sorry i phrased it with you as the respondent, i definitely know you're in the know :)
[Google Pixel 6 Pro] roirraW "edor" ehT:
LOL! No sweat. I'm glad my confusion had a good reason!
[Google Pixel 6 Pro] Lughnasadh:
Looks like they finally updated the "Updating Pixel 6, Pixel 6 Pro, and Pixel 6a devices to Android 13 for the first time" section on the download page to include the correct command for Option 2 (adb reboot bootloader rather than adb reboot fastboot).
[Google Pixel 6 Pro] Nergal di Cuthah:
I tell you they don't know what they did so they're (badly) following this thread (not my actual belief/ a joke on alphabet's girth and ability)
[Google Pixel 6 Pro] DanielF50:
I didn't think this deserved a new thread, but thought it was interesting enough to post in here as wasn't sure where else to post and is semi-related to general updates I suppose? (but could possibly just be anecdotal).

I updated to A13 from A12.1 when it came out (via OTA) but my phones battery life was a noticeably worse so I wiped and flashed the A13 factory image via Fastboot (flash-all.bat with -w tags still in-place) but after running through setup with no restore from Google One (reinstalled apps with SwiftBackup, but did no SMS/dialer/app data restores), my battery life was so much worse than before, with my battery dropping to ~40% in 5 hours off charge with very, very light usage.

While attempting to look into what was causing this huge battery drain (apparently nothing according to Android battery stats), I noticed that every single time I rebooted the phone, the permissions and battery optimisation for each app was reset (with no modules/root). I made a couple of changes to see if I could stabilise battery usage (including installing Kiri kernel + CleanState app with power saving mode set to the highest), but nothing helped. I've seen this issue before with A12 and A12.1, but it's never seemed to affect the battery usage, only permissions, so I never really figured out what was causing it.

Yesterday, I gave up and completely reset, went back to A12.1 (with A13 bootloader in-place and --force added infront of "update raven.zip" flash-all.bat) and after initial setup the phone worked perfectly, with battery drain being minimal. Overnight, I let the phone update to A13 via OTA again, and battery usage today seems to be much lower than before I initially wiped.

TLDR; I found my battery life and Android experience as a whole was better after a fresh install of A12.1 (minus bootloader), setting up the phone completely, and then taking the A13 OTA.

PS. Whenever I reset my phone, I always make sure to turn off the persistent notification for USB debugging because I always find myself accidentally tapping it instead of USB connection choice, but after flashing A13 via fastboot, I was unable to hide this notification ("system notifications cannot be hidden"), though A12 allowed me to hide this notification (and so did A13 installed via OTA). I left this notification un-hidden before allowing the phone to take the OTA to A13 overnight, and as per the below screenshots, I was still able to hide system notifications on A13, which is weird - I'm wondering if this is a bug, or if it is expected behaviour and that my fresh A13 install became corrupt somehow (or could be related to the permissions thing). Just another observation, might help someone 🤷‍♀️
[Google Pixel 6 Pro] Ghisy:
Since today is Labor Day in the US, I guess we're not getting the September patch today? Tomorrow then?
[Google Pixel 6 Pro] Lughnasadh:
Likely tomorrow, if history holds.
[Google Pixel 6 Pro] roirraW "edor" ehT:
September 2022 factory image is available:

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

developers.google.com

13.0.0 (TP1A.220905.004, Sep 2022)	Flash	Link	4dba4ced0ea829e3d334dee55d8b15daa4cd1b57848417a8787d68a0b6ce3793
[Google Pixel 6 Pro] roirraW "edor" ehT:
Pixel Update Bulletins | Android Open Source Project

source.android.com

Bulletin	Languages	Published date	Security patch level
September 2022	Coming soon	September 6, 2022	2022-09-05
[Google Pixel 6 Pro] card13:
I've been wondering this since the first A13 build. The flash-all script can be modified w/"fastboot flash --slot all" for the Bootloader and Radio. Is there a way to modify "fastboot update" to update both slots or is that limited to 1 slot?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Short answer No.

Slot All doesn't work with the update.zip portion, at least on the Pixel 6/Pro/a - I believe it may still work on older Pixels but I don't have first hand experience with that. You can modify the script switch slots, reboot into bootloader, wait for the computer to detect the phone again, then flash the update.zip to the new slot if you wanted.

Or you could just run flash-all.bat the current slot, then manually change slots, reboot into the new slot's bootloader, then flash-all again. <- What I did.

There's no particular advantage to flashing the full update.zip to both slots. The A13 bootloader being flashed to both slots is the only truly important thing, and this should be done before doing anything else. This is a one-time thing, and you don't have to do this every month.
[Google Pixel 6 Pro] DanielF50:
Changes in this month's build - quoted directly from the Google Pixel Community post (as couldn't see them anywhere).

Am I missing something though? I thought September was meant to be a feature drop update?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thanks!

No. There should be a new Beta sometime this month, which would be QPR1 Beta 1. I'll have a separate thread for that, or will maybe revive my Beta thread.
[Google Pixel 6 Pro] michaelrager:
Everything works for me up until step 5 OEM unlocking is greyed out and I cannot select it. Any ideas? Thank you very much in advance!