yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] abuttino:
Not Unlockable.

Sent from my Pixel 2 XL
[Google Pixel 2 XL Guides, News, & Discussion] oakley470:
Incorrect I setup 5 pixel 2xl with a Verizon sim bought from Google and everyone of them remained unlockable. The bootloaders are locked by Google based on IMEI numbers, that's why you can look on your Verizon account under devices and see that it's called "non VZW pixel 2 XL". If your IMEI is stored in Verizon's system the non-vzw designation drops off and the bootloader is locked pre shipment by Google.
[Google Pixel 2 XL Guides, News, & Discussion] humdrum2009:
Hmm so how are these ones from Fort Worth Texas coming unlocked, I mean bootloader wise?

Are they true Google models or something else is going on and they just don't have the time to load the vzw edition software? Because if it is imei based, that sounds plausible.

Maybe they just don't have a vzw supply to refill from on rma devices
[Google Pixel 2 XL Guides, News, & Discussion] oakley470:
They do not have Verizon models sitting there, that's why on release day off you bought the Verizon version it says shipping in 5-6 weeks, where as the Google version was available immediately. Once the order is placed for a Verizon version, Google has a system available the scan the barcode and put a sim in the box. They then notify Verizon to add the IMEI to their approved list, so by the time it shows up to you everything is set and at activation you're locked. Google most likely is not doing this with RMA devices in order to get the phone into people's hand faster, as you would complain if they said you won't have a replacement device for 5 weeks. So odds are pretty much anyone who wants an unlocked device can just request an exchange from Google and as long as they are still sending new not refurbished devices, you'll get back an unlocked model
[Google Pixel 2 XL Guides, News, & Discussion] humdrum2009:
Makes sense my rma devices will be here today, phone having freezing and reboot issues, I'll check if it's unlocked or not and report lol.
[Google Pixel 2 XL Guides, News, & Discussion] alienware777:
.........................................................
[Google Pixel 2 XL Guides, News, & Discussion] Cbass15:
No Google will send you a Verizon one. If you call Verizon and RMA the device there is a "chance" you will get sent a Google unlocked version.
[Google Pixel 2 XL Guides, News, & Discussion] humdrum2009:
Sweet just got phone bootloader unlock successful

Im assuming now i can set up as normal and it wont relock cool
[Google Pixel 2 XL Guides, News, & Discussion] mlin:
Requested a warranty exchange yesterday due to screen issues. I didn't care much about the bootloader which is why I bit the bullet and purchased from VZW during their 50% off trade in promo. Nonetheless, if I get an unlockable bootloader I'll be pretty excited, but only if the screen is acceptable as well. Mine is coming from Ft. Worth, TX FWIW.
[Google Pixel 2 XL Guides, News, & Discussion] humdrum2009:
I just hope I don't get the screen freezing with this one and reboots
[Google Pixel 2 XL Guides, News, & Discussion] ironmaskusa:
I've searched around but I guess you just need to go find a thread some cool Dev hangs in to get a few kicks in and accepts the challenge.. point me the way please.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
https://xdaforums.com/pixel-2-xl/help/verizon-bootloader-unlock-discussion-t3697493

:good:
[Google Pixel 2 XL Guides, News, & Discussion] mobile_sensei:
Put me down $100 - that's well over $1000 bounty. I hope [MENTION=6949582]RootNinja[/MENTION] sees this ?

---------- Post added at 01:24 PM ---------- Previous post was at 01:23 PM ----------

Put me down $100 - that's well over $1000 bounty. I hope [MENTION=6949582]RootNinja[/MENTION] sees this ?
[Google Pixel 2 XL Guides, News, & Discussion] btonetbone:
So, silly question, but has anyone tried using Kingroot for Windows on either 8.0 or 8.1? I can try it later tonight if nobody else has given it a shot.

https://kingroot.net/
[Google Pixel 2 XL Guides, News, & Discussion] enzyne:
Failed on 8.1 pixel 2. Device not adaptive.
[Google Pixel 2 XL Guides, News, & Discussion] KyleK29:
Did you do the warranty exchange through Google directly or did you go through Verizon to do it?
[Google Pixel 2 XL Guides, News, & Discussion] mlin:
Verizon, I went into the store to see if I could get an exchange because I was told I was within their holiday exchange period but that was not the case. Instead they just started the warranty exchange process for me.

Oddly, when I received the device, the OEM unlock option was grayed out and could not be toggled. However, after updating to 8.1 the option became available... Not sure why but I still have not put a SIM in it.
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
i have tools to build and sign edl programmers already.. the issueis wedont have the oem key.. the keys i have are qualcomm keysas thetoolscame from aqualcomm employee when i was still workin on the S8+ (which is also msm8998.) Eventuallyi found a sammy signed programmer, before that it was literally weeks i wasted lol

theres alot more than just flashing with signed programmers that can be done with edl.. maybe someone should connect the phone in edl mode and run through QXDM.. peek and poke, writing NV stuff, some commands etc
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
point is he came in here claiming he could unlock the p2xl and ppl were hittin him up on FB and he dissappeared from xda then he was charging but "wasnt charging" until after success which never happened.. he wasbasically using xda to tryn make some money all while being super shady..

i was actually trying to help him lol we went back n forth abit and he was supposed to get me some logs but never heard from him again despite him reading my fb messages askin what happened lol.. but anyway, hes banned for a reasonso ill leave it at that lol
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
thatsy itsgood to reada bit before posting lol just sayin..

but no, it is a touchy subject in here that seems to pop back up randomly when its been discussed multiple times and never worked for us here
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
lmao right, he just touched a very touchy subject in here haha..the other guys right too, seems werkly it comes up haha, thats xda for ya
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
yep.. locked devices need oem key.. aosp uses public keys.. i just learned this the hard way haha, by building aosp :).. read those articles 100x before starting, good stuff!
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
haha i need to stop commenting before reading all recent posts to avoid leaving multiple posts :)

i read one post 5 pages back n comment smh
[Google Pixel 2 XL Guides, News, & Discussion] fortillian:
I bought my Pixel 2 XL from Verizon 2 days ago after my 6P died a sad death. I needed a phone quick and so I purchased one from Verizon online for local pickup...silly me. I just processed an online return, and then purchased an unlocked from Google. Although I was aware of the locked bootloader I though there would be a way. Reading this thread made me realize my mistake.
[Google Pixel 2 XL Guides, News, & Discussion] MColbath:
What tools are you using? I have OpenPST and QPST for EDL. Also, could you upload the stuff you have regarding it.

As for QXDM that won't work because it's in download mode which only allows for flashing images.

Honestly, I think the most viable method right now is going through the LG Download Mode using LGLAF. Although, I don't have enough knowledge on programming to tweak the script so that it works for the Pixel 2 XL. Well, actually it might not even needed to be tweaking considering some of the commands work and I just don't know how to use them.

--UPDATE--

Okay, so I found a version of LGLAF that works better with the device. I was able to dump the laf, misc, persist, etc. images with it but, some of them like, boot, oem, etc show up as unknown as you can see below in the partition table dump.

MBR Header
LBA size (sector size): {0} 512
Number of MBR partitions: 1
# Active From(#s) Size(#s) Code Type
1 _ 1 4294967295 EE EFI GPT protective MBR
GPT Header
Disk GUID: DCED69FA-062B-963F-B207-C324C9911FB3
LBA size (sector size): 4096
GPT First LBA: 1
GPT Last LBA: 15258623
Number of GPT partitions: 13
# Flags From(#s) To(#s) GUID/UID Type/Name
1 35747322042253312 6 12293 98523EC6-90FE-4C67-B50A-0FC59ED6F56D Unknown
E1AF1CBA-5490-EE3C-E772-FA666CCE9344 laf_a
2 34621422135410688 12294 24581 77036CD4-03D5-42BB-8ED1-37E5A88BAA34 Unknown
CD54239F-1B22-E4FB-8E9A-F8CC10DE427F laf_b
3 0 24582 24583 2C86E742-745E-4FDD-BFD8-B6A7AC638772 Unknown
E5D61440-ED48-A0C1-F7BB-F9CEF4A7E905 ssd
4 0 24584 32775 6C95E238-E343-4BA8-B489-8681ED22AD0B Unknown
26D5F316-B75C-6EC9-BE45-60DE9F00216B persist
5 0 32776 33031 82ACC91F-357C-4A68-9C8F-689E1B1A23A1 Unknown
B064BADE-50ED-C5CE-156A-99BBBD71F1C3 misc
6 0 33032 41223 DAA3EAAC-9D97-4EFF-A9B5-6BAF57D1495E Unknown
2D041A89-A9C2-2250-457B-885846E43E5B ftm
7 35747322042253312 41224 696583 97D7B011-54DA-4835-B3C4-917AD6E73D74 Unknown
5F0A0732-5341-0511-E253-2D04B7C1CE12 system_a
8 34621422135410688 696584 1351943 77036CD4-03D5-42BB-8ED1-37E5A88BAA34 Unknown
5B492F57-20D9-0460-5E05-F5F6FDA52872 system_b
9 0 1351944 1353991 025064E1-D2A2-44C6-9626-67E374C08EAB Unknown
12713019-023D-2379-33E0-F9DE6E6D84F8 pstore
10 35747322042253312 1353992 1354119 BD9E4B34-E2F3-49FC-920D-BCCBDF3D4710 Unknown
9B962BD6-A241-5655-D162-F32107871C5B aes_a
11 34621422135410688 1354120 1354247 77036CD4-03D5-42BB-8ED1-37E5A88BAA34 Unknown
CB953643-DCE5-0FF8-7EFC-093D8E18101B aes_b
12 0 1354248 1355775 0A7BE037-F315-4166-B2C2-851B004C696B Unknown
85F7C639-DB57-37B4-2EA4-B01DBE4D2E01 align_parti
13 0 1355776 15258618 1B81E7E6-F50D-419B-A739-2AEEF8DA3335 Unknown
CFF9B02B-A9CD-0802-CB6B-A413D4D5F97C userdata

Writing partitions appears to be working as well. It might be possible to overwrite the LAF partition with TWRP. There's a guide here. Although, it is for V10/V20 it looks like it could be ported to other devices, so maybe it could be used for the pixel as well.
[Google Pixel 2 XL Guides, News, & Discussion] bobby janow:
That's the way to do it.
[Google Pixel 2 XL Guides, News, & Discussion] Addiso:
https://xdaforums.com/v20/how-to/laf-download-mode-how-root-t3676011/page99

This a good read on laf. Currently the g6 is known to be compatible and works are being made to get the v30 on the list by cross flashing laf's.
[Google Pixel 2 XL Guides, News, & Discussion] Scott:
This is all very interesting!

Anyone here able to even connect with the app? I keep getting USB device not found. Yea, I know. Its way OT.
[Google Pixel 2 XL Guides, News, & Discussion] Skorpyun812:
I understand little about coding and programming and all that fancy talk. But if edl is a mode that allows force flashing of OEM software, is it possible to rollback/overwrite the security updates by flashing a version that came on the phone at its debut? Or any other previous OPM build that allowed users to exploit and unlock the bootloader?
[Google Pixel 2 XL Guides, News, & Discussion] MColbath:
Well, yes but, there wouldn't really be a need since if that was the case you could just flash images with oem unlock enabled. Techincally, this could be done already as, I figured out a way to write to partitions in LDL, that seems to be working. I only tested it only laf_b though. I just need someone to write TWRP to laf_a to know if it works for sure. If I had a google version of the pixel I'd try it myself as I wouldn't have to worry about bricking the LAF partition with an unlocked bootloader. Anyways, I was able dump system images and they weren't corrupted or anything so it should work.
[Google Pixel 2 XL Guides, News, & Discussion] slogar25:
So in theory, once we get TWRP installed on laf, we should be able to flash an image with OEM unlocking switch enabled? Or would we still be blocked out by not having OEM keys
[Google Pixel 2 XL Guides, News, & Discussion] MColbath:
As long as you reboot to bootloader after flashing the image it should work.
[Google Pixel 2 XL Guides, News, & Discussion] GokuSSJgod:
Are you saying that you're close?
[Google Pixel 2 XL Guides, News, & Discussion] mrkhigh:
He's saying he may have done it for the LG based ones. He just cannot afford to risk bricking his phone.

Sadly I'm on the htc variant.
[Google Pixel 2 XL Guides, News, & Discussion] MColbath:
I honestly have no idea until somebody attempts what I suggested. Although, yes, if it works, we would have TWRP which will let us do everything we need to, to unlock the bootloader.
[Google Pixel 2 XL Guides, News, & Discussion] Scott:
WHen you in Download, does the phone show up as a com port, like Com 1, com 2, etc?

I would be more than willing to try and flash with this tool but it says that it needs a USB connection but when I connect my phone it shows up as Com3.

I have zero concerns of brick so if I could get this phone to communicate properly I would be more than willing to try flashing.

The fact that you did flash a b partition and it did not throw up a security concern during boot is very entertaining.
[Google Pixel 2 XL Guides, News, & Discussion] MColbath:
I'm running Ubuntu 17.10, so I didn't really pay attention to COM port. Although, COM3 should be correct, that's what it was for EDL when I was on a virtual machine for QPST.

Although, you probably already know this. You need python and the LG drivers to get it to work. I have the LG drivers if you need them. Although, when I tried to get LGLAF on windows it was a hassle, so I just kept to linux.

Check here.
[Google Pixel 2 XL Guides, News, & Discussion] Scott:
Ahhh, Ok. I was following the Windows 10 Guide, and yes, it was a hassel. I will just boot into Ubuntu and try again tonight.
[Google Pixel 2 XL Guides, News, & Discussion] MColbath:
Okay, on Ubuntu the first time you send a command it will be an error, afterwards it works. Also, you need runningnak3d's version of LGLAF and the branch that works best is h918-miscwrte, although the link in my previous post pretty much covers all of it. I'm just not sure if it needs to be --restoremisc when writing the partition or not because, I used --restore when I did it.
[Google Pixel 2 XL Guides, News, & Discussion] Skorpyun812:
If I knew what an laf was let alone how to write one, I'd try to help you with that. Lol.
[Google Pixel 2 XL Guides, News, & Discussion] slogar25:
Laf stands for"LG advanced flash".
[Google Pixel 2 XL Guides, News, & Discussion] MColbath:
LAF is a recovery partition on LG devices. Main purpose is flashing firmware, like EDL and Bootloader.
[Google Pixel 2 XL Guides, News, & Discussion] b00ster23:
Any luck?
[Google Pixel 2 XL Guides, News, & Discussion] enzyne:
[MENTION=2477527]mrjaydee82[/MENTION] Please remove my contribution. I did not realize that this was for the XL.
[Google Pixel 2 XL Guides, News, & Discussion] Scott:
Just got home from work now. Rebooting into Ubuntu... I should be back with in the hour...
[Google Pixel 2 XL Guides, News, & Discussion] Scott:
Wow. Cant be this easy. Its letting me write back to the Laf_b with the dump I made.

Thats my first test... Pull it off the device then put it right back on. If that fails everything else will fail. If that passes that the rest of it is still 50/50...

Second test will be the recovery image file.

Here is a screenshot of it writing it succesfully...

I got TWRP downloaded...

Cross your fingers... I cant be this easy, right???
[Google Pixel 2 XL Guides, News, & Discussion] Scott:
Ok, yeah so. No good.

It says that it writes it but it does not actually write anything.
[Google Pixel 2 XL Guides, News, & Discussion] MColbath:
Did you try it with laf_a too? Or did you only do it on laf_b because, laf is in slot a by default.
[Google Pixel 2 XL Guides, News, & Discussion] Scott:
Yep, I flashed B then A. Then rebooted. Have you (or anyone else for that matter) contacted the script developer for input on our situation?
[Google Pixel 2 XL Guides, News, & Discussion] MColbath:
Well, at least it doesn't appear to be impossible to write images with it. I haven't contacted the developer yet, doubt anyone else has, but you can if you want to. The script probably needs a few tweaks and we should be good to go. I mean, it isn't denying write access outright, so there should be some hope.

--UPDATE--

Nevermind, I just sent him an email, I'll let you know what he says.
[Google Pixel 2 XL Guides, News, & Discussion] jimlightner:
I just want to thank the guys who are giving it hell to try and unlock this thing.. without your dedication and perseverance things like this would not be possible..I think a breakthrough is almost here..?..from the last couple of pages I've read seems like your close..thanks again..
[Google Pixel 2 XL Guides, News, & Discussion] fr0st420:
Put me down for $25 on the bounty. I'm happy to see people are still trying to unlock the Verizon variant.
[Google Pixel 2 XL Guides, News, & Discussion] slogar25:
It seems like it will let you restore images. What if you restored a system dump from a system with the OEM switch enabled. Just spit balling
[Google Pixel 2 XL Guides, News, & Discussion] MColbath:
Can't there is a limit on the size of the image that can be sent over. The system_a partition is ~2.7GB and I tried twice restoring it, but it fails around 50% and the speed is only 1MB/s it takes like half an hour or more just to get to 50%, unforunately.
[Google Pixel 2 XL Guides, News, & Discussion] Scott:
Sweet!

Yeah, you can try that but my ascertion is that the device, although appears to be writing the info to the eMMC its not.

I don't think that would matter actually. Its not writing the image. However, I cant see how there would be a size limit. This appears to be serial communication that is writing directly to disk. I really don't think size will be an issue. BUt... I honestly cant say that for any certainty.

However, those that stated its on the MISC partition and they have a google variant with unlocked bootloader... I wonder what would happen if you flashed our MISC partition? Yeah... anyways... not important but wonder what would happen...
[Google Pixel 2 XL Guides, News, & Discussion] Scott:
Also, I wonder if there would be any value in trying to write to the "FTM" partition as they are pretty synonomous with download mode. And that is how they do it on the V20, they flash the download mode as its not protected like the other partitions. From there they install twrp then install twrp again in recovery. Just thinking out loud.

EDIT: Yes, the FTM is the download mode... according to Google anyways: https://productforums.google.com/forum/#!topic/phone-by-google/jwNRZJSyRII

This is where I need to try flashing when I get out tonight.
[Google Pixel 2 XL Guides, News, & Discussion] TonikJDK:
I think the misc partition is your target. The state of the slider is irrelevant. It's the bits on that partition that matter.
[Google Pixel 2 XL Guides, News, & Discussion] GokuSSJgod:
Can't wait to hear back the results. I'm currently on Android p. If this works would that matter? I can possibly get back to 8.1 on April patch. What are you on?
[Google Pixel 2 XL Guides, News, & Discussion] Scott:
This would be independent of the OS.

Basically what we are trying to do is us the LGLAF utility to write the recovery to the (wrong) unlocked partition whih is the FTM partition.

I will try this when I get home. Clocking out of work now...
[Google Pixel 2 XL Guides, News, & Discussion] Scott:
TWRP is too big for the partition... Ugh!
[Google Pixel 2 XL Guides, News, & Discussion] d33dvb:
Throwing in $20 for root, $50 for bootloader. I have faith in you guys.
[Google Pixel 2 XL Guides, News, & Discussion] b00ster23:
Seema like that was a problem back during development... From what I remember reading
[Google Pixel 2 XL Guides, News, & Discussion] Addiso:
If I remember correctly, twrp is sent in chunks. Since writing to it can only take a certain chunk size. Correct me if I'm wrong.
[Google Pixel 2 XL Guides, News, & Discussion] Scott:
TWRP was too big so I tried another recovery that was smaller and that flashed but just like the other partitions, it did not save to the device.

So... I also tried writing to MISC also.. And of course... That is copy protected so it looks like the back door in the Gx and Vx series from LG are not present on this device.

Maybe the dev that wrote the script can chime in...
[Google Pixel 2 XL Guides, News, & Discussion] GokuSSJgod:
Or it's just a secure device :(
[Google Pixel 2 XL Guides, News, & Discussion] Addiso:
I believe the laf present on the phone requires the COPY codes in order for the back door to work. The V30 does not have the Copy codes. The G6 is able to flash the v20 laf that has the COPY codes to take advantage of the backdoor.
[Google Pixel 2 XL Guides, News, & Discussion] GokuSSJgod:
So when V30 codes available then maybe¿
[Google Pixel 2 XL Guides, News, & Discussion] Scott:
So your saying there is more to it then just having an available back door?
[Google Pixel 2 XL Guides, News, & Discussion] Addiso:
https://xdaforums.com/v20/how-to/laf-download-mode-how-root-t3676011/post76115181

The phone requires an unlocked boot loader in order for the laf to be written.
[Google Pixel 2 XL Guides, News, & Discussion] Scott:
Ahhh... Hmmm... Thought the entire point of this script was to be able to write to a locked bootloader device via an unsecured download mode? Maybe I mis read something somewhere.
[Google Pixel 2 XL Guides, News, & Discussion] slogar25:
I'm sorry but if we had an unlocked bootloader then there would be no point in trying to use LAF. This whole point is to find a way to unlock the Verizon pixel 2 xl. And I thought that was why the thread referenced was created for the v20 as well
[Google Pixel 2 XL Guides, News, & Discussion] Addiso:
Thing is certain LG devices had unlocked bootloaders with fast boot commands stripped, which is why laf was used to load twrp. The developer who made the script is in the works with getting a way to unlock the boot loader on locked down devices. I would try and get in contact with him. Here's more insight on how laf works. https://github.com/Lekensteyn/lglaf/blob/master/protocol.md
[Google Pixel 2 XL Guides, News, & Discussion] MColbath:
That's what we've been doing, tbh.

We've been using this, although the original script's authorization doesn't work with the pixel 2 xl's so we're usimg runninga3dk's version of it. Most of the commands don't work, only dmesg and umount work in rawshell as far as I know, out of the rest of the commands I know that './lgaf.py -c '!INFO GPRO \x08\x0b\0\0' and the restart commands work, the rest, not so much.

Although, the reason it might not actually be writing the device is more than likely related to the partitions, offsets, size, and what not. If it was a problem the authorization we would be getting access denied, so it's more than likely not that. Furthermore, the device is responding when it's being written to, just nothing is changing. I'm trying to find out what might be conflicting through the dmesg right now.
[Google Pixel 2 XL Guides, News, & Discussion] slogar25:
I'm sure you did but did you guys update the rules.d in lglaf

to include our device?
[Google Pixel 2 XL Guides, News, & Discussion] Nabooki:
Name the file from ".xxx" to ".old". HaHa
[Google Pixel 2 XL Guides, News, & Discussion] MColbath:
This is probably a stupid question but, what would happen if we wipe the misc and/or the persist partition(s). Although, I doubt it's possible considering that we can't write the partitions at the minute.
[Google Pixel 2 XL Guides, News, & Discussion] GokuSSJgod:
There's no stupid questions when it comes to this but. If I had to guess I don't think that it would wipe. What color is your phone btw?
[Google Pixel 2 XL Guides, News, & Discussion] MColbath:
My phone is the white 64gb model, and yeah it probably wouldn't be able to. I'm still waiting for the developer of the LGLAF I'm using to email me back, it's been ~2 days now. Not sure if he's busy or just ignored it at this point.