It sucks to be honest, and the people reporting the OEM unlock ungraying itself during the "deadline" (sept 2019 > july 2020) may be reporting actual VZW pixels that also found vulnerable moments. Some theories stated that when Google and VZW (it may not even be correct that VZW has a role) moves around servers, this is when the server is vulnerable, because it's inactive, or nothing there from stopping the OEM unlock mechanism if I'm correct?For what it's worth, I haven't had any luck either. I visited XDA and saw the article too late. I tried it twice and the second time I've left it for a couple of days now with no luck. Thanks anyway, and good luck for the future to all of us! This particular Pixel I got off Swappa, and the guy put at as a Google Edition 128 GB. I only had the 32 GB Google Edition I got cheaply from Best Buy in 2016, and the Swappa deal was only $50-$55, so I kept it even though it was a Verizon edition instead. I did tell the seller in order to educate him, though.
No idea if it was refurbished, and it has the indication it's on the October 2019 security patch even though I'm on the final OTA.
At the moment, the VZW research team is put back to work. I may end up requesting this thread to be closed so it does not confuse people, but I'll decide on this later. I apologize so much that you didn't get your bootloader unlock. At this point it's safe to say that the classic exploit is a unstable exploit, and should not be depended on.
Thanks for your time.