Installer fails

usenix

@antidroid Good point about the slots- I thought the more careful approach is to flash just the one- however, since after flashing the phone is in a state where I can't select the other slot anyway, I can probably flash both
BTW upon detecting the phone the ubports installer instructs to use a specific stock android version and provides the dowload link. So yes, this must be phone-specific.
@BristledKing did you flash the stock android 9 (downloaded from ubports link, I suppose)? To both slots? And how (just to make sure I could reproduce your approach)? And from a phone that was running android 9 or android 10?

BristledKing

@usenix I did try an other android without success. I followed this vidéo but I translated on Linux instead of windows : https://www.youtube.com/watch?v=0t4UE4SiEL8

And used Ubuntu android 9 link instead of the one he provides in the comments section. I also used his twrp guide, for exemple he claims that only twrp 3.3.1 works for the A2... I wish you will find the solution!

I am not really understanding what I am doing ! so it s hard for me to help you correctly ...

c4pp4

I successfully went through the process from Android 10 -> 9 -> UT. I don't remember exact walkthrough but I think it was something like this:

I was using Linux distribution.

At first I unlocked the device and flashed TWRP 3.5.0_9-0. I followed the video from here:
https://www.youtube.com/watch?v=sqmng9WQFkI.
Instead of installing TWRP installer (time 10:02) I used Advanced -> ADB Sideload:

adb sideload twrp-installer.zip

I also sideloaded Magisk-v21-4.zip to check "jdi" LCD via app:
https://play.google.com/store/apps/details?id=ru.andr7e.deviceinfohw.

After that I followed the video from here (the same @BristledKing linked):
https://www.youtube.com/watch?v=0t4UE4SiEL8.
I switched from slot A to B and sideloaded Android 9 from here: https://github.com/ubports-xiaomi-sdm660/artifacts/releases/download/v0.1/jasmine_sprout_stock_android9.zip (UBports installer recommends flash it to both slots to be safe but I didn't do that).

UBports installer:
I think the device was recognized as "jasmine" not "jasmine_sprout" so I chose the right one from the list.
I chose devel channel.
After the failure with downloaded vendor.img I think I made a copy into ~/snap/ubports-installer/334/.cache/ubports/jasmine_sprout/firmware/ folder.
UBports installer told me UT was successfully installed but after that gave me an error. The device didn't boot. I tried the installation again and the second try was really succesful.

belohoub

Hello all!
I just won a fight with the A2 installation process

After many iterations with the installer, I successfully installed it from the "devel channel".

I tried to replicate all steps mentioned above, but for a long time with only a little success.

The part of the process running "in the" fastboot (almost) always finished well: in short I have a working ubports recovery. The only two inconveniences I observed here:

there is the vendor.img checksum mismatch - this is probably only a mistake in the config file (old checksum and updated file ?) - it is possible to ignore, but it's a security issue
the installer "requested" reboot to "bootloader", but "fastboot" was in reality required - I noticed when I was in the bootloader and the installer said something like "fastboot is waiting for device"

But what I observed too many times was the following error:

the installer (almost) always hangs when I was already in recovery and the installer was trying to download ubuntu touch with the following error:

Error: systemimage:install: Error: Failed to download latest version TypeError: Cannot read property 'forEach' of undefined

I was successful only with the devel channel and even with the devel channel only in "some cases".

After a "successful" installation, the device stuck about 3-times in the "boot screen", the 4th "completed" iteration (after a few iterations terminated with the error above) was successful.

I tried from two locations with different network configurations...

I believe, that the root of the problem would be in the config file and/or remote repository accessibility, but I'm unable to perform diagnostics without deeper knowledge of the UBports ecosystem (which I do not have).

During the debug process, I was trying to find the instructions for the "manual installation" - could you provide it or point me to its description? I believe, that I'll be able to provide a closer analysis of what happened to report it using the manual process.

Is the "stable" and "rc" channel available for this device or it is not - I was unable to locate it (based just on the brief docs study).

usenix

@belohoub That's very interesting. I followed the instructions from the video as well. That left me at least with an Android 9 installation where fastboot and adb work as expected.
When trying to use the installer thereafter, it is detecting the device, showing no error message, but then hangs when trying to install "stable", the installer hangs indefinitely. All I get on the console is

peter@pt450:~/Downloads$ ubports-installer 
info: Welcome to the UBports Installer version 0.8.4-beta!
info: device detected: jasmine_sprout
info: Installing Ubuntu Touch on your Xiaomi Mi A2 (jasmine_sprout)
info: configuring...
info: settings: {"channel":"16.04/arm64/android9/stable","wipe":false,"bootstrap":true}
 info: Good bye!

After your report, I might try again with the dev channel. However, since I want to use the phone as a daily driver, I have little interest in running anything that is not as stable as possible.
I'm kind of snowed in with work right now, but I will post my progress hopefully within a week.

I think it would be rather beneficial to not have a "black box" installer that can't be diagnosed, and instructions for a "manual install" would be more than welcome.

Best

AppLee

@usenix said in Installer fails:

a "black box" installer that can't be diagnosed

The sources are available and there are log files.
Investigation is possible and the procedure being complex the installer is the best option for most people.

New devices to the installer require some work, that's for sure. And some are more troublesome than others...

Best of luck

belohoub

@applee @usenix The problem actually was, that there was empty stable channel for jasmine_sprout (no release in this channel), but the installer offered it.

Currently, there is the first release(OTA-16) in the stable channel (http://system-image.ubports.com/16.04/arm64/android9/stable/jasmine_sprout/index.json)

To be honest, currently, the ubports ecosystem is somehow foggy for someone who is not familiar with it... actually, it took me some time to get into and get basic understanding of the dev cycle and resource location. This little piece of information is provided by ubports docs, while the good explanation is e.g. here

If I'll find some time, I'll try to document what I learned, because I started to like ubports, but currently, I invested my allowed hobby time into learning and doing this, and unfortunately I'm currently loaded by too many things ...

usenix

@AppLee As a user I will not troubleshoot the source code (which is also written in a language I don't speak). Where are the log files you speak of? They are not in the directory that ubports-installer is run from, they are not in $HOME. If they exist, that's great, but the existence and the location should be documented. The easiest solution is often to print everything to the terminal...
The Mi A2 is not a "new device" that should "require some work". I actually bought this device specifically since it is listed as supported by the installer and it is listed as a device where "everything" works.
Don't get me wrong, I'm aware that this is a community project. And I'm further aware that the Mi A2 is a community device. It's not a problem if things don't work. However, UBports presents itself (on ubports.com) as a project that is hiding a lot of technical details from its target audience, thereby making the impression that it's not necessary to care about technical details. "Just run the installer and go." Not.
@belohoub Thanks, that is valuable information. With the latest installer (0.8.7), I tried again to install the stable channel. But it hangs at "Cleaning Up - Formatting system partition" with no further information on the shell, just a lot of CPU load. Or does one have to wait (hours?) long? Afterwards the device is again in a state where fastboot is broken. Seems like I have to go the lengthy upgrade path to android 10 again to get a working device. I might try to re-flash the android 9-image once more and try again. At some point it will be time to settle for Lineage OS

Keneda

@usenix
I don't know for GNUL but on windows like for almost any program data, log is at C:\Users\User\AppData\Roaming\ubports\ubports-installer.log, some logs are also in C:\Users\Keneda\AppData\Roaming\ubports-installer.
I bet there is an identical folder on GNUL...

AntiDroid

On linux it is in the hidden home cache folder.

home/{user_name}/.cache/ubports/{device_name}/ubports-installer.log

belohoub

@antidroid for SNAP, it is here: ~/snap/ubports-installer/current/.cache/ubports, however, the messages are not very helpful for someone begining with ubports

I reported it - it might be an issue for new users with newly adopted devices