Fixed
Status Update
Comments
rh...@rhonk.com <rh...@rhonk.com> #2
I'm experiencing this issue as well on my Pixel XL and Pixel 2 XL.
sc...@gmail.com <sc...@gmail.com> #3
I got the same error attempting to ADB sideload to my Pixel 2 XL.
qu...@gmail.com <qu...@gmail.com> #4
I have the same issue on my Pixel XL coming from OPR3.170623.008
lu...@gmail.com <lu...@gmail.com> #5
Same here, Pixel XL running OPR3.170623.008/4294783
do...@gmail.com <do...@gmail.com> #6
Same issue on my Pixel 2 with the OTA sideload. Also having a problem reflashing totally. Getting a weird error when unlocking the bootloader
./fastboot flashing unlock
...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (Undefined error: 0))
finished. total time: 10.590s
After that the bootloader says it is unlocked but I am unable to flash the 8.1 bootloader image ->
./fastboot flash bootloader bootloader-walleye-mw8998-002.0062.00.img
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38648 KB)...
OKAY [ 0.826s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.830s
./fastboot flashing unlock
...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (Undefined error: 0))
finished. total time: 10.590s
After that the bootloader says it is unlocked but I am unable to flash the 8.1 bootloader image ->
./fastboot flash bootloader bootloader-walleye-mw8998-002.0062.00.img
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38648 KB)...
OKAY [ 0.826s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.830s
my...@gmail.com <my...@gmail.com> #7
Getting the same error on my Google Fi 2016 Pixel. 8.0.0/OPR1.170623.027/4292972
bh...@gmail.com <bh...@gmail.com> #8
I also got the same issue on my Pixel XL
br...@gmail.com <br...@gmail.com> #9
I also have the parse error result -22, when I try to sideload the OTA zip for my Pixel (Sailfish).
ne...@gmail.com <ne...@gmail.com> #10
I too have the same issue. Also enrolled in over the air betas and I'm not seeing an update when I press the check for update button multiple times here at 6:25pm -6 Central Time.
Reported Issue
I have a 2016 Pixel (Model G-2PW4100) currently on Android 8.0.0 build number OPR3.170623.008 and I'm trying to sideload the OTA for 8.1 preview from here:https://developer.android.com/preview/download-ota.html
I downloaded this zip -> sailfish-ota-opp5.170921.005-bde99141.zip
I have done OTA sideloads many times before with no issue. When I try to sideload this OTA I get the following output:
Update package verification took 276.0 s (result 0).
E:Failed to verify package compatibility (result -22): parse error
Installation aborted.
Reported Issue
I have a 2016 Pixel (Model G-2PW4100) currently on Android 8.0.0 build number OPR3.170623.008 and I'm trying to sideload the OTA for 8.1 preview from here:
I downloaded this zip -> sailfish-ota-opp5.170921.005-bde99141.zip
I have done OTA sideloads many times before with no issue. When I try to sideload this OTA I get the following output:
Update package verification took 276.0 s (result 0).
E:Failed to verify package compatibility (result -22): parse error
Installation aborted.
cy...@gmail.com <cy...@gmail.com> #11
Same here on 2016 Pixel XL Aussie Telstra version
Shows -22 error
Shows -22 error
ma...@gmail.com <ma...@gmail.com> #12
Yep, also on my Pixel XL, tried re-downloading the package but no difference.
de...@gmail.com <de...@gmail.com> #13
happened to me too
dd...@gmail.com <dd...@gmail.com> #14
likewise. Pixel.
st...@gmail.com <st...@gmail.com> #15
Likewise XL2
am...@gmail.com <am...@gmail.com> #16
getting the same issue
E:Failed to verify package compatibility (result -22): parse error
for original Pixel XL
when sideloading the marlin-ota-opp5.170921.005-d5c84fb7.zip update
E:Failed to verify package compatibility (result -22): parse error
for original Pixel XL
when sideloading the marlin-ota-opp5.170921.005-d5c84fb7.zip update
to...@gmail.com <to...@gmail.com> #17
Same here. Pixel XL
ra...@gmail.com <ra...@gmail.com> #18
Same situation Pixel XL. Anyaone with a fix for this?
ja...@gmail.com <ja...@gmail.com> #19
Same Pixel XL
dr...@gmail.com <dr...@gmail.com> #20
Same Pixel 2016 verizon
ba...@gmail.com <ba...@gmail.com> #21
Same issue.
Pixel, OPR3.170623.008.
I did not have this issue on the Pixel C, which did not have the latest security patch. Is this the issue? 8.1 OTA doesn't match the October 2017 patch?
Pixel, OPR3.170623.008.
I did not have this issue on the Pixel C, which did not have the latest security patch. Is this the issue? 8.1 OTA doesn't match the October 2017 patch?
ar...@google.com <ar...@google.com>
ar...@gmail.com <ar...@gmail.com> #22
Samesies. Pixel XL
ar...@google.com <ar...@google.com> #23
Thank you for reporting this issue. We have shared this with our engineering team and will update this issue with more information as it becomes available.
k1...@gmail.com <k1...@gmail.com> #24
Experiencing the same issue. Pixel.
sl...@gmail.com <sl...@gmail.com> #25
ugg, all of these me too's is not helpful.
If you just want to indicate a me too, click the start at the top beside the bug title.
That way everyone doesn't get an email.
If you just want to indicate a me too, click the start at the top beside the bug title.
That way everyone doesn't get an email.
t....@gmail.com <t....@gmail.com> #26
The OTA website (https://developer.android.com/preview/download-ota.html ) is no longer accessible. I'm assuming they've found the bug and will upload new files once fixed.
tr...@gmail.com <tr...@gmail.com> #27
Looks like it's back up now and the file names are slightly different. I'm downloading now and will attempt to flash again.
la...@gmail.com <la...@gmail.com> #28
that's the full factory image, not the OTA. The OTA seems to have been removed from the site.
tr...@gmail.com <tr...@gmail.com> #29
Okay, never mind. I didn't realize that the OTA page was redirecting to the factory image page.
na...@google.com <na...@google.com> #30
Thank you for reporting the issue with the OTA package. As a workaround, please download and flash a factory image instead. Alternatively, you can enroll your eligible device in the Android Beta program and receive the update over-the-air (www.android.com/beta ).
ac...@gmail.com <ac...@gmail.com> #31
That is not a solution. The whole point of the OTA is that it doesn't require a device wipe or bootloader unlock. Also, it does not appear that the OTA as actually being pushed to these devices (yet?) even when enrolled in the beta program. Has the rollout begun yet or is this error blocking our devices from receiving the OTA... OTA?
ne...@gmail.com <ne...@gmail.com> #32
Over the air at android.com/beta is still showing my pixel 1 with October security patch as up to date after enrolling in the beta and pressing check for update several times. Do not want to flash the factory image as that would require me to unlock the bootloader and cause a factory reset, in addition to leaving me without Android pay or safety net.
ba...@gmail.com <ba...@gmail.com> #33
My Pixel has been enrolled in beta since the 8.0 preview and I don't have the OTA. I'm guessing its the same issue as with the manual method.
kr...@gmail.com <kr...@gmail.com> #34
"Alternatively, you can enroll your eligible device in the Android Beta program and receive the update over-the-air (www.android.com/beta) ."
No, this is not an alternative because enrolling devices into the Beta program still doesn't pull in any updates.
No, this is not an alternative because enrolling devices into the Beta program still doesn't pull in any updates.
mc...@gmail.com <mc...@gmail.com> #35
Same error here. OG Pixel XL.
th...@gmail.com <th...@gmail.com> #36
OTA is rolling out through the beta program on my XL now.
tr...@gmail.com <tr...@gmail.com> #37
Same here. I just checked and the update appeared.
na...@google.com <na...@google.com> #38
Android 8.1 OTA's are live now. If you have enrolled for the Android Beta program, please expect them shortly. At this point in time, we do not have OTA images that can be side loaded.
ac...@gmail.com <ac...@gmail.com> #39
Update appeared. Installation "completed" device rebooted. Still on 8.0.0. Seems to be failing in the same way after receiving the OTA.
na...@gmail.com <na...@gmail.com> #40
Same here, after reboot it says failed to install system update.
tr...@gmail.com <tr...@gmail.com> #41
Mine installed without issue and is on 8.1.0 now.
sc...@gmail.com <sc...@gmail.com> #42
Same here. Update via OTA, after installation and reboot a new boot sequence appeared twice and then the old boot sequence appeared to boot to 8.0.0! Now on the second try.
to...@gmail.com <to...@gmail.com> #43
Mine installed without issue as well. Now running 8.1.
Pixel XL 128 T-Mobile, purchased from Google store.
Pixel XL 128 T-Mobile, purchased from Google store.
na...@gmail.com <na...@gmail.com> #44
"Mine installed without issue as well. Now running 8.1.
Pixel XL 128 T-Mobile, purchased from Google store."
Were you already on the October security patch?
Pixel XL 128 T-Mobile, purchased from Google store."
Were you already on the October security patch?
to...@gmail.com <to...@gmail.com> #45
Yes. I was already running 8.0 October update. I had received that a few weeks ago.
ac...@gmail.com <ac...@gmail.com> #46
Second attempt to install the OTA failed as well.
sc...@gmail.com <sc...@gmail.com> #47
Same here. Second try failed too. Pixel with October patch.
na...@gmail.com <na...@gmail.com> #48
Mine failed as well. Pixel October patch. Two tries.
ma...@gmail.com <ma...@gmail.com> #49
Same with Pixel 128Gb Play Store with October patch - 2 tries
kr...@gmail.com <kr...@gmail.com> #50
Beta Program OTA failed.
to...@gmail.com <to...@gmail.com> #51
Very strange that I was having the failure with "adb sideload", like everyone else in this thread, but had zero issues with the OTA via the beta program OTA download.
Anyway, 8.1 beta, so far, feels snappier than 8.0. Memory management may be slightly improved. Hard to say with any confidence at this point. The Pixel 2 launcher appears to be a little smoother, but still not as smooth as Nova launcher. The navigation button bar changes are subtle and tasteful, and should help mitigate differential aging (burn in) on OLED panels. So far I'm happy with the beta.
Anyway, 8.1 beta, so far, feels snappier than 8.0. Memory management may be slightly improved. Hard to say with any confidence at this point. The Pixel 2 launcher appears to be a little smoother, but still not as smooth as Nova launcher. The navigation button bar changes are subtle and tasteful, and should help mitigate differential aging (burn in) on OLED panels. So far I'm happy with the beta.
de...@gmail.com <de...@gmail.com> #52
OTA already available, check your phone
ac...@gmail.com <ac...@gmail.com> #53
If you'd bothered to read this thread, you'd see that the OTA fails in the exact same way for the majority of people experiencing this error.
Also, other person, anecdotal experiences with running a build don't belong in unrelated issue tracker threads.
Also, other person, anecdotal experiences with running a build don't belong in unrelated issue tracker threads.
ne...@gmail.com <ne...@gmail.com> #54
So 8.1 (OPP5.170921.005) OTA shows as available but when I download (currently on 8.0.0 OPR3.170623.008) it installs and reboots and the boot animations play a couple of times on my 2016 pixel (non XL) then says 'installation problem' and I am still on 8.0.0 OPR3. I do not wish to unlock my bootloader. The OTA images have been pulled. I don't want to loose android pay or safety net by unlocking the bootloader
could google pretty please fix it again when they come into the office tomorrow?
could google pretty please fix it again when they come into the office tomorrow?
t....@gmail.com <t....@gmail.com> #55
OTA install failed for me as well on Pixel 2016 128GB. Trying again to install but I'm sure it'll fail again based on the reports in this thread. This is not good QA, Google engineers - this should be embarrassing for you guys.
cf...@gmail.com <cf...@gmail.com> #56
I can't flash the full system image, even. It gets as far as flashing boot.img and tells me that bootb doesn't exist. Did anyone check their code?
cf...@gmail.com <cf...@gmail.com> #57
That, or my version of ADB isn't new enough.
cf...@gmail.com <cf...@gmail.com> #58
Turns out it's my ADB version after all. Whoops. I retract my statement.
ch...@gmail.com <ch...@gmail.com> #59
I tried multiple times on my Pixel (2016) to install the beta. It downloads and installs, yet after the reboot, it seemed to fail.
t....@gmail.com <t....@gmail.com> #60
Same here. Tried multiple times as well - no go.
na...@gmail.com <na...@gmail.com> #61
Even after a factory reset, still not installing.
ss...@gmail.com <ss...@gmail.com> #62
My Pixel (2016) 128GB also not updating via the OTA beta program. Reboots with an installation error. I've tried 4 times now, twice yesterday and twice today.
ne...@gmail.com <ne...@gmail.com> #63
Tried again, and it fails. Was hoping something could be done today, guess I'll try again monday
ac...@gmail.com <ac...@gmail.com> #64
I FOUND A WORKAROUND!
This requires you to have the OTA zip downloaded.
Step 1: Enroll in the Beta program and install the OTA that is pushed to your device.
Step 2: The device will reboot, Immediately after the Google Logo Shows the screen will go black and reboot again. IMMEDIATELY Hold Volume Down + Power to boot into the bootloader
Step 3: Enter recovery mode. You should see that recovery mode is now version 8.1.0. If this is NOT the version displayed, start over.
Step 4: Entire sideload mode and sideload the 8.1.0 OTA Zip.
Step 5: Allow everything to complete as normal. (No error! but the progress of the update process will be a little different than normal, just ignore it and let it do its thing).
Step 6: Your device will reboot several times, and then boot into the OS. Congratulations, you now have v8.1.0.
This requires you to have the OTA zip downloaded.
Step 1: Enroll in the Beta program and install the OTA that is pushed to your device.
Step 2: The device will reboot, Immediately after the Google Logo Shows the screen will go black and reboot again. IMMEDIATELY Hold Volume Down + Power to boot into the bootloader
Step 3: Enter recovery mode. You should see that recovery mode is now version 8.1.0. If this is NOT the version displayed, start over.
Step 4: Entire sideload mode and sideload the 8.1.0 OTA Zip.
Step 5: Allow everything to complete as normal. (No error! but the progress of the update process will be a little different than normal, just ignore it and let it do its thing).
Step 6: Your device will reboot several times, and then boot into the OS. Congratulations, you now have v8.1.0.
ne...@gmail.com <ne...@gmail.com> #65
AC... if you are still following this can you link me to the URL. Not sure where to get the OTA zip now they have removed it from the developer page. Thanks in advance for your help
ac...@gmail.com <ac...@gmail.com> #68
Removed access to my link. Please use SR's official link instead.
ne...@gmail.com <ne...@gmail.com> #69
AC thank you so very much. It worked. I was a bit worried I would brick the thing but It went smoothly. To anyone else waiting if you have experience with ADB its painless and works 100% Thanks to user SR as well for providing the OTA link.
la...@gmail.com <la...@gmail.com> #70
Cheers AC. Hopefully this does not cause issues for Google with the next update in accounting for these phones that were updated in this way, but it would have never been a thing in the first place if the update wasn't botched so I don't feel too bad. Got updated and Finally got rid of that annoying notification telling me I had an update or that the update failed 24/7
ri...@gmail.com <ri...@gmail.com> #71
AC, can confirm your workaround from #64. THANK YOU!!!
Pixel fix confirmed. Was on OPR3.170623.008 locked and stock. Followed instructions per AC in post #64.
I would like to add however that to make it easier as far as the button pushing thing goes... (the recovery key press vol+ pwr)
If you have developer options enabled:
When you see the "reboot to install" button appear from the ota, instead of pressing the button you can actually just issue "adb reboot recovery" and it'll bring you right to recovery with 8.1.
As far as I can tell it sorta "pre-loads" the ota when the button appears your good to go.
Pixel fix confirmed. Was on OPR3.170623.008 locked and stock. Followed instructions per AC in post #64.
I would like to add however that to make it easier as far as the button pushing thing goes... (the recovery key press vol+ pwr)
If you have developer options enabled:
When you see the "reboot to install" button appear from the ota, instead of pressing the button you can actually just issue "adb reboot recovery" and it'll bring you right to recovery with 8.1.
As far as I can tell it sorta "pre-loads" the ota when the button appears your good to go.
ch...@gmail.com <ch...@gmail.com> #72
New release is killing my 6p. Goes from
80 pct batt to zero. Then reboot and power shows 60 pct. Very strange behavior.
80 pct batt to zero. Then reboot and power shows 60 pct. Very strange behavior.
Description
I downloaded this zip -> sailfish-ota-opp5.170921.005-bde99141.zip
I have done OTA sideloads many times before with no issue. When I try to sideload this OTA I get the following output:
Update package verification took 276.0 s (result 0).
E:Failed to verify package compatibility (result -22): parse error
Installation aborted.