yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 Guides, News, & Discussion] cb474:
Thanks for all your help and suggestions. It looks like there are a couple different ways to flash .025, so I guess I'll just do that. I really paid a price in thinking I bricked my device and in time by being so impatient. :p

It is weird that I couldn't downgrade. Maybe I just didn't wait long enough for the fist startup after I flashed it? It was stuck on the G logo for maybe ten minutes when I gave up. Since the device starts so fast otherwise, even after flashing .018 (both as OTA and as factory image), I just assumed something was wrong.

I am concerned about that "FAILED (remote: Command Flash Error)" I got when the factory image update tried to flash the bootloader. I only found two other mentions of that anywhere online, without much explanation. Maybe it really was unable to flash the bootloader, but it wasn't an update over the original bootloader, so it didn't matter for .018. But if my device can't flash a bootloader that's obviously a problem. I guess I should just try flashing the bootloader alone. Perhaps I'll start a separate thread about it.

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

I don't know for sure. But I imagine you flash the OPD1, because that's the device you have. What difference does it make what carrrier you are on? The phone from the Google store will work on any carrier, so the carrier shouldn't determine the updates. That's what I'd do. Flashing the OPD3 Verizon version I'd think would potentially mess up your device (or even fail since your IMEI number would correlate to the update you're trying to flash).

If you're feeling really uncertain, then just wait for the update to get pushed directly to your device (through the update method in the settings). All devices are supposed to get it sometime within a week of release. That way you can't screw up. And you can look at the build number after that update and you'll know what it did for the future.
[Google Pixel 2 Guides, News, & Discussion] xene97:
Just standard impatience!
[Google Pixel 2 Guides, News, & Discussion] cb474:
I'm with you. If you read back in this thread you can see the giant heaps of trouble I got myself into last night, being impatient. :)
[Google Pixel 2 Guides, News, & Discussion] kinfam:
Unlocked variant on TMO, locked bootloader.

Flashed .018 OTA then .025 OTA via ADB.

No issues so far. Clicking gone as well.

VOLTE and WiFi Calling seem to be working fine.
[Google Pixel 2 Guides, News, & Discussion] cb474:
Do you just adb sideload this, the same way you would with the whole OTA image on the Google developer site?
[Google Pixel 2 Guides, News, & Discussion] petrus764:
Yes. OTA's delivered via system updates are incremental, thus you need the previous update (which in this case isn't a problem, since the pixel 2 only has one update), while google's OTA images available for download on https://developers.google.com/android/ota are full system images and can be flashed even if you don't have the previous update installed.

The method for installing them are identical, adb sideload ota.zip

I agree, now that there are flashable zips for .025 I'd just go with that too.
[Google Pixel 2 Guides, News, & Discussion] gm007:
Bought my phone today and got .025 update directly via ota,is this one has the latest security patch including the krack fix?
[Google Pixel 2 Guides, News, & Discussion] MoosDiagramm:
No, the KRACK fix is yet to be released.
[Google Pixel 2 Guides, News, & Discussion] km8j:
I'm on unlocked and have not gotten the OTA yet. I keep trying to pull it but nothing. Did everyone else?
[Google Pixel 2 Guides, News, & Discussion] MaxNXS:
Got my Pixel 2 from Freedom Mobile (Wind) in Canada. Sideloaded .018 yesterday and today I sideloaded .025, but at the end of the process I got a:

However after rebooting everything was fine. .025 is the version reported, I have the new color boost under the display options and the nav bar fades to grey when not in use. All is good!
[Google Pixel 2 Guides, News, & Discussion] km8j:
So did everyone get this OTA except me?
[Google Pixel 2 Guides, News, & Discussion] daandman:
Can these be flashed if I'm on the beta program? If so, which would one do I go with? My Pixel 2 (Walleye) is unlocked, but being used on Rogers.
[Google Pixel 2 Guides, News, & Discussion] acey_zero:
No, I still haven't gotten it
[Google Pixel 2 Guides, News, & Discussion] mt2020:
Similar issue here. Bought unlocked Pixel2 from Google, did all the updates, then I did put a Verizon sim into it, now oem unlock is grayed out and still won't get OTA for Nov.

As a follow up, Google is sending me a new phone. This exact issue happened with my previous Pixel 1, but only after a put a Verizon sim in it after 9 months on a different carrier. Worked perfect until then. The Verizon simm locked OEM and stopped updating.
[Google Pixel 2 Guides, News, & Discussion] UltraM8:
Can anyone share system & vendor dump? I've tried nearly every unpacker, but they always crash for whatever reason
[Google Pixel 2 Guides, News, & Discussion] csxt8142:
Awesome, thanks! Trying to figure out how to flash this using FlashFire, as the screens in the app are different than what's depicted in this link: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

I assume the app has been updated since these directions were posted. Anybody with updated instructions?

I'm rooted non-Verizon P2 on Verizon, currently on OPD1.170816.010. From what I've seen, it appears I can go straight to .25 from .10. Just not sure how to do it and not lose root. :)
[Google Pixel 2 Guides, News, & Discussion] ajrty33:
You don't. You update and re-root.
[Google Pixel 2 Guides, News, & Discussion] sdsurferbob:
I hadn't thought about my lack of a push update yet being Verizon related. I too have a unlocked P2 from Google, using with a Verizon sim. Didn't think that factored into it? I'm on .10

---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------

What carrier/service are you using? How did you purchase?
[Google Pixel 2 Guides, News, & Discussion] gm007:
I don't live in USA, got my phone in Lebanon and i think it's an unlocked Canadian version.
[Google Pixel 2 Guides, News, & Discussion] frostbach:
From looking into this over the past couple days, it seems like the carriers still have to approve the update. However, it definitely seems like Verizon should have approved the update because it's posted on their website for Pixel 2 and I'm pretty sure I've seen people with Verizon phones that have received it.

However, the question I would definitely have is which upgrade path are we supposed to be on here?

OPD1.170816.010 -> OPD1.170816.025

OR

OPD1.170816.010 -> OPD3.170816.023 (Verizon specific build)

?

Could this be something where either Verizon hasn't approved the non-Verizon update, or Google didn't make an OTA to go from .10->.023?
[Google Pixel 2 Guides, News, & Discussion] quakeaz:
Not sure if anybody has done this, but wondering if it is possible...

If a Google store unlocked Pixel 2 was pushed OPD3.170816.023 (Verizon) OTA due to having a Verizon SIM installed, is it possible to sideload the non-carrier specific OPD1.170816.025 OTA update in recovery to change the version from OPD3.170816.023 -> OPD1.170816.025?

I'm not sure if this would work, since I assume the OTA is expecting to patch an older version from September (OPD1.170816.010). For example if I switched carriers, I no longer need/want the Verizon specific build.
[Google Pixel 2 Guides, News, & Discussion] sdsurferbob:
I gave up on waiting and just went ahead and side loaded the OTA file from the Google site, going from .10 to .25. Easy enough and now I'm updated, just frustrated I had to do it myself.
[Google Pixel 2 Guides, News, & Discussion] frostbach:
Did you actually receive an OTA from .10->.023?

I'm just about ready to stop waiting and sideload the update, but I was figuring I was just going to use .025 just in case the .023 one would cause weird issues with the unlocked phone(can no longer unlock the bootloader, for example).
[Google Pixel 2 Guides, News, & Discussion] quakeaz:
Yes, strangely I did receive it OTA on Nov 6. The .23 build shouldn't break unlockability. I have a Verizon prepaid SIM.

https://xdaforums.com/pixel-2/how-to/november-security-update-t3701239/post74557703#post74557703
[Google Pixel 2 Guides, News, & Discussion] quakeaz:
Just wanted to update in case anybody else was curious of this. It does work. Download the full OTA image (around 1.1GB) and sideload via ADB. I successfully changed from the Verizon OPD3.170816.023 build to the standard non-carrier specific OPD1.170816.025 build.
[Google Pixel 2 Guides, News, & Discussion] Kisakuku:
December 8.1 images are up.
[Google Pixel 2 Guides, News, & Discussion] mikeyinid:
For whatever reason you can't sideload the OTA over DP2. It fails saying the timestamp for 8.1 final is older than DP2.
[Google Pixel 2 Guides, News, & Discussion] Erik1805:
Still need to wait for the Verizon image . Hope that post it soon so I can update. Locked version of Verizon, with a non Verizon sim so don't get the OTA update.

Or can I first flash the 0.25 coming from the 0.23 and then receive OTA?

And if not, does anyone know when the Verizon version will be posted?
[Google Pixel 2 Guides, News, & Discussion] Indashio:
Dump?
[Google Pixel 2 Guides, News, & Discussion] mikeyinid:
Why do you need to wait for the Verizon version? I'm on Verizon and sideloaded the one posted with no issues.

As long as you're not on DP2 you shouldn't have any issues/
[Google Pixel 2 Guides, News, & Discussion] Erik1805:
Thanks so I can just flash the 8.1.0 (OPM1.171019.011, Dec 2017)
[Google Pixel 2 Guides, News, & Discussion] mikeyinid:
Yup.
[Google Pixel 2 Guides, News, & Discussion] Stretlow:
When trying to flash it ADB using "Flash-all" im getting the following error

checking product...

OKAY [ 0.001s]

checking version-bootloader...

FAILED

Device version-bootloader is 'mw8998-002.0059.00'.

Update requires 'mw8998-002.0066.00'.

Any help?
[Google Pixel 2 Guides, News, & Discussion] IDroidThere4Iam:
The non-Verizon OTA 171019.011 can be sideloaded onto Verizon 170816.023 with a locked bootloader?
[Google Pixel 2 Guides, News, & Discussion] Erik1805:
Yes i just did. Worked great.

Went from Verizon 170816.023 to 171019.011
[Google Pixel 2 Guides, News, & Discussion] fosser2:
VoLTE is enabled in Android 8.1 for AT&T. I just flashed the final factory image and it does indeed work. You do have to verify that your sim card is properly provisioned for VoLTE. As for the WiFi calling portion of this conversation, I still cannot access the "Wi-Fi calling" setting within "Mobile network settings."
[Google Pixel 2 Guides, News, & Discussion] Diesel_Jeremiah:
Following the instructions from [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye)

I removed the "-w" from flash-all

and getting the image from Factory Images for Nexus and Pixel Devices

Using the link to "https://dl.google.com/dl/android/aosp/walleye-opm1.171019.011-factory-f74dd4fd.zip"

I get this:

checking product...

OKAY [ 0.001s]

checking version-bootloader...

FAILED

Device version-bootloader is 'mw8998-002.0059.00'.

Update requires 'mw8998-002.0066.00'.

Thoughts?
[Google Pixel 2 Guides, News, & Discussion] Stretlow:
getting same, not sure what to do
[Google Pixel 2 Guides, News, & Discussion] fosser2:
Make sure your adb version is up to date? Other than that, I'm not sure
[Google Pixel 2 Guides, News, & Discussion] redsmith:
You surely ran into the error where fastboot will not flash the new bootloader, so it can't continue flashing system. There's no known solution for this. I suggest flashing the OTA instead.
[Google Pixel 2 Guides, News, & Discussion] Diesel_Jeremiah:
Will flashing the OTA wipe the phone?
[Google Pixel 2 Guides, News, & Discussion] mikeyinid:
Sideload the OTA from here

Follow the instructions on that page, very simple.

---------- Post added at 02:00 PM ---------- Previous post was at 01:59 PM ----------

No, it will not.
[Google Pixel 2 Guides, News, & Discussion] Diesel_Jeremiah:
Updated by OTA.

Root via Magisk.

You all are awesome.

Edit:

After Magisk patched the boot image, there was a pop up that it patched DTBO.img as well and wanted to reboot.

After restarting, a pop up over the screen lock:

"Android System

There's an internal problem with your device. Contact your manufacturer for details.

OK"

It is coming up after each restart.

Has anyone else seen this?
[Google Pixel 2 Guides, News, & Discussion] cb474:
I wonder if this might have to do with how you unlocked your bootloader. Google says on the page with the factory images that for the Pixel 2 XL, and only the Pixel 2 XL, you need to use the "unlock_critical" command and not just "unlock." So in theory on the regular Pixel the "unlock" fastbook command should be fine and there is no need for "unlock_critical."

But after the November update I had a problem where I could flash everything in the factory image, except the bootloader, which gave the error: "FAILED (remote: Command Flash Error)." I couldn't find others online with this error at all and no one seemed to know what it meant. I wondered if in fact one does need the "unlock_critical" command for unlocking the bootloader on the regular Pixel 2, to be able to write to the bootloader partition. But I didn't want to wipe my whole device again, by unlocking the bootloader another time. In theory, if this were the problem one should get the error: "FAILED (remote: Flashing is not allowed for Critical Partitions)." That's what the Pixel 2 XL does if one has unlocked the bootloader with "unlock" but not "unlock_critical."

It does seem curious though that some people are having trouble flashing the bootloader on the Pixel 2. Is anyone able to successfully flash the bootloader on the Pixel 2, from a factory image, when having unlocked their bootloader with the regular "unlock" fastboot command?
[Google Pixel 2 Guides, News, & Discussion] kendong2:
Completely in the same boat as you. Unlocked without critical, now the same error message, the same not-wanting-to-wipe-AGAIN. Was able to sideload the OTA file, so I am fine on 8.1, the error is annoying and confusing nevertheless.

fastboot version -4022467, which should be the latest.
[Google Pixel 2 Guides, News, & Discussion] cb474:
I just found this thread where someone found a solution to the " FAILED (remote: Command Flash Error)": https://xdaforums.com/pixel-2/help/flash-bootloader-unlocked-pixel-2-t3713740#post74748906.

In that thread, before that person found his solution, he tried "unlock_critical" on the Pixel 2 (walleye) and that did not solve the issue, so at least that rules that out.

The solution he did find, however, involved flashing back to stock, locking the bootolader, getting the Dev Preview, unlocking the bootloader, and then downgrounding. However I speculate in that thread that simply doing the December OTA image sideload, as you did, might solve the problem. I wonder if the issue was the original bootloader and now with a newever version it will be solved. There were weird issues like this early on with both the Pixel 2 and 2 XL: https://www.xda-developers.com/pixel-2-failing-flash-factory-images/

Did the December OTA sideload that you did update the bootloader? I haven't had time to try yet. If the December OTA sideload did update the bootloader, it would be interesting to see if you can now flash the bootloader image with fastboot, even though you'd just be reflashing the bootloader you already have. If you wanted to experiment to see if you still have the problem, you could try that.
[Google Pixel 2 Guides, News, & Discussion] kendong2:
Update: Oh yey. Not.

After installing Magisk via patched boot.img (which worked fine before), I got a notification saying Magisk patched my dtbo.img and I should reboot. Now I have a message after every reboot:

Doesn't seem to have any further implications though, at least so far.

---------- Post added at 11:55 PM ---------- Previous post was at 11:52 PM ----------

It did, as far as I can tell everything has been updated. Didn't even complain about the modified boot.img from the previous Magisk installation.

Edit: locking and unlocking the bootloader would wipe the device, wouldn't it? So I could just as well unlock_critical. Well anyway, I am good for now, just figured it might help you or others. Someone, somewhen will figure it out ;) Next time I might do the wipe, now that we have some decent transfer speeds with ADB push and pull it is just a few commands, thanks to Titanium Backup.
[Google Pixel 2 Guides, News, & Discussion] seanhassars:
I had this on the DP2. I believe it has to do with dm-verity. It's a known issue, but shouldn't negatively impact anything
[Google Pixel 2 Guides, News, & Discussion] cb474:
I edited my post above, maybe you didn't see that, to mention that the person in the other thread had already tried "unlock_critical," before he found his solution, and that didn't help. It's not supposed to be necessary or even do anything on the regular Pixel 2, so I think that other person's having tried it confirms that we need not bother. Also, when he did lock and unlock the device (and do all the other stuff), he only used the regular "unlock" command, which further confirms that "unlock_critical" has nothing to do with it on the regular Pixel 2. But yes, his method still required locking and unlocking the bootloader, which will wipe the device, so it didn't get around that problem.

Have you tried flashing the bootloader image since after you did the December OTA update? I'm curious, as I said, if that alone solves the problem. Hopefully I'll have time later to experiment.
[Google Pixel 2 Guides, News, & Discussion] Diesel_Jeremiah:
Previously flashed OTA "walleye-ota-opm1.171019.011", bootloader now on "mw8998-002.0066.00".

Performed flash-all from the factory image (with -w removed).

Root with patched image via Magisk.

Magisk notified patched DTBO, Reboot.

Still got:

"Android System

There's an internal problem with your device. Contact your manufacturer for details.

OK"

EDIT:

I found this here: https://xdaforums.com/showpost.php?p=74750043&postcount=164

I think the message is coming from when Magisk modifies the DTBO image.
[Google Pixel 2 Guides, News, & Discussion] nexuus:
This update does NOT fix the low audio issue when video recording as promised.. Also when recording videos now i get a low space error and the camera app hangs ..i have 20gb free.. get it together google
[Google Pixel 2 Guides, News, & Discussion] snovvman:
Ideas please:

I am on the November patch, Magisk, trying to go to 8.1, getting the same bootloader flash error. Issue: I have TWRP installed.

After downloading the OTA zip, I cannot sideload via TWRP (fails). I put the OTA zip onto internal memory and tried to flash with TWRP and it also failed. Ordinarily, I would flash the factory recovery and off to sideload I go. However, looking inside the factory image zip file, I did not find an obvious factory recovery image.

Any thoughts (other than relock/unlock BL)? Thanks.

-------------------------------------------------------------------------------

Duh!! Disregard the above. Where have I been?! Recovery is part of boot now. I flashed a factory boot and I am good to go.
[Google Pixel 2 Guides, News, & Discussion] AsuraDas:
If i am on dp2 will I get the OTA? Or do I have to manually flash something I don't really want to do
[Google Pixel 2 Guides, News, & Discussion] Ashray_Vk:
For those who has the bootloader version unable to update bug, I faced the same issue. Here is how I got mine updated

1) downgraded to the earliest version. That had .0059 bootloader in it.

2) relocked bootloader

3) Updated via OTA on phone ( not via PC )

4) now, noticed that the bootloader was in the latest version 0.66 and was also running Dev preview 2

Post this, I think you can run the commands to flash all and stuff with the new bootloader

Let me know if this helps .

Ash
[Google Pixel 2 Guides, News, & Discussion] kibmikey1:
Confirming that .011 OTA sideloads on locked Verizon versions with no problems. Now, if a Verizon specific OTA is released, I'll put that one on, but color me slightly shocked that a non-Verizon version actually flashes correctly. Oh, and no, the OEM unlocking option is NOT ungreyed.
[Google Pixel 2 Guides, News, & Discussion] gururoop:
I updated to 8.1 using full factory image (removing - w) from DP2. But I'm getting a notification that an update (DP2) is available. I'm unable to dismiss the notification. I know it would go away if I unenroll from beta program but I want to stay enrolled for future beta updates.
[Google Pixel 2 Guides, News, & Discussion] quakeaz:
https://www.verizonwireless.com/support/google-pixel-2-update/

Verizon lists .011 as their build.. maybe there won't be specific builds for this release?
[Google Pixel 2 Guides, News, & Discussion] Erik1805:
Why would you flash the Verizon after? I also flashed a non verzion version on my locked verizon phone. Can't seem to see any difference.
[Google Pixel 2 Guides, News, & Discussion] IDroidThere4Iam:
I'd echo the same as [MENTION=4948854]Erik1805[/MENTION], why flash the Verizon on top of this? I'd say leave it as-is, I don't see anything different from running it on a Verizon build. I was surprised, like you, to see that it worked.

I also think Verizon phones will never be able to be bootloader unlocked. That has less to do with what build you run and more to do with what pool of IMEI's (or some other identifier) was assigned to Verizon for their phones. During initial startup (when you turned it on fresh) - I think that's when the phone sends it's identifying info and figures out if it should allow the bootloader to be unlocked. Once that is done, only a factory reset will let the phone try that again. I may be wrong about that, but it's my guess. Unfortunately....

-Lenny

---------- Post added at 04:34 AM ---------- Previous post was at 04:16 AM ----------

That's interesting. They also removed language they had there before that said you need a Verizon activated sim to receive their update. Maybe Verizon has given that up? I wonder if a non-Verizon sim in the "Verizon" Pixel 2 would get the OTA. I wasn't getting them before so I had been sideloading.
[Google Pixel 2 Guides, News, & Discussion] thesebastian:
Unenroll from the beta. Enroll again when a new DP is released.

However I don't recommend flashing images with the -w option. In most of the versions is OK...but in some could bring issues.

I always try to use an OTA or flash with full wipe.

Now consider that you downgraded to a 2 day older version with a more recent security patch. The beta is still active. Just unenroll and when a new program or DP is out you, enroll again.

Sent from my Pixel 2
[Google Pixel 2 Guides, News, & Discussion] 760hacker:
I'm enrolled in the beta, will I get the final build via OTA or do I need to unenroll?
[Google Pixel 2 Guides, News, & Discussion] heiserhorn:
You will have it via OTA.
[Google Pixel 2 Guides, News, & Discussion] MaxNXS:
I'm unable to sideload 8.1 from .25. It get stuck on verifying package. Even the flash-all script fails...
[Google Pixel 2 Guides, News, & Discussion] Stretlow:
Same.
[Google Pixel 2 Guides, News, & Discussion] MaxNXS:
I did a factory reset, and after setting up my account, the 8.1 update was downloaded. All good for now, hopefully the sideload will work for the next update
[Google Pixel 2 Guides, News, & Discussion] gm007:
Use usb-A to usb-C cable not C to C
[Google Pixel 2 Guides, News, & Discussion] MaxNXS:
I always use A to C. This is the same cable I used last month to update to .25