Navigation

    UBports Robot Logo

    UBports Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    SOLVED Flashing of the latest android image fails

    Support
    1
    3
    253
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jobus last edited by

      I had learned in https://forums.ubports.com/post/49306, I have to install the latest android image for my device, which is a nexus 5.
      Today, I had the opportunity to try that. I have done following tasks:
      In general, I followed the introduction on https://developers.google.com/android/ota#hammerhead. Because the UBports Recovery menu differs from the original android menu, I list the steps I have done:

      on the linux host:
      - adb reboot recovery

      on the nexus 5 device (shows UBports Recovery)
      - clicked "Android actions"
      - clicked "Apply update"
      - clicked "Apply from ADB"
      now the device is in sideload mode and shows the entry
      - Cancel sideload

      on the linux host:
      - adb devices
      I see a device - which must be mine, but I can't identify the number - in mode sideload
      - adb sideload hammerhead-ota-m4b30z-752c16b1.zip
      That fails and on the recovery screen of the device an error message is shown:
      - E:opening /res/keys: no such file or directory
      I suppose, that path should be contained in zip archive, which is not.

      sideload-error.jpg

      Does anybody know what is going wrong ?

      J 1 Reply Last reply Reply Quote 0
      • J
        jobus @jobus last edited by

        Update:
        The image, I used, is an OTA image. Now I read on https://source.android.com/devices/tech/ota/sign_builds#signatures-sideloading, that these kind of images are used for updating and checked on authenticity which makes sense of course. For this kind of check should be a key set available. That key set should be available, because an android image is already installed.

        In my case is an UBports image installed and I suppose, I should better use this link https://developers.google.com/android/images#hammerhead
        I will try that tomorrow.

        J 1 Reply Last reply Reply Quote 0
        • J
          jobus @jobus last edited by

          yapp, it worked. Now the phone is on the latest android again.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post