AqaraDoorbellG4 icon indicating copy to clipboard operation
AqaraDoorbellG4 copied to clipboard

Latest firmware(s) (partially) restricted UART access?

Open fonix232 opened this issue 11 months ago • 6 comments

My G4 is on the latest firmware - unfortunately I've only recently found this repo so it didn't even occur to me to keep it on the lowest possible version.

I've soldered the appropriate test points, verified cable integrity and continuity (none of the three are shorted to the others, both Rx and Tx test points and cable ends show a ~3.3V difference to Gnd), and hooked it up to my know to be good serial adapter, with PuTTY as per the documentation.

While pressing Enter does seem to interrupt the boot process - based on the LED, which stays yellow - however I'm getting absolutely no output from any command I enter. I can see that the commands are being executed - for example if I enter run bootcmd, even though there's no output through the terminal, the chime continues the boot process, obvious from the LED changing to blue, beginning to blink (looking for WiFi or possibly the doorbell itself), then settles on static blue LED.

I've tried re-soldering the pad thinking I've messed it up, but no, even with the cleanest solder joints and as per above verified cable status. Unfortunately executing the guide's commands results in no change, and since there's no visible output, I can't confirm if the given commands even run properly or not. What I know for sure is that I get no telnet client on startup.

HW Rev.: 1.1 Firmware version: 4.0.6

fonix232 avatar May 18 '25 21:05 fonix232

Check your connection of UART. It shall logs out while booting.

niceboygithub avatar May 20 '25 03:05 niceboygithub

I was getting absolutely no output on UART. Turns out that the model I have was missing one of the resistors next to the UART pins - a quick solder bridge fixed the issue and I managed to hack my unit successfully.

fonix232 avatar May 23 '25 00:05 fonix232

What software version does your Aqara G4 have? I'm on the latest version (firmware-version:4.0.6_0044.0092), I can connect via UART, and I can see the boot log, but Uboot doesn't interrupt when I hold down the enter button.

Gerrett84 avatar Jun 26 '25 20:06 Gerrett84

@Gerrett84 I'm also on latest firmware, as per my initial post (same 4.0.6 version).

Does your G4 react to any input after boot? If not then your board too is missing one or more resistors. Please see the image in this repo you'll see that below the 3 UART pins, are 4 resistors (they're near 0 ohm, so you don't have to worry about direct replacement, a solder bridge will work). In my case, one of them was missing, on the Tx pin.

Image

fonix232 avatar Jul 01 '25 11:07 fonix232

Does your G4 react to any input after boot? If not then your board too is missing one or more resistors. Please see the image in this repo you'll see that below the 3 UART pins, are 4 resistors (they're near 0 ohm, so you don't have to worry about direct replacement, a solder bridge will work). In my case, one of them was missing, on the Tx pin.

Yes, it react to input, but doesn't canceled uboot. Just checked it und found 4 resistors.

Gerrett84 avatar Jul 03 '25 18:07 Gerrett84

Unfortunately with that I cannot help much. For me the best tactic was doing the following:

  • Plug UART adapter into host machine and connect pins
  • Open UART terminal
  • In said terminal, press and hold the Enter key
  • Plug in power supply for doorbell

fonix232 avatar Jul 04 '25 12:07 fonix232