yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 Questions & Answers] DA6030:
[MENTION=2659927]bobby janow[/MENTION]

I think you understand the desired outcomes, but might have a couple typos. Also, what do you mean by "on a device like the Pixel 2"? Do you mean a device with an obviously buggy bootloader? Or a device that performs a server validation of the IMEI prior to unlock? Or something else?

On the buggy bootloader, all bets are off, because it seems anyone can unlock, regardless of FRP partition state, and then load a custom ROM that will wipe the FRP partition clean. So, anti-theft security easily compromised on the Pixel 2, obviously a bug.

On a compliant device:

That's correct. This is what a "normal user" (the 99% that don't know about XDA, don't use custom ROMs, etc) should experience.

A thief should be unable to access the OS of the device (without owner's screen unlock PIN), thus unable to perform a full factory reset. They can boot into stock recovery and wipe the data partition, but stock recovery cannot wipe the FRP partition, so upon first boot they will have to enter the correct Google credentials. Assuming bootloader is locked, they will not be able to load custom code that circumvents this. They also will not be able to unlock the bootloader, because OEM unlock toggle bit has not been set (stored on the FRP partition, and only accessible from within the booted OS).

That's not exactly right. As soon as you toggle the OEM unlock switch in settings, you lose FRP. Because now a thief could boot your device to bootloader, unlock, then load custom code (Recovery or ROM) that wipes the FRP partition, eliminating the need for the owner's Google credentials.

By the way, this isn't just how Pixel devices should work, this is how ALL Android devices (6.0+, I think) should work. The only difference between devices is what conditions need to be met to toggle the OEM unlock toggle, that enables the bootloader commands. On the Pixels it is "only after a server validation of IMEI". On some carrier branded devices it is "never allow" (don't even show the toggle). On many devices it is "always allow" (but remember, this still requires being logged into the OS, so not accessible to thieves). On some devices it is "after entering a secret code from the OEM, obtained by providing the OEM your personal info and acknowledging that you void your warranty". In other words, implementation of any prereqs to unlocking is at OEM discretion.
[Google Pixel 2 Questions & Answers] Ph@nta:
Can anyone confirm this is still working? I just picked up a pixel 2 (walleye 64gb) this morning after seeing the story, but the command is giving me device already locked error. I have not inserted any Sim card yet, so I don't know if that is the issue. I am using the latest adb, pixel is on September 5 patch, build number OPD3. 170816.012
[Google Pixel 2 Questions & Answers] bobby janow:
[MENTION=632910]DA6030[/MENTION] That is some great info that I didn't know. So just to summarize, if you flip the switch even though the bootloader is still locked then anyone can bl unlock before login and thus wipe the FRP partition? Your data might be sort of safe due to a wipe on unlock but the device is no longer protected by FRP. I'll assume I have that right.

So the problem now is that with this new bug / method of unlocking anyone can unlock even without the switch being set? You issue the command and boom it's done. FRP is history with a factory reset now that it is bl unlocked? So currently thieves trying to bypass FRP means that the stolen device was neither unlocked or toggled to allow it, right? This is pretty huge if I understand it correctly. There are zero protections on a Pixel 2 now.

edit: On a device like the Pixel 2 I should have said a Pixel 2 from Google. Not like a Pixel 2 but an actual Pixel 2 from Google which allows bl unlock by checking the IMEI allow.
[Google Pixel 2 Questions & Answers] Lightn1ng:
What command are you running?

Also, update the device, that's not the newest build.
[Google Pixel 2 Questions & Answers] Ph@nta:
Using the fastboot flashing lock_critical command. Tried every other version I know as well.

And yeah, I'm downloading the update now. Was trying to do this first thing to avoid any last minute fixes that might have been pushed.
[Google Pixel 2 Questions & Answers] Lightn1ng:
It worked for me on the latest update as of now. This is a huge security hole; Verizon is going to make sure they take their time and patch it the right way
[Google Pixel 2 Questions & Answers] mr573162:
What version of magisk did you use? it's not sticking for me. i would appreciate if you could link me to what you used thanks!
[Google Pixel 2 Questions & Answers] Do0zman:
using Magisk 15.1

https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
[Google Pixel 2 Questions & Answers] D3RP_:
So far with a total of 3 wipes and two different kernels. I have had FRP enabled the whole time. I might not be wiping to the fullest extent I can, but it would seem FRP is withstanding the wipes.
[Google Pixel 2 Questions & Answers] DA6030:
How are you wiping? Only a factory reset initiated from within the OS (Settings app) will wipe the FRP (resetting OEM toggle and mandatory Google credentials). Wiping from Recovery is designed to preserve FRP, since Recovery is accessible to a thief.
[Google Pixel 2 Questions & Answers] Ph@nta:
Just updated and it works for me now. So this was obviously introduced between the OPD3.170816.012 build and the OPM1.171019.011 build
[Google Pixel 2 Questions & Answers] SoarinFerret:
Same. FRP is still working after I unlocked my bootloader using the fastboot commands, so its not as big of a deal as some are making it out to be.

That being said, I just bought the Pixel from Verizon on Wednesday, after finally deciding that an unlocked bootloader was not the end of the world. Thankful that I didn't have to settle! Its a better late Christmas present than I could have thought to ask for:)
[Google Pixel 2 Questions & Answers] maven1975:
Okay,

Let me see if I have this straight.

One can now unlock the boot loader “Permanently “ with this method?

Does one have to flash a new system image to block/avoid the bootloader from being re-locked by a system update from Verizon/Google in the future?

Is it now the same as buying an unlocked bootloader version directly from Google? (Aside from the process to unlock the bootloader)
[Google Pixel 2 Questions & Answers] Lightn1ng:
yes
[Google Pixel 2 Questions & Answers] maven1975:
There is no need for concern about it being relocked and or a need for a new image flash?

Thanks in advance.
[Google Pixel 2 Questions & Answers] neonjam:
Throw another one on. Purchased Pixel 2 new from Target mobile on the deal ending tomorrow for Verizon model with installment yesterday. Updated to 8.1. Unlocked no problem.
[Google Pixel 2 Questions & Answers] Lightn1ng:
Keep backups and check XDA before doing updates. You'll almost certainly be fine.
[Google Pixel 2 Questions & Answers] DA6030:
Exactly right. Leaving the OEM unlock toggled removes anti-theft protection, but you still have data protection afforded by the fact that a bootloader unlock will wipe the data partition (combined with other protections, e.g., encryption, lock screen).

---------- Post added at 02:07 AM ---------- Previous post was at 02:04 AM ----------

No need to worry about a future OTA re-locking the bootloader, once you're unlocked. However, if you re-lock yourself, you likely will not be able to unlock again (after this gets patched by OTA).
[Google Pixel 2 Questions & Answers] r0ck0:
Works on my pixel 2 as well.
[Google Pixel 2 Questions & Answers] Kyle_Pen:
Would also just like to add tried this on my XL and can confirm does not work. I get the same error everyone else is getting.
[Google Pixel 2 Questions & Answers] alienware777:
Picked mine up from target becaues of their amazing $250 off + verizon $300 off deal, phone became ~$100...

Anyways, IT WORKED

THANK YOU!!!!!!!

Edit: Can anyone else confirm whether they have passed safetynet? I installed TWRP then magisk through TWRP, enabled all the right settings I think and it fails.
[Google Pixel 2 Questions & Answers] Lightn1ng:
I am passing SafetyNet here.
[Google Pixel 2 Questions & Answers] jyuengel:
Passes on my Pixel 2.

OP: Your method worked on my Verizon Pixel 2, thanks. Purchased 2 months ago from the VZW business website (it's a corporate phone). Already flashed TWRP, Magisk v15.1 and installed the tethering module. Rooted and passes Safetynet.
[Google Pixel 2 Questions & Answers] thenoname:
What are the (if any) downsides to doing this? I don't plan to flash a new rom or anything, but I don't want to lose the opportunity to in the future. Does this open me up to security holes? Is there a way to save my data so after unlocking I still have everything?

Edit: Also, how much time do I have to do this? Is this something that Verizon/Google can fix without me knowing? Or would I need to take an OTA update for it to be fixed?

Edit 2: A more general question: Does the Pixel 2 do OTA updates automatically or will I be prompted to have it update? In other words, if Verizon pushes an update in the middle of the night, will my phone automatically update?
[Google Pixel 2 Questions & Answers] PuffDaddy_d:
You can use the backup feature on the pixel 2 to reload your apps and settings.

Rooting always exposes you to some level of security risk, but so does driving a car. Hasn't stopped me from doing either.

You can take as much time as you need to decide if you want to do this, but if you update past the December security patch, there is no guarantee you can get it to unlock.

OTA updates will still be pushed to your device, but will not relock your bootloader.

Correction:

They will fail to install automatically if you have root. You will have to side load from the Google OTA repository online.
[Google Pixel 2 Questions & Answers] djer34:
Confirm another one. Purchased direct from Verizon online. Running 8.1. Bootloader now unlocked. Passes safety net.

However, at first when it was unlocked, under developer options, toggle was greyed out and said the bootloader was already unlocked. Now after some time, still greyed but now says the typical connect to the internet or contact your carrier....however my bootloader is still unlocked and i still have root... is this similar to what everyone else is seeing?
[Google Pixel 2 Questions & Answers] alienware777:
Care to give some more info? Any settings in magisk you had to click? When you installed TWRP it mentioned something about /system at first, what did you choose, What version of magisk are you using, etc etc. Can't really emulate what you guys did with what you gave me ;)

Edit: Oh wtf? I do actually pass safetynet when magiskhide is on, but it turns it off every reboot! Can't get it to stick on
[Google Pixel 2 Questions & Answers] bakemcbride21:
This is VERY exciting news as I have a 2 yr old Verizon HTC 10 that gets about 6-7 hours max on it's battery these days. I am an unabashed HTC guy and only like their phones...even if it is branded as the Pixel 2 lol. Since they do not seem to be releasing anything on Big Red for the foreseeable future I will pick this up ASAP on Tuesday (I manage get phone through work so I have to go through Verizon as they will not pay for OEM/manufacturer direct phones). For $50 for the 64GB it's a no brainer now...

So a few questions...I am used to going all the way and S-Off ing my HTC phone....is this now possible with the bootloader unlocked and root through ADB commands? Or is some greater exploit needed for that?

And lastly, I imagine it is possible to get the mobile hotspot feature working without having to pay Verizon while not losing advanced calling and Volte using Magisk? lol They charge our account $30 for hotspot (we have unlimited data on our gov't account) so I have been saving $360 every year by being S-Off on all my HTC phones since the T-Bolt
[Google Pixel 2 Questions & Answers] iamnotreallyhere:
OMG this worked! Can we flash Google's factory image ? So we don't have to worry about Verizon's ota updates?
[Google Pixel 2 Questions & Answers] TonikJDK:
OTA's come based on the SIM. There is no harm in them coming from VZ, they are made by Google anyway but you should turn off updates and sideload them yourself. If you mod anything the download updates will fail anyway.
[Google Pixel 2 Questions & Answers] iamnotreallyhere:
Oh so I just flashed for no reason. Bummer. Well at least I know it works.
[Google Pixel 2 Questions & Answers] TonikJDK:
Well, now you know how and are all set up for it. Did you use the flash all bat file? For future reference if you edit it in notepad near the end you will see a -w. Remove that and it will skip flashing the user data partition which saves your data, apps and settings. A quick easy way to update.
[Google Pixel 2 Questions & Answers] jyuengel:
No problem bro, here's what I did. Not necessary the best/fastest way, but it worked for me:

In android: Enabled Developer Options, Enabled USB Debugging, adb reboot bootloader

In bootloader: fastboot flashing lock_critical

I allowed the phone to first boot and present the android setup wizard. I then powered off the the phone. Powered back on and entered bootloader mode (Power + vol down key I think)

flashed TWRP (use the instructions here, read carefully! There's an img and zip file, you need them both. To answer your question, the first boot of TWRP I did NOT swipe to allow it to make modifications. I think there was a button in the lower-right that said to keep it read-only.

After following the install instructions and flashing the TWRP zip installer, remain in TWRP to install Magisk. Download the zip from here. I used the latest v15.1. I pushed the Magisk zip to sdcard storage using the same method you pushed the TWRP zip.

Reboot into android and finish setup your phone as you normally would. Enter developer options and disable the automatic install of system updates. There are instructions elsewhere how to take OTAs while having Magisk installed.

Inside the Magisk app you can verify passing SafetyNet. I entered the Downloads menu, searched for Tethering Enabler (I have unlimted VZW data, but no tethering package). Install the module and reboot the phone. i changed no other settings inside Magisk. Magisk Hide was and is still enabled, even after multiple reboots.

Ta-Da! enjoy!
[Google Pixel 2 Questions & Answers] COMpulse:
I'm also getting the 'Device already : Locked' message. Did you find a solution?
[Google Pixel 2 Questions & Answers] Kyle_Pen:
Do you have an XL? This seems to only work for the Pixel 2, NOT the XL like some of us have tried. Just be patient and hopefully something can be done for us XL's.
[Google Pixel 2 Questions & Answers] iamnotreallyhere:
Can someone please tell us which method was used to install twrp. I'm rooted but I can't seem to get twrp. I tried both the app and flashing. Maybe I need something more specific for my device.

When I flash it says it was successful but when I boot into recovery it boots I to stock recovery.

When I use the app it ask me to download the version for my phone and I do but it never goes past that screen. The app can't find my boot partition.

Thanks in advance.
[Google Pixel 2 Questions & Answers] Kyle_Pen:
Did you follow these steps ? He seemed to lay it out pretty well.

https://xdaforums.com/showthread.php?p=75017413
[Google Pixel 2 Questions & Answers] COMpulse:
I am not on an XL. But I got it sorted out. It turns out this bootloader unlock only works after you install the 8.1 update.
[Google Pixel 2 Questions & Answers] Lightn1ng:
Load TWRP via fastboot boot, flash the TWRP zip from there. That's it. Afterwards you can root with Magisk 15.1 beta.
[Google Pixel 2 Questions & Answers] thenoname:
Do I need to install Magisk to keep the bootloader unlocked? Or is Magisk only for root? I just want to unlock the bootloader while I can, I'm not interested in rooting or installing mods at the moment.
[Google Pixel 2 Questions & Answers] TonikJDK:
It is for root. You don't have to do anything after you unlock.
[Google Pixel 2 Questions & Answers] Lightn1ng:
No need for Magisk, that's only for root.
[Google Pixel 2 Questions & Answers] D3RP_:
fastboot flashing lock_critical
[Google Pixel 2 Questions & Answers] xtacocorex:
Ended up taking the same Target/Verizon deal that at least 2 others here have done. Was able to unlock bootloader using the method prescribed prior to updating to 8.1. I did pull the SIM on the first power on to keep the phone from trying to auth with VZW.

Thanks [MENTION=7357565]D3RP_[/MENTION] for trying this out and documenting your work!
[Google Pixel 2 Questions & Answers] mamarcac:
Successfully flashed stock image via fastboot

FWIW, I flew too close to the sun with TWRP and the A/B slots and wound up stuck in boot loop (couldn't get past fastboot). The good news is I downloaded the Google stock 8.1 image after having used the unlock trick described in this thread and flashed via fastboot. Bootloader remains unlocked and it's like I got a brand new unlocked phone from Google now.

Sharing in case anyone was curious if flashing the Google stock image in fastboot was available now and this confirms it is.
[Google Pixel 2 Questions & Answers] mamarcac:
Mine is greyed out but stays as "Bootloader is already unlocked" after multiple reboots etc. However I flashed the stock Google image so not sure if that makes a difference.
[Google Pixel 2 Questions & Answers] thenoname:
So if I want the stock image with just an unlocked bootloader, do I just issue the command and stop? Do I need to do anything with TWRP even?
[Google Pixel 2 Questions & Answers] iamnotreallyhere:
which image did you download exactly? I screwed up now im stuck at bootloader still unlocked. Ive tried almost every image but I wasnt sure if I had to use the verizon and install updates in order....I fear I made things worse.
[Google Pixel 2 Questions & Answers] mamarcac:
I followed the instructions here https://developers.google.com/android/images

If you don't want to wipe then modify the .bat file by removing the "-w". I kept it because my phone was borked. The .bat did everything for me, it was beautiful haha.

The flash-all.bat erases TWRP and install the stock recovery so if you want TWRP back you'll need to reinstall it after using the stock image. Someone here may know a workaround for keeping TWRP but I don't know of one.

---------- Post added at 01:20 AM ---------- Previous post was at 01:18 AM ----------

I used the walleye 8.1 image from here (8.1.0 OPM1.171019.011, Dec 2017)

https://developers.google.com/android/images

It gets flashed in fastboot not from recovery just to be clear.
[Google Pixel 2 Questions & Answers] thenoname:
I must've really messed mine up. I had to use the deuce scripts to fix my Pixel 2 after I too flew too close to the sun with TWRP. It essentially flashed all 20ish images...
[Asus ZenWatch 3] hallevison:
Hi Everyone:

I just got a used Zenwatch 3 on ebay. Although, other notifications come through, I am not getting the usual notifications when a call comes in. The watch does vibrate, but I am use to (I have used an LG G and a Wear24) getting an indication of who is calling and giving me an option not to answer. Does anyone have any suggestions. Some details: The first thing I did when I received was watch was to unlock the bootloader and flashed janjan's ROM. Could that be a problem?

Thanks for the help!
[Asus ZenWatch 3] hallevison:
I fixed it on my own. I needed to unpair/pair (re-pair does not work :laugh:) the watch and the phone. I used https://www.xda-developers.com/pair-android-wear-without-factory-reset/ and so did not have to do a factory reset on my watch. Way cool and groovy!
[Google Pixel 2 XL Guides, News, & Discussion] Shadow/Walker:
Warning: This guide recommends the user to backup their data as this process includes an automated wipe

Hello XDA,

I'm suggesting this Tutorial for anyone aware of another person flashing a system on the phone, and I do not recommend it for TWRP users,

unlock bootloader using "fastboot flashing unlock"

do not run the fastboot critical unlock command if you did then relock it,

when you use your phone without magisk installed you won't be able to edit the OEM unlocking option from developer options.

when you install magisk the option OEM unlocking in developer options can be edited and switched off

switch off OEM unlocking option in dev options as long as long as you didn't unlock critical in the bootloader.

while the "critical partition is locked" this will not allow you to flash a full system from google website

only use OTA using recovery when you update

make sure you enable OEM unlocking option in dev option when you make internal partition changes

this method may be a wall against a full system change from thefts as when someone tries to flash a message will pop saying failed to update

even if someone tries to unlock the critical partitions using fastboot unlock_critical it will display failed as you disabled the OEM unlocking option from developer options.

if someone tries to factory reset from recovery this should trigger FRP ( factory reset protection) which will ask about the google account used before that factory reset.

I hope this somehow protects unlocked bootloader phones from any external changes without vulnerabilities or exploits,

Cheers. :fingers-crossed:
[Google Pixel 2 XL Questions & Answers] lacaprjc:
Hi guys! What is the best way to backup as much data as possible before rooting? I'm coming from an iPhone but prior to it I was on Android so I'm a little rusty. I'm aware of TiBu backups but if I recall correctly you need root to get a full backup. What I'm doing now is backing up everything through Google Drive backups and Google Photos. Is there an app that can maybe batch backup/restore apks along with their data without root? I'd like to keep as much data as possible like app data and MMS before I wipe and root.

One more thing, I'm currently on the 8.1 official firmware but came from the DP2 OTA. If I were to unenroll from the beta program, will it force a wipe? I know it forces a wipe when unenrolling and going down to the 8.0 firmware but since it's on the same version of Android, will it still require a wipe?

Thanks in advance for any help.