it is successful, but on reboot it goes to an endless bootloop. i have tried ota, factory images...flashing twrp flashing rom. only reboots when trying to go into system. sometimes it will bootloop from twrp, but never from stock recovery or fastboot
Ah, lucky You!Breaking news - I UNLOCKED bootloader, rooted & install Lineage OS V17 (Android 10 final build) on my OG Pixel (PVT variant). Here's my results, see screenshots & photo images taken yesterday ... woohoo. As always - please read, follow and give it several tries on your best efforts, and YMMV. Good luck.
One of the most useful aspect of having, owning & using the Google OG Pixel or Pixel XL after June 1, 2021 is the continuing support for uploading original photos via it to Google Photos for storage (until early 2022) without being counted against one's allowance, or having to pay more/extra for it. I do have Google One with 100GB shared among 3 accounts but ... Some of the "original" photos are precious & priceless memories of families & friends - I've sold my 1st. generation Pixel XL Google Edition earlier to move up to the 3a XL, but let's say, I do miss the Pixel's unique choices these days - thus, I picked up an inexpensive Pixel in good to excellent condition, battery life is average but otherwise great overall, supposed to be the Google variant, unlockable bootloader. Well, it was/is not when it arrived by postal package and my reaction was ---- (fill in your own words) knowing that it is a waste & going to need to return to seller. To make a long story short, I failed twice with previously outlined steps and ADB sideloaded, etc. etc. taking all the steps, no luck or success .... resigned to either use it as is, with stock rom or return/refund & go find another one.
"OEM Unlocking" option under Developer's option within Settings was greyed out, no matter what - was on the final OEM Build ... until
A word of warning, doing these could damage and/or brick your Pixel, and I am not responsible nor anyone else that wrote the steps & guides for the attempts/efforts to get the locked bootloader to somehow unlock, root & install your choice of custom rom, etc.
First, I follow the steps to factory reset, install ADB and sideload, etc. and re-install the zip file, reset & boot, initially without connecting to WiFi, enabled Developer's option, enable USB debug, and confirmed that both ADB and FASTBOOT options are working, that the PC (Windows 10 Pro, 64 bits) recognizes the serial number/device ID. Uninstall the com.android.phone via ADB before another reboot, connect to WiFi & open browser to google, open various websites and check the OEM unlock options, etc. - it was still no can't do. After spending all afternoon/evening, trying & waiting, cursing too, I gave up AND decide to sideload the final stock rom zip file again, and boot up to do the basic / regular setup, etc.
Well, after installing basic apps and setting it up for minimal functions, I went ahead to play with it. Well, I went back into Developer's setting and guess what, the OEM unlocking function is now enabled, no longer greyed out. Woohoo - joys, I went ahead to boot into bootloader/fastbook, and, unlocked it. The rest is history - after clicking the "warning" on screen. Lineage 17 (Android 10) is now installed, running, with pico gapps, and Google settings from a previously saved device and apps restored, up & running smoothly.
I did not insert any nano sim card (this will be kept & used at home and connect to WiFi only) mostly for uploads & cloud access.
To sum it, follow the previously documented steps to try and if it failed (most likely, it will ... just like me) then by the 3rd time, reset again but let the sideload rom/zip file install fully - boot up the stock rom, then, setup as usual, for a minimal one. Wait & let the rom settle & finished updating everything from Play Store, etc. - then, check again about the OEM unlock option (fingers crossed & good luck). If you are like me, the device will be fully wiped again as part of unlocking & factory reset, erasing everything - then, you are good to sideload Lineage and optionally, gapps, etc. and enjoy.
Any questions, feel free to ask and if I can help, will cheerfully do so. Have a great week ahead. It it works for you with a bit of efforts, thumbs up and if not, please share anyway. Good luck !! Next, going to upload photos at full quality/resolution (almost all are 12 MP or less in resolutions anyway) for additional "free, for now" secure storage.
I would try to root XL again but i have to figure out how to backup actual setup without Google or with minial use of 3rd apks.Yes, pretty much as you said & what I wrote. I picked up the OG Pixel (not XL) 1st gen on Swappa last week for $65+tax, read thru & searched all the previous guides, instructions & feedbacks - installed the latest ADB, Google drivers (current) and basically threw the towels in already. Trying to go backtrack & re-trace all the steps, failed visuals ... I've done the numerous reboot, factory reset & full wipe, all without connecting to a Google account or WiFi, without a nano sim. Pretty positive (99%) that in my final sideload, just didn't uninstall the android phone apk as others "instructed" - and then gone thru the routine setup with LOS (no Magisk, no custom kernel - just OG's arm64 pico for Android 10 ... watched Play Store to update, reinstall a minimal # of Apps to keep the device's storage as free as I wanted it to be.
On a hunch, I checked it later that evening and woohoo, the OEM unlock button was no longer greyed out - so, I ADB reboot to bootloader, check to make sure fastboot can access and issued the command to unlock ... watched it reset & wipe again.
Once I saw the hardware was coded for the Verizon variant, I was disappointed and really wasn't expecting the efforts to payoff & work ... somehow, it did and luckily, made screenshots for my records. Our Pixel 3a and 3a XL are both unlocked, not VZ locked with the bootloader so I knew the difference. Now, I got 6+ months to upload some of the precious, old family pictures for folks that are no longer ... in original quality to cloud storage at Google, it's wonderful - along with offline backup storage.
If you feel like giving it a try again, go ahead & backup things first, reset and bump everything along - hopefully, you get a chance unlike several months ago. Good luck !!
Here is what worked for me:
No SIM card in the phone
ADB and Platform Tools installed on a computer (https://www.xda-developers.com/install-adb-windows-macos-linux/)
The latest OTA image downloaded to the computer (https://developers.google.com/android/ota#sailfish for the Pixel or https://developers.google.com/android/ota#marlin for the Pixel XL)
The phone connected to the computer with USB
Learn how to use ADB and Fastboot on your computer as it can differ.
1. On the phone, open Settings>System>Reset Options and factory reset the phone. It should say "Restarting" or something similar.
2. When the screen goes black, press and hold the Volume Down key until you get into the Bootloader mode. Use the volume keys to navigate to "Recovery Mode" and select it with the power button.
3. Hold the Volume Down key for about a minute (while it resets) until you see an android lying down.
4. Hold the Power button then press the Volume Up button once. It should give you a menu.
5. Use the volume and power buttons to select "Wipe Data/Factory Reset" and confirm the reset.
6. Once it finishes, select an option that is something like "Sideload OTA"
7. Go to your computer and type in 'adb sideload sailfish-ota-qp1a.191005.007.a3-394b5899.zip' (without quotes) for the Pixel or 'adb sideload marlin-ota-qp1a.191005.007.a3-23002a57.zip' for the Pixel XL OR you may drag the zip file into the command prompt after typing "adb sideload", either way it should look similar.
8. Factory reset again from recovery mode
9. Reboot to system
10. While it just shows the G, press the power button until the phone restarts
11. Once it boots up, skip all of the steps but disable the options for sending information to Google.
12. Enable Developer Options by tapping "Build Number" seven times
13. In Developer Options, enable USB Debugging
14. On your computer, run 'adb shell pm uninstall --user 0 com.android.phone'
15. Reboot twice
16. Connect to WiFi
17. Open google.com in Chrome
18. Check Developer Options to see if you can enable OEM unlocking
19. If you can't, swipe away Settings from the Recents menu and go back to Chrome
20. In Chrome, open a bunch of websites. After opening each one, check the OEM Unlocking option again and close Settings afterward.
21. Once you can enable it, do so! Now you can unlock the bootloader.
Unlocking the bootloader:
-Reboot and press the Volume Down key when the screen goes black
-On the computer, type 'fastboot flashing unlock'
You just unlocked the bootloader!
Credit goes to djared704 for finding this method.
Let me know if I need to change anything about this guide.
Hey guys. After 5 months of my purchase I finally achieved bootloader unlocking. Basically I am a user that has never updated to latest, I don't know if it makes it a variable if you're already on latest and try this. (I was coming from Sept 2019). So what I did was factory reset from the system menus. Then as soon as the screen went black, I did bootloader combos and straight to recovery. I factory resetted as prep, flashed DECEMBER patch, then after that finished, factory resetted again. Essentially, I followed the classic ADB exploit that has "never worked since Sept-Oct 2019" And yes I do have the VZW_001 CID and "_VZ" in GL website. Know when yours is bootlooping as soon as you reboot it, just hard reboot so it boots up quicker, I don't know what it does for it to take so long. Anyways when you get in, just setup like we'd always do, NO google account, turn off all setting requests (Data location, wallpapers, etc). Then as soon as I got in, I turned on debugging, ran the classic adb pm command, rebooted TWO times. This means as soon as I booted, i swiped to go to home, then rebooted a second time. As soon as I did that, I loaded up my wifi connection, I don't know if it matters but Im using the 5G wifi, then I load up google.com. Immediately, I already notice something strange. Google.com doesn't have a "valid SSL certificate" I thought it was weird, so I went to google.com on my PC and look certified SSL. As I knew that was weird, I was clicking around and I thought that was enough. so I went to the dev menu. OEM lock still grayed out. I went back to chrome and simply typed in "youtube" Let it load up. Then I clicked on the site. I went back to the dev menu. Still grayed out. I exited settings app and relaunched it to the dev menu. OEM unlock lit up in flying colors. I could not believe it. I instantly ticked it with 0 hesitation and rebooted immediately to the bootloader. The unlock command worked! I am now unlocked sailfish! I thank the community so much for all the hard work. I, only motivated the community to their potential. Thank you again!
Generally there are some kinds of factors.
Users have stated before if you OTA'd from menus to Latest patch, it would say "October", even though it's really december. This may make the unlocking procedure impossible. I have also not seen any marlin users report back to me yet about this method. You can still try flashing from googles site if you're already on "October = Dec".
Enjoy guys. We proved WE own these phones, and not VZW.
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?
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.
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.