UNITREE G1 EDU MODEL

Controllers
1

G1 EDU (29 DoF) won’t stand after update — only damping works, remote + app can’t connect

Hi, hoping for some help diagnosing a G1 EDU that stopped working.

Symptoms

  • Robot will not stand. Only damping responds on the remote (L2+B works). L2+UP and R2+A do nothing.
  • Handheld remote won’t regain control (DL link not establishing).
  • Explore app won’t connect in either AP mode or Wi-Fi mode.
  • SDK / terminal commands from the dev PC all time out.
  • Battery is healthy (3/4 LEDs). Problem persists after a full clean cold boot.

What I checked over the wired network (SSH into the onboard dev PC)

  • The onboard dev PC is fully healthy: networking, DDS, and the OTA service are all normal.
  • The internal motion controller responds to ping but refuses SSH.
  • The low-level state estimator comes up but publishes no data — the lowstate topic has 0 publishers / 0 Hz, and the estimator process then exits.
  • No locomotion/motion-control process is ever present. The higher service layer (motion switcher, robot_state, voice, hands) is up, but the low-level layer below it never starts.
  • A firmware update appears staged but not applied (a newer version package is sitting in the update folder while the running version is still the older one).

My read

This looks like the internal low-level estimator/control stack failing to start, likely after an interrupted firmware update — which matches other post-update “won’t stand, only damping responds” cases I’ve seen on this forum. Damping works because it’s the lowest level; everything above it never initializes.

Questions

  1. Is this a known post-update failure on the G1 EDU?
  2. Should the staged update be completed or rolled back, and what’s the safe way to do that?
  3. If not recoverable that way, can you arrange a recovery image / correct firmware (or SD card) through Unitree?

I have not attempted any manual firmware flashing, since the forum consistently warns against it.

Purchase details

  • Model: G1 EDU, 29 DoF

Happy to share the detailed terminal diagnostic logs privately if that helps. Thanks in advance.