yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Sometimes there are updated releases that deal with carrier specific issues. Look over the last few months and you'll see releases for: Telus, Rogers, Fi, O2/UK, T-Mobile....etc..etc.

As to your other question. True. You couldn't/can't flash them with a locked bootloader. However, Google makes them for folks like me, and many others, that purchased the unlockable version of the phone. Carriers are clamping down on selling phones with bootloader unlock capabilities, to decrease return/warranty issues because some folks don't do enough research before they attempt unlocking their device, then want a replacement/refund when they brick it.

I agree with you in that the buyer should have the option to choose if they want to unlock the bootloader, however, that's likely never going to happen. Look at Apple and Sammy in the US anymore. It's darn near impossible to unlock either one of them! At least Google still makes versions that you can purchase if you want to unlock them. And there ya go :cool:
[Google Pixel 2 XL Guides, News, & Discussion] slogar25:
But you can download the full ota and sideload it through recovery as long as the version sideloaded is newer or equal to currently installed
[Google Pixel 2 XL Guides, News, & Discussion] bobby janow:
I know a lot of people think that it's because of replacement / refunds that the bl is locked. And I believe there is something to that. However, how many phones do you think are bricked and returned because of that? 100? 500? I really think the reason is that the carriers want the phones to be sold to corporations that have strict policy against root on the network thus possibly compromising trade secrets and/or sensitive information. One purchase of 10,000 devices by a large company all on the Verizon (for example) network seems way more important than replacing a few hundred devices. As a network admin I would never allow a device on the network that could be rooted or bl unlocked if I were purchasing those phones for employees. IMHO

I fear the Google unlockable version is on life support at this time. I do hope I'm wrong but signs are leading that way. As they make a push for Project Fi that might be the straw. Perhaps they will make a premium costing device that can be unlocked and when no one buys it that will go away as well. Also IMHO. /flame off.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Can't argue with anything you said Bobby. Your likely right. Just hope your wrong about the unlockable phones. But, unfortunately, your likely right as well. That'll be a sad day!
[Google Pixel 2 XL Guides, News, & Discussion] djmouse:
This I can confirm on a verizion locked bootloader,with OEM greyed out.At least on the may patch,I'm on beta 3 P June patch ,haven't really tried anything but factory resets.
[Google Pixel 2 XL Guides, News, & Discussion] djmouse:
Also I can confirm you can opt out of the beta 3 P
[Google Pixel 2 XL Guides, News, & Discussion] slogar25:
Nice. What patch level do they take you back too
[Google Pixel 2 XL Guides, News, & Discussion] djmouse:
I haven't opted out,I'm assuming it's gonna be may,before it was April.But I've seen a lot of people saying they didn't even have that option to opt out witch seemed rediculous so was just confirming the option is there I don't want to go back but I'd bet my phone on it,it will let me.

Remember I'm on a locked bootloader 100 percent factory from verizion too.
[Google Pixel 2 XL Guides, News, & Discussion] hiaig:
Upon opting out, you'll be on the June 5, 2018 security patch level (Build number OPM2.171026.006.C1)

NOTE that opting out will factory reset your device. Prior to opting in, I was on the Verizon May security patch. I don't think there is a Verizon June security patch.

FYI, I am also on a Verizon locked bootloader Pixel 2XL
[Google Pixel 2 XL Guides, News, & Discussion] GokuSSJgod:
You say opting or will take you to June and then you say there isn't a Verizon June lol. Yeah there is lol
[Google Pixel 2 XL Guides, News, & Discussion] hiaig:
I should have been a bit more specific. Piror to opting in, I was on the verizon May patch, There wasn't a June patch available. I was on the beta for about 1 hr and opted out. I was then back to the June patch. Unless Verizon issued a June patch within that period of time (which verizon may have). I may be on the google June patch and that may be the reason for the factory reset.

Of course, I could be wrong and opting out of beta will factory reset the device automatically .... If that was the case, it would have been nice to be forewarned.

Cheers
[Google Pixel 2 XL Guides, News, & Discussion] bobby janow:
The June patch was out on Monday June 4th. You might not have gotten it yet, sometimes it takes a while to rollout. But when you rolled back they sent you the latest patch which naturally was June. Opting out of the beta will reset your device. You were forewarned but perhaps you missed it. Here it is from the beta sight. Emphasis added by me.

Leaving the beta program

You may opt out of the program at any time to return to the stable, public version of Android and/or Wear OS by Google. If you opt out when your device is running a beta version of Android or Wear OS by Google, all user data on the device will be wiped. If you choose to stay enrolled until the end of the program, you will graduate from the program and receive an update to the stable public release of P/Wear OS by Google. Your device will not be wiped.
[Google Pixel 2 XL Guides, News, & Discussion] deskjet390:
Do any of the Verizon OTA's update the bootloader version and have we captured those?

If the Verizon OTA file that is flashable in stock recovery contains a bootloader and is not allowed to be flashed to a Google Unlocked version...then this could mean that the same mechanism that prevents a Verizon bootloader being flashed to a Google Version through OTA is the same mechanism that works the other way around. Therefore, for more help to this cause, Google Unlocked users could start working on this issue as well by trying to find a way to flash the Verizon bootloader to their device through some means and if a way is found then it should work if the same mechanism is preventing it all. This would be done without using fastboot at all ofcourse.
[Google Pixel 2 XL Guides, News, & Discussion] djmouse:
I'm on June
[Google Pixel 2 XL Guides, News, & Discussion] slogar25:
Were you on May before taking the beta
[Google Pixel 2 XL Guides, News, & Discussion] djmouse:
I've been In and out of the betas,I just hard reset lastnight,I'm was going back because I miss substratum but I'm getting used to the factory theme,Im pretty sure 8.1 the June patch was pushed out OTA.
[Google Pixel 2 XL Guides, News, & Discussion] mkhader:
Since we don't see any progress regarding the topic , I suggest to all write a letter to Verizon that signed with our

names, email addresses , locaton , and IMEI numbers telling them that we ready to avoid our warentries , but unlock the bootloaders on our devices . ..

I don't see any risk doing that since we all want our devices warranties to be voided by choice, and to have our freedom to do whatever on them .
[Google Pixel 2 XL Guides, News, & Discussion] mrkhigh:
I'm assuming Warranties are not Verizon's main concern.

I imagine it is business security, premature unlocking and an agreement with the bloatware companies.
[Google Pixel 2 XL Guides, News, & Discussion] mkhader:
What if we offered them to have reasonable unlock fees per unlock ?
[Google Pixel 2 XL Guides, News, & Discussion] bobby janow:
Business security period! Premature unlocking? That's a new one. Bloatware is non existent.
[Google Pixel 2 XL Guides, News, & Discussion] AdamDevlopper:
So first of all, I didn't use XDA for a damn long time but now its time to get back to XDA due to I have a locked Pixel 2 XL!

So what I have tried or better what we tired (PM me to tag you)

-> Trying to spoof the request when the device is being setup and where it asks for the config file.

Conclusion: It wasn't possible for me I used Fiddler and the request is made through a tunnel, also installing Fiddler HTTPS certificate would make WiFi "Not Working" even it works but then it doesn't want to make any request at all. The request goes to afwprovisioning-pa.googleapis.com and there it asks for the config file. Why Im sure? I used the pm uninstall phone app methode and set a breakpoint on the URL and when I Run it into complition (So it can make the request) the OEM toggle was toggleable (Dat english). Oh yeah and the app is com.google.android.apps.work.oobconfig. What I also found out is that Afw means Android For work (If Im sure). I dont have that much knowledge in MiTM or debugging network connections but if you know please contact me! Here are some interesting codes (Decompiled the app using Jadx)

https://pastebin.com/itinN6pZ

https://pastebin.com/GRehCWkA
[Google Pixel 2 XL Guides, News, & Discussion] keaheng:
Keep up the good work
[Google Pixel 2 XL Guides, News, & Discussion] mkhader:
Have you tried to block afwprovisioning-pa.googleapis.com from your firewall ( or any router that can block certain URLS ) before using pm uninstall method ?

actually that makes sense, it may work

Name: googleapis.l.google.com

Addresses: 2a00:1450:4002:80a::200a

172.217.23.106

216.58.205.42

216.58.205.74

216.58.205.106

216.58.205.138

216.58.205.170

216.58.205.202

172.217.23.74

Aliases: afwprovisioning-pa.googleapis.com
[Google Pixel 2 XL Guides, News, & Discussion] AdamDevlopper:
Well the oobconfig won't enable oem unlock then at all, it stays grey for ever then...
[Google Pixel 2 XL Guides, News, & Discussion] twinkyz1979:
https://www.xda-developers.com/android-hardware-vulnerability-rampage/

Maybe this will help us?
[Google Pixel 2 XL Guides, News, & Discussion] Strephon Alkhalikoi:
If I recall correctly, no information about how to exploit the vulnerability has been released, meaning the devs would have to work from square one and attempt to duplicate the work the security team has done. Worse, I believe the security team required some 4000USD of special equipment to be able to accomplish the exploit in the first place
[Google Pixel 2 XL Guides, News, & Discussion] deskjet390:
What I think.

The phones are not unlockable with WiFi tricks or mitm things because I don't think they "call home" to decided to be locked or not because the bootloader literally does not contain the commands to be unlocked at all. They forgot to remove all the commands from the pixel 2 bootloader but successfully removed all of them from the xl.

The way I think it could be hacked

Someone creates an OTA package that can be sideloaded through stock recovery that contains a bootloader that has the unlocking commands still in it.

The OTA contains a payload.bin that contains all the separate files (one of them being the bootloader) and has been signed with a specific key.

Does anyone have any clue what allows or dissallows an OTA package install?

Could someone build an OTA package using Google's instructions and a copy of Android from source for the Verizon specific model?
[Google Pixel 2 XL Guides, News, & Discussion] TonikJDK:
They most certainly do phone home to get permission to unlock. We have the packets, we have the server names. We have had all of that since day one almost.

They most certainly do contain all the bootloader tools. Any claim otherwise is silly. It's the same exact software. And when a VZ one is unlocked all the commands work.

The mitm attack works, that was proven by the guy on Facebook that does it for 35 bucks. It's not working on the 2.

The phone will not load an OTA unless it is signed with Google's Certificate.

There is no source that is Verizon specific. They are exactly the same. Exactly.

Where did you come up with all these ideas? There is nothing even remotely true or factual about anything you have said in your post.
[Google Pixel 2 XL Guides, News, & Discussion] slogar25:
The only thing we need is the location in vender from where the transmission is coming from. I think that is the last step
[Google Pixel 2 XL Guides, News, & Discussion] deskjet390:
Okay since i have been educated on how this unlocking system works for this device.

Thanks TonikJDK for educating me (sometimes if you want to know the answer to something here you say exactly what it isn't and let someone flame you)

I guess what could be of use is a successful "Call to home" capture vs a failed one (verizon locked BL version ) with wireshark.

Also has anyone tried to setup ADB and look at debugging (either with remote adb daemon or other methods) of a device when a "call home" is being made? I know it would be tricky to insert this monitoring on the device when its just getting setup. But maybe with the developers kit and these instructions https://developers.google.com/web/tools/chrome-devtools/remote-debugging/ you might be able to see the process that is controlling it.

What do you think?
[Google Pixel 2 XL Guides, News, & Discussion] lucky_strike33:
I believe this happens way before we get our phone. The Sim is already in the phone and I'm sure they do the activation their end. This is coming from Best buy.
[Google Pixel 2 XL Guides, News, & Discussion] mrkhigh:
Pretty sure I installed my Verizon Sim.
[Google Pixel 2 XL Guides, News, & Discussion] deskjet390:
Im fairly certain this "Call home" takes place after a factory reset
[Google Pixel 2 XL Guides, News, & Discussion] lucky_strike33:
Lets hope we can find that call home and get it deleted
[Google Pixel 2 XL Guides, News, & Discussion] VulguM:
From what I've read here, it's more likely that the device will remain locked as long as it's not able to call home (thus unlocking only after successful communication with the server). So a MitM attack would be a way to unlock it, but achieving that is really difficult due to the measures taken by Google/Verizon and highly unlikely.

I hope someone finds a way, but I'm not holding my breath.
[Google Pixel 2 XL Guides, News, & Discussion] criswellc90:
Yeah I'm watching development for the Moto G6 and once there is confirmed root and L-OS I'm buying it at Walmart for less than I can sell this phone for.
[Google Pixel 2 XL Guides, News, & Discussion] slogar25:
It's more like needing to find the right way to stop the transmission. Uninstalling com.android.phone doesn't stop the call home for p2xl like it does for the og pixel. Looking through the source all the OEM lock stuff is nullable. But we have not been able to find the OEM lock stuff in vendor. Not sure if anyone has disassembled the bootloader yet
[Google Pixel 2 XL Guides, News, & Discussion] criswellc90:
Kind if off topic but not really. I acquired my phone through a friend who got it off contract from Verizon. What do you think the likelyhood is of me being able to request a non-verizon version through the warranty process since I have it on ATT?
[Google Pixel 2 XL Guides, News, & Discussion] mrkhigh:
Zero....
[Google Pixel 2 XL Guides, News, & Discussion] paradeedle:
https://xdaforums.com/pixel-2-xl/how-to/warranty-verizon-to-google-t3814454
[Google Pixel 2 XL Guides, News, & Discussion] aaronrw:
Preach on I will probably do the same
[Google Pixel 2 XL Guides, News, & Discussion] slogar25:
Will see what I can do later on tonight. Work two jobs?

But may also be helpful if we can see what is happening in fastboot as that is were the failure takes place. We can get the toggle active all we want but we are getting this in fastboot with the flashing unlock cmd:

(Remote failure: flashing unlock not allowed)
[Google Pixel 2 XL Guides, News, & Discussion] deskjet390:
Yes fastboot failure takes place because the application or activity that is responsible for enabling or disabling the commands is controlled by a remote database transaction that takes place while the Android system is running and connected to the internet.

Which is exactly why we need to start with a Google Edition of the device to capture the transaction that is happening to enable the bootloader unlock.

We have cases where a whole bunch of Google Edition devices we're not able to be unlocked and Google acknowledged this and fixed the issue remotely without EVER rolling out a firmware or software patch. This means that they let a whole batch of devices out the door and did not add their IMEI's to the unlockable database and they tracked down the exact batch/shipment of those devices and added them to the allowed database and issue was resolved.

So they turned what was essentially a Verizon locked variant into a Google Edition without changing anything but the whitelist.
[Google Pixel 2 XL Guides, News, & Discussion] slogar25:
Ok well I can't do anything haha. I have a Verizon variant. Maybe [MENTION=2955144]bryantjopplin[/MENTION] or someone with a Google edition could help
[Google Pixel 2 XL Guides, News, & Discussion] bobby janow:
I agree and have for a long time. However, let's assume you can capture the transaction. How would you add a device to the whitelist? If they connect to a database then there is no way to do it other than hacking into it and adding each manually right? That would hardly accommodate people here looking for temp root in order to change some system variables. I mean it's a great thought but not very practical imo. Unfortunately, I think this ship has sailed.
[Google Pixel 2 XL Guides, News, & Discussion] deskjet390:
I want to start with capturing the activity that occurs so we actually know for sure what exactly is happening.

You can not make any progress without knowing exactly what is happening...we need this so that we understand our devices... as soon as someone can capture these two things and get the captures to me (or someone else that knows how to read logs and wiresharks) we can go from there
[Google Pixel 2 XL Guides, News, & Discussion] bobby janow:
Hasn't this been attempted already?
[Google Pixel 2 XL Guides, News, & Discussion] slogar25:
I like where you want to go with this. Part of the problem is there aren't enough out here with Google editions willing or maybe not care enough anymore to help out anymore. It seems pretty much all that is left is us few that have Verizon variants and are kind of stuck. But if I remember correctly there were some traffic packets captured pretty early on in this thread. Not sure if they came from Google or Verizon but maybe useful. I'll try and find them.
[Google Pixel 2 XL Guides, News, & Discussion] Travisdroidx2:
I applaud you all for not giving up. I bought my Nexus 5X from Verizon and unlocking the bootloader was no issue. Little did I know when I bought my Pixel 2XL from Verizon that had changed. This is the first Android I owned in years I could not root and flash ROMs. But once I found out that the bootloader was locked by big red and people like jcase was not going to try and crack it for root. I accepted that this device will never be rooted and I have survived.

Best of luck to you all and maybe one day it will be discovered how to root even if we are on to our next device by then.
[Google Pixel 2 XL Guides, News, & Discussion] PILLMUZIK3600:
I feel u.. this phone is badass even without root.
[Google Pixel 2 XL Guides, News, & Discussion] slogar25:
Here is the post with the capture. All the way back to page 40. It lost in the game
[Google Pixel 2 XL Guides, News, & Discussion] deskjet390:
I have seen this....and i can look at 1000 more of them and get absolutely nowhere.

The simultaneous logcat is required for any captures to be of use in this situation. I can see if i can borrow a Pixel 2 XL from a friend and get this but I doubt i can borrow it.
[Google Pixel 2 XL Guides, News, & Discussion] computerfreek274:
I have a Verizon and now a Google unlocked bootloader. It maybe a long shot but when I get time I will look into it. I 1st had a Verizon pixel 2xl and gave it to my son I picked up a unlocked Google direct from Google. So I can do some development and roms. I already unlocked and root. I will when I get time try and at least see if I can get some logs out if it. But I been doing this kind of stuff for years this is going to be a long shot. I will do my best.
[Google Pixel 2 XL Guides, News, & Discussion] mrkhigh:
Don't I know you from Droid turbo rom? Or was it razrm?
[Google Pixel 2 XL Guides, News, & Discussion] PILLMUZIK3600:
U did a lot of good work on the turbo. This should be interesting
[Google Pixel 2 XL Guides, News, & Discussion] StankFiss:
Il try not to sound like a douche bag. But the last 8-10 years and the retiring of the great dev Dan Rosenberg, any root for a Verizon phone will never happen again. So if you buy a Verizon phone. You will never have root or bootloader unlocked. Its never going to happen. Face reality.
[Google Pixel 2 XL Guides, News, & Discussion] PILLMUZIK3600:
Heard it before .. u wanna bet money
[Google Pixel 2 XL Guides, News, & Discussion] StankFiss:
Ill be waiting. But wont hold my breath. Good luck.
[Google Pixel 2 XL Guides, News, & Discussion] mrkhigh:
Djrbliss wasn't the only person who rooted motos.

Geohotz (yes gone) and beaups (many times) did as well.

I deleted Twitter... No idea what beaups is into now but my guess is not this phone.
[Google Pixel 2 XL Guides, News, & Discussion] deskjet390:
I know that it's a Longshot....

But the very basics of defining exactly what is happening is missing here. I see this as a way of at least gathering that information.
[Google Pixel 2 XL Guides, News, & Discussion] computerfreek274:
Yeah I was looking over some stuff today turning in and off oem lock and unlock. Not much happening I will dig deeper. When I have time. I am hoping to push out my own kernels or tweaks for the pixel family. I did work on the Droid turbo and started out years ago on the Motorola Eris years and years ago. They also said the Droid Turbo couldn't be unlocked on Verizon and it got unlocked 10 months after the release the Eris too. My Verizon Motorola Rezound was a combo of a hardware and software unlock there is always hope. Look even the Nintendo switch got hacked Anything is possible. But as far as a EASY software hack slim chance.

I am not going to be the one to do it I know that. But if you guys are looking for some logs and data I can help with that. But it all useless you know what to do with them. So if any developer would like direct info or data from me please PM me and I will be happy to help. As I too would like to root my son's pixel.
[Google Pixel 2 XL Guides, News, & Discussion] computerfreek274:
Some of Logcat Stuff Not much of a help. There is nothing new here as other phones send the same info out. But I still hate to post it as I would like to talk to someone 1st who is working to maybe unlock the Verizon Pixel. but here you go's you guys can toy around with that. I will dig into it more at some point.

https://1drv.ms/u/s!AtD9D112ASnIgYXTBzLvaXcZJSABDgg
[Google Pixel 2 XL Guides, News, & Discussion] nolanjb:
That's from your Verizon pixel 2? That's what my capture from my Verizon pixel 2 looks like too. Could the line that says "Parse: Incorrect message command" be part of the issue? It seems like maybe it's failing to update the unlock bit or something.

https://drive.google.com/file/d/1aELjsiXprphm5NH0ElLq0D7pIpNjZW1G/view?usp=drivesdk
[Google Pixel 2 XL Guides, News, & Discussion] actionracingphotos:
I've used the og vzw pixel unlock method to enable my oem unlock button but still couldn't get it to unlock in fastboot