Sorry for the confusion I was able to reach the home screen in offline setup mode. What I was referring to is using the offline trick to unlock the bootloader. Unfortunately I was unable to unlock it even with the offline setup. Sigh I probably have to get an unlocked model if I want to root. Using vzw was the cheapest route for me. This was on a Verizon p6p
I've always bought unlockable phones, but Android has gotten to the point, where most of the things I rooted for are now baked in. The only thing not in there is ad blocking, but by adding dns.adblocking in settings, I don't need root for anything anymore. I think I'm going to enjoy having everything working and not having to fiddle with my phone. Wait, did I really just say that?
Technically it doesnt't, but that OEM Unlocking toggle is almost always locked on a carrier-locked device. As you would expect, for subsidized devices with a payoff balance due.
It was a new one to me, too. Just like you, I had pointed out that achieving carrier unlock is completely separate from bootloader unlock, but several forum members with T-Mobile variants have detailed how they previously on older phones (and I believe since have replicated on the P6P) that they can request carrier unlock (temporary or permanent) directly with T-Mobile, and that it then ungrays the OEM unlock option, and were indeed able to unlock the bootloader. I don't use T-Mobile and I had a factory-unlock model anyway, so I haven't followed 100% closely, but I have read enough of the experiences and it's interesting.
What ad blocking DNS do you use?I've always bought unlockable phones, but Android has gotten to the point, where most of the things I rooted for are now baked in. The only thing not in there is ad blocking, but by adding dns.adblocking in settings, I don't need root for anything anymore. I think I'm going to enjoy having everything working and not having to fiddle with my phone. Wait, did I really just say that?
Yes. There is no AT&T specific version of the firmware.
If they can't toggle the OEM unlock in Developer Options, then they're not going to be able to unlock using fastboot.
You need to run fastboot flashing unlock to enable OEM unlocking in the Developer options.
I can confirm that unlocking the AT&T version, does indeed ungrey the bootloader unlock option in the developer settings. I contacted AT&T to request an unlock a couple days ago, and this morning I got a notification on my phone that it was now unlocked. I didn't have to input an unlock code, it was all done remotely. After that, I could input my Verizon sim along with me using my Esim (that's enrolled with AT&T service), and run a dual sim set up. I checked the developer settings after getting the notification, and found the bootloader unlock option was no longer greyed out. So it appears there is hope for those that wish to unlock their bootloader. They just have to carrier unlock the phone first.
Not sure about AT&T, but you buy a device from VZW, the bootloader is locked forever.I've been buying unlocked phones for years and I can't remember the last time I bought from a carrier. But I can get a 6 Pro 256GB from one of those carriers for $500 through work so I'm thinking I might try.
I guess the other thing I'd ask is if they've clarified if the Google-direct 6 Pro will support mm-wave/UWB 5G?
I didn't. It was easier to just return it and go to Best Buy. No hassle.Sorry if lot sounds like I'm being too specific on this, but did you fully pay off the phone and ask AT&T to unlock it? I'm sure the bootloader is locked at first, but they've always allowed phones to be unblocked and that to the best of my knowledge. And they have to carrier unlock it before you'd be able to bootloader unlock it.
On the offline note, I'm pretty sure there's a way around that offline. In some cases, I bring it was earlier Samsung Galaxy phones, your had to tap a hidden white hotspot area on the instruction screen several times and it would move forward offline. Just FWIW.