Struggling to root the viomi v6

[Realitaetsverlust]

Are you already using Valetudo?

No, but in the process of starting it

Your questions

I recently bought a viomi v6 (was branded as a viomi v2) since it was on sale. However, I am struggling to flash it.

I have downloaded the repository for it (https://github.com/Hypfer/valetudo-crl200s-root) but I’m unable receive an adb shell. When connecting the device to my PC, it first registers as “Allwinner Technology sunxi SoC OTG connector”. It’s active for about 2 seconds, then it’s disconnects again. A few seconds later, the robot says “Turning on” and the device then registers as “USB Developer Android” for like a splitsecond, then it disconnects again.

Now, according to the docs, when this happens, I have to run the enable-adb.sh script. However, this is where I'm stuck. I followed the instructions the script provides (powering the robot off, disconnecting the battery, usb cable ready), and upon pressing enter, the script starts. I plug in the cable, and the script keeps churning out "adb: error: failed to get feature set: no devices/emulators found". This keeps happening until the device registers as a "USB Developer Android", which then turns the output to this:

adb_shell: 1 file pushed, 0 skipped. 1.0 MB/s (58 bytes in 0.000s)
adb_shell: 1 file pushed, 0 skipped. 1.3 MB/s (58 bytes in 0.000s)
adb_shell: 1 file pushed, 0 skipped. 1.7 MB/s (58 bytes in 0.000s)
adb_shell: 1 file pushed, 0 skipped. 1.7 MB/s (58 bytes in 0.000s)
adb_shell: 1 file pushed, 0 skipped. 1.4 MB/s (58 bytes in 0.000s)
adb_shell: 1 file pushed, 0 skipped. 1.6 MB/s (58 bytes in 0.000s)
adb_shell: 1 file pushed, 0 skipped. 1.6 MB/s (58 bytes in 0.000s)
adb_shell: 1 file pushed, 0 skipped. 1.6 MB/s (58 bytes in 0.000s)
adb: error: failed to read copy response

Immediately afterwards, the scripts starts returning the adb error above. Now, I also saw that this might take 10 or more attempts, but I've been sitting here for almost 30 minutes replugging the USB over and over again, getting the exact same result and I just kinda can't shake the feeling that something else is wrong.

I tried playing around with udev rules, but that wasn't leading me anywhere. My next chain of thought was that I accidentally bought a version of the robot that is not supported. The serial number is "V-RVCLM21B" tho which seems to correspond to the "Viomi V2 Pro", which is also indicated to be supported. The device also looks like a carbon copy of the device in the images of the "Supported robots" section of the docs.

I'm kinda at the end of my knowledge here. If the answer is "Try replugging the USB longer", I'll do that, but I just can't shake the feeling something else is kinda brittle here and prevents this from working as intended.

Any idea or help would be greatly appreciated!

[Hypfer]

The unpleasant thing with that rooting method is that it relies on exploiting a race condition, so it will confuse the hell out of you, because it is not deterministic.

but I just can't shake the feeling something else is kinda brittle here and prevents this from working as intended.

Probably, yes. But no idea what exactly, unfortunately.

Could be a lot of things. Have you already tried a different host? Some people had trouble using a Raspberry Pi, because it didn't enumerate USB fast enough.

[Realitaetsverlust]

I did try two devices, my laptop and my stationary PC - both are rather new and both run arch. Since you said "didn't enumerate fast enough", I tried setting the kernel parameter "usb-storage.delay_use" to 0 in the hopes that would make the enumeration go faster, but sadly, that didn't do the trick either. My girlfriend got linux mint on her machine, but the machine is substantially older and I'm not entirely sure it would be faster.