tchebb
Question: Noted differences regarding flashing SoundLink Mini II with bose-dfu vs official btu website
I have a SoundLink Mini II that its rather bug. Every time the battery completely discharge, it enters the famous "blinking red light" mode, in which it does not charge. I have read that its a "shipping mode" for protecting the battery from absolute discharge thus harming the battery life.
The thing is... Last time I tried flashing it with bose-dfu and the firmware updated successfully, downgrading or upgrading worked fine, at least in regards of the firmware state being updated. But the "shipping mode" remained. So... I was able to flash the speaker but not force it out of the obnoxious "shipping mode".
Afterwards I got to use a friend's Mac for flashing it via bose btu, which made the speaker functional but rather buggy: sometimes, even it was "turned off" the yellow light persisted, then fixed itself and so forth.
I'll go now there again to try bose-btu "error leaving combination" O, P, T, Up, Down and update here what I came to.
It might has to do with #6?
In any case, it would be nice if I could make the speaker leave the dreadful mode without the need for using the official btu tool
If you need something from me just let me know, I might be able to usb scan or so if needed (better if with guided instructions)
Could you be suffering from the likes of https://www.reddit.com/r/bose/comments/kvo0yn/bose_qc35_turning_on_by_itself_bose_will_replace/ on the mini? That would cause the headset to spontaneously power on and subsequently unnoticed drain the battery -- jiving well with your description and the symptoms I experience from the issue on my QC35.
I think its not the same. I never noticed it turning itself on. Maybe sometimes not looking like quite powering off fully. Mostly the yellow light but every other symptom looks like it actually power off.
If I don't let the battery run away, it's quite ok. But just a matter of letting it go to 0% and it enters this aforementioned state
In any case I would contact Bose Support. Thanks!
Hi, I had a similar problem and was able to "upgrade" to 1.1.3 and then use the Bose site to upgrade back to 1.1.4 which also resurrected it. I captured traffic through USBPcap by just setting it to capture new devices only and then plugged it in - here's the pcapng, disguised as a .dmp
I had a similar problem and was able to "upgrade" to 1.1.3 and then use the Bose site to upgrade back to 1.1.4 which also resurrected it.
For me that worked twice... the third time it happen (got back to red blinking each time the battery got drained) it didn't work anymore