yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
OMG how did you do this whole post without a single singular punctuation?!?!:eek:

and, after reading all that, we suggest trying different cables and ports because, for whatever reason -- at least with the pixel 2's -- it works with one set of cables and/or ports, and then craps out with the same other ones. Also, again for whatever reason, USB-C to USB-C seems to have a troubles that a USB-A to USB-C doesn't....
[Google Pixel 2 XL Guides, News, & Discussion] Strephon Alkhalikoi:
You're a better man than I am. I would have simply told him I couldn't be bothered to read what he had to say because he couldn't be bothered to break down his wall of text into discrete paragraphs with punctuation and capital letters. Seriously, if you want help put some damn effort into making your post readable. Otherwise you're simply going to be ignored.
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
Hello all it's been a while since I posted in here. I'm still running the Pixel 2 XL and opted out of moving to the Pixel 4. In all honesty I'm waiting for the Pixel 4A to come around as I'll probably go to that. I'm just tired of spending close to $1,000 on a cell phone.

That said I'm trying to take the January update which I do have downloaded and on my phone, but when I boot into recovery I follow these steps

1. Wipe the dalvik cache

2. Install the taimen update for January

This is the part where it goes really fast. it says it is done within like less than 10 seconds of starting the process. Generally this takes about 5 minutes to install the new image. but I thought I would check it out and see if it installed an image at all and it did not. So I read downloaded it and put it onto my phone after deleting the copy I already had there and I have the same issue.

Is anyone else having issues getting the January update image onto their Pixel 2 XL?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Did you take the update via OTA or downloaded it from the google site. Sup DJ! :laugh:
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
I actually downloaded it straight to my phone from the website. I visited the site on my phone and downloaded it straight there. That's what I've done in the past and it's worked every time.
[Google Pixel 2 XL Guides, News, & Discussion] Ghisy:
Maybe you should try flashing the full image from a PC and remove the -w in the .bat file so it doesn't wipe your phone.

Make a full backup before, just in case! ;)
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Or fastboot into twrp again and try it then. If it's a no go, then definitely do the fastboot routine :good:
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
So...my monthly "ritual" is to use TWRP to backup before going forward and doing any updating and reflashing.....

After creating some space, I'm running into the same issue [MENTION=6550255]ProoN[/MENTION] had been previously....

which is weird since I was able to take a backup a month prior when I had updated to the December (so running from November security version)...it is the same "createTarFork() error 255"...

I would've figured it would have something to do (and belong to) the issue of not being able to "mount" the partitions like before and/or have "write" access, but I was under the impression that it happened immediately when upgrading to 10/Q; so how was I able to do it coming from Nov.?!

In any case, if anyone else is in the same boat and/or have some idea to resolve this bug if it doesn't relate to the regular "mount"ing/write access problems TWRP is currently having...

Additional info: FWIW, it's able to create two ".win###" files that are 1.3GB partial's of the whole backup....
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Hey ol friend. Personally, I don't even try to use twrp on my backup P2XL anymore. I just use an older, but effective adb method. It generates about a 9gb file in my platform-tools when it's finished :good:

https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Thanks for this ol' buddy! I was already beginning to look into this as a "plan b" of sorts.... Now I have something pointed from a legend...!
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
Great minds, and all that schtuff. :silly:

https://xdaforums.com/showpost.php?p=80389539&postcount=3474
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
I downloaded the January image from the site to my PC then copied it to my device; all is well with my Pixel. Thanks for your help, though. It's good to see some of the Old Guard still active in here.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Legend!?....Bwahahahahaha..that'll be the day!??

Mine is pretty well shot. But, I don't mind, I rather enjoy the "ignorance is bliss" routine! Happy New Year ol friend...Er, at least I think it is! ??
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
Oh, it most definitely is! Happy New Year to you and yours and all the XDA hangers on. Things have really changed, but I still lurk here daily. :good:
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yeah, things have changed, somewhat. I'm on the P4XL forums a lot now a days. However, some of the questions are still the same. So, I reckon some things never change. Still love the one where people lock their bootloader without being full stock! And you know where it goes from there! Can you say..PAPERWEIGHT! ???
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
How you liking the new device??????????????????????????????????????????????????????????????????????????????????
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
It's pretty sweet my fiend. I like screen and sound improvements. The extra ram is nice, although I really don't have that much need for it since I don't game. The fluidity is a noticeable increase IMO, and I still get 8-11 hours of SOT just like I did on the P2XL. I do miss the FP scanner and led light, but oh well, I've adapted. Is it a giant leap from the 2, nah, not really, but I got it because I wanted something newer, and my battery and screen on the 2 was showing it's age, however, I still keep it as a backup, and keep it updating every month. I don't even miss TWRP. The Devs have done such a great job with kernel flashing, and magisk modules, that I don't even need it. I just use adb for backups now. Other than that, I'm glad I got it, and have been very satisfied with it :good::cool:
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
I'm so jelly!

View attachment 4922469
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Bwahahahahaha....I have a hard time believing a marine could be gelatinous in any way, shape, or form! Although, I'm sure your feeling father time creeping in ever so slowly! I didn't use to creek as much when I get up in the morning! ???
[Google Pixel 2 XL Guides, News, & Discussion] Ghisy:
Whaaa-? You got 8-11 hours of SOT on the P2XL? How? Is this sorcery?! O_o
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
No sorcery man, although I wish?

I'm a very light user. No gaming, social media, on wifi 80% of the time, dark mode always, screen brightness averaging around 40%, rooted with Ex kernel and a few magisk modules, and mostly do web browsing and on xda a lot. And that's it :cool:
[Google Pixel 2 XL Guides, News, & Discussion] Ghisy:
Ah, that makes sense then! I still get between 5 and 6 hours of SOT daily. Been debating getting a P4XL but waiting for a good opportunity. I'm not spending 1000 bucks on that phone!
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I totally understand on the $$'s my friend. Personally, I'd wait until July to see what the P5 has to offer. By then leaks and renders should be out and about. If not much has changed, then you could get a P4 for a decent price I would think :good:
[Google Pixel 2 XL Guides, News, & Discussion] pantallica420:
Voice to text and the simple fact of testing it and personally not worried about who ignores or reads it. I have more important things to seriously worry about. Honest note though is that I've had issues with my voice to text and well I have been a member of this forum longer than a lot of people on here though I've not had time to bump my junior to senior status. The once in a blue moon time I actually respond to anything is on something outdated and such. You can tell me anything you want no matter how nice or how mean you wish. I've seen people knock and straight belittle people on here to the point of questioning exactly how helpful some people are on here. For the most part people are friendly though there are others that are snide and downright rude. My opinion is there is no dumb or stupid question and yes it may be in the wrong part of whatever they're asking in but seriously!? Some feel the need to belittle them when maybe they honestly don't know? I'm not saying you personally but what I have seen just in this device forum in general. I honestly don't care what is said of anything I have posted. Opinions are a dime a dozen and sometimes people don't understand nor see the real reasoning behind things asked or posted. But if you seriously read what I posted especially when it's an obvious ramble on then I apologize but I have my reasoning and have stated such. I am not concerned about getting kicked off of here and I am not concerned if anyone has something rude to say about it. I can't post what my true and honest response would be if someone said something rude. I do wish you a good evening as I feel your posts are informative and helpful.
[Google Pixel 2 XL Guides, News, & Discussion] Nikos2k:
Are you used to be paid by the word? [emoji2]

---------- Post added at 22:09 ---------- Previous post was at 22:08 ----------

Btw, "comma" and "period" work nicely in voice to text
[Google Pixel 2 XL Guides, News, & Discussion] Strephon Alkhalikoi:
When what you have to say is unreadable, no one is going to care what you have to say. They're simply going to tune you out. So, sorry if you don't like that, but it's true. And that isn't opinion, but fact.
[Google Pixel 2 XL Guides, News, & Discussion] Greenmirage:
Hi guys,

I'm relatively new to flashing ROM's and am struggling to find how to fix a '/vendor (invalid argument)' issue.

I have access to both ADB and fastboot and currently have reverted to the latest factory image.

The main issue being, is that I can't create any backups in TWRP nor can I access the file system from my PC when connected via the file transfer feature.

If I boot to TWRP I get the message "Keep system read only?" intially and I've noticed upon trying "mount" that both vendor and storage can't be checked unless "Mount system partition read-only" is also checked; so I'm assuming this here is the issue? The /vendor erorr also occurs when factory resetting via TWRP.

I've clean flashed multiple times and tried flashing different custom ROM's and reverting back to stock yet I still haven't figured it out.

The commands I used to clean flash are as follows:

-fastboot set active_a

-flash-all.bat

*Wait for phone to boot, power down and reboot into fastboot

-fastboot set active_b

-flash-all.bat

Boot into stock and enable USB debugging

ADB into bootloader and then into stock recovery

Wipe phone from there

Tried both using booting to TWRP and flashing it, the version is 3.0.0-0.

The factory image is 10.0.0 (QQ1A.200105.002, Jan 2020) and I tried with 10.0.0 (QQ1A.191205.008, Dec 2019) prior to this.

If anyone has any idea how to fix this please let me know, I really need my phone atm so any help is appreciated.

Thanks :)
[Google Pixel 2 XL Guides, News, & Discussion] Nikos2k:
Why do you wipe your phone from the recovery?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Often times vendor issues arise when there's a mismatch between the the rom and monthly security updates. If you are on lets say, the January security update, but your rom is still on the December update, then you will likely get a vendor error. You can pull the vendor.img from the factory image secondary zip and fastboot it with..fastboot flash vendor vendor.img

Hope you get it figured out :good::cool:
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Because sometimes you have to if you can't get into your OS :good:
[Google Pixel 2 XL Guides, News, & Discussion] Nikos2k:
Yes, but hasn't he already flashed twice the full firmware image by running flash-all.bat ?

(and without the -w option that would preserve the data partition)

The option in TWRP for "Factory Reset" and the option "Wipe data/Factory Reset" in the stock recovery, what do they do besides erasing the data partition?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Sorry, I thought you were asking your question not relating to the other poster, my bad.

Yes, he's wiped his system twice, apparently, by fastbooting the factory image with the -w.

Twrp will wipe the system and cache, but not the data partition unless you specify it to do so. The standard swipe bar you see will only wipe what I mentioned :good:
[Google Pixel 2 XL Guides, News, & Discussion] Nikos2k:
So the user above, by using the standard Factory Reset swipe bar in TWRP tries to erase system partition (which he has already wiped by fastbooting the firmware image) and the cache partition (which does not exist in pixel 2 xl), right?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Right :good:
[Google Pixel 2 XL Guides, News, & Discussion] Nikos2k:
Here are some ideas:

Error message when Factory Resetting from TWRP: a factory reset is not needed

Error message when Factory Resetting from stock recovery: a factory reset is not needed

Cannot access the file system from your PC when connected via the file transfer feature: If you mean that you do not see the system partition, probably this is not feasible anyway. If you mean that you see the device connected in windows file explorer but you do not see the sdcard files, try to select again the "file transfer" from the notification on your phone

TWRP backup not working: you could use the adb backup solution that badger has described above

If you really use TWRP 3.0.0-0 (which I doubt :)), try to flash a newer TWRP

(https://dl.twrp.me/taimen/)
[Google Pixel 2 XL Guides, News, & Discussion] Greenmirage:
I thought that might be the case too but after flashing the vendor.img nothing seemed to happen.

Initially it booted to the corrupt data screen but then booted up to stock again straight away. I've just reverted back to android 9 and tried to install lineage os 16.

Followed the instructions exactly but as soon as I dare to install magisk I get that same /vendor (invalid argument) error!

It booted to a black screen and looped a few times then booted up to stock android 9 again.

I'm totally stumped at this point :crying: Thank you for the help though

---------- Post added at 06:28 PM ---------- Previous post was at 06:03 PM ----------

To be honest, I couldn't give you a logical explanation passed the fact I watched a youtube video on returning to factory state and he instructed to :laugh:

About the -w option. I'm assuming this is referring to altering the flash-all.bat script and removing the -w from the fastboot -w update?

Is this is a necessary step? As I definitely haven't always done this when flashing back to a factory image.

I mainly mentioned this just in case it was at all relevant in understanding the error but you're probably right

The issue I have here is that the device no longer shows within the windows file explorer at all. So as you say, I'm unable to access the sdcard files.

Sure I can use ADB push and pull to push and pull files to and from /sdcard/ but that isn't as convenient and since it was working just fine prior to unlocking the bootloader and doing anything within TWRP I can only imagine it has something to do with my vendor issue.

Thanks for this, suppose I can at least use my phone this way and not have to lose all my data all the time:good:

I've 1000% been using the latest TWRP with both the .img and .zip, so I'm confident it's not that :confused:

Thanks for the help though man, if anyone else has any insight into what might be wrong please let me know

---------- Post added at 07:09 PM ---------- Previous post was at 06:28 PM ----------

If I was to say to want to return to using stock. I'm guessing I would just flash a factory image again and then lock the bootloader?

At this point i wouldn't mind doing so but I'm concerned about whether there might be issues related to the /vendor (invalid argument)? The file transfer already doesn't work in stock and I don't reckon it's a fault with my PC

Thanks again:good:
[Google Pixel 2 XL Guides, News, & Discussion] post-mortem:
Latest platform-tools? They don't always update the changelog, so you really have to download it again to make sure you have the latest version.

Dont relock the bootloader! It's not worth the risk.
[Google Pixel 2 XL Guides, News, & Discussion] Nikos2k:
If you leave the "-w" parameter as it is in the flash-all.bat script, it will wipe userdata (data partition with you apps etc and sdcard files)

If you want to keep your userdata when flashing the factory image, you have to edit the flash-all.bat script removing the "-w" parameter
[Google Pixel 2 XL Guides, News, & Discussion] Greenmirage:
I only very recently downloaded platform-tools but I'll give it a shot.

Also, point taken:laugh:

Seems like every ROM Eamo5 makes gives me a black screen/bootloader loop.

Have so far flashed BlissRoms, Carbon Rom, Colt OS and Ressurection Remix without fault but LOS16, Derpfest, LOS17 I've had no luck at all with.

Perhaps it is a vendor security mismatch issue? But is there an obvious way to tell?

Whenever I flash a factory image the security update in the settings has always matched the version but whether this is the correct way to check I don't know

---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------

Ah sweet, that's pretty handy. I'm assuming that's what's meany by a dirty flash then
[Google Pixel 2 XL Guides, News, & Discussion] Nikos2k:
If in stock rom and in some of the custom roms you do not have problem, and you only have problems in some specific custom roms, then yes, there is most probably a mismatch issue

In each rom's thread, they do not discuss what vendor.img version is required by the latest rom version?
[Google Pixel 2 XL Guides, News, & Discussion] Greenmirage:
I've only switched between Android 10 factory images (Dec + Jan security patch) and Android 9 (August security patch).

Am I required to flash the vendor.img separately from the flash-all script?
[Google Pixel 2 XL Guides, News, & Discussion] Nikos2k:
No, you do not need to flash vendor.img separately

Flashing vendor.img separately is needed when updating to a new version of a custom rom that requires the latest vendor.img, by only flashing rom.zip and vendor.img through TWRP without having a PC

Running flash-all.bat will flash everything
[Google Pixel 2 XL Guides, News, & Discussion] Greenmirage:
So after I update to the factory image specified in the custom rom installation instructions. Are you saying I then need to also update to the correct vendor in twrp before/after installing the custom rom zip?

If so that might be why certain custom roms aren't working for me
[Google Pixel 2 XL Guides, News, & Discussion] Nikos2k:
No, i am not saying this

Since you have flashed the full factory image in both slots, you do need to mess around with vendor.img

But if for example you had October's stock rom, and then had flashed a custom rom (that worked ok with October's vendor.img), and now you want to update to the latest version of that stock rom, and that version of stock rom requires January's vendor.img, then the quickest way (and the only way if you do not have a pc available) would be to

Install vendor.img (January's in this example)

Install rom.zip

Install TWRP.zip

Reboot to recovery (from within TWRP)

Install vendor.img (again)

Install Magisk.zip

Reboot to System
[Google Pixel 2 XL Guides, News, & Discussion] Greenmirage:
Ah I think i get you, apologies.

So you flash the vendor.img twice so that it's fully flashed to both A and B partitions just as the flash-all script would do.

But the rom.zip which is stock that you mention flashing, is this one file or are you just simplifying in words the flashing of the bootloader, radio and image file?

I didn't manage to figure out my issue with file transfer btw and doesn't seem like anyone else has this issue which is a little frustrating. I guess I can just use "adb pull /sdcard/" to get a similar outcome quickly for now.

The /vendor error still shows in twrp but I've flashed the pixeldust rom for now and am rooted with magisk.

It's weird, the /vendor error will show whilst installing like for example magisk and yet still installs magisk fine.

Backups in TWRP absolutely do not work for me though (at least in android 10), it gets all the way to the end and then throws a different error and deletes the backup.

Pixeldust seems to run smoothly though but of course not much different from stock.

Just need to figure out backups properly. Also not sure if to stick with a custom rom or go to stock with root. I feel like stock is less work and more secure in that you get the latest updates and security patches OTA whilst with pixeldust and other custom roms I'm assuming the only way to update is to download and flash manually and it's going to be some time after stock first receives the updates (correct me if I'm wrong).
[Google Pixel 2 XL Guides, News, & Discussion] Durkan:
I've been having the same issue for quite sometime. as a result I haven't been keeping up with any Android 10 or security updates via OTAs or otherwise as, of i can't get my PC to see my phone, and hence can't use ADB or fastboot tools I don't want to be doing any flashing... no safety net. Were you able to find out what was causing this issue?

Thanks
[Google Pixel 2 XL Guides, News, & Discussion] Superschmiddi:
Yes I solved the issue.

There was just a lot of dirt in the USB-C connector of the phone :eek:

You cant really see it, just take a fine needle, a thin wire or a paperclip and rub gentely but with pressure at the bottom of the connector :fingers-crossed:
[Google Pixel 2 XL Guides, News, & Discussion] pantallica420:
You are very true in that statement! Has nothing to do with if I like it or not and I do appreciate honesty no matter how, if bitter or salty it may or may not be. I have no shame in admitting a mistake or anything else.
[Google Pixel 2 XL Guides, News, & Discussion] vboy7:
how do you flash the TWRP installer zip? im on a mac, falling at the last herdle

Sorry im a noob at all this - just managed to get to the last step of installing TWRP --- can anyone tell me how do you "flash" the TWRP installer zip?
[Google Pixel 2 XL Guides, News, & Discussion] Lughnasadh:
First flash the TWRP image using fastboot. After that it will automatically boot into TWRP and then flash the TWRP installer in TWRP.
[Google Pixel 2 XL Guides, News, & Discussion] vboy7:
in terminal i typed fastboot boot and then dragged the img file into terminal window, then my phone screen loaded up with the TWRP screen but jut froze with that. it wouldnt let me do anything else. sorry i dont really know what you mean by flash the TWRP installer in TWRP, do you mean drag in into terminal do i need to type anything else? thanks for your help!
[Google Pixel 2 XL Guides, News, & Discussion] Lughnasadh:
In fastboot, you type fastboot boot <name of file>

Ex: fastboot boot twrp-3.3.0-0-taimen.img

Then use the install button in TWRP to flash the installer zip.
[Google Pixel 2 XL Guides, News, & Discussion] vboy7:
TWRP screen frozen

Can anyone help when i fastboot boot the twrp-3.3.0-0-walleye.img the TWRP screen comes up on my phone but just freezes and does not respond. Does anyone know how to fix this? I have taken my pin away as I read that can be the problem but it didnt help. Thanks in advance (and yes im using a google pixel 2)