yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
OTA's no, but if you plan on EVER flashing a full image including the bootloader then you need to do the critical unlock. Many ppl have had weird issues being semi-unlocked. Just get it out of the way. Yes, it will wipe data.
[Google Pixel 2 XL Guides, News, & Discussion] rockingondrums:
I'm only stock with Magisk (and critical unlocked). No TWRP, kernel, or anything else. Reading the initial announcement for Magisk and OTAs working nicely together was really exciting and was something I was looking forward to.

I think I'll try it tonight.
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
Ok but "only" Magisk still means both your boot and dtbo partitions have been modified. You're in the exact same boat as others with TWRP and Kernel. Try flashing back your boot and dtbo to original (December) beforehand and maybe you'll get lucky. ;) Be sure to specify whether you "took" it from the Notification, or you sideloaded it from Recovery. :good:
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
I do it by typing CMD in the address bar of the platform tools folder where I placed the unzipped factory image (all the extracted files including the flash-all.bat) and the fastboot application in it.

I updated my step by step to make this more clear, my apologies.
[Google Pixel 2 XL Guides, News, & Discussion] myprecious27:
I flashed twrp and now system doesn't load only twrp - what to do?
[Google Pixel 2 XL Guides, News, & Discussion] probono10:
Stuck on Google "G" White Screen

Any thoughts on getting past this?

- Up-to-date platform-tools

- Unlocked

- Unlock_Critical

- Flashed 8.1, got the OS up

- Attempted Magisk Install and got the dreaded White "G" screen

Pixel 2 XL
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Try rebooting by holding power button.

If that doesn't work, follow these steps. Hold power & vol down to boot into bootloader.

Should be fine starting at "Boot into TWRP.img" via fastboot
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
oops, note to self - do not read and post while eating lunch :rolleyes:
[Google Pixel 2 XL Guides, News, & Discussion] probono10:
Tried that several times. ADB lets me "Flash-All" for either the November Update (025) or December "011". I can even flash TWRP, but all the folders are encrypted due to there being a Password set up on the device. No Matter. I will always get the White Google Screen.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Did you edit the flash-all.bat file to remove the -w?

If so, maybe get a fresh factory image and start from scratch, leaving the -w in and wiping the device.

Might be an easier way, but whenever I run into unknown snags or difficult problems, I prefer to start fresh rather than chase unknown issues forever :D
[Google Pixel 2 XL Guides, News, & Discussion] probono10:
I wiped the device in TWRP yesterday, but now when I flash TWRP fastboot flash boot twrp-3.2.1-0-taimen.img, all I get is the splash screen. It's like I'm blocked from every angle. I'd be happy to factor reset, if I could.

Appreciate the help, thanks.
[Google Pixel 2 XL Guides, News, & Discussion] AMARH777:
Hi guys can someone help me please I've never rooted a phone before this basically what I've done is I've rooted my pixel 2xl unlocked the bootloader flashed twrp and installed magisk I want to return the phone to factory image state so I've downloaded the stuff of google developers website I've tried to do the flash all script but I keep getting an error saying flashing crictical unlocked I've tried Google that error I need do the critical unlock I've tried doing it on cmd but I keep getting a ton of messages which I don't understand can someone help me flash the phone back to factory state please.

Sorry I'm a new member any help would be appreciated!
[Google Pixel 2 XL Guides, News, & Discussion] ilal2ielli:
Fastboot flash boot is the command to flash the boot.img partition. The reason you only boot to TWRP after is because you have overwritten the kernel that would normally be there.

You'll want to reflash the factory boot.img for the version you were on. Either that or reflash full factory image to get everything back to stock before trying again.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
So you are saying once you fastboot into the TWRP.img, you are not given the option to install or wipe, just the initial TWRP screen?

That's a new one for me.

And you get no where starting over from scratch, flashing the factory image, and following the steps I suggested?.
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
He is correct since the other poster used

fastboot [B][I]flash boot[/I][/B] twrp-3.2.1-0-taimen.img

https://xdaforums.com/showpost.php?p=75065496&postcount=660

when it should be

fastboot [B][I]boot[/I][/B] twrp-3.2.1-0-taimen.img

Oopsie! Exact command syntax matters...
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Good catch! I missed that... I should try replying with my eyes open!
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Meh...those 3 day New Years Hangovers are a bugger sometimes! :silly:
[Google Pixel 2 XL Guides, News, & Discussion] kpalian:
How would I go about applying the January OTA to my Magisk rooted Pixel 2 XL? I have the OTA downloaded but idk what to do. I want the simplest solution please.
[Google Pixel 2 XL Guides, News, & Discussion] outbackpaul:
Your CMD tip was awesome. I love it.
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
It's not different for January. Same as December, November. I wouldn't recommend using an OTA at all. Just use a full image and remove the -w switch from flash-all.bat. There are literally dozens of threads with the sequence you need to use to re-root. Look HERE.
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
Instruction are in the OP (Original Post) that is also post #1.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
So while I was flashing the Jan 8.1 image, I accidentally wiped the entire device :D

I removed the -w, saved the bat file, reopened it before flashing it to make sure the -w was gone, and it was.

Fastbooted Jan 8.1 and POOF! Everything was gonzo.

Not sure what happened but like the advice I recently gave; sometimes it's nice to start fresh from scratch, and I did, against my will, kicking and screaming :p

Moral of the story, double and triple check the flash-all.bat file to ensure the -w is gone, and that the file saved properly.

Good news is, THESE steps still work perfectly!
[Google Pixel 2 XL Guides, News, & Discussion] damngood98:
just finished using this info w/out issue....funny thing though, when I updated to 8.1/dec it wiped my phone regardless taking out the -w.....perhaps the mistake was mine somewhere but I was counting on it this time around...in any case it is appreciated to see reminders so frequently on what the correct steps are for all of this....seems like there's a lot of ups & downs around here but I still love xda and many of people who help contribute so regularly
[Google Pixel 2 XL Guides, News, & Discussion] rockingondrums:
I was going to use the uninstall option in Magisk Manager itself, following the instructions in the link you posted... Hmm. I don't mind setting up my personal stuff again, especially with Google backup working pretty well these days. But I have a lot of work apps I don't feel like setting up again right now. Also, working in emergency services requires minimal down time. I'll consider any additional advice or wisdom you have, and keep an eye on future responses while I mull this one over.

Edit: I remember you guys talking about removing the -w but the last few posts have added pause to my effort.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Oh dude, that sucks! Guess that's why we do data backups on our pc's frequently. Luckily I haven't had that issue the last 3 updates with the -w removed. Don't know if this matters, however, every time we get new factory images, after I edit the flash-all.bat file, I reboot my pc, then check it again. So far so good the last 3 Google updates :good:
[Google Pixel 2 XL Guides, News, & Discussion] Cowbell_Guy:
I don't think that anyone here has actually confirmed that OTA can work with magisk.
[Google Pixel 2 XL Guides, News, & Discussion] outbackpaul:
I'm on the January update with root working.
[Google Pixel 2 XL Guides, News, & Discussion] kvoolk:
I can attest to this. The January full image has a new bootloader and it will not install without fastboot flashing unlock_critical. And without the new bootloader, the new system will not apply.
[Google Pixel 2 XL Guides, News, & Discussion] Rookx:
Trying to follow the steps and I think I've hit a wall with my cable - for starters the phone didn't come with any sort of cable to connect the phone directly to a PC, which I found more than odd. Nonetheless I had ordered several after marker 3.0 cables in preparation for my Pixel 2 XL to arrive. Trying to just unlock the bootloader I'm not getting a serial # spit back at me when I try the fastboot command to identify the phone, and attempting to run the adb reboot bootloader I'm getting "more than one device/emulator"

Is it safe to assume I'm on a cable that won't let me move forward? Basically my only option now is to go to a store and buy a 2.0 cable? or otherwise try all this on a different pc?

edit: Im going into my phone and changing the cable to Transfer Files instead of just charge too, not sure if that's relevant.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You should be fine with a 2.0 USB-A to USB-C cable. This issue has been frequently reported. But I definitely agree with about Google not supplying a proper cable. Especially at these prices! SMH :eek:
[Google Pixel 2 XL Guides, News, & Discussion] Rookx:
Ugh as I suspected. Will try from my home PC to see if it works there, otherwise it's more than tedious that I will need to go out just to buy an outdated cable. Not even sure where I'd go to buy such a thing, and waiting a few more days on amazon would suck.

While I'm here I have another question which I may need to know before moving forward...

I've got a google version of the phone, and am planning on unlocking, rooting, flashing a Kernel etc before I pop my sim card in. When I do that I will be on verizon, however - so to my question.

When I'm picking out the different images to flash on the google page, they have some listed for verizon specifically. Since my phone isn't on the verizon network yet since there's no sim in it, which file would I need to flash? The verizon ones or the non verizon ones?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
All good questions :good: I too am on Big Red. I use the Google factory images that ARE NOT Verizon specific! And have done so the last 2 monthly security updates without issue! Your definitely in the right thread for unlocking and flashing kernels and twrp. Just need that correct cable. Although the 3.0 version should work fine on your home pc. It's laptops that cause the headaches from what I've read. Just make sure your SDK and device drivers are up to date before you begin. It's really not that hard if you take the time to learn it properly. Best of luck to you, and welcome to the P2XL :good:
[Google Pixel 2 XL Guides, News, & Discussion] jwigley24:
after clean flashing a factory image, i want to re-lock the bootloader. should i run the "flashing lock" command then "flashing lock_critical", or does it even matter which order i run them in? is it necessary to run a command for "flashing lock_critical", or just "flashing lock"?

thanks for this excellent guide!
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Why do you want to lock it down outa curiosity? None of my business of course. But unless your returning it, why bother? :eek:
[Google Pixel 2 XL Guides, News, & Discussion] jwigley24:
Because I wouldn't be able to use Android Pay nor other certain apps if my bootloader is unlocked, at least that's how it was when I had my 6P.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Ah, gotchya. You could root it with magisk if you want and still use AP as many do. But it's your call.

Shouldn't matter which one you lock up first. Personally I would do....

Fastboot flashing lock_critical first

Then fastboot flashing lock

Either way should be fine though :good:
[Google Pixel 2 XL Guides, News, & Discussion] kpalian:
Does flashing the January image require an unlock_critical command? Because I opted to not go that route and I really don't feel like factory resetting my phone :(
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
You didn't specify which image but in general- OTA=No, full image=Yes. What is the perceived value of unlocking while leaving critical locked and putting your phone in a semi-locked state? I'd honestly like to know.
[Google Pixel 2 XL Guides, News, & Discussion] kpalian:
I tried to critical unlock but it didn't work so I just unlocked normally. I regret not finding a way to get the critical unlock to work, but alas, that's in the past. Does the FlashFire method work? If not, does the method where you return to stock boot, then re-flash Magisk via TWRP work? I

Thanks for the help, by the way.
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
It's not in the past, it's in your future....it just mandates a data wipe.

Do NOT use FlashFire yet. I love FF and have used it on all my previous devices and it worked flawlessly (for full images), but not now. Not until it get's updated and there is no word when/if ever.

Lastly flashing boot/dtbo to stock first is your best bet. I wouldn't even bother with uninstalling MM, just fastboot flash those two files beforehand (in bootloader) and then from recovery mode sideload the OTA. I personally would not "take" an OTA and let the phone update itself. For right now, flashing the full image is the cleanest, safest way. That's just me. I don't like OTA's and don't use them. Good luck.
[Google Pixel 2 XL Guides, News, & Discussion] kpalian:
Woah that's a lot of stuff I don't quite 100% understand. What does it mean to flash boot/dtbo to stock? Flashing the full image requires a critically unlocked bootloader, right? (Which I don't have). Could you make a dumbed down tutorial or possibly link me in the direction of one, please? Sorry to be a bother/noob.
[Google Pixel 2 XL Guides, News, & Discussion] probono10:
I used the code fastboot boot twrp-3.2.1-0-taimen.img and I am still looking at the twrp splash screen. Never gets past that. As AZ Biker has stated, it's a new one on me too. Just wondered if anyone else had encountered it and if so, what they did or would do?
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
HERE. Well written and concise for those who are doomed to using OTA's. Be sure and thank [MENTION=2781818]sn0warmy[/MENTION] and give him credit. You'll need to d/l and extract the boot/dtbo images from the full image (December). I know MM has an uninstall feature to restore those, but I don't trust that feature, and besides I always have the full image to pull those from. Good luck. We all have to start somewhere. :good:
[Google Pixel 2 XL Guides, News, & Discussion] kpalian:
Okay I have a couple last questions: 1. Why am I using the December image? 2. What is a dtbo image and how do I download that? 3. Why don't you trust MM's uninstall feature?
[Google Pixel 2 XL Guides, News, & Discussion] probono10:
Since twrp for 3.2.1 was just giving me the splash screen, I opted to go back to 3.1.1 (Code: fastboot boot twrp-3.1.1-beta2-taimen.img). Now I'm into twrp, but because the phone had a password, all of the folders are encrypted, which makes it a bit difficult to install the twrp zip file. Anyone have a work around?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Remove your lock screen fingerprint pin/password and then fastboot into twrp and flash your twrp.zip, kernel, and root. Then you can add your lock screen security back in :good:
[Google Pixel 2 XL Guides, News, & Discussion] probono10:
Thanks badger50, but how do I remove the lock screen using twrp? Don't forget, I can't boot the OS, so how do I remove that from twrp itself?
[Google Pixel 2 XL Guides, News, & Discussion] v12xke:
1. Assumed you were on the December build wanting to update to January? You have to restore the original boot.img and dtbo.img by whatever means you want before you allow your phone to take the OTA. You get those from the original full image of whatever build you are on currently.

2. dtbo (GOOGLE IT) is just another partition modified by Magisk. So you need to restore both boot.img and dtbo.img before upgrading (or it will fail). Flashing the dtbo.img restores the dtbo partition to it's untouched state. You get all the image files from the full Google image. I feel like I've said this 3 times now.

3. I trust Magisk. What I don't trust is that after flashing 4 or 5 Magisk updates, that my original boot.img and dtbo.img are retained in a pristine state. Besides, as I mentioned I only use full images, so those .img files are already in there.

4. You are postponing the inevitable by not unlocking critical with no defense other than you screwed up earlier and couldn't be assed with restoring your setup again. Lame.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You can't boot into the OS? Why? Did you just flash a factory image or take an ota?
[Google Pixel 2 XL Guides, News, & Discussion] probono10:
Booting a factory image (Nov, Dec, or Jan) will yield only the white "G" screen, so the only option I have on this device that I'm aware of, is twrp.
[Google Pixel 2 XL Guides, News, & Discussion] kpalian:
Okay, I got it to work by just flashing the newest stock img then installing twrp and magisk. Im very relieved and I look forward to learning more about the process and *not* being a noob ha haha thanks to everyone who helped me!
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Twrp won't help you in that regard. You need to get the OS running first. Have you updated your SDK platform-tools, device drivers and using a good USB-A to C cable??

---------- Post added at 01:41 AM ---------- Previous post was at 01:36 AM ----------

Never unplug it during an update my friend. First, calm down. Can you get back to fastboot mode, type in fastboot devices. If it returns your phone ID number, then you'll be fine. Just fastboot the factor image again, it'll wipe your phone, and your overlays as well. Would also recommend reading a bit more before you start flashing things my friend.
[Google Pixel 2 XL Guides, News, & Discussion] probono10:
Yes, I have the very latest platform tools and several USB-A to C cables.

It's puzzling that twrp starts up without requesting my password as it always has in the past. If I could read the unencrypted folders/file names, I might have a fighting chance. ADB and Fastboot commands are all working fine.

Anyhow, Level 3 support from Google is replacing my phone, but it still bothers me that I can't get past this. I thought I followed all of the instructions to the letter, but I made a mistake somewhere along the line.

Even if I can't get it fixed, I will have to root the new device so I can reload my Titanium backup.

Appreciate all the help just the same.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Have you tried fastbooting the factory image again with the -w removed from the flash-all.bat script? It won't wipe your phone. If it works at least you can get into the OS and then start over with twrp.
[Google Pixel 2 XL Guides, News, & Discussion] probono10:
Yes for Nov and Dec. Although I didn't see a -w in the January image.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Huh!!? You on the .013 or .014 version? The latter of the 2 is for O2/UK. It was definitely there on the .013 for me. Maybe download it again :rolleyes:
[Google Pixel 2 XL Guides, News, & Discussion] rockingondrums:
You can use the USB C to A OTG dongle that came with the phone. Nearly every gas station and convenience store I visit has cables. Local electronics stores too. With the dongle you just need an A to A cable.

HTH
[Google Pixel 2 XL Guides, News, & Discussion] beezar:
If I permanently flash TWRP, will the phone still pass Safetynet if rooted with Magisk?
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
SOLVED!

One just has to post, then to make you look like an idiot, google spits out the answer. :rolleyes:

https://snowdream.github.io/51-android/
[Google Pixel 2 XL Guides, News, & Discussion] p70shooter:
Yes.
[Google Pixel 2 XL Guides, News, & Discussion] probono10:
It was .013. I think I was looking at a FLASH-ALL file I'd already modified after a long day.

As I go through the process again with a brand new device (8.1 already installed, Magisk 15.2 Installed, ctsProfile: True, basicIntegrity: True), I'm having second thoughts about trying to install TWRP at this point (Magisk already installed). I hesitate because I believe this is what got me in trouble last time. As Nathan said regarding rooting with Magisk, "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."

Ultimately, all I want to do is to be ad-free (particularly with youtube) and use Titanium, so is TWRP worth it, and if so, is it possible to install it with Magisk already installed?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Twrp is only worth it if you want to flash kernels and mods. If your happy with the way things are, then enjoy. I will just say that twrp works great with Flash kernel without any issues :good:
[Google Pixel 2 XL Guides, News, & Discussion] probono10:
Would a custom kernal allow me install some version of YT without ads? My old Moto X with SU has literally no ads with no configuration changes to adaway. On the Pixel 2 with adaway, they're everywhere. It's brutal.
[Google Pixel 2 XL Guides, News, & Discussion] rickysidhu_:
Quick question, if I want to critical unlock, do I need to perform the regular fastboot unlock command first, or can I get away with just doing the critical unlock command?
[Google Pixel 2 XL Guides, News, & Discussion] ram4ufriends:
You can use https://xdaforums.com/android/apps-games/app-iytbp-injected-youtube-background-t3560900/page688
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Might as well do both back to back :good:
[Google Pixel 2 XL Guides, News, & Discussion] rickysidhu_:
Gotcha, will do. Thanks for the help!! :highfive:
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
No worries. Give em hell bro :good:
[Google Pixel 2 XL Guides, News, & Discussion] DaveMar:
I finally found some time this morning. I was already unlocked... So all I did was the unlock-critical... All went well. But because I has twrp installed it keep bootlooping into twrp screen... I held vol down + power it booted into bootloader then did full flash-all and then proceeded to set all up again. It will wipe your data so save what you want to computer first then just recopy back. Was back up and running in under an hour.
[Google Pixel 2 XL Guides, News, & Discussion] probono10:
From that thread it says: "8. Flash the iYTBP Vanced Universal Installer in TWRP recovery (recommended) or else install it via Magisk Manager."

Tried it via Magisk, but it didn't work. So, I am back to trying to install TWRP with Magisk already installed, which was fatal last time.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
The unlock_critical WILL wipe the device clean.

Flashing "flash-all.bat" file in fastboot will only wipe the device if the -w is NOT removed from the .bat file.

Removing the -w near the end of the flash-all.bat file will prevent your device from being wiped.

Make sure you SAVE the file after editing, close the file, and re-open to be sure the -w is gone, BEFORE you flash it.

Trust me when I tell ya :p