White Screen after firmware update

I was on 1.0.11 and tried to update to the latest after getting a wifi expander. I kept getting checksum errors, so I tried installing earlier versions to work up to latest. It looked like it was loading one and then it failed and now is white screen and nothing happens when I hold down the encoder to try and use the USB to fix. Looked over different threads but couldn’t find anything that helped. Any ideas of things I can try? Not sure what to do if holding the encoder on startup doesn’t do anything.

I was downloading from Github and being careful to find ones that had same naming as the latest from Downloads.

Were you trying the method described here?

Yes. That is what I’ve been following to try and use USB to recover.

Do you know for sure that your USB cable will pass data?

So, when you power up with the encoder held down, watch the button light carefully. Does it flash blue? Does it turn green?
The answer will tell us at what stage it’s getting stuck.

There is another way to boot, which requires flashing an image onto an SD card and flipping a tiny DIP switch in the back. I’ll need to write up some documentation for how to do this.

Also, which versions did you load and what was the last one (that presumably failed)

The light stays off the whole time and the screen white. 1.1.1 I believe was the one that failed. It went through several stages of writing data in the firmware update.

I can see the device in Windows as DFU in HS Mode with no driver available in blutetooth & devices. It does not show up in the Connect dialog.

And you’re sure this is the MetaModule? That is, if you unplug and power down the MetaModule this DFU device goes away, and then it comes back if you plug the MM back in (with encoder held down)?

I’m asking because if the MetaModule light is not green, then it’s not in DFU mode (unless the light is broken I suppose?). When you used it before did you notice the light not being white (if green was broken it would be purple)?

But if you can see it in the Windows devices, then there’s hope that you can connect to it.
As someone else said: Make sure you are using a good quality USB cable that supports Data (many USB cables are for charging only, they will not support data connections). And make sure you are in Google Chrome.
Click the Connect button with the MetaModule unplugged and with it plugged in, and see if the list of the devices changes. It might be called something different on your system.

I’m preparing an image for SD card booting, which I’ve been meaning to do. So that can be a last-resort effort to restore the module.

Any updates?

Here’s the instructions for restoring the MetaModule using an SD Card:

I was able to fix it with that information and the restore file. Thanks!

1 Like

Great! Glad it worked.