@MrT10001 said in Can NOT install UT Redmi note 9 pro "exit code 256":

Try installer version 0.10.0. Windows sometimes has an issue with fastbootd (which is not regular fastboot).

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA!!!!!!!????!!!
W.T.Flag

I installed UBport Installer in my dev rig/linux and IT WORKED!!!!!!!!!!!!

$*&% windows

After about 20 hours, maybe more, of trying, it just came to: "just don't use windows dude"

The windows installer do not recognize the phone when it is in fastbootd mode, so it stops the process.

Thanks guys @MrT10001 @Vlad-Nirky for the help and support
Alex

The guy from the reddit forum answer with the following, just in case it will help someone:

*Hi, if you give me more information about your current situation I might be able to assist more.

Basically my issue was that the installer made the system partition too small for all the files and updates and it fizzled out while trying to complete. So I just manually increased the partition size.

To do that you need to boot the phone in fastbootd (not the bunny fastboot/bootloader). If you are in UBports recovery, just select Advanced>fastboot, if not use fastboot reboot fastboot (I assume you have platform-tools installed, if you have gotten this far, you need them for next step).

First remove these two partition if present to free space (UT doesn't need them):

sudo fastboot delete-logical-partition product
sudo fastboot delete-logical-partition system_ext

Then run sudo fastboot resize-logical-partition system 3900000000 (3.9GB worked for me). If you get "size too big" try a smaller number.

Then go back to bootloader/fastboot (bunny) and run the UBports installer again. Make sure to select wipe data and bootstrap.*

@Vlad-Nirky
Well...... when my phone was in bootloader, the adb was finding it without any issues. Only when it was on fastbootd mode could not recognize it.

By the way, the global rom was not working, since I live in Greece, and I can verify that I re-install UT with the following Android version for European users:
V12.0.1.0.QJZEUXM

@arubislander
could be

@MrT10001 said in Can NOT install UT Redmi note 9 pro "exit code 256":

Try installer version 0.10.0. Windows sometimes has an issue with fastbootd (which is not regular fastboot).

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA!!!!!!!????!!!
W.T.Flag

I installed UBport Installer in my dev rig/linux and IT WORKED!!!!!!!!!!!!

$*&% windows

After about 20 hours, maybe more, of trying, it just came to: "just don't use windows dude"

The windows installer do not recognize the phone when it is in fastbootd mode, so it stops the process.

Thanks guys @MrT10001 @Vlad-Nirky for the help and support
Alex

@MrT10001 said in Can NOT install UT Redmi note 9 pro "exit code 256":

When installing UT only interact with the device when you have to. The reboot into fastbootd can take some time.

when you say "some time" do you mean 30 minutes?
because that how long I let there doing nothing

by the way I manage to install Droidian, which I do not want, successfully.

@Vlad-Nirky @MrT10001

I am not familiar with the ./flast_all.sh procedure.
I am installing with XiaoMiFlash application and it is working just fine.
With XiaoMiFlash I install with the locking , without the locking more that 30 times already the device and all the versions above 12 I had no problem. Always booted in the android environment.
@Vlad-Nirky
I cannot use all the instructions of the guide, of how to install from scratch, because when I click to install it from fatsbootd it stays in fastbootd and the UBport Installer can not recognize it to continue the process. Just stays in fastbootd for ever.
And whatever I do I always get exit code 256 at the end

@Vlad-Nirky
well..... it stops with an error

@Vlad-Nirky
the installation never ends.
It stops at the error:Error installing Ubuntu update, exit code: 256
and it start an endless reboot.
Please, you can also read the reddit post
I uploaded the log files

@Vlad-Nirky
Yes is the "classic" Xiaomi Redmi Note 9 Pro global
Yes the model is M2003J6B2G.
No the joyeuse_global_images_V12.0.3.0.QJZMIXM ROM did NOT work.