@stanwood said in Installation Experience:
I guess you did unlock the bootloader using the MI flashtool?
Yes. I believe this is the only way to do it. And they have an official client only for Windows.
I've completed the setup successfully. Now onto exploring. 
Is this supported by UT?
I see that the device has this option, although I haven't tried or enabled it while it was still on Android.
Does anyone know how to activate with UT installed?
@messayisto Interesting. I found only some Java version but it didn't run on Arch at first.
Thanks for sharing.
@flohack Oh, nevermind. Touching the fingerprint sensor wakes the device and this is just as good to give that power button a break!
So, the issues is solved. The thread still has an "unsolved" tag, making it really prominent in the forum.
Is this supported by UT?
I see that the device has this option, although I haven't tried or enabled it while it was still on Android.
Does anyone know how to activate with UT installed?
@stanwood said in Installation Experience:
I guess you did unlock the bootloader using the MI flashtool?
Yes. I believe this is the only way to do it. And they have an official client only for Windows.
I've completed the setup successfully. Now onto exploring.
Checking the installation script, it seems that it expects the vendor.img but the downloaded file is .zip and I used that without unzipping the content.
In the meantime, I've also downloaded a few more versions of lavender firmware from miui
The sha256 hash matches, so perhaps the third time lucky...
One, obviously important, detail is that I selected the RC channel initially, because I wanted a shorter release cycle.
In the meantime I managed to get into Fastboot mode and have repeated the process with the stable version and it did manage to install and boot successfully.
But, as I'm writing this, it has rebooted itself and is again stuck at the boot logo.
Just checked the checksum with sha256 and it indeed differs from the one in the script.
However, the script does not really know which file will be downloaded from the url, though. (you can see I'm under the impression of IPFS and its benefits)
I got a Redmi Note 7 today just so I could install UT on it. The experience wasn't so great, unfortunately. I'll report a few issues here, hopefully it might help someone.
The real nightmare was trying to unlock the device. Fortunately, on this one there is no 1 week waiting period, as there is on some other Xiaomi devices. But I ran into a problem where the device would disconnect on Fastboot when reading the "oem device-info". The same was happening when the unlocker tool was trying to read the info so it took a while to figure out which part was not working correctly.
Luckily, found a similar issue somewhere on Reddit, stating that it worked on an older PC. For me it did not work on one Windows laptop, the Java tool couldn't run on Linux, but fortunately it worked on a third machine.
After unlocking, the installer reported a wrong checksum for the downloaded vendor file, although the zip file has no errors.
Now, after the installation has completed, the phone is stuck on the boot logo and can't be turned off.
