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

    unable to install on poco f1

    Scheduled Pinned Locked Moved Xiaomi
    23 Posts 4 Posters 4.3k 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.
      • A Offline
        audrew @MrT10001
        last edited by audrew

        @mrt10001 Sir, fastboot and adb-tools is latest. I will try to check if adb devices is available before running ubports. But maybe there is other way to do it manually because it doesn't seem to work.

        Mario.CHM 1 Reply Last reply Reply Quote 0
        • Mario.CHM Offline
          Mario.CH @audrew
          last edited by

          Hi Audrew,

          @audrew said in unable to install on poco f1:

          Sir, fastboot and adb-tools is latest. I will try to check if adb devices is available before running ubports. But maybe there is other way to do it manually because it doesn't seem to work.

          To determine if the Android device is reachable, enter the following command in the terminal:

          adb devices
          

          If adb has not been used in the current session, the terminal will first report the start of the adb daemon, then, if all goes well, something like

          * daemon not running. starting it now on port 5037 *
          * daemon started successfully *
          List of devices attached 
          5200d6fd904b2200 device
          

          If there is only an empty line after List of Devices attached instead, the device is not reached (yet); check in the USB connection settings on the device if "Load only" is selected. If unauthorized is displayed instead of device, the connection has been established, but must be confirmed on the device; to do this, confirm permanent access in a message displayed on the device. If recovery is displayed next to the device number, the device is in recovery mode.

          Please check and let us know.

          Greetings
          Mario
          Translated with www.DeepL.com/Translator (free version)

          πŸ“± Oneplus Nord N100 UT20.40 (OTA5); then Xperia X (since 2020) at last UT 20.04(OTA5), now out of service due to defective camera
          🐎 When you realize you are riding a dead horse, get off!
          My languages skill: πŸ‡¨πŸ‡­πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ, and only orally: πŸ‡¬πŸ‡§ πŸ‡ΉπŸ‡­

          A 1 Reply Last reply Reply Quote 0
          • A Offline
            audrew @Mario.CH
            last edited by

            @mario-ch device is listen in adb devices. I still receive same error. Waiting for device adb is scanning for devices.

            KenedaK 1 Reply Last reply Reply Quote 0
            • KenedaK Offline
              Keneda @audrew
              last edited by

              @audrew
              What is the OS on your PC ?

              2015-2023 : Meizu MX4 ☠️⚰️✝️
              2023-2024 : Nexus 5 ☠️⚰️✝️
              2024-***** : FPOS Fairphone 5 waiting UT for freedom πŸ˜‰
              πŸ‡²πŸ‡«πŸ‡¬πŸ‡§

              A 1 Reply Last reply Reply Quote 0
              • A Offline
                audrew @Keneda
                last edited by audrew

                @keneda linux ubuntu

                KenedaK 1 Reply Last reply Reply Quote 0
                • KenedaK Offline
                  Keneda @audrew
                  last edited by

                  @audrew
                  Ah ok.
                  Can you adb device from pc when it is booted in recovery ?

                  2015-2023 : Meizu MX4 ☠️⚰️✝️
                  2023-2024 : Nexus 5 ☠️⚰️✝️
                  2024-***** : FPOS Fairphone 5 waiting UT for freedom πŸ˜‰
                  πŸ‡²πŸ‡«πŸ‡¬πŸ‡§

                  A 2 Replies Last reply Reply Quote 0
                  • A Offline
                    audrew @Keneda
                    last edited by

                    This post is deleted!
                    1 Reply Last reply Reply Quote 0
                    • A Offline
                      audrew @Keneda
                      last edited by

                      @keneda no

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

                        @audrew either you don't have the correct/latest or no ADB driver installed, or your usb cable is faulty. Also try another usb slot on the pc, preferably not usb 3.

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

                        A 1 Reply Last reply Reply Quote 0
                        • A Offline
                          audrew @MrT10001
                          last edited by audrew

                          @mrt10001 I did correct installation on nexus 4 with same usb. I just also tried another usb even though one is working too. nothing changed

                          KenedaK 1 Reply Last reply Reply Quote 0
                          • KenedaK Offline
                            Keneda @audrew
                            last edited by Keneda

                            @audrew
                            Here what i can tell you, but i did install on my mx4 using windows 7 so it surely differs from ubuntu.

                            I asked you for the recovery thing because my mx4 ubports installer install always issued the same exact moment each time i tried, untill i understand that on windows, my device was 3 separate devices in device manager for every boot mode, one device was normal boot, for wich i had to install (or link) adb drivers so that ubp installer auto detect device, one another device was when i connected my mx4 in fastboot, another adb driver link needed here to allow installer to reconnect to device after rebooting it from normal to fastboot, and at least, one last adb driver link when booted in recovery, so that ubp installer can continue to "talk" to device after rebooting it from fastboot to recovery, and finish install.

                            So best is to boot device in normal, link adb driver, then reboot fastboot, link adb driver again, and then reboot recovery, and do the last adb link, and then you can reboot in normal, launch ubp installer, and plug usb then device recognised and install is auto from beginning to end.

                            Again, that was under windows, with a mx4, and i have no clue how unbutu or linux desktop handle drivers install and link to devices, so maybe your issue is not the same or same origin, but, my two cents here ^^

                            2015-2023 : Meizu MX4 ☠️⚰️✝️
                            2023-2024 : Nexus 5 ☠️⚰️✝️
                            2024-***** : FPOS Fairphone 5 waiting UT for freedom πŸ˜‰
                            πŸ‡²πŸ‡«πŸ‡¬πŸ‡§

                            A 1 Reply Last reply Reply Quote 0
                            • A Offline
                              audrew @Keneda
                              last edited by audrew

                              @keneda I tried to find manual to install it via twrp, I get official system.img boot.img of ubuntu touch. But probably not all files was correct and it doesn't boot. Maybe anyone know any article about that?

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

                                @audrew Check here. I would still recommend the Ubports Installer as they do.

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

                                A 1 Reply Last reply Reply Quote 0
                                • A Offline
                                  audrew @MrT10001
                                  last edited by audrew

                                  @mrt10001 out artifacts link is broken

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

                                    @audrew It's an old post, but should give pointers. Don't take it "as is", but use it to help solve issues.

                                    If you have an ADB error, you have to do basic troubleshooting i.e.:

                                    Change USB cable
                                    Change USB port
                                    Try another PC
                                    Update ADB drivers
                                    Clear space on your PC
                                    Install TWRP and format data partition and make sure it is formatted to EXT4
                                    Wipe the system and Cache partition
                                    Reinstall the correct stock ROM, but DO NOT relock the bootloader (you have to use a windows PC for Xiaomi phones and use the Mi Flash tool) and start again.

                                    One USB cable may work on one device, but not on another.

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

                                    A 1 Reply Last reply Reply Quote 0
                                    • A Offline
                                      audrew @MrT10001
                                      last edited by audrew

                                      @mrt10001 as far as I know adb shoudnt to be detected in fast boot mode. Or it should? Every time I try to install ubuntu, boot data is erased and the ubuntu touch is not installed. So basically I have to rewrite back android and try again. It is very tedious

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

                                        @audrew ADB is like a higher level of Fastboot. Basically ( please feel to correct me anyone) fastboot installs a boot image and a recovery image. The boot image allows UT to boot, but you usually have to manually boot to recovery. Once in recovery ADB is then working and the UT install will continue by pushing the UT files over it from the PC to the device.
                                        A bad or incompatible USB cable will stop ADB from functioning so no UT install.
                                        An encrypted data partition will stop an install and can be flagged as an ADB error, that is why you have to format the data partition to EXT4 and wipe it so it is decrypted.
                                        If the partitions have been resized, usually by installing a non stock ROM such as Lineage OS, UT won't install and may give an ADB error.
                                        A bad or USB 3 port may cause an ADB error.
                                        A PC/laptop may cause an issue for various reasons, if UT won't install on Windows, try a Linux based machine or a MacOS based machine.
                                        Try an older installer, the latest Ubports installer may be a bit buggy.
                                        Also follow the installation instructions to the letter or the install usually fails. Try a different channel if the stable channel fails to install.

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

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