You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think I might have messed up my unit, but hopefully someone can help me bring it back to life.
I'm not sure how to classify this, but I can try to describe where I'm at...
The unit is a Viomi V8 (STYTJ02M), stock firmware 3.5.3_0017. I tried to root it using the script, enabled ADB (just holding both buttons until lights turned orange).
The script managed to install Dropbear on it, but then stranded on SSH connection rejected.
This is where I think I messed up.
I opened a shell through ADB, commented out the PasswordAuth line in Dropbear config thinking that the issue was related to some sort of certificate error.
Ran the script again but with same error.
Then I just tried to open a SSH connection which prompted me to add the key to known hosts.
Reran the script, it got stuck on password issues.
Returned to ADB shell, ran passwd and set a new root user pass on the vacuum.
Ran the script once again, entered the password when prompted, and now the script completed installing valetudo (updated the script with latest version 2023.8.0).
When the unit boots now, it has SSH running (port 22 is open), and after a few seconds Valetudo is available. No commands are working though, and it reboots after four minutes uptime exactly.
Now - I thought I might look at the Valetudo config files - but suddenly the password is not working anymore (and @3i#sc$RD%xm^2S& as mentioned in the script doesn't work either). Still unable to use the key pair... So SSH seems unusable.
Back to ADB - boot the unit, release keys when the light is orange, and now adb shell throws this back at me:
cubie@cubieboard2:~$ ssh vacuum
root@10.1.1.131's password:
Permission denied, please try again.
root@10.1.1.131's password:
cubie@cubieboard2:~$ adb shell
- exec '/bin/adb_shell' failed: Exec format error (8) -
OPEN
cubie@cubieboard2:~$ adb shell
- exec '/bin/adb_shell' failed: Exec format error (8) -
CLSE
[adbd D][ done fd=8 ]
[adbd D]about to read (fd=8, len=7)
[adbd D][ done fd=8 ]
[adbd D](null): received remote packet, sending to transport
[adbd D]about to read (fd=8, len=24)
[adbd D]transport_socket_events(fd=11, events=0001,...)
[adbd D]handle_packet() OPEN
cubie@cubieboard2:~$ adb shell
- exec '/bin/adb_shell' failed: Exec format error (8) -
8 ]
[adbd D]about to read (fd=8, len=7)
[adbd D][ done fd=8 ]
[adbd D](null): received remote packet, sending to transport
[adbd D]about to read (fd=8, len=24)
[adbd D]transport_socket_events(fd=11, events=0001,...)
[adbd D]handle_packet() OPEN
cubie@cubieboard2:~$ adb shell
- exec '/bin/adb_shell' failed: Exec format error (8) -
8 ]
[adbd D](null): received remote packet, sending to transport
[adbd D]about to read (fd=8, len=24)
[adbd D]transport_socket_events(fd=11, events=0001,...)
[adbd D]handle_packet() OPEN
cubie@cubieboard2:~$ adb shell
- exec '/bin/adb_shell' failed: Exec format error (8) -
OKAY
[adbd D]readx: fd=10 wanted=4
[adbd D]readx: fd=10 wanted=4 got=4
[adbd DR]0d000000 ....
[adbd D]transport_socket_events(fd=11, events=0001,...)
[adbd D]handle_packet() CLSE
[adbd D][ done fd=8 ]
[adbd D]about to read (fd=8, len=7)
[adbd D][ done fd=8 ]
[adbd D](null): received remote packet, sending to transport
[adbd D]about to read (fd=8, len=24)
[adbd D]transport_socket_events(fd=11, events=0001,...)
[adbd D]handle_packet() OPEN
cubie@cubieboard2:~$ adb shell
- exec '/bin/adb_shell' failed: Exec format error (8) -
wanted=4
[adbd D](null): received remote packet, sending to transport
[adbd D]readx: fd=10 wanted=4 got=4
[adbd D]about to read (fd=8, len=24)
[adbd DR]0d000000 ....
[adbd D][ done fd=8 ]
[adbd D](null): received remote packet, sending to transport
[adbd D]transport_socket_events(fd=11, events=0001,...)
[adbd D]about to read (fd=8, len=24)
[adbd D]handle_packet() OKAY
[adbd D]transport_socket_events(fd=11, events=0001,...)
[adbd D]handle_packet() CLSE
[adbd D][ done fd=8 ]
[adbd D]about to read (fd=8, len=7)
[adbd D][ done fd=8 ]
[adbd D](null): received remote packet, sending to transport
[adbd D]about to read (fd=8, len=24)
[adbd D]transport_socket_events(fd=11, events=0001,...)
[adbd D]handle_packet() OPEN
cubie@cubieboard2:~$
Any suggestions are welcome - I did backup the nanda > nandk before messing too much about, so If I get ADB working I might have a chance to flash them back? Can it be done through UART perhaps?
The text was updated successfully, but these errors were encountered:
I think I might have messed up my unit, but hopefully someone can help me bring it back to life.
I'm not sure how to classify this, but I can try to describe where I'm at...
The unit is a Viomi V8 (STYTJ02M), stock firmware 3.5.3_0017. I tried to root it using the script, enabled ADB (just holding both buttons until lights turned orange).
The script managed to install Dropbear on it, but then stranded on SSH connection rejected.
This is where I think I messed up.
I opened a shell through ADB, commented out the PasswordAuth line in Dropbear config thinking that the issue was related to some sort of certificate error.
Ran the script again but with same error.
Then I just tried to open a SSH connection which prompted me to add the key to known hosts.
Reran the script, it got stuck on password issues.
Returned to ADB shell, ran passwd and set a new root user pass on the vacuum.
Ran the script once again, entered the password when prompted, and now the script completed installing valetudo (updated the script with latest version 2023.8.0).
When the unit boots now, it has SSH running (port 22 is open), and after a few seconds Valetudo is available. No commands are working though, and it reboots after four minutes uptime exactly.
Now - I thought I might look at the Valetudo config files - but suddenly the password is not working anymore (and @3i#sc$RD%xm^2S& as mentioned in the script doesn't work either). Still unable to use the key pair... So SSH seems unusable.
Back to ADB - boot the unit, release keys when the light is orange, and now adb shell throws this back at me:
Any suggestions are welcome - I did backup the nanda > nandk before messing too much about, so If I get ADB working I might have a chance to flash them back? Can it be done through UART perhaps?
The text was updated successfully, but these errors were encountered: