-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
need new version! #24
Comments
joining, could be great to get! |
Any updates on this? |
Same issue here |
+1 ... have a basically useless Bose 700nc right now. Mine is a demo set (has the screw in the right earcup) so not sure if going to 1.3.1 i smart, but i've tried "rebooting" the set several times with no success. |
If you're desperate, you can get the current updater working again by using HTTP Toolkit to intercept the responses from the updater app when the "webapp" queries its version string and manually set it to |
No luck… got as far as being able to intercept the version request, but by the time I’m able to retrieve the token and paste a response, the cycle has started all over again on the Bose side. If you’ve actually done this or have some sort of instruction, I’d love to hear what I’m doing wrong. Meanwhile, two expensive aluminum bricks in the form of a Soundlink Mini 2. I should add, I also tried the Charles Proxy method mentioned in other threads, and while I can see the most recent 2 firmware versions, I receive the dreaded “No Dice” response, indicating I’m already on the current version. I would love to get these speakers working again, and am up to try just about anything, short of paying Bose $, to do so. Any help, or an updated version of the installer which actually allows a downgrade, or re-update of the current firmware on the Bose Soundlink Mini 2, would be greatly appreciated. |
it's 7.0.27.4971 now!thanks!
The text was updated successfully, but these errors were encountered: