---

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

My Dear Friends, @Keneda, @Moem and @DPITTI

35). I would like to thank you for your Great Help and all the UBports Knowledge you were so kind to share with me

36). I managed to find the 5.1.3.0A Firmare for Meizu PRO 5 here: http://firmware.meizu.com/Firmware/Flyme/PRO_5/5.1.3.0/cn/20160130134300/50c60f50/update.zip

37). Therefore, I would like to mark this Topic as [SOLVED] - in the title or in another way but I don't know how to do it... would you give me a hint, please?

I wish you All the Best, thank you and kind regards~~ Piotrek~~pe3no.

Dear @tigerpro,

Which exactly Note 4 version should I buy to support you?

Is "SM-N910P" the only that you support ?
I can see that there are different models called N4: SM-N910S, SM-N910C, SM-N910H, SM-N910L, SM-N910K.

Kind regards and good luck, Piotr.

Dear @DPITTI, @Moem, @Josele13, @MrT10001 and @Lakotaubp, thank you very much for your Valuable Feedback

15). Dear UBports Friends, I'm sorry that I unintentionally caused such a discussion... I consider all of you and me as one big Ubuntu Touch Family and thank you once again for each your answer!!! I want to say that I value very highly the Great Help and the Efforts of All of you - Ubuntu Touch Developers, Porters and Users!!! You offer your Valuable Time and share your Expert Knowledge and this helps to make UT more and more popular

16). Dear @DPITTI, thank you for sharing your Tips related to the installation gotchas, in case of UT 20.04@XiaomiRedmiNote9Pro . Now I understand that I need to be aware of these constraints and I'm going to prepare better for the installation ...

17). Dear @Moem, yes I'm still unsure if there exists any UT20.04 compatible XiaomiRedmiNote9Pro which physically has 8GB of RAM, which I consider to be one of the Key Factors related to the good Performance of Ubuntu Touch. As an Ubuntu Touch Ambassador I would like to promote our OS, showing the best possible User Experience, and to achieve that, 8GB of RAM would be better than 6GB...

18). Therefore, I'm still trying to understand if the 8GB of RAM shown here: "https://devices.ubuntu-touch.io/device/excalibur" are correct or not?

19). The same question here: https://devices.ubuntu-touch.io/device/joyeuse/
Is the maximum 8GB RAM shown here meant as the physical amount? - are there really available such XiaomiRedmiNote9Pro Phones, compatible with Ubuntu Touch 20.04?

20). Dear @Josele13, sorry if I haven't explained what I meant clearly enough... Let me explain once again... I do not have any XiaomiRedmiNote9Pro Phone at the moment. I was about to buy one this Saturday, as I described above The Seller was presenting it as 8/128GB one. But when we checked in the Androind, it was showing "6+2 GB" of RAM and not simply "8GB of RAM", as I would expect. Further googling explained that Xiaomi is using a Technical/Marketing Trick that their XiaomiRedmiNote9Pro Phones have physical 6GB of RAM and additional +2GB or Virtual Ram is offered, but these +2 GB are Virtual/Fake, based on HDD space assigned for Android.

21). That's why I create this Thread, to understand if there exist any version of XiaomiRedmiNote9Pro that would have 8GB or RAM but I mean the physical amount, not any Virtual/Fake 6+2 GB of RAM...

22). Back to your concern, Dear @Josele13 - yes, I assumed that the XiaomiRedmiRedmiNote9Pro5G is probably NOT appropriate for Ubuntu Touch 20.04, unless any of you, my Dear UT Friends, would say something different (?) I mentioned that phone because the 5G variant of XiaomiRedmiNote9Pro seems to really have the physical 8GB of RAM and 256GB of HDD, which would also be nice to have in an Ubuntu Touch Phone...

23). Dear UBports Administrators/Moderators, would you be so kind to correct the "Redmin" to "Redmi" (or even to "Xiaomi Redmi"), in the title of my thread or to give me a hint how I could correct it myself, please? Sorry that I haven't noticed this when I created my post...

I wish you All the Best and thank you in advance for the clarification if the physical 8GB or RAM XiaomiRedmiNote9Pro models are available for UT 20.04 or the maximum is the 6GB - kind regards ~~ Piotrek~~pe3no.

Dear UBPorts Users / Developers,

I'm a father of two boys and they strongly claim to have smartphone(s) so:
1). I've been continously supporting UBPorts via Patreon since 2019-02-04 and would like to continue that way
2). I bought 3 different phones that support UBPorts.
3). I managed for the moment to install UBPorts UT 16.04 OTA-11 at Bq E5 HD.

... and now I have a question, how can I achieve the following :

4). I want to have an 8-digit pin to access the phone using the "simplified" (0-9) keyboard. AFAIK the 0-9 keyboard does not allow to insert pins composed of many digits, correct? On the other hand, there is the "full keyboard" where I could set an 8-digit password but it isn't comfortable as the "simplified" keyboard, which has only 0-9 fields.

5). At the same time I want to have the Ubuntu Store blocked/secured with a separate 26-character password which allows to install software, as when you install software at desktop, doing "sudo apt-get install xxxxx".

6). Finally (if I haven't forgotten something - please be patient), when my child creates/changes the PIN, I want to have the possibility to access the phone with my root password and change/reset the PIN.

Could you please tell me, if this is already available and how can I do it, if so?
If it's not available "out of the box", how could I do it / hack the phone to do so?
If hacking is not possilbe, would it be possible to ask the Developers for such a Feature, plese ?

Thank you in advance and kind regards, Peter.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.