Ubuntu Boot problems after install On A2

Tinninator

@Tinninator follow up.
I've done the factory reset and tried again the installation.
I am back at the start. Boot and crash

MrT10001

@Tinninator On your PC in your ADB/Fastboot (see note at the bottom) folder command prompt:

./fastboot flash recovery <location of your TWRP image file>

In TWRP wipe Cache/Dalvik
In TWRP wipe data
In TWRP wipe system
In TWRP wipe internal storage

In TWRP reboot to the bootloader.

On your PC in your ADB/fastboot folder command prompt::

./fastboot --set-active=b

Then:

./fastboot flash recovery <location of your TWRP image file>

In TWRP:

Advanced, adb sideload, wait
and then go to your PC and type in the ADB/Fastboot command line:

./adb sideload <location of your zipped Android ROM>

Wait, set the slider to start the install and then hit enter on the PC. Once it has finished in TWRP, reboot to the bootloader and in your PC ADB/fastboot folder type in:

./fastboot --set-active=a

Then:

./fastboot flash recovery <location of your TWRP image file>

Then reboot to recovery and in TWRP, Advanced, adb sideload and then go to your PC and type in the ADB/Fastboot command line:

./adb sideload <location of your zipped Android ROM>

Wait, set the slider to start the install and then hit enter on the PC. Once it has finished in TWRP and the PC command line, reboot to the system.

If all goes well it will boot into Android.

Once in Android, set USB debugging once you have enabled developer options and follow the onscreen instructions on the Ubuntu Touch installer.

Points to note:

Have your vendor.img file downloaded and ready.

Install Android Studio - all of it.

Why?

It will give you the latest ADB and fastboot drivers which work. It works constantly on all my installs with no issues. This is on Windows (10 and 11), MacOS and Linux.

In Windows navigate to:

C:\Users\<yourname>\AppData\Local\Android\Sdk\platform-tools

to access ADB and fastboot running the command line.

If the set active slot command fails, research for the commands, the syntax of the command gets tweaked and may be slightly different

Tinninator

@MrT10001 Same problem.
Can't load Android system, your data may be corrupt

MrT10001

@Tinninator You have formatted data in TWRP to EXT4? You have wiped in advanced wipe all above? You have tried another USB cable? You have redownloaded the correct ROM? The bootloader is unlocked?

If so, then you are probably looking at a hardware fault, which basically means the device needs specialist repair.

Tinninator

@MrT10001 do you know what Android version is the one inside website rom?
I' ll try to download it from Xiaomi instead of the website.
If even in that case it will not work i'll send it to repair

MrT10001

@Tinninator The ROM that you download from the UT jasmine_sprout device list is the correct one.

Point 2 as I said earlier is important:

"Your device must be running a specific android 9 build before installing Ubuntu Touch. You can use the link below to download it. You can use either use stock recovery or TWRP recovery to flash it. Flash it to both slots to be safe."

Also note the fastboot option on the device is buggy and may cause issues. I have two of these devices and have had no issues with the installs.
I have flashed the above noted stock ROM to both slots, following the instructions I have stated using TWRP as the recovery.

I cannot be there fully to help you, but you are either missing a step, your partitions are the incorrect size or you have hardware failure (hardware failure is usually a bootloop or a boot into what you are seeing, and the filed piece of hardware within the device is the storage chip (eMMC)).

Set the b slot active and flash the ROM to that using TWRP.
Before flashing, wipe the data partition in the wipe command (not the advanced wipe).

Tinninator

@MrT10001 ok.
I've tried something different.
I've done a factory reset of Android 9 and after flashed that rom (founded on Xiaomi website)with MIflash.
No file corrupted, it worked nicely.
And here is the but, after the installation it still boot and crash in loop

arubislander

@Tinninator OK, but did you try following @MrT10001 's instructions step by step?

Tinninator

@arubislander yes i did