After you enter the bootloader, you have to enable rootfs check, then reboot
Your gateway should enter a normal booting process, and discover that main rootfs failed, switch to backup rootfs.
At that moment, you can telnet to your device, then issue dd command to restore your backup
After you finished dumping backup back to mmcblk, disable rootfs check, then reboot again.
You should check post #103 by @serrj-sv, as he already described the whole un-bricking process.
Also, if it’s possible, can you provide more information regarding your issues?
For example, the error logs you’ve seen?
Or any screenshots, so we can know which stage you’re at right now.
Remove integration and reconnected gw with new token, but only Ble devices appeared, the zigbee does not show, although they are displayed in the mihome
I’ve noticed an interesting thing: I’ve connected to the device with chinese region: integration worked well, could add other devices (ikea bulb), etc…
I connected to the telnet with putty.
Then I decided to try the same with European region, because the Chinese server is quite slow to respond… Initiated pair mode (long pressed the button), set the phone app to china, etc. Paired with the phone successfully. Then I looked at the telnet connection, and suprisingly it was still open. When I power cycled the device, couldn’t connect to it with telnet any more.
Before restarting the device, I could interact with it through the home assistant integration. I even could pair new devices too…
So i wonder if this trick could help to figure out how to connect to devices, if not China was selected.
It would be cool, if it would work with other regions, because the server delay could be minimized this way.
Maybe a linux guru could dig something. Eg. modify system files, to keep telnet open after restarting the device, would be enough…
No, the IP is the same, because is set it static lease in the router, so it always get the same address…
It seems that when you pair the ZNDMWG03LM with your phone, it uploads some kind of configuration over bluetooth, which determines the behavior of the device, i.e., whether or not to open the telnet option…
As I experienced, after region change from chinese to europe and re-pairing the device, the original (chinese) token was alive till power-cycling the device, and telnet connection as well. After that the token changed, and couldn’t connect to it anymore, even if I deleted and reinstalled the integration, and walked through the initial setup process (get token from online account, then added local ip with token…)
As I mentioned above, integration only works with selecting the Chinese region, because the initial pairing process with the phone application uploads certain configurations that allow telnet connectivity only for the Chinese region.
Tip: Those who have global version (i suppose it’s ID is ZNDMWG02LM), should try to set china region in phone app, before first pairing the gateway with the phone, maybe that could unlock telnet possibility for them too…
It’s 1.4.6_0012.
By the way, the integration is working well, I can use everything with home assistant, and with xiaomi home app parallelly, which is very cool feature.
I tried that option first, but didn’t worked for me. First, I’ve selected europe region when paired the phone with the gateway. Then the miio command didn’t worked (Устройство 192.168.1.xxx не доступно или не отвечает.). After that changed the phone app region to china mainland, re-paired the device, and everything working now.
With china region, the miio command also worked (just checked to be sure), returned: {“code”:0,“result”:[“ok”],“id”:0})
Information sharing :
If firmware version of your gateway is 1.47_0063, the new feature “auto upgrade firmware (only in China region)” was added in it.
I also upgraded the firmware before i read this forum… but mine was upgraded to 1.4.6_0012. I selected Hungary (Euorpoe) region in the app for first try. Then later changed to china… This was 3 days ago.
I was lucky with it. Perhaps you shall try to select other regions, then redo the pairing process - but I think it won’t downgrade the firmware anyway…
