yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] Felix_222:
Stuck in a complete mess, please help!

I'm coming from the first Pixel XL so I'm familiar with the process, however, I'm running into a lot of trouble and inconsistencies. I'll go through everything step by step. Please bear with me:

Notes:

-Purchased Pixel 2 XL from Google Store a few days ago. I have Verizon, though.

-Installed Feb OTA update while stock.

-Installed latest Platform Tools, latest drivers for Windows 10, and using factory type-c cable

-debugging enabled, oem unlock ticked on

Steps:

-adb reboot bootloader

-"fastboot flashing unlock" and i get the following:

-so i try "

fastboot flashing unlock_critical

" and it appears to work.

-pick up phone and hit "unlock bootloader." The phone goes through the unlocking process then reboots.

-I see the the unlock symbol at google boot screen. Awesome.

-reboot to bootloader, i see that bootloader is unlocked. awesome

-I then attempt to flash feb factory image and get the following errors:

-

-so i use Tool-All-In-One to verify bootloader unlock status and see "devices critical unlocked: false":

-

-So, I attempt to repeat "fastboot flash unlock" but the same initial "FAILED" error

-attempt to repeat "fastboot flash unlock_critical" but get "FAILED" error

-attempt to fastboot to twrp.img. but get "FAILED"

I'm not sure what to do. I get the bootloader unlocked warning at reboot, then the unlocked symbol on the google boot screen, the oem unlock ticker in developer options shows the bootloader is unlocked. However, fastboot commands aren't working and fastboot bootloader status command shows it is not "critically" unlocked.

What on earth is going on? Can anyone please help!
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
If you are still using the factory cable that is c-to-c then swap that out for a USB 3 to USB 2 design. Back in the beginning here many folks were failing at fastboot commands and it turned out to be the usb-c issue. It's not failing for everyone but I would start there.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
In addition to what CyberpodS2 said, are you sure your fastboot flashing unlock_critical was successful??? In one of your screen shots, it appears that it wasn't ?
[Google Pixel 2 XL Guides, News, & Discussion] Felix_222:
Worked like a charm! Thank you so much, what a relief. Ironically, my Pixel 1 XL was the opposite. Worked only the UBS-C-C.

Thanks for the input! That was one of the inconsistencies that confused me. The bootloader status said it was unlocked but not critically, which is the opposite of the fastboot commands.

Last question: I want to flash a new rom. Should I flash the feb factory.img if I already updated to feb via OTA?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Here's where the fun begins because of the A/B partition thing. The short answer is yes...but to both slots. Your likely on slot A atm. When you flash a new rom, it'll switch you slot B, problem is, the new rom is dependant on shared data from both the A/B slots, which is why you'll want to dirty fastboot the factory image to the B slot before you flash your rom. Hope that makes some sense to you :cool:

Oh...and don't wipe system in twrp before you flash the rom, and....set your screen lock to swipe on none before you begin your adventure ?
[Google Pixel 2 XL Guides, News, & Discussion] dredq:
Easy way to flash on both A and B is to use the Deuce script. Use it just like flash all. It works great.
[Google Pixel 2 XL Guides, News, & Discussion] pantmunu:
Hey guys, got a question, I still haven't jumped into the whole twrp thing. And I prolly won't for a bit. But I'm rooted with magisk and have flashed flash kernel(I like how it goes, flashed flash kernel). And I was wondering how the update process would go if I were to update to the march security build once it drops in.

TIA
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
This is how I do it, and it won't wipe your data :good:

And...remove or disable all theme overlays before you begin :good:
[Google Pixel 2 XL Guides, News, & Discussion] pantmunu:
Thank you good sir. Very much appreciated.
[Google Pixel 2 XL Guides, News, & Discussion] Ryder.:
Can i update with the ota with magisk installed? I have stock recovery
[Google Pixel 2 XL Guides, News, & Discussion] MikereDD:
You can use the factory images.

Just open flash-all script and remove the "-w" save file and run it.

Then reboot to fastboot and boot twrp and flash a kernel then flash magisk.

Reboot and have a beer or a taco or both.
[Google Pixel 2 XL Guides, News, & Discussion] Ryder.:
Ok but bootloader didn't update when i ran the flash-all script. It gave me error. I'd rather update with ota zip if it can be done with root installed...
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
If your bootloader didn't update, either unlock bootloader or unlock_critical hasn't been done, or there was a user error..

Fastboot flash latest factory image (remove the -w so it doesn't wipe the device)

boot into TWRP.IMG via fastboot

flash TWPR.ZIP in TWRP (skip if you don't want TWRRP to stick)

flash cust kernel in TWRP (optional)

flash latest Magisk (16.0 ATM) in TWRP (optional)

reboot,

profit

I still don't get why people are doing OTA updates or see the actual benefit of going that route.

The above process is so quick, so easy, doesn't wipe your data, and always works.
[Google Pixel 2 XL Guides, News, & Discussion] Ryder.:
I'll try... and if bootloader image doesn't update again?? You didn't answer my question. Can i still update with ota zip having root?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You'd have to side load the OTA of course, but yes, it should work. Having said that, I would 100% agree with AzBiker that having your bootloader fully unlocked, and fastbooting factory images is the easiest, most reliable way to do monthly updates. Not to mention, that if you bork something with your phone, you have a way to rescue it with the factory image :good:
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Don't know about the OTA, I've always just flashed the factory image.

If:

- you unlocked the bootloader, and

- performed critical_unlock, and

- you're using the latest SDK tools, and

- you've verified you're using the latest Google taimen factory image, and

- your fastboot files are in the same platform tools folder as the fastboot application, and

- your OEM unlocking toggle is ON (in Developer options),

- you've tried both a USB 2.0 & 3.0 cable, in different ports, and

- you're issuing the correct fastboot commands given in OP, and

if after all this, your bootloader still fails.... I wouldn't know what to tell you next.
[Google Pixel 2 XL Guides, News, & Discussion] pacman photog:
Anyone else getting failed to install!

I flashed clean March and Feb. Both fail install when black screen shows up
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Don't do February! Can you please describe what you did in a little more detail? :confused:
[Google Pixel 2 XL Guides, News, & Discussion] TanakaX5:
please delete
[Google Pixel 2 XL Guides, News, & Discussion] pantmunu:
So flashed latest March security update and can't seem to get magisk to work at all. Flashed flash kernel and magisk in twrp and when I go to check in magisk .. no root.

Also just watching the bootimage from.magisk isn't helping either.

Anyone else having this same issue ?

Tia
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Try opening the command prompt directly from the platform tools folder instead of power shell. Also, did you put your patched boot.img directly in the platform-tools folder?? And, the correct command is...fastboot boot xxxxx.img

---------- Post added at 04:07 PM ---------- Previous post was at 04:02 PM ----------

No issues with magisk or the latest Flash kernel here. Are you getting any errors in twrp when flashing? I assume your using the latest MM app and version 16.0 zip as well?
[Google Pixel 2 XL Guides, News, & Discussion] pantmunu:
Yup and no errors. It just flashes fine.

Also tried to patch it via magisk app and reboot and flash the patched boot in fastboot without flashing twrp and reboot. No luck. Just weird.

Worked fine on Feb update.
[Google Pixel 2 XL Guides, News, & Discussion] pantmunu:
Just some screenshots to show that I have the patched kernel
[Google Pixel 2 XL Guides, News, & Discussion] TanakaX5:
yo Badger,

thanks for the reply

it was just my ****ing usb c-c cable... switched to c-a cable - done, worked

thanks anyway
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Nice! I always forget to mention the USB cables for some reason!! You'd think for close to 1k for a phone, Google would have included one!! I shall stop there before I get myself in trouble! ???

---------- Post added at 05:35 PM ---------- Previous post was at 05:34 PM ----------

What happens if you install the 16.0 zip from MM??
[Google Pixel 2 XL Guides, News, & Discussion] pantmunu:
Idk what I derped but it's working now. Still not gonna stick with twrp. Kept rebooting back to twrp after flashing twrp installer zip.

Everything else is fine now. Thanks ?
[Google Pixel 2 XL Guides, News, & Discussion] pacman photog:
I clean flashed March images.

Installed magisk from apkmirror with latest

Went to patch boot says downloading 16.0 goes to black screen says 3 lines and 3rd line says failed.

Doesn't do anything else. This happened when I flashed Feb over Jan. And still persists in March images.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
If your going to patch the boot.img, then you need to have the stock boot.img on your internal storage. Then when you get the prompt, you should be able to navigate to where the boot.img is, and then patch it. Then you'll need to fastboot the patched boot image. Have you tried flashing the 16.0 magisk zip in twrp??
[Google Pixel 2 XL Guides, News, & Discussion] pacman photog:
As I did as the black screen comes up. Like it would think it's starting to create patched boot. But as I said 3rd line says failed.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Then I would just flash the magisk zip in twrp and call it good.
[Google Pixel 2 XL Guides, News, & Discussion] pacman photog:
I can't flash if it fails lol
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Dang! You must have one of those ornery phones! Have you tried other versions of magisk to see if they flash in twrp???
[Google Pixel 2 XL Guides, News, & Discussion] cbasse:
So, I unlocked,flashed TWRP, rooted with Magisk, and flashed your kernel all the other day, but now can't seem to replicate it to flash the March update. I've edited the flash-all.bat to remove the "-w" to avoid wiping. I have everything in my platform tools folder. i reboot to bootloader via command prompt. ADB Devices recognizes my device. Then, from the command prompt, I type "flash-all" and get the following: 'flash-all' is not recognized as an internal or external command, operable program or batch file.

Any idea what I'm doing wrong? Thanks in advance!!
[Google Pixel 2 XL Guides, News, & Discussion] greyhd:
Double click on the script and it should flash all or copy the file into your CMD window and hit enter.
[Google Pixel 2 XL Guides, News, & Discussion] cbasse:
Ok, I won't be able to try until later, but just so I understand, I open CMD window, then double click on the flash-all.bat file, then hit enter?

Thank you!
[Google Pixel 2 XL Guides, News, & Discussion] dredq:
Make sure your phone is in Fastboot mode (turn on phone while pressing vol- and then release only power button).
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
I know this may sound crazy:

Are you on a Mac? (if yes, you need to flash the flash-all.sh file)

Have you tried a USB 2.0 cable? (if not, try it, it is one of the many wonders of the universe why it works sometimes, and doesn't other times)
[Google Pixel 2 XL Guides, News, & Discussion] dredq:
Did you unzip the files? Are they all in the same file? Are you sure the CMD is open in the the right file? If you have all your files in platform-tools does the CMD prompt say C:/platform-tools
[Google Pixel 2 XL Guides, News, & Discussion] cbasse:
Followed the instructions in the OP to the T...managed to get the "flash-all" command to be recognized (CMD wasn't open in the right folder), but now i'm getting the following errors...

target didn't report max-download-size

sending 'bootloader' (36344 KB)...

FAILED (remote: unknown command)

finished. total time: 0.004s

rebooting into bootloader...

OKAY [ 0.001s]

finished. total time: 0.002s

target didn't report max-download-size

sending 'radio' (60428 KB)...

FAILED (remote: Requested download size is more than max allowed

)

finished. total time: 0.004s

rebooting into bootloader...

OKAY [ 0.002s]

finished. total time: 0.003s

extracting android-info.txt (0 MB) to RAM...

extracting boot.img (40 MB) to disk... took 0.313s

target didn't report max-download-size

error: Failed to identify current slot

Any idea what I'm doing wrong?
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
- Make sure your SDK tools are the latest and greatest

- If you're using a USB 3.0 cable, try a USB 2.0 cable

IF you've done those^^^^ and things still no worky, Post the exact command you are using.
[Google Pixel 2 XL Guides, News, & Discussion] cbasse:
Go figure: switched to a different USB port on my laptop and everything worked fine! Thanks for all the suggestions!!
[Google Pixel 2 XL Guides, News, & Discussion] dredq:
Are you sure you have all the files in the same location? Did you unzip the folder inside factory image and place all files in the platform-tools folder? Try using deuce script. It is great. Maybe start over. Delete the platform-tools folder and begin fresh making sure all the files are in the same folder and unzipped.

https://xdaforums.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761

---------- Post added at 11:31 PM ---------- Previous post was at 11:27 PM ----------

Glad you got it to work. It is really weird how different cables seem to work as well as different ports. I have found the USB-A to USB-C cable works much better than the USB-C cables. Just is weird.
[Google Pixel 2 XL Guides, News, & Discussion] bigthugs0:
Any one succeeded to root Android P on Pixel 2 XL ?

i tried patching boot.img with Magisk , but no success, phone booted without root
[Google Pixel 2 XL Guides, News, & Discussion] drmoeed:
Hello,

Is there any way the Verizon Pixel 2 XL bootloader be Unlocked ????
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Not at this time :(
[Google Pixel 2 XL Guides, News, & Discussion] drmoeed:
How cruel ... ?

I can't believe I am going to miss Android P DPs ... :(
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You could always sign up for beta program :good:
[Google Pixel 2 XL Guides, News, & Discussion] drmoeed:
Yeah ...

But just thinking, betas are always buggy ... One give a try, for a few days and then get back to stable image ...

If I sign for beta programe, would I be able to move back to Oreo 8.1???
[Google Pixel 2 XL Guides, News, & Discussion] force70:
Yes but you will have to wipe your device

sent from my Pixel 2 XL or Note FE
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I know you can on the Google version with unlocked bootloader and fastbooting the factory images. On the Verizon version, I'm not sure if once you unenroll from the beta program, if you can then take another OTA, or side load an OTA to get back to 8.1. Gonna have to do some research on that one my friend :rolleyes:
[Google Pixel 2 XL Guides, News, & Discussion] drmoeed:
Yeah ... Leaving beta program sends the latest stable build OTA update ... That wipe the device after getting flashed ....
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Ah...thank ya kindly my friend :good:
[Google Pixel 2 XL Guides, News, & Discussion] drmoeed:
Ohh ... Well that can be the case ... Means I'm locked ... It's so so so bad feeling ...
[Google Pixel 2 XL Guides, News, & Discussion] Namolas:
Yes, in command window type,

fastboot --speak-with-your-wallet /stop-giving-verizon-your-money

Its not possible. Sorry. I really truly am. I had Verizon for 13 years and I know your pain.
[Google Pixel 2 XL Guides, News, & Discussion] drmoeed:
My bad ...

Would I be able to join Android P beta and then would get the stable build OTA if I leave Beta ...
[Google Pixel 2 XL Guides, News, & Discussion] dredq:
Yes
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
According to several concurrent discussions going on, nothing close yet.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
I love Verizon's coverage in my area, but I have bought my last three devices retail and unlockable (and will from now on) to run on Verizon's network.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Bwahahahahaha...funniest thing I've seen all day! Good one bro...Bwahahahahaha ????
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Not the least bit funny!

You have any idea how long I spent trying to get that command to work in fastboot???!!!!

Kept getting this error:

FAILED (remote: unknown command)

finished. total time: 0.004s

KEEP FEEDING BIG RED YO $$$(36344 KB)...

rebooting into bootloader...

OKAY [ 0.001s]

finished. total time: 0.002s
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Bwahahahahaha...that's the second funniest thing I've seen today!! Good one brother! And true to boot! ???
[Google Pixel 2 XL Guides, News, & Discussion] clothednblack:
New Twrp is out, decrypt is fixed.
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
Some reports that it's not flashing roms. I'll try when I get home from work.
[Google Pixel 2 XL Guides, News, & Discussion] mihir85:
Anyone tried downgrading from Android P to Android 8.1? Its not working for me. I get the following error while flashing update zip:

platform-tools 2 $ ./fastboot flash -w update image.zip

target reported max download size of 536870912 bytes

Invalid sparse file format at header magic

error: write_sparse_skip_chunk: don't care size 1069842709 is not a multiple of the block size 4096

error: write_sparse_skip_chunk: don't care size 532975893 is not a multiple of the block size 4096

sending sparse 'update' 1/3 (524284 KB)...

error: write_sparse_skip_chunk: don't care size 1069842709 is not a multiple of the block size 4096

error: write_sparse_skip_chunk: don't care size 1069842709 is not a multiple of the block size 4096

OKAY [ 1.322s]

writing 'update' 1/3...

FAILED (remote: No such partition.)

finished. total time: 1.323s

After rebooting its stuck at Google logo! any help would be appreciated.

Thanks!
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Are you trying to "dirty flash" to get back to 8.1?
[Google Pixel 2 XL Guides, News, & Discussion] MikereDD:
Use the flash-all.sh script
[Google Pixel 2 XL Guides, News, & Discussion] stumpy352:
Maybe the problem is that you're trying to "update" from p to 8.1. Might be missing something here, but I doubt there is an update image for what you're trying to do. Shouldn't you be downloading the full factory image for 8.1?
[Google Pixel 2 XL Guides, News, & Discussion] mihir85:
Removing the -w doesnt help. I get the same error. It is the full factory image, the flash-all.sh command doesnt seem to work either. just takes too long and does nothing

---------- Post added at 01:22 PM ---------- Previous post was at 01:20 PM ----------

How long do I wait for it? It doesnt seem to work

---------- Post added at 01:44 PM ---------- Previous post was at 01:22 PM ----------

Is there any other command to run the full factory image. It is the full factory image, but somehow fastboot doesn't seem to read the partitions. I downloaded the latest platform tools.
[Google Pixel 2 XL Guides, News, & Discussion] stumpy352:
You would have to extract all the images & flash them individually.
[Google Pixel 2 XL Guides, News, & Discussion] mihir85:
Tried that too. If I am correct the command to flash the image.zip is "fastboot flash update image.zip" ?
[Google Pixel 2 XL Guides, News, & Discussion] stumpy352:
I don't think so. The only way I'm aware of to flash the full factory image in one go is to execute the flash-all script. To flash the images separately you flash each image to the individual partitions.

i.e. "fastboot flash boot boot.img"

"fastboot flash recovery recovery.img"

etc.

I believe the image.zip you're referring to needs to be extracted to find the relevant images inside.
[Google Pixel 2 XL Guides, News, & Discussion] mihir85:
Right! trying that right now :)

Btw there are quite a few files here, is flashing modem, system and vendor enough?
[Google Pixel 2 XL Guides, News, & Discussion] stumpy352:
You need to flash them all in the right order. Maybe someone else here can clarify. Actually it should all be in the op.
[Google Pixel 2 XL Guides, News, & Discussion] mihir85:
Yes, that would be helpful because currently i am doing the following which is not working:

./fastboot flash bootloader bootloader.img

./fastboot flash radio radio.img

./fastboot flash boot boot.img

./fastboot flash modem modem.img

./fastboot flash system system.img

./fastboot flash vendor vendor.img

./fasboot reboot bootloader

Then rebooting..stuck at google plus unlock logo
[Google Pixel 2 XL Guides, News, & Discussion] simplepinoi177:
You may have already done/know this but.....also be sure you are on the latest "platform tools"... a lot of people forget and it's pretty much always assumed, and then a lot of time and frustration going down various paths when it was that that was the problem....

good luck to you...
[Google Pixel 2 XL Guides, News, & Discussion] mihir85:
I am still stuck at google boot image.

yes, i did update the latest platform tools, I am able to flash everything properly. no errors this time but I might be missing a step or two. waiting for someone to point out the exact steps.

UPDATE: Got it working using Deuces script!
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
Anyone know why I would get this kind of error trying to flash stock via the flash-all.bat method (see below) also is what my folder looks like.
[Google Pixel 2 XL Guides, News, & Discussion] nathanchance:
You either need to use a different USB cable/port or your driver/binaries are out of date.
[Google Pixel 2 XL Guides, News, & Discussion] vibrantliker:
How do I update driver/binaries?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
With phone in the OS and plugged in with USB debugging set to data transfer, open your pc's device manager, and look for android generic device or something like that. If there's a red triangle by it, it needs to be updated. Or go to the Google factory image page and look for OEM drivers. However, like Nathan said, it's probably your cable. If your on a laptop, use a 2.0 USB-A to USB-C cable, or a 3.0 for desktops.
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
I might as well get an iPhone.... you guys are all over 2 XL troubleshooting like a fat kid on a funnel cake :p

Sheesh... I might as well retire!
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Don't do that Hoss! Btw..I do like funnel cakes ??
[Google Pixel 2 XL Guides, News, & Discussion] pa.pn2:
Why not flash the factory image 8.1?

As i have read you have to go completely clean including the -w
[Google Pixel 2 XL Guides, News, & Discussion] mihir85:
Ya, thats what I was trying to do. Flash-all.sh was not working so I had to manually flash each file. The code for that I borrowed from Deuces' script. Went through, everything working fine now