Website Comment

[utterances-bot]

Rooting the Xiaomi STYJ02YM (viomi-v7) Vacuum Robot - itooktheredpill

https://itooktheredpill.irgendwo.org/2020/rooting-xiaomi-vacuum-robot/

[tovroman]

Hello! Your method will help if my vacuum cleaner blinks slowly but does not respond to pressing and cannot work? https://youtu.be/lGFEfKLKq64

[rumpeltux]

I don’t know. Give it a try.

[tovroman]

@rumpeltux Suddenly he will completely break? Could you make a script that you can simply run when connected to a PC?

[rumpeltux]

Potentially, once there’s more use of root functionality. E.g. a Valetudo install script.

[berrywhite96]

I connected the device to my MacBook, ran while true; do adb shell; done and didn't get any shell or terminal.
Tried to put the usb cable in while running the vacuum, put it in before booting and the booted several times. But nothing worked. I am on a version later, so version 3.5.3_0044. Maybe they fixed the terminal access? Can someone on the same version verify this behaviour?

[berrywhite96]

Sorry I meant version 3.5.3_0045. dmesg | grep usb doesn't show any usb device, maybe they turned the usb debugging completely off.

[rumpeltux]

Did you power off the vacuum before connecting the USB?
The adb briefly appears around the time the vacuum plays its first sound after power on. It’s also not 100% reliable (but probably ~80% or so), so you may need to try twice.
I looked at the diff to the 3.5.3_0045 firmware. There’s no indication that adb was disabled.

[berrywhite96]

Did you power off the vacuum before connecting the USB?
The adb briefly appears around the time the vacuum plays its first sound after power on. It’s also not 100% reliable (but probably ~80% or so), so you may need to try twice.
I looked at the diff to the 3.5.3_0045 firmware. There’s no indication that adb was disabled.

Yes, I also disconnected the battery from the vacuum. I tried it very often, but the shell does not appear. I also tried adb with my phone, there was no problem the shell appeared immediatly.

[berrywhite96]

Ok maybe I got a charging only usb cable or I didnt saw the shell (lol?). Now I am stuck at point 2, I don't know why but it spawns the shell instead of running the given the command. I tried to run with the -n and -t flag and also put the command into quotes, this also does not work.
Maybe my the adb for Mac OS is broken or my robot. Is there a way run commands on boot?

[rumpeltux]

You’ll need to push the fixed /bin/adb_shell as outlined in the article to be able to execute shell commands.

[berrywhite96]

You’ll need to push the fixed /bin/adb_shell as outlined in the article to be able to execute shell commands.

I did it, also I pulled the file from the vacuum to double check that this is the actual file. It seems to be that the custom adb_shell file stays there also after reboot, but still it isnt possible to run shell commands.

[rumpeltux]

I did it, also I pulled the file from the vacuum to double check that this is the actual file. It seems to be that the custom adb_shell file stays there also after reboot, but still it isnt possible to run shell commands.

So what’s the error you’re getting?

[berrywhite96]

I did it, also I pulled the file from the vacuum to double check that this is the actual file. It seems to be that the custom adb_shell file stays there also after reboot, but still it isnt possible to run shell commands.

So what’s the error you’re getting?

There arent any errors, it just spawns the shell instead of running the given command.

[rumpeltux]

There arent any errors, it just spawns the shell instead of running the given command.

If you get a shell that’s good enough. You can try piping commands to it: echo id | adb shell
You can also just adb push -a an executable shell script for startup execution, e.g. /etc/rc.d/S51rootme.
It’ll be executed on every boot.

[Nortonko]

thanks, successfully rooted. is there a way how to get the valetudo on this device?