yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] roirraW "edor" ehT:
Personally, I would wait then, although I would fully expect to pay more than that for the Pixel 7 Pro. Since the Google Store is directly selling the SIM-unlocked (bootloader unlockable) 128 GB Pixel 6 Pro for $649 (at one point in the process it says $899, but the next step shows it back at $649), and you can get the 512 GB unlocked P6P for $849 direct from the Google Store, I would first determine what size you want. If 128 GB is enough for you, the $640 from your source isn't horrible, but if you need more storage than 128 GB, I think I would hold off until the Pixel 7 Pro even though you will definitely be paying more than $850 for any Pixel 7 Pro.

So I probably didn't make the decision any easier, but... :)

Also, I didn't stop using my Pixel 1 until a few months after it received its last update in December 2019 or so.
[Google Pixel 6 Pro] I7210I:
And the release date of the pixel 7 is right?

and about the p6, is the bugs are fixed with the updates?

thanks
[Google Pixel 6 Pro] roirraW "edor" ehT:
I don't know what the release date of the Pixel 7 is. It is probably either next month or as you said, more likely October/late October. October 19, 2021 was when they had the first-day pre-orders for the Pixel 6. It was a nightmare. Their site couldn't handle the load, but eventually maybe five hours later I was able to pre-order. Got my wife's and my factory unlocked Pixel 6 Pro 512 GB models in late October.

The only noticeable bugs I remember ever having were a slight problem with using gestures with third-party Launcher apps, but it didn't cause me a problem that often and was always recoverable. I know others have had other bugs but I was one of the lucky ones.

I haven't noticed the issue the last less than two days I've had 13 Stable installed but that isn't really long enough to tell if the issue is still around.

Personally, I think Android 13 is much smoother than Android 12, and when I reboot the phone, the home screen loads noticeably faster the first time I unlock it. I've been withholding full judgment one way or another on 13 because it takes time to observe all the overall differences objectively, and sometimes there is also a placebo effect with a new shiny Android version, but my general impression is that Android 13 compared to 12 is like Android 5.11 compared to 5. But honestly not as big a difference as the 5->5.11 changes - just reminiscent of that situation, although Android 5.x was when I was still using non-Google OEM phones.

You're welcome! Good luck with whatever you choose to do.
[Google Pixel 6 Pro] I7210I:
And we said nothing on the competitors (S22 ultra) in front of the pixel 6 pro...

So everything is relayed on rumors about the release dates...

The price sounds good , and you said you was lucky about the 6 pro so that's one thing that might be scary
[Google Pixel 6 Pro] roirraW "edor" ehT:
Well, from what I've seen in this section there were plenty of others who were lucky too. Any one of us can be lucky or unlucky with any phone brand or model.
[Google Pixel 6 Pro] I7210I:
agreed, it might catch you in any brand and device.

overall I think that for that price it's looks good, and who knows what will be the start (problems, prices) of the 7 pro, isn't it?

and to go the S22 ultra is something else
[Google Pixel 6 Pro] Ricardo_G:
i has hear several rumors about an early realease by september, with official ETA for early october... you could wait a little bit, however the price for the P6/P6P will surely down with the new ones on market, si it could be a good time for to buy at reasonable price.
[Google Pixel 6 Pro] LLStarks:
I'd wait. The Pixel 7 looks like it could solve a lot of issues and shortcomings with the Pixel 6.

The Pixel 6 is getting harder to find as Google apparently wants the inventory gone.

If you're in the US, you could get a Pixel 6 Pro for $0 down from T-Mobile on the JOD program and upgrade to a regular Pixel 7 for free (Pro probably $150-$300 down?) when it comes out.
[Google Pixel 6 Pro] I7210I:
So as far as I see, the p7 pro is behind the corner, I'm in Europe till 7 of September, I hope that I will have good news till than...

anyhow, looks like its better to wait than if I understand, also the thing with the inventory is right
[Introductions] Bronxman_JRP:
Hello my name is Justin, im from the US. I also love technology
[Introductions] orb3000:
Hi Justin, welcome to XDA
[Android Apps and Games] ronenfe:
Hi, I've created a new Android app which changes the music volume of the device based on the traveling speed. It can be downloaded from here:

LinkedIn

This link will take you to a page that’s not on LinkedIn

lnkd.in

View attachment 5687801
[Android Apps and Games] ronenfe:
This app is for adjusting the volume, not for warning when going over the speed limit. There are other apps for that. I could add a warning for one top speed only if there is enough demand for such a feature. Second question is not clear.
[Android Apps and Games] junarie:
Thanks, I was looking for just something like this.
[Android Apps and Games] ronenfe:
A new and improved version is out:

AutoVolume (With Ads) - Apps on Google Play

Auto Adjustment of Music Volume Based on Speed

play.google.com
[Google Pixel 6a] TenPercentPower:
Got an unlocked Pixel 6a delivered yesterday from the Google Store. Was planning to root it immediately upon setup but the "OEM Unlock" option in Dev settings is greyed out, saying "Connect to the internet or contact your carrier". I am connected to the internet, have a Visible SIM installed, and am on the most recent Android 13 update available for the 6a. I have tried all of the options, including factory resetting, going through setup without SIM or internet, etc. Google support has been of little to no help.

Pulled the build.prop using adb shell getprop and the value ro.oem_unlocking_supported does not exist.
[Google Pixel 6a] mmead1143:
Same here - same issue
[Google Pixel 6a] seangeezy12:
:( this is super annoying, i wanted to root also! they need to fix this ASAP
[Google Pixel 6a] bobby janow:
Perhaps you can close this redundant thread since you cross posted to this one and it already has over 200 posts.

https://xdaforums.com/t/6a-from-google-cant-unlock-bootloader.4473669/
[Google Pixel 6a] tcat007:
Odd, when I got June update it became available. But I haven't received any update since, just waiting for ota. I think I'll wait rather than sideload, maybe it will stick.
[Google Pixel 6a] ritchea:
Not for me. Just loaded stable 13 via beta; checked the unlock switch; still gray. So, I did the reset (but not the sim-removal-turn off wifi, etc) and still no bootloader unlock. What I haven't done is try the fastboot unlock anyway. It seems it would simply not work. However, trying to sideload the June OTA put my phone into a bootloop (which would have been so easy to fix with an unlocker BL) so not really going to mess around much.
[Google Pixel 6a] benji:
Have you tried factory resetting after updating? That's what worked for me.
[Google Pixel 6a] TenPercentPower:
Yeah, I have, several times, but unfortunately to no avail.
[Google Pixel 6a] mmead1143:
I did the factory reset from the setting app and that did the trick. I had 13 plus the update before I did this.
[Google Pixel 6a] TenPercentPower:
Yeah, for whatever reason that hasn't been working for me.
[Google Pixel 6a] GivIn2It:
Just a guess, maybe go to settings/about phone/regulatory labels, and check your model number. Make sure they didn't mistakenly send you a locked to carrier phone.
[Google Pixel 6a] bobby janow:
Do you know of a list like that? That would be so helpful to so many.
[Google Pixel 6a] tcat007:
I did the sign up for beta, get ota 13, sign out of beta, thing. Got 13 instantly (although takes 45 minutes to install), and unlock bootloader is still available.
[Google Pixel 6a] roirraW "edor" ehT:
What list are you talking about? :)
[Google Pixel 6a] bobby janow:
A list of model numbers and which is Verizon, unlocked, ATT, Google unlocked etc. Things like that so if someone can't unlock the bl they can check their version/model. For instance I bought a BB unlocked and the model is:

GA03715-US

and in Regulatory Labels is shows GX7AS So I'm pretty much at a loss as to which devices are which if it even matters. I just see so many people that still can't unlock the bl even after updates and factory reset that maybe there is a pattern or versions that will not allow it.
[Google Pixel 6a] roirraW "edor" ehT:
@bobby janow You forgot to type a response when you quoted me. :) It just seemed like when you said something about a list that maybe you had posted that in the wrong thread, since I didn't notice anything else in the thread that made sense for that response.

Edit: Oh, you edited it now. Nevermind. :) I understand now.

list of pixel 6a models - Google Search

Although the first search result only lists:

GSMArena only lists three:
[Google Pixel 6a] hammered58:
Just received 6a today, straight outta the box set it up no sim installed checked version, it was 12 , OEM unlock greyed out, did a factory reset , no help, still greyed out, took the ota update , it's was just a newer version of 12, oem still greyed out, factory reset this version and it worked, oem unlock granted
[Google Pixel 6a] arfarfdan:
HEY THIS MIGHT WORK FOR U!​

Was having the same issue, nothing seemed to be working.

I had success finally, though!

Be sure you realize your phone will be wiped, etc.

Airplane Mode & No SIM inserted.

Remove All Accounts From Phone (to prevent issues with locks, etc)

Make sure you can put the phone in fastboot & adb modes

I put the phone in various modes to test, and ended up doing this:

[ REBOOT PHONE INTO SIDELOAD MODE VIA: ]

$ adb reboot sideload

Once the phone is ready to accept the side load OTA package, push that happy bullsh1t right on down the USB cable to the phone via:

adb sideload ~/MagicalGarbageDump/bluejay-ota-sd2a.220601.003-ddfde1f7.zip

From the OTA file downloaded directly from Google at THIS SITE. It's this one:

12.1.0 (SD2A.220601.003, Jun 2022)	Link	ddfde1f7edcdbb2b3de41d24f6c3f31587f836f387cab4cc6d16adee32bcab8a

After downloading and flashing that OTA, I had to "reset to factory settings" about two more times, seemingly randomly, and then it worked!

I made sure to have:

- NO SIM CARD IN THE PHONE.

- NO WIRELESS NETWORKS CONNECTED.

I am kind of annoyed it seemingly randomly decided to work, but also grateful that it finally unfzcked itself.
[Google Pixel 6a] varoyzf:
Also no luck over here. I bought my Pixel 6a directly from Google store as a "non locked device". It was sent from France Google store to Spain.

I'm in the 5th September security update under Android 13.

Tried all the tricks posted before: factory reset from settings and from recovery, sideload OTA, tried with sim and without it... No luck, OEM unlock still greyed out.

I wrote to Google about it. They asked me for the imei. After all, no help received from them to solve it.

Still waiting for "magically" disappear the greyed option...

View attachment 5715241
[Google Pixel 6a] GivIn2It:
l would send it back and get the p6 pro. For a few dollars more you get a better phone and no unlock issues.
[Google Pixel 6a] oidasldas:
Hi folks. Jumping into the thread here as well with some info.

Basic context: Carrier unlocked Pixel 6a phone purchased in the US. Carrier unlock status confirmed by Google via IMEI check and by swapping out SIM cards in device. Multiple SIMs work fine. Have had multiple conversations with Google, no help at all. Been told it is a "software issue", to wait for the next update, but that next software update might** not solve it. Tons of circular logic while talking with Google reps, but I digress... I have updated to the September security release, Android 13, done factory resets from the OS, and followed other instructions listed. EOM Unlocking is still greyed out.

Without OEM Unlocking available, phone is basically no useless for me.

***Here is the potentially interesting bit...I seems like there are errors during the factory reset process.

While trying to perform a factory reset from "Android Recovery" screen, I get the following output:

--Wiping data

ERROR: recovery: [libfs_mgr] Unable to enable ext4 verity on /dev/block/platform/14700000.ufs/by-name/metadata because /system/bin/tune2fs is missing

Formatting /data...

Formatting /metadata...

Wiping Titan M...

Wiping key...

ERROR: recovery: gto_eseha1 SecureElement:t1_recv_window_append free 261

ERROR: recovery: gto_eseha1 SecureElement:t1_recv_window_append free 261

ERROR: recovery: gto_eseha1 SecureElement:t1_recv_window_append free 261

ERROR: recovery: gto_eseha1 SecureElement:t1_recv_window_append free 261

Data wipe complete

Is it possible that these errors are resulting in EOM Unlocking not being available?

Don't want to sound conspiratorial but after multiple conversations with Google reps, it sounds like they have a sense of what is wrong but don't want to share for some reason.
[Google Pixel 6a] :
Looks like the os is corrupt. Tune2fs missing possibly means either faulty flash etorage or they didn't image it correctly from the start. Either way, replace it
[Google Pixel 6a] oidasldas:
@n0lan Thanks for your reply.

I am running Build Number TP1A.220905.004.A2, which I downloaded and sideloaded directly from the Google Developer site.

Specifically referring to here:

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

developers.google.com

13.0.0 (TP1A.220905.004.A2, Sep 2022)

I also confirmed that the build matches the SHA-256 Checksum posted on Google's site.

I also tried downgrade to the previous build but that was blocked. I can't downgrade and the current build is potentially messed up. Google also prevents rollback to Android 12...

ERROR: recovery: Current SPL: 2022-09-05 Target SPL: 2022-08-05 this is considered a downgrade

ERROR: recovery: Denying OTA because it's SPL downgrade

EDIT:

To be clear, were you suggesting replacing the physical device or trying to install a different build number? If there is an issue with the build overall then getting a new device will the same build loaded would yield the same issue no? @n0lan
[Google Pixel 6a] oidasldas:
FYI, sounding more and more like needing to wait for yet another build.......and hoping the change was set. Are people using build TP1A.220905.004.A2 and are able to do EOM Unlocking?

Lock and unlock the bootloader | Android Open Source Project

source.android.com

The ro.oem_unlock_supported property should be set at build time based on whether the device supports flashing unlock.

If the device suppports flashing unlock, set ro.oem_unlock_supported to 1.

If the device doesn't support flashing unlock, set ro.oem_unlock_supported to 0.

If the device supports flashing unlock, then the bootloader should indicate the lock status by setting the kernel command line variable androidboot.flash.locked to 1 if locked or to 0 if unlocked. This variable must be set in bootconfig instead of in the kernel command line in Android 12.

For devices that support dm-verity, use ro.boot.verifiedbootstate to set the value of ro.boot.flash.locked to 0; this unlocks the bootloader if the verified boot state is orange.
[Google Pixel 6a] batp:
Navigate to Settings > About phone

Scroll down to “Build number” and tap it 7 times or until you become a developer

Navigate to Settings > System > Developer options > OEM Unlocking and tap to enable.

🚨If OEM unlocking is greyed out on your device:

Connect the Pixel 6a to the internet

Navigate to Settings > System > System update

Install first critical system update and reboot.

Return to stage 1 of OEM Unlocking. If greyed out, proceed to #5.

Remove sim card. Connect to WiFi.

Navigate to Settings > System > Reset options

Erase all data (factory reset)

Once reset, go through setup and connect to WiFi.

Reboot device.

Return to Step 1 of OEM Unlocking.

Source: https://www.bayareatechpros.com/pixel6a-graphene/
[Google Pixel 6a] oidasldas:
@batp Thanks for your message.

I have just redone steps 1 through 3. OEM Unlocking is still greyed out.

I then continued to the next step of steps listed as 1 through 10.

When I get to step number 3 ("Install first critical system update and reboot."), the screen says "Your system is up to date. Android version : 13, Android security update: September 5, 2022. Last successful check for update : XXXXX

I then performed all of the others steps listed. OEM Unlocking is still greyed out.
[Google Pixel 6a] oidasldas:
Friends....it looks like I am hosed unless the powers that be aka Google (who actually apparently own my device despite paying a pretty penny) decide otherwise.

After doing the reset steps over and over. Decided to take a look at overall settings.

Connected to device, enabled USB debugging, then using adb:

""""

./adb shell getprop | grep oem_unlock

[sys.oem_unlock_allowed]: [0]

"""

I would be grateful if anyone from the thread or wider community could please see if they can reproduce that with build 13.0.0 (TP1A.220905.004.A2, Sep 2022) listed in the link above.
[Google Pixel 6a] :
The last thing I'll suggest is factory reset through recovery a few times
[Google Pixel 6a] oidasldas:
@n0lan Thanks for the suggestion on factory reset. Per above I get an error message while trying to do the factor reset from the Recover Screen:

"

--Wiping data

ERROR: recovery: [libfs_mgr] Unable to enable ext4 verity on /dev/block/platform/14700000.ufs/by-name/metadata because /system/bin/tune2fs is missing

Formatting /data...

Formatting /metadata...

Wiping Titan M...

Wiping key...

ERROR: recovery: gto_eseha1 SecureElement:t1_recv_window_append free 261

ERROR: recovery: gto_eseha1 SecureElement:t1_recv_window_append free 261

ERROR: recovery: gto_eseha1 SecureElement:t1_recv_window_append free 261

ERROR: recovery: gto_eseha1 SecureElement:t1_recv_window_append free 261

Data wipe complete"

Not convinced that a total wipe is being done despite "Data wipe complete".
[Google Pixel 6a] :
Dunno if this helps..sorry if doesnt

https://xdaforums.com/t/guide-root-pixel-6-with-magisk-android-13.4388733/post-86342049
[Google Pixel 6a] batp:
I suggest you send it back to Google, who will repair it under warranty.

My experience with that is that I bricked a pixel 3a I purchased on ebay. It was still under 2 year store warranty and they fixed it for free. I had it back in a week IIRC.
[Google Pixel 6a] ypnos42:
On a positive note, these instructions worked for me!

I got my Pixel 6a a week ago. Now did the steps with update and factory reset. OEM unlock was grayed out until step 9 + an additional reboot. Oddly enough, the first reboot was not enough.
[Google Pixel 6a] Syntaxerror_s:
To unlock you need the ota June 2022 firmware
[Google Pixel 6a] TechX1991:
Remove your google account, remove your SIM, do the OTA, then factory reset.

Go through setup without connecting to wifi, do not put your sim in yet

When setup is complete, connect to wifi, wait a few minutes, enable Dev Options and OEM Unlock should be possible to enable and you can put your SIM back in

Having a service provider sim in the device seems to screw it up and make it think its a sim locked device
[Google Pixel 6a] smgoller:
This worked for me as well. Worked after step 8, I forgot to reboot before going into developer mode.
[Google Pixel 6a] bobby janow:
Possibly but when I first got the phone it was not unlockable. Then the next day the update came and I factory reset and unlock was available. But I had my Verizon sim in the whole time along with an activated eSim. So perhaps other providers will block it but Verizon did not on my unlocked version bought from BB.
[Google Pixel 6a] TechX1991:
So far, an AT&T and Verizon SIM have kept OEM Unlock disabled after a factory reset for me, but that's not to say all of them will do that.
[Google Pixel 6a] :
I use att and am able to toggle it. I don't think its the carrier locking it. Google may be slacking for some reason
[Google Pixel 6a] Lada333:
What number are we supposed to look for here?

I just got my 6a yesterday, from Google, allegedly unlocked, but OEM unlocking option is greyed out for me as well.

I went ahead and checked the regulatory labels, says my model number is G1AZG.
[Google Pixel 6a] roirraW "edor" ehT:
You seem to have found your model number fine, so I'm not clear on if you still have a question relating to "What number are we supposed to look for here?".

Try removing the SIM card, factory reset, and connect to Wi-Fi, then check if you can enable OEM unlocking.
[Google Pixel 6a] Lada333:
I'm unsure what this number means. I assume you can tell by the model number whether or not your device is carrier locked?
[Google Pixel 6a] roirraW "edor" ehT:
I see. I simply used a Google Search. Several search hits say:

Google PIXEL 6a 5G (Charcoal) G1AZG 128GB + 6GB RAM - GSM Unlocked (No CDMA)

Google Pixel 6A 5G 128GB/6GB RAM (G1AZG) GSM Unlocked International Version

So, carrier unlocked, but GSM only - no CDMA.
[Google Pixel 6a] bobby janow:
Since there really isn't a complete list of which devices are which I guess you can start out telling us where you bought the device from and what you thought you purchased. I bought an unlocked version from Best Buy and the regulatory label says Model GX7AS. That's different from the model number on the box which is GA03715-US. I updated day 1, factory reset with a Verizon sim in it, both physical and eSim and the OEM switch became active.
[Google Pixel 6a] Lada333:
I bought my 6a from the Google Store. I live in Hungary, unfortunately Google doesn't ship to Hungary, so I had a friend of mine ship the device to me from Germany.

I booted up the phone, put my Hungarian Telekom SIM card in, set up everything normally. There was an update with a size of about 50 MB. Even after installing that + rebooting, in developer settings OEM unlocking is still greyed out, saying "Connect to the internet or contact your carrier." The second half of this message got me worried a bit - thinking it can only be unlocked with a German SIM? (That's probably nonsense though).

I'm not super keen on rooting yet. I want to use the phone for a few weeks/months, just to see if everything is in order. Realistically, I'd only use Magisk to be able to use Advanced Charging Controller.

--

Apologies if this is super off-topic, but I've just noticed that there is a system update available that would upgrade me to Android 13. I've read about some nasty stuff about it (especially how the new bootloader (?) makes it basically impossible to root/unlock), so I'd rather postpone it for a while. Is my phone going to automatically download and install this update? If so, is there any way for me to prevent that from happening?
[Google Pixel 6a] bobby janow:
First thing you need to do is factory reset after the 50 mb update. That will allow OEM unlock. After that upgrade to A13 it's a needed update. Don't worry about root yet.
[Google Pixel 6a] CmdrCrichton:
That's exactly what I did and OEM unlocking was there. A little bummed I upgraded to A13 though because I didn't realize that meant no going backwards so now I have to wait for custom rooms that are A13.
[Google Pixel 6a] bobby janow:
But at least you have a FPR that works. Lol Maybe a custom kernel to get started? They kinda pulled the rug out on that one but they did say there was a major security flaw in the A12 bootloader. I'm not rooted so I'm really not sure if there is anything you can do at this point other than what you suggest by waiting.
[Google Pixel 6a] Lada333:
Implying the fingerprint reader doesn't work on A12? Haven't had issues with it since I've got my device.

Yeah, I'm sure there totally is a major security flaw, and they didn't just do this as another step to make modding more difficult. :D
[Google Pixel 6a] bobby janow:
Some, like yourself, never had problems with the FPR. However, many did until the September update or the QPR1 beta. Personally I went from about 30% success to now close to 100%. That is pretty common for those, like me, who were saddled with a faulty unlock mechanism.

As for modding, I'm not a conspiracy theorist though there are some in your camp saying Google is playing games. I don't mod these days so I was just reporting what has been documented.