Lost ssh key and unable to reinstall valetudo after a factory reset

[pulien]

Are you already using Valetudo?

No, but in the process of starting it

Your questions

Hello,

I wanted to connect to the vacuum cleaner via SSH, but I lost the keys. I wanted to retrieve them from the job, but they were no longer available (after only two days).
Unable to find a solution, I performed a factory reset. When I tried to reinstall the files in fastboot, I encountered the following errors (which I hadn't seen before).

fastboot flash toc1 toc1.img
Warning: skip copying toc1 image avb footer (toc1 partition size: 0, toc1 image size: 1245184).
Sending 'toc1' (1216 KB)                           OKAY [  0.046s]
Writing 'toc1'                                     OKAY [  0.051s]
Finished. Total time: 0.107s

fastboot flash boot1 boot.img
Warning: skip copying boot1 image avb footer (boot1 partition size: 0, boot1 image size: 10838016).
Sending 'boot1' (10584 KB)                         OKAY [  0.399s]
Writing 'boot1'                                    OKAY [  1.141s]
Finished. Total time: 1.549s

fastboot flash rootfs1 rootfs.img
Warning: skip copying rootfs1 image avb footer (rootfs1 partition size: 0, rootfs1 image size: 140735507020512).
Sending sparse 'rootfs1' 1/4 (32764 KB)            OKAY [  1.238s]
Writing 'rootfs1'                                  OKAY [  2.583s]
Sending sparse 'rootfs1' 2/4 (32764 KB)            OKAY [  1.244s]
Writing 'rootfs1'                                  OKAY [  1.684s]
Sending sparse 'rootfs1' 3/4 (32764 KB)            OKAY [  1.238s]
Writing 'rootfs1'                                  OKAY [  2.581s]
Sending sparse 'rootfs1' 4/4 (10400 KB)            OKAY [  0.393s]
Writing 'rootfs1'                                  OKAY [  1.431s]
Finished. Total time: 12.456s

fastboot flash boot2 boot.img
Warning: skip copying boot2 image avb footer (boot2 partition size: 0, boot2 image size: 10838016).
Sending 'boot2' (10584 KB)                         OKAY [  0.402s]
Writing 'boot2'                                    OKAY [  1.136s]
Finished. Total time: 1.548s

 fastboot flash rootfs2 rootfs.img
Warning: skip copying rootfs2 image avb footer (rootfs2 partition size: 0, rootfs2 image size: 140721261134304).
Sending sparse 'rootfs2' 1/4 (32764 KB)            OKAY [  1.242s]
Writing 'rootfs2'                                  OKAY [  3.491s]
Sending sparse 'rootfs2' 2/4 (32764 KB)            OKAY [  1.238s]
Writing 'rootfs2'                                  OKAY [  2.576s]
Sending sparse 'rootfs2' 3/4 (32764 KB)            OKAY [  1.239s]
Writing 'rootfs2'                                  OKAY [  3.477s]
Sending sparse 'rootfs2' 4/4 (10400 KB)            OKAY [  0.394s]
Writing 'rootfs2'                                  OKAY [  1.429s]
Finished. Total time: 15.142s

fastboot reboot
Rebooting                                          OKAY [  0.000s]
Finished. Total time: 1.553s

When I rebooted and connected via SSH with the new keys, it asked me for a password that I didn't have. It was as if the factory reset hadn't deleted the SSH part. What can I do to actually reset all this and reinstall Valetudo?

ssh -i keys/key.id_rsa root@192.168.5.1
The authenticity of host '192.168.5.1 (192.168.5.1)' can't be established.
ED25519 key fingerprint is SHA256:s...
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '192.168.5.1' (ED25519) to the list of known hosts.
root@192.168.5.1's password:
Permission denied, please try again.
root@192.168.5.1's password:

Since then, in a panic, I did another factory reset and tried to start the process again with another dustbuilder, but I'm still at the same point when I do the toc part :
fastboot flash toc1 toc1.img
Warning: skip copying toc1 image avb footer (toc1 partition size: 0, toc1 image size: 1245184).
Sending 'toc1' (1216 KB) OKAY [ 0.046s]
Writing 'toc1' OKAY [ 0.977s]
Finished. Total time: 1.033s

The only file I have from the first installation is the backup.tar

Thank you for your assistance

[Hypfer]

I have no idea what error message you mean. The whole blob of text here isn't exactly easy or fun to follow.
But anyway.

Reflashing won't help with a lost ssh key, as the authorized_keys file that is used by dropbear is not stored on any flashable partition.
Unless you've disabled it, you should be able to login via password using the password calculated from the SN as can be seen in the UART rooting instructions for dreame.

On a rooted bot, you should also have a passwordless UART shell which would also allow you to do that.

Once you have a shell, delete /mnt/misc/authorized_keys and reboot. On reboot, the rooted firmware will then re-seed that file with the key baked into the rooted rootfs you've flashed.

[pulien]

Sorry for the long text above and sorry for my English. So, if I understand correctly, the factory reset does not affect the SSH keys, and my second “Phase 2: Rooting” did nothing

I managed to connect via SSH with the SN password and was able to install Valetudo and reinstall a new Dustbuilder build (problem with the L10S Pro Ultra Heat, which wouldn't do anything other than vacuum)

Thank you very much and have a great day!