yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
Even if you traded in your pixel 2xl 64gb right now I'm great condition you're only getting $208 for it. I don't want the pixel 3 and the pixel 4 will surely be closer to or over $1k. I'd rather sirens a few bucks to fix my issues on my GP2XL because the phone just rocks
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Yeah....I tried putting you onto that company because I knew about them as well....I learnt from a Google rep as well when they couldn't find my (refurbished) IMEI in the Google servers that uBreakiFix are license repair contractors... So i'm glad you know/found of the alternative...

I see you...apparently Apple, Samsung, and other phone manufacturers (maybe not Google because they have so many lucrative divisions and may not depend as much on smartphone sales) are starting to get hit hard and not hit estimated (hoped, is more like it) "projections" because they are making their devices so well and technology is advancing so much that people are holding on to their devices for longer, finding less need on paying more and more expensive premiums while having perfectly working "chugging"/"humming" along devices... But I feel the sentiment, and it really makes me re-consider purchasing/upgrading; although i must say that the early "leaks" of the Pixel 4 has me seriously considering...

This is all true...hopefully I can find/get a good deal on the 4 because I'm afraid the "closer to or over $1k" might even be justifiable!:eek::silly:
[Google Pixel 2 XL Guides, News, & Discussion] srqrob:
Follow this link to [MENTION=1164058]azb[/MENTION]iker post and follow steps scrupulously and you will have joy.

https://xdaforums.com/pixel-2-xl/how-to/quick-2xl-upgrade-reference-8x-oreo-to-t3826330
[Google Pixel 2 XL Guides, News, & Discussion] johnlgalt:
I said a similar thing prior to upgrading from the BIONIC to my Shamu. Then again prior to upgrading the Shamu to my Taimen.

You have to realize that this is all subjective. No one thinks you should, or should not, upgrade - it's your choice. I paid ~$1000 for my Taimen (128 GB XL) and it is in mint condition - but I've also never traded in an old phone for a new one. I still have (and in working order) my OG DROID, my BIONIC, and my Shamu. Yet, I am already making plans for upgrading to the P4XL when it comes out. Why? Well, while my Taimen does still, as you say, rock, it's getting long in the tooth when it comes to advanced applications, particularly those that continue to use more and more CPU processing power, and especially with the current iteration of the Android Q Betas and Magisk, it is starting to show its age, taking longer and longer to do things (yes, I've been through a variety of Magisk fixes, and I'm pretty active in that thread, so I know what does and what has not worked for me). But there is more - I'm using Blokada actively to block as much surreptitious advertising as I can. I have more than a couple of weather apps installed (6 to be exact - most with active notifications disabled but with alerts enabled) because I am a weather chaser. I game on my phone at least an hour an night. I want the processing power that a 2 generation newer processor will provide.

For my folks, though, who are still rocking their pair of Galaxy S8s, they, too, have no need for any sort of upgrade - and until VZW offers them a decent phone at a price they consider fair (aka free) they won't. And I don't bother telling them that they are on what amounts to over 2 year old phones. Their devices, their choices. My device, my choice.

OTOH, I'm not one of those people who keeps buying a new device every 2/4/6 months - I use my devices for 24 months minimum, and more if I can get them to keep working well enough for allowing skipping a generation. Then again, I'm the king of using old hardware - my most current computer is a desktop powered by a Core i7 965 EE (yes, 1st gen i7) with 12 GB RAM, a 960 GB SSD paired with a 256 GB SSD, and 3+ TB Storage, an nVidia GTX 970 video card, and a pair of full rotation 23" ws monitors. I don't need the processing power on my computer - it plays the games I want it to, and performs the tasks I want it to - so I can afford to splurge on the phone every couple of years, if need be.

And my 128 GB variant nets me $228 - but I'm not letting it go. Just in case I need a backup - for whatever reason.

I'm going to finance my next phone through Fi just like I did wit my Taimen, since it just spreads it across 24 months with no interest. I've got mixed opinions of the P4, but I'm really hoping that they are joking about removing the dual front firing speakers - as Ive mentioned in the Pixel 2 love thread, I've already given up my removable battery and headphone jack. If the P4XL doesn't have dual front firing speakers, I might have to seriously take a look at some of the alternatives out there - although my Fi account will naturally limit my choices.
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Hmmmm. I hadn't heard that...but then again, if they were attempting to go with getting as close to an infinity screen as possible, it's hard to imagine them being able to include 2 front speakers like in the Pixel 2 -- which is a feature I enjoy greatly as well...

I may be biased, but I look at it more as better to lose the front speakers and gain pinholes than to have what is on the Pixel 3 where you get the speakers but a godawful sore that is its notch; versus the simple front facing speakers versus pinhole....

But I'm with you that it'll be a significant loss of something rather unique (if it remains true...)...
[Google Pixel 2 XL Guides, News, & Discussion] johnlgalt:
Yeah, all of the more recent renders show a single speaker up top. I'm slowly (but surely) resigning myself to the lack of dual speakers. Gonna suck, though.
[Google Pixel 2 XL Guides, News, & Discussion] tetra.proxy:
Issue with Patching boot Image

I am using Magisk Manager 7.3.2 (224) on my Pixel 2 XL with an unlocked bootloader. I go to patch my taimen zip (from google) but I get a U"nsupported/Unknown Image format" error. Does anyone know why that might be or know of a known good pre-patched img file? I am using a google Fi version if that matters.
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Hi there! Welcome to XDA Developers forum!

It is likely that you have missed a couple of steps in rooting & patching the boot image (.img) "(from google)". I suggest you go back to the OP/first post and carefully read the steps and directions again. Make sure you download the Full Factory image "(from google)", extract the proper .img file (boot.img), properly "push" that .img file to your phone (the OP directs using an adb command, but if you know other methods and what you are doing...), that you are correctly using the Magisk Manager app to patch, and that you are "pointing" the app to the proper .img file (you had just, supposedly, pushed to your device) -- these are the "steps and directions" I suspect you may have missed or been mistaken at. Also, keep in mind that I'm just mentioning these beginning starting steps as there are more steps to do after this point, but since this is as far into the method as you mention, this is as far as I would critique.

If you find all of this too complicated and troubling, I highly suggest instead of manually patching the boot.img file and manually pushing it to the device, that you (temporarily or permanently) run TWRP and install/flash/root via Magisk's installation .zip file as it will automatically and properly patch the boot image/partition as well as properly set and install it in the proper "slot" (either A or B). I have found that there are very many that have had issues and gotten stuck at patching the boot image file manually and would really benefit from just booting up TWRP (even temporarily via the "fastboot boot twrp.img" command) and installing the Magisk installation .zip file and letting the "pros" coding handle all of that instead.

Hope this helps...
[Google Pixel 2 XL Guides, News, & Discussion] johnlgalt:
Have to agree with [MENTION=4618389]simplepinoi177[/MENTION] - I have the same device as you, Pixel 2 XL (which I affectionately refer to as Taimen in all of my posts) and on Google FI as well. The manual process worked flawlessly, but using the fastboot 'boot' command to temporarily boot TWRP and directly flash the magisk,zip that you can obtain from the Magisk Git repository.
[Google Pixel 2 XL Guides, News, & Discussion] ghostbusted:
Guys are this method still working? I'm thinking of unlocking my phone

what's the different with the critical unlock ?

please advice

thanks
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Check the 9x upgrade link in my sig.

(*critical_unlock required with bootloader versions PRIOR to TMZ20a)...

If your bootloader is newer than TMZ20a, critical unlock is not needed.
[Google Pixel 2 XL Guides, News, & Discussion] ghostbusted:
Thanks for the answer, but how can I check my bootloader version? I'm using the latest official update
[Google Pixel 2 XL Guides, News, & Discussion] rockingondrums:
I know it's a bit late, but I scrolled down to the Linux certain, and it's only the tools. You don't install them, the adb and fastboot file (I forget the extensions) are what do the work.

I can't remember if I had to set up the "path" so I could just type adb and have it work. I messed with my path for another reason, believe it was pixel 1 related. Something about a file called android.51 or something. HTH.
[Google Pixel 2 XL Guides, News, & Discussion] collegencmc:
Nope not the only one that hit the issue with the other TWRP versions. I'm also glad, as I couldn't get it rooted any other way.

As a side note if your stuck in bootloopm or don't want to flash OTA like:

fastboot update image-taimen-opm1.171019.011.zip

Use Deuces script: HERE

Works great!!
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
I'm flashing Flash's cust kernel it's not a required step if you want to keep stock kernel.
[Google Pixel 2 XL Guides, News, & Discussion] andrewjt19:
[MENTION=6842057]nathanchance[/MENTION]

I was able to get the bootloader used using a different computer. My question is this... I've already soft bricked my device trying to install twrp 3.1.1 and magisk. I had to reinstall the entire operating system again. Do you have a recommended way of installing twrp? The other thing is how can I extract and install the following: stock bootloader, recovery and boot images? I've downloaded the latest 8.1 image for December. Thanks so much!
[Google Pixel 2 XL Guides, News, & Discussion] cwburns32:
Alright read this whole damn thread and probably could have come straight to this post. Came over from N6P, glad to see [MENTION=6842057]nathanchance[/MENTION] here. Google bought phone on ATT, still on stock on the Nov 8.0 Google factory build. Getting ready to unlock and critical unlock (before I ensure Fastboot/SDK Tools are up to date) and have a few quick questions.

- Do you recommend I install 8.1 first and then unlock or unlock on 8.0 and then do what you did above?

- I'd still like to receive my OTAs but don't mind sideloading them if need be. It looks like the above wasn't too difficult. Does that wipe your phone? (I know unlocking will wipe phone but I am more asking for future updates)

- It appears we no longer have to patch the boot.img so long as we install Magisk via TWRP?

- I'm new to the whole 2 slots thing and just want to make sure I have good understanding of that before I start unlocking and flashing away....I'm no noob but the 2 slots is uncharted territory for me.

Your insight and guidance is greatly appreciated!
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Thanks, but I just collected the wisdom from everyone in the 2 XL forum, and consolidated it :D
[Google Pixel 2 XL Guides, News, & Discussion] cwburns32:
Thanks for your swift reply! I suppose my only question left is what does removing the -w do when flashing a factory image? :cool:
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Makes it so it doesn't wipe all your data. Kinda like a dirty flash of a custom rom :good:
[Google Pixel 2 XL Guides, News, & Discussion] cwburns32:
Cheers mate!
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Hey [MENTION=3064020]godzulu[/MENTION], how did things turn out?

Except that it's NOT a dirty flash or a cust Rom... Your example is invalid :p

Let us know how everything went.

Welcome to the 2 XL family!
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Ok AZ, it's just an analogy Hoss. :cool:
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
:D
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
BTW...get Beans to spill some goodness on our new toys bro! :good:
[Google Pixel 2 XL Guides, News, & Discussion] godzulu:
Thanks for the follow up. Been a crazy busy day here, but I got my issue sorted and I happy as can be. Running 8.1, magisk and Nathan's kernel. All good. Still not sure what I worked initially did to f'up, but a little adb here, a little fastboot there...and sh*t works..go figure :) Appreciate all the help and the guides here. Keep up the good work
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Well.... I don't flash and tell.... I know absolutely nothing.... But don't be surprised if there's a little sumpin sumpin in your Christmas stocking...

But seriously, I know nothing!
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Hahahahahaha...fair enough. Ride easy buddy :good:
[Google Pixel 2 XL Guides, News, & Discussion] louie 0607:
OEM lock greyed out saying carrier locked can I still root my phone please some one let me know many thanks
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Nope. You must have the Verizon version of the phone correct?
[Google Pixel 2 XL Guides, News, & Discussion] louie 0607:
Thanks not sure ? But Baseband is g8998-001221708311414and my Build number is OPD1.170816.025 is there a root method coming out ?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
From where did you purchase the phone??
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
Responding to you too help answer his question... Using the critical even if on a newer build can't hurt though right? It just doesn't accomplish anything and probably says it fails that function??
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
If you're on the latest update, you're definitely beyond the bootloader that requires critical_unlock.

But long press power & vol down to boot into bootloader to see version.

I'm not 100% sure. I imagine if critical unlock did work on later bootloaders it wouldn't really do anything, but I think the reason it fails on later bootloaders is because it's no longer needed?

Maybe someone with a lot more brain juice than me knows for sure :p
[Google Pixel 2 XL Guides, News, & Discussion] post-mortem:
Google says it is not needed & not to do it. I wouldn't do it. It may actually open you up to a security vulnerability.
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
Open question to anyone, if indeed that is the case...

For all of us old heads that DID need to unlock critical, I wonder if we are open to the possible security vulnerability. Lol
[Google Pixel 2 XL Guides, News, & Discussion] vermaekansh:
quick question???

My pixel 2xl is rooted, but due to curiosity I have enrolled for android Q beta program, and suddenly I have received Beta DP4 OTA.

now should I install it, have anyone done the same I did before and is everything working fine after that?
[Google Pixel 2 XL Guides, News, & Discussion] itslels:
Unless you're in the CIA, or something, I wouldn't worry too much about it.
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
Yeah considering many of us keep TWRP backups on our phones that were created without screen security for example. Lol This critical thing is nothing...
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
Well...to add on top of this...it's good to remember that you actually do have the option to "encrypt" the TWRP backups -- I imagine much in the same way that, without "decrypting" using a screen lock, all data is garbled and can't be read/understood...

So...with or without the "screen security", there is still a way to somewhat protect these TWRP nandroid backups...for those who weren't aware...
[Google Pixel 2 XL Guides, News, & Discussion] johnlgalt:
Probably not - you have to remember that the newer bootloaders do not need the function call to be run in the first place, and that (as reported in a few places) it simply fails. IOW, the unlock critical no longer works because what you were unlocking is no longer unlockable (which can either mean it is permanently locked, or that it no longer exists, to take 2 scenarios).

So, if you previously unlocked it, it won't matter, because the newer bootloaders will remove the vulnerability anyway.

At least, that is what I got from talking to a couple of people about it briefly when I finally decided to root after Pie was stable on my Taimen, right before Q Beta was announced.

There is that. But I figure that if I am going to run around with my BL unlocked anyway, I'm pretty positive that I am not too concerned about the data on my phone being hacked in the first place. When I first got the Taimen, I kept the BL locked and never rooted - and my data was safeR than it is now. But after 15+ months of ownership, I've decided that I can take the risk - and have moved any appropriately sensitive data off the phone completely.
[Google Pixel 2 XL Guides, News, & Discussion] trim81:
For the past few security updates, removing -w is not working and causing a full format.

Anyone else?

I'm flashing with a macbook
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
I haven't updated for the last few months as life has kept me busy.

In the past, I have had to save the edited flash-all file more than once to get the remove -w edit to stick, which caused a full format.

When the July update comes out, I plan to get my 2 XL up to speed and current, I'll keep an eye out for this and report back.
[Google Pixel 2 XL Guides, News, & Discussion] srqrob:
I've removed the -w for the last few months with no issue. All updates have worked flawlessly.
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
Call it paranoia but I always reload the file in notepad++ after saving it to make sure I didn't have any typos. I have never had it not keep my changes. Interesting issue...
[Google Pixel 2 XL Guides, News, & Discussion] ghostbusted:
Guys please confirm if this already corrected steps for sideload to the latest ota,

Sideload the ota using OP instruction - Flash Magisk - flash custom kernel- reboot ?

Pleass advice
[Google Pixel 2 XL Guides, News, & Discussion] trim81:
Do you flash on a windows or a Mac?

I'm using the method with a Mac.. And it's been formatting for the past 3 updates
[Google Pixel 2 XL Guides, News, & Discussion] srqrob:
Same.

---------- Post added at 05:53 PM ---------- Previous post was at 05:52 PM ----------

Win10.
[Google Pixel 2 XL Guides, News, & Discussion] johnlgalt:
Copy the instructions from the shell script / batch file (depending upon your OS) and paste into a new file, remove what you want to remove, save the new file as the shell script / batch file and then run that new file.

End of issues. Because a new file that you create as a user will already have the appropriate permissions for you to write to, and execute, directly out of box, because you're the one creating it.
[Google Pixel 2 XL Guides, News, & Discussion] trim81:
Thanks I'll give it a try
[Google Pixel 2 XL Guides, News, & Discussion] post-mortem:
You can always type the commands in yourself, one line at a time. You don't need to use the batch file.
[Google Pixel 2 XL Guides, News, & Discussion] billgufran:
Hello. I'm trying to flash TWRP and Magisk from Pixel 2 XL Q beta 4, but I always get failed to mount /system (invalid argument) and failed to mount /vendor (invalid argument). I've tried manually mount it but it won't do. Does anyone know the solution for that? Thank you.
[Google Pixel 2 XL Guides, News, & Discussion] johnlgalt:
A little more information, please. Because, first of all, you don't flash from the Taimen, you flash TO the Taimen. And, most likely, you're trying to flash TWRP directly, which, last I checked, could not be done directly, you'll need to live boot TWRP and then use TWRP to flash TWRP if you actually want it installed, and use TWRP to flash Magisk. However, there might be more, as the order may also be important.

But if that is not what you are doing, and you are actually booting TWRP, and then trying to flash from inside TWRP, then we need more info to see what you're doing so we can actually provide help.
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
Hey, guys, I'm asking this question here because this is the thread where I learned how to root the Google Pixel 2 XL and many of you have helped me with a lot along the way.

Last month I noticed that when charging my phone using a type c to type c cable I could only put the charger in one way and the phone would charge. If I pulled the charger out and turned it over (not using the other end, actually flipping it over) then my phone would not take a charge. This only happened with type C on both ends cable. If I had used a USB to type c then it would charge no matter what which way I had it in. At first, I thought this was a cable issue so I tried three other cables and had the exact same problem. At that point I thought there was something wrong with my charging port so I reached out the to community in XDA but didn't get much feedback as no one else experienced this problem. Again I did not notice this problem until June after I installed the June security patch.

Today I installed the July security patch and the cable works fine now. I can put it in the charging port anyway and it will charge. I have tried this several times with several different cables, all the same cables that were failing before, and they all work perfectly now.

My question to you is; does the software have anything to do with how the phone takes a charge at all? I'm no expert in this but I am currently learning how to write Java, and I know that has nothing to do with my question, but I was just thinking this is now a software issue and not a hardware issue. Does anybody know enough about this to possibly explain it to me?
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
I just updated to the latest everything using the 9x Upgrade Guide in my sig.

Not a single problem, even removing the -w worked. The basic steps in the guide are still spot on :D

I was still on the March factory image (I know; lazy, lazy, lazy), but now I'm running the latest factory image, latest TWRP, latest EX kernel, and latest Magisk :good:

Just thinking out loud but could your -w issues be Mac related?
[Google Pixel 2 XL Guides, News, & Discussion] post-mortem:
It's either a fluke, or the cable (or port) is not truly reversible. Without some hardware issue, there is no way the software would know that you flipped the cable over.

BTW, did you ever try flipping both sides at the same time?

---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------

Just to be sure, which script were you editing and flashing? There are 2 scripts included, flash-all.bat and flash-all.sh.
[Google Pixel 2 XL Guides, News, & Discussion] Digital DJ:
Maybe it is a fluke, but I'll take it. No I never thought to try and flip both sides at same time. But I will and I'll let you know
[Google Pixel 2 XL Guides, News, & Discussion] trim81:
For mamy MacBook I edited flash-all.sh

This is the correct file to edit and run, correct?
[Google Pixel 2 XL Guides, News, & Discussion] post-mortem:
Yes, correct. The .bat file is only for Windows.

So I guess it goes back to what the others have said: double-check the contents of the script before actually running it. You could also type the commands in a terminal window yourself, so you know exactly what you're running.