PixelExperience 12.1 alioth Unable to adb Sideload.

[dc9500]

Build date

PixelExperience_alioth-12.1-20220920-0632-OFFICIAL

Expected Behavior

When following the PixelExperience upgrade guide, it says the installer can be sideloaded using adb sideload.

Current Behavior

The following error is reported on the PixelExperience Recovery command line (not verbatim):
Expected alioth but got alitoh|alothin

Possible Solution

In the installer archive, there is a com/android/metadata file. Change alioth|aliothin to alioth,aliothin in this file. This worked for me.

Steps to Reproduce

1. Download the Android 12 installer zip for alioth from the PixelExperience Download page
2. Boot the alioth device into PixelExperience recovery
3. Factory reset the device then reboot into PixelExperience recovery
4. Select Update from ADB on the PixelExperience recovery menu.
5. On the PC, execute "adb sideload (installer.zip)"

/device alioth
/version twelve

[pixelexperiencebot]

Issue created! You can close at any time by commenting /close

[lzgmc]

Which recovery are you using? This is usually caused by using an old version of PixelExperience Recovery or a different, non-supported custom recovery.

[dc9500]

I used the recovery included in the PixelExperience_alioth-11.0-20211010-0709-OFFICIAL.img build. Thanks, David

…

On Wed, 19 Oct 2022 at 16:35, lzgmc ***@***.***> wrote: Which recovery are you using? This is usually caused by using an old version of PixelExperience Recovery or a different, non-supported custom recovery. — Reply to this email directly, view it on GitHub <#3541 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFQAUGSI55MRV32ICOPMICDWD6JDPANCNFSM6AAAAAARIVAGCM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[valtf]

Do you have rom in same folder of adb?

[dc9500]

Do you have rom in same folder of adb?

No I do not, although I'm not sure how that would trigger this issue.

[dc9500]

Which recovery are you using? This is usually caused by using an old version of PixelExperience Recovery or a different, non-supported custom recovery.

Could you advise how I might find the version of PixelExperience Recovery I'm using?

[valtf]

Try this
adb shell getprop ro.build.date

[lzgmc]

I used the recovery included in the PixelExperience_alioth-11.0-20211010-0709-OFFICIAL.img build. Thanks, David

Yeah, older recovery builds from Android 11 aren't compatible with newer roms. Since you already flashed the latest 12 build, the latest version of PixelExperience recovery was also flashed and you can flash future zip files without any problems.

Could you advise how I might find the version of PixelExperience Recovery I'm using?

The PixelExperience Recovery version number is the same as the rom it came with.

[dc9500]

Ok thanks. So I take it that PixelExperience A12 moved from using the ',' character to the '|' character to list out multiple supported devices for a build? And this now makes A11 to A12 upgrades on alioth impossible without manually modifying the metadata file?

…

On Fri, 21 Oct 2022, 8:51 am lzgmc, ***@***.***> wrote: I used the recovery included in the PixelExperience_alioth-11.0-20211010-0709-OFFICIAL.img build. Thanks, David Yeah, older recovery builds from Android 11 aren't compatible with newer roms. Since you already flashed the latest 12 build, the latest version of PixelExperience recovery was also flashed and you can flash future zip files without any problems. Could you advise how I might find the version of PixelExperience Recovery I'm using? The PixelExperience Recovery version number is the same as the rom it came with. — Reply to this email directly, view it on GitHub <#3541 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFQAUGUV2KTCQLB6X3GAZFTWEHEHDANCNFSM6AAAAAARIVAGCM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[lzgmc]

Pretty much. You should've been able to use the software updater to upgrade though.