Replies: 2 comments
Bose SoundTouch Portable — BatteryMonitor Patch for BOSE_A Replacement BatteriesDuring extensive testing with multiple replacement batteries for the Bose SoundTouch Portable, I discovered that many third-party batteries are electrically functional but rejected by the original This patch modifies the Bose are treated like the officially supported: battery personality. The result is that many compatible third-party replacement batteries can work properly again with full charging support and stable operation. Why this mattersBefore identifying the actual problem, I tested several replacement batteries. Some batteries caused severe issues such as:
One important warning sign was: If after replacing the battery:
then the battery is often unstable under load and should probably be returned. Many problematic batteries initially looked completely normal:
But under real load conditions they became unstable. Possible reasons include:
What this patch actually doesThe Bose firmware contains battery personality profiles. The original firmware expects: But many third-party replacement batteries identify themselves as: This patch changes the internal personality mapping so the firmware accepts: as a supported battery personality. The patch does NOT disable charging protections. It only changes the accepted battery personality identifier. Tested firmware versionThis patch was developed and tested ONLY on: Important compatibility warningThe patch directly modifies binary offsets inside: Because of this:
To prevent accidental corruption, the script checks the exact SHA256 hash before patching. Expected SHA256: If the binary differs, the script aborts automatically. Where the original BatteryMonitor binary is locatedOn the SoundTouch Portable: You can verify the checksum directly on the device: sha256sum /opt/Bose/BatteryMonitorSafety warningUse this entirely at your own risk. I am NOT responsible for:
Lithium-ion batteries can be dangerous if defective or improperly handled. This patch should only be used by experienced users who understand the risks. Always monitor charging behavior carefully after installing any replacement battery. If the device behaves strangely:
Tested replacement batteryThe following battery worked well during my testing: Purchased via Amazon / Akku-King. Other third-party batteries using the same: identifier may also work. Full all-in-one patch script#!/bin/bash
GREEN="\033[1;32m"
RED="\033[1;31m"
YELLOW="\033[1;33m"
BLUE="\033[1;34m"
NC="\033[0m"
EXPECTED_SHA="93b23730a3ac66f3331f63711d4a1d1d60704ccb03635b7ab8210c1f084f4fa0"
echo
echo -e "${BLUE}========================================${NC}"
echo -e "${BLUE} Bose SoundTouch Portable Battery Patch ${NC}"
echo -e "${BLUE}========================================${NC}"
echo
read -p "Enter SoundTouch IP address: " IP
SSH="ssh -oHostKeyAlgorithms=+ssh-rsa -oPubkeyAcceptedAlgorithms=+ssh-rsa root@$IP"
SCP="scp -O -oHostKeyAlgorithms=+ssh-rsa -oPubkeyAcceptedAlgorithms=+ssh-rsa"
echo
echo "Select action:"
echo
echo "1) Show current BatteryMonitor status"
echo "2) Apply BOSE_A patch"
echo "3) Restore original BatteryMonitor"
echo
read -p "Choice: " ACTION
show_status() {
TMPFILE=$(mktemp)
$SSH "strings /opt/Bose/BatteryMonitor | grep -E 'BOSE_A|BOSE_SANYO|BOSE_ICC'" > "$TMPFILE"
echo
echo -e "${BLUE}=== BatteryMonitor Status ===${NC}"
echo
if grep -q "BOSE_A" "$TMPFILE"; then
echo -e "${GREEN}PATCHED${NC}"
echo
echo -e "${GREEN}Third-party BOSE_A batteries supported${NC}"
echo
echo "Detected markers:"
cat "$TMPFILE"
else
echo -e "${RED}UNPATCHED${NC}"
echo
echo -e "${RED}Only original Bose/SANYO batteries supported${NC}"
echo
echo "Detected markers:"
cat "$TMPFILE"
fi
rm -f "$TMPFILE"
}
apply_patch() {
echo
echo "[1/8] Downloading BatteryMonitor..."
$SCP root@$IP:/opt/Bose/BatteryMonitor ./BatteryMonitor || exit 1
echo
echo "[2/8] Checking SHA256..."
ACTUAL_SHA=$(sha256sum BatteryMonitor | awk '{print $1}')
echo "Expected: $EXPECTED_SHA"
echo "Actual: $ACTUAL_SHA"
if [ "$ACTUAL_SHA" != "$EXPECTED_SHA" ]; then
echo
echo -e "${RED}ERROR:${NC} Unsupported firmware/binary!"
exit 1
fi
echo
echo -e "${GREEN}SHA256 verified${NC}"
echo
echo "[3/8] Creating patched binary..."
cp BatteryMonitor BatteryMonitor.bosea_as_sanyo
printf 'BOSE_A\x00NYO' | dd of=BatteryMonitor.bosea_as_sanyo \
bs=1 seek=$((0x4ecd0)) conv=notrunc
echo
echo "[4/8] Verifying patch..."
strings BatteryMonitor.bosea_as_sanyo | grep -E "BOSE_A|BOSE_SANYO|BOSE_ICC"
echo
echo "[5/8] Uploading patched binary..."
$SCP BatteryMonitor.bosea_as_sanyo root@$IP:/mnt/nv/
echo
echo "[6/8] Installing patch..."
$SSH << 'EOF'
mount -o remount,rw /
cp /opt/Bose/BatteryMonitor /mnt/nv/BatteryMonitor.backup.original
rm -f /opt/Bose/BatteryMonitor
cp /mnt/nv/BatteryMonitor.bosea_as_sanyo /opt/Bose/BatteryMonitor
chmod 755 /opt/Bose/BatteryMonitor
sync
EOF
echo
echo "[7/8] Final verification..."
show_status
echo
echo -e "${GREEN}PATCH SUCCESSFULLY INSTALLED${NC}"
echo
echo -e "${GREEN}BOSE_A replacement batteries are now supported.${NC}"
}
restore_original() {
echo
echo "[1/3] Restoring original BatteryMonitor..."
$SSH << 'EOF'
mount -o remount,rw /
cp /mnt/nv/BatteryMonitor.backup.original /opt/Bose/BatteryMonitor
chmod 755 /opt/Bose/BatteryMonitor
sync
EOF
echo
echo "[2/3] Verifying restore..."
show_status
echo
echo -e "${GREEN}Original BatteryMonitor restored.${NC}"
}
case "$ACTION" in
1) show_status ;;
2) apply_patch ;;
3) restore_original ;;
*) echo "Invalid option." ;;
esacUsageSave as: Make executable: chmod +x soundtouch_portable_bosea_patch.shRun: ./soundtouch_portable_bosea_patch.shFinal notesThis patch was created purely for repair and preservation purposes. The goal was to restore normal functionality with compatible replacement batteries after Bose original batteries became difficult and expensive to obtain. Please use responsibly and carefully monitor battery behavior after installation. |
Additional Findings About the BOSE_A Battery Patch and Charging BehaviorAfter longer testing and charge/discharge analysis I noticed several additional behaviors that were quite interesting. I wanted to share them separately because they may help others understand what the firmware is actually doing internally. The Patch Does NOT Disable Safety FeaturesOne important thing first: Even WITHOUT the patch I never observed dangerous charging behavior. The charging electronics inside the SoundTouch Portable regulate extremely precisely and remain very close to healthy lithium-ion operating limits. The patch does NOT disable:
It only changes the accepted battery personality mapping. What Changed WITHOUT the PatchWithout the BOSE_A patch I repeatedly noticed that the firmware appeared to continuously "adjust" or "re-check" charging behavior. A very strange symptom was: Several times per hour you could hear a subtle internal noise. The best comparison is: old FM radio interference noise when reception became unstable. My assumption is that the firmware continuously verifies whether:
match each other correctly. If they do not fully match, the firmware seems to repeatedly compensate or retry internal checks. Incorrect Battery Indicator WITHOUT the PatchAnother interesting observation: Without the patch, the battery level indicator shown after holding the power button for several seconds was permanently wrong. Even after:
the displayed charge state stayed incorrect. After applying the BOSE_A patch: the battery indicator suddenly behaved normally again. This strongly suggests that the firmware internally links:
directly to the battery personality. Different Discharge LimitsI also noticed different discharge behavior. Observed during testing:
The charging curve itself also behaved differently without the patch. So the firmware clearly appears to use:
depending on the detected battery personality. Charge Curve ObservationsWith the patched BOSE_A configuration the charging curve became much more stable and predictable. Example observations:
Example values from my testing: This behavior was significantly more stable than some earlier incompatible batteries I tested. About the Battery Logger ScriptTo analyze all this properly I created a long-term logging script for Linux. The script:
The goal was to better understand:
Final ThoughtsFor me personally this research answered the important questions:
At this point the patched configuration behaves very close to an original supported battery setup. I intentionally skipped publishing complete discharge and unpatched charge curves because for my own testing the important behavior differences were already confirmed. But maybe these findings still help others who are trying to repair or preserve their SoundTouch Portable devices. |
Uh oh!
There was an error while loading. Please reload this page.
What would you like to discuss?
Why a Bad Battery Can Seriously Affect Bose SoundTouch Devices
During extensive testing with Bose SoundTouch Portable devices, I tested a total of three different replacement batteries before finally finding one that worked properly and stable.
The differences between the batteries were surprisingly large.
Some replacement batteries caused issues such as:
One very important warning sign was:
What makes this difficult is that many problematic batteries initially appear completely normal:
But under real load conditions, some of them became highly unstable.
The likely causes are:
The analysis even showed indications that bad batteries may contribute to NAND/storage instability and general runtime problems.
Unfortunately, there is currently no reliable way (at least not for me) to identify problematic batteries beforehand based on:
In the end, the only real method is:
My current battery:
has been working very well so far and is significantly more stable than the previously tested batteries.
Interestingly, the same battery was even more expensive on AliExpress.
Original Bose batteries are now often:
So in the end, everyone has to decide for themselves:
The important thing is:
All reactions