[BUG] Galaxy Buds 2 Pro firmware downgrade fails: progress completes but earbuds disconnect and revert to latest firmware

[Zakariaboudelaa]

Describe the bug
Attempting to downgrade Galaxy Buds 2 Pro firmware using GalaxyBudsClient always fails at the final stage.
The firmware transfer completes (progress reaches 100%), but the earbuds disconnect/reboot and remain on the latest firmware version. No explicit error is shown in the application.

To Reproduce
Steps to reproduce the behavior:

Pair Galaxy Buds 2 Pro with the PC via Bluetooth

Open GalaxyBudsClient

Load an older official Samsung firmware for Galaxy Buds 2 Pro

Start the firmware downgrade process

Wait until progress reaches 100%

Earbuds disconnect/reboot automatically

Reconnect earbuds and check firmware version

Expected behavior
The earbuds should successfully install the selected older firmware version and report the downgraded firmware after reboot.

Actual behavior
The progress bar reaches 100%, but the earbuds disconnect at the final commit stage and reboot.
After reconnecting, the firmware version is unchanged and remains the latest version.

Additional context
Issue occurs consistently with Galaxy Buds 2 Pro on the latest firmware

Same behavior observed when attempting downgrade via Android (progress completes but firmware does not change)

On Windows 11, earbuds often disconnect during or immediately after the final flashing stage

This may indicate firmware-level anti-rollback protection silently rejecting the downgrade while the client reports a successful transfer

[asmar01ali]

found any solution?
same issue

[nup34p]

I just bought the app and... Same issue.

[schaffertaden-crypto]

I had this same issue. I installed the older version of the Buds Client: 4.5.3 Pre-release. Then you will need to manually find the firmware for your buds on this page: https://github.com/ThePBone/galaxy-buds-firmware-archive (you can find the model number on your phone in Samsung Find, then Device Settings, then About earbuds). After this, you should be able to downgrade your Buds 2 Pro.

[asmar01ali]

Thanks man... i will try and responsed back

I had this same issue. I installed the older version of the Buds Client: 4.5.3 Pre-release. Then you will need to manually find the firmware for your buds on this page: https://github.com/ThePBone/galaxy-buds-firmware-archive (you can find the model number on your phone in Samsung Find, then Device Settings, then About earbuds). After this, you should be able to downgrade your Buds 2 Pro.

[nup34p]

I had this same issue. I installed the older version of the Buds Client: 4.5.3 Pre-release. Then you will need to manually find the firmware for your buds on this page: https://github.com/ThePBone/galaxy-buds-firmware-archive (you can find the model number on your phone in Samsung Find, then Device Settings, then About earbuds). After this, you should be able to downgrade your Buds 2 Pro.

Thx mate! Maybe you know how to get an old mobile version? I bought it on Google Play precisely cause I don't have a PC with BT :(

[schaffertaden-crypto]

Yea, this app hasn't been updated in a long time, and something happened to the newer versions. For the google play version, I would recommend trying to get a refund. I am not aware of a way to get an older version. I would recommend getting a bluetooth usb dongle in the meantime.

[asmar01ali]

I had this same issue. I installed the older version of the Buds Client: 4.5.3 Pre-release. Then you will need to manually find the firmware for your buds on this page: https://github.com/ThePBone/galaxy-buds-firmware-archive (you can find the model number on your phone in Samsung Find, then Device Settings, then About earbuds). After this, you should be able to downgrade your Buds 2 Pro.

hey man i tried pc version galaxy buds manager 4.5.3 but same issue.. is there any other version i can try... i am stuck with latest frimware and it have awafull ANC in older frimware it was too good.

[tikkamasalla]

I had this same issue. I installed the older version of the Buds Client: 4.5.3 Pre-release. Then you will need to manually find the firmware for your buds on this page: https://github.com/ThePBone/galaxy-buds-firmware-archive (you can find the model number on your phone in Samsung Find, then Device Settings, then About earbuds). After this, you should be able to downgrade your Buds 2 Pro.

hey man i tried pc version galaxy buds manager 4.5.3 but same issue.. is there any other version i can try... i am stuck with latest frimware and it have awafull ANC in older frimware it was too good.

The new version works fine for my buds 2 pro.

[asmar01ali]

I had this same issue. I installed the older version of the Buds Client: 4.5.3 Pre-release. Then you will need to manually find the firmware for your buds on this page: https://github.com/ThePBone/galaxy-buds-firmware-archive (you can find the model number on your phone in Samsung Find, then Device Settings, then About earbuds). After this, you should be able to downgrade your Buds 2 Pro.

hey man i tried pc version galaxy buds manager 4.5.3 but same issue.. is there any other version i can try... i am stuck with latest frimware and it have awafull ANC in older frimware it was too good.

The new version works fine for my buds 2 pro.

In downgrading? And on which host window, Mac, Linux or android... Please explain

[Zakariaboudelaa]

I had this same issue. I installed the older version of the Buds Client: 4.5.3 Pre-release. Then you will need to manually find the firmware for your buds on this page: https://github.com/ThePBone/galaxy-buds-firmware-archive (you can find the model number on your phone in Samsung Find, then Device Settings, then About earbuds). After this, you should be able to downgrade your Buds 2 Pro.

hey man i tried pc version galaxy buds manager 4.5.3 but same issue.. is there any other version i can try... i am stuck with latest frimware and it have awafull ANC in older frimware it was too good.

The new version works fine for my buds 2 pro.

In downgrading? And on which host window, Mac, Linux or android... Please explain

You should use a bluetooth 4.0 device as a workaround. It will not work with blutooth 5.x or greater