yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] BladeRunner:
That's pretty much what I am asking, but not being 100% familiar with Majisk, how does one fully unroot? Flashing the system.img does not overwrite root as it is systemless, correct? I am not critical_unlocked so currently the only way for me to upgrade is to unroot and get back to stock so as to take an OTA, but, if anywhere in that process I need to wipe my system I might as well do a critical_unlock and then just flash the new factory image when it comes out.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
To fully unroot just hit the uninstall button in the magisk app is you want to go the OTA route. Yes, unlocking the _critical will wipe your phone including root. I think you'll find it much easier, and more fun flashing the factory images with fastboot. Still something to be said about doing things on your own, and learning at the same time ???
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Forgot the pic! ?
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
Unlock critical ffs and flash the full image. You will lose root/kernel/twrp because they reside in boot.img. After flashing the full image, boot twrp, then flash twrp,kernel,magisk (queued). Done.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Here are easy to follow steps that include the option to skip TWRP if desired.

As for installing TWRP: why not just install it?

You can flash mods, kernels, magisk, nand backups, and soon enough, more and more cust roms will be popping up.

If you don't want TWRP permanent, just fastboot the TWRP .IMG (it boots you into TWRP so you can flash cust kernel), then SKIP the flash TWRP.ZIP from within TWRP portion (see my steps linked above) it's all there.

So if it were me, I'd just flash TWRP and be done with it :D
[Google Pixel 2 XL Guides, News, & Discussion] NMEAGENT:
I was debating because the OP said TWRP wasn't stable because of "the way that security has been set up on this device (lack of decryption, failing to boot, etc)."

Based on what you are saying, if I wanted to install a custom ROM, i could just fastboot the TWRP image and install from there like normal and then flash custom kernel, and then lastly magisk to root again, correct?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yep, that's pretty much what he's saying ?
[Google Pixel 2 XL Guides, News, & Discussion] CrimsonToker:
Is TWRP still unstable? Before I unlock/root/flash, should I stick with just magdisk for the time being and hope for better TWRP later?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Twrp is working fine for me. Have had no issues with the official 3.2.1-0 version thus far.
[Google Pixel 2 XL Guides, News, & Discussion] CrimsonToker:
That's good to hear. I haven't had a rooted phone in about 4 years, but back when I did I always had TWRP. It's one of the best recoveries I've used.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Agreed. Here's the link to it you need it :good:

https://dl.twrp.me/taimen/
[Google Pixel 2 XL Guides, News, & Discussion] CrimsonToker:
Trying to decide between staying stock with root (safer route, I would think) or flashing a custom ROM. What are your thoughts? And is there a chance we might see Cyanogen on the Pixel 2 XL sometime?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
My thoughts...that's scary!? Well, I'm just running stock rooted myself ATM. Rom development is still pretty slow given the A/B partitions, however, there are a few good ones out there from what I've read. I just haven't seen the need to flash one yet, mainly because I am essentially on call 24/7 with an ailing mother in a nursing home, and can't afford any down time with my phone. As far as CM/Lineage goes, if I'm not mistaken, I think there's one in the works already :cool:
[Google Pixel 2 XL Guides, News, & Discussion] CrimsonToker:
Yeah I definitely get your hesitation there! I think I will stay stock until there's a stable CM up and running.
[Google Pixel 2 XL Guides, News, & Discussion] dredq:
Sorry about your mom Badger.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Thanks my friend. End stage parkinson's is no fun at all.?
[Google Pixel 2 XL Guides, News, & Discussion] galaxys:
Bummer, wish all of you the best...
[Google Pixel 2 XL Guides, News, & Discussion] elliwigy:
there will never be a stable cm lol.. its lineage now
[Google Pixel 2 XL Guides, News, & Discussion] galaxys:
RIP CM...
[Google Pixel 2 XL Guides, News, & Discussion] CrimsonToker:
Well it doesn't matter to me anyway. My amazing new phone won't communicate with my sh***y old POS laptop. So no unlocking and rooting for me just yet
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Make sure you grab the latest SDK tools (link in the OP), try using a USB 2.0 cable , try a different USB port on your PC, and try rebooting your PC .

Unless when you say your laptop is old, you mean like 203 old :p
[Google Pixel 2 XL Guides, News, & Discussion] CrimsonToker:
I just got a new USB 2.0 data cable yesterday, my laptop is running xp still, even though the stickers on it say it was made for 7. But it was working poorly when I got it for $20 from a friend, so whatcha gonna do? I'm too broke to afford a new or even newer laptop ATM.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
It's free to download the latest SDK tools and give it a try :D
[Google Pixel 2 XL Guides, News, & Discussion] CrimsonToker:
I have the ADB and fastboot binaries working correctly. But I can't even get the phone drivers installed
[Google Pixel 2 XL Guides, News, & Discussion] dredq:
Watch Deuces video . https://youtu.be/hbyPwhCqcHQ

Check out Deuces OP.

https://xdaforums.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
[Google Pixel 2 XL Guides, News, & Discussion] E30Nova:
Just got this phone yesterday, used this guide to unlock the bootloader and root it. Haven't installed twrp, though, because the OP says it's still unstable. Looks like most of you are saying it's pretty stable, though, as long as you turn off the screen time-out.

I came from a 6P so I miss being able to boot into recovery to flash stuff. :(

I also have a message saying "internal problem with your hardware, blah blah".

Googling says it was a problem with magisk modifying the dbto automatically. Is there anyway to fix that permanently or is the only option to flash the dbto from the factory image? It doesn't bother me enough to do that, lol.
[Google Pixel 2 XL Guides, News, & Discussion] galaxys:
TWRP is stable, go for it... Op was referring to a beta version.
[Google Pixel 2 XL Guides, News, & Discussion] E30Nova:
Thanks, will do!
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
PSA for y'all. Since the February update, TWRP is having difficulties decrypting data when you have a password enabled. Nathan Chance (Flash) has stated that you can remove lock screen fingerprint/pin/password to enter twrp successfully to flash kernels and mods. I too have this issue as well. Guess we'll have to wait for an update to twrp to correct the issue. And now back to your regularly scheduled program :cool:
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
ALWAYS double check your files, just ONE more time...

As I was making my final checks after unzipping the image, and removing the -w from flash-all, with my device already booted to the bootloader, I did one last check on the files in the platform tools folder, and they were all WALLEYE files!!!!!!!!!!!!!!

So I must've fat fingered the download link and somehow grabbed Walleye image instead. Talk about distracted :D
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You just crack me up my brother!!??? That AZ sun is just kicking your back side!
[Google Pixel 2 XL Guides, News, & Discussion] outbackpaul:
This has been driving me crazy for the last hour. Glad to know it's not something I've done.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
With all security removed I followed norm steps:

remove -w from flash-all.bat file

flash-all

fastboot boot <twrp- filename.img>

flashed twrp.zip, rebooted to recovery

flashed Flash 2.16 kernel.zip in twrp

flashed magisk 15.2 .zip in twrp

rebooted to recovery

rebooted to system

profit :D
[Google Pixel 2 XL Guides, News, & Discussion] outbackpaul:
After doing flash all .bat my phone reboots. Any way to stop that next month?
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Mine rebooted to system too, has never done that before.

Just got back to bootloader and carried on.

Must be something in Feb factory image? Although I don't recall anyone reporting this except us two.

meh... a bit inconvenient, but whatever....
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You can always hold the power button and down volume button simultaneously until it boots into bootloader mode while it's trying to boot up after the flash-all procedure. If that's what your asking.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Yeah, but if his issue is like mine, the device has never rebooted in to system after flash-all before.

Just a weird anomaly.
[Google Pixel 2 XL Guides, News, & Discussion] outbackpaul:
Ok, gotcha
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Huh...that is weird. My update just booted up to the OS as usual. Must a been that Walleye you had! ??
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
So after you flash the flash-all file, you always reboot to the OS?

Mine has NEVER booted back into the OS after installing a factory img, it just hangs out in fastboot waiting for me to boot the twrp img...

Weird.

View attachment 4410900
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Go figure bro. I swear these things have a mind of their own sometimes! ???
[Google Pixel 2 XL Guides, News, & Discussion] damngood98:
security removed....but no issues implementing it again after all is flashed correct?
[Google Pixel 2 XL Guides, News, & Discussion] clothednblack:
Mine has always rebooted to the os afterwards
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
If you really want it, you guys might try adding the lines at the end of the .bat file "--skip-reboot" where the "-w" is at and ">nulfastboot reboot bootloader" before the last "echo"; I imagine the --skip-reboot line would only go right before it invokes updating the .zip lest it stops all automatic rebooting prior.

I haven't tested this out as I've never chose to require this need but theoretically it should work (disclaimer: the --skip-reboot command I might be misunderstanding and may not work as I had hoped/intended), but I can't say for 100% concretely certain it will...

Hope this helps...
[Google Pixel 2 XL Guides, News, & Discussion] outbackpaul:
Mine has always booted to OS too. I thought I was doing it wrong.
[Google Pixel 2 XL Guides, News, & Discussion] benjmiester:
I keep getting TWRP asking me for password (encryption) now after rebooting to twrp to do a backup of my stock setup. I was on 8.1, unlocked BL and did the whole fastboot boot twrp then flashed magisk and twrp installer. Booted to OS, everything's fine. But the first time I went to boot TWRP to do a backup before flashing any roms, it's asking for a password aka encrypted data. I can of course hit cancel and get into twrp but all of the files are number/letter hashes and can't do a backup so it's obviously still encrypted. Do I really have to wipe/format data and reset my OS yet again just to be able to use TWRP to backup for the 1st time? I mean I've been there on my Mate 9, but didn't think a pixel would be this messy just doing a backup.

---------- Post added at 05:38 AM ---------- Previous post was at 05:34 AM ----------

Doh!! I think this answers the question I just asked in here in the above post. I'll give it a try. I've got to start reading threads backwards instead of oldest to newest :laugh:
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
As stated several times in this thread. After the February update, TWRP is having difficulty with decrypting data. If you remove all lock screen security, TWRP will work fine. That's why after you hit cancel in the TWRP start up screen, your files look like Egyptian hyroglifics. Remove the lock screen security, and you'll be fine :good:
[Google Pixel 2 XL Guides, News, & Discussion] E30Nova:
So I successfully unlocked the bootloader (ran the flashing_unlock and unlock_critical commands) and rooted my phone following this guide.

Then I decided I'd update to the new February image.

Except no matter what I do, I can't flash anything from it. This is what happens every time:

So far I've tried two different usb ports on my computer and two different usb cables.

ADB version is 1.0.32.

I've even put all the platform tools files and factory image files in the same folder and still nothing.

I'm pretty much stumped. :confused:
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
With no intention of sounding condescending at all, you did unzip the Feb factory file twice, and are using the second zip file to put in the platform tools folder?

Have you tried not using adb\ command and just typing flash-all ?

I'm at work so I'm going off memory here. But I think your files are in the wrong folders. It looks like your flash-all.bat file in inside your factory image folder?

IIRC it should run like this: sdk toolkit folder > platform tools folder > 11 files (to include fastboot application) and a few folders

unzip your factory image folder elsewhere, then unzip it again, there should be 6 or 7 files (boot.img, bootloader, radio, flash-all, flash-all.sh, and one or two other files..

copy these files and paste them inside the platform tools folder (see above) where the fastboot application is. You'll want your TWRP.IMG file to be here as well if you want to boot into TWRP.

Again, this is off memory, so if anyone has any corrections to this, please comment.
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
yea it seems that all the files in your folder "taimen-opm1.171019.018" should be in your "adb" folder (assuming adb.exe and fastboot.exe is within this "adb" folder); it doesn't count if you put the extracted .zip files all collected in its own folder within your platform-tools folder ("adb" folder in your case it seems). And, as AZ Biker has already stated, you should simply run the command "flash-all.bat" while running the command within "C:\adb" (not from system32 necessarily); no adb command needed...the "flash-all" batch file has all the fastboot commands within it...

P.S. clarification: most of us have our folder named some iteration of "platform-tools" instead of your "adb"
[Google Pixel 2 XL Guides, News, & Discussion] E30Nova:
To be honest, I tried multiple times doing that...

I think.

That text that I pasted was from powershell instead of the usual command prompt. I just wanted to go to bed so I figured I'd try that, too.

I did all this after getting home from work, so I guess I'll try again by putting everything in the adb folder.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Dude. Just realized you're in San Bernardino! I lived in Ontario for over a decade. Rode literally thousands of miles Mountain biking up and down Baldy every summer... Left in '96.

Anyway, back on topic.

I'll be home from work in about an hour, I'll get a few pics of my platform tool folder hierarchy/tree with the correct files to make sure I didn't misspeak earlier from memory. If you moved files or folders, or opened zips in the wrong place, fastboot is a fickle beast :p
[Google Pixel 2 XL Guides, News, & Discussion] E30Nova:
Nice! Fellow, so-cal-er, lol. Yeah, I've wanted to cruise Mt Baldy for a while, I've heard it's a fun drive.

But uh, I guess I'll blame working 8 hours and then trying to do this while extremely tired. I just deleted the adb folder, reinstalled platform tools and then copied everything from the factory image into that folder and it worked this time.

I got a lot of messages saying "folder does not contain x" like

dt.img

recovery.img

vendor.sig

vendor_other.sig

etc

But it's booted up and working. I'm used to some of those from the 6P, so I'm guessing it's no big deal.

Now to just flash twrp, the kernel, and magisk.

Thanks guys, sorry for the super noob mistake. :o:silly:
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Not everyone is a fastboot savant; including me, so don't sweat it.

Biking Baldy is a blast! They put hooks on the back of the ski lift chairs, you put your bike on the hooks, lift to the top, scoping a sweet trail to ride on the way down, get off the lift, grab the bike and head to the bottom! Wash, rinse, repeat till your arms and legs are noodles. Good times man!
[Google Pixel 2 XL Guides, News, & Discussion] umx:
I am guessing with out unlocking the boot loader, you also cant root.. BC i have one of the lucky phones with the oem unlocked greyed out
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Correct. Verizon version not unlockable, yet. And with a locked bootloader, you're not doing much except substratum. (which IS still better than a poke in the eye)

There's not much hope it will ever be, but you never know.

If you're within your 14 day trial period, turn it in and go Google!
[Google Pixel 2 XL Guides, News, & Discussion] umx:
i bought it today.. i was just trying to decide if i liked it more then my v30 before ordering it from google.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Turn that puppy in and go Google! If you decide you don't want the 2 XL, you'll have another trial period to try it out.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Here is the folder progression for my SDK PLATFORM TOOL

C:\USER\ANDY\DESKTOP\PIXEL 2 XL\ (follow the address line progression in pics)

Put this folder somewhere easy to find

View attachment 4411817

You get this after opening SDK PLATFORM TOOLS

View attachment 4411819

I created a FACTORY IMAGE folder inside the non-zip platform tools folder, unzip factory image in FACTORY IMAGE folder (next pic)

View attachment 4411820

Unzip the second zip file inside the factory image here too, copy/paste THESE 6 files into the last folder below, which will also have your FACTORY IMAGE folder you created

View attachment 4411821

THIS is your fastboot folder, place a copy of TWRP.IMG here to boot into TWRP, and the 6 factory image files from the above pic as well

View attachment 4411822

highlight the address bar and type CMD hit enter to enter fastboot cmd prompt

View attachment 4411827

I'm sure there are other ways to accomplish this, but this has been the easiest way I found :D
[Google Pixel 2 XL Guides, News, & Discussion] BladeRunner:
I create a folder called Android-SDK in the root of C drive then unzip the SDK to that folder. I also edit my enviromental variables and add "C:\Android-SDK\platform-tools;" at the end. It eliminates having to move things in and out of the plat-form tools folders. I just shift-right click in the folder of whatever I want to flash and open powershell from there.
[Google Pixel 2 XL Guides, News, & Discussion] eushaun99:
When you unlocked your bootloader, did you do unlock_critical? Seems to me that is the major problem as it said

writing 'bootloader_a'...
FAILED (remote: Flashing is not allowed for Critical Partitions

The missing files aren't necessary for our phones.

Also make sure you have updated adb and fastboot binaries.
[Google Pixel 2 XL Guides, News, & Discussion] benjmiester:
I must not have. So should I unlock it? I'll check if adb and fastboot are updated in the meantime. I am still able to get TWRP to load via boot twrp.img command, and I can sideload the twrp installer zip but can't seem to flash a rom that way yet.
[Google Pixel 2 XL Guides, News, & Discussion] eushaun99:
Yes you should. Keep in mind it will wipe your phone including the internal storage. For adb and fastboot, download the latest one from https://developer.android.com/studio/releases/platform-tools.html, unzip it and replace the folder with your old one.
[Google Pixel 2 XL Guides, News, & Discussion] benjmiester:
OK thanks. Is there a separate command for critical unlocking? I don't remember seeing it when I unlocked. I just

used 'fastboot flashing unlock' for that one, and then enabled it on the phone. I got instructions from this guide: http://highonandroid.com/android-smartphones/how-to-root-pixel-2-or-pixel-2-xl-easiest-method/
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
To install factory images, fastboot flashing unlock_critical is a have to! This WILL wipe your phone! Which, at this point is probably a good thing. Also, TWRP is unable to decrypt data since the February update. Therefore, you need to remove all lock screen security before using twrp.
[Google Pixel 2 XL Guides, News, & Discussion] eushaun99:
Yup fastboot flashing unlock_critical, read the first post here for a more comprehensive guide.

Also as Badger said, this is probably the root cause of your issue.
[Google Pixel 2 XL Guides, News, & Discussion] benjmiester:
Thanks. Sure sounds like it. I'll try that and give the factory image flash another run. My ADB is probably out of date too, haven't installed anything new since my Mate 9 and that was still 2016

EDIT:

Yep critical unlock was the problem. Works perfectly fine now. Thanks guys! Yet another new curve ball in the flashing game. It's kind of tough coming from a Huawei, which is wildly different heh.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Oh!....it's definitely out of date! ??
[Google Pixel 2 XL Guides, News, & Discussion] igknight:
I've had my Pixel 2 XL since it came out, had it rooted this way without issues, but had some problems with the January update. Decided to flash the factory images for February, but needed to unlock critical first. I unrooted my phone, unlocked critical, flashed the Factory images without issues, but Magisk won't patch the book image.

I'm not using TWRP, encrypted phone, so I installed Magisk Manager v 5.5.5(91), but when I select the boot image from the factory image download, I get the below:

- Device platform: arm64
- Extracting files
- Use boot image: /data/user_de/0/com.topjohnwu.magisk/install/boot.img
! Invalid Uri
! Installation failed

Not sure if it is trying to move the image or not, but I have it stored at /storage/emulated/0/boot.img

Any help is appreciated.
[Google Pixel 2 XL Guides, News, & Discussion] Ric G:
Why not just install from a USB stick?
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Try following these steps. I just updated February image using them, all is good.
[Google Pixel 2 XL Guides, News, & Discussion] rickysidhu_:
So I'm going to attempt to flash-all the Feb update in the next day or so, but I'm afraid of running into the same error I quoted myself in.

Just wondering if anyone knows of a solution to that (if) I do end up running into that same error during flash-all.

I ask ahead of time just because I no longer have a spare phone to fall back on. I could use a toolkit but I prefer to do things manually just to be more independent on modifying my device, and using toolkits only as a last resort/desperate measure.

When I experienced that error, I did have my platform tools completely up-to-date and followed the guide in the OP exactly.

I also did read somewhere that deleting fastboot in /usr/local/bin/ could help resolve that issue.

I'd love to hear what you guys think! Thanks in advance :)
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Are you using, or did use the flash-all.sh file install of the flash-all.bat file since your using a Mac?
[Google Pixel 2 XL Guides, News, & Discussion] rickysidhu_:
I used the ./flash-all.sh file and that worked really well when I had my OG Pixel XL, but I get that error when trying on my 2 XL for some reason.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I'm not a Mac guy, so I can't help much. But maybe this will make some sense for you ?

https://xdaforums.com/pixel-2-xl/de...tloop-recovery-flashing-t3704761/post75483700