UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Nord N10 lito - what is this, and is it supported?

    Scheduled Pinned Locked Moved Oneplus Nord N10
    6 Posts 2 Posters 77 Views 1 Watching
    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.
      • NoodleCollieN Offline
        NoodleCollie
        last edited by

        Hi,

        I bought a OnePlus Nord N10 5G in order to install Ubuntu Touch on it, since https://devices.ubuntu-touch.io/device/billie/ indicated it was well-supported. After going through the firmware downgrade and sorting out all my drivers, the installer eventually says the phone is not supported, because it's "lito" instead of "billie". I had no idea there were different versions of this model, and sites like https://www.phonemore.com/models/oneplus/nord-n10-5g/ state there's only one model and variant.

        Is this "lito" handset significantly different from a "billie" one, and if it is too different, is there a way I can determine whether a model is correct before I purchase it?

        MrT10001M 1 Reply Last reply Reply Quote 0
        • MrT10001M Offline
          MrT10001 @NoodleCollie
          last edited by

          @NoodleCollie Read here. It looks like the codename "lito" is for the Qualcomm chip in the device, not the codename of the OP Nord N10 5G.

          Xiaomi Redmi Note 7.... And more...
          I have too many devices...

          NoodleCollieN 1 Reply Last reply Reply Quote 0
          • NoodleCollieN Offline
            NoodleCollie @MrT10001
            last edited by NoodleCollie

            @MrT10001 I'm still not 100% clear - does this mean the device is compatible or not? The installer is treating it as a device name, and says it is not supported. I can try installing it anyway, but want to be sure.

            276cd26b-e0f4-4ac2-8fb7-a6f6d559e6b0-image.png

            MrT10001M 1 Reply Last reply Reply Quote 0
            • MrT10001M Offline
              MrT10001 @NoodleCollie
              last edited by

              @NoodleCollie This came up before on another device. Just to check, you downgraded using the Android ROM stipulated on the devices page? You have also unlocked the bootloader too as downgrading or upgrading the Android ROM using the MSM Download tool will automatically lock the bootloader?

              If all is done as above you should be good to go, if you are on the screen, manually select the device from the drop down box.

              Xiaomi Redmi Note 7.... And more...
              I have too many devices...

              NoodleCollieN 2 Replies Last reply Reply Quote 0
              • NoodleCollieN Offline
                NoodleCollie @MrT10001
                last edited by

                @MrT10001 Ah, I didn't know it'd re-lock the bootloader. I'll check that out and try again.

                1 Reply Last reply Reply Quote 0
                • NoodleCollieN Offline
                  NoodleCollie @MrT10001
                  last edited by

                  @MrT10001 That seemed to be the issue, thanks! Not sure why the installer interpreted the phone as a different device, but all was OK once I unlocked again.

                  Additionally, for anyone else who might stumble upon this, I had a random Android emulator listed in ADB, which caused the installer to get confused and raise an error. This turned out to be a Native Instruments background service, for some reason. Following https://stackoverflow.com/a/33810103, I was able to remove it and continue the installation.

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