Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • B Backlog
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 1,205
    • Issues 1,205
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • ee
  • Backlog
  • Issues
  • #5470
Closed
Open
Issue created May 19, 2022 by Alexander Nolting@a.nolting

Installing current OnePlus Nord e-0.23-q-20220511185000-stable-avicii.zip image fails

  • /e/ version: e_avicii-userdebug 10 QQ3A.2008053.001 eng.root.20220401.152129 dev-keys,stable-release
  • Device model(s): Oneplus Nord
  • Device rooted: no

Summary

I tried to update to the latest e/os/ using phones OTA capability.

The problem

Going to Settings,select Systemupdates and download and intall the rom fails.

Steps to reproduce

Go to Settings,select Systemupdates and download and intall the rom.

What is the current behavior?

The installations fails with simply an error message "Installation error". No additional information.

I tried to update the phone using adb and fastboot. I downloaded the the also available new recovery and the image from https://images.ecloud.global/stable/avicii/

  • recovery: recovery-e-0.23-q-20220511185000-stable-avicii.img
  • image: e-0.23-q-20220511185000-stable-avicii.zip
  • Checksum file: SHA256

Calculated the checksum and compared and found them to matched with checksum file.

I've updated the recovery on phone using the method described in the installation documentation for OnePlus Nord. Rebooted and tried again to do a OTA update. The installation fails again.

Next I tried to update the phone using adb sideload and the phone shows the error found on the screen shot.

Technical informations

Relevant logs (adb logcat) I would support with logs if someone can point me how to grab logs while in recovery.

Relevant screenshots

Attached screenshot image: PXL_20220519_091743642.MP

Solutions

Workaround

Possible fixes

Edited May 19, 2022 by Alexander Nolting
Assignee
Assign to
Time tracking