<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[UBports Installer reports a successful install but Curtana seems empty now]]></title><description><![CDATA[<p dir="auto">Hi. Thanks for this amazing project. The world needs it.</p>
<p dir="auto">I have this Xiaomi Redmi Note 9S device, and I decided to install Ubuntu Touch on it.</p>
<p dir="auto">Many install attempts later, I can't even tell when things started looking messy. Little did I know but I was then playing with fire, and it's been two weeks without succeeding.</p>
<p dir="auto">The point is now I have apparently removed MIUI, but UT is not there. There are three booting options left:</p>
<p dir="auto"><strong>i)</strong>	an eternal loop, showing me the Redmi Powered by Android screen;<br />
<strong>ii)</strong>	Fastboot; or<br />
<strong>iii)</strong>	UBports Recovery.</p>
<p dir="auto">And that's it. I'm not making further progress from that point.</p>
<p dir="auto">Reproducing the problem goes like this: when Curtana boots to Fastboot, if I run the UBports installer 0.8.8-beta, it does not yike, reporting then a successful install. For a while, Curtana keeps showing the orange robot in a dark gray background, with the message:</p>
<p dir="auto"><em>Installing update<br />
Installing system update</em></p>
<p dir="auto">As the update procedure ends, the device loads the UBports Recovery screen, and the following message is shown at the botton:</p>
<p dir="auto"><em>Executing Ubuntu update script...<br />
Error installing Ubuntu update, exit code: 256<br />
Please go to Advanced -&gt; View recovery logs -&gt; /cache/ubuntuupdater.log</em></p>
<p dir="auto">I go to <em>View recovery logs</em> but it's empty.</p>
<p dir="auto">What about the logs left in ~/.cache/ubports/ubports-installer.log?</p>
<p dir="auto">The 94‑line output follows:</p>
<pre><code>{"level":"info","message":"Welcome to the UBports Installer version 0.8.8-beta!"}
{"level":"command","message":"exec: {\"cmd\":[\"heimdall\",\"detect\"],\"error\":{\"message\":\"Command failed: heimdall detect\\nERROR: Failed to detect compatible download-mode device.\",\"code\":1},\"stderr\":\"ERROR: Failed to detect compatible download-mode device.\"}"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"kill-server\"],\"stderr\":\"cannot connect to daemon at tcp:5037: Connection refused\"}"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"start-server\"],\"stderr\":\"* daemon not running; starting now at tcp:5037\\n* daemon started successfully\"}"}
{"level":"command","message":"exec: {\"cmd\":[\"heimdall\",\"detect\"],\"error\":{\"message\":\"Command failed: heimdall detect\\nERROR: Failed to detect compatible download-mode device.\",\"code\":1},\"stderr\":\"ERROR: Failed to detect compatible download-mode device.\"}"}
{"level":"command","message":"exec: {\"cmd\":[\"fastboot\",\"devices\"],\"stdout\":\"1ee98c46\\tfastboot\"}"}
{"level":"command","message":"exec: {\"cmd\":[\"fastboot\",\"devices\"],\"stdout\":\"1ee98c46\\tfastboot\"}"}
{"level":"command","message":"exec: {\"cmd\":[\"fastboot\",\"getvar\",\"product\"],\"stderr\":\"product: curtana\\nFinished. Total time: 0.000s\"}"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"wait-for-any-any\"],\"error\":{\"message\":\"Command failed: adb -P 5037 wait-for-any-any\",\"signal\":\"SIGTERM\",\"killed\":true}}"}
{"level":"info","message":"device detected: miatoll"}
{"level":"info","message":"Installing Ubuntu Touch on your Xiaomi Redmi Note 9 Pro/Pro Max/9S - Poco M2 Pro (miatoll)"}
{"level":"info","message":"configuring..."}
{"level":"info","message":"settings: {\"channel\":\"16.04/arm64/android9/stable\",\"wipe\":true,\"bootstrap\":true}"}
{"level":"verbose","message":"running step {\"actions\":[{\"core:download\":{\"group\":\"firmware\",\"files\":[{\"url\":\"https://github.com/ubuntu-touch-miatoll/ubuntu-touch-miatoll/releases/download/stable-installer-fix/recovery.img\",\"name\":\"recovery.img\",\"checksum\":{\"sum\":\"461259015c4bdd0e8fb36c7412454f9c8c9e8ae6b1413e79598bd1c6ec0095ea\",\"algorithm\":\"sha256\"}},{\"url\":\"https://github.com/ubuntu-touch-miatoll/ubuntu-touch-miatoll/releases/download/stable-installer-fix/dtbo.img\",\"name\":\"dtbo.img\",\"checksum\":{\"sum\":\"d408a9ecd7d2c6098cc06ec7dab03f69a532741f3626e6188d57b7557f421eb8\",\"algorithm\":\"sha256\"}}]}}],\"condition\":{\"var\":\"bootstrap\",\"value\":true}}"}
{"level":"verbose","message":"running core action download"}
{"level":"debug","message":"checking previously downloaded firmware files"}
{"level":"verbose","message":"running step {\"actions\":[{\"adb:reboot\":{\"to_state\":\"bootloader\"}}],\"fallback\":[{\"core:user_action\":{\"action\":\"bootloader\"}}],\"condition\":{\"var\":\"bootstrap\",\"value\":true}}"}
{"level":"verbose","message":"running adb action reboot"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"reboot\",\"bootloader\"],\"error\":{\"message\":\"Command failed: adb -P 5037 reboot bootloader\\nerror: no devices/emulators found\",\"code\":1},\"stderr\":\"error: no devices/emulators found\"}"}
{"level":"debug","message":"attempting to handle Error: no device"}
{"level":"verbose","message":"running core action user_action"}
{"level":"verbose","message":"running step {\"actions\":[{\"fastboot:wait\":null}]}"}
{"level":"verbose","message":"running fastboot action wait"}
{"level":"command","message":"exec: {\"cmd\":[\"fastboot\",\"devices\"],\"stdout\":\"1ee98c46\\tfastboot\"}"}
{"level":"verbose","message":"running step {\"actions\":[{\"fastboot:format\":{\"partition\":\"cache\"}}],\"condition\":{\"var\":\"bootstrap\",\"value\":true}}"}
{"level":"verbose","message":"running fastboot action format"}
{"level":"command","message":"exec: {\"cmd\":[\"fastboot\",\"format\",\"cache\"],\"error\":{\"message\":\"Command failed: fastboot format cache\\nFAILED (remote: 'Fastboot HAL not found')\\nfastboot: error: Command failed\",\"code\":1},\"stderr\":\"FAILED (remote: 'Fastboot HAL not found')\\nfastboot: error: Command failed\"}"}
{"level":"debug","message":"attempting to handle Error: formatting failed: Error: {\"error\":{\"code\":1,\"cmd\":\"fastboot format cache\"},\"stderr\":\"FAILED (remote: 'Fastboot HAL not found')\\nfastboot: error: Command failed\"}"}
{"level":"error","message":"Error: fastboot:format: Error: formatting failed: Error: {\"error\":{\"code\":1,\"cmd\":\"fastboot format cache\"},\"stderr\":\"FAILED (remote: 'Fastboot HAL not found')\\nfastboot: error: Command failed\"}\nstack trace: Error: formatting failed: Error: {\"error\":{\"code\":1,\"cmd\":\"fastboot format cache\"},\"stderr\":\"FAILED (remote: 'Fastboot HAL not found')\\nfastboot: error: Command failed\"}\n    at /opt/ubports-installer/resources/app.asar.unpacked/node_modules/promise-android-tools/lib/module.cjs:1200:15\n    at /opt/ubports-installer/resources/app.asar.unpacked/node_modules/cancelable-promise/dist/CancelablePromise.js:27:18\n    at runMicrotasks (&lt;anonymous&gt;)\n    at processTicksAndRejections (internal/process/task_queues.js:97:5)"}
{"level":"warn","message":"error ignored"}
{"level":"verbose","message":"running step {\"actions\":[{\"fastboot:format\":{\"partition\":\"userdata\",\"type\":\"ext4\"}}],\"condition\":{\"var\":\"wipe\",\"value\":true}}"}
{"level":"verbose","message":"running fastboot action format"}
{"level":"command","message":"exec: {\"cmd\":[\"fastboot\",\"format:ext4\",\"userdata\"],\"error\":{\"message\":\"Command failed: fastboot format:ext4 userdata\\nFAILED (remote: 'Fastboot HAL not found')\\nfastboot: error: Command failed\",\"code\":1},\"stderr\":\"FAILED (remote: 'Fastboot HAL not found')\\nfastboot: error: Command failed\"}"}
{"level":"debug","message":"attempting to handle Error: formatting failed: Error: {\"error\":{\"code\":1,\"cmd\":\"fastboot format:ext4 userdata\"},\"stderr\":\"FAILED (remote: 'Fastboot HAL not found')\\nfastboot: error: Command failed\"}"}
{"level":"error","message":"Error: fastboot:format: Error: formatting failed: Error: {\"error\":{\"code\":1,\"cmd\":\"fastboot format:ext4 userdata\"},\"stderr\":\"FAILED (remote: 'Fastboot HAL not found')\\nfastboot: error: Command failed\"}\nstack trace: Error: formatting failed: Error: {\"error\":{\"code\":1,\"cmd\":\"fastboot format:ext4 userdata\"},\"stderr\":\"FAILED (remote: 'Fastboot HAL not found')\\nfastboot: error: Command failed\"}\n    at /opt/ubports-installer/resources/app.asar.unpacked/node_modules/promise-android-tools/lib/module.cjs:1200:15\n    at /opt/ubports-installer/resources/app.asar.unpacked/node_modules/cancelable-promise/dist/CancelablePromise.js:27:18\n    at runMicrotasks (&lt;anonymous&gt;)\n    at processTicksAndRejections (internal/process/task_queues.js:97:5)"}
{"level":"warn","message":"error ignored"}
{"level":"verbose","message":"running step {\"actions\":[{\"fastboot:flash\":{\"partitions\":[{\"partition\":\"recovery\",\"file\":\"recovery.img\",\"group\":\"firmware\"},{\"partition\":\"dtbo\",\"file\":\"dtbo.img\",\"group\":\"firmware\"}]}}],\"condition\":{\"var\":\"bootstrap\",\"value\":true}}"}
{"level":"verbose","message":"running fastboot action flash"}
{"level":"command","message":"exec: {\"cmd\":[\"fastboot\",\"devices\"],\"stdout\":\"1ee98c46\\tfastboot\"}"}
{"level":"command","message":"exec: {\"cmd\":[\"fastboot\",\"devices\"],\"stdout\":\"1ee98c46\\tfastboot\"}"}
{"level":"command","message":"spawn:start: {\"cmd\":[\"fastboot\",\"flash\",\"recovery\",\"/home/mbarbado/.cache/ubports/miatoll/firmware/recovery.img\"]}"}
{"level":"command","message":"spawn:exit: {\"cmd\":[\"fastboot\",\"flash\",\"recovery\",\"/home/mbarbado/.cache/ubports/miatoll/firmware/recovery.img\"]}"}
{"level":"command","message":"spawn:start: {\"cmd\":[\"fastboot\",\"flash\",\"dtbo\",\"/home/mbarbado/.cache/ubports/miatoll/firmware/dtbo.img\"]}"}
{"level":"command","message":"spawn:exit: {\"cmd\":[\"fastboot\",\"flash\",\"dtbo\",\"/home/mbarbado/.cache/ubports/miatoll/firmware/dtbo.img\"]}"}
{"level":"verbose","message":"running step {\"actions\":[{\"fastboot:reboot_bootloader\":null}],\"fallback\":[{\"core:user_action\":{\"action\":\"recovery\"}}],\"condition\":{\"var\":\"bootstrap\",\"value\":true}}"}
{"level":"verbose","message":"running fastboot action reboot_bootloader"}
{"level":"command","message":"exec: {\"cmd\":[\"fastboot\",\"reboot-bootloader\"],\"stderr\":\"Rebooting into bootloader                          OKAY [  0.000s]\\nFinished. Total time: 0.050s\"}"}
{"level":"verbose","message":"running step {\"actions\":[{\"fastboot:boot\":{\"file\":\"recovery.img\",\"group\":\"firmware\"}}],\"fallback\":[{\"core:user_action\":{\"action\":\"recovery\"}}]}"}
{"level":"verbose","message":"running fastboot action boot"}
{"level":"command","message":"exec: {\"cmd\":[\"fastboot\",\"boot\",\"/home/mbarbado/.cache/ubports/miatoll/firmware/recovery.img\"],\"stderr\":\"&lt; waiting for any device &gt;\\nSending 'boot.img' (131072 KB)                     OKAY [  3.288s]\\nBooting                                            OKAY [  5.098s]\\nFinished. Total time: 8.486s\"}"}
{"level":"verbose","message":"running step {\"actions\":[{\"systemimage:install\":null}]}"}
{"level":"verbose","message":"running systemimage action install"}
{"level":"verbose","message":"running step {\"actions\":[{\"core:download\":{\"group\":\"Ubuntu Touch\",\"files\":[{\"url\":\"https://system-image.ubports.com//pool/ubports-227e5edffd603396044dea1dee123edb4b695539a26712b4815a33561fc6ea43.tar.xz\",\"checksum\":{\"sum\":\"4b309fd284a988e63eb150ce032d731c0371dec5520beb999bc0af7b2dd0df20\",\"algorithm\":\"sha256\"}},{\"url\":\"https://system-image.ubports.com//pool/ubports-227e5edffd603396044dea1dee123edb4b695539a26712b4815a33561fc6ea43.tar.xz.asc\"},{\"url\":\"https://system-image.ubports.com//pool/device-6afac5871a5c3b0c831b0371c978f7350251da0bc580e108b72f660c8dae992a.tar.xz\",\"checksum\":{\"sum\":\"709348eaadbe66cddb775fcddf860a697623cb7a9eb3c66040f72ef3fe4137a0\",\"algorithm\":\"sha256\"}},{\"url\":\"https://system-image.ubports.com//pool/device-6afac5871a5c3b0c831b0371c978f7350251da0bc580e108b72f660c8dae992a.tar.xz.asc\"},{\"url\":\"https://system-image.ubports.com//pool/boot-c0fa5e5e5b239a61e2c4c336234c4144bcf49bbb4b6bb819b8c7729cce7895a0.tar.xz\",\"checksum\":{\"sum\":\"7089aeb9907ad0d94f91b93a529a18942923b96fd79b002f78a08181fda4a6e0\",\"algorithm\":\"sha256\"}},{\"url\":\"https://system-image.ubports.com//pool/boot-c0fa5e5e5b239a61e2c4c336234c4144bcf49bbb4b6bb819b8c7729cce7895a0.tar.xz.asc\"},{\"url\":\"https://system-image.ubports.com//pool/keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz\",\"checksum\":{\"sum\":\"aa88fbf7d1aa6d9ab95a2a41cdf50b5b8da705a887cc34cde101c821ae7eb3d8\",\"algorithm\":\"sha256\"}},{\"url\":\"https://system-image.ubports.com//pool/keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz.asc\"},{\"url\":\"https://system-image.ubports.com//16.04/arm64/android9/stable/miatoll/version-3.tar.xz\",\"checksum\":{\"sum\":\"1fec0bdae3c78128a37f2a9fdcba9425d248c7859adff3bd6a999eaf453cb794\",\"algorithm\":\"sha256\"}},{\"url\":\"https://system-image.ubports.com//16.04/arm64/android9/stable/miatoll/version-3.tar.xz.asc\"},{\"url\":\"https://system-image.ubports.com/gpg/image-signing.tar.xz\"},{\"url\":\"https://system-image.ubports.com/gpg/image-signing.tar.xz.asc\"},{\"url\":\"https://system-image.ubports.com/gpg/image-master.tar.xz\"},{\"url\":\"https://system-image.ubports.com/gpg/image-master.tar.xz.asc\"}]}},{\"core:write\":{\"content\":\"format system\\nload_keyring image-master.tar.xz image-master.tar.xz.asc\\nload_keyring image-signing.tar.xz image-signing.tar.xz.asc\\nmount system\\nformat data\\nupdate ubports-227e5edffd603396044dea1dee123edb4b695539a26712b4815a33561fc6ea43.tar.xz ubports-227e5edffd603396044dea1dee123edb4b695539a26712b4815a33561fc6ea43.tar.xz.asc\\nupdate device-6afac5871a5c3b0c831b0371c978f7350251da0bc580e108b72f660c8dae992a.tar.xz device-6afac5871a5c3b0c831b0371c978f7350251da0bc580e108b72f660c8dae992a.tar.xz.asc\\nupdate boot-c0fa5e5e5b239a61e2c4c336234c4144bcf49bbb4b6bb819b8c7729cce7895a0.tar.xz boot-c0fa5e5e5b239a61e2c4c336234c4144bcf49bbb4b6bb819b8c7729cce7895a0.tar.xz.asc\\nupdate keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz.asc\\nupdate version-3.tar.xz version-3.tar.xz.asc\\nunmount system\",\"group\":\"Ubuntu Touch\",\"file\":\"ubuntu_command\"}},{\"adb:wait\":null},{\"adb:preparesystemimage\":null},{\"adb:push\":{\"group\":\"Ubuntu Touch\",\"files\":[\"ubports-227e5edffd603396044dea1dee123edb4b695539a26712b4815a33561fc6ea43.tar.xz\",\"ubports-227e5edffd603396044dea1dee123edb4b695539a26712b4815a33561fc6ea43.tar.xz.asc\",\"device-6afac5871a5c3b0c831b0371c978f7350251da0bc580e108b72f660c8dae992a.tar.xz\",\"device-6afac5871a5c3b0c831b0371c978f7350251da0bc580e108b72f660c8dae992a.tar.xz.asc\",\"boot-c0fa5e5e5b239a61e2c4c336234c4144bcf49bbb4b6bb819b8c7729cce7895a0.tar.xz\",\"boot-c0fa5e5e5b239a61e2c4c336234c4144bcf49bbb4b6bb819b8c7729cce7895a0.tar.xz.asc\",\"keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz\",\"keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz.asc\",\"version-3.tar.xz\",\"version-3.
tar.xz.asc\",\"image-signing.tar.xz\",\"image-signing.tar.xz.asc\",\"image-master.tar.xz\",\"image-master.tar.xz.asc\",\"ubuntu_command\"],\"dest\":\"/cache/recovery/\"}}]}"}
{"level":"verbose","message":"running core action download"}
{"level":"debug","message":"checking previously downloaded Ubuntu Touch files"}
{"level":"info","message":"Downloading 9 files"}
{"level":"debug","message":"downloading Ubuntu Touch files"}
{"level":"info","message":"Downloaded file 1 of 9"}
{"level":"info","message":"Downloaded file 2 of 9"}
{"level":"info","message":"Downloaded file 3 of 9"}
{"level":"info","message":"Downloaded file 4 of 9"}
{"level":"info","message":"Downloaded file 5 of 9"}
{"level":"info","message":"Downloaded file 6 of 9"}
{"level":"info","message":"Downloaded file 7 of 9"}
{"level":"info","message":"Downloaded file 8 of 9"}
{"level":"info","message":"Downloaded file 9 of 9"}
{"level":"verbose","message":"running core action write"}
{"level":"verbose","message":"running adb action wait"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"wait-for-any-any\"]}"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"get-state\"],\"stdout\":\"recovery\"}"}
{"level":"verbose","message":"running adb action preparesystemimage"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"shell\",\"mount -a\"],\"error\":{\"message\":\"Command failed: adb -P 5037 shell mount -a\\nmount: '/dev/block/dm-1'-&gt;'/product': Invalid argument\\nmount: '/dev/block/dm-2'-&gt;'/vendor': Invalid argument\\nmount: '/dev/block/bootdevice/by-name/boot'-&gt;'/boot': No such file or directory\\nmount: '/dev/block/bootdevice/by-name/modem'-&gt;'/vendor/firmware_mnt': No such file or directory\\nmount: '/dev/block/bootdevice/by-name/dsp'-&gt;'/vendor/dsp': No such file or directory\\nmount: '/dev/block/bootdevice/by-name/persist'-&gt;'/mnt/vendor/persist': No such file or directory\\nmount: '/dev/block/bootdevice/by-name/bluetooth'-&gt;'/vendor/bt_firmware': No such file or directory\\nmount: '/dev/block/bootdevice/by-name/misc'-&gt;'/misc': No such file or directory\",\"code\":1},\"stderr\":\"mount: '/dev/block/dm-1'-&gt;'/product': Invalid argument\\nmount: '/dev/block/dm-2'-&gt;'/vendor': Invalid argument\\nmount: '/dev/block/bootdevice/by-name/boot'-&gt;'/boot': No such file or directory\\nmount: '/dev/block/bootdevice/by-name/modem'-&gt;'/vendor/firmware_mnt': No such file or directory\\nmount: '/dev/block/bootdevice/by-name/dsp'-&gt;'/vendor/dsp': No such file or directory\\nmount: '/dev/block/bootdevice/by-name/persist'-&gt;'/mnt/vendor/persist': No such file or directory\\nmount: '/dev/block/bootdevice/by-name/bluetooth'-&gt;'/vendor/bt_firmware': No such file or directory\\nmount: '/dev/block/bootdevice/by-name/misc'-&gt;'/misc': No such file or directory\"}"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"shell\",\"cat /etc/recovery.fstab\"],\"stdout\":\"# Copyright (c) 2018-2019, The Linux Foundation. All rights reserved.\\n#\\n# Redistribution and use in source and binary forms, with or without\\n# modification, are permitted provided that the following conditions are\\n# met:\\n#     * Redistributions of source code must retain the above copyright\\n#       notice, this list of conditions and the following disclaimer.\\n#     * Redistributions in binary form must reproduce the above\\n#       copyright notice, this list of conditions and the following\\n#       disclaimer in the documentation and/or other materials provided\\n#       with the distribution.\\n#     * Neither the name of The Linux Foundation nor the names of its\\n#       contributors may be used to endorse or promote products derived\\n#       from this software without specific prior written permission.\\n#\\n# THIS SOFTWARE IS PROVIDED \\\"AS IS\\\" AND ANY EXPRESS OR IMPLIED\\n# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF\\n# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT\\n# ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS\\n# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR\\n# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF\\n# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR\\n# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,\\n# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE\\n# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN\\n# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.\\n\\n# Android fstab file.\\n# The filesystem that contains the filesystem checker binary (typically /system) cannot\\n# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK\\n\\n#TODO: Add 'check' as fs_mgr_flags with data partition.\\n# Currently we dont have e2fsck compiled. So fs check would failed.\\n\\n#&lt;src&gt;                                                 &lt;mnt_point&gt;               &lt;type&gt;  &lt;mnt_flags and options&gt;                            &lt;fs_mgr_flags&gt;\\nsystem                                                  /system_root             ext4    ro,barrier=1,discard                                 wait,logical,first_stage_mount,avb=vbmeta_system,avb_keys=/avb/q-gsi.avbpubkey:/avb/r-gsi.avbpubkey:/avb/s-gsi.avbpubkey\\nproduct                                                 /product                 ext4    ro,barrier=1,discard                                 wait,logical,first_stage_mount,avb=vbmeta_system\\nvendor                                                  /vendor                  ext4    ro,barrier=1,discard                                 wait,logical,first_stage_mount,avb\\n/dev/block/bootdevice/by-name/cache                     /cache                   ext4    nosuid,noatime,nodev,barrier=1                       wait\\n/dev/block/bootdevice/by-name/boot                      /boot                    emmc    defaults                                             defaults\\n/dev/block/by-name/metadata                             /metadata                ext4    noatime,nosuid,nodev,discard                         wait,formattable,wrappedkey,first_stage_mount\\n# Add fs_mgr flag - sysfs_path=/sys/devices/platform/soc/xxxx.[ufshc|sdhci] to userdata entry, based on UFS|eMMC device.\\n/dev/block/bootdevice/by-name/userdata                  /data                    ext4    noatime,nosuid,nodev,nodiscard,reserve_root=32768,resgid=1065,fsync_mode=nobarrier     latemount,wait,check,formattable,fileencryption=ice,wrappedkey,quota,reservedsize=128M,checkpoint=fs\\n/devices/platform/soc/8804000.sdhci/mmc_host*           /storage/sdcard1         vfat    nosuid,nodev                                         wait,voldmanaged=sdcard1:auto,encryptable=footer\\n/devices/platform/soc/1da4000.ufshc_card/host*          /storage/sdcard1         vfat    nosuid,nodev                                      
   wait,voldmanaged=sdcard1:auto,encryptable=footer\\n/dev/block/bootdevice/by-name/modem                     /vendor/firmware_mnt     vfat    ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait\\n/dev/block/bootdevice/by-name/dsp                       /vendor/dsp              ext4    ro,nosuid,nodev,barrier=1                            wait\\n/dev/block/bootdevice/by-name/persist                   /mnt/vendor/persist      ext4    noatime,nosuid,nodev,barrier=1                       wait\\n/dev/block/bootdevice/by-name/bluetooth                 /vendor/bt_firmware      vfat    ro,shortname=lower,uid=1002,gid=3002,dmask=227,fmask=337,context=u:object_r:bt_firmware_file:s0 wait\\n/devices/platform/soc/a600000.ssusb/a600000.dwc3/xhci-hcd.0.auto*     /storage/usbotg    vfat    nosuid,nodev         wait,voldmanaged=usbotg:auto\\n# Need to have this entry in here even though the mount point itself is no longer needed.\\n# The update_engine code looks for this entry in order to determine the boot device address\\n# and fails if it does not find it.\\n/dev/block/bootdevice/by-name/misc                      /misc              emmc    defaults                                             defaults\\n/dev/block/zram0                                        none               swap    defaults                                             zramsize=1073741824\"}"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"shell\",\"umount /cache\"]}"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"shell\",\"make_ext4fs /dev/block/bootdevice/by-name/cache\"],\"error\":{\"message\":\"Command failed: adb -P 5037 shell make_ext4fs /dev/block/bootdevice/by-name/cache\\n/system/bin/sh: make_ext4fs: inaccessible or not found\",\"code\":127},\"stderr\":\"/system/bin/sh: make_ext4fs: inaccessible or not found\"}"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"shell\",\"rm -rf /cache/*\"]}"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"shell\",\"mkdir -p /cache/recovery\"]}"}
{"level":"debug","message":"adb created /cache/recovery directory"}
{"level":"verbose","message":"running adb action push"}
{"level":"command","message":"spawn:start: {\"cmd\":[\"adb\",\"-P\",5037,\"push\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/ubports-227e5edffd603396044dea1dee123edb4b695539a26712b4815a33561fc6ea43.tar.xz\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/ubports-227e5edffd603396044dea1dee123edb4b695539a26712b4815a33561fc6ea43.tar.xz.asc\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/device-6afac5871a5c3b0c831b0371c978f7350251da0bc580e108b72f660c8dae992a.tar.xz\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/device-6afac5871a5c3b0c831b0371c978f7350251da0bc580e108b72f660c8dae992a.tar.xz.asc\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/boot-c0fa5e5e5b239a61e2c4c336234c4144bcf49bbb4b6bb819b8c7729cce7895a0.tar.xz\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/boot-c0fa5e5e5b239a61e2c4c336234c4144bcf49bbb4b6bb819b8c7729cce7895a0.tar.xz.asc\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz.asc\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/version-3.tar.xz\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/version-3.tar.xz.asc\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/image-signing.tar.xz\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/image-signing.tar.xz.asc\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/image-master.tar.xz\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/image-master.tar.xz.asc\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/ubuntu_command\",\"/cache/recovery/\"]}"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"shell\",\"mount\"],\"stdout\":\"rootfs on / type rootfs (rw,size=2213924k,nr_inodes=553481)\\ntmpfs on /dev type tmpfs (rw,nosuid,relatime,size=2849256k,nr_inodes=712314,mode=755)\\ndevpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)\\nproc on /proc type proc (rw,relatime,gid=3009,hidepid=2)\\nsysfs on /sys type sysfs (rw,relatime)\\ntmpfs on /mnt type tmpfs (rw,nosuid,nodev,noexec,relatime,size=2849256k,nr_inodes=712314,mode=755,gid=1000)\\ntmpfs on /apex type tmpfs (rw,nosuid,nodev,noexec,relatime,size=2849256k,nr_inodes=712314,mode=755)\\nnone on /acct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct)\\ntmpfs on /tmp type tmpfs (rw,relatime,size=2849256k,nr_inodes=712314)\\ntmpfs on /storage type tmpfs (rw,relatime,size=2849256k,nr_inodes=712314,mode=050,gid=1028)\\npstore on /sys/fs/pstore type pstore (rw,relatime)\\nnone on /config type configfs (rw,relatime)\\nadb on /dev/usb-ffs/adb type functionfs (rw,relatime)\\nfastboot on /dev/usb-ffs/fastboot type functionfs (rw,relatime)\\n/dev/block/sda18 on /cache type ext4 (rw,relatime,resgid=1065,errors=remount-ro,stripe=2,data=ordered)\\n/dev/block/dm-0 on /system_root type ext4 (rw,relatime,discard,data=ordered)\\n/dev/block/sda12 on /metadata type ext4 (rw,relatime,discard,data=ordered)\\n/dev/block/sda18 on /data type ext4 (rw,relatime,resgid=1065,errors=remount-ro,stripe=2,data=ordered)\"}"}
{"level":"debug","message":"ext4 data partition ok"}
{"level":"command","message":"spawn:exit: {\"cmd\":[\"adb\",\"-P\",5037,\"push\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/ubports-227e5edffd603396044dea1dee123edb4b695539a26712b4815a33561fc6ea43.tar.xz\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/ubports-227e5edffd603396044dea1dee123edb4b695539a26712b4815a33561fc6ea43.tar.xz.asc\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/device-6afac5871a5c3b0c831b0371c978f7350251da0bc580e108b72f660c8dae992a.tar.xz\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/device-6afac5871a5c3b0c831b0371c978f7350251da0bc580e108b72f660c8dae992a.tar.xz.asc\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/boot-c0fa5e5e5b239a61e2c4c336234c4144bcf49bbb4b6bb819b8c7729cce7895a0.tar.xz\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/boot-c0fa5e5e5b239a61e2c4c336234c4144bcf49bbb4b6bb819b8c7729cce7895a0.tar.xz.asc\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/keyring-28992f008be20d562ea06745f563d3abe00b08da1b16e5b92e448e2d4ba21e9f.tar.xz.asc\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/version-3.tar.xz\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/version-3.tar.xz.asc\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/image-signing.tar.xz\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/image-signing.tar.xz.asc\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/image-master.tar.xz\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/image-master.tar.xz.asc\",\"/home/mbarbado/.cache/ubports/miatoll/Ubuntu Touch/ubuntu_command\",\"/cache/recovery/\"]}"}
{"level":"verbose","message":"running step {\"actions\":[{\"adb:reboot\":{\"to_state\":\"recovery\"}}],\"fallback\":[{\"core:user_action\":{\"action\":\"recovery\"}}]}"}
{"level":"verbose","message":"running adb action reboot"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"reboot\",\"recovery\"]}"}
{"level":"verbose","message":"running step {\"actions\":[{\"core:end\":null}]}"}
{"level":"verbose","message":"running core action end"}
{"level":"info","message":"All done! Your device will now reboot and complete the installation. Enjoy exploring Ubuntu Touch!"}
{"level":"info","message":"Good bye!"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"kill-server\"]}"}
</code></pre>
<p dir="auto">If I reboot Curtana, the same Redmi screen loop is there again, so I'm not sure how to proceed now.</p>
<p dir="auto">Help?</p>
]]></description><link>https://forums.ubports.com/topic/7574/ubports-installer-reports-a-successful-install-but-curtana-seems-empty-now</link><generator>RSS for Node</generator><lastBuildDate>Mon, 08 Jun 2026 21:17:11 GMT</lastBuildDate><atom:link href="https://forums.ubports.com/topic/7574.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 16 Mar 2022 16:52:22 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to UBports Installer reports a successful install but Curtana seems empty now on Mon, 18 Apr 2022 06:51:57 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/keneda" aria-label="Profile: keneda">@<bdi>keneda</bdi></a> It's in the devices subforum so it's easy to guess he's talking about one of his phone :))</p>
<p dir="auto">There are 5 phones (4 codenames)</p>
<p dir="auto">joyeuse, curtana, excalibur, gram.</p>
<p dir="auto"><img src="https://forums.ubports.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=aee68f5cf05" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:23px;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
]]></description><link>https://forums.ubports.com/post/63766</link><guid isPermaLink="true">https://forums.ubports.com/post/63766</guid><dc:creator><![CDATA[nitanmarcel]]></dc:creator><pubDate>Mon, 18 Apr 2022 06:51:57 GMT</pubDate></item><item><title><![CDATA[Reply to UBports Installer reports a successful install but Curtana seems empty now on Sun, 17 Apr 2022 23:51:37 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/mbjunior" aria-label="Profile: mbjunior">@<bdi>mbjunior</bdi></a> a<br />
Ah ok it's its codename <img src="https://forums.ubports.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f605.png?v=aee68f5cf05" class="not-responsive emoji emoji-android emoji--sweat_smile" style="height:23px;width:auto;vertical-align:middle" title="😅" alt="😅" /><br />
Thanks.</p>
]]></description><link>https://forums.ubports.com/post/63765</link><guid isPermaLink="true">https://forums.ubports.com/post/63765</guid><dc:creator><![CDATA[Keneda]]></dc:creator><pubDate>Sun, 17 Apr 2022 23:51:37 GMT</pubDate></item><item><title><![CDATA[Reply to UBports Installer reports a successful install but Curtana seems empty now on Sun, 17 Apr 2022 22:34:22 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/keneda" aria-label="Profile: keneda">@<bdi>keneda</bdi></a> Oh hi. Thanks.</p>
<p dir="auto">Curtana is another name for Redmi Note 9S.</p>
<p dir="auto">It's easier to search for ROMs and stuff by using the <em>curtana</em> keyword. As in googling with:</p>
<p dir="auto">inurl:curtana rom</p>
]]></description><link>https://forums.ubports.com/post/63764</link><guid isPermaLink="true">https://forums.ubports.com/post/63764</guid><dc:creator><![CDATA[mbjunior]]></dc:creator><pubDate>Sun, 17 Apr 2022 22:34:22 GMT</pubDate></item><item><title><![CDATA[Reply to UBports Installer reports a successful install but Curtana seems empty now on Sun, 17 Apr 2022 20:36:01 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/mbjunior" aria-label="Profile: mbjunior">@<bdi>mbjunior</bdi></a><br />
<a href="https://forums.ubports.com/topic/6311/how-to-ask-a-question-and-then-mark-it-as-solved">https://forums.ubports.com/topic/6311/how-to-ask-a-question-and-then-mark-it-as-solved</a></p>
<p dir="auto">PS : what is "curtana" ?</p>
]]></description><link>https://forums.ubports.com/post/63760</link><guid isPermaLink="true">https://forums.ubports.com/post/63760</guid><dc:creator><![CDATA[Keneda]]></dc:creator><pubDate>Sun, 17 Apr 2022 20:36:01 GMT</pubDate></item><item><title><![CDATA[Reply to UBports Installer reports a successful install but Curtana seems empty now on Sun, 17 Apr 2022 19:33:33 GMT]]></title><description><![CDATA[<blockquote>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/mbjunior" aria-label="Profile: mbjunior">@<bdi>mbjunior</bdi></a> if miui starts and it says you have to confirm your phone number or something similar then you're good to go. Reboot in fastboot and run the installer.</p>
</blockquote>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nitanmarcel" aria-label="Profile: nitanmarcel">@<bdi>nitanmarcel</bdi></a> You're right, yay! <img src="https://forums.ubports.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f938.png?v=aee68f5cf05" class="not-responsive emoji emoji-android emoji--person_doing_cartwheel" style="height:23px;width:auto;vertical-align:middle" title=":person_doing_cartwheel:" alt="🤸" /></p>
<p dir="auto">At that point, both the tough partition and the block problems can be overcome by the installer.</p>
<p dir="auto">Thanks, people. I guess it is safe to consider this one as solved now! <img src="https://forums.ubports.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f60a.png?v=aee68f5cf05" class="not-responsive emoji emoji-android emoji--blush" style="height:23px;width:auto;vertical-align:middle" title=":blush:" alt="😊" /></p>
]]></description><link>https://forums.ubports.com/post/63757</link><guid isPermaLink="true">https://forums.ubports.com/post/63757</guid><dc:creator><![CDATA[mbjunior]]></dc:creator><pubDate>Sun, 17 Apr 2022 19:33:33 GMT</pubDate></item><item><title><![CDATA[Reply to UBports Installer reports a successful install but Curtana seems empty now on Thu, 14 Apr 2022 06:27:39 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/mbjunior" aria-label="Profile: mbjunior">@<bdi>mbjunior</bdi></a> if miui starts and it says you have to confirm your phone number or something similar then you're good to go. Reboot in fastboot and run the installer.</p>
<p dir="auto">Also you can find fastboot flashable ROMs here <a href="https://xiaomifirmwareupdater.com/archive/miui/curtana/" target="_blank" rel="noopener noreferrer nofollow ugc">https://xiaomifirmwareupdater.com/archive/miui/curtana/</a></p>
<p dir="auto">Just run flash_all.sh or flash_all.bash depending on your OS (Windows or Unix)</p>
]]></description><link>https://forums.ubports.com/post/63661</link><guid isPermaLink="true">https://forums.ubports.com/post/63661</guid><dc:creator><![CDATA[nitanmarcel]]></dc:creator><pubDate>Thu, 14 Apr 2022 06:27:39 GMT</pubDate></item><item><title><![CDATA[Reply to UBports Installer reports a successful install but Curtana seems empty now on Tue, 12 Apr 2022 03:26:44 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/mbjunior" aria-label="Profile: mbjunior">@<bdi>mbjunior</bdi></a> Xiaomi have put security in place to make life very difficult to flash through fastboot to install the stock (correct) ROM. You need a windows PC and the MiFlash tool to do the job properly. DO NOT relock the bootloader as it has a high chance of bricking the device.</p>
]]></description><link>https://forums.ubports.com/post/63611</link><guid isPermaLink="true">https://forums.ubports.com/post/63611</guid><dc:creator><![CDATA[MrT10001]]></dc:creator><pubDate>Tue, 12 Apr 2022 03:26:44 GMT</pubDate></item><item><title><![CDATA[Reply to UBports Installer reports a successful install but Curtana seems empty now on Tue, 12 Apr 2022 02:12:35 GMT]]></title><description><![CDATA[<p dir="auto">Hi, <a class="plugin-mentions-user plugin-mentions-a" href="/user/tchan" aria-label="Profile: tchan">@<bdi>tchan</bdi></a> and <a class="plugin-mentions-user plugin-mentions-a" href="/user/nitanmarcel" aria-label="Profile: nitanmarcel">@<bdi>nitanmarcel</bdi></a>. Thanks for your time helping me in this adventure. I'm afraid it's not over yet, though <img src="https://forums.ubports.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f616.png?v=aee68f5cf05" class="not-responsive emoji emoji-android emoji--confounded" style="height:23px;width:auto;vertical-align:middle" title=":confounded:" alt="😖" /></p>
<p dir="auto">Okay, some progress was achieved. I have managed to obtain proper Android 10-based images in &lt;<a href="http://miui.com" target="_blank" rel="noopener noreferrer nofollow ugc">miui.com</a>&gt;. The partitions I have flashed are:</p>
<ul>
<li><em>boot</em></li>
<li><em>cache</em></li>
<li><em>cust</em></li>
<li><em>dtbo</em></li>
<li><em>ffu</em></li>
<li><em>metadata</em></li>
<li><em>misc</em></li>
<li><em>recovery</em></li>
<li><em>super</em></li>
<li><em>userdata</em></li>
<li><em>vbmeta</em></li>
<li><em>vbmeta_system</em></li>
</ul>
<p dir="auto">There is this one tough partition I cannot flash, no matter what. It's called <em>persist</em>. Yes, I have tried to flash it after a <em>fastboot flashing unlock_critical</em> command, but it fails with the following message:</p>
<pre><code># fastboot flash persist ./persist.img
target reported max download size of 805306368 bytes
sending 'persist' (32768 KB)...
OKAY [  0.773s]
writing 'persist'...
FAILED (remote: Flashing is not allowed for Controlled Partitions)
finished. total time: 0.774s
</code></pre>
<p dir="auto">So, now MIUI boots but it tells me the device is locked because the phone belongs to, well, me. As Curtana is not connected to the Internet, I guess it's a safe bet to say it retained my information. Maybe in the <em>persist</em> partition?</p>
<p dir="auto">I still have access to Fastboot via the volume down button, but now, in the place of UBports Recovery, volume up leads to a <em>Main Menu Redmi-Recovery 3.0</em> interface. There are three buttons in such interface:</p>
<ol>
<li>Reboot</li>
<li>Wipe Data</li>
<li>Connect with MIAssistant</li>
</ol>
<p dir="auto">Well, when I choose option 2, a wiping process allegedly takes place in a successful manner. But then again, in rebooting the device, the lock confronts me, showing that the wiping process did not wipe some data.</p>
<p dir="auto">I totally understand at that point giving Curtana my Xiaomi credentials would probably help, but that in my opinion is the whole point why a marvelous project like Ubuntu Touch matters: controlling my device, or die trying <img src="https://forums.ubports.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f635.png?v=aee68f5cf05" class="not-responsive emoji emoji-android emoji--dizzy_face" style="height:23px;width:auto;vertical-align:middle" title=":dizzy_face:" alt="😵" /></p>
<p dir="auto">CLI fastboot commands are not working, so I am considering <em>dd</em> but decided to talk to you first.</p>
<p dir="auto">Thus, once more, I ask you gentlemen for guidance. What can I do at this point, without notifying Xiaomi? Do you think <em>dd</em> may help in this situation?</p>
]]></description><link>https://forums.ubports.com/post/63609</link><guid isPermaLink="true">https://forums.ubports.com/post/63609</guid><dc:creator><![CDATA[mbjunior]]></dc:creator><pubDate>Tue, 12 Apr 2022 02:12:35 GMT</pubDate></item><item><title><![CDATA[Reply to UBports Installer reports a successful install but Curtana seems empty now on Tue, 29 Mar 2022 12:05:15 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/mbjunior" aria-label="Profile: mbjunior">@<bdi>mbjunior</bdi></a>  sorry for the late reply. I'm more active in the <a href="https://t.me/ut_miatoll" target="_blank" rel="noopener noreferrer nofollow ugc">https://t.me/ut_miatoll</a> group on telegram.</p>
<p dir="auto">Make sure you had the stock Android 10 ROM for your phone flashed with fastboot and also that you selected the wipe data option in the installer.</p>
<p dir="auto">There are some cases I noticed that the OS refuses to boot if a custom ROM has been flashed before reflashing the stock ROM. The reason is unknown but it can be fixed by flashing the recovery ROM over the fastboot one. But I noticed this happening just one time on my phone.</p>
<p dir="auto">Check again the first steps then in the last resort the last ones.</p>
<p dir="auto">Thanks.</p>
]]></description><link>https://forums.ubports.com/post/63387</link><guid isPermaLink="true">https://forums.ubports.com/post/63387</guid><dc:creator><![CDATA[nitanmarcel]]></dc:creator><pubDate>Tue, 29 Mar 2022 12:05:15 GMT</pubDate></item><item><title><![CDATA[Reply to UBports Installer reports a successful install but Curtana seems empty now on Wed, 23 Mar 2022 05:35:41 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/mbjunior" aria-label="Profile: mbjunior">@<bdi>mbjunior</bdi></a></p>
<p dir="auto">Hi,<br />
If the Hardware abstraction layer (Halium)was the problems , the android version should be the problems.<br />
I think it's better to flash a Android 10 again to be sure . When it's installed start it to enable devlopper mode and adb and launch the installer ( bootloader should be still unlocked I guess ).<br />
Be sure to follow the instructions for your device.</p>
<p dir="auto">Good luick!</p>
]]></description><link>https://forums.ubports.com/post/63106</link><guid isPermaLink="true">https://forums.ubports.com/post/63106</guid><dc:creator><![CDATA[tchan]]></dc:creator><pubDate>Wed, 23 Mar 2022 05:35:41 GMT</pubDate></item><item><title><![CDATA[Reply to UBports Installer reports a successful install but Curtana seems empty now on Tue, 22 Mar 2022 20:08:53 GMT]]></title><description><![CDATA[<p dir="auto">Hi, <a class="plugin-mentions-user plugin-mentions-a" href="/user/tchan" aria-label="Profile: tchan">@<bdi>tchan</bdi></a>. Thank you for replying, and sorry for this delayed answer. Even though I've set the Watching icon, no message was received (nothing in my spam folder either), and I have only seen your message now.</p>
<blockquote>
<p dir="auto">Also sometime it's nice to tried differents cables and usb port...</p>
</blockquote>
<p dir="auto">Well, yes. I have tried some variations of USB ports and cables. Sadly, results are pretty much the same as the ones I previously posted.</p>
<blockquote>
<p dir="auto">I'm not an expert of install, but did you have the right android version before started the installer?</p>
</blockquote>
<p dir="auto">I don't know. That was some time ago.</p>
<p dir="auto">As I read somewhere, the proper version is supposed to be Android 10.</p>
<p dir="auto">As a matter of fact, some fastboot and adb commands I try end up complaining about a missing hardware abstraction layer (HAL). And, as I now understand, that would only be available on my system partition, if Android 10 was there.</p>
<p dir="auto">All this making sense, do you think I should try to install Android 10 somehow first, and then UT, or is there any other way to get what the HAL would provide me with?</p>
]]></description><link>https://forums.ubports.com/post/63103</link><guid isPermaLink="true">https://forums.ubports.com/post/63103</guid><dc:creator><![CDATA[mbjunior]]></dc:creator><pubDate>Tue, 22 Mar 2022 20:08:53 GMT</pubDate></item><item><title><![CDATA[Reply to UBports Installer reports a successful install but Curtana seems empty now on Fri, 18 Mar 2022 15:59:44 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/mbjunior" aria-label="Profile: mbjunior">@<bdi>mbjunior</bdi></a><br />
Hi,<br />
I'm not an expert of install, but did you have the right android version before started the installer?<br />
Also sometime it's nice to tried differents cables and usb port...</p>
<p dir="auto">Good luck!</p>
]]></description><link>https://forums.ubports.com/post/62962</link><guid isPermaLink="true">https://forums.ubports.com/post/62962</guid><dc:creator><![CDATA[tchan]]></dc:creator><pubDate>Fri, 18 Mar 2022 15:59:44 GMT</pubDate></item></channel></rss>