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
When I select the Profile for "1.3.21 - BK7231N" "oem_bk7231n_light_ty", it takes me to the page to choose the output directory, but when I both select or create a new directory, it takes me back to the Profiles tab. I'm trying to dump the data for this Maelrsrlg E17 RGB bulb . I was able to successfully exploit several of the same bulbs using tuya-cloudcutter and a Raspberry Pi, but I believe I'll need the firmware dump to move forward. Selecting the first in the list of profiles did alllow me to go through the whole process and fail at the end, which is good.
The text was updated successfully, but these errors were encountered:
You should not be using known version numbers with LightLeak, only the ones prefixed with LightLeak - . If you know your version, and there is a matched version already in CloudCutter, LightLeak will not be useful for you, you should be using Tuya-CloudCutter. The LightLeak app is only for potentially dumping firmware OTA, not actually cutting or replacing firmware.
You can simply flash KickStart to these devices, then use LTChipTool if you need to build a configuration or dump the storage data. The storage is available even after flashing custom firmware when done via Tuya-CloudCutter.
When I select the Profile for "1.3.21 - BK7231N" "oem_bk7231n_light_ty", it takes me to the page to choose the output directory, but when I both select or create a new directory, it takes me back to the Profiles tab. I'm trying to dump the data for this Maelrsrlg E17 RGB bulb . I was able to successfully exploit several of the same bulbs using tuya-cloudcutter and a Raspberry Pi, but I believe I'll need the firmware dump to move forward. Selecting the first in the list of profiles did alllow me to go through the whole process and fail at the end, which is good.
The text was updated successfully, but these errors were encountered: