ct-Open-Source / ct-Open-Source/tuya-convert

Device partially update but seems to be stuck at intermediate firmware: Aoyococr X10S

Open
#553 22 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
5.1k
Forks
523
PR merge metrics
No merged PRs in 30d

Description

I am trying to flash the default tasmota.bin to a few Aoyococr X10S smart plugs. I got 2 of the 4 to work without any issues with 2 failing.
Looking at the logs it seems that the intermediate firmware uploaded successfully but then the rest of the steps failed. I do not see an SSID of vflash-recovery on my network post the install.

I actually took one of the devices apart to see if I could put a header on it to manually flash tasmota on it but that is not going to work at all.

Is there anything I can do to recover from this?

[smarthack-mqtt.log](https://github.com/ct-Open-Source/tuya-convert/files/4247321/smarthack-mqtt.log)
[smarthack-udp.log](https://github.com/ct-Open-Source/tuya-convert/files/4247322/smarthack-udp.log)
[smarthack-web.log](https://github.com/ct-Open-Source/tuya-convert/files/4247323/smarthack-web.log)
[smarthack-psk.log](https://github.com/ct-Open-Source/tuya-convert/files/4247324/smarthack-psk.log)
[smarthack-wifi.log](https://github.com/ct-Open-Source/tuya-convert/files/4247325/smarthack-wifi.log)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the attached smarthack-mqtt.log, smarthack-udp.log, smarthack-web.log, smarthack-psk.log, and smarthack-wifi.log to identify where flashing stops. Done would require establishing whether these devices have a supported recovery path and documenting the recovery steps or limitation.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.