@mrt10001 Thank you I will give it a try and hopefully works

@mrt10001 So at the moment the only program available on Linux to flash Android on MTK devices is the SP Flash Tool and by using Fastboot with the Runner that comes in the official ROM, I tried both ways and with both of them I get the same behaviour.
After installing Android and opening a terminal from recovery using the mount command, it list the partitions available to the OS on Android and it lists all of the partitions except for partition 18 and partition 19 if I recall correctly, with partition 18 being the NVRAM partition, trying to use e2fsck -yf /dev/block/sdc18 will show a message saying that the partition is not a valid Ext4 partition or that it might be corrupted, that we would need to try e2fsck -b with a different superblock, if I install Ubuntu however and run list the partitions Ubuntu shows the partitions and it labels it properly, at first I thought that somehow I had erased the partition completely, but it is not the case since Ubuntu can read it, so it seems to be more of an issue with being locked or hidden from Android somehow.

About the bootloader I have not relocked it, since I followed the cloud procedure once the bootloader is unlocked it can not be locked once more, it even gets disabled on the Developer options.

I have been trying to look for anything unusual but the only other amiss thing I have found is that ls /etc/deviceinfo/devices shows the device listed as a Pine device, but I am not really sure if this is just a leftover from the original Image that was used to develop this version of the OS, because at least based on documentation on Ubports wiki the device should be listed a Begonia with a yml format, but instead I have a Pinetab.yml file

is it possible to download an image or a click package and update that way?

@lakotaubp It shows Stable despite chosing RC in the AppImage installer, I tried changing to a different channel, from the updates screen, but I only get a blank screen in channels available

Today I tried seeing if it was possible to go to OTA 24 through the RC channel, but it was not possible at all, the same problem shows version 2021-09-11 and when looking for updates just shows that is up to date, any idea if 20.04 will be available for this device?

@moem I am not really sure, I liked the OS a lot but yeah, lack of updates means that will continue having the same bugs that had since it was released, and I have been trying to solve some of them but I am not at a level of a developer so a lot of times it feels like just trying some random solution and praying, I would love to try the latest version, if it was possible to upgrade.

Hi thank you in advance to everyone before hand for your time and assistance.

So I am currently having this issue, I have a Xiaomi Redmi Note 8 Pro, and I installed Ubuntu touch on it a long time ago, and I used to love it however, I realized that the project for that specific model was abandoned since there were no updates, even up to this date it has not received an OTA update and is currently sitting on version 2021/09/21, and despite my efforts to get Waydroid working properly I just managed to get it barely up and running, thanks to TheKit btw, after seeing no updates, probably due to low demand or usage on that specific device, I gave up and decided to return the device to Android.

It bricked, somehow I managed to get it up and running once more, however on Android using the stock rom MIUI baseband and IMEI showed as unknown, after looking for a way to restore the IMEI through software, it was possible but it required a backup of the NVRAM and NVDATA partitions, which I did not have access to from Android and sadly I did not back up before installing UT, and the only other solution I found on how to fix it, was through hardware modification which is beyond my level of skill, so I decided to install UT once more to see if it somehow UT had something to do with the IMEI missing on Android, to my surprise on UT the IMEI can be read just fine, it shows on my settings listed and somehow UT is able to communicate with the modem to connect to network through SIM, which makes me wonder if UT encrypts the NVRAM/NVDATA partition in a way that Android can not read it afterwards or just formats in a way that Android can not see it, and this is the reason why I am here.
I need some assistance with the following, in Android is possible to make a back up of the different partitions, and through a rooted device you can re-flash the parameters for the IMEI to restore it, so since UT can read these partitions and files, I need to know if I am able to extract the NVRAM.bin file through UT and the NVDATA.img partition, so that I can after flashing Android back, use this two specific partitions extracted from UT to restore the IMEI on Android. so how can I back up these partitions on UT? is this something even possible? and if possible would these files be compatible with Android?

if you read all the way to this point, I thank you for your time and any advice!
Regards,

@arubislander It's a Xiaomi Redmi Note 8 Pro

@arubislander It´s currently formatted as a FAT32

Hi,
I am currently trying to get some things working on my phone, and one of them is some android apps, I hope that this is the right place to ask, I looked into this and the information that I get is that I have to use either Waydroid or Anbox, I would like to know whether Anbox is still being developed or if is going to be replaced with Waydroid, I have seen that most posts that ask about Anbox end up referring to Waydroid instead, and I am confused on whether they will be merged or if there is no longer any interest in Anbox and is getting replaced instead on UT.

The other thing I would like to know, is that so far I have manage to install Waydroid however, when I try to run it I get the message that I am running XDG session which is not Wayland, it was a really long time ago that the discussion of Mir vs Wayland happened and I thought that UT was already compatible with Waydroid since most people directs you towards that, but it looks like since it does not run on Wayland is not compatible, do I have to install the entire display server of Wayland, or is it a thing that only some devices were taken into consideration for running it?

Thanks for any information.