Hey everyone,
I was so excited when my uConsole finally arrived. I assembled it, started exploring, and decided to try cellular connectivity by inserting a SIM card. That’s when things started going wrong.
The 4G expansion module came with outdated firmware that didn’t support SMS or voice calls. I followed the official GitHub instructions to update it but midway through the process, the module suddenly disconnected from USB and never came back. Completely bricked.
I know firmware updates are risky second only to BIOS flashing in terms of fear factor. I was nervous about it, and unfortunately my fears came true. What I don’t understand is: why ship a product with outdated firmware in the first place? These things should come pre-flashed with the latest version.
To make matters worse, recovery via UART is theoretically possible but the debug interface uses an FPC connector, not a pin header. That makes it nearly impossible to work with for most users. A pin header would have made maintenance so much more accessible.
After that, things seemed stable for a while until the uConsole suddenly powered off completely. I opened it up and tested the battery cells: 4.2V, perfectly normal. Then I started probing the mainboard with a multimeter. I found that Q101 was running abnormally hot, and the power circuit connected to the battery had failed. The AC side was fine, so I’m currently limping along on adapter power only.
All of this happened within less than 2 weeks of receiving the unit.
I’ve already contacted support at help@clockworkpi.com. I’m hoping for a replacement, but I wanted to share this here too in case anyone else has experienced similar issues — and to ask if anyone has advice.
One more thought on hardware design:
The exposed power circuitry is a bit concerning. If a metal tool accidentally contacts that area during assembly or maintenance, a short circuit could cause further damage. I’d suggest considering an insulated aluminum cover over that section in future revisions it would not only protect against accidental shorts, but also act as a heatsink for the components underneath, potentially preventing heat-related failures like the one I experienced.
Would love to hear if anyone else has had similar issues or found a workaround.
That’s sucks. I just had mine cancelled by alex@clockworkpi because I asked if a refund was possible. He misunderstood and we argued and now I don’t even know if I will get my money back. I’m buying one off Aliexpress. They have thousands of them and single customers have to wait over half a year. This project has been managed terribly by them imho.
there were no reports that anyone didn’t receive unit or money back.
Thanks that’s good to hear.
Thanks for the reply, and sorry to hear you’re going through something similar.
Honestly, the support situation is what worries me most right now. Coming from Japan, I’m used to customer support that responds quickly and reliably it’s kind of a cultural standard here. So dealing with overseas support that might just… not reply, is genuinely stressful. I can live with a small team and slow responses, but being left in the dark entirely is rough.
I really do love this project the concept, the open hardware philosophy, the whole vibe. But now that I’ve actually gotten my hands on one, some of the design choices are starting to raise eyebrows. It’s the kind of thing you only notice once you’re in the thick of it.
Anyway, hoping things work out for both of us. Let’s see how support responds.
I’m sorry you’re having so much trouble, but the uConsole is really designed for experienced hackers rather than beginners.
When performing a firmware update, fear is a worse companion than caution.
Like any electronic system, the uConsole should only be powered on when short circuits have been ruled out.