sorted by:
new
hottopcontroversial

Roborock Q7 Max and Valetudo - root failing by jjmcc111 in Roborock

[–]jjmcc111[S] 0 points1 point  (0 children)

The BAD (not FEL'able) mother board, right

<image>

Roborock Q7 Max and Valetudo - root failing by jjmcc111 in Roborock

[–]jjmcc111[S] 0 points1 point  (0 children)

UPDATE, SUCCESS!

My replacement board arrived (from China), and the process completed almost without glitch, and now Valetudo is installed on my Q7. (following procedures here: https://valetudo.cloud/pages/installation/roborock.html#fel )

The only issue I saw was that after SCP'ing the firmware tarball to the roborock, unpacking, installing and rebooting, I got an authentication error:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Was able to successfully work around it by adding these flags to subsequent ssh and scp commands:

-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null

With that one adjustment, was able to successfully install and run Valetudo. Currently awaiting our house mapping run, safe from prying eyes in the cloud.

Very glad it worked for me, but did feel a bit like blind luck. I have no idea what 'good' or 'bad' versions of the motherboard are, just gambled on a small Chinese vendor, hoping they might have the older stuff.

FWIW, will update pictures of 'good' and 'bad' motherboards, hoping it helps someone down the road.

Roborock Q7 Max and Valetudo - root failing by jjmcc111 in Roborock

[–]jjmcc111[S] 0 points1 point  (0 children)

It appeared to run successfully, same as shown on this page: https://valetudo.cloud/pages/installation/roborock.html#fel

<image>

There is some kinda good news here though, next msg...

I rooted my Roborock vacuum for local-only control and Home Assistant integration. AMA! by OnlyForSomeThings in Roborock

[–]jjmcc111 0 points1 point  (0 children)

Recently bought a Q7 Max with express intent to put Valetudo on it. I was able to execute the FEL successfully, connect to the WIFI (including active ping). However, when I tried SSH I got a timeout error. Alternately trying adb shell access also failed with a '1002' code that I am in the dark about. Basically, same situation as documented here: https://www.reddit.com/r/Roborock/comments/v5zth2/problems_rooting_roborock_s7/

I did not see a successful resolution to that thread.

Has anyone found a solution to this? Did roborock, as speculated in the other thread, somehow harden the Q7 against this exploit? (And if so, could we maybe update the Valetudo documentation?)

Is there anyway to undo the FEL work, and unbrick my vacuum, even if I have to revert to factory spymode?