bosefirmware
New BOSEUPDATER.EXE version
Hi could you please patch 7.0x boseupdater version , bose no longer accepts the current patched one
up！Now it can't work and the website shows: There's a new version of the Bose Updater! The version you're running is out-of-date and won't let you access product updates. Download the newest version so you can get updates for all your Bose products.
Upvote :) It's head-shakingly-bad that Bose Support won't offer this option and that we need to resort to a hacked updater to simply have headphones that work without constantly rebooting. I'm grateful for your time in helping with this. Thank you.
Or - possibly share how you're changing the updater and some of us can help out as well.
[UPDATE] For anyone who needs to fix their headphones now before an update comes out, I was able to do it using Proxyman on the Mac. (People have also used Charles Web Debugging Proxy on Windows). Here's the configuration that worked in another issue thread: https://github.com/bosefirmware/ced/issues/4#issuecomment-808810756
To follow this discussion since indeed it does not work with Boseupdater 7.2.27 and my mic is not working anymore. for those who succeeded what firmware version did you select finally?
@bosefirmware Any new version available?
@chrisplough did you succeed to revert to older version than 2.5.5 (which is 'allowed' by Bose)
@chrisplough did you succeed to revert to older version than 2.5.5 (which is 'allowed' by Bose)
No - currently using 1.3.1, which is the latest stable release that works well with my headphones.
Side note - just wish I didn't have to use the Bose app to select active Bluetooth sources. Somehow I left it open it the headphones were just updated 1.8.2 (and continually crashing again) - so I'm re-downgrading to 1.3.1 now.
Thanks for the answer. What procedure did you use to downgrade?
if I understand you used Proxyman on Mac. Since I only have a windows machine I will need to look at 'Charles Web Debugging Proxy' if I am correct.
EXE is now UPX1 packed which isn't an issue. The issue is string for the lookup URL is not longer hard coded in the latest version 7.0.27. Will take some time to see where it gets the info from. Also Bose has moved some firmwares to AWS S3. Old updater string to replace was "http://worldwide.bose.com/connected_device"
In a nutshell, redirect https://downloads.bose.com/lookup.xml to goto: https://raw.githubusercontent.com/bosefirmware/ced/master/lookup.xml
Thanks
Forgot to mention that I have a QC35 (not the QC35II)
I succeeded to re-install version 1.0.0 but mic was still not working I am now trying other versions 1 by 1 in order to find one where my Mic is working again.
I see following versions 1.0.0 -> no Mic 1.0.3 -> no Mic 1.0.4 -> no Mic 1.0.5 -> no Mic 1.0.6 -> no Mic 1.3.2 -> no Mic 1.3.6 -> no Mic 1.5.1 -> no Mic 2.5.3 -> no Mic 2.5.5 official -> no Mic 3.0.3 official -> no Mic
start to feel depressed. Before they forced this stupid update i am sure my mic was working fine.
issue is that changing the firmware does not really reset the device since the list of paired device remains. Do you know a way to really reset the device?
My QC35 original has been sitting in my drawer since I got the NC700, but I do remember Mic wouldn't work on my computer's Bluetooth for a long time now, it did when I got the headphones, but don't recall when it stopped working so I started running on my internal Mic with software noise cancellation. Samsung S8 always worked with it;'s Mic (Fully updated firmware until Oct 2020 whatever it may be)
You can try: Power off your product Wait 30 seconds Connect your product to a wall outlet using a USB charger Wait five seconds Disconnect the USB cable from the headset Wait one minute Power on your product
QuietComfort 35 wireless headphones II -Reset - BOSE
EXE is now UPX1 packed which isn't an issue. The issue is string for the lookup URL is not longer hard coded in the latest version 7.0.27. Will take some time to see where it gets the info from. Also Bose has moved some firmwares to AWS S3. Old updater string to replace was "http://worldwide.bose.com/connected_device"
In a nutshell, redirect https://downloads.bose.com/lookup.xml to goto: https://raw.githubusercontent.com/bosefirmware/ced/master/lookup.xml
Also doesn't seem to work. I am using chrome-extension "redirector" to redirect the url. If I manually open a tab and try to connect to https://downloads.bose.com/lookup.xml it redirects me to https://raw.githubusercontent.com/bosefirmware/ced/master/lookup.xml
But after pressing the mentioned key combination it doesn't give me the possibility to flash another firmware version. I can only send some diagnostic information to bose. Do you have any idea how to solve this?
on windows I used 'Charles Web Debugging Proxy' and it worked fine, you can find instructions on how to setup that tool above.
Using Charles Web Debugging Proxy instead of the chrome extension worked fine indeed! Back on good old 1.3.1 again ;-) Thanks!
Using Charles Web Debugging Proxy instead of the chrome extension worked fine indeed! Back on good old 1.3.1 again ;-) Thanks!
May I ask for screenshots of your Charles mapping settings? After fiddling with the mapping and certificates I am getting this pop-up:
It looks exactly like this: https://github.com/bosefirmware/ced/issues/4#issuecomment-556381149
I used internet explorer/edge on windows 10. Did you import the root certificate (http://chls.pro/ssl) in the correct root ca store? Don't let windows choose the certificate store for you since it will pick the wrong one.
After configuring the Charles Web Debugging Proxy, I could see 1 older firmware version for my Soundlink Mini 2 that I couldn't see before. My SLM2 has a red flashing power light, which should be fixed by reapplying firmware. However, when I select the older version and try to apply that, I get the message "No Dice. There are no available updates for this product.". I guess the proxy redirects aren't enough to trick Bose into re-flashing and thus fixing my broken Soundlink Mini 2? Don't think I'll buy Bose again! :-(
Man this is seriously depressing. After fiddling with charles web debugging proxy I'm able to get into advanced mode however I can only see two firmwares one 3.0.3 the other 2.5.5. My unit is the original QC35. How the frick is bose not letting me go below 2.5.5??????? I thought only some QC35 II has this problem.
The bose headphones and speakers still have a lot of errors but no one else is here, it may be too late for me to ask someone how to fix the red white flashing error on my bose quietcomfort earbuds.
