Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Categories
Random page
Top Contributors
Recent changes
Special pages
Contribute
Create a page
How to help
Wiki policy
Article suggestion list
Articles in need of work
Help
Frequently asked questions
Join the discord!
Help about MediaWiki
Moderators' noticeboard
Report a bug
Consumer Rights Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Talk:Battery firmware lockout
(section)
Add topic
Page
Discussion
English
Read
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit source
Add topic
View history
Purge cache
General
What links here
Related changes
Page information
Cargo data
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== On Texas Instruments BQ-series BMS == This type of BMSes is the most common type used on laptop computers. Unlike the BMS in power tools that you can dump the firmware, the Texas Instruments BQ series BMS has something like "a chip within a chip", similar to Intel Management Engine or fTPM. I learned from some friends who worked with power electronics. The BQ series needs password to access the internal memory. Unfortunately, the "Permanent Fail" is gated the same "height" of the "wall" as flashing firmware. If you know the password you can read and even write (both official and custom) firmware, if you don't know the password you can't even clear the PF error code. The BMS sends the battery's current status like the voltage, current, temperature, cycle count and the limitations like charge max voltage/current, discharge min voltage/max current, etc, to the device. It's know that some computer models use different battery packs, the EC supplies the correct voltage and current to the battery because the BMS tells these values to the EC. These messages are not encrypted and are read by embedded controller (EC) on the computer's motherboard. Thus, we can technically build our own FOSS BMS using the same way of communication with the EC, without any "lockout" logic, or we can just buy a BQ chip from TI, use the official firmware but without setting a custom password. If the "community driven" custom BMS gains traction and reaches mass production, we can solve the "battery firmware lockout" once and for all. The reason why few people talk about it, I think, is the "baseline" reliability difference. The reliability of a product depends on the least reliable part, so laptop batteries have to be very reliable. As a result, they don't fail randomly. Given the high quality standard, non-OEM battery manufacturers and independent repair technicians can rarely reach the reliability standard of the original ones. Therefore there's low incentive for those people to find a reliable way of unbricking the BMS. [[User:Charlie 6|Charlie 6]] ([[User talk:Charlie 6|talk]]) 13:13, 17 September 2025 (UTC)
Summary:
Please note that all contributions to Consumer Rights Wiki are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 International (see
Consumer Rights Wiki:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:
Cancel
Editing help
(opens in new window)
Search
Search
Editing
Talk:Battery firmware lockout
(section)
Add topic