RoboRollBack

Independent guides for robot mower owners

Not affiliated with or endorsed by any device manufacturer. All trademarks belong to their respective owners.

← All guides

LUBA mini 2 (1500 LiDAR): firmware 1.30.25.16 — NetRTK disconnected, stuck in Single positioning

Models covered
LUBA mini 2 AWD (1500 LiDAR)
Rolling back from
1.30.25.16
Last verified
3 September 2026
Before you start: confirm your mower's current firmware version and note it down. If this rollback doesn't go as planned, you'll want that number to ask for help.

What was reported

An owner on r/MammotionTechnology reported a LUBA mini 2 (1500 LiDAR variant — originally posted as "LUBA mini," corrected by the poster in comments) stuck in "Single" positioning mode, refusing to mow. All mapped lawn channels had disappeared even though the lawns themselves were still defined, and the charging station shown in the app no longer matched its real position. Confirmed details from the post:

  • Positioning Status: Single
  • RTK / iNavi Signal Quality: None (L1 0 | L2 0)
  • Mower firmware: 1.30.25.16
  • Companion app version: 2.3.12.11
  • Both WiFi and 4G showing full signal (3/3 bars) — not a connectivity problem on the mower's end
  • A power-cycle (holding the power button until "powering off," then back on after 10-15 seconds) did not resolve it

Related context

A separate, unrelated owner of the same LUBA mini 2 AWD line reported deliberately never updating away from the out-of-box firmware (2.3.27.0), specifically citing "the horrible recent updates" as their reason, and reporting zero issues after several weeks of use. That's not proof this specific NetRTK issue is tied to 1.30.25.16, but it's a real, dated data point that some owners on this model line are avoiding updates altogether right now.

Rollback procedure

Follow the general Android rollback guide.

Prior known-good version not confirmed. We don't yet have a confirmed firmware version to target as "the one before 1.30.25.16" for this model. This targets the mower's own body firmware, which our research has not found a confirmed manual downgrade path for regardless — see the Android guide.

Sources