Posts made by pe3noATo2DOTpl

pe3noATo2DOTpl

Dear @AppLee and @alagirialagiri,
My Ubuntu Desktop Experience with the snap = a lot of storage space consumed.
I searched the web and I met articles where the people where showing how to remove snap and how to live without it using the alternative solutions. The general summary was: snap was introduced by Canonical and furthermore it was promoted/forced by them. But it causes problems, as the users confirm (my case is the many GB consumption of the storage space). I'm not sure what would be the potential benefits...? Just to double check/think before implementing the snap mechanism into Ubuntu Touch...
Kind regards~~ Piotrek~~pe3no.

pe3noATo2DOTpl

Dear @Luksus, @DPITTI, @gzagatti, @muskist, @Resonus and other UBPorts Friends,

57.1). Would you be able to help me to solve the "Checking info..." error, please? Moreover, the real goal is to install, run and use the WizzAir Aplication, please.

57.2). I installed Waydroid some time ago, with GAPPS and now for the first time I need to install some Applications.

57.3). The Waydroid Updater has upgraded the Image to the Latest Version: 18.1 (26 Jul 2024). I try to Sign In to the Play Store and I get the "Checking info..." loop. After some time I get the error: "Something went wrong. Please go back and try again". When I go back and try again, the same error occurs.

57.4). I checked that the internet works on the Waydroid. The Web browser is showing web pages without any problem.

57.5). I cannot perform the Factory Erase: Settings > System > advanced > Reset options > Erase all data (factory reset) > Erase all data > Erase all data > {no effect}.

57.6). Settings > Accounts > Add account > {I would like to add the google mai} > Again the same error: "Something went wrong".

57.7). Unfortunately, I'm not able to successfully install manually the WizzAir Application, either. Well, the installation was done, the application runs, the WizzAir App Initial Screen appears but it gets frozen...

57.8). I did the following:

57.9). Inside Waydroid > WebBrowser > WizzAir apk > Search > https://apkpure.com > WizzAir 8.0.5 > Download APK > Quick Download from APK Pure > Download > Install > Scann App > Install > App installed > Open > Wizz Air > Downloading.. 153.6MB > Allow from this source > {Switched from 0 to 1} > back > Do you want to install this application? > Install > Installing... > App Installed > OPEN >

57.10). The WizzAir application starts, the Initial Screen appears but it gets frozen on this first screen...

Thanks in advance for your help and Kind Regards~~ Piotrek ~~ pe3no.

pe3noATo2DOTpl

Dear @MrT10001 and other UT Friends,

54). I unpacked the "excalibur_in_global_images_V12.0.3.0.QJXINXM_20210218.0000.00_10.0_in_d103044d71.tgz" and I checked that md5=d103044d71b3d4fa4b480d7fd6fa9e08.

55). I executed the flash_all.sh
$ ~/Downloads/excalibur_in_global_images_V12.0.3.0.QJXINXM_20210218.0000.00_10.0_in$ sh flash_all.sh

product: excalibur
Erasing 'boot'                                     OKAY [  0.010s]
Finished. Total time: 0.013s
Sending 'xbl' (3562 KB)                            OKAY [  0.126s]
Writing 'xbl'                                      OKAY [  0.185s]
Finished. Total time: 0.317s
Sending 'xblbak' (3562 KB)                         OKAY [  0.104s]
Writing 'xblbak'                                   OKAY [  0.096s]
Finished. Total time: 0.204s
Sending 'xbl_config' (70 KB)                       OKAY [  0.005s]
Writing 'xbl_config'                               OKAY [  0.006s]
Finished. Total time: 0.016s
Sending 'xbl_configbak' (70 KB)                    OKAY [  0.004s]
Writing 'xbl_configbak'                            OKAY [  0.006s]
Finished. Total time: 0.015s
Sending 'imagefv' (20 KB)                          OKAY [  0.005s]
Writing 'imagefv'                                  OKAY [  0.001s]
Finished. Total time: 0.010s
Sending 'imagefvbak' (20 KB)                       OKAY [  0.009s]
Writing 'imagefvbak'                               OKAY [  0.001s]
Finished. Total time: 0.016s
Sending 'aop' (159 KB)                             OKAY [  0.010s]
Writing 'aop'                                      OKAY [  0.002s]
Finished. Total time: 0.016s
Sending 'aopbak' (159 KB)                          OKAY [  0.009s]
Writing 'aopbak'                                   OKAY [  0.002s]
Finished. Total time: 0.016s
Sending 'uefisecapp' (123 KB)                      OKAY [  0.007s]
Writing 'uefisecapp'                               OKAY [  0.002s]
Finished. Total time: 0.026s
Sending 'uefisecappbak' (123 KB)                   OKAY [  0.008s]
Writing 'uefisecappbak'                            OKAY [  0.002s]
Finished. Total time: 0.016s
Sending 'qupfw' (52 KB)                            OKAY [  0.008s]
Writing 'qupfw'                                    OKAY [  0.001s]
Finished. Total time: 0.015s
Sending 'qupfwbak' (52 KB)                         OKAY [  0.009s]
Writing 'qupfwbak'                                 OKAY [  0.001s]
Finished. Total time: 0.016s
Sending 'metadata' (48 KB)                         OKAY [  0.009s]
Writing 'metadata'                                 OKAY [  0.001s]
Finished. Total time: 0.015s
Sending 'tz' (2919 KB)                             OKAY [  0.079s]
Writing 'tz'                                       OKAY [  0.011s]
Finished. Total time: 0.095s
Sending 'tzbak' (2919 KB)                          OKAY [  0.080s]
Writing 'tzbak'                                    OKAY [  0.011s]
Finished. Total time: 0.095s
Sending 'hyp' (386 KB)                             OKAY [  0.020s]
Writing 'hyp'                                      OKAY [  0.003s]
Finished. Total time: 0.028s
Sending 'hypbak' (386 KB)                          OKAY [  0.017s]
Writing 'hypbak'                                   OKAY [  0.005s]
Finished. Total time: 0.027s
Sending 'keymaster' (232 KB)                       OKAY [  0.010s]
Writing 'keymaster'                                OKAY [  0.002s]
Finished. Total time: 0.023s
Sending 'keymasterbak' (232 KB)                    OKAY [  0.008s]
Writing 'keymasterbak'                             OKAY [  0.003s]
Finished. Total time: 0.016s
Sending 'cmnlib' (388 KB)                          OKAY [  0.017s]
Writing 'cmnlib'                                   OKAY [  0.003s]
Finished. Total time: 0.025s
Sending 'cmnlibbak' (388 KB)                       OKAY [  0.017s]
Writing 'cmnlibbak'                                OKAY [  0.002s]
Finished. Total time: 0.025s
Sending 'cmnlib64' (503 KB)                        OKAY [  0.018s]
Writing 'cmnlib64'                                 OKAY [  0.003s]
Finished. Total time: 0.026s
Sending 'cmnlib64bak' (503 KB)                     OKAY [  0.016s]
Writing 'cmnlib64bak'                              OKAY [  0.003s]
Finished. Total time: 0.025s
Sending 'modem' (131084 KB)                        OKAY [  3.841s]
Writing 'modem'                                    OKAY [  0.627s]
Finished. Total time: 4.473s
Sending 'dsp' (32768 KB)                           OKAY [  1.073s]
Writing 'dsp'                                      OKAY [  0.122s]
Finished. Total time: 1.201s
Sending 'dspbak' (32768 KB)                        OKAY [  1.056s]
Writing 'dspbak'                                   OKAY [  0.119s]
Finished. Total time: 1.181s
Sending 'bluetooth' (892 KB)                       OKAY [  0.037s]
Writing 'bluetooth'                                OKAY [  0.003s]
Finished. Total time: 0.045s
Sending 'bluetoothbak' (892 KB)                    OKAY [  0.029s]
Writing 'bluetoothbak'                             OKAY [  0.008s]
Finished. Total time: 0.043s
Sending 'storsec' (20 KB)                          OKAY [  0.011s]
Writing 'storsec'                                  OKAY [  0.001s]
Finished. Total time: 0.018s
Sending 'devcfg' (42 KB)                           OKAY [  0.010s]
Writing 'devcfg'                                   OKAY [  0.001s]
Finished. Total time: 0.017s
Sending 'devcfgbak' (42 KB)                        OKAY [  0.009s]
Writing 'devcfgbak'                                OKAY [  0.002s]
Finished. Total time: 0.017s
Sending 'abl' (204 KB)                             OKAY [  0.010s]
Writing 'abl'                                      OKAY [  0.002s]
Finished. Total time: 0.017s
Sending 'ablbak' (204 KB)                          OKAY [  0.011s]
Writing 'ablbak'                                   OKAY [  0.002s]
Finished. Total time: 0.019s
Sending 'dtbo' (8192 KB)                           OKAY [  0.270s]
Writing 'dtbo'                                     OKAY [  0.025s]
Finished. Total time: 0.300s
Sending 'vbmeta' (4 KB)                            OKAY [  0.007s]
Writing 'vbmeta'                                   OKAY [  0.001s]
Finished. Total time: 0.014s
Sending 'vbmetabak' (4 KB)                         OKAY [  0.010s]
Writing 'vbmetabak'                                OKAY [  0.001s]
Finished. Total time: 0.017s
Sending 'recovery' (131072 KB)                     OKAY [  4.310s]
Writing 'recovery'                                 OKAY [  0.543s]
Finished. Total time: 4.859s
Sending sparse 'super' 1/7 (784676 KB)             OKAY [ 25.613s]
Writing 'super'                                    OKAY [  0.000s]
Sending sparse 'super' 2/7 (785048 KB)             OKAY [ 25.564s]
Writing 'super'                                    OKAY [  0.000s]
Sending sparse 'super' 3/7 (786360 KB)             OKAY [ 25.394s]
Writing 'super'                                    OKAY [  0.001s]
Sending sparse 'super' 4/7 (777060 KB)             OKAY [ 26.093s]
Writing 'super'                                    OKAY [  0.000s]
Sending sparse 'super' 5/7 (710432 KB)             OKAY [ 21.993s]
Writing 'super'                                    OKAY [  0.000s]
Sending sparse 'super' 6/7 (785093 KB)             OKAY [ 25.963s]
Writing 'super'                                    OKAY [  0.001s]
Sending sparse 'super' 7/7 (435084 KB)             OKAY [ 14.702s]
Writing 'super'                                    OKAY [  0.000s]
Finished. Total time: 165.352s
Sending 'vbmeta_system' (4 KB)                     OKAY [  0.004s]
Writing 'vbmeta_system'                            OKAY [  0.001s]
Finished. Total time: 4.598s
Sending 'vbmeta_systembak' (4 KB)                  OKAY [  0.009s]
Writing 'vbmeta_systembak'                         OKAY [  0.001s]
Finished. Total time: 0.016s
Sending 'cache' (152 KB)                           OKAY [  0.009s]
Writing 'cache'                                    OKAY [  0.002s]
Finished. Total time: 0.027s
Sending 'userdata' (300888 KB)                     OKAY [  9.610s]
Writing 'userdata'                                 OKAY [  0.000s]
Finished. Total time: 9.616s
Sending 'cust' (205060 KB)                         OKAY [  5.956s]
Writing 'cust'                                     OKAY [  0.000s]
Finished. Total time: 7.505s
Sending 'ffu' (7168 KB)                            OKAY [  0.245s]
Writing 'ffu'                                      OKAY [  0.038s]
Finished. Total time: 1.104s
Erasing 'misc'                                     OKAY [  0.009s]
Finished. Total time: 0.013s
Erasing 'apdp'                                     OKAY [  0.002s]
Finished. Total time: 0.005s
Sending 'boot' (131072 KB)                         OKAY [  4.290s]
Writing 'boot'                                     OKAY [  0.610s]
Finished. Total time: 4.905s
Rebooting                                          OKAY [  0.000s]
Finished. Total time: 0.050s

55). "Redmi" appeared on the phone's screen.

56). "MIUI" appeared on the screen.

57). "MIUI 12" appeared > Settings > About phone > MIUI Global 12.0.3 Stable.

58). I suppose that now I'm ready for UT installation

Thank you for your Feedback/Patience/Hints and Kind Regards~~ Piotrek~~pe3no.

pe3noATo2DOTpl

Dear @MrT10001, thank you so much for that Important Clarification, to avoid the wrong ROM!!!

51). Based on your Great Hint, I found this:
https://xmfirmwareupdater.com/miui/excalibur/stable/V12.0.3.0.QJXINXM/

52). Device: Redmi Note 9 Pro Max India
Codename: excalibur
Version: V12.0.3.0.QJXINXM
Branch: Stable
Type: Fastboot
Size: 3.1 GB
Release Date: 2021-02-18
Package Name: excalibur_in_global_images_V12.0.3.0.QJXINXM_20210218.0000.00_10.0_in_d103044d71.tgz
MD5: d103044d71b3d4fa4b480d7fd6fa9e08

53). Would you be so kind to help me prepare the proper fastboot command, please?

Thank you and Kind Regards~~ Piotrek~~pe3no.

pe3noATo2DOTpl

Dear @MrT10001,

45). Should I use this file for my Note 9 Pro MAX 8/128 4G? : "miui_CURTANAGlobal_V12.0.3.0.QJWMIXM_fffd838f47_10.0.zip", md5=fffd838f47190ef69762118c59d7da07, 2.3GiB.

46). I'm not going to relock the BL but I want to continue with UT installation instead.

47). What do you mean when saying "Use the flashboot ROM and the flash_all command"?

48). Sorry if I'm asking a silly question, but I checked that in the HowTo (https://forums.ubports.com/topic/9957/installation-guide-redmi-note-9s) and I cannot find such steps... I'm still learning

49). Or maybe I should use this file, which I also downloaded from the same web site? : "curtana_global_images_V12.0.3.0.QJWMIXM_20210117.0000.00_10.0_global_de4cf898d7.tgz", md5=de4cf898d7cc1575df3859b4e741740c, (4.1GiB).

Thank you for the clarification, your Great Patience and Kind Regards~~Piotrek ~~pe3no.

pe3noATo2DOTpl

Dear Friends,

42). The above link still does not work.

43). I found another one - where actually 2 files are available. Could you point the right one, please?
https://xiaomirom.com/en/download/redmi-note-9s-note-9-pro-curtana-stable-V12.0.3.0.QJWMIXM/

Thanks and Kind Regards~~ Piotrek~~pe3no.

pe3noATo2DOTpl

Dear @stanwood and Dear @Emphrath - thank you for your Great Help and for the Great HowTo!!!

38). The download fails when I try to access the following site:
https://xiaomifirmwareupdater.com/miui/curtana/stable/V12.0.3.0.QJWMIXM/

39). I get the "We can’t connect to the server at xiaomifirmwareupdater.com" Error Message.

40). Every other web site loads correctly, so I suppose it might be a temporary failure?

41). Would it be possible to ask you to upload that somewhere, please?

Thanks and Kind Regards~~ Piotrek~~pe3no.

pe3noATo2DOTpl

Dear @Beyolf and Dear @Josele13,

32). After a very long search I finally found a Note 9 Pro MAX 8GB / 128GB 4G and I'm very happy!

33). Being still a medium level user, I'm fighting for a few days trying to unlock the BootLoader... what a shame.

34). Would you be so kind to share the detailed HowTo for this first step, please?

35). It seems to me that I try to do it precisely like in the films but when I finally have the phone in the FastMode, with the Mi Account logged in, the button to unlock the BL is inactive.

Thank you and I wish you All the best Kind Regards ~~ Piotrek~~pe3no

pe3noATo2DOTpl

Hello Dear @rubencarneiro, Dear @muskist and other UT Friends

15.1). Dear @rubencarneiro, Congratulations and thank you very much for this Wonderful Port and for your Great Effort!

15.2). Dear Friends, would you be so kind to confirm, if these two Lenovo Tab M10 HD models would be good for the installation, please?

15.3). https://psref.lenovo.com/Detail/Lenovo Tablets/Tab_M10_HD_2nd_Gen?M=ZA6V0012PL

15.4). https://psref.lenovo.com/Detail/Lenovo Tablets/Tab_M10_HD_2nd_Gen?M=ZA6V0117PL

Thanks and regards~~ Piotrek~~pe3no.

pe3noATo2DOTpl

Dear @Luksus,

I successfully installed UT20.04 devel-14 @ X605L 4/64, using ubports-installer - thank you very much for another Great Step and Congratulations!

Kind regards~~ Piotrek~~pe3no.

pe3noATo2DOTpl

Hello Dear @KingProNoob2, @Marsh_Jiang and other UBports Firends

13.1). Did you get any progress and/or do you continue your efforts?

13.2). I found the quite fresh LineageOs 19.1 for N80xx here:
https://xdaforums.com/t/lineageos-19-1-android-12l-for-gt-n8000-gt-n8005-gt-n8010-gt-n8013-gt-n8020-beta.4363603/

13.3). I would be happy to get involved to help somehow to someone who could try to port this device to Ubuntu Touch 20.04

Thank you and kind regards~~ Piotrek~~pe3no.

pe3noATo2DOTpl

Dear @Luksus thank you for the explanation and I would be happy if I could support you further
Have a nice day and kind regards~~ Piotrek~~pe3no.

pe3noATo2DOTpl

Dear @Luksus - again thank you very much for your Effort and for having shared this new UT 20.04 Upgrade/Release!

53.001). I confirm that I was able to boot it without any workaround However, I needed to do a temporary Ubuntu Touch 16.04 installation in between (as shown in the [PASSED] TC002/53.301). I needed to execute the additional steps "53.309-310", to be able to boot UT20.04@X605L 4/64, after having flashed boot.img, ubuntu.img and recovery.img.

53.002). On the other hand, I was not able to boot it when I flashed these 3 images directly on top of Android 9, without the temporary UT16.04 installation (see the [FAILED] TC001/53.201 for more details). Therefore, I'm not sure if someone who has a Lenovo X605L with Android 9 would be able to install UT 20.04 without the need to install UT 16.04 first.

53.003). As you suggested, I added flashing of recovery.img and I avoided wiping (unless explicitly requested, e.g. in 53.310) and I stopped using any workaround.

53.004). In my Test Cases I wanted to reflect the real life use cases which UT users can face during Ubuntu Touch 20.04 installation. Could you let me know what/how I could change there, in order to better support you, please ?

53.005). Could I also ask you, if I correctly understood that when I have the Fresh Factory Reset Android 9 on X605L 4/64 then I should only flash boot.img, ubuntu.img and recovery.img, using the FastBootMode? or maybe I should do something more (what/how)?
53.006). I'm asking that because the UBports-Installer downloaded 9 files for UT 16.04 (I'm not sure if all of them were flashed then) but I'm asking myself if these only 3 which I flashed for UT 20.04 were not to few?
53.007). I'm happy and ready to do the re-test with more files if I could get them, together with the information what/how I should do

Dear @Luksus, thank you in advanced for your feedback and kind regards~~ Piotrek~~pe3no.

If you want to know more, see the below details please:

53.101). PREREQUISITES:
53.102). I used boot.img (MD5=e1fc16cdb3e85094ce40c96315ccc68a) and system.img (MD5=75fc62c23bd81858528c140660ab573a) extracted from artifacts.zip (ID=5951873058), shared in your Latest Build ("/50").
53.103). I took recovery.img shared in your "/52" entry (MD5=02967e01c979f04e79e10e610a22ea20).
53.104). "ETW" = "Empty-Tray-Workaround", which I was using to bypass booting problems.
53.105). "FBM"= "FastBootMode".
53.106). "TC", "TCs" = Test Case, Test Cases.
53.107). Tablet has the BootLoader Unlocked. User installs UT20.04 at X605L 4/64 (ZA490162PL or equivalent). Other models not tested.
53.108). TWRP: the file "twrp-3.7.0_9-0-X605F.img" from https://twrp.me/lenovo/lenovo_X605F.html can be installed for X605L, using FBM.

53.201). Name and Status: TC001 - [FAILED]
53.202). Description: "Android9@X605L -> via -> FBM-FlashBootSystemRecovery-NoETW -> to -> UT20.04"
53.203). Details: User of an Android 9 X605L 4/64 tablet wants to manually install Ubuntu Touch 20.04 on the device, flashing: boot.img, ubuntu.img and recovery.img in the FastBootMode. Empty-Tray-Workaround is not applied.
53.204). Test Case Steps:
53.205). I get back the Factory Fresh Android 9 on X605L 4/64.
53.206). In TWRP-3.7 I restored "20180802...FreshAndroid9" backup (which I can share with you if needed).
53.207). I booted X605L to Android 9, set up Language, accepted License Agreement and all the rest, skipping what possible to save time and to simplify the step.
53.208). Now I have the Factory Fresh Android 9 on X605L 4/64, with the Stock Recovery, because TWRP has been replaced by Android at boot because Magisk was not installed.
53.209). Therefore, now we have the real life use case - the typical, fresh, not customized Android 9 on X605L 4/64 and user wants to manually flash UT20.04. Bootloader is unlocked.
53.210). I turn off X605L, connect it to PC via USB-C cable and I switch X605L to FastBootMode (VolumeDown+Power).
53.211). I flashed boot.img, ubuntu.img, recovery.img and I restarted, being in FBM:
$ fastboot flash boot boot.img; fastboot flash system ubuntu.img; fastboot flash recovery recovery.img; fastboot reboot
53.212). Lenovo Logo appears, I disconnect USB-C cable. Ubuntu Touch is not booting. I wait 5 minutes.
53.213). I don't apply the Empty-Tray-Workaround, so both SIM and microSD are continuously inside X605L.
53.214). I turn off X605L (Power button pressed for 10 seconds).
53.215). I turn on X605L (Power button - 2 seconds).
53.216). Lenovo Logo is continuously shown on the screen and UT is not booted. I wait 5 minutes again but no success.
53.217). I consider the TC to be FAILED.

53.301). Name and Status: TC002 - [PASSED]
53.302). Description: "Android9@X605L -> via -> {temporary UBports-Installer 16.04 Installation} -> FBM-FlashBootSystemRecovery-NoETW -> to -> UT20.04"
53.303). Details: User of an Android 9 X605L 4/64 tablet temporarily installs UT 16.04 using UBports-Installer, in order to prepare the device to perform the manual installation of Ubuntu Touch 20.04, by doing FBM flashing of: boot.img, ubuntu.img and recovery.img. Empty-Tray-Workaround is not applied.
53.304). Test Case Steps:
53.305). I get back the Factory Fresh Android 9 on X605L 4/64.
53.306). In TWRP-3.7 I restored "20180802...FreshAndroid9" backup (which I can share with you if needed).
53.307). I booted X605L to Android 9, set up Language, accepted License Agreement and all the rest, skipping what possible to save time and to simplify the step.
53.308). Now I have the Factory Fresh Android 9 on X605L 4/64, with the Stock Recovery, because TWRP has been replaced by Android at boot because Magisk was not installed.
53.309). Therefore, now we have the real life use case - the typical, fresh, not customized Android 9 on X605L 4/64 and user wants to manually flash UT20.04. BootLoader is Unlocked. Developer Mode is activated by tapping 7x the Build Number (TB-X605L_S210283_221108_ROW). In Developer Options the USB Debugging is turned on.
53.310). I connect it to PC via USB-C, I executed "$ adb devices" in the terminal on PC and I confirmed "Allow Debugging" > Always > ok > I run ubports-installer on PC ($ ubports-installer &) > "info: device detected: X605" > My device is unlocked > Ubuntu Touch > Install > 16.04 stable > Wipe userdata (mandatory on first install) > OK > rebooting to bootloader > I'm in FBM > Flashing Firmware > Cleaning up > Continue > Waiting for the device > Manually switched to Recovery > VolumeUp+Down+Power > Not disconnected USB-C > then VolumeUp+Down until Ubuntu Recovery appears > waiting some time > Pushing files message on PC's screen > Reboot > USB-C cable has been disconnected > Installing update > Reboot > Lenovo Logo > Ubuntu Touch . . . . Logo appears > booting quickly > Success > Languages/Countries list appeared > I did a quickest possible setup in order to check the System Version: Ubuntu 16.04 (OTA-25) > I powered off X605L > Switched to FastBootMode manually (VolumeDown+Power) and I connected X605L to PC via USB-C cable.
53.311). I flashed boot.img, ubuntu.img, recovery.img and I restarted in FBM:
$ fastboot flash boot boot.img; fastboot flash system ubuntu.img; fastboot flash recovery recovery.img; fastboot reboot
53.312). Lenovo Logo appears, I disconnect USB-C cable > Ubuntu Touch is booting > Welcome to Ubuntu Touch 20.04. We will make sure your device is ready to use Ubuntu Touch 20.04 > Next > Major Changes > Welcome back > Your device is ready to work > Continue > Settings > OS > Ubuntu Touch 20.04
53.313). I consider the TC to be PASSED

53.401). Name and Status: TC003 - [Not Yet Available]
53.402). Description: "Android9@X605L -> via -> UBports-Installer -> to -> UT20.04"
53.403). Details: User of an Android 9 X605L 4/64 tablet wants to install Ubuntu Touch 20.04 on the device, using "UBports-Installer".

Dear @Luksus, thank you one more time for having shared the Great fruit of your Effort and kind regards~~ Piotrek~~pe3no.

pe3noATo2DOTpl

Dear @Luksus,

51). Thank you very much for your Effort and for sharing the new image

51.1). I installed it on X605L 4/64, using the below steps. This time I'm taking notes while I'm installing it, so I'm creating the detailed description, to be sure that I don't miss anything. Sorry if it's too detailed...
51.2). Using TWRP 3.7 (Keep Read Only applied), I did Wipe > Format > yes > Swipe to wipe.
51.3). Advanced Wipe : Dalvik / ART Cache, System, Vendor, Data, Internal Storage, Cache > Swipe to wipe.
51.4). I restored Android 9, [Boot, Recovery, System Image, Vendor Image, Firmware Image, Data (excl. storage), Cache, Persist, Misc, Config (frp), EFS], using "20160402_...FreshAndroid9" backup, which I can share with you if needed.
51.5). I connect X605L and PC via USB-C cable and I switch from TWRP to FastBootMode in the following way: Reboot > BootLoader.
51.6). In FastBootMode I flash the fresh boot and system images.
51.7). $ fastboot flash boot boot.img
51.8). $ fastboot flash system buntu.img
51.9). In parallel I prepare "fastboot reboot" command in PC's terminal and i press "VolumeUp+VolumeDown+Power" followed by "Enter" on the keyboard.
51.10). X605L reboots and when the "Lenovo" logo appears I release "Power" but I continue "VolumeUp+Volume+Down" pressed until TWRP appears.
51.11). I disconnect USB-C cable from X605L.
51.12). I turn off X605 doing: Reboot > Power Off
51.13). I empty the SIM/microSD tray and I put it empty into X605L.
51.14). I turn on X605L using the power button, Lenovo Logo appears and after about 1 minute Ubuntu Touch booting screen appears, followed by languages list. I press long the power button, select the red "Power Off" option and X605L is powered off.
51.15). I put the microSD & SIM into the tray and I insert it into X605L.
51.16). I turn on X605L using the power button and the Languages List appears. I power off X605L in order to perform TWRP backup.
51.17). I backup all (Boot, Recovery, System Image, Vendor Image, Firmware Image, Data (excl. storage), Cache, Persist, Misc, Config (frp), EFS), with compression enabled > Swipe to Backup > "20240117...05951873058...Fresh" and if needed I can share it with you (for example if the workaround with the empty tray would not work on your device or for any other reasons) > Reboot > System.
51.18). Ubuntu Touch booted, the Language List appeared, I selected English (USA) > Defined my location > password and ... woooow ... I was able to run the new Ubuntu Touch! I have not tested any function for the moment but I will be happy to share my experience.

Dear @Luksus - I'm so happy and thankful for the new UT20.04 image which you developed and shared with us! Kind regards~~ Piotrek~~pe3no.

pe3noATo2DOTpl

Dear @kuailexs,

27). I'm trying to install Waydroid @ Meizu Pro 5 UT 16.04 devel 983 (2023-04-14) and it seems that the porter should allow/activate it for this device. Could you please help or if I'm doing something wrong, could you share how to properly install Waydroid on it, please?

28). When I try to install it using the Waydroid Helper, it's stuck on "Preparing to download system image".

29). When trying in terminal, I get the following messages:
Failed to load binder driver
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/3.10.100-user-01771-g301b04f/modules.dep.bin'
modprobe: FATAL: Module binder linux not found in directory /lib/modules/3.10.100-user-01771-g301b04f
ERROR: Binder node "vndbinder" for waydroid not found

30). To be more specific, in terminal I was trying to install Waydroid in the following way:
sudo -s
sudo mount -o remount,rw /
apt update
apt install waydroid -y
waydroid init

Thank you and kind regards~~ Piotrek~~pe3no.

pe3noATo2DOTpl

Dear @Luksus and Dear other UBports Friends,

48). I would like to share with you the workaround/s to boot the UT 20.04 of Luksus, which has/have worked for me, at my X605L 4/64 (other versions not tested).

48.1). I did a lot of actions/tests and now I'm trying to reconstruct/collect all the steps which I performed.

48.2). My description might not be fully accurate, so please be patient and ask, if something is incomplete and/or incorrect, please.

48.3). WORKAROUND SHORT VERSION:
48.4). Flash the boot.img and ubuntu.img in FastBootMode (uplodaded by Luksus on 2023-09-22 01:27:25 as the #1013489143 artifacts_zip).
48.5). During the first boot of UT 20.04 on X605L 4/64, you need to have the empty tray inserted into the tablet (without SIM nor microSD cards but the tray should be insterted).
48.6). The Lenovo Logo should disappear after some time and tablet should boot in the optimistic scenario. Sometimes it can get stuck at Lenovo Logo or after it disappears, the screen can be black but you can notice that the lighting of the screen still works. If it's stuck for longer, press the Power button once and it should immediately Power off. Press the Power button again and this time it should properly boot. That's the tricky part and especially here, please forgive me if I might describe it not fully properly, as I'm trying to remind myself the steps which I did in several attempts...
48.7). When the language selection list appears, press long the physical Power button and select "Power Off" on tablet's screen. X605L 4/64 is turned off.
48.8). Put the SIM and microSD cards into the tray and re-insert into the tablet.
48.9). Press the Power button and since this moment the X605L 4/64 should boot every time normally, with the SIM and microSD inserted. I haven't tested other combinations. My microSD card is 256GB but I suppose that the size and type does not matter.

48.10). Well, it seems to be so simple and... actually I'm having a bit of a problem with that... because I'm still a beginner, full of Respect and Appreciation to you, Dear @Luksus, who have developed and shared this X605 UT 20.04 port with all of us! Well, I'm trying to refrain from expressing all what I feel in a manner which I would really like, having in mind what you asked me some time ago ... so I say only: Thank you very much! I'm so happy

48.11). WORKAROUND LONG VERSION:
48.12). Some of the steps/actions seem to be not needed or optional but anyway I describe them for you here, if the short version would not work. I can also provide additional details, based on your questions.
48.13). I started with the X605L 4/64 which had the Android 9 installed.
48.14). I unlocked the bootloader.
48.15). I downloaded twrp-3.7.0_9-0-X605F.img from https://twrp.me/lenovo/lenovo_X605F.html and I installed it in FastBootMode.
48.16). Being in FastBootMode i pressed VolumeUp+VolumeDown+Power and at the same time i pressed enter, having "fastboot reboot" in terminal of my PC.
48.17). Tablet started to reboot and I was keeping pressed VolumeUp+VolumeDown+Power.
48.18). When the Lenovo Logo appeared, I released Power but I continued to keep pressed VolumeDown+VolumeUp until TWRP appeared.
48.19). Being in TWRP I selected Reboot > Bootloader, to come back into the FastBootMode.
48.20). Being in FastBootMode I flashed the boot.img and ubuntu.img (mentioned in "48.4).".
48.21). In TWRP I did Reboot > Power off.
48.22). Then I did the "48.5)." : "48.9).".

48.23). To be more precise, I should maybe add some additional steps in between, which would describe my UT16.04 installation, which I started being in Android 9 and which was performed using UBports-Installer (Ubuntu 20.04). TWRP was replaced by the Stock Recovery so I had to reinstall it in the FastBootMode. Moreover I was doing some backups and restores also. However, I didn't want to complicate the things, so I decided to skip these steps and to mention them only here because I suppose that they are not necessary as a part of the workaround.

Thank you in advance for your Feedback and kind regards~~ Piotrek~~pe3no.

pe3noATo2DOTpl

Dear @Luksus,

47). Reading your last message, should we worry about your current/future UT X605L Implementation/Porting Involvement ... ?

47.1). Well, the "funny" thing on my side is that right now I can finally/officially confirm that X605L 4/64 exist and I'm learning to install UT on it.

47.2). Well, yes... it's a shame... I'm not strong in the internet research... so sorry it took me so loooooooooong to find something... relatively easy to find.

47.3). Moreover, I must say that this was helpful to physically buy the 4/64 version of X605L:
https://psref.lenovo.com/Detail/Lenovo Tablets/Tab_M10?M=ZA490160SE
https://psref.lenovo.com/Detail/Lenovo Tablets/Tab_M10?M=ZA490158SE
https://psref.lenovo.com/Detail/Lenovo Tablets/Tab_M10?M=ZA490161PL
https://psref.lenovo.com/Detail/Lenovo Tablets/Tab_M10?M=ZA490162PL
https://psref.lenovo.com/Detail/Lenovo Tablets/Tab_M10?M=ZA490157RU
https://psref.lenovo.com/Detail/Lenovo Tablets/Tab_M10?M=ZA490159RU

47.4). Now I'm trying to improve my skills. The installation of 16.04 went smoothly, using the UBports-Installer.

47.5). I'm not sure if I'm doing it correctly but anyway today I tried to install your 20.04 and now I'm trying to boot it.
$ fastboot flash boot 20230922_012725_UT2004_X605_F_L_by_Luksus_1013489143_artifacts_zip___boot.img
$ fastboot flash system 20230922_012725_UT2004_X605_F_L_by_Luksus_1013489143_artifacts_zip___ubuntu.img

47.5). Dear @Luksus I'm happy for all that and I would be happy if you would continue your Project, which for the moment continues to be the only one UT 20.04 Implementation for a tablet with a SIM based internet, which for me is Great and I want to get involved in that !

Thank you and kind regards~~ Piotrek~~pe3no.

pe3noATo2DOTpl

Dear @Luksus,

45.1). I'm a crazy UT Ambassador, challenged by a group of young Android fans, so I continuously search the strongest possible hardware, to be able to present the best User Experience with our Great OS!

45.2). Initially, I was also able to find only the 2/3GB RAM versions, according to what the official specifications present but I was tireless in looking for the 4GB version of X605L, based on the information in this thread, that the X605 with 4GB or RAM exists.

45.3). As I was unhappy for my initial research results, so I extended its range and the first positive results I found outside of my country, i.e. here: https://mobileplanet.ua/ua/lenovo-tab-m10-10-1-lte-4-64gb-polar-whi-155443

45.4). I translated it in Chromium Browser and it confirms that X605L 4/64 actually exists:
Screenshot from 2023-12-10 23-00-36.png

45.5). However, as there seem to be no more companies who have any brand new items in stock, I'm trying to get in touch with private owners of X605L 4/64.

Kind regards~~ Piotrek~~pe3no.

......................................................................
Devices : MeizuPro5, Mx4 & BqAquarisE5.
Soon/hopefully ... X605L 4/64

pe3noATo2DOTpl

Dear @Luksus,

43.1). Sorry for my crazy behavior while expressing the emotions of happiness for the only UT 4G tablet, which you develop for all of us, and the inconvenience I caused... I'll try to keep it in mind.

43.2). I was asking about a separate X605 for the development because I actually can see two "X605L 4GB/64GB" items.

43.3). Thank you again for sharing the 2GB/3GB RAM concerns for X605. Now I'm sure I want to look for rather the 4/64 version, to have the TWRP and the OTA available.

Dear @Luksus , I wish you All the Best, thank you again and kind regards~~ Piotrek~~pe3no.

......................................................................
Devices : MeizuPro5, Mx4 & BqAquarisE5.
Soon/hopefully ... X605L 4/64

pe3noATo2DOTpl

Hello again my Dear Friends, @Josele13 and @beyolf and sorry for my late answer - I was massively looking for the 8GB miatoll and I hope to finalize the purchase soon

Dear @Josele13, thank you for having underlined the hardware differences of the 4G vs. the 5G devices

26). Now I'm hundred percent sure which smartphone to buy/avoid

27). Fortunately, I haven't bought the wrong phone. Thank you again for your Great Help

Dear @beyolf, thank you very much for your Warm Welcome - it's so kind of you I feel so happy and really honored to meet you, the UT Focal port for miatoll Contributor

28). Big Thanks also to you for having mentioned clearly that the 5G version is not supported by UT at the moment, in order to avoid it now.

29). My Enormous Thanks also for your wonderful helpful attitude which makes me and other potential UT Users to approach the Ubuntu Touch Adventure more easily

30). By the way, could you maybe share some YT links to the films where the UT @ Redmi Note 9 Pro are presented, please ? As an UT Ambassador I would have a Great Help/Tool to promote our Great Phone System, as I really want to share the best of what I/we have

31). Dear @beyolf I also wish you Luck - both with UT Development/Porting, as well as in your private life - God bless you!

I wish you All the Best, thank you in advance for your further feedback and kind regards~~ Piotrek~~pe3no.

......................................................................
Devices : MeizuPro5, Mx4 & BqAquarisE5.
Soon/hopefully ... RedmiNote9Pro