mirko / SonOTA

Flashing Itead Sonoff devices with custom firmware via original OTA mechanism
GNU General Public License v2.0
719 stars 104 forks source link

SonOTA --legacy question #148

Closed mesab0ogie closed 6 years ago

mesab0ogie commented 6 years ago

Sonota.exe crashed halfway while using it, after connecting to Itead. Read around the forums and some people said to use the --legacy. Question is how do i do this with sonota.exe?

Thanks in advance for the help

2018-09-06 13:23:47,642: DEBUG: Current IPs: ['192.168.1.105', '192.168.1.195'] 2018-09-06 13:24:21,923: INFO: Using the following configuration: 2018-09-06 13:24:21,924: INFO: Server IP Address: 192.168.1.195 2018-09-06 13:24:21,924: INFO: WiFi SSID: mesab0ogie_2.4G 2018-09-06 13:24:21,924: INFO: WiFi Password: ** 2018-09-06 13:24:21,924: INFO: Platform: win32 2018-09-06 13:24:21,981: INFO: Now connect via WiFi to your Sonoff device. 2018-09-06 13:24:21,981: INFO: Please change into the ITEAD WiFi network (ITEAD-100001XXXX). The default password is 12345678. 2018-09-06 13:24:21,981: INFO: To reset the Sonoff to defaults, press the button for 7 seconds and the light will start flashing rapidly. 2018-09-06 13:24:21,981: INFO: This application should be kept running and will wait until connected to the Sonoff... 2018-09-06 13:25:09,286: DEBUG: Current IPs: ['192.168.1.105', '10.10.7.2'] 2018-09-06 13:25:09,320: DEBUG: ~~ Connection attempt 2018-09-06 13:25:09,321: DEBUG: >> HTTP GET /10.10.7.1/device 2018-09-06 13:25:15,279: DEBUG: << { 2018-09-06 13:25:15,279: DEBUG: "apikey": "420088dc-853f-474b-adbe-35cedcff1f9e", 2018-09-06 13:25:15,281: DEBUG: "accept": "post", 2018-09-06 13:25:15,281: DEBUG: "deviceid": "100037c910" 2018-09-06 13:25:15,281: DEBUG: } 2018-09-06 13:25:15,282: DEBUG: >> HTTP POST /10.10.7.1/ap 2018-09-06 13:25:15,282: DEBUG: >> { 2018-09-06 13:25:15,283: DEBUG: "serverName": "192.168.1.195", 2018-09-06 13:25:15,283: DEBUG: "version": 4, 2018-09-06 13:25:15,284: DEBUG: "password": "****", 2018-09-06 13:25:15,284: DEBUG: "ssid": "mesab0ogie_2.4G", 2018-09-06 13:25:15,285: DEBUG: "port": 8443 2018-09-06 13:25:15,285: DEBUG: } 2018-09-06 13:25:17,681: DEBUG: << { 2018-09-06 13:25:17,682: DEBUG: "error": 0 2018-09-06 13:25:17,682: DEBUG: } 2018-09-06 13:25:17,683: INFO: ~~ Provisioning completed 2018-09-06 13:25:18,598: INFO: Starting stage2... 2018-09-06 13:25:18,627: INFO: The IP address of (192.168.1.195) is not assigned to any interface on this machine. 2018-09-06 13:25:18,627: INFO: Please change WiFi network to mesab0ogie_2.4G and make sure 192.168.1.195 is being assigned to your WiFi interface. 2018-09-06 13:25:18,628: INFO: ** This application should be kept running and will wait until connected to the WiFi... 2018-09-06 13:25:32,829: DEBUG: Current IPs: ['192.168.1.105', '192.168.1.195'] 2018-09-06 13:25:32,830: INFO: ~~ Starting web server (HTTP port: 8080, HTTPS port 8443)

sillyfrog commented 6 years ago

Try using the "run" prompt (or cmd.exe), and then dragging the file in, and adding --no-prov to the command. This assumes you are at the "FinalStage" SSID - but based on that log, it didn't get that far, so you just need to restart the process from scratch and, providing the firmware is still old enough, and the flash type is OK, you should be away.