I bricked my Dreame Z10 Pro with the helped of Valetudo, brought to you by Soren Beye, a.k.a. “Hypfer”.
Yes I AM PISSED, but not about the bricking itself. I get that there are risks, I willingly toke them, what I am pissed about is getting shadow-banned on Github because I reported it. The issue I opened was deleted and I can’t create a new one nor can I fork the project. I wasn’t rude, asking for a refund or anything. I posted it there to; 1. warn others and 2. see if there was any change of recovery.
Now in hindsight I could have know based on this so-youve-been-banned . I don’t what hot piece of garbage this is but it should have been a clear sign. Stay away from Valetudo.
I spoke to a couple of people on the Valetudo Discord, while they were nice and helpful, even mods (yes, multiple) on his own Discord report he, Soren, “is like that”.
For the interested, here is my issue I tried to submit the second time. I didn’t think I needed to save it the first time.
Bricked Dreame Z10 Pro
What is happening?
boot failure resulting in bootloop
136]HELLO! SBOOT is starting!
[139]sboot commit : ee0e26c
NOTICE: BL3-1: v1.0(debug):b108d89
NOTICE: BL3-1: Built : 14:13:35, 2020-04-08
NOTICE: BL3-1 commit: 8
NOTICE: secure os exist
MESSAGE: [0x0] TEE-CORE: OP-TEE version: 5f533bf9-dirty #1 2020年 08月 08日 星期六 03:04:16 UTC arm
NOTICE: BL3-1: Preparing for EL3 exit to normal world
NOTICE: BL3-1: Next image address = 0x4a000000
�[01.049][NE]rawnand not support chip 1: 03 03 03 03 03 03 03 03
[01.055][NE]rawnand not support chip 2: 03 03 03 03 03 03 03 03
[01.061][NE]rawnand not support chip 3: 03 03 03 03 03 03 03 03
[01.072]Item0 (Map) magic is bad
[02.548]set disp.dev2_output_type fail. using defval=0
[02.593]secure storage read rpmb_key fail with:-1
[02.597]secure storage read dm_crypt_key fail with:-1
[02.604][ARISC ERROR] :get [allwinner,sunxi-hwspinlock] device node error
[SCP] :sunxi-arisc driver begin startup 2
[SCP] :0x1
[SCP] :arisc version: [ramsm-xt318rnit-1v-a0.0.ler-esaerid-]
[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
What should be happening?
rooted robot, show MOTD
built with dustbuilder (https://builder.dontvacuum.me)
Fri 04 Feb 2022 10:08:21 PM UTC
1099
How to reproduce
- https://valetudo.cloud/pages/general/supported-robots.html#dreame_z10pro
- https://valetudo.cloud/pages/installation/dreame.html#uart
- reset the robot
- prept’ed a USB drive with https://valetudo.cloud/pages/installation/res/dreame_uart_root_img.zip
- Used Dreame Breakout PCB
- setup https://github.com/Hypfer/valetudo-helper-httpbridge
- opened screen
- logged in
- tar cvf /tmp/backup.tar /mnt/private/ /mnt/misc/ /etc/OTA_Key_pub.pem /etc/publickey.pem
- curl -X POST http://192.168.5.100:1337/upload -F ‘file=@./backup.tar’
- wget http://192.168.5.100:1337/dreame.vacuum.p2028_fw.tar.gz
- tar -xvzf dreame.vacuum.p2028_fw.tar.gz
- ./install.sh
Please enter the Valetudo version you’re using
None yet, didn’t get to that part yet
Please enter the vendor and model of robot you’re using
Dreame Z10 Pro
Please enter the robot’s firmware version you’re using
latest
Additional context
I dont know why my previous ticket was deleted
Screenshots
