L10 Pro: boot loop after ./install.sh

[Brockhold]

Are you already using Valetudo?

Yes, for a long time

Your questions

I've rooted and installed Valetudo successfully on a few previous Dreame vacuums, but have failed with this Dreamebot L10 Pro.

As the serial number sticker was damaged, I got the serial number from the Xiaomi Home API.
I followed the UART root directions, and was able to log in successfully. Then I created a backup and extracted it.
I used the dustbuilder for L10 Pro and downloaded the firmware to the robot and extracted it.
Finally, when I executed install.sh, install appeared fine, but the robot began to boot-loop with logs indicating a handful of failures prior to starting the kernel. The kernel does claim to start, but the unit reboots after a few minutes.

The logs repeat like so:

[138]HELLO! SBOOT is starting!
[141]sboot commit : 92365cb
NOTICE:  BL3-1: v1.0(debug):0880fb7
NOTICE:  BL3-1: Built : 18:49:08, 2020-11-17
NOTICE:  BL3-1 commit: 8
NOTICE:  cpuidle init version V1.0
NOTICE:  secure os exist
M/TC: OP-TEE version: 7eb0ba4d-dirty (gcc version 5.3.1 20160412 (Linaro GCC 5.3-2016.05)) #1 2021年 10月 12日 星期二 05:46:52 UTC arm
NOTICE:  BL3-1: Preparing for EL3 exit to normal world
NOTICE:  BL3-1: Next image address = 0x4a000000
[01.131][NE]rawnand not support chip 1: 03 03 03 03 03 03 03 03
[01.136][NE]rawnand not support chip 2: 03 03 03 03 03 03 03 03
[01.142][NE]rawnand not support chip 3: 03 03 03 03 03 03 03 03
[01.153]Item0 (Map) magic is bad
[02.682]set disp.dev2_output_type fail. using defval=0
[02.727]secure storage read rpmb_key fail with:-1
[02.731]secure storage read dm_crypt_key fail with:-1
[02.738][ARISC ERROR] :get [allwinner,sunxi-hwspinlock] device node error
[SCP] :sunxi-arisc driver begin startup 2
[SCP] :0x1
[SCP] :arisc version: [ramsm-xt318rnit-2v-ar-0.aele]
[SCP] :arisc startup ready
[SCP] :arisc startup notify message feedback
[SCP] :send hard sync feedback message: 0x900200
[SCP] :sunxi-arisc driver v1.10 is starting
sunxi verify rootfs fail, reboot
[138]HELLO! SBOOT is starting!
[141]sboot commit : 92365cb
NOTICE:  BL3-1: v1.0(debug):0880fb7
NOTICE:  BL3-1: Built : 18:49:08, 2020-11-17
NOTICE:  BL3-1 commit: 8
NOTICE:  cpuidle init version V1.0
NOTICE:  secure os exist
M/TC: OP-TEE version: 7eb0ba4d-dirty (gcc version 5.3.1 20160412 (Linaro GCC 5.3-2016.05)) #1 2021年 10月 12日 星期二 05:46:52 UTC arm
NOTICE:  BL3-1: Preparing for EL3 exit to normal world
NOTICE:  BL3-1: Next image address = 0x4a000000
[01.131][NE]rawnand not support chip 1: 03 03 03 03 03 03 03 03
[01.137][NE]rawnand not support chip 2: 03 03 03 03 03 03 03 03
[01.142][NE]rawnand not support chip 3: 03 03 03 03 03 03 03 03
[01.153]Item0 (Map) magic is bad
[02.640]set disp.dev2_output_type fail. using defval=0
[02.684]secure storage read rpmb_key fail with:-1
[02.689]secure storage read dm_crypt_key fail with:-1
[02.695][ARISC ERROR] :get [allwinner,sunxi-hwspinlock] device node error
[SCP] :sunxi-arisc driver begin startup 2
[SCP] :0x1
[SCP] :arisc version: [ramsm-xt318rnit-2v-ar-0.aele]
[SCP] :arisc startup ready
[SCP] :arisc startup notify message feedback
[SCP] :send hard sync feedback message: 0x900200
[SCP] :sunxi-arisc driver v1.10 is starting
[03.425]Starting kernel ...

I have submitted this information to VAERS as requested, and created this public discussion in the hope there is a way to fix the robot. I'm pretty comfortable with poking around embedded linux systems. If there is anything else I can provide that would help, please let me know.

[Hypfer]

That was likely one of those bots that received a replacement PCB from service.
Those are not rootable, unfortunately.

You trying to make it work regardless of the SN roadblock in this case was its death sentence.

[Brockhold]

I wasn't aware that getting the serial number this way was a workaround, I expected it to match the dustbin sticker serial. That's unfortunate.
Thanks for the confirmation that it is dead.

[Hypfer]

No such workaround is mentioned in the docs on valetudo.cloud, so just following them would've been safe.
It would've ended in a roadblock, but with a working (albeit cloud-connected) robot. Now it's dead.