yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] thereal_bigjake:
I'm curious if you try taking out the sim, factory reset and rey booting again if you might get lucky. I read somewhere else this worked for someone. Worth a shot
[Google Pixel 2 XL Guides, News, & Discussion] hanschke:
I cannot flash the full image from may :( I remove the -w inside the bat file like before but only got:

sending 'bootloader' (36344 KB)...

FAILED (command write failed (Too many links))

finished. total time: 0.004s
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Switch out your USB cable from 2.0 to 3.0, or vice versa,

if that doesn't work (which I bet it will) try a different USB port,

if that doesn't work, pour 8oz of water on your keyboard, drop a 5lb weight plate on it, then try step 1 again :p
[Google Pixel 2 XL Guides, News, & Discussion] mayorblurps:
I am a Fi customer and I've flashed the beta versions of TWRP, now on the latest TWRP version and april release, with flash kernel and Magisk. No issues at all! The nice part about root is having FiSwitch working!

I've flashed the monthly releases (after bootloader unlock and critical unlock) along with Magisk over the past few months and honestly haven't had any problems. I follow these steps, which are repeated thru the thread in 1 way or another. And I've got them saved in Google keep.

EDIT: as long as you are signing into your phone with the email attached to your eSIM then you should not have any issues upon sign in.

Good luck.

https://xdaforums.com/showpost.php?p=74772300&postcount=296
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Nice one Cap! Gotta good laugh for sure! Well played! ??????
[Google Pixel 2 XL Guides, News, & Discussion] hanschke:
I bought a 2500 euro pc and you told me that I have to damage it?
[Google Pixel 2 XL Guides, News, & Discussion] nathanchance:
Surely you can tell the difference between a little tongue in cheek humor and serious instruction?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Sarcasm bruh...sarcasm! However, the first part of his post is spot on about the cables :good::cool:
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
you guys also forgot to mention the obligatory "also make sure you have the latest version of platform-tools/adb/fastboot".... ;)
[Google Pixel 2 XL Guides, News, & Discussion] Wartickler:
Have you tried turning it off and turning it back on again?

You should also try a different cable or USB port...just sayin' :silly:
[Google Pixel 2 XL Guides, News, & Discussion] hanschke:
I have taken different usb port. load the last adb and use the cable like before.
[Google Pixel 2 XL Guides, News, & Discussion] thereal_bigjake:
Lol, that phone is so picky I have to use fastboot from my Nexus 6p every time I need to boot recovery.
[Google Pixel 2 XL Guides, News, & Discussion] hanschke:
I have taken the nexus 6p cable too and dont work. from 2.0 til 3.1 nothing.
[Google Pixel 2 XL Guides, News, & Discussion] Hormesis:
When using a custom ROM, does anyone happen to remember which files need to be flashed from the latest Taimen image to get the monthly security fixes? Someone posted a very simple guide to doing this without doing a clean install and I can't for the life of me find it.

It was just a few files, i.e:

fastboot flash vendor vendor.img

fastboot flash modem modem.img

... etc, etc, I just can't remember which.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Usually just the vendor will suffice :good:
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
I did this same thing, I have no Idea however to run the unlock command. I still show locked, what should I do?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
fastboot flashing unlock_critical

and

fastboot flashing unlock

Neither of these work? :confused:
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
I tried to do the unlock again and it says it's already unlocked. However, when I into the recovery to root it, it says device status is locked.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Well, have you tried different USB cables and ports? SDK/platform-tools is up to date? Or are you using minimal adb? Have you looked into dueces script?
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
I got it unlocked , now I'm having issues rooting. I have copied the twrp files over to my phone, but everytime I type in the prompt, it says the files do not exist. Any suggestions??
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
The twrp.img goes in your platform-tools folder. Then you fastboot that with....fastboot boot twrp-3.2.1-2-taimen.img

When that boots you into twrp, then you flash the twrp installer zip. Then flash your custom kernel, then the magisk.zip

Be sure your screen lock security is set to none or swipe before you begin all of this.

How did you finally get it unlocked?
[Google Pixel 2 XL Guides, News, & Discussion] wpy:
During factory image flash on the sending vendor_a i am getting a FAILED (data write failure (Unknown error))

any help guys?

writing 'vbmeta_a'...

OKAY [ 0.004s]

erasing 'vendor_a'...

OKAY [ 0.080s]

sending 'vendor_a' (354904 KB)...

FAILED (data write failure (Unknown error))

finished. total time: 89.652s

Press any key to exit...
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
I went back and unlocked it with the normal command, without critical. Worked perfectly.
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
This sounds like an issue that relates to the usual obligatory 3 inquiries: Have you tried using a different USB cable (USB-C to USB-A seems most compatible)? Have you tried changing from USB 3.0 to USB 2 [either cord and/or slot])? Have you made sure that you are using the updated platform-tools/adb/fastboot?

Also, for your specific issue [MENTION=480539]wpy[/MENTION], I would make sure you have at least 3 GB of free space on your C drive and I would re-download the full factory May image, and then check the checksum of the .zip file you downloaded to confirm you have a complete unaltered factory image copy. I have had personal experience that I have run into errors where my download wasn't complete and my checksum did not match which caused the issue (if certain "images" do not match perfectly, it returns that "write failure (unknown error)") and/or it attempts to extract specific images and partitions temporarily, and because I didn't have enough free space, it just errored out at the prompt...

hope this helps...
[Google Pixel 2 XL Guides, News, & Discussion] Pikakun:
I've tried searching and couldn't find anything. My device wasn't showing up in fastboot devices until I manually located the windows drivers. Perfect she thought. However now upon rebooting my phone, the option for oem unlocking has suddenly greyed itself out. It was there before. I have no idea what's happened. Can anybody assist? TIA
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Is it grayed out in the on or off position??
[Google Pixel 2 XL Guides, News, & Discussion] wpy:
Yeah it solved the problem.... Thank you very much. I was using 2 type-c to type-c cable. First by anker then the pixel 2xl supplied type c cable. I switched to nexus6p type A to type c and the update completed. Very strange really. But all is well now.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
[MENTION=6842057]nathanchance[/MENTION]

I hate to be a bother, but the above troubleshooting revolving door is the reason I suggested adding this language to the OP in close proximity to fastboot instructions/FAQ :D
[Google Pixel 2 XL Guides, News, & Discussion] nathanchance:
I will try my hardest to get to this today haha.
[Google Pixel 2 XL Guides, News, & Discussion] nathanchance:
[MENTION=4670411]Az Biker[/MENTION] done, let me know if there are any other pain points I should be aware of!
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
It's still saying there is no file. I'm lost.
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
lol...interesting note that I

had

to post and include: I had actually went back a couple pages to look up this post you're speaking of and refer to it as I made my reply/advice... :p

...but I didn't want to bother or pester nathanchance more about it... And, since you are a mod, you have to know that more than 50% (I predict) of the people who would benefit from this information isn't gonna/wouldn't read the OP anyways (and merely straight up post instead of search; i.e. touch isn't working for TWRP, should I get a Verizon Pixel 2, is Verizon's a locked bootloader, should I (keep) unlock_critical, is my Magisk installed, can I root without using/installing TWRP, etc.)....:silly:

---------- Post added at 01:30 PM ---------- Previous post was at 01:23 PM ----------

The "twrp-3.2.1-2-taimen.img" file has to go inside the same folder that shows adb.exe and fastboot.exe. In essence, put the twrp-3.2.1-2-taimen.img file in your "platform-tools" folder; where it'll sit with other files and folders such as adb.exe and fastboot.exe. Then run the fastboot command...

Hope this helps...

---------- Post added at 01:35 PM ---------- Previous post was at 01:30 PM ----------

I know I am not the "Great One" (Az Biker) of whom you particularly asked, but I would like to submit that instead of titling the section "Common Issues", I would use the wording (or more like the wording...) "Common Troubleshooting Solutions" or "Solutions For Common Issues"...

See what ya think...
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
Like this? Cause I've done that. View attachment 4497003
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
and when it errors "file not found", is it referring to your "boot image" or the "fastboot" executable?

Or, better yet, what happens if you were to type in (seperately)

adb devices

and

fastboot --version

and

fastboot get_unlock_ability
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
While you are correct that MANY will not bother reading the OP, those who do, first timers who don't want to brick their device (at least in my case) read the OP roughly 11 times...

In a forum with 8million+ members, you'll always have a few who are lazy, hardheaded, or the dullest tool in the shed. We should do what we can to minimize the impact on the forum from folks like this, but with kindness and respect (when possible).

If the blurb Nathan added stops just 10% of the "I'm getting this error (which is fixed by changing USB cables/ports)" then it will be well worth it.

Plus, now the thread regulars can say "Read the bottom of the OP" and be done with it.

I'm a firm believer that thread regulars and veteran crack flashers should be helpful, giving the answer if they know it, and generally holding the hands of those brand new to the process or device.

But when those questions come from a 4 year, senior member, I have another take on it:

I am also a firm believer of "tell the member what's in the OP, fix his problem for the day; teach the member to read the OP, help him fix his own problems for life" :D
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
LOL... Fair enough...:good:

I'll be sure to keep that in mind and point to the OP...

But very wise indeed...it seems (which should be obvious enough with you being an Admin) that you've run into this a bit (/s) and have formed some thoughts and a response... haha;)

That is why you "stand atop" :bows down:
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
When I type"fastboot devices" it gives my serial number fastboot.

Oh crap. I have been putting in wrong command
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
:silly::silly::silly::silly:

View attachment 4497010

Here's my "guide" should you need help in the future :D

.
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
This is what I get.View attachment 4497013
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
looks good.... the commands I gave was just to confirm what the error might be referring to and/or confirm where you were at in the steps...

so...as I said...looks good...so all you need to do now (at the point of that screenshot) is to reboot to bootloader and boot into twrp using the boot image...

I was gonna leave it at that (cuz i'm feeling a bit lazy) and let you figure the syntax, but I don't want you to get any more lost...

so, after plugging in your phone and laptop together through a USB, confirm your computer is seeing your phone by running the command (remember to have your powershell/command prompt directed to your platform-tools folder):

adb devices

then, while the homescreen is open, run the command:

adb reboot bootloader

and while in the bootloader, run the command:

fastboot boot twrp-3.2.1-2-taimen.img

and...as the great Az Biker might say... "profit!"

P.S. After looking at your previous screenshot of your computer, if all this doesn't work, I believe the problem may lie in the fact that you are not showing "extensions" in your Windows OS -- which may mean that instead of having twrp-3.2.1-2-taimen.IMG, you might have another twrp-3.2.1-2-taimen; like twrp-3.2.1-2-taimen.ZIP or twrp-3.2.1-2-taimen.ASC ...
[Google Pixel 2 XL Guides, News, & Discussion] mayorblurps:
That post is my upgrade Bible, so to speak! Thanks AZ for posting it.

Now for those updating to the May release. I noticed that for once there's a Fi carrier version and regular. Prior to now I've been using the regular version and Fi has been fine. I wonder what the differences are?
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
LMAO :rofl:
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
In fastboot or in twrp?? :confused:
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
Fastboot
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
Yes, well, maybe. As another mod once explained (click to unhide the comment). :D

https://xdaforums.com/showpost.php?p=64436550&postcount=4400
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
And you get the proper response when you type in....fastboot devices....? And, are you opening the command prompt on the platform-tools folder?
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Hey [MENTION=3730810]Badger50[/MENTION]! Sorry to butt in, but I wanted to try and stop you right here so to not waste your time necessarily...

I know it was you who brackett5 initially replied to, but it seems that I may have resolved his issue here as he "thanked" my reply. I think he may just be answering your queries and isn't quite lost...

I know how helpful you are and try to be and I just didn't want you to through a bunch of trouble going down a whole road that's already been resolved...

...with that in mind, please feel free to carry on....
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
Just the one on my laptop. I'm guessing I'm doing that wrong?

---------- Post added at 09:40 PM ---------- Previous post was at 09:37 PM ----------

I haven't gotten to try it yet. I will have to tomorrow. I will let you know what happens.

While I have you wise fellas attentions, I was thinking about doing the beta programs. Should I root before I try or should I just forget the beta program all together?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Oh dude, not a big deal at all. Glad you got him sorted out. That's why we're all here bruh, to help each other out :good::cool:

---------- Post added at 04:09 AM ---------- Previous post was at 03:41 AM ----------

Wise fellas huh! That's funny ? it's your phone bruh, do what you like. Personally, I could care less about betas. I'll update my device when it's official. Not ridiculing anybody's decision to try them out, but it's just not my thing. My stock + root is just fine and dandy to me, it's easy to update each month, and runs beautifully. Just my 2 pennies worth ??
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
BETA SNOB ALERT!

<woot-woot>

BETA SNOB ALERT!

<woot-woot>

*ALL YOUR BETAS ARE BELONG TO US*
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
Ok, don't hate me for these questions lol. If I opt out and I go back to the latest build, I don't lose the unlocked bootloader again do I?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Nope! Bootloader will remain unlocked unless you lock it up yourself with fastboot or dueces script :good:
[Google Pixel 2 XL Guides, News, & Discussion] mayorblurps:
Those of you on the latest May release AND a Fi user.

Did you update using the regular taimen or the 'fi-specific' taimen version? Up to April release I've used the regular taimen release without any Fi issues...first time I've seen the Fi only version along with the generic taimen version. Worried if I flash the non-Fi that something wonky will happen

[MENTION=4670411]Az Biker[/MENTION] - any thoughts?
[Google Pixel 2 XL Guides, News, & Discussion] slogar25:
I would just update using the fi specific version. It obviously has some FI specific fixes.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
I'm currently running DU and haven't even tried the factory May image, so I'm afraid I'd be little help (as usual when it comes to FI issues) :p

Sorry.
[Google Pixel 2 XL Guides, News, & Discussion] cognitivedissonance:
While you're updating the OP, you might want to amend this bit just to eliminate the confusion with that bit. Thanks again btw.
[Google Pixel 2 XL Guides, News, & Discussion] last_nooby:
Hi folks, I just flashed the new (May) update using this guide and for the first time my phone wasn't flashed as deep reset (as happened with previous updates). I still have my data, my apps..

Is it something new?
[Google Pixel 2 XL Guides, News, & Discussion] cognitivedissonance:
Hi there, is there any reason for me to update to the May release? I'm on the April one with an unlocked bootloader, magisk (16.0 stable), magisk manager (5.7.0), the Flash kernel (v2.34 stable), and the latest TWRP (3.2.1-2) with touch interface working properly. I'm sorta hesitant to update. I don't want any incompatibilities cropping up, any wiping of settings or data, or anything of the sort.

Also, updating would mean I need to flash something overtop of my current setup, which sounds a lot like "dirty flashing" to me, and that always kinda gives me pause.

If I do decide to move to the update, anyone have suggestions about whether I should use the factory image or the OTA method?

Besides the steps below, do I need to do anything else?

Probably reflash the kernel and magisk in TWRP before booting?
[Google Pixel 2 XL Guides, News, & Discussion] DanteXXL:
Running into a bit of a battery issue, what should I do to factory reset the phone?

I'm unlocked, rooted with TWRP.

Thanks!
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Just download the May factory image and follow this, no problems at all.

Whether or not you'll get more features with the May updates isn't the most important feature, it's the security updates.

And if you remove the -w from the flash-all.bat file, you do wipe everything BUT your internal sdcard, so it's basically a clean install.

It only takes a few minutes, and flashing new stuff is like opening presents on Christmas morning, without the annoying music, snow, and fruitcake!

If I wasn't running DU weeklies, I'd be updating my factory image every time one came out, bar none!

Just one guy's humble opinion.
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
[MENTION=4433558]cognitivedissonance[/MENTION], it's as Az Biker says....

Also, I'm certain Badger50 and nathanchance (and me as well, but not that it weighs as heavily as these guys' endorsement) would say that updating via Full Factory image (versus OTA) would be the best way to go -- and given that, it wouldn't necessarily be "dirty flashing" really in this case. I know when using my Galaxy S5 and Motorola Droids that flashing the OTA's were considered "dirty flashing" really -- as there are benefits from wiping everything and installing a fresh full factory image -- but with Google's Pixels, since (I imagine) it's their software and OS, they make it easy(ier) to update/install/flash full factory's than other phones. Simply taking out the "-w" wipe option in the command (or in the .bat file in this case), you can install a fresh Full Factory image -- which does not install over the existing partitions -- and still keep your data and makes it not necessary to restore any/all of your backups. Also, going from root (Magisk & the fact that there is no more recovery.img or partition) to a state where you can sideload the OTA is actually more hassle and, since it would be installing "over" existing partitions, is actually considered more of this "dirty flashing" than the alternative. I've seen both these guys say that it is just simply safer and more stable to flash the Full Factory than unrooting, sideloading, and there potentially having conflicts and bugs -- interesting note: either way you would have to re-root and re-install kernels, modules, ROMs, etc..

But, if you are still interested, I did a write up and/or a whole guide is here (extremely similar but put together by another user) to follow if you so wish...

TL;DR Whether or not there is any more benefit from one month's security update patch that's been detailed or expressed than any previous months', it's still a really good idea to be current with Google and their patches to their OS as well as the fact that we are rather lucky to have access to it; I read articles about Samsung and many other phones having issues on getting an update once every 3-4 months if that! Our Pixels and Nexus's should be considered rather fortunate in that regard... So why not take advantage...right?
[Google Pixel 2 XL Guides, News, & Discussion] cognitivedissonance:
You guys are awesome. This is insane that I can flash a factory image, flash a couple more files and it doesn't just obliterate my setup (I'll be very aware of the "-w" obviously.) Super pumped to flash now. Thanks again guys!
[Google Pixel 2 XL Guides, News, & Discussion] brackett5:
So after a crazy work week and trying the beta, which wasn't bad, I decided to try this again and root. Thanks to your guide, I was successful!! Thank you very much!!!!
[Google Pixel 2 XL Guides, News, & Discussion] Kamkor82:
Just for clarification purposes for me, and so I have everything prepared, updating with the factory image method and removing the -w flag, you still have to re-install all apps and re-set up all phone settings, correct? Along with re-rooting and kernel if you use a custom kernel?

So it would be a good idea to have a Titanium backup of all apps and data in that folder prior to update?

I've got the steps down but I just want to see about preventing downloading everything again each time, as I normally dont have WiFi access.
[Google Pixel 2 XL Guides, News, & Discussion] srqrob:
With the -w removed, you should not have to do any app reinstalls or configuration. Might lose an app password but usually not from my experience.