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

    Stucked in recovery mode while installing with UBports Installer

    Scheduled Pinned Locked Moved Solved Oneplus 6/6T
    25 Posts 4 Posters 5.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.
      • S Offline
        ShadowCastiel @Lakotaubp
        last edited by

        @lakotaubp yes it was also in Android 9, the recovery Mode thing can I test later, so that I can try to check if it is there. Do you know a good command on ubuntu to check if the device is there? šŸ™‚

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

          @shadowcastiel said in Stucked in recovery mode while installing with UBports Installer:

          Do you know a good command on ubuntu to check if the device is there?

          Like @Lakotaubp said, use fastboot devices adb command to do so, when phone connected to PC in fastboot mode.
          https://technastic.com/fastboot-commands-list/#fastboot_devices

          There is also this command : adb devices , when phone connected to PC in normal boot mode (android running).
          https://technastic.com/fastboot-commands-list/#Fastboot_Mode

          2015-2023 : Meizu MX4 ā˜ ļøāš°ļøāœļø
          2023-2024 : Nexus 5 ā˜ ļøāš°ļøāœļø
          2024-***** : FPOS Fairphone 5 waiting UT for freedom šŸ˜‰
          šŸ‡²šŸ‡«šŸ‡¬šŸ‡§

          S 1 Reply Last reply Reply Quote 0
          • S Offline
            ShadowCastiel @Keneda
            last edited by

            @keneda Okay in Fastboot mode there can the device be detected. If i switch into the recovery mode it is unable to detect the device. How can this happen?

            With fast boot there is the following output:

            (bootloader) Verity mode: true
            (bootloader) Device unlocked: true
            (bootloader) Device critical unlocked: false
            (bootloader) Charger screen enabled: true
            (bootloader) enable_dm_verity: true
            (bootloader) have_console: false
            (bootloader) selinux_type: SELINUX_TYPE_INVALID
            (bootloader) boot_mode: NORMAL_MODE
            (bootloader) kmemleak_detect: false
            (bootloader) force_training: 0
            (bootloader) mount_tempfs: 0
            (bootloader) op_abl_version: 0x0
            (bootloader) cal_rebootcount: 0x31
            OKAY [  0.001s]
            Finished. Total time: 0.002s
            
            KenedaK LakotaubpL 2 Replies Last reply Reply Quote 0
            • KenedaK Offline
              Keneda @ShadowCastiel
              last edited by Keneda

              @shadowcastiel
              Well, i had a similar detection issue whith my MX4, but that was the opposite, phone was detected in normal boot and recovery by adb command, but not in fastboot mode...
              But that didn't prevent from installing, my problem was a driver issue (my device needed 3 drivers installations, one for each device mode : normal, recovery, and fastboot).

              If you want to check my adventure installing UT UBP version on my phone, you can go there.

              Edit :
              I see

              (bootloader) Device critical unlocked: false
              

              In your log, maybe it's the issue, and that should be on "true", but i can't tell, not knowing your device much.

              2015-2023 : Meizu MX4 ā˜ ļøāš°ļøāœļø
              2023-2024 : Nexus 5 ā˜ ļøāš°ļøāœļø
              2024-***** : FPOS Fairphone 5 waiting UT for freedom šŸ˜‰
              šŸ‡²šŸ‡«šŸ‡¬šŸ‡§

              S 1 Reply Last reply Reply Quote 0
              • LakotaubpL Offline
                Lakotaubp @ShadowCastiel
                last edited by

                @shadowcastiel @Keneda is right double check the bootloader is actually unlocked thentry the commands again. Both need to detect your device.

                S 1 Reply Last reply Reply Quote 0
                • S Offline
                  ShadowCastiel @Keneda
                  last edited by

                  @keneda nah critical unlock is for updating the bootloader I guess. So my problem is now. The device won't be detected if I connect it within the recovery mode. With the fastboot is everything fine. So my problem for now is, I don't know why no Notebook (Windows, Mac oder Linux) can detect the phone while it is in recovery mode. And no it also won't be shown in the device manager in windows.

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

                    @shadowcastiel So you are sure the bootloader is unlocked (fastboot oem unlock) if so you could try here https://t.me/WelcomePlus our install group. I have no experiance of OP6 but it is normally something simple and someone there will know. If you enabled oem unlocking, developer options and Advanced boot (not sure if this is needed) not sure where to go.

                    1 Reply Last reply Reply Quote 0
                    • S Offline
                      ShadowCastiel @Lakotaubp
                      last edited by

                      @lakotaubp Well i ran the command:

                      fastboot flashing unlock
                      
                      FAILED (remote: '	Device already : unlocked!')
                      fastboot: error: Command failed
                      

                      So why the fastboot is still telling me this?

                      fastboot oem device-info
                      (bootloader) Verity mode: true
                      (bootloader) Device unlocked: true
                      (bootloader) Device critical unlocked: false
                      (bootloader) Charger screen enabled: true
                      (bootloader) enable_dm_verity: true
                      (bootloader) have_console: false
                      (bootloader) selinux_type: SELINUX_TYPE_INVALID
                      (bootloader) boot_mode: NORMAL_MODE
                      (bootloader) kmemleak_detect: false
                      (bootloader) force_training: 0
                      (bootloader) mount_tempfs: 0
                      (bootloader) op_abl_version: 0x0
                      (bootloader) cal_rebootcount: 0x31
                      OKAY [  0.001s]
                      Finished. Total time: 0.001s
                      
                      MrT10001M 1 Reply Last reply Reply Quote 0
                      • MrT10001M Online
                        MrT10001 @ShadowCastiel
                        last edited by

                        @shadowcastiel Try:

                        fastboot oem unlock
                        

                        and:

                        fastboot oem unlock_critical
                        

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

                        S 1 Reply Last reply Reply Quote 0
                        • S Offline
                          ShadowCastiel @MrT10001
                          last edited by

                          @mrt10001 for both commands the following output:

                          fastboot oem unlock_critical
                          FAILED (remote: '	Device already : unlocked!')
                          fastboot: error: Command failed
                          
                          
                          MrT10001M 1 Reply Last reply Reply Quote 0
                          • MrT10001M Online
                            MrT10001 @ShadowCastiel
                            last edited by

                            @shadowcastiel Great so that means the device is definitely unlocked.

                            Flash the device back to the required stock ROM and go into developer options and ensure that the check for OEM unlock is in the unlock position (it may be giving you a false flag).

                            When you have done that, install TWRP and ensure all the partitions are on EXT4.

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

                            S 1 Reply Last reply Reply Quote 0
                            • S Offline
                              ShadowCastiel @MrT10001
                              last edited by

                              @mrt10001 how can I flash it back to stock rom? I am not able to find a device:

                              adb reboot bootloader
                              error: no devices/emulators found
                              

                              Is my phone now bricked? What happened here? How can I install TWRP now? I am really not sure for now.

                              MrT10001M 1 Reply Last reply Reply Quote 0
                              • MrT10001M Online
                                MrT10001 @ShadowCastiel
                                last edited by

                                @shadowcastiel make sure the phone is disconnected from the USB cable and switch the phone off. Wait a few seconds to make sure. Then press the power button till and volume down buttons together until the phone switches on. This will boot you into fastboot mode. Connect the phone to the PC and install TWRP using the fastboot command:

                                fastboot flash recovery <location and name of your TWRP img file>
                                

                                Once TWRP is installed, your phone should be picked up by the PC and you can copy the stock ROM image over to the root of your device and side load it with TWRP.

                                Download the stock image from here

                                I used rollback image.

                                Once the image is installed, reboot the device and set Android up. Make sure it is on Android 9 and enable developer options. Make sure OEM unlock is enabled or has been enabled.

                                Then reboot the phone to the bootloader, install TWRP and ensure the data and storage partitions are EXT4 - this is important as UT won't install.

                                Try UT install again. If it fails, go back to TWRP (you will have to install it again) and wipe the data partition and ensure the data and system partitions are EXT 4, then wipe all the partitions except OTG. If you get warnings when these processes are happening, when they end reboot to fastboot, install TWRP and do it again.

                                If no warnings try the UT install again.

                                I apologise, I have skimmed over a bit.

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

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

                                  @mrt10001 Just out of interest could you not just install TWRP then wipe and format EXT4 system,data and cache as needed like with the OP5 then run the installer.

                                  Edit: If on Android 9 that is.

                                  MrT10001M 1 Reply Last reply Reply Quote 0
                                  • MrT10001M Online
                                    MrT10001 @Lakotaubp
                                    last edited by

                                    @lakotaubp If it was on Android 9, but I would go back to stock to a)make sure it is on Android 9 and b) to ensure the OEM unlock button has been checked.

                                    It is a faff, but I have found with all the devices, if an error get thrown up, back tracking and going back to stock is the best way to success.

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

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

                                      @mrt10001 Good point best to check that everything is as it should be to avoid false errors and know the process is correct.

                                      S 1 Reply Last reply Reply Quote 0
                                      • S Offline
                                        ShadowCastiel @Lakotaubp
                                        last edited by

                                        @lakotaubp is now all fine with the OnePlus 6. I recovered it with the Qualcomm Emergency Downloader.

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

                                          @shadowcastiel Good to know. Could you please mark as solved https://forums.ubports.com/topic/6311/how-to-ask-a-question-and-then-mark-it-as-solved Thanks

                                          1 Reply Last reply Reply Quote 0
                                          • S ShadowCastiel marked this topic as a question on
                                          • S ShadowCastiel has marked this topic as solved on
                                          • First post
                                            Last post