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

    Installing UT on oneplus 1 w Cyanogen Mod

    Scheduled Pinned Locked Moved Support
    18 Posts 8 Posters 1.0k 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.
      • KenedaK Offline
        Keneda @El Franko
        last edited by

        @El-Franko
        Seems like for almost quite all the "frozen" install problems, an ADB driver issue.

        2015-2023 : Meizu MX4 ☠️⚰️✝️
        2023-2024 : Nexus 5 ☠️⚰️✝️
        2024-***** : FPOS Fairphone 5 waiting UT for freedom 😉
        🇲🇫🇬🇧

        E 2 Replies Last reply Reply Quote 0
        • E Offline
          El Franko @Keneda
          last edited by

          @Keneda Yes, "ADB is scanning for devices" message over and over again. The phone is in "fastboot" mode now. Should this work, or is fast boot the wrong mode? I have tried numerous different cables.

          KenedaK R 2 Replies Last reply Reply Quote 0
          • KenedaK Offline
            Keneda @El Franko
            last edited by Keneda

            @El-Franko
            For my MX4, on windows, i had to attach ADB driver to phone when booted in each normal, recovery, and fastboot mode.
            Each time boot in one mode, then connect and attach ADB driver when new "device" detected, then deconnect once done, and do this for every mode.
            I failed 3 days or more before understanding the ADB "mode" issue.
            Then, when i succeeded, i only had to connect phone in "normal" mode for ubports to recognize it (wich it wasn't before), and installer did all alone (reboot in fastoot then in recovery, and of course, install ubport image)
            See : https://forums.ubports.com/topic/4026/problem-upgrading-mx4-from-ota15-to-ubport

            I recently installed on a Nexus 5 using same method, and succeeded the first try ("full auto" install again).

            Maybe it's not your issue, but it could.

            2015-2023 : Meizu MX4 ☠️⚰️✝️
            2023-2024 : Nexus 5 ☠️⚰️✝️
            2024-***** : FPOS Fairphone 5 waiting UT for freedom 😉
            🇲🇫🇬🇧

            1 Reply Last reply Reply Quote 0
            • R Offline
              Rondarius @El Franko
              last edited by

              @El-Franko I don't have a OPO but I think that you need to put the phone in recovery mode for adb to see it. To enter recovery mode: In fastboot pushing vol+ or vol- until it says Recovery Mode push power button to enter Recovery Mode.

              4 Google Pixel 3A
              1 Google Nexus 6P
              2 Google Nexus 5
              2 Pinephones
              2 Sony Xperia X

              E 1 Reply Last reply Reply Quote 0
              • E Offline
                El Franko @Rondarius
                last edited by

                @Rondarius FYI, when the phone is in fastboot mode, it doesn't respond to pushing vol+ or vol-. Thanks for the suggestion.

                LakotaubpL 1 Reply Last reply Reply Quote 0
                • LakotaubpL Offline
                  Lakotaubp @El Franko
                  last edited by

                  @El-Franko If you hold the power button for long enough it will turn off. Then try putting it into recovery and clear the cache or just restart the installer and try again with the wipe option ticked.

                  1 Reply Last reply Reply Quote 0
                  • N Offline
                    Nathan123
                    last edited by

                    Actually change of plans. I got a OPO 64g with duel boot Android 10/ and lineage OS. It has TWRP on it.

                    1 Reply Last reply Reply Quote 0
                    • E Offline
                      El Franko @Keneda
                      last edited by

                      @Keneda So, I made it through the "reboot to bootloader" step in the UBports installer, by selecting "reboot to bootloader" on the phone. This steps completes very quickly, probably less than a second. The next step is called "reboot to recovery" and this is where it hangs up with the "ADB is scanning for devices" message. I have tried the process by selecting different options on the phone, as there isn't one specifically titled "reboot to recovery." It seems that neither "Reboot system now" or "reboot to bootloader" options on the phone work. Both leave UBports hanging. It seems a bit strange as I assume the ADB can find the phone as it passes the first step, but gets stuck on the second step. Any thoughts?

                      R KenedaK 3 Replies Last reply Reply Quote 0
                      • R Offline
                        ricardo65 @El Franko
                        last edited by

                        This post is deleted!
                        1 Reply Last reply Reply Quote 0
                        • R Offline
                          ricardo65 @El Franko
                          last edited by

                          @El-Franko When you get a hold of it, boot it up in recovery mode and when it appears it will start loading the system.

                          E 1 Reply Last reply Reply Quote 0
                          • E Offline
                            El Franko @ricardo65
                            last edited by

                            @ricardo65 Man, that was kind of painful. Bacon has been installed after being lubricated with a few tears. I have no idea why it started to work, I essentially just started jamming everything through. Had to acknowledge the “lost communication” warning about six times while downloading, even though the Mac and the phone showed data being steadily transferred. I really didn’t have the patience left to methodically continue trouble shooting after several hours. Thanks everyone for their input, clearly a big responsive community here. No SIM in it yet, but otherwise the OPO is running good, just starting to poke around and see what I can set up.

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

                              @El-Franko
                              The only thing you have to do on the phone is enabling developper mode on USB.

                              Booting on recovery or fastboot is done when phone is off, then keeping VOL- or VOL+ pushed, and pushing power button untill phone boot and say "recovery" or "fastboot".

                              https://www.droidape.com/how-to-boot-into-oneplus-one-recovery-mode/
                              https://www.droidape.com/how-to-boot-into-oneplus-one-fastboot-mode

                              It's very important that you attach ADB driver to device(s) like i said in my last previous post before doing anything else.

                              When all is ok, i repeat, ubports installer will do everything FULL AUTO, without touching anything appart from connecting phone, normally booted, to PC, when prompted by ubports installer in the beginning of the procedure.

                              2015-2023 : Meizu MX4 ☠️⚰️✝️
                              2023-2024 : Nexus 5 ☠️⚰️✝️
                              2024-***** : FPOS Fairphone 5 waiting UT for freedom 😉
                              🇲🇫🇬🇧

                              AppLeeA 1 Reply Last reply Reply Quote 0
                              • AppLeeA Offline
                                AppLee @Keneda
                                last edited by

                                @Keneda
                                It is my understanding that the OPO is more unpredictable than most other phones.
                                Many people complain about problems and it always seem to be really random and unidentified.

                                While with other devices it's more frequently a step missed or hardware issue.

                                OPO is well supported but I sense that installation will always be a pain with this device.

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