Software rollback on Android: what's actually possible

App version: confirmed rollback path

The Mammotion Android app isn't Google Play-exclusive-locked the way some apps are. Older versions are mirrored on third-party APK archive sites, which is the real, working path if a specific app update (not a firmware update) is what broke something for you:

1. Note your current app version from the app's About/Settings screen.
2. Uninstall the current app version (back up any local data the app doesn't sync to your Mammotion account first).
3. Download the previous known-good version from an APK archive: Uptodown, APKPure, and APKCombo each maintain a browsable version-history page for Mammotion's app^{1, 2, 3} (individual version listings aren't independently confirmed). See the Android app version history for a dated list of what's been mirrored so far.
4. Install the downloaded APK (you'll need "install from unknown sources" enabled).
5. Disable automatic app updates in the Play Store for this app until you're ready to move forward again.

Mower body firmware: no confirmed manual rollback path

This is different, and important to be upfront about: no official or reliably-documented way to manually downgrade the mower's own body firmware exists. It's pushed over-the-air and, unlike the RTK reference station (which does have an official manual tool), Mammotion doesn't publish a sanctioned manual flashing path for the mower body itself. Asked directly, Mammotion's own position is the same as ours: an owner who asked to be taken back to an earlier firmware published Mammotion support's reply in their thread: "Mammotion does not currently support user-initiated firmware downgrades"⁵. So the "no downgrade path" conclusion is not just what owners have observed: it is the manufacturer's stated position, quoted publicly as of September 13, 2026. A company-named Mammotion account said it again on 5 October, to a LUBA 2 AWD owner who had written about the app and firmware trouble: "at this time, rolling back to a previous version is not supported"¹⁰. That is the same position, stated a week after one owner posted that support had pushed an older build to their mower (see the bullet on pressing support, below). In August a Mammotion staff account had been more specific about why. It wrote that the company can technically provide a firmware rollback, but iOS owners cannot get the previous app, and the new firmware creates files the old firmware and app cannot deal with. Its answer is a new, more reliable firmware rather than a list of old ones to choose from¹¹.

Rolling the app back does not roll the mower back, and one owner tested exactly that. A LUBA 3 owner who wanted the old multi-point turn downgraded the Android app to 2.3.12.11: the multi-point turn option came back on screen, but the mower kept "doing a hybrid MPT / tank turn, with emphasis on tank"⁶. The turn only improved once the mower itself received firmware 2.3.30.39, after the owner had put the current app back and support had escalated a ticket about the missing update⁶. The app decides which options you see; the mower's firmware decides how it moves.

Holding the firmware back is what kept the turn, in the one case we have of it working. A LUBA 2 AWD 3000H owner switched off automatic app and firmware updates when owners began reporting in July that the multi-point turn had gone, though not before their iPhone app had updated. They moved to an Android phone with the app rolled back, and because the mower itself had not yet updated, it kept the multi-point turn. They now run firmware 1.30.29.8 with Android app 2.3.12.11⁹. One owner's report, not yet confirmed by another. It is the LUBA 3 case above seen from the other side: the same app version, but the firmware held back, so the turn stayed. Two costs come with it. The same owner finds the Android app buggier, with many more connection problems than on their iPhone⁹. And because you cannot roll the mower's firmware back yourself, this only works if you stop the firmware update before it installs.

In practice, when a mower-body firmware update has broken something, the realistic options found so far are:

• Wait: there's at least one documented case (see the multi-point turning report) of Mammotion restoring removed functionality in a later release rather than owners having to revert anything.
• Report the fault via Mammotion's own support channels and the community (roboter-forum.com, r/MammotionTechnology) to add pressure and confirm you're not alone in seeing it.
• Press support for a revert: it has worked, but only for owners who refused to take no for an answer. Two owners report first-hand that support pushed an older body firmware to their mower after first saying no. A LUBA 2 5000 owner who kept asking "why not" got a build they date to April 2025 after about a week⁷. A Mammotion staff account answered that post, restated the owner's account of the downgrade, and asked for a device name or case ID so it could check its records; it did not say whether the downgrade had been authorised¹². A LUBA mini 2 AWD 1500 owner was told it was "not possible" several times, then got "the last version from June" back after four weeks, having told support they held written proof it had been promised and would take legal action⁸. Neither is a path you can take yourself, and both sit against Mammotion's own written "not currently supported"⁵: what support will do when pushed and what it says it supports are not the same thing. Name the exact version you want (the second owner picked it from the release notes as the last one before things went wrong), keep the conversation in writing, and expect to be refused first.
• Where the idea first surfaced, second-hand: in a Reddit thread (September 8, 2026), one commenter advised a LUBA 3 3000 owner stuck on a broken update to "tell support to remotely revert the firmware to a June version, then disable all auto-updates," adding that Mammotion "did it for someone else" and to be persistent about it⁴. This is secondhand (the commenter isn't describing their own case) and no version numbers or ticket outcome are given. It now sits against Mammotion's own flat "not currently supported" reply to the same kind of request⁵, so it doesn't meet this site's bar for a confirmed rollback path. A support-side remote revert, if real, would be a materially different mechanism than a user-side manual downgrade. A separate reply in the same thread cautions that Mammotion "can and have forced push updates even with auto-update off"⁴, which, if also true, would mean disabling auto-updates alone isn't sufficient to keep a reverted version in place. If you've asked support for a remote revert, tell us what happened: they did it, they refused, or anything in between. Two successes are not yet a policy, and refusals count just as much.