@MrT10001 The sign of unlocked is significant because we can see an unlock icon on top of the screen every time when we restart our phone. And we can also see whether the phone is locked or not in developer mode. So I can confirm my phone is unlocked.
I also try two different USB cables and also try the front and back ports on my PC. It didn't work at all
.
And I also saw the same issue on GitHub such as https://github.com/ubports/ubports-installer/issues/3968
@MrT10001 the problem is still same. and the log is also same as before.
@MrT10001 No, if this version is available, I can try it tonight.
@MrT10001 Hi, I have left it for more than two hours. Then nothing changed.
@MrT10001 of course unlocked
the running log is :
<!-- Please do not edit any of the following, you can add a description further down. -->
UBports Installer 0.11.2 (exe)
Microsoft Windows 11 专业版 10.0.26100 Windows 10.0.26100 x64 26100 0.0 NodeJS v20.18.3Ubuntu Touch{"bootstrap":true,"wipe":true,"channel":"20.04/arm64/android9plus/devel"}
info: Welcome to the UBports Installer version 0.11.2!
verbose: Running on: Microsoft Windows 11 专业版 10.0.26100 Windows 10.0.26100 x64 26100 0.0 NodeJS v20.18.3
verbose: Versions: {"node":"20.18.3","acorn":"8.14.0","ada":"2.9.2","ares":"1.34.4","base64":"0.5.2","brotli":"1.0.9","cjs_module_lexer":"1.4.1","cldr":"44.1","icu":"74.2","llhttp":"8.1.2","modules":"130","napi":"9","nghttp2":"1.61.0","openssl":"0.0.0","simdutf":"5.6.4","tz":"2024a","undici":"6.21.1","unicode":"15.1","uv":"1.46.0","uvwasi":"0.0.21","v8":"13.0.245.25-electron.0","zlib":"1.3.0.1-motley","electron":"33.4.11","chrome":"130.0.6723.191"}
debug: Setting up application menu
verbose: Reading config file: undefined
command: exec: {"cmd":["heimdall","detect"],"error":{"message":"Command failed: C:\\Users\\PANXIA~1\\AppData\\Local\\Temp\\2zH15Mn5JzNTJumOuB378BJAJzP\\resources\\app.asar.unpacked\\node_modules\\android-tools-bin\\dist\\win32\\x86\\heimdall.exe detect\nERROR: Failed to detect compatible download-mode device.","code":1},"stderr":"ERROR: Failed to detect compatible download-mode device."}
command: exec: {"cmd":["adb","-P",5037,"kill-server"],"stderr":"cannot connect to daemon at tcp:5037: cannot connect to 127.0.0.1:5037: 由于目标计算机积极拒绝，无法连接。 (10061)"}
command: exec: {"cmd":["adb","-P",5037,"start-server"],"stderr":"* daemon not running; starting now at tcp:5037\r\n* daemon started successfully"}
command: exec: {"cmd":["adb","-P",5037,"wait-for-any-any"]}
command: exec: {"cmd":["fastboot","devices"]}
command: exec: {"cmd":["heimdall","detect"],"error":{"message":"Command failed: C:\\Users\\PANXIA~1\\AppData\\Local\\Temp\\2zH15Mn5JzNTJumOuB378BJAJzP\\resources\\app.asar.unpacked\\node_modules\\android-tools-bin\\dist\\win32\\x86\\heimdall.exe detect\nERROR: Failed to detect compatible download-mode device.","code":1},"stderr":"ERROR: Failed to detect compatible download-mode device."}
command: exec: {"cmd":["adb","-P",5037,"get-state"],"stdout":"device"}
command: exec: {"cmd":["adb","-P",5037,"shell","getprop ro.product.device"],"stdout":"sagit"}
info: device detected: sagit
info: Installing Ubuntu Touch on your Xiaomi Mi 6 (sagit)
info: configuring...
info: settings: {"bootstrap":true,"wipe":true,"channel":"20.04/arm64/android9plus/devel"}
verbose: running step {"actions":[{"core:download":{"group":"firmware","files":[{"url":"https://github.com/UbuntuTouch-sagit/ubuntu-touch-sagit/releases/download/v1.1/vendor.zip","name":"vendor.zip","checksum":{"sum":"13b018a5e72a966b22cc4fdabfacdd5eff434366269602b1bae713973f57aaa6","algorithm":"sha256"}},{"url":"https://github.com/UbuntuTouch-sagit/ubuntu-touch-sagit/releases/download/v1.1/recovery.img","name":"recovery.img","checksum":{"sum":"bf857a093e1df99fba91252d4114ef8796d515e821657fcbfb504a5cdc8893c5","algorithm":"sha256"}}]}}],"condition":{"var":"bootstrap","value":true}}
verbose: running core action download
debug: checking previously downloaded firmware files
verbose: running step {"actions":[{"core:unpack":{"group":"firmware","files":[{"archive":"vendor.zip","dir":"unpacked"}]}}],"condition":{"var":"bootstrap","value":true}}
verbose: running core action unpack
debug: Unpacking C:\Users\panxiaoguang\AppData\Roaming\ubports\sagit\firmware\vendor.zip to: C:\Users\panxiaoguang\AppData\Roaming\ubports\sagit\firmware\unpacked
verbose: running step {"actions":[{"adb:reboot":{"to_state":"bootloader"}}],"fallback":[{"core:user_action":{"action":"bootloader"}}],"condition":{"var":"bootstrap","value":true}}
verbose: running adb action reboot
command: exec: {"cmd":["adb","-P",5037,"reboot","bootloader"]}
verbose: running step {"actions":[{"fastboot:format":{"partition":"userdata","type":"ext4"}}],"condition":{"var":"wipe","value":true}}
verbose: running fastboot action format
I didn't see any error information in this log, but the process continuely stucks on cleaning up (Formatting usedata partition) and my mobile phone just show a fastboot page.
Anyone can help me on this issue ?