yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
I am under the belief that it's better just to consider it a "global statement"...and it may very well be you were able to get away with re-locking without consequence because you did not unlock_critical. But, as I understand it, the newer versions of the OS (Pie, Q, maybe even 8.1+) Google removed the need and option to unlock_critical. I can't remember where I read this, but I'm sure it can be found easy enough...

I've read/seen some of those "numerous stories on the forum" where it

seems

that they did everything correct and still came out with a "paper weight"!!! Like, they got a Full Factory image, did the flash-all with "-w" intact, and did not turn off USB debugging (I could be wrong about this because, loading the OS stock has USB debugging and Developer options disabled to being with...) and disable OEM unlocking, and ended up with a "corrupt" or invalid/can't find OS issues!!! Seeing all of those "stories" and reading how they did steps that I would take, and still came out in a real bad way, reading til your eye's bleed or no-reading, I just wouldn't do it -- or even say it's "alright" or suggest trying it -- unless absolutely without-any-other-option necessary....

Yeah...i'm pretty traumatized...
[Google Pixel 2 XL Guides, News, & Discussion] johnlgalt:
ISTR also that when I first installed a clean version of Pie the instructions I saw (more than likely here, as this is my first stop for info about the Taimen) said critical was optional, so I tied it without critical and it worked.

But I also did my reading. I installed the system image, rebooted the phone, let it boot into Android, then without setting anything up, rebooted back to the bootloader, locked it, then rebooted to recovery and performed an FDR manually. I also, at the time, was not rooting nor installing any other third party mods - so it was pure stock (as you can see from the strikeouts in my sig).

Finally, I'm confident in my abilities to figure out a fix for things tech related. So I'm not worried about doing it on my devices. However, I'm not the one that goes around saying "It's easy, peasy!" like a lot of n00bs were doing with older devices because of toolkits and rooting apps. Hell, I learned how to root the OG DROID manually, way before Peter (I think he was first, don't get mad if I forgot someone in the interim) released the first, uh, either it was flashable root or automatic root (been so long I forgot).

I give all the necessary warnings an caveats to anyone else who wants to do what I do, especially if I feel they are even remotely less technologically inclined than I am.

I pay for my devices - so I'm willing to put mine on the line if need be. I won't advocate (nor be held responsible) for what anyone else does.

In all my dealings with things like this (and, on a similar note, BIOS flashing, of which I have probably done in excess of 200 in my lifetime) I've never lost any of my own devices, and with BIOS flashing, never had one go badly for me. But, if you check my posts elsewhere, when I am getting ready to do something like this with the potential for bricking, I ask, ask and ask some more until I am sure of how I want to proceed.

IMO, well over 75% of the problems encountered that I read about are user error.

Still though, for people not as technologically adept, I agree - global warning, don't re-lock your BL unless you know WTF you're doing - and can fix it yourself without whining in here about it.
[Google Pixel 2 XL Guides, News, & Discussion] Sam Nakamura:
I'm one of them! :angel:

I just locked the bootloader of my Taimen few days ago for reasons and it runs just fine now! Before this I had flashed TWRP, a custom kernel and Magisk, however flashing the latest full factory image followed by a boot to android and stock recovery before locking the bootloader in fastboot worked just fine for me - but yeah I totally understand everyone who's reluctant to do it... locking the bootloader again is potentially one of the most risky things to do on every android phone but locking shouldn't be a problem if you are sure you returned to stock completely and didn't miss anything!

It's definitely recommended to NOT take this action lightly and do all necessary precautions, double check recovery and that it boots up fine before going back to fastboot to lock it - I would never flash factory images and locking the bootloader in one session without booting up in between! Just because I would feel uneasy to simply rely on a flawless booting process when I haven't checked it out myself...
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
To show how much has changed, we used to unlock and relock the bootloader on the Galaxy Nexus with an app!!!! :cool:

https://xdaforums.com/galaxy-nexus/help/locking-bootloader-t1748412

https://play.google.com/store/apps/details?id=net.segv11.bootunlocker

edit - here is the original dev thread! I've had a fun morning in the way back machine. :good:

https://xdaforums.com/galaxy-nexus/themes-apps/app-bootunlocker-nexus-devices-version-t1731993

I used it on my Galaxy Nexus back in 2011 and later Nexus 6 & 7 .

https://www.digitaltrends.com/mobile/history-of-google-nexus/

Now unless you are careful and read and understand precisely how to relock, it is extremely risky, As the pros say, "Don't try this at home". (Unless you are a pro of course.) :D

Relocking it does give more security, but if you are that concerned with security, do not unlock your bootloader and root your phone. It truly is a security compromise that too many take too lightly without thinking and understanding the consequences. Some of us do, but the majority do not, sadly.
[Google Pixel 2 XL Guides, News, & Discussion] johnlgalt:
Ha! My Shamu was my first unlockable device - device before that one was the BIONIC.....
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
Had the Nexus S first, and it took me less than a week to totally brick it. :eek:

I still have my GNex and N6 which I still think was my best Google phone to date. If I could have the P2XL Pie features on the N6, I would be in geek heaven. ;)
[Google Pixel 2 XL Guides, News, & Discussion] johnlgalt:
Except for the fact that I used it for almost 3 years running, and thus the battery has somewhat degraded, I do agree that I like the Nexus 6 - a lot. My use of it for 3 years is a testament to that.

I still have it, and have installed BlissROM on it - it's a pretty decent Pie rendition on the device, but I cannot really say how well it performs as I have not set up any accounts on it, and it is not connected to any cell service, as my Taimen is my daily driver.

I've become a fingerprint user junky, and I think that was a much-missed feature. And I never really use the wireless charging on the Shamu, so I haven't missed it on my Taimen.

But the camera in my Taimen is so, so much better than the Shamu ever was, even without the AI post-processing and features like Night Sight. The first pic I ever took with my Taimen simply blew me away.
[Google Pixel 2 XL Guides, News, & Discussion] HACK3DANDR0ID:
BestBuy is selling *NEW* (Verizon) Pixel 2 XLs for $399 at the moment and i was thinking about picking 1 up until a SD855 device I like comes out.

Does the (Verizon) OG PIXEL Rule still apply that if you 1st boot the Pixel 2 XL (VZW) with my TMO SIM, it will register as an UNLOCKED Version so I can then Unlock BL?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Short answer is...nope. It's a sim unlocked device, not a bootloader unlockable device. There still isn't a viable option to unlock the bootloader on the verizon variant device. Not a bad price though for sure.
[Google Pixel 2 XL Guides, News, & Discussion] HACK3DANDR0ID:
The OG Pixel XL i owned was a VZW Locked Device, and when you boot the *Brand New* (never Booted) OG Pixel, it did indeed register as a Google Edition Pixel... At this price, for the Pixel 2 XL, you can see my argument! :confused:

Do you know this information for a fact? Because no matter how much Locked BLs and Carrier Locked devices are 2 very different things and have nothing to do with one another, however the OG Pixel, on the (3) that I owned, did indeed register as a Google Edition device depending on how the very first Boot Registration went (Depending on whether or not it 1st booted with VZW SIM or Not)....
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Oh I definitely see your argument, and yes you are correct that the Verizon OG Pixel did have a bootloader unlock method, for a while. However, the Verizon P2XL never had a viable option to do so. The info I have is from 18 months of almost daily observation on the forum threads about the P2XL. There have been at least 2 bounty threads regarding the issue, and had some very fine code writers working on unlocking the device, those threads have since died out, and still no solution was found. This is the last thread I've noticed about unlocking the device.

https://xdaforums.com/pixel-2-xl/how-to/exp-verizon-pixel-pixel-2-xl-potential-t3750795
[Google Pixel 2 XL Guides, News, & Discussion] HACK3DANDR0ID:
Thanks for your explanation, I guess they patched that for good!
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yeah, unfortunately so. Here's another bounty thread that has since been closed if you want to read more about it. :good:

https://xdaforums.com/pixel-2-xl/how-to/temp-root-bounty-verizon-users-t3710652
[Google Pixel 2 XL Guides, News, & Discussion] HACK3DANDR0ID:
Thanks, but I give up and already had (2) Pixel 2 XLs, it was a deal i couldnt refuse... Not enough SD855 options yet:(
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Coming in a bit late, but from what I've seen, if you flash stock image and are 100% stock, locking the bootloader shouldn't be an issue. It's when you are not 100% stock and try locking the bootloader that things get wonky.
[Google Pixel 2 XL Guides, News, & Discussion] Will008:
Yea after all the comments and the experiences, seems like the correct way to do it as u said is to get to a 100% stock then you've to boot into the system and recovery once to make sure all boots up ok before locking the bootloader. It's just useful to have this on here in case someone searches for a way to do it in the future.
[Google Pixel 2 XL Guides, News, & Discussion] johnlgalt:
Yup - which is what I did, after gobs of reading.

Not really sure why someone would want to try to lock a BL that they unlocked in the first place to install some 3rd party software, when said 3rd party software is still installed - but I read and re-read until I understand, not just follow instructions.

Some of the BL re-lock issues were legitimate foulups, though - my guesstimate a few pages back was that ~75% were user error.
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
Does anyone use an app or a method where they have unlimited tethering? I have the Beyond Go Unlimited Plan or whatever it's called and I get Unlimited data that might slow down to 3G speeds after my first 22GB of LTE are used and I get 15GB of hotspot usage as well. I'm wondering if anyone has a way to use WiFi unlimited off the same plan as my mobile data? I actually thought I asked this question in here before but maybe I missed it, I couldn't find the question.
[Google Pixel 2 XL Guides, News, & Discussion] louderthanu99:
root questions

is there a step by step guide with pics on how root running android pie? I seem to be having trouble getting it right.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
What have you done so far, and where are you getting stuck?
[Google Pixel 2 XL Guides, News, & Discussion] louderthanu99:
unable to get pc to connect to pixel i have oem unlocking and developer options on. Do i need to connect through Kies? At one point i had it working and now nothing I have the command prompt box up but get adb is not recognized as a command.

Thank you all for your help
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
No pics, but in my sig is a pretty detailed step by step, start to finish with links.

If you have questions, post here what step you're on in the process, what issues yo might be facing, and make sure to read the entire guide.

Make sure you have a couple of different USB cables handy (trust me) as well as the latest SDK tools installed on your pc.'

Have at it! :good:
[Google Pixel 2 XL Guides, News, & Discussion] louderthanu99:
So after I gts I have found out the following

how to put phone in boatloader mode

How to get the proper command box to open

after reading the guides would it be better to move the correct files to its own folder to makeit idot proof?

I have the latest version of magisk downloaded

I have 2 different usb cables but they are the same

off topic whats you edc? mine is a xdm 40 first gen
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Place all your files you want to fastboot in your platform-tools folder and open your cmd prompt on that folder. As long as your using a 2.0 USB A to USB C cable, you should be fine. What are you having problems with??
[Google Pixel 2 XL Guides, News, & Discussion] louderthanu99:
adb reboot bootloader

dameon not running starting now at tcp 5037

daemon started successfully

error device unauthorized

this adb server's $adb vendor key is not set

I think I cant get the pc to talk to phone but not sure
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Check your device manager on your pc. Do you see an android generic device? Or what is it showing for driver status?
[Google Pixel 2 XL Guides, News, & Discussion] louderthanu99:
lemobile android device
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Should read something like the pic. Are you using a USB A to C cable?
[Google Pixel 2 XL Guides, News, & Discussion] louderthanu99:
usb to usb c cable

I dont have what you highlighted I have downloaded it to pc
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
What kind of cable? Your answer is incomplete.
[Google Pixel 2 XL Guides, News, & Discussion] louderthanu99:
https://www.amazon.com/Snowkids-Cha...348&s=gateway&sprefix=snowkids,aps,415&sr=8-1
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Gotchya. You might actually need a 2.0 instead of a 3.0. It's a well documented problem with the P2XL for whatever reason.

---------- Post added at 07:53 PM ---------- Previous post was at 07:47 PM ----------

These are what I use without issues :good:

[2-Pack] Anker Powerline+ USB-C to USB A 2.0 Cable, for Galaxy S9, S8+, S8, MacBook, Sony XZ, LG V20 G5 G6, HTC 10, Xiaomi 5 and More (3ft) (Red) https://www.amazon.com/dp/B072152BWQ/ref=cm_sw_r_other_apa_i_mWqOCbKKQJVJN
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
Just for grins, try revoking USB debugging in Developer Options, then connect to PC and use "adb devices" and watch your phone for a pop up asking permission. See screenshot.
[Google Pixel 2 XL Guides, News, & Discussion] louderthanu99:
tried it did not work and I dont have adb devices. I seem to be missing the adb driver from google I think.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Get a 2.0 USB A to USB C cable. The 3.0 cables don't seem to work well with data transfer or device recognition with pc's :good::good:
[Google Pixel 2 XL Guides, News, & Discussion] post-mortem:
You sure you have the latest version of platform-tools? They released a new version this month (28.0.2).
[Google Pixel 2 XL Guides, News, & Discussion] powerserge1:
Is it still the case with TWRP being unstable at times if I would just like to install it on the phone? Read some of the thread.

Aware of the USB cable issue, have the lastest SDK platforms.

Basically would like to flash custom roms and root my 2 XL, so assuming installing TWRP would be best but looking for feedback. Also the adb command above will boot twrp, is there a prompt to flash it? Recall on my previous phone there was a specific command to flash TWRP.
[Google Pixel 2 XL Guides, News, & Discussion] jd1639:
TWRP is working fine. But you don't want to flash it with fastboot. You want to boot twrp, then install the twrp zip once booted into twrp. This will install twrp on your device. When you first boot twrp you'll want to allow modifications and then when you exit twrp make sure you don't install the twrp app on your device. Use the do not install button, not the slider prompt.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Twrp has been stable on my P2XL for about a year now. I've never had an issue with it. To fastboot into twrp, the command is: fastboot boot twrp-3.2.3-1-taimen.img

After you enter twrp, swipe to allow modifications, then flash the installer zip. DO NOT install the twrp app from within twrp. And there ya go :good:

---------- Post added at 12:25 PM ---------- Previous post was at 12:22 PM ----------

Dang ninjas! :laugh::laugh::good:
[Google Pixel 2 XL Guides, News, & Discussion] jd1639:
Don't you hate that? Happens to me all the time times too.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
It's all good Hoss :good::cool:
[Google Pixel 2 XL Guides, News, & Discussion] louderthanu99:
I have the ones from the link you sent me on order.

---------- Post added at 12:12 PM ---------- Previous post was at 12:09 PM ----------

I just downloaded all the files yesterday.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Great! Let us know how it goes when you get them :good:
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
UPDATE FROM 9x TO LATEST 9x FACTORY IMAGE:

PREP WORK:

* Unlocked bootloader. (*performing critical_unlock only required with bootloader versions PRIOR to TMZ20a) read it here.

* Latest SDK Platform Tools found here.

* USB 2.0 & 3.0 cables available (trust me)

* Remove screen lock security before starting

* Remove all substratum overlays

:silly:
[Google Pixel 2 XL Guides, News, & Discussion] johnlgalt:
In order to have

adb devices

show your device (instead of showing unauthorized) you need to have USB debugging enabled on your phone (under Developer Options), and when you connect the phone to the PC using the cable, if adb is already running, you'll get a popup on your phone asking you to authorize the adb connection immediately. If adb is not already running, then when you try to run

adb devices

you'll get that popup. You need to accept / press OK in order to allow the connection or none of the rest of this process will work.

I always had issues with my previous devices, but I'm using a USB A (3.0) to USB C cable on my USB 3 port and never had an issue, and the cable is even from MonoPrice lol.

But, yeah, if at first USB 3 does not work, always switch to a USB 2 port.

That unauthorized is usually symptomatic of not having accepted the popup on the phone.

However, the line immediately underneath it is troubling - because in googling it, I found all sorts of different things.

1) Wrong version of adb.exe;

2) Wrong keys on device;

3) Bad connection;

And a few other reasons.

That's the line that has me most concerned right....

See this ^^^^

Can you run

adb version

and tell us what it says? that will (for sure) eliminate that as an issue....
[Google Pixel 2 XL Guides, News, & Discussion] louderthanu99:
adb version

28.0.2-5303910

switched usb ports it rebooted in bootloader so does this mean i should be able to proceed?
[Google Pixel 2 XL Guides, News, & Discussion] louderthanu99:
currently in process of running full backups with reware to attempt root.

Much thanks to the Forum for the help!

I am able to get phone in fastboot mode. When i try to give unlock flashing command I get unknown flashing command. Do I need to copy files to pixel?
[Google Pixel 2 XL Guides, News, & Discussion] johnlgalt:
To unlock my Pixel 2 XL, I just had to make sure that OEM unlocking was enabled in Developer options, and then run the command in bootloader mode.

Follow the first page "unlocking bootloader" section explicitly.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
So your pc is recognizing your phone now with the new cables?? If so, are you running the proper command? And, there are no files you need files you need to copy to your phone to unlock the bootloader.
[Google Pixel 2 XL Guides, News, & Discussion] louderthanu99:
Bootloader unlocked need to do some more reading before trying to root. Much thanks to the Forum for the help.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Did the new cables do the trick????

Feedback on resolved issues is always appreciated :good:
[Google Pixel 2 XL Guides, News, & Discussion] louderthanu99:
The bootloader is now unlocked Im using the same cable just a different port on pc. I thought I read where when rooting pixel has to be flashed with new boot image and OS? And certian files have to be moved to the same folder?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You are partially correct. You will need the twrp.img on your pc to fastboot into twrp so you can flash magisk for root, or to flash custom kernels and roms. You would also need the proper factory image files in your platform-tools folder to do the monthly google updates. You don't necessarily need any certain boot or OS image to root your device. However, most of us like being on the latest release of whatever there is :good:
[Google Pixel 2 XL Guides, News, & Discussion] louderthanu99:
After reading the guide I'm sure I have all the correct files. Im still confused on how to root without flashing a new image. I would like to install Magisk then install TWRP . I have read the guide and it seems a bit confusing to me. What are the steps for this? Due to flashing the factory image after unlocking the bootloader. What are the right steps for what I want?
[Google Pixel 2 XL Guides, News, & Discussion] johnlgalt:
Until I joined the Android Q, the procedure I used was as follows (this assumes that you are not actually installing TWRP to the device, just booting it to install Magisk):

Put your phone in Bootloader mode (I usually do it by adb, using the command below, but you can do it manually with the power + Vol up button, too, as listed in https://source.android.com/setup/build/running )

adb reboot bootloader

Live boot TWRP on your Taimen by using the command

fastboot boot {path_to_TWRP}\twrp-3.2.3-1-taimen.img

Decrypt data using your passcode

Copy the Magisk.ZIP file to the Taimen using the command:

adb push {path_to_Magisk.ZIP} /sdcard

(this only works if you were able to decode the data partition. If that failed, you can still push the file to unencrypted locations, like so)

adb push {path_to_Magisk.ZIP} /data

(yes, it makes no sense, but /data is a folder under root, not mapped to the data partition, so it is not encrypted, believe it or not :p )

Use TWRP to install the Magisk.zip you just pushed (you'll need to navigate to the correct folder if you pushed the file to a location other than /sdcard)

Reboot the device, then open Magisk Manager

Press the INSTALL button next to "Magisk" (the first one), then press Direct install.

Follow prompts to reboot

IIRC, that is all it took for Magisk 18.1+ - no need to do it by hand anymore as in the steps in the first page.

[MENTION=3730810]Badger50[/MENTION] - anything else?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You got it Hoss :good:
[Google Pixel 2 XL Guides, News, & Discussion] iamjimmy:
Is it possible to install the April Security update WITHOUT the new Magisk version 19.0 beta? I have Magisk 18.1. Can that version still be used with the April Update?

I would rather not install Magisk 19 - as it seems to be having issues with Google Play. Thanks.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Heck yeah, go right ahead :good::good:
[Google Pixel 2 XL Guides, News, & Discussion] iamjimmy:
Thank you Sir. I will flash and report back.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Root will work fine, GP on the other hand may not.

Seems the latest google play services has kinda wrecked it a little bit from what I've read :eek:
[Google Pixel 2 XL Guides, News, & Discussion] iamjimmy:
I am planning to use Magisk stable 18.1 with the April security update.

Google pay does Not work even with that?

I had thought of not upgrading to Magisk 19 because of all Google pay issues.