Yeah I tried that but the seller doesn't want to go through the trouble.
No worries, I'll just walk away.
Thanks ?
Top Liked Posts
-
There are no posts matching your filters.
-
2This looks to be a problem with the "refurbished" Pixel 2s they send out for warranty replacement. After sending me 3 "refurbished" ones, they now said I qualify for an exception to receive a new phone, and got the new one -- which worked immediately without any problems. Notably, in Developer Options, the "OEM Unlocking" slider is off after a factory reset, not on as on the refurbs.
Also curious: if you do a adb shell getprop ro.boot.cid, you should see VZW__001 on a Verizon phone and 11111111 on a Google phone. My refurbished phones, as well as the new one I just received, all returned 00000000.
The refurbished phones all shipped with a 3/2018 patch date, whereas the new one shipped with a 9/2017 patch date. That might also be part of the issue.2Mine was a brand new device. I did update to the June security patch before I finally got it to work. I refused to install my SIM card (which is Verizon) until I managed to get the bootloader unlocked.11
Agree that it's probably going away... But disagree "no one cares about BL unlock". I care... LOL
1I have the same issue, refurbished replacement from Google. The option is available on first boot after factory reset but fastboot command does nothing. After reboot, option is greyed out. Has there been any developement on this? Or am i stuck in their RMA cycle until they wise up and send a new one... Ive reached out to them and requested a new device based on the info provided here and reddit etc.. its been escalated to management but i highly doubt its going to be resolved to my satisfaction..
