How to get latest firmware .pkg from Xiaomi which is not listed here?

[ovaltineo]

My Gen 1 Xiaomi is telling me that there is 3.3.9_003357 available firmware. But this firmware is not listed in the .pkg files in this project. How can I pull the latest .pkg from Xiaomi so I can update my rooted vacuum?

[lukeman11]

Yeah, same for my Roborock. Floleapp is telling me, there is 3.3.9_001598. The last one in this project is 3.3.9_001518 :-(

[ovaltineo]

I found out how to do it. First, disable update on the robot by renaming /usr/bin/ccrypt to /usr/bin/ccrypt_. Then, use the app to update the firmware. It will download the firmware but will fail to update. The .pkg file can now be copied from /mnt/data/.temp/Update.pkg.

[dugite-code]

@ovaltineo are you able to upload and share the latest firmware somewhere?

[muhviehstah]

v1 firmwares can be found here https://cloud.it-kraut.net/s/BW4SHMeTRt36k43

[muhviehstah]

latest v1 firmware 3358 added

[dugite-code]

It would be great if anyone who has the latest firmware from Xiaomi could submit the encrypted/decrypted hashes for updating the firmwareversions.xlsx

@muhviehstah files have these MD5 hashes
35538ab7035b4061efed0b10a90e8f69 *v11_003290.pkg
e03ed1f5bb5cf34bffda7b8e6202e4a1 *v11_003357.pkg
32707314f898c8bd0e631f98013fca06 *v11_003358.pkg

[dgiese]

Untested/Firmware with unknown things: https://dustcloud.seemoo.de/public/temp
Beware, apparently something breaks some open source tools in the new version. It seems that rockrobo tries to close down the firmware or is changing the API.

[ovaltineo]

Gen 1 v11_003504 from Flolevac is here https://drive.google.com/uc?id=1vwvMu44NZ8W_JiqULyf2S91lIo2lUVHQ&export=download

[junior013]

If you know the version number, you need (from FloleApp or elsewhere), you can download it from official direct link, like this: https://cdn.awsbj0.fds.api.mi-img.com/rubys/updpkg/v11_001228.pkg (just change the package name)

[dugite-code]

@junior013 I'm having no luck fetching any other firmware using the suggested link with any of the latest package names

https://cdn.awsbj0.fds.api.xiaomi.com/rubys/updpkg/v11_003290.pkg
https://cdn.awsbj0.fds.api.mi-img.com/rubys/updpkg/v11_003357.pkg
https://cdn.awsbj0.fds.api.mi-img.com/rubys/updpkg/v11_003358.pkg

All return:
Object Not Found: Make sure your object exist in current region, request-id=#######################

Given how old the package number in your link is it could be no longer used or it could be the cdn for my region just isn't allowing me to see any of the files. Where did you find this link?

[junior013]

Sorry, it really doesn't work with your versions :/ I used it for latest Gen2 FW-s from EU, and downloaded 4 different version. (Maybe it's only for G2?)
I found the link in a thread on roboter-forum.de

[dugite-code]

It could well be "rubys" is the model name for the Gen2? A search online suggests Xaiomi uses [url]/[model]/[resource] so it might be possible.

[StefanSchoof]

Has someone tried the 3.3.9_001633 for the gen2? The description mentions saved maps and software barrier. That sound interesting.

[FeatureExpert]

Seems those features are disabled on EU servers unfortunately.

EDIT: Well, I think I'm a bit closer. There's a file on roborock - /mnt/data/rockrobo/lab.cfg with content '0'. If you set it to '1', the 'Map saving mode' option shows up in MiHome application. I can set software barriers and no-go zone in app. Testing it now.

[reaper7]

@FeatureExpert - it means that root works on gen2 with fw 001633 ?

[junior013]

@reaper7 Yes, it works with all newer versions. I use 001644 now (wow, 002002 available!)
But map handling changed in 001618 -> dustcloud can't extract live map :/

[reaper7]

@junior013 - tnx for the info :)
I can download fw for gen2 from this location ?? https://dustcloud.seemoo.de/public/temp/

[StefanSchoof]

I updated to 001633 and for me the saved map option was in the app. I had not to edit the lab.cfg, but the already contains a 1

[asch8505]

EDIT: Well, I think I'm a bit closer. There's a file on roborock - /mnt/data/rockrobo/lab.cfg with content '0'. If you set it to '1', the 'Map saving mode' option shows up in MiHome application. I can set software barriers and no-go zone in app. Testing it now.

For me there is no lab.cfg file on 001633 oO I created it with the content '1', but it has no effect on my app. Maybe a new app is required, which is not yet available in my region (Germany). Which is the latest mi home app version? In my Play Store it is 5.4.26

[reaper7]

@asch8505 - in Poland I have 5.4.29

[blakeblackshear]

Found the path to download the firmware for Gen1 directly: https://cdn.awsbj0.fds.api.mi-img.com/updpkg/v11_003416.pkg

[dugite-code]

@blakeblackshear Huh well that's interesting they must have set that up prior to their current layout of [url]/[model]/[resource] they appear to be using for their other products. So I didn't think of just removing [model]

Thanks for letting us all know

Edit:
v11_003290.pkg works
v11_003357.pkg works
v11_003358.pkg Not Found
v11_003600.pkg works

[dugite-code]

I've added a page to the wiki

[dgiese]

I changed the site, and added more information: https://github.com/dgiese/dustcloud/wiki/Xiaomi-Vacuum-Firmware

[sanghpm]

hi bro , thank good i finded you .
i have a problem with my xiaomi gen 1 , a problem at EMMC it empty. im finding the mentos to conect xiaomi vancuum to pc but dont have any thing guide about that .
i has download the firmware v11_003357.pkg but i cant update.
everyone helpt me about that .
thank you so much

[dgiese]

Not related to this issue.
However eMMC problems might have 2 general causes: 1. The eMMC is completely broken (e.g. not detected or detected with 0 MB). In that case the only way would be to replace the eMMC (like with a SD card). 2. The partition format or data on the eMMC is deleted. I would not think that this is the reason for your case, but theoretically you could restore the data from a working gen1 robot.

In both cases your vacuum will propably never be able to connect to the cloud again, as the DID, Key and MAC information is lost. In addition the LDS calibration data is also stored on the eMMC, this can also cause issues. Maybe it would be possible to run the vacuum with dummycloud and Valetudo, as it is independant of the cloud.

The first step to figure out what happened to the eMMC would be to connect to serial and look into the bootlog.

[sanghpm]

Yeah thank Dgiese somuch about the answer me .
I have the vancuum xiaomi and that is life , i had read emmc by UFI and write a new emmc after that . but appear in my eye the vancuum not really life because dont turn on wifi it only turn on and clearner and came back home .
I had read more topic about update the firmware by dumycloud but really i dont have any solution to connect with my vancuum
Can you give me some solution about update firmware to vancuum , ADB or Write by UFI

[dgiese]

I guess you need to connect via Serial to figure out whats going on.

[sanghpm]

Hey , can you add friend me on facebook . we can tell in there . ( https://www.facebook.com/sanghpm )

[ghost]

How i can update firmware to my Xiomi S5 gen 2 from file *.pkg ?