Stucked in recovery mode while installing with UBports Installer

ShadowCastiel · 3 Jun 2022, 10:27

I found already another post here, but I think it won't solute my issue. I already installed a OnePlus 6t successfully here with the UBports Installer Version 0.9.5 (really awesome). Now I want to install another OnePlus 6 with the same UBports Installer Version on my Ubuntu 21.10 Version here. Now it get stucked in the Recovery Mode. I can't even turn it off for now. If I try to restart the UBports Installer and step back into the Bootloader it flashes again the files to the system and tell me I have to restart it in Recovery Mode. I restarted it into the recovery mode, but it still can't find my system. Whats the matter here? Does anyone have an idea?

Keneda · 6 Mar 2022, 10:51

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

with the same UBports Installer Version on my Ubuntu 21.10 Version here

You installed first phone on same PC with all same software or only same ubp intaller version on another PC ?

ShadowCastiel · 3 Jun 2022, 11:04

@keneda I installed the whole OnePlus 6t with the same setup, including Notebook, Ubuntu Version and UBports Version. So this is the point. I do not really know why this crashed.

Keneda · 3 Jun 2022, 11:16

@shadowcastiel
Same USB port and cable ?

ShadowCastiel · 3 Jun 2022, 11:20

@keneda Yes, I just plugged the one OnePlus 6t off (from the same cable) and plugged the other OnePlus 6 in.

Keneda · 3 Jun 2022, 12:35

@shadowcastiel
Oh, the one that worked is a 6t and the one that stucks is a 6 not t ?

Lakotaubp · 6 Mar 2022, 12:45

@shadowcastiel Just as a check can

fastboot devices

typed in a terminal detect the OP6 when in Recovery Mode? and it was on Android 9.

ShadowCastiel · 3 Jun 2022, 13:00

@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?

Keneda · 6 Mar 2022, 13:15

@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

ShadowCastiel · 3 Jun 2022, 13:12

@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

Keneda · 6 Mar 2022, 13:27

@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.

Lakotaubp · 3 Jun 2022, 14:02

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

ShadowCastiel · 3 Jun 2022, 14:03

@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.

Lakotaubp · 3 Jun 2022, 14:13

@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.

ShadowCastiel · 3 Jun 2022, 14:14

@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

MrT10001 · 3 Jun 2022, 14:18

@shadowcastiel Try:

fastboot oem unlock

and:

fastboot oem unlock_critical

ShadowCastiel · 3 Jun 2022, 14:20

@mrt10001 for both commands the following output:

fastboot oem unlock_critical
FAILED (remote: '	Device already : unlocked!')
fastboot: error: Command failed

MrT10001 · 3 Jun 2022, 14:30

@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.

ShadowCastiel · 3 Jun 2022, 14:52

@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.

MrT10001 · 3 Jun 2022, 15:32

@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.