@jezek Well, you would need to find the partition table of you phone to find the correct partition to flash the image to.

Not sure what would happen if the boot logo image was incorrect, it would work nonetheless (with a black screen) or perhaps it would brick the phone and you would have to reflash the correct image using fastboot then ... something like fastboot flash logo splash.img (the command may not work at all or could be different depending on the device).

And if you flash it to a wrong partition there is a great chance of bricking the phone.

@jezek You should be able to write the correct partition image (could be called e.g. "logo.img") using dd command right on the device but in order to do that you would have to have that image prepared already.

This is however very much device specific: https://forum.xda-developers.com/android/software-hacking/guide-how-to-create-custom-boot-logo-t3470473 so you would ideally have to check the correct instructions for you phone. And I expect such thing (if the XDA instructions do not recommend a Windows executable) would be doable on a phone as well but it would certainly not be the most comfortable way to deal with it.

@Flohack Thank you. Sadly I don't have that device for something like 2.5 years but am very happy it got fixed. Nice work :).

@Stefano I had Nexus 7 2013 deb and tasemnice was the only server that provided fully working Nexus 7 deb images. I've had Ubuntu Touch installed there both in dualboot mode as well as the only system present over the years and never experienced any WiFi issues. When tasemnice stopped working, I also tried UBports image from Nexus 7 flo on the device and it was also working fine in this perspective. So I've never seen this issue myself.

From what you say though it could mean the build was done differently when tasemnice was still active. But maybe you would have experienced the same issue with official Canonical images back then.

@Stefano Hm, this doesn't make sense then. If it works with Android sending to manufacturer is certainly not an option here. If that's the case then it would mean the EFS doesn't get destroyed but rather Ubuntu Touch has issues reading it.

@UniSuperBox Would there be a way for users to debug this somehow? It would be great if this thing could be solved as it seems to be recurring quite often in the forums/on github.

@UniSuperBox Yup :(, but it is not the first time I've experienced something like that. Last year when Xenial was still pretty much testing it (devel) also didn't work on arale for some time.

Edit: Oh, it was something else: https://forums.ubports.com/topic/901/xenial-ui-constantly-freezing-at-least-on-mx4 + https://github.com/ubports/ubuntu-touch/issues/434
In that case this is a new thing for me

I was wondering what's the best place to write about this and maybe more people will see this here.

It relates to Meizu MX4 (arale) and it seems I am unfortunately not able to run the latest edge releases on my phone.
I can use any of the following two commands but it always end up with my phone being not bootable as on power-on it always gets stuck at the boot logo:

system-image-cli --switch ubports-touch/16.04/edge --progress dots
ubuntu-device-flash --server=http://system-image.ubports.com touch --device=arale --channel=ubports-touch/16.04/edge

Do I by any chance need to do a full wipe first? But I doubt that's it.

Edit: And if I do:
system-image-cli --switch ubports-touch/16.04/edge --progress dots -r 22 for instance
the system seems to boot just fine. But nothing newer boots

Edit 2: So I've tried to wipe my phone completely and am still stuck on boot logo even with the latest revision (27). But it is apparently not affected by the latest Mir and Unity8 changes since 1. it is stuck right at the start, 2. revision 23 is much older, from "2019-01-02", and still doesn't work, even though rev 22 from "2019-01-01" does.

Actual report: https://github.com/ubports/ubuntu-touch/issues/1052

@giukas I don't know :(. All I did was that I used some clean alcohol to wipe the SIM card and regarding the slot I've just looked inside if there is something visible that would cause the issue and haven't seen anything. So I just blowed some air there ... and it still wasn't ok since the contact was lost later again so what resolved the issue for me was to push the card into the slot thoroughly ... maybe I haven't had it fully inserted before ... there could have been some dust there that have prevented me to place the card correctly.

Not sure ... but be careful and try not to destroy the slot it if isn't yet :). Good luck.

PS. It could also be a SIM card issue. You may want to try another one to see if it works or try this one in a different phone.

@giukas I've recently replaced battery on mine so I had to unscrew the back cover and prior taking that off remove the sim card from the slot. I am not sure what I did wrong but I had to re-insert the card to that slot a few more times in the next few days until I am finally not experiencing more such issues.

Fortunately in my case removing the sim card, cleaning the slot as well as the card and reinserting it fixed the issue (after a few retries).

This doesn't seem like system related issue though (especially since it does work for me). You can try installing Android on your device and see if it works there, but I suspect it to be a hardware issue. If that's the case that you may want to try cleaning the slot again and if nothing helps either ask some cellphone service to repair it or purchase a new device.

TBH I am often experiencing weird OSK behaviour with Telegram Plus (TELEports). From time to time I start typing a sentence and when I am on it, having its part written already, the keyboard just hides and I can only summon it again by either waiting a bit for it to appear again (if this works it can take quite a while, even like 30 to 60 seconds) or I can close the Telegram app and restart it again to finally be able to type - for a while :).

And now I've just found out I already reported this thing I am explaining above: https://github.com/ubports/ubuntu-touch/issues/695 so in case you are experiencing that too (no matter the app) please add your comment to that report so that it can be confirmed :).