yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 Questions & Answers] cb474:
When I was flashing factory updates on my Pixel 2 last night, I got an error at the first step (using the flash-all.sh method), when it flashes the bootloader:

sending 'bootloader_a' (38728 KB)...
OKAY [ 2.095s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 2.099s

This happened both trying to flash the original .010 factory image and the .018 November update (haven't tried .025 yet). I had problems getting .010 to work (I was trying to downgrade, long story, it seemed to get stuck at the G logo, I gave up). But .018 worked fine, even with the flash of the bootloader failing. In fact, the bootloader version is the same as in .010, the September factory image, so I guess for .018 it just did not matter that the bootloader did not flash.

But anyway, I'm worried about this "Command Flash Error." What does it mean? If a new bootloader really can't be flashed on my device that seems like a problem.

I saw a mention of this problem in these two places: https://www.xda-developers.com/pixel-2-failing-flash-factory-images/ (in the comments) and https://www.reddit.com/r/AndroidPre...one_unlock_the_pixel_2_bootloader_without_an/. But there's no real explanation or solution.

[Edit: Just tried flashing just the bootloader manually, from the .018 and .025 factory images, and it failed in the same way. It's the identical bootloader in both images so it's not surprising. So, indeed, the bootloader cannot be flashed on my device. Or at least the one that comes in .010, .018, and .025 cannnot: bootloader-walleye-mw8998-002.0059.00.img.]

[Edit, 12/7/17: The December update solves this problem. If you sideload the December OTA image, using adb, it updates the bootloader. After that it is possible to flash a bootloader image directly using fastboot as expected. So something was just wrong with the original bootloader on this device or how it was installed. The only situation in which this solution will not work, I think, is if you have a custom recovery, i.e. TWRP. I think then you cannot sideload an OTA image. You would need, I believe, to restore the stock recovery first, by flashing the stock boot.img that goes with you current version of Android.]
[Google Pixel 2 Questions & Answers] Ashray_Vk:
[MENTION=1871830]CB7[/MENTION]4 hi, did you find a way to solve this ?
[Google Pixel 2 Questions & Answers] ecs1984:
Bumping this thread as I'm in the same boat: "Command Flash Error" when flashing any bootloader.

Really annoyed with Google rn, because now that I recovered my phone to a previous factory image, I am now getting FC's on Pixel Setup and cannot even set up my phone again.
[Google Pixel 2 Questions & Answers] cb474:
I never found a solution. But I just saw this thread where someone says he found a way to fix it: https://xdaforums.com/showpost.php?p=74728097&postcount=8

It does require locking the device and unlocking the bootloader again, which of course wipes it. I am hesitant to do that. I do wonder from what's said in that thread if there is just something weird about the original bootloader that came with the device and that once the person in that thread got a a new version of the bootloader by signing up for the developer preview of Android that solved the problem. If that's the case then it would seem that sideloading the December OTA update might accomplish the same thing, without locking and unlocking the bootloader. I think the December OTA ought to also update the bootloader. I haven't tried this yet though. Just don't have time to mess with updates right now.

I did find with the November update that the OTA worked fine, even though the factory image would not flash the bootloader.
[Google Pixel 2 Questions & Answers] kendong2:
Can confirm sideloading the OTA according to Googles instructions on the download page also updates the bootloader.
[Google Pixel 2 Questions & Answers] ecs1984:
I managed to update to 8.1.0 through a bit of a Frankenstein method.... but not without a ton of stress. I tried side-loading the OTA, which updated the bootloader, but then something failed later about 95% of the way in.

Apparently, the phone switched itself to the B system partition, and I was able to the 8.1.0 factory image without a problem. 8.1.0 boots and everything works fine, but I am getting a warning message to contact the manufacturer when booting up.

I think there is an issue with the bootloader slot in my A system partition, because I had some other random errors when unlocking etc. Hopefully Google will send me a new replacement phone because this one has been a headache.
[Google Pixel 2 Questions & Answers] peikojose:
I posted the solution here...

https://www.reddit.com/r/GooglePixel/comments/7ht2tr/failed_remote_failed_to_loadauthenticate_boot/
[Google Pixel 2 Questions & Answers] kinfam:
I had this issue when trying to flash 8.1 Factory Image over 8.0.

I fixed it by flashing back stock boot.img and then ADB sideloading 8.1 OTA update.

Bootloader/8.1 updated successfully.
[Google Pixel 2 Questions & Answers] cb474:
The problem in your thread at reddit seems to have to do with flashing the boot.img, which is not the same issue here. This thread is about problems flashing the bootloader. The boot.img and the bootloader image are not the same thing.
[Google Pixel 2 Questions & Answers] cb474:
Okay, so I did my own experiment and I was right. I sideloaded the December OTA image. That updated the bootloader, as others have reported. After that whatever the problem was with flashing the bootloader from a factory image went away. I extracted the bootloader image from the December factory image zip, rebooted into the bootloader, and flashed the bootloader .img file using fastboot without a problem. So I assume going forward it should be possible to flash factory images, rather than sideoading OTA images, without issues regarding the bootloader.
[Google Pixel 2 Questions & Answers] thedesp:
Seems like sideloading the December OTA is the only solution here.
[Google Pixel 2 Questions & Answers] razrlover:
** So this is how I fixed my issue.

I used Deuces v4 script to flash all 8.1, after it was done was stuck in bootloader and wouldnt reboot out.

So then I used Google's flash-all.bat, then at the end I got a error missing boot.img, check folder and it was there.

So I re-used Deuces v4 script and flashed it again.

This time after it was done I was in 8.1 and all good.

Hope this helps!
[Google Pixel 2 Questions & Answers] dewhashish:
I started that reddit thread. I'd try to sideload the OTA but I can't even get into recovery. It just goes right back to the bootloader.

---------- Post added at 09:52 AM ---------- Previous post was at 08:56 AM ----------

This worked! Thanks! I was able to get it to erase through recovery and it booted!
[Google Pixel 2 Questions & Answers] cb474:
You really made that hard on yourself.

If you had read the whole thread you would have seen that simply sideloading the December OTA image, with adb, updates the bootloader and solves the problem. After that you can flash the bootloader with fastboot successfully (though it's unnecessary for now, since it has already been updated--but in the future should hopefully mean there will be no more problems flashing bootloaders).
[Google Pixel 2 Questions & Answers] zz358840:
I have the same problem.

But I solved it.

This is a bug,it already fixed in 2017/12 OTA File.

use adb sideload otafile.zip

or

check system update

Bug will fix after update.

Bootloader version is mw8998-002.0066.00 .

good luck.
[Google Pixel 2 Questions & Answers] depii:
Hm okay. Sideload didn't work for me. How can i sideload the ZIP to a stock system without TWRP?

In bootloader:

# adb sideload test.zip

adb: sideload connection failed: no devices/emulators found

adb: trying pre-KitKat sideload method...

adb: pre-KitKat sideload connection failed: no devices/emulators found

In "download mode" the phone display says: "ERROR: Operation Denied"

In "recovery mode" the phone display says: "No command"
[Google Pixel 2 Questions & Answers] Ra6idr0y:
The steps are right on Googles OTA images page. Need to hold power button and press volume up when in recovery. Then a list of options will appear, one being Apply update from ADB.
[Google Pixel 2 Questions & Answers] depii:
EDIT: aaah i found my error :D I had overlooked that I have to press Power and Vol-Up, when i see the red exclamation mark (with "No command"). Thanks!

1) adb reboot recovery

2) The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.

3) Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
[Google Pixel 2 Questions & Answers] cb474:
Yeah, the stock recovery is a little confusing. You get to the image of the Android lying on its back with the red exclamation mark and no menus and you think: OMG what happened?! :( Did I brick my device?

I don't know why it doesn't just boot to the menu, rather than hiding it behind a secret set of key presses. I guess that's to keep people who don't know what they are doing from messing things up? But then, wouldn't such people never boot to the recovery anyway? You already have to have gone out of your way to figure that out, so hiding the menu at that point seems a bit silly.
[Google Pixel 2 Questions & Answers] MattSkeet:
could I ask how did you sideload it without the bootloader?
[Google Pixel 2 Questions & Answers] cb474:
I just followed the instructions on Googles developer site for sideloading OTA images, using adb.

I'm not sure what you mean by "without the bootloader." I had a bootloader, the original one. It worked fine. Just for some reason I (and others) could not flash only the bootloader using fastboot. But sideloading the entire OTA image with adb updates the bootloader also. After that, as I explained, the problem is solved and it's possible to flash a bootloader alone with fastboot (although there is no newer bootloader yet that one would need to flash--I just tried it anyway with the latest bootloader to see if it would work).
[Google Pixel 2 Questions & Answers] con4n007:
saved my day, just need to flash the same bootloader on slot a and b and it works!
[Google Pixel 2 Questions & Answers] Colday96:
Thanks a lot!! I though I was done for.....
[Google Pixel 2 Questions & Answers] deepdvd:
I had the same issue. I was pretty concerned until I switched to "a" by doing:

fastboot --set-active=a

Even after switching slots, flashing the bootloader (fastboot flash bootloader bootloader-walleye-mw8998-002.0067.00.img), restarting the bootloader (fastboot reboot-bootloader) and doing a flash-all, my slot b is still messed up. I can boot from bootloader a, but not b. If I try to boot from slot b, I get the message at the bottom of the bootloader screen:

Error LoadImageAndAuth failed: load error

Hopefully this doesn't cause an issue in the future. If so, I might have to have Google replace it.
[Google Pixel 2 Questions & Answers] trhacker01:
I just started a thread about this before seeing your post. I've had to replace a few p2's stuck in bootloader with that error, except I haven't been able to boot from slot a, looking for answers myself. All I really know is call google support and they will replace your phone.
[Google Pixel 2 Questions & Answers] JasonVaritekMVP:
So I'm currently running November 8.0 and I am having this same issue. Bootloader says its 059.

I rooted via a modified boot image and magisk (no twrp). Can I use the Dec OTA as you have mentioned with the boot images as they currently exist or do I need to flash back to the original boot images?

I'm attempting to update to the May update and while failing I at least still have an operational phone and I want to try and avoid making this worse before better if I can. Thank you so much for any help.

Best,

- JasonVaritekMVP
[Google Pixel 2 Questions & Answers] cb474:
It's been so long since I dealt with this, I can't really remember all the details. I would think the safe thing to do would be to flash back to the original boot image, with the option that Magisk has for this. In fact, you should check the Magisk instructions, but I think they say that before flashing an update you always have to first restore the original boot image. That's what I do before every update.

Also, I don't really know the answer to this, but once you restore the original boot image, I wonder if you can simply update with the May OTA and do not need the addition step of flashing the December OTA first. It could save you a step, but I make no promises about what might happen, because I just don't know if that is kosher or not.
[Google Pixel 2 Questions & Answers] kkjb:
Just in case you find that nothing works. I would hold off on having Google replace phone, if you can't live without it for now. I have found that Google Store refurbished replacements will not OEM unlock, even if a unlock-able phone. Seems that in the google store refurb replacement channel this is screwed up. I have had so far four replacements and ALL have the same failure. I have been told that Engineering support knows of this trouble but so far I am still wanting for mine to be unlock-able. Since Mid March!!

My original failure was as above post of restoring Magisk original before patching but some how I did it wrong and phone was stuck in bootloop after I tried to switch A to B thinking I could go back.....
[Google Pixel 2 Questions & Answers] JasonVaritekMVP:
Firstly thanks for the response.

To update I ended up flashing the December OTA and then flashing the May factory image without wiping. I'm happy to report that everything went off without a hitch and after re-flashing Magisk I am once again rooted.

Cheers!
[Google Pixel 2 Questions & Answers] rosenbaa29:
Totally solved this issue by running,

fastboot oem lock

(then select lock)

fastboot reboot-bootloader

fastboot oem unlock

(then select unlock)

(then run

fastboot flash bootloader *filename

)
[Google Pixel 2 Questions & Answers] Theracerlucky:
Now i am suffering from this comand flash errors what can I do on this time but the latest ota is now Android 11 plz sum one help me plz
[Google Pixel 2 Questions & Answers] Theracerlucky:
Dear members plz suggest me a best solution for this problem plz

I have a pixel 2 (walleye) and few days ago i am unlocked my bootloader and i used sum custom os like linage os on my device this yesterday I have changed my mind and i flashed a stock factory images

But i do a mistake is i am flashed a Android 8.0 factory images that is walleyes first release frimware or factory images after i am flashed my device flashing process is susessful and it is booted normally and work fine but when I am now trying to flash latest version factory images that's besed on Android 11 it is showing me sum errors on flashing time what i do now
[Google Pixel 2 Questions & Answers] Theracerlucky:
Now my system update showing available and my bootloader is unlocked can i download and install that or sideload the latest Android 11 ota plz help all members plz
[Google Pixel 2 Questions & Answers] V0latyle:
Next time, please resize or spoiler large photos.

There are 4 ways you can update:

Delta OTA (Android System Update)

Sideload OTA

Manually dirty flash factory image

Use Android Flash tool to dirty flash factory image

The easiest way by far is to use Android System Update and let the phone handle everything.
[Tilt, TyTN II, MDA Vario III General] m3power:
i just installed htc home and somehow i'm not getting the black start menu you guys are getting and im still stuck with the default att blue start menu. What do i have to do guys to get this? Do i have to install those modified HTC ROMS over the att one?

Im new btw i just got a tilt this past weekend and you guys will probably see more often here since i want to learn to take advantage of this phone to full potential. I'm new to the PDA scene i just upgraded this phone from my SE w600i and 810i.
[Tilt, TyTN II, MDA Vario III General] swiftgs:
Re

I don't know excactly, but have you looked in the settings, today, and deactivate the AT&T and activate the HTC home. (I have no AT&T so maybe it's not even in there. but you can take a look...
[Tilt, TyTN II, MDA Vario III General] DarkDvr:
Use this theme (file attached)

Unzip it in your My Documents folder (on the Phone, NOT ON Storage Card), then go to Start - Settings - Today and choose "WM_Black2" theme. Tap OK couple of times and you should have standard HTC black theme everywhere.
[Google Pixel 2 XL Guides, News, & Discussion] zachman1750:
UPDATE 2: if you are on the November update already I recommend following this guide that's a lot better than my own and does not rely on TWRP. To get snokes kernel going to use with that guide (you must be on the November update and non-verizon), download this kernel that was posted in this thread by [MENTION=634006]123SIT[/MENTION].

After gaining root, come back here for the Viper portion.

Hey all. This took me a bit to get up and running on my own phone, but with some help from the XDA community I've now got Magisk/Root, Snoke Kernel, and Viper4Android all working. Since I know other members have to be struggling with the same things, I've decided to post a semi-noob friendly guide.

This worked for my device, I make no guarantees for your own. This guide assumes you have an unlocked bootloader already and therefore are not using a Verizon device. I have not tested this on 8.1, so I can say that this, for now, is only applicable to 8.0. Before starting, please ensure that you have the latest version of adb/fastboot. This is extremely important.

Install the MagiskManager-v5.4.1.apk to your device

Open Magisk Manager on your phone and click install (Not 100% sure if this step is necessary)

Download TWRP alpha here.

Download the Magisk version that [MENTION=2955144]bryantjopplin[/MENTION] posted in this thread.

Download the Taimen version of the Snoke.R10.zip kernel found in this thread.

Rename twrp file to twrp.img and open a command prompt/adb window where all of the downloaded files are located.

Rename the Magisk-v14.4.1.zip file to magisk.zip for simplicity

Type the following command in the adb window to reboot to bootloader: adb reboot-bootloader

After it reboots, type the following command to boot into TWRP. Swipe to allow system mods: fastboot boot twrp.img

When TWRP loads, go to Advanced and choose ADB Sideload, swipe to confirm, then type the following command:adb sideload Snoke.R10.zip

After that completes, you'll have to select ADB Sideload again, then type the following command: adb sideload magisk.zip

Reboot. When you go to Magisk Manager, you should see that you now have root.

Go to normal android settings -> Apps & notifications -> See all apps -> Three dot menu button -> show system -> find MusicFx in the list and click it -> Click force stop -> Click disable -> Go to storage -> Clear Data.

Reboot

Download version 2.2 (latest) of viper4Android from this thread. Other members have reported that this module version can now be found in the magisk manager downloads section!

In magisk manager, click menu and go to modules. Click the add button, and select the viper4Android zip you downloaded in the previous step.

After installation completes, reboot.

Open the newly installed Viper4Android app on your phone

Enable master power where you'd like it.

Play some music. Viper4Android should now be working. It could require an additional reboot, song change, or master power toggle in viper to get things processing.

Thanks to [MENTION=2955144]bryantjopplin[/MENTION] and [MENTION=3529245]g3v0[/MENTION] for the assistance.
[Google Pixel 2 XL Guides, News, & Discussion] Taebom:
Thanks for the write up. Instead of snokes kernel I used stock and just installed selinux mode changer and set permissive and every step you wrote worked for me. Just thought I would let you know for people who wanted to keep stock.
[Google Pixel 2 XL Guides, News, & Discussion] shizat63:
Good post.

Are Snoke and Viper4Android to fix the audio clicks on some models?

I got root without TWRP. Should I install or or just wait for a more polished version?
[Google Pixel 2 XL Guides, News, & Discussion] idkwhothatis123:
But this is not valid for anyone who took the Nov update because TWRP is incompatible, correct?
[Google Pixel 2 XL Guides, News, & Discussion] zachman1750:
I believe that is correct, yes.
[Google Pixel 2 XL Guides, News, & Discussion] zachman1750:
Viper will make any audio coming out of your phone sound amazing if tuned properly. For TWRP, yes, I'd definitely wait until a full beta or stable release to do a real flash.
[Google Pixel 2 XL Guides, News, & Discussion] g3v0:
Root/Magisk, Viper and Snoke's kernel still work fine. Refer to my previous post:

If your phone's build number in Settings -> About Phone is "OPD1.170816.025" (ends in .025), you can use the attached boot.img file, which includes Snoke's R10, and skip the first 3 lines. You will still need to patch it in Magisk and reflash it though.

Was too big too attach, get here: https://drive.google.com/open?id=1_2vXBn5zGCGVq_b5PIKQszpqQa1xHS1f
[Google Pixel 2 XL Guides, News, & Discussion] soundneedle:
I love you zachman175.
[Google Pixel 2 XL Guides, News, & Discussion] KHANrad_SIN:
I've tried the steps in the OP and Viper will work for a little bit, but then after a couple minutes it stops working or when I switch the master power on and off a few times then it stops working, it's odd.
[Google Pixel 2 XL Guides, News, & Discussion] Redrockzz:
Afaik that is a typically issue with viper and magisk. A few months ago when I used viper with super su there wasnt any issues. But I am not 100% sure, just a hint.
[Google Pixel 2 XL Guides, News, & Discussion] Taebom:
for me it works for speaker output but not processing for bluetooth. Anyone else?
[Google Pixel 2 XL Guides, News, & Discussion] zachman1750:
I was having the same issue and got it working by installing the Magisk Module called 'Universal deep_buffer Remover' by ahrion, zackptg5 that can be found within the downloads section of magisk manager. After installation, I disabled master power on bluetooth in Viper, rebooted, and then turned master power back on. I then opened spotify and it started processing. I'll update the main thread with this information.
[Google Pixel 2 XL Guides, News, & Discussion] KHANrad_SIN:
hmm I'm having the same issue as well and I tried the deep buffer module but bluetooth master power is still not working for me, gonna try to uninstall and redo it all
[Google Pixel 2 XL Guides, News, & Discussion] zachman1750:
Maybe before reinstalling all of it you could try clearing your Viper app data and then reboot. I took that step as well. I've had success streaming Spotify over bluetooth with these steps, but it definitely seems a bit finicky.
[Google Pixel 2 XL Guides, News, & Discussion] KHANrad_SIN:
I actually ended up doing both reinstalling everything and clearing vipers data then rebooting but its still not working. Maybe it could be that i'm using google play music to play local music instead of streaming on spotify. Under driver status, does yours say "Processing: Yes"? Mine says "Processing: No". Or it could be the bluetooth headphones I'm using, I'm using one of those truly wireless earbuds with no wire in between.
[Google Pixel 2 XL Guides, News, & Discussion] zachman1750:
Mine says processing: no as well, but that could be because I'm not presently streaming audio. Are you sure you're using the permissive version of the kernel? The non-se version that is.
[Google Pixel 2 XL Guides, News, & Discussion] KHANrad_SIN:
Mine says processing: no when i start playing music with bluetooth headphones. I used the patched boot image with R10 incorporated that you provided in post #7.
[Google Pixel 2 XL Guides, News, & Discussion] zachman1750:
Keep in mind that was another member who posted that and I am speaking from a pre-november update perspective.
[Google Pixel 2 XL Guides, News, & Discussion] KHANrad_SIN:
ohhhhhhh you're on the september update? I guess that may be it, I'm on the november update