Even with the modified EXE, downgrades are now blocked

[misterblack1]

I'm trying to revive a dead Soundlink Mini II (red flash battery icon) by downgrading to 1.1.3. Using the modified BOSEUPDATER.EXE and setting a breakpoint on the updater page to bypass the version check, I am able to see 1.1.3 in the drop down when in advanced mode, but trying to update the speaker results in the attached error.

The log file shows it is hitting this repo to grab the firmware, which is why it's showing 1.1.3 (otherwise it won't show up)

I assume BOSE introduced yet another check to prevent downgrading. They are actively trying to stop this, which is super infuriating!

I've been poking around in app.js trying to figure out how to bypass this, but my expertise level on Javascript is just slightly above rudimentary.

1/7/2024 12:14:58.236,  Info,       Bose Updater startup ver .0.13.4860
1/7/2024 12:14:58.243,  Info,       Loading translations
1/7/2024 12:14:58.243,  Info,       Loaded locale: en, suffix: en, result = false
1/7/2024 12:14:58.244,  Info,       Starting web server
1/7/2024 12:14:58.247,  Info,       Listening on port 49312
1/7/2024 12:14:58.247,  Info,       Loading settings
1/7/2024 12:14:58.247,  Info,       Creating notification icon
1/7/2024 12:14:58.247,  Info,       Tray available: 1
1/7/2024 12:14:58.247,  Info,       Loaded icon: 1 :/images/favicon.png
1/7/2024 12:15:40.369,  Error,      Called method getCurrentDevicesConnected without a session
1/7/2024 12:15:40.538,  Info,       LOOKUP FILE download: https://cutt.ly/git-hub-bose-firmware-files
1/7/2024 12:15:40.806,  Info,       LOOKUP FILE redirecting: https://raw.githubusercontent.com/bosefirmware/ced/master/lookup.xml
1/7/2024 12:15:40.823,  Info,       LOOKUP FILE successfully downloaded.
1/7/2024 12:15:59.549,  Info,       INDEX FILE  = https://raw.githubusercontent.com/bosefirmware/ced/master/kcup/index.xml
1/7/2024 12:15:59.567,  Info,       INDEX FILE successfully downloaded.
1/7/2024 12:16:00.676,  Info,       Internal version is 1.1.4.3558
1/7/2024 12:16:00.676,  Info,       External version is 1.1.4.0
1/7/2024 12:16:00.676,  Info,       Device version is 1.1.4.3558
1/7/2024 12:16:00.832,  Info,       Current voice prompt language is en-us

[misterblack1]

I tried editing the JS to make it think the speaker was v1.0.1 (tried a couple others too) and while it shows up and wants to update, I still get the "No Dice"

There is stuff in the JS for downgrading the speaker.... if only we could find out how to enable that. Perhaps the BOSEUPDATER.EXE needs those commands to do that?

[Roieeeeee]

Hey, I've found a new method now, and yeah, it's paid, but don't worry, it's super cheap. If you're interested, just hit me up at [email protected]. Make sure to include your Bose model and firmware, and I'll hook you up with some remote tech support.

[vogelh0ws]

I created a post on X regarding this. Share if you like. This planned-obsolescency behavior totally bothers me.

The problem with the red-flashing charging indicator on my Bose SoundLink II happened to me for the second time. The first time I had it repaired by Bose for $55. I am not willing to pay again, if the repair just takes a couple of minutes with the appropriate SW and I need to expect that it breaks again after 2 years.

https://x.com/vogelh0ws/status/1795786130022904151

I have the impression that X even restricted my reach after I interacted with Bose.