Titantool disk space 0GB

Jupiter
1

Hi,

I hope this is the right forum. I always run into an error with titantool on Linux when trying to use the DFU onto the eNVM. Device is found, zip selected, but it fails to extract the zip. In seetings it shows for every location I select “0GB” despite my disk has tons of space left. Is this related to AppImage sandboxing? Any suggestion for a workaround?

Best,
Stefan

2 
unzip /change/this/path/to/file/titantools_for_linux-1.0.35-beta.AppImage.zip

chmod 555 /change/this/path/to/file/titantools_for_linux-1.0.35-beta.AppImage

sudo /change/this/path/to/file/titantools_for_linux-1.0.35-beta.AppImage
3

Hi,

thanks, yes, this is what I did, but inside the AppImage application it complains about 0GB during unzip and in settings I can change the workspace folder, its always 0GG for every folder.

Best,
Stefan

4

What is the name of zip file image being used?

Which workspace folder is being selected?

What is the output from the command

df  -h
5

milkv-jupiter-ubuntu-23.10-desktop-k1-v1.0.9-release-2024-0719.img.zip and titantools_for_linux-1.0.35-beta.AppImage.zip

Any workspace folder (/tmp, ~/, …)

[info]  目录已创建: /run/user/1000/.flash_tmp/1724917293603_1724917293603
[info]  /run/user/1000/.flash_tmp/
[info]  当前磁盘剩余空间大小为3.089752197265625
[error] >>>>>
[error] 刷机文件解压失败!

Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vgxubuntu-root 1,8T 1,3T 485G 73% /

Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy
6

I now ran it as sudo and with --no-sandbox, and it leads to this error:

[info] create socket server
[info] use socket port: 35955
[info] 执行刷机命令"/root/.flash_temp/flashserver" -path /tmp/.flash_tmp/1725039572903_1725039572903 -port 3-2-3 -address localhost:35955 -id DRS1jU28olByP9Ck -config
[info] 刷机失败!
[info] 【错误码】 20004【错误原因】刷机配置YAML加载错误【详细原因】/tmp/.flash_tmp/1725039572903_1725039572903/fastboot.yaml not exist
[warn] 烧录失败!

7

Ha, the last one was easy. Not the .img.zip, but the regular .zip. I just did the same with unip as user and then fastboot and it seems to work too. So maybe something with sandboxing.

Thanks, best!

8

Yeah only the regular zip named ‘milkv-jupiter-ubuntu-23.10-desktop-k1-v1.0.9-release-2024-0719.zip’ (without ‘img.zip’ at the end) can be used to write to NVMe. So stick to that one. There are actually two types of files being used by the tool. The one with ‘.img.zip’ extension is a standard single disk image that is common in linux. The other zip file is an Android-like rom package, which is the only format the tool supports for transferring to NVMe.
Also when using the tool, at the screen where the NVMe drive can be selected as the destination dfu-device there is a check box and slider shown below the file name. It may be necessary to click that slider if the NVMe has old data on it and make sure to select ALL partitions listed before clicking Start Flashing.

9

It may be necessary to click that slider if the NVMe has old data on it and make sure to select ALL partitions listed before clicking Start Flashing.

Using Linux titantools Version 2.0.1-Rc for linux (Not available on Github, but I got a prompt when running 1.0.35-beta) it was not possible for me to select all 3 options. Generally option 2 (partition_flash.json) was not selectable. Using no option for the Configure Partition File Slider, or only one the Jupiter_V1.0 would not boot, even after flashing successfully.

I got it working after selecting partition_2M.json and partition_universal.json.
This selection resulted in the following partitioning:
image

The Ubuntu Image I used: milkv-jupiter-ubuntu-23.10-desktop-k1-v1.0.9-release-2024-0719.zip