yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL Guides, News, & Discussion] magicfajita:
Hello, when I try to flash updates using the method where I download the zip from the stock images, extract, and run the flash-all.bat, I try to boot and it says google, then it goes black, and says my phone is corrupt and I shouldnt trust it, I continue, and it gets stuck on Google boot logo. Tried doing a full wipe and reinstalling, same thing, tried flashing the 8.1 preview, same thing, tried before the Nov update, same thing. I already did fastboot flashing unlock and fastboot flashing unlock_critical. Please help
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
So far from what I've seen, USB cable, not having the newest versions of adb and fastboot or human error have been most of the issues. Hopefully someone who has worked through this same issue can chime in. In the mean time try a different cable that is not usb-c to usb-c as that had been mentioned and also verify you have the latest platform tools installed.
[Google Pixel 2 XL Guides, News, & Discussion] clothednblack:
So, if I am in the beta program (8.1.0) and opt out, the phone fails to install the previous 8.0. I was rooted but un rooted with magisk because I wanted to roll back, but apparently we can't do that. I was going to roll back so I could get the Nov fix update. Am I just stuck on the beta till its nolonger a beta?
[Google Pixel 2 XL Guides, News, & Discussion] Pkt_Lnt:
Here is a tool that might help get you out of this.

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

I have no direct experience with your issues, but that script has helped many resolve what appears to be similar issues with OTAs or updates.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I know you've been around a while, and I guarantee you know more about this stuff than I do, but, did you also do the standard "fastboot flashing unlock"? Didn't see it mentioned in your post.
[Google Pixel 2 XL Guides, News, & Discussion] Mentalmuso:
Say what. Is that really a thing? I glossed over that I think. So I'll relock my device let it erase.

Then do flashing unlock, let it do it's thing, reboot to bootloader, then do unlock_critical. Is it really that simple..
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yeah, pretty much. You might be able to do it without relocking. Give it a shot :good:
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
I agree. I only unlocked because I was not aware of critical_unlock at that time... then a week later, I fastbooted critical_unlock without ever relocking the BL.
[Google Pixel 2 XL Guides, News, & Discussion] Mentalmuso:
Does the order in which whatever unlock gets done first? Could regular unlock be done after critical?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
I can only speak from experience. I did...

fastboot flashing unlock first, then fastboot reboot bootloader, then did fastboot flashing unlock_critical

However, I don't think it makes a difference.
[Google Pixel 2 XL Guides, News, & Discussion] G111444:
I need help!

I was getting a message about an update so I tried following the update instructions. Now my phone freezes up at the white Google screen. I tried going back to version OPM1.171019.011, Dec 2017, but that does the same thing. I think I've already deleted everything because I forgot to remove the "-w" on about the third attempt flashing the update. Can someone point me in the right direction? thanks in advance.
[Google Pixel 2 XL Guides, News, & Discussion] jrbxx7:
Try deuces script. Should fix it.
[Google Pixel 2 XL Guides, News, & Discussion] G111444:
It did...thanks!
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
I've been meaning to ask someone this, but wanted it to be in the right context. What exactly is the script doing that the flash-all.bat script is not? Any thoughts? You or anyone else??
[Google Pixel 2 XL Guides, News, & Discussion] Mentalmuso:
My Linux distro must need a clean. I tried skipsoft tool on a Windows PC and I saw the twrp splash screen, it didn't boot fully, but at least I know where my problem was. I'll continue to use adb and fastboot on Windows for now.. man, I feel like a noob
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
Not able to install the OTA update on my phone.

Maybe the TWRP recovery is creating the problem . How to fix it up
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
If your on twrp, and rooted I presume, your OTA's won't work. Personally speaking, if your taking the time to root, and use twrp, why not just fastboot the factory image?? If you want to take traditional OTA's, then you'll need to unroot, and be on stock recovery. You may also want to look into the Deuces script to help facilitate your updates. Seems that standard OTA methods can cause problems once you've been rooted, and on twrp. Here's a link to the script.

https://xdaforums.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
Can't flash the system image via flash-all.bat script.

Error... bootloader is different
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Did you unlock both aspects of the bootloader?

fastboot flashing unlock

And

fastboot flashing unlock_critical
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
Unlock_critical command not working for me
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Hmmmm....are your SDK platform tools and device drivers up to date? Have you taken an OTA since you've got the device? Have you tried a different cable or USB port? What happens when your in bootloader mode when you type fastboot devices? Does it return your phones ID number?
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
The phone is updated, trying to install the Jan security patch. And yeah the platform tools are working fine for every other command.

Yes fsstboot devices command is working fine with serial number
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Stupid question, but after you downloaded the factory image, not ota, and then extracted the contents. Did you put the bootloader, radio, the other large zip folder, and the flash-all.bat file in your platform-tools folder?
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
Yes did the all the files like systemimg and other files around 15 in the platform folder
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Wow! Well then about the only other thing I can recommend is to try the Deuces script to see if you can get it working. Nothing is going to update properly until you get the unlock_critical resolved, which, unfortunately, is going to wipe your phone. So better start backing stuff up! :eek:

https://xdaforums.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
[Google Pixel 2 XL Guides, News, & Discussion] rickysidhu_:
So I finally got around to trying to unlock and set this up, ran into a problem...

I was able to unlock and unlock_critical just fine, but the flash-all won't work on my Mac. I run the script and get the following error:

/usr/local/bin/mke2fs failed with status 1

error: Cannot generate image for userdata

I'm pretty sure I have everything up-to-date as I'm following the OP instructions exactly. Any help would be appreciated!
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Going off of memory, I believe you have to edit the flash-all.SH file and not the .bat file if you're using Mac. Did you edit the .SH file?
[Google Pixel 2 XL Guides, News, & Discussion] rickysidhu_:
When you say edit, you mean I need to go into the .sh file and change something in there?
[Google Pixel 2 XL Guides, News, & Discussion] nathanchance:
I need to update the OP to install the few binaries that Google includes in the latest zip. I'll do this over the weekend.
[Google Pixel 2 XL Guides, News, & Discussion] Mentalmuso:
I'm starting to lose my s**t. I can boot into twrp temporarily, no problem, but flashing magisk or SuperSU causes a boot loop to bootloader. All I want to do is root and it's so painful.

January stock image flashed

3.2.1-0 twrp booted temporarily

Flash SuperSU sr5 2.82

Bootloop.

Am I meant to format data before hand or something? I feel like I'm missing something stupid.

And also, I have unlock_critical, though fastboot flashing unlock doesn't work afterward as it says already unlocked..
[Google Pixel 2 XL Guides, News, & Discussion] rickysidhu_:
Thank you!

In the meantime, I opened up Parallels and tried to do all of this with Windows. The flash-all seemed to have worked in there but then I got the message "Your device is corrupt. It can't be trusted and may not work properly". I clicked power to continue boot and now it's just stuck at the white Google logo.

I believe a non-stock boot.img causes this, but since I flashed stock factory images to both slots just now, confusing as to why that message showed up.

If I could get this thing to at least working state (for now), that'd be a lot better than being stuck in the bootloader:eek:
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
You definitely CAN'T use SU! Only magisk will work. Question, will the phone boot up? I remember you having trouble the other day, you said you already did the critical_unlock, but not the standard "fastboot flashing unlock" Is all of this correct?
[Google Pixel 2 XL Guides, News, & Discussion] nathanchance:
Flash the vbmeta image to the vbmeta partition, that should fix that error.
[Google Pixel 2 XL Guides, News, & Discussion] rickysidhu_:
That seemed to have fixed it! Booted into initial setup, phew.

Thank you times a thousand man. I'm going to stick with using my OnePlus 3T before continuing to mess with this Pixel. I'll await your updated OP instructions and will attempt another clean flash/rooting/etc.

I can't say thanks enough, you're the man:highfive:
[Google Pixel 2 XL Guides, News, & Discussion] Mentalmuso:
Yeah I had the phone booting with a working twrp just before, so thanks.. I'll eliminate SuperSU from my flash drive.

So from stock boot.img

Simply flash twrp

Then flash magisk

And it should boot right?
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
It should. In bootloader mode, if you haven't already:

fastboot boot twrp.img(or whatever you named it)

That should take you to temporary twrp, then flash the twrp.zip, custom kernel(if you want) then the magisk 15.3 zip, all in succession. Do not wipe dalvik/cache when done. Just hit reboot. Then it should boot up.
[Google Pixel 2 XL Guides, News, & Discussion] kheltek:
Here's the suggestion and what's worked for many. Download and install the magisk apk, click install and patch boot img. for now. Once that's done, pull the patched boot img. onto your desktop, boot into fast boot and fast boot flash patched boot img. You should then be able to boot up and be rooted. THEN, go back into fastboot/bootloader, and boot up with the twrp img. Make sure you have the twrp zip in a folder on your phone. You'll know if the twrp img booted correctly if you have to enter a pin. Once that is set, flash the twrp zip from the booted twrp like any zip, then flash a kernel zip (pick one), and THEN flash magisk. This should keep you rooted and keep twrp as the recovery on your phone.

---------- Post added at 09:10 PM ---------- Previous post was at 09:10 PM ----------

Here's the suggestion and what's worked for many. Download and install the magisk apk, click install and patch boot img. for now. Once that's done, pull the patched boot img. onto your desktop, boot into fast boot and fast boot flash patched boot img. You should then be able to boot up and be rooted. THEN, go back into fastboot/bootloader, and boot up with the twrp img. Make sure you have the twrp zip in a folder on your phone. You'll know if the twrp img booted correctly if you have to enter a pin. Once that is set, flash the twrp zip from the booted twrp like any zip, then flash a kernel zip (pick one), and THEN flash magisk. This should keep you rooted and keep twrp as the recovery on your phone.
[Google Pixel 2 XL Guides, News, & Discussion] Mentalmuso:
Ok thanks, I'm flashing back to stock again, then I'll do it all in that order. I obviously don't have to flash twrp do i
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Not if it's already installed. However, I would start the process over like just stated just to be sure.
[Google Pixel 2 XL Guides, News, & Discussion] Mentalmuso:
Unreal...

After 2 days, I'm rooted. Haha thanks for your help. Now I can mod this thing
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Saaweeeeeeeeeeet! VICTORY! :good::good:
[Google Pixel 2 XL Guides, News, & Discussion] Az Biker:
Sorry. I meant did you use the .SH file if you edited to remove the -w (prevents wiping the device) or just to be sure you used the. .sh file since you are on a Mac.
[Google Pixel 2 XL Guides, News, & Discussion] rickysidhu_:
Oh okay gotcha, I had a feeling that's what you meant but I wanted to be sure!

Yeah I ran .sh with the "w" since I have nothing on the device to begin with (fresh 2 XL).

I used to have the XL so I thought I'd be familiar with flashing factory images on this 2 XL, but seems like it's a tad bit more complex (or maybe it's just me lol).

Interesting thing I noticed though, when I download the factory images from the official Google site where they're located, two copies download. The second with a (1) at the end of the filename.

At first I thought it was a glitch but since nothing else was working I decided to let them both download. When both downloads finished, there was only one file in my downloads folder, very strange.

I'm going to attempt another flash-all and see if that changed anything. Probably doesn't but I'm using a friend's 3T at the moment so I can afford to wipe everything with the -w and start fresh as many times as needed.

I just want a clean install on both slots before getting TWRP/Magisk/Custom Kernel on there.

I'll edit this post and keep you/others updated in case anyone else runs into a similar situation!

I really appreciate the help!:D

Edit: the double download issue is no longer present and it also didn't change anything in regard to successfully flashing factory images.

Edit 2: I try to stray away from using toolkits but Skipsoft hadn't failed me in the past so I used it again and I was able to flash-all to both slots perfectly fine using it. Permanently installed TWRP, Flash kernel & Magisk! I'll still wait for OP to get updated instructions just because I prefer being able to flash-all manually, without toolkits. They do come in handy in times like these though!
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
Now the phone is stuck on Google Logo Screen

See this - https://xdaforums.com/showpost.php?p=75178566&postcount=170

---------- Post added at 07:08 AM ---------- Previous post was at 06:40 AM ----------

With Platform tool and Flashj all command am also gettign this error

target reported max download size of 536870912 bytes
sending 'bootloader_b' (36344 KB)...
OKAY [ 1.163s]
writing 'bootloader_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 1.170s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 1.920s]
writing 'radio_b'...
OKAY [ 0.586s]
finished. total time: 2.509s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.259s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.043s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1936 MB) to disk... took 53.290s
archive does not contain 'system.sig'
extracting system_other.img (568 MB) to disk... took 14.655s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
extracting vendor.img (349 MB) to disk... took 9.025s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 13902843 4k blocks and 3481600 inodes
Filesystem UUID: 59e3c384-f802-11e7-b7f5-f537d6061253
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424

Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done

--------------------------------------------
Bootloader Version...: TMZ12a
Baseband Version.....: g8998-00164-1710262031
Serial Number........: 711KPPB0684376
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
FAILED

Device version-bootloader is 'TMZ12a'.
Update requires 'TMZ12b'.

finished. total time: 0.031s
Press any key to exit...
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yeah, I saw that on the other thread. Gee whizz man, I wish I could help more, but I'm outa ideas. Hopefully Deuce, or one of the really smart guys can help you out. Sorry my friend :(
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
Is this the problem

checking product...

OKAY [ 0.003s]

checking version-bootloader...

FAILED

Device version-bootloader is 'TMZ12a'.

Update requires 'TMZ12b'.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Could very well be. Which factory image are you trying to use?
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
The latest one... 8.1.0 (OPM1.171019.013, Jan 2018)

I tried last two also ...all are giving me the same error
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
That's just weird. Read your install scrip again. Still looks like the unlock_critical is not getting done. And I have no idea how to solve it. I'm at a loss my friend.

About the only other thing I noticed is that the script is trying to flash to slot _b. Wonder if we can get it to the _a side and see if that works.
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
Finally Worked the flash-all command

this time i used the OLD system image with the same bootloader image which my pixel 2 xl has.

THanks Guys
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
So you used the 8.0 one? Either way, cudos to you for sticking with it :good::good:
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
yes with this bootloader img bootloader-taimen-tmz12a.img
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
Just for other folks info... if the update fails and your stuck with a dead phone, very often reflashing the existing installed factory image back over itself will get you back to a position where you have options...
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
But the OTA update failed problem is still there.

Now the phone is unrooted and run on the stock reocvery.

Still can't apply the OTA update.

See the screenshot.
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Oh mercy! At this point my friend, since your on stock 8.0, and you had success with the flash-all, maybe just update the same way to 8.1. Maybe??
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
Am on the 8.1.10 December Security pAtch. and Not able to install the January Security patch.

Tried to install the full factory system image.

Same error - Bootloader is different.
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
Not talking OTA, but factory image. Too many problems it seems with side loading OTA. Even Google has mentioned it recently. But anyway. Download the factory image for what is currently installed maybe and run the flash-all.bat with the -w removed. If you don't edit that -w out it'll wipe the entire phone. Or if it's actually in good shape now, download the 013 update and flash the same way.
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
Yes, am using the Full factory image. Not the OTA one

---------- Post added at 08:02 AM ---------- Previous post was at 07:58 AM ----------

See:-

checking product...

OKAY [ 0.001s]

checking version-bootloader...

FAILED

Device version-bootloader is 'TMZ12a'.

Update requires 'TMZ12b'.

finished. total time: 0.017s

Press any key to exit...
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
By chance, did you confirm that the critical_unlock was completed by running the command again?
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
I already unlock the phone with the fashing unlock command

now this command is not working for me

see the screenshot
[Google Pixel 2 XL Guides, News, & Discussion] CyberpodS2:
Did you do BOTH unlock commands?
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
Yes... One by one
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Yeah, got that. How bout fastboot flashing unlock_critical
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
Right now the phone is unlocked with fastboot flashing unlock

To run the fastboot flashing unlock_critical command, should I lock the bootloader first (fastboot flashing lock

)
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
No, just run the command and see what happens.
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
C:\Users\RAJESH\Desktop\platform-tools-latest-windows (1)\platform-tools>fastboot devices

711KPPB04376 fastboot

C:\Users\RAJESH\Desktop\platform-tools-latest-windows (1)\platform-tools>fastboot flashing unlock_critical

...

FAILED (remote: Flashing Unlock is not allowed

)

finished. total time: 0.002s

C:\Users\RAJESH\Desktop\platform-tools-latest-windows (1)\platform-tools>
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Ah crud! I just don't know what the problem is! I never would recommend locking the bootloader. But in this case, it might be necessary. However, I would hold off until someone with more knowledge than me can help out. If you do decide to lock it, make sure you keep OEM unlocking ON as well as USB debugging. Then and only then you can lock it down.
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
Last time i tried to relock the bootloader on Oneplus 3 and after that, the phone is hard bricked. No fastboot and no recovery.

So worried :eek:
[Google Pixel 2 XL Guides, News, & Discussion] Badger50:
Like I said, it's not something I'd recommend. I'd just hold off until one of the uber knowledgeable members can shed some light on the matter.
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
Yes. Will wait
[Google Pixel 2 XL Guides, News, & Discussion] Surge1223:
I thought the newest factory image had TMZ12b bootloader img in it. This sounds like the wrong factory image.

Anyways if not check the info shown when you run

fastboot oem device-info

Also run fastboot oem unlock

Nothing happens if it fails, don't worry
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
The bootloader is already unlocked.
[Google Pixel 2 XL Guides, News, & Discussion] Surge1223:
What does unlocked mean to you?

You're not unlocked critical, means you can't update critical partitions. I was asking you for that info and because it doesn't hurt to run that command. I obviously know you're device is unlocked lol
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
Actually, i want to install the latest January security patch. But OTA will not work for.

The bootloader is unlocked and not able to flash the Full system image of the latest update.

Error. The bootloader is different.
[Google Pixel 2 XL Guides, News, & Discussion] Surge1223:
So grab the bootloader from the latest factory image and flash it
[Google Pixel 2 XL Guides, News, & Discussion] Vatumb:
That to not working..Some Critical partition error.
[Google Pixel 2 XL Guides, News, & Discussion] Surge1223:
What? Don't use a script literally download the factory imagine open a cmd prompt in the dir and just manually flash the bootloader img. There is no _b, for some of the images inside the bootloader img.

See this.