Unable to root STYTJ02YM CN version

[rysiacz]

I had no luck and after starting script it looks that adb_shell was sent to vacuum:
[100%] /bin/adb_shell

adb_shell: 1 file pushed. 0.0 MB/s (58 bytes in 0.034s)
Shell fixed...
rm: can't remove '/etc/rc.d/S90robotManager': No such file or directory
Please replug the USB cable again. Do not unplug once you hear the sound.
shell_is_ready
Shell is present.
Waiting a bit to allow the robot to connect to wifi.............
error: no devices/emulators found
Robot IP is
--2021-07-31 04:58:33-- https://itooktheredpill.irgendwo.org/static/2020/dropbear_2015.71-2_sunxi.ipk
Resolving itooktheredpill.irgendwo.org (itooktheredpill.irgendwo.org)... 37.187.99.185, 2001:41d0:a:23b9::1
Connecting to itooktheredpill.irgendwo.org (itooktheredpill.irgendwo.org)|37.187.99.185|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 81893 (80K) [application/octet-stream]
Saving to: dropbear_2015.71-2_sunxi.ipk

dropbear_2015.71-2_sunxi. 100%[==================================>] 79.97K --.-KB/s in 0.08s

2021-07-31 04:58:33 (961 KB/s) - ‘dropbear_2015.71-2_sunxi.ipk’ saved [81893/81893]

dropbear_2015.71-2_sunxi.ipk: OK
adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
error: no devices/emulators found
Setting local ssh alias vacuum to root@.
You can use 'ssh vacuum' to connect to the robot from now on.
SSH was installed.
Please change the root password now. The default one is typically "@3i#sc$RD%xm^2S&".
/root/.ssh/config line 2: Missing argument.
Restoring robot services.
/root/.ssh/config line 2: Missing argument.
Your device is now rooted.
/root/.ssh/config line 2: Missing argument.
Would you like to install Valetudo (open-source cloudless vacuum robot UI)? (y/n) n

But now it looks vacuum service is not starting - home/power light are flashing slowly. After connecting debug cable vacuum is visible in adb devices but adb shell returns below errors:

• exec '/bin/adb_shell' failed: No such file or directory (2) -
  7 ]
  adbd D: received remote packet, sending to transport
  [adbd D]about to read (fd=7, len=24)
  [adbd D]transport_socket_events(fd=11, events=0001,...)
  [adbd D]handle_packet() OPEN

Any idea how to back my vacuum operational again?

[rysiacz]

Just for other issues was casued by linux in live cd mode. After installing standalone version all is fine. Found in #10 @rumpeltux - please add short note to do not use live cd linux :)