Related
Hi,
Im working on adding the OnePlus 1, 2 and 3 device to the Unified Android Toolkit but need some help as I don't own any of the devices.
If anyone has a device which has not been unlocked or rooted, I need to know the error message displayed in the command prompt when the fastboot oem unlock command is run without enabling oem unlocking in developer options.
I also need a few people who could help test various procedures in the Toolkit. I am modifying the Nexus Toolkit so most things will be the same.
Any help and/or knowledge about the OnePlus devices would be appreciated.
Thanks, Mark.
Questions:
1. Can you fastboot boot on OnePlus devices (fastboot boot boot.img or fastboot boot recovery.img) or does the image need flashing first. I have looked at some root procedures for the OnePlus and they fastboot flash the imge first, then reboot to bootloader and fastboot the image. Im not sure what that is about.
2. Does the standard twrp recovery image work on the OnePlus devices? I have seen a lot of posts where twrp has failed and a different twrp recovery was recommended to fix the problem (which then worked).
3. I need links to all the builds for the OnePlus 1, 2 and 3 devices. Does anyone have these?
4. Does the Universal adb driver pack from koush (CWM) work with the OnePlus? I have found the official drivers made by OnePlus for their devices but I just want to make sure they are the best ones to use. I read that samsung drivers also work.
5. I have been told that the OnePlus devices usb mode does not revert to "charging only" like all the Nexus devices and that adb commands can be sent with the device in MTP mode (Nexus devices need to be switched to PTP to communicate). Can this be confirmed.
I think this is all I need to get a working Toolkit ready within a few days.
Mark.
mskip said:
Questions:
1. Can you fastboot boot on OnePlus devices (fastboot boot boot.img or fastboot boot recovery.img) or does the image need flashing first. I have looked at some root procedures for the OnePlus and they fastboot flash the imge first, then reboot to bootloader and fastboot the image. Im not sure what that is about.
2. Does the standard twrp recovery image work on the OnePlus devices? I have seen a lot of posts where twrp has failed and a different twrp recovery was recommended to fix the problem (which then worked).
3. I need links to all the builds for the OnePlus 1, 2 and 3 devices. Does anyone have these?
4. Does the Universal adb driver pack from koush (CWM) work with the OnePlus? I have found the official drivers made by OnePlus for their devices but I just want to make sure they are the best ones to use. I read that samsung drivers also work.
5. I have been told that the OnePlus devices usb mode does not revert to "charging only" like all the Nexus devices and that adb commands can be sent with the device in MTP mode (Nexus devices need to be switched to PTP to communicate). Can this be confirmed.
I think this is all I need to get a working Toolkit ready within a few days.
Mark.
Click to expand...
Click to collapse
1. Yes,
Code:
fastboot boot boot.img
works.
2. Old firmware needs old TWRP (link) as new firmware needs new TWRP (link).
There is also hybrid recovery which supports both firmware (link) or also this thread which lets you flash right firmware with the good recovery.
3. Thread to official zip and unofficial fastboot files for the Oneplus Two. Here for the Oneplus One. Thanks to @Spannaa. I think mirrors for the Oneplus 3 are actually not available.
4. I don't know.
5. Yes, in MTP, adb commands work. But I think without USB for Marshmallow, the connectivity will go back to Charge only.
mskip is in the house ??
Sent from my ONE A2005 using Tapatalk
Last thing to do is the stock firmware flashing procedure but I think everything else is done.
Does anyone have a OnePlus 1, 2 or 3 and can test any parts of the Toolkit? Main parts to test is driver install, unlock/relock, apk and folder backup and rooting.
Firmware flash procedure should be finished by tomorrow.
Mark.
Hi Mark,
I got a OnePlus 2 with latest OOS 3.0.2
Bootloader unlocked
rooted
TWRP 3.0.2-1
I'm willing to test...
Manuel
castor31 said:
Hi Mark,
I got a OnePlus 2 with latest OOS 3.0.2
Bootloader unlocked
rooted
TWRP 3.0.2-1
I'm willing to test...
Manuel
Click to expand...
Click to collapse
Thanks, what kind of testing can you do?
If you don't want to touch your rom then the basic functions (apk backup, booting to stock/custom recovery) but ideally if you can make a twrp backup or don't mind wiping the device then I need the bootloader unlock, flash stock firmware, rooting, etc tested. If you can do the more in depth testing I can compensate you with a pro code so you can also test the ALLINONE root procedure.
Let me know as the OnePlus 2 main code has been completed and the device modules are being built now.
Mark.
Hi Mark.
OnePlus One with latest COS-13.1-ZNH2KAS1KN
stock
bootloader unlocked
not rooted
twrp backup done
Willing to help with more in depth testing if still needed.
Frank
mskip said:
Thanks, what kind of testing can you do?
If you don't want to touch your rom then the basic functions (apk backup, booting to stock/custom recovery) but ideally if you can make a twrp backup or don't mind wiping the device then I need the bootloader unlock, flash stock firmware, rooting, etc tested. If you can do the more in depth testing I can compensate you with a pro code so you can also test the ALLINONE root procedure.
Let me know as the OnePlus 2 main code has been completed and the device modules are being built now.
Mark.
Click to expand...
Click to collapse
Yes, I can test all this.
I did a dirty flash when the OOS3 community build was released in March. So its time for me to wipe my device and do a clean install...
I'm using your Toolkit with pro for my GNex, n8000 and Nexus5. would be great if you can provide a pro code.
Best
Manuel
UPDATE - TEST RELEASE FOR ONEPLUS DEVICE SUPPORT
I have finished all the work on the OnePlus modules for the 1, 2 and 3 devices and it is ready for testing.
You can download and test the Toolkit from the below link. Please remember that this IS a test version at the moment as I do not own any OnePlus devices but I have checked all the code thoroughly and don't see any problems. I am especially pleased with the unlock/lock routines and will probably implement the code for the Nexus modules if it works well.
Everything can be checked (and please do) except downloading a stock build directly from the Toolkit as I am waiting to hear back from AndroidFileHost to see if I can get direct links to use in the Toolkit. The fastboot flash routines are working though and the Toolkit will detect the storage of the device (16GB or 64GB) and flash the relevant userdata image so you do not have to do that manually anymore.
I have used the Universal USB driver pack from CWM so if anyone has not installed OnePlus drivers yet PLEASE test if this works. I did originally include the official drivers from OnePlus but they close the Toolkit when the drivers installation starts and thats not great.
The ALLINONE routine should work fine and I have sent out some pro codes to testers to check it all works.
All builds are covered and the correct version of TWRP will be downloaded depending on the build selected. Please check everything and let me know of any bugs or textual errors (as I used a lot of the Nexus code) so I can release it publicly as soon as possible.
Download Link: http://skipsoft.net/?wpdmdl=2627
Thanks, Mark.
Frudge1701 said:
Hi Mark.
OnePlus One with latest COS-13.1-ZNH2KAS1KN
stock
bootloader unlocked
not rooted
twrp backup done
Willing to help with more in depth testing if still needed.
Frank
Click to expand...
Click to collapse
Mark- I have the same version on my OnePlus One but unable to unlock the bootloader also. Can you share the procedure to do it. So far, I was trying to use the Toolbox V6 and when I do unlock bootloader in fastboot mode but phone doesnt get detected even. Please help
reply.rathi said:
Mark- I have the same version on my OnePlus One but unable to unlock the bootloader also. Can you share the procedure to do it. So far, I was trying to use the Toolbox V6 and when I do unlock bootloader in fastboot mode but phone doesnt get detected even. Please help
Click to expand...
Click to collapse
Has the bootloader been unlocked before or is this the first time you want to unlock it?
Do you have adb and fastboot drivers installed?
Do you have any knowledge of using adb/fastboot commands in the command prompt?
First thing is to make sure you have the correct drivers installed: http://www.skipsoft.net/?page_id=1302
You can try the Toolkit to see if the bootloader will unlock or I can talk you through the procedure but its a simple command (fastboot oem unlock, or from the toolkit fastboot-toolkit oem unlock).
If it won't unlock you may need to boot to stock recovery and flash a stock image back to your device.
Mark.
New device new rules/tricks
The main purpose for this thread is to post info that doesn't real justify it's own thread.
Most of what is posted is what interests me, usually in no particular order.
If you think something is missing, please share (include links or as much info you can)
General Info
Index
Have a question? Please consider asking in the
Help Thread
How to Check if you have a Verizon or Google Model from CID info
Custom Recovery info
FAQs
USB Drivers
Using ADB and Fastboot commands
Unlocking the Bootloader
Rooting
WiFi Tether
Installing new security update with fastboot.exe for a bootloader-unlocked Pixel
[GUIDE] Restore to stock after soft BRICKED Written for XL version, but a good reference
Set/Change Active System Partition with Fastboot Command in Bootloader Mode
[Re]Activate Google Voice on Pixel
46 Google Pixel XL & Google Pixel Tips and Tricks (www.droidviews.com)
https://www.androidpit.com/google-pixel-tips-and-tricks
USB Drivers for using ADB/Fastboot commands
If using Mac or Linux drivers should not be an issue.
If using Windows 10 correct drivers should already be installed but you likely will need to select them in Device manager
If drivers are correct the Pixel should be listed in Device Manager as
Android Phone
adb composite interface
An easy way to install correct drivers on a Windows PC is using
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05
Official Google Drivers
Unlocking the Bootloader - 06 Nov 2016
If it's a pure Google device just run
Code:
fastboot oem unlock
If you bought the Pixel from Verizon, Best Buy.... dePixel8 method will be required to unlock the bootloader
Note: Verizon, Build Version NDE63X, Nov 2016 can be unlocked,Builds after that cannot.
Using dePixel8
Be sure Drivers are correct
Change screen timeout to 30 mins in settings/display options
Enable Developer Options
In Settings/About Phone >Tap build version until it says "you are developer"
go back to main Settings screen
Open Developer Options
Enable ADB Debugging (in Developer Options)
Be sure ADB and Fastboot commands are working
Download dePixel8
Run in Command prompt
Code:
adb push dePixel8 /data/local/tmp
Code:
adb shell chmod 755 /data/local/tmp/dePixel8
then
Code:
adb shell /data/local/tmp/dePixel8
when you see
Code:
[+] getting there, about 20 more seconds please
open the Chrome app on the phone
then you should see
Code:
[+] done
[+] rebooting your device to bootloader mode
[+] run "fastboot oem unlock" to unlock your bootloader
[+] P.S. Pixel is made by HTC, and dePixel8 was made by beaups
[+] cheers jcase - copyright Streamlined Mobile Solutions, LLC
Discussion Thread: BL unlock for Verizon Pixel just released by murryrulz
Do not relock the bootloader
[PSA] Read before relocking your bootloader by jcase
Rooting
Requires Unlocked Bootloader
[ROOT] SuperSU by Chainfire
Hotspot/WiFi Tether
Hotspot should work out of the box for most data plans except Unlimited Data plans
Verizon Unlimited Data Plans
Rooted method
Make sure your bootloader is unlocked and you are rooted.
Instal a Root File Manager (Root Browser / ES File Explorer)
enable root access in File Manager (it's off by default in some)
browse to /System > Long press build.prop > Open in Text Editor
Scroll all the way to the bottom. Type in "
Code:
net.tethering.noprovisioning=true
.. Then save and exit. Reboot the phone and you're good to go.
Discussion Thread: Pixel Hotspot by polo2883
[Mod][Systemless Root][Pixel/Pixel XL] TetherMod - Bypass provisioning checks. by Fenny
http://forum.xda-developers.com/pixel-xl/themes/mod-tethermod-systemless-install-guide-t3501448
Non Root method
Verizon native tether subscription bypass A Pixel XL thread
Sprint WiFi Tethering Thread
[ROOT/Guide] Native Hotspot Working by stuntnmore A Pixel XL thread
Setting up and Using ADB/Fastboot (Android Debugging Bridge)
For Mac or Linux: see Can ADB/Fastboot be used on Linux and Mac?
Setting up ADB/Fastboot (Windows)
[Index] Setting up and Using ADB/Fastboot
Using ADB/Fastboot
adb commands are used in normal boot/OS or in Recovery
fastboot commands are used in fastboot/bootloader mode
Set/Change Active System Partition with Fastboot Command in Bootloader Mode
Code:
Fastboot set_active _a
Code:
Fastboot set_active _b
Installing new security update with fastboot for a bootloader-unlocked Pixel.
Note: This is a work in progress, but it should be correct.
Even if it works for the Nov update, it may need to be written for future updates
Problem:
If you have modified the stock firmware (hosts file, root, kernel, etc.), the OTA update likely will fail
Solution:
This does not factory reset, user apps and data are not removed.
This will remove your custom kernel/root/hosts/recovery...
Install Verify Drivers
see post #2
Setup ADB.exe see
[Index] Setting up and Using ADB/Fastboot
[INFO] How I restored to stock after soft bricking, then flashed new kernel & rooted by CZ Eddie
Download the system image for Sailfish (Pixel) from google
For November update, there are 3 versions:
NDE63U Europe
NDE63V US, except Verizon
NDE63X Verizon
Unzip the file
Unzip xxxxxxnde63v.zip from inside the new directory/folder
Copy files to same folder as adb.exe files (unnecessary if adb is setup as global)
Open open Command Prompt (with same directory path as firmware files)
Reboot into bootloader
Code:
adb reboot bootloader
or
Power off, Hold volume down button, power on
check your boot slot (_a or _b) and following line may need to be adjusted?
Code:
system_b system_other.img
Execute fastboot commands
Code:
fastboot flash bootloader bootloader-sailfish-*.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
Custom Kernel, Root, and other mods will need to be reflashed
Credit
[GUIDE] Update with fastboot by @firewave
Custom Recovery
Twrp links
TWRP RC1 for Pixel Devices
https://plus.google.com/+DeesTroy
Thanks a lot for this thread. Very helpful for updating my pixel. Have linked it a few times to help out. This thread should be stickied.
GeekMcLeod said:
Thanks a lot for this thread. Very helpful for updating my pixel. Have linked it a few times to help out. This thread should be stickied.
Click to expand...
Click to collapse
Thanks, hope it helps.
It is linked in the index
sd_shadow said:
check your boot slot (_a or _b) and following line may need to be adjusted?
Code:
system_b system_other.img
Click to expand...
Click to collapse
To be clear, you want the one used to match the one you're currently set to right? (My bootloader specifies boot slot a.)
sturmeh said:
To be clear, you want the one used to match the one you're currently set to right? (My bootloader specifies boot slot a.)
Click to expand...
Click to collapse
I did it the other way. System other seemed like it shouldnt be your boot slot. I updated it already and it's working so I think I got it right.
GeekMcLeod said:
I did it the other way. System other seemed like it shouldnt be your boot slot. I updated it already and it's working so I think I got it right.
Click to expand...
Click to collapse
so boot slot was a in bootloader?
you use b command?
is it now b in bootloader?
Sent from my XT1254 using XDA Labs
the Pixel has 2 system slots/partitions,
in theory you could have 2 different roms to choose from, that maybe an option in a future version of twrp
Sent from my XT1254 using XDA Labs
sd_shadow said:
so boot slot was a in bootloader?
you use b command?
is it now b in bootloader?
Sent from my XT1254 using XDA Labs
Click to expand...
Click to collapse
No, my bootloader still says my bootslot is a.
GeekMcLeod said:
No, my bootloader still says my bootslot is a.
Click to expand...
Click to collapse
thanks, sounds good
Sent from my XT1254 using XDA Labs
new
[Mod][Systemless Root][Pixel/Pixel XL] TetherMod - Bypass provisioning checks. by Fenny
http://forum.xda-developers.com/pixel-xl/themes/mod-tethermod-systemless-install-guide-t3501448
Sent from my sailfish using XDA Labs
I just tried reverting to stock and my phone is stuck in a bootloop and then eventually gets stuck on dead android with No command text. I followed all directions to the dot and I'm on boot slot b. Any ideas?
---------- Post added at 11:04 AM ---------- Previous post was at 10:43 AM ----------
Ok so I followed GeekMcLeod's advice about flashing system-other to the opposite partition. Since I was on boot_b I change the line in the OP to flash system_a and now my phone is booting. @sd_shadow I'm not sure if this is the case for everyone.
Just a short story about my experience so far with the Pixel.
When i first got my device it wanted to update. I let it update (OTA) and rebooted. Once that was done, I unlocked the bootloader, booted TWRP flashed it, rebooted TWRP and then flashed root. All was awesome, I went to reboot and noticed that TWRP shows which boot slot you're in (I was in B). I rebooted anyway and everything works as expected.
I was curious, so I booted back into TWRP, went to reboot and changed the boot slot to A, got an error but checked it again and it shows I was in fact in boot slot A. So i rebooted... it booted into non rooted, pre update android... so it looks to me that this seamless update system applies the update the opposite partition that your in. So if you're in A and take an OTA it applies it to B and then reboots into B (updated) and the opposite will happen if you take the OTA while in B. All apps and data you've collected is shared with either system partition.
So, in theory we could take the OTA as long as we flash the recovery and (possibly) boot images before downloading and applying it. We would only have to flash TWRP and root again.
And I agree, it looks like we should be able to dual boot two different ROMS, maybe even kernels without too much messing around.
I'm sure this is not new news but I just wanted to share and maybe someone will correct me or learn from it.
thanks for the replies, good stuff
Sent from my sailfish using XDA Labs
Moderators could not provide any evidence
I believe this is why the bootloader is locked is my phone. The cid says it's a Verizon but it's also a project fi and carrier unlocked Google Pixel XL. Is there anyway to modify the boot image so it's RO.BOOT.FLASH.LOCKED=0 I believe that will unlock the bootloader if there was just a way to modify it so you could sideload the modified boot through stock kinda like how you could modify the boot images of Samsung devices and flash them in Odin through the stock bootloader. Any thoughts.
Who would be interested in trying this I modified the boot image in the ramdisk so you can turn oem unlock on and unlock the bootloader.. I didn't want to jump to link posting I wanna see who is interested. You have to sideload the boot image through the bootloader but it installs like it's official.. 32 gb pixel XL only this is the 8.1 dev preview boot image so you need to have 8.1 installed.
Links removed due to suspicious moderator activity and possible tampering with the links while they had them removed.
I really think a modified stock boot image which can be side loaded through the stock bootloader will solve the problem about the Verizon Google Pixel XL having a locked bootloader cause even if the bootloader is locked like it is now once you unlock it via a modified boot image it opens it up for flashing you wouldn't need some fancy tool which you'd have to run on a computer to unlock it or a oem unlock code you could modify the locked boot image to be the key into the bootloader.
What you thinking? You thinking support could be added for the Verizon Pixels once again I know there was development at one time but due to them patching the tool used to unlock the bootloader it stopped after a while well with this you could bring back development for it
We also wanted to make sure there was no central point of failure, where one industry player could restrict or control the innovations of any other. The result is a full, production-quality operating system for consumer products with source code open for customization and porting.
Google stated that on it's Android open source project right now with the locked bootloaders Verizon is basically restricting and controlling the innovations of how the device could be used and Google doesn't go with that that is why the Google store edition pixels are unlocked so I think setting the example that there's a permanent way to keep the Verizon bootloaders unlocked by modifying the boot images will show Verizon that they need to remove some policy's they have in place cause in the end as customers the old saying is the customer is always right.
Actually now that I think about it I can modify the ramdisk by unpacking the boot image and taking a text editer and going in then you can edit it to say 0 then repack it and flash it via side load i believe that's how you do it. I'm pretty sure I can do that. Doesn't seem too hard to do.
I am also seeing in the cid that there's RO.BOOT.OEM_UNLOCK_SUPPORT=0 it needs to be kept at RO.BOOT.OEM_UNLOCK_SUPPORT_0 I believe and the boot hardware is samsungs
This all started out as a question but I answered my own question. Plus it's nice to have a unlocked bootloader. Cheers.
Did anyone tried to unlock it ?
If you wanna see this cid information for yourself get the app called cid getter from the play store it doesn't have the best reviews but it at least gives you the right cid information and shows you how the bootloader was locked
user-67 said:
If you wanna see this cid information for yourself get the app called cid getter from the play store it doesn't have the best reviews but it at least gives you the right cid information and shows you how the bootloader was locked
Click to expand...
Click to collapse
did you start with an unlocked bootloader and were you also able to sideload the modified boot.img and then able to unlock the bootloader? also, is this on a VZW Pixel or XL?
user-67 said:
I really think a modified stock boot image which can be side loaded through the stock bootloader.....
Click to expand...
Click to collapse
You can't do that if the bootloader is locked.
Mod Message: OP could NOT provide photo/video evidence on it. Proceed at your own risk!
Click to expand...
Click to collapse
Who would be interested in trying this I modified the boot image in the ramdisk so you can turn oem unlock on and unlock the bootloader.. I didn't want to jump to link posting I wanna see who is interested. You have to sideload the boot image through the bootloader but it installs like it's official.. 32 gb pixel XL only this is the 8.1 dev preview boot image so you need to have 8.1 installed.
Never mind here's the link for pixel XL 8.1 dev preview https://drive.google.com/file/d/1ehXD2LVOBoRbs1EDh33nLyw7I0aRyOqH/view?usp=drivesdk
Here's the link for pixel 8.1 dev preview
https://drive.google.com/file/d/19xvVkadK79p6OLx5LePZSRA7V201ortd/view?usp=drivesdk
Here is the link for the pixel 2... 8.1 Dev preview
https://drive.google.com/file/d/1M-sgp33NTrrlS12SY0xLQxrec44ZejJl/view?usp=drivesdk
Bump
If you didn't know the part that controls oem unlocking is in the boot image. You can go crazy trying to break into the actual bootloader partition but you don't need all that.
I have a pixel (not xl) and i curious, if the bootloader is locked how can i sideload the boot.img?
Sideload is the install of a custom image what you have here is a modified custom boot image which install like it's stock so in terms sideload is what it is through the bootloader
When it comes to boot images I'm good at tweaking them here's a old project it was just a test build to see if it would actually work.
Custom adb root boot image with chainfires adbd kernel from adbd insecure as the phones adbd.. it has a few other tweaks and a custom permissive kernel and systemless root from chainfires supersu... the rsa fingerprint doesn't pop up when you connect a computer but it can be bypassed with adb in a custom recovery and found out if you use adbd insecure and let it patch chainfires adbd kernel it makes the phone as attached device in for adb devices instead of the plain unauthorized device and vendor keys not set. ... if you use it now you get adb root access and regular root access with the su binary but due to the rsa fingerprint not popping up you have to use adbd insecure until a recovery comes out cause it bypasses rsa fingerprint.. credits to come... to use adb root access you need a custom recovery with adb... adbd insecure app... adb on you're computer.... android sdk/android studio... java... boost mobile j7 running build f3 but you can just run systemless root until a recovery comes through. You can grab systemless root from here http://forum.xda-developers.com/gala...j700p-t3430185
And use it with the boot image.. but i just added systemless root patches to the boot image so all you have to do is flash the boot image.
user-67 said:
Who would be interested in trying this I modified the boot image in the ramdisk so you can turn oem unlock on and unlock the bootloader.. I didn't want to jump to link posting I wanna see who is interested. You have to sideload the boot image through the bootloader but it installs like it's official.. 32 gb pixel XL only this is the 8.1 dev preview boot image so you need to have 8.1 installed.
Nevermind here's the link https://drive.google.com/file/d/1ehXD2LVOBoRbs1EDh33nLyw7I0aRyOqH/view?usp=drivesdk
Click to expand...
Click to collapse
Will you be able to provide the boot image for Verizon pixel on 8.1? I would be interested in trying it. Thank you.
i definitely want to try this, i have the VZW Pixel, not upgraded to 8.1 yet, but will if this is made available for the pixel!
If you all give me a copy of your boot.img in Img format I'll do the ramdisk changes.. you can get a copy by downloading the factory image you want then on your phone go to the play store and get the app zarchiver then go in and open the factory image and copy the boot image into internal storage then hit the Google drive and post a link and I'll get right on it.
Introduction
Hello everyone, this is a guide to assist you with customizing your Pixel 2 XL! I will be going over installing fastboot and adb, unlocking your bootloader, how to flash the factory images for clean flashes and upgrades, and how to root. Please feel free to ask any questions if you need clarification. Enjoy!
This information has been distilled from Google's official factory image site and the Magisk thread.
Installing fastboot and adb
Thankfully, Google has provided just adb, fastboot, and systrace as a simple zip file, making this process super easy. You MUST be on at LEAST 26.0.2 for the commands in this guide to work. When in doubt, grab the latest copy and install them using the following instructions.
SDK Platform-Tools for Windows
SDK Platform-Tools for Mac
SDK Platform-Tools for Linux
Windows:
Unzip the folder somewhere on your hard drive.
Go to the folder containing the adb and fastboot files and type "cmd" in the path bar at the top.
A command prompt should open with the current folder showing on the prompt.
Type the following commands:
Code:
adb --version
fastboot --version
You should see some information appear. If that is the case, you were successful!
Mac/Linux:
Unzip the folder somewhere on your hard drive.
Navigate to that folder with your terminal.
Run the following commands:
Code:
sudo install adb dmtracedump e2fsdroid etc1tool fastboot hprof-conv make_f2fs mke2fs mke2fs.conf sload_f2fs sqlite3 /usr/local/bin
sudo mkdir -p /usr/local/lib64
sudo install lib64/libc++.so /usr/local/lib64
Type the following commands:
Code:
adb --version
fastboot --version
You should see the version information, along with telling you they are installed to /usr/local/bin. If so, you were successful!
Unlocking the bootloader
WARNING: This WILL wipe your entire phone. Please make copies or backups of any important data. This can also go wrong rendering your device inoperable. Proceed with caution.
On your phone, open Settings, navigate to "System" then "About phone", and tap on the build number 7 times.
Go one menu up, click on "Developer options", and turn on USB debugging and OEM unlocking.
In your terminal, type the following command:
Code:
adb reboot bootloader
Next, decide if you want to do a standard unlock or critical unlock. A critical unlock allows you to directly flash bootloader files, otherwise you will get an error when you try to do so.
Depending on what you decided in the previous step, run the following commands:
Code:
fastboot flashing unlock
(OPTIONAL)
Code:
fastboot flashing unlock_critical
Follow the prompts on your device then reboot!
Flashing factory images
NOTE #1: If you have mounted /system as rw at any point (like in TWRP), you must upgrade using the factory image method. OTAs will fail because they cannot verify the integrity of the disk since its verity data has been changed.
NOTE #2: Flashing the factory images requires an unlocked bootloader. Flashing the OTA zips does not (but if anything goes wrong, you may not be able to recover without an RMA).
Updating to a new release (factory image):
Download the latest factory image from Google's website.
Reboot into the bootloader:
Code:
adb reboot bootloader
Unzip the factory image.
Inside you will see a bootloader image, a radio image, an image zip file, and a couple of flash scripts.
If you are on Windows, open the "flash-all.bat" file in a text editor. If you are on Mac or Linux, open the "flash-all.sh" instead.
Remove the "-w" flag before the fastboot command towards the end of the file. This will prevent fastboot from formatting your device.
Run the flash all script! Open a command prompt, navigate to the folder with the script, and run one of the following commands:
Windows:
Code:
flash-all
Mac/Linux:
Code:
./flash-all.sh
Reboot once it is finished!
Updating to a new release (OTA zip):
Download the latest OTA zip from Google's website
Reboot into recovery:
Code:
adb reboot recovery
Hold down the power button and push volume up
Select "Apply update from ADB"
Run the following command from the folder containing the OTA zip:
Code:
adb sideload <zip_name>.zip
Reboot once it is finished!
Clean flashing a factory image (wipe everything):
Download the latest factory image from Google's website
Reboot into the bootloader:
Code:
adb reboot bootloader
Unzip the factory image.
Run the flash all script! Open a command prompt, navigate to the folder with the script, and run one of the following commands:
Windows:
Code:
flash-all
Mac/Linux:
Code:
./flash-all.sh
Reboot once it is finished!
Rooting with Magisk
NOTE #4: This section assumes you are not going to install TWRP. If you are, skip to the next section and just flash the latest Magisk zip after installing TWRP.
Download the Magisk zip from the official thread and install the manager from the zip.
Grab a boot image to patch (either the one from the latest factory image or a custom kernel one) and push it to your device:
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Reboot into the bootloader:
Code:
adb reboot bootloader
Flash the boot image and reboot.
Code:
fastboot flash boot patched_boot.img
fastboot reboot
Open Magisk Manager and you should be rooted!
Installing TWRP
NOTE #5: If you just want to temporarily boot TWRP to flash Magisk and your custom kernel, you can just skip flashing the installer zip in this process.
NOTE #6: TWRP can be unstable at times given the way that security has been set up on this device (lack of decryption, failing to boot, etc).
Download both the TWRP image and zip installer from the official site.
Temporarily boot the TWRP image.
Code:
fastboot boot <path_to_twrp_image>
Flash the TWRP installer zip.
Reinstall Magisk and your custom kernel if you had them.
Reboot and profit!
Common issues
Outdated fastboot/adb: This device requires the latest fastboot and adb binaries to work properly. A lot of common quick adb/fastboot installation guides link to installers that are old. Please manually install the latest using the information at the beginning of the thread!
Using a USB-3.0 or USB-C port: Some newer USB ports do not work with fastboot. Issues manifest as weird errors during a flash. Use a different USB cable/port.
Closing statements
If there are any procedures you would like to see added (like flashing a custom kernel or booting TWRP), I am happy to add them if requested. Also, when requesting help, please be as specific as possible where you get confused. I want this guide to be clear as possible.
Reserved
Reserved
Thanks @nathanchance I've been trying to keep track of things to do once my taimen ships, and I've been waiting on a "how-to" post. Thanks again!
Thanks so much for your efforts. These are much appreciated. Just what we needed for Pixel 2 XL.
One can only hope that we eventually get SU Root, TWRP and Custom ROMs. The Pixel 1 XL's development was disappointing. Hopefully this phone has more.
To Ubuntu users: the
Code:
android-tools-adb
android-tools-fastboot
packages won't necessarily work. The fastboot from the repos didn't have the same options as the one from the zip from Google. So if you are getting a usage dialog after running fastboot, that is why.
Thank you ninja!
The boss is back. Thanks for the guide man
followed from the nexus 6p threads, waiting for TWRP to get stable and then it's on!
I always took the noobish method and used twrp...
If my device is bootloader unlocked and in developer mode, and in a chance I am stuck in a bootloop, can I fastboot adb the stock image and be back up and running?
Question is: with fastboot enabled, can I recover if I F up installing magisk/root?
Mods...please make this thread a sticky:good:
pvtjoker42 said:
followed from the nexus 6p threads, waiting for TWRP to get stable and then it's on!
Click to expand...
Click to collapse
That's exactly what I'm doing. Waiting for TWRP, then I will buy the pixel. 6P is working perfect at the moment, after a battery replacement.
pvtjoker42 said:
followed from the nexus 6p threads, waiting for TWRP to get stable and then it's on!
Click to expand...
Click to collapse
choder said:
That's exactly what I'm doing. Waiting for TWRP, then I will buy the pixel. 6P is working perfect at the moment, after a battery replacement.
Click to expand...
Click to collapse
Not to sound pessimistic but if that's what you are waiting for, you'll probably never get this device lol. Even the Pixel 1's TWRP isn't the most stable thing (it's close but still).
Sent from my Pixel 2 XL using XDA Labs
nathanchance said:
Not to sound pessimistic but if that's what you are waiting for, you'll probably never get this device lol. Even the Pixel 1's TWRP isn't the most stable thing (it's close but still).
Click to expand...
Click to collapse
Oh no So you're saying we might never get a stable TWRP and no good custom ROMs for Pixel 2 XL?
Any idea whether PureNexus or any of the other custom ROMs of Nexus/Pixel will come to Pixel 2 XL?
Based on my experience custom ROMs/Kernels can transform a mid range device to Flagship performance and features. I am using the 2 XL and still within the return window. If it is speculated that this phone will not have much development, then I might as well return it and continue using OG Pixel XL or get a OnePlus. Thanks.
iamjimmy said:
Oh no So you're saying we might never get a stable TWRP and no good custom ROMs for Pixel 2 XL?
Any idea whether PureNexus or any of the other custom ROMs of Nexus/Pixel will come to Pixel 2 XL?
Based on my experience custom ROMs/Kernels can transform a mid range device to Flagship performance and features. I am using the 2 XL and still within the return window. If it is speculated that this phone will not have much development, then I might as well return it and continue using OG Pixel XL or get a OnePlus. Thanks.
Click to expand...
Click to collapse
I'm saying if that is your only deciding factor for owning this device, considering getting another like the OnePlus 5 which has a guarantee of that. TWRP may get stable eventually but it may not. I personally love the kernel source that Google puts out and have been digging stock so I'm comfortable with just root with my kernel. If you aren't, then doing something else may be a good idea.
ROMs may end up coming in the form of images though (like system and boot and such), negating a need for TWRP. We will have to see.
Sent from my Pixel 2 XL using XDA Labs
That's so strange. Why is that? It's a pixel which is the successor to Nexus phones so I'm not sure why the line of phones would have a hard time with twrp and custom ROM flashing.
JDROIDS said:
That's so strange. Why is that? It's a pixel which is the successor to Nexus phones so I'm not sure why the line of phones would have a hard time with twrp and custom ROM flashing.
Click to expand...
Click to collapse
Well few reasons...
1. A/B partitioning makes it so the boot and recovery partition are unified, meaning when you flash a ROM, you need to reflash TWRP.
2. With the Pixel 2 (XL), as stated in the TWRP thread, the secure crypto chip requires a rewrite of some things into Java, which will take time.
The Pixel isn't really a successor to the Nexus line because these are geared purely to consumers. It's Google's iPhone.
Sent from my Pixel 2 XL using XDA Labs
nathanchance said:
I'm saying if that is your only deciding factor for owning this device, considering getting another like the OnePlus 5 which has a guarantee of that. TWRP may get stable eventually but it may not. I personally love the kernel source that Google puts out and have been digging stock so I'm comfortable with just root with my kernel. If you aren't, then doing something else may be a good idea.
ROMs may end up coming in the form of images though (like system and boot and such), negating a need for TWRP. We will have to see.
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply.
That is unfortunate. If we can't have custom Kernels, we miss out on features such as color control, calibration, sound amplication , bluetooth high performance audio, USB fastcharge, vibration strength control and other mods. Will this be developed in any Kernel? I'm assuming it will take a long time (if ever) to get Elemental X, Franco Kernal or anything similar.
Also for Root, I just unlocked my bootloader. If I use the Magdisk Root Manager for Root, is there any way to flash next month's security patch WITHOUT factory reset. With SU root of Pixel XL, it was usually as simple as flashing factory images (without wipe switch) and then flashing SU plus kernel.
For Magdisk, will a full wipe or unroot needed before flashing an update?
iamjimmy said:
Thanks for the reply.
That is unfortunate. If we can't have custom Kernels, we miss out on features such as color control, calibration, sound amplication , bluetooth high performance audio, USB fastcharge, vibration strength control and other mods. Will this be developed in any Kernel? I'm assuming it will take a long time (if ever) to get Elemental X, Franco Kernal or anything similar.
Also for Root, I just unlocked my bootloader. If I use the Magdisk Root Manager for Root, is there any way to flash next month's security patch WITHOUT factory reset. With SU root of Pixel XL, it was usually as simple as flashing factory images (without wipe switch) and then flashing SU plus kernel.
For Magdisk, will a full wipe or unroot needed before flashing an update?
Click to expand...
Click to collapse
Custom kernels will absolutely be a thing on this device. I already have mine publicly available. I haven't looked into external features (and probably won't be able to for a bit as I am rather busy) but they will certainly come.
It's the same process for the Pixel 2 XL except you need to patch the boot image you are doing to flash first in Magisk Manager then flash it after the factory images.
nathanchance said:
I'm saying if that is your only deciding factor for owning this device, considering getting another like the OnePlus 5 which has a guarantee of that. TWRP may get stable eventually but it may not. I personally love the kernel source that Google puts out and have been digging stock so I'm comfortable with just root with my kernel. If you aren't, then doing something else may be a good idea.
ROMs may end up coming in the form of images though (like system and boot and such), negating a need for TWRP. We will have to see.
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I need Verizon, so the OnePlus 5 is out of the question. Maybe once the V30 source is released and bootloader unlocked that may be worth looking at. But it probably won't get much development anyway.
Possibly the Essential Phone (seems to be a good deal now, and it has root and twrp)
I probably would be okay with kernel tweaks and root on the Pixel 2 XL.
I'm not entirely sure if this is old news or not, but if you have the Verizon Pixel 2 like I do, and have been depressed that we can't unlock the bootloader thanks to the Evil Verizon people, and want to stick it to the Evil Verizon people and still Unlock the Bootloader for whatever purpose (Root, TWRP or Custom recovery, Custom ROM, Kernel, etc...) we are in luck! :good:
Even though the Evil Verizon people have Disabled the OEM Unlocking in Developer Options.
There is a fastboot command that bypasses the disabled oem unlocking. :victory:
This only works for the Pixel 2 not the Pixel 2 XL variant.
Thanks to @b00ster23 for the following;
Correct on the steps, including the entire discussion found here. https://forum.xda-developers.com/pix...el-2s-t3726294
Big Thanks goes to @D3RP_ for finding the command.
***PATCHED BY OUT-OF-CYCLE JANUARY UPDATE***
If you have received the OTA patch for your pixel2, and now are on OPM2.171019.016, you will no longer be able to run the command. And downgrade is not available at this time.
As of 1/24/2018 users who have purchased new phones have been able to remove the SIM, refuse internet (WiFi) connection at the initial startup. After completing the initial setup, you can sideload 8.1 to take advantage of the command in the OP. If you connect to the internet with WiFi or with your SIM, chances are high you will receive the update and this method WILL NOT work. To date, there are no other ways to unlock the bootloader on VZW PIX2 other than this method.
Instructions to sideload stock OTA's are found here along with the downloads. https://developers.google.com/android/ota
Once again, DO NOT USE 8.1.0 (OPM2.171019.016, Jan 2018, Verizon) but instead use 8.1.0 (OPM1.171019.013, Jan 2018) The command is not available on 8.0
Click to expand...
Click to collapse
Unlocking the Bootloader WILL WIPE YOUR DEVICE!! so backup important files.
To Unlock your Verizon Pixel 2, follow the steps below..
Install ADB/Fastboot Drivers
Enable Developer Options
Enable USB Debugging in Developer Options
Plug Pixel 2 into PC
Open a Command Prompt window;
In Command Prompt, type
Code:
adb start-server
and hit ENTER
If you see * daemon started successfully *
continue to next step
In Command Prompt, type
Code:
adb devices
and hit ENTER
If you see "List of devices attached" as well as "Your Devices Serial Number device or unauthorized"
continue to next step
On Pixel 2 - Allow PC for USB Debugging
In Command Prompt, type
Code:
adb reboot bootloader
Once your Pixel 2 has rebooted into the bootloader
In Command Prompt, type
Code:
fastboot flashing lock_critical
and hit ENTER
Then follow the instructions on your Pixel 2 to finish Unlocking Bootloader.
If you have successfully unlocked your bootloader on reboot you should see;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yup. Just did this with my Verizon Pixel 2 and it went through swimmingly.
OP any chance you can include step by step instructions on how to load TWRP and magisk? I did mines already but I was a bit confused with loading (pushing) twrp.img via adb and also installing magisk.
Correct on the steps, including the entire discussion found here. https://forum.xda-developers.com/pixel-2/help/maybe-stupid-question-verizon-pixel-2s-t3726294
Big Thanks goes to @D3RP_ for finding the command.
***PATCHED BY OUT-OF-CYCLE JANUARY UPDATE***
If you have received the OTA patch for your pixel2, and now are on OPM2.171019.016 or LATER, you will no longer be able to run the command. And downgrade is not available at this time.
As of 1/24/2018 users who have purchased new phones have been able to remove the SIM, refuse internet (WiFi) connection at the initial startup. After completing the initial setup, you can sideload 8.1 to take advantage of the command in the OP. If you connect to the internet with WiFi or with your SIM, chances are high you will receive the update and this method WILL NOT work. To date, there are no other ways to unlock the bootloader on VZW PIX2 other than this method.
Instructions to sideload stock OTA's are found here along with the downloads. https://developers.google.com/android/ota
Once again, DO NOT USE 8.1.0 (OPM2.171019.016, Jan 2018, Verizon) but instead use 8.1.0 (OPM1.171019.013, Jan 2018) or 8.1.0 (OPM1.171019.011, Dec 2017)The command is not available on 8.0
***UPDATED 6/11/18***
https://forum.xda-developers.com/showpost.php?p=75945799&postcount=167 As of 3/19/18 People are still finding VZW Pixel2 phones in stores with the December patch. Not sure if VZW/Google are shipping newer patched phones at this time, but a good sign to users still looking for a phone they can unlock.
https://forum.xda-developers.com/showpost.php?p=75908059&postcount=1 Another user confirms that his phone was shipped "It was still on 8.1.0 (OPM1.171019.011, Dec 2017)"
***UPDATED 6-9-18*** https://forum.xda-developers.com/showpost.php?p=76757116&postcount=239 Another user received the 128GB White variant of the Pixel2 with the December build and was able to unlock successfully
***UPDATED 6-14-18*** https://forum.xda-developers.com/showpost.php?p=76795831&postcount=265 Users are are now getting phones directly from Verizon and the store with .016 or later factory installed.
To review, the command referred in the OP is available in 8.1 and not 8.0. Which means that you can upgrade to a compatible version of Android OS to take advantage of the command. However, your phone CANNOT be on ANY build OPM2.171019.016 or later, as the command was patched. Please see the attached table. Some users have been able to find phones in stores, and from surplus. However some newer phones are now being shipped with the latest security updates (OPM2.171019.016 and older.)
The best way to ensure you can unlock the BL on your VZW PIX2 is going to the store and physically verifying the patch revision on device.
nes4r2 said:
OP any chance you can include step by step instructions on how to load TWRP and magisk? I did mines already but I was a bit confused with loading (pushing) twrp.img via adb and also installing magisk.
Click to expand...
Click to collapse
I second this. After having read through the instructions for them both, it's still incredibly hard to understand what needs to be done.
I thought you didn't want to use the unlock critical command on pixel 2 and only the xl?
dobbs3x said:
I thought you didn't want to use the unlock critical command on pixel 2 and only the xl?
Click to expand...
Click to collapse
Not sure where you heard NOT to use the unlock_critical_ command. However, if there is a reason not to, please post your findings. Keep in mind this is for the VZW Variant ONLY that is being referenced. (See OP)
nes4r2 said:
OP any chance you can include step by step instructions on how to load TWRP and magisk? I did mines already but I was a bit confused with loading (pushing) twrp.img via adb and also installing magisk.
Click to expand...
Click to collapse
I'll write up a little how to on flashing TWRP and Magisk first thing tmrw morning and add it to the original post.
Shiestie said:
I'll write up a little how to on flashing TWRP and Magisk first thing tmrw morning and add it to the original post.
Click to expand...
Click to collapse
I would add disclaimers....links to other posts where information is already available.... Reference this post is for unlocking VZW pixel2 only.... Give credit to the XDA user that found the command...
Personally it's difficult to try and hash thru data in a forum post when the scope of information is too broad or double-posted. I like to have steps and supporting discussion for each step... My 2 cents about guide posting
Ordered my VZW Pixel 2 on 12/31, received it yesterday. It automatically updated to the January OTA. This morning, I ran the above steps and the bootloader is now unlocked. Easy Peasy. Thanks @Shiestie for the guide and @D3RP_ for the discovery!
SoloTSi97 said:
Ordered my VZW Pixel 2 on 12/31, received it yesterday. It automatically updated to the January OTA. This morning, I ran the above steps and the bootloader is now unlocked. Easy Peasy. Thanks @Shiestie for the guide and @D3RP_ for the discovery!
Click to expand...
Click to collapse
Oh. My. God. AAHHHHH! Could you go over to My thread And post a screenshot (cover your serial) and a picture of your bootloader screen?
I'm trying this on a Pixel 2 which I received today (have not connected it to any network yet to ensure I avoid OTAs) but when I run fastboot flashing lock_critical I just get: FAILED (remote: Device already : locked!)
Any ideas? Thanks!
---------- Post added at 11:04 PM ---------- Previous post was at 10:54 PM ----------
According to this thread, you need the Android 8.1.0 OTA before you can unlock it. https://www.reddit.com/r/GooglePixel/comments/7ms5ke/verizon_pixel_2_bootloader_unlock/drxs086/
UPDATING TO 8.1 LET ME UNLOCK IT!
Worked for me as well, thanks for the post
Sent from my Pixel 2 using Tapatalk
D3RP_ said:
Oh. My. God. AAHHHHH! Could you go over to My thread And post a screenshot (cover your serial) and a picture of your bootloader screen?
Click to expand...
Click to collapse
Will do.
Just tried it and it worked fine for the January patch!
b00ster23 said:
Not sure where you heard NOT to use the unlock_critical_ command. However, if there is a reason not to, please post your findings. Keep in mind this is for the VZW Variant ONLY that is being referenced. (See OP)
Click to expand...
Click to collapse
It says it on the google developers website here ----> https://developers.google.com/android/images
scroll down a little and you will see this --->
" If necessary, unlock the device's bootloader using one of the following methods:
If you are updating a Nexus or Pixel device that is manufactured in 2015 or later (for example, a Nexus 5X, Nexus 6P, Pixel, Pixel XL, Pixel 2 or Pixel 2 XL device), run this command:
fastboot flashing unlock
Note: the 'flashing unlock' command is only available with fastboot version 23.0.1 or later. The latest available version of fastboot can be downloaded from SDK Platform Tools.
For Pixel 2: To flash the bootloader, Pixel 2's boot loader must be updated to at least Oreo MR1's version first. This may be done by applying an over-the-air (OTA) update, or sideloading a full OTA with the instructions on that page.
For Pixel 2 XL only: the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command, and should NOT be done on other devices:
fastboot flashing unlock_critical
If you are updating an older device, run this command:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
See Unlocking the bootloader for more detailed instructions. "
dobbs3x said:
It says it on the google developers website here ----> https://developers.google.com/android/images
scroll down a little and you will see this --->
" If necessary, unlock the device's bootloader using one of the following methods:
If you are updating a Nexus or Pixel device that is manufactured in 2015 or later (for example, a Nexus 5X, Nexus 6P, Pixel, Pixel XL, Pixel 2 or Pixel 2 XL device), run this command:
fastboot flashing unlock
Note: the 'flashing unlock' command is only available with fastboot version 23.0.1 or later. The latest available version of fastboot can be downloaded from SDK Platform Tools.
For Pixel 2: To flash the bootloader, Pixel 2's boot loader must be updated to at least Oreo MR1's version first. This may be done by applying an over-the-air (OTA) update, or sideloading a full OTA with the instructions on that page.
For Pixel 2 XL only: the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command, and should NOT be done on other devices:
fastboot flashing unlock_critical
If you are updating an older device, run this command:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
See Unlocking the bootloader for more detailed instructions. "
Click to expand...
Click to collapse
Interesting. I may take some time later to understand exactly what the command is intended to do. I have a feeling that the command was probably intended for an lock/unlock to other areas, but because of BigRed's config the phone defaults to the bootloader unlock option first. It's like giving the command to upgrade windows, and the setup displaying a format option without actually giving the format command. Speculation here...
Either way... Tick Tick Boom goes the dynamite
b00ster23 said:
Interesting. I may take some time later to understand exactly what the command is intended to do. I have a feeling that the command was probably intended for an unlock to other areas, but because of BigRed's config the phone defaults to the bootloader unlock option first. It's like giving the command to upgrade windows, and the setup displaying a format option without actually giving the format command. Speculation here...
Either way... Tick Tick Boom goes the dynamite
Click to expand...
Click to collapse
You aren't using fastboot flashing unlock_critical to unlock the verizon Pixel 2. It's fastboot flashing lock_critical. Either way, yes, it shouldn't do what it does.
I can confirm that it worked on mine this morning. I just used the fastboot flashing lock_critical command I found in the article that was posted out on the main site. Hate having to put all of my stuff back but it was worth it. That said, can I leave the standard recovery on the phone and continue to get VZ updates and not have it relock the bootloader? Or should I definitely install TWRP ? If I do that will I still get OTA updates or will I have to start doing them manually?
robocuff said:
You aren't using fastboot flashing unlock_critical to unlock the verizon Pixel 2. It's fastboot flashing lock_critical. Either way, yes, it shouldn't do what it does.
Click to expand...
Click to collapse
Correct... I should have stated lock not unlocked...edited