-
@lepotototor I don't have that device (yet) but it looks like you are doing the right thing. You may have to wait some considerable time for it to do some things. I have found with Xiaomi phones you have to be very patient. When it does not work from the installer I have found going back to stock ROM and trying again usually works.
-
Hello
I retry today, it doesn't work, but when the phone bootloop I try to flash the boot.img file and when I reboot the phone freese on poco logo.
So I've search into the cache data of the installer and there is a folder with recovery.img,vbmeta.img... but no one boot.imgSo I look the log of the installer, and I find something: the installer hasn't install boot.img and when he flash img he flash recovery.img for recovery and boot
I will try to flash with the reals img and the rom on the github repository
https://github.com/ubuntu-touch-juice/ubuntu-touch-citrus/releases
-
@lepotototor It doesn't work with flashing vbmeta, boot, recovery, dtbo and super image after installing android 10Q, the phone boot but the screen is black and I can't go into the recovery
-
@lepotototor switch the device off by holding the power button down with no power cable attached for at least 20 seconds. Once powered off, boot to fastboot mode by holding volume down and power button. It may boot to a blank screen. Attach the device to the pc and try again with the installer. Make sure you have the latest UT installer installed, the latest fastboot and ADB drivers installed and miflash and a stock ROM to hand.
-
@mrt10001 no it's doesn't work, the installer use recouvery.img to boot partition gain and thé phone bootloop
-
@lepotototor You need to install the stock ROM to try again. If it is boot looping at all times, make sure you set the active slot in fastboot to install the ROM to.
-
@mrt10001 yes I reinstall the stock rom but the problems are the same. I don't understand what you mean by set the active slot into fastboot. Also the recovery rom doesn't work, when I flash it the phone can't boot into recovery partition
-
@lepotototor Most newer phones have two slots, slot A and B. Here is an explanation of the slots which is far better than I could explain.
-
@mrt10001 OK I understand but when I try to see what is the current slots the terminal return that:
fastboot: error: Device does not support slots -
@lepotototor Ok, looks like that phone is not set up with slots. So back to square one:
You are at fastboot, which is good.
Have a read through this: TWRP
Your partitions may be screwed up. Reinstalling stock usually sorts this out, but TWRP is very useful to recover and repair things. I would not worry about rooting the device, but look at TWRP.
-
@mrt10001 Yes I know TWRP. I reinstall the stock ROM with fastboot and recovery but the installation of ubport failed. I also try to change the recovery.img by TWRP.img into the cache folder of ubport but I think installation can work juste with the ubport recovery.
I looked into the citrus's configuration file and other configuration with halium 10 and I think it's normal to flash the recovery.img into the boot and the recovery partition because after the installer use a fonction "install:image" and during the the reboot it download the file for thé système into several archives and into these archives there is the boot.img
I think my phone is cursed
. So I will try with the next version of the recovery.img and if still doesn't work I will sell it and buy a volla phone -
@lepotototor You checked the Data partition was EXT4?
-
@mrt10001 No I don't know how the partitions format and how change if it's not
-
@lepotototor In TWRP use the wipe feature (of course the usual disclaimer of back up your device, possibility of bricking it etc.). If I install any ROM, in TWRP I tend to erase Data, System and Cache in advanced wipe. However if installing a Linux based ROM, i.e. Sailfish OS, UT, PostMarketOS, I will convert the Data partition to EXT4 as some devices are in F2FS this which means no install.
-
@lepotototor Make sure you used the latest fastboot image and not recovery image of android 10
-
@nitanmarcel The poco m3 is build with halium 10 so I flash the recommended rom with android 10 and I use the latest recovery image of miui or the latest of TWRP ?
-
@lepotototor said in Installation on poco m3 failed:
@nitanmarcel The poco m3 is build with halium 10 so I flash the recommended rom with android 10 and I use the latest recovery image of miui or the latest of TWRP ?
I cannot see what you are trying to achieve. If you use the installer and follow the instructions, you should get a good install. If you don't, it is best to install TWRP, wipe DATA, CACHE and SYSTEM, then reinstall stock (using the MiFlash tool, ensuring you DO NOT relock the bootloader) and then try again with the UT installer.
If UT won't install, you have to make sure (using TWRP) that the DATA partition is erased and formatted to EXT4 and NOT F2FS - this will decrypt the DATA partition and allow UT to see it when installing.
If UT still fails to install then the device may have had a revision upgrade and might have (annoyingly and unknown) changed hardware like a different manufactured eMMC, Screen, Camera etc, that may stop UT installing.
These are some observations where I have had installation issues across a lot of devices. I have avoided flashing devices in the list using the CLI if there is the Installer available for it as without the installer it generally has failed down to my lack of CLI and coding Fu. I have had moderate success with devices not on the installer using the CLI without bricking the device to the point of unusability, an example is the Moto E 2nd gen EXT1524 which seems to be OK(ish) with UT.
-
L Lakotaubp moved this topic from Xiaomi Redmi Note 9 Pro/Pro Max/9S & Poco M2 Pro on
