Helium Desktop

Helium Desktop is the computer half of a two-part Android backup system, and it does exactly one thing. The Helium app on the phone can copy an app’s saved data, game progress, settings and logins, to the phone’s storage or a cloud account and restore it later, even onto a different handset.

But a phone that has not been rooted will not let an app do that on its own. It needs the permission switched on from outside, over a USB cable, by a computer running the Android Debug Bridge. That is what this program does.

Every other route to the same result involves rooting the phone or a paid transfer suite. Helium Desktop is the no-root answer, and for years it was the only one worth having. Three things temper that.

The permission it flips resets after every reboot, the debug bridge it ships with is old enough to fail on current phones, and the newest Android releases have removed the backup mechanism it relies on.

What happens when you plug the phone in

The program installs a bundled copy of adb, the command-line tool that talks to Android devices, and a universal driver so the computer sees the phone as a debug device.

On the phone you enable USB debugging in the hidden debugging settings, usually switch the USB mode to PTP rather than file transfer (the app is fussy about this and says so), connect, and accept the “allow USB debugging” prompt.

The desktop window then reads Connected, the Helium app on the phone reports that backups are enabled. Rooted phones skip this whole dance, though a one-click rooting tool is its own gamble.

Android drops the backup permission when the phone restarts, so a phone that has been turned off needs the cable and the program again before it will back up.

When the window refuses to say Connected

Most failures come from the bundled adb, not the phone. The copy inside the program’s win32 folder is several generations behind, and a phone running anything recent answers it with an “adb server is out of date” refusal or simply never appears. The fix regulars pass around is to drop three files, adb.exe and the two AdbWin DLLs, from a current platform-tools package over the bundled ones.

They ship inside the full Android development kit or as a small standalone package.

Driver clashes and the unauthorized prompt

Driver clashes are the other cause, and Helium Desktop cannot tell you which one you have. The universal driver the installer sets up can override a maker’s own driver, and some phones only respond to their maker’s.

Uninstall one, install the other, and check with “adb devices” at a command prompt before blaming this program. If it lists the phone as “unauthorized”, the debugging prompt on the phone was dismissed and needs accepting again.

What can and cannot be backed up

Once enabled, the phone app lists installed apps with a tick box each and a choice of app data only or data plus the installer file. Backups go to internal storage, an SD card, or a linked cloud account, and a backup made on one phone restores on another, which is the whole reason for the exercise when moving handsets.

Any app whose maker has set the no-backup flag is greyed out, and that list includes most large-name apps and several popular games. Some phone brands block the mechanism entirely and the app tells you so at first launch. And Android itself deprecated the underlying adb backup command a few releases ago, so on a current phone the desktop program may connect perfectly and the backup still fail.

For those phones a transfer tool such as AirDroid copies files and media but not app data, which is the one thing this pairing was for.

Conclusion

Helium Desktop is for someone with an older, unrooted phone who wants to carry game saves and app settings to a new handset or keep them safe before a reset. For that person it does a job nothing else does without root, once the adb file swap and the PTP quirk are understood.

Owners of recent phones should test it before relying on it, because the ground has moved underneath it. When it fails, the fault is almost never in this window and almost always in the three files behind it.