Battery name is GARDA31, based on bq29330 and bq8030.
Most probably I killed it myself when soldering by shorting terminals with solder wire :( Controller is alive (communicates through SMbus), but shows "critical" and 0% charge in the OS.
The marking seems to be
but I am not sure in first 0 as the defect is exactly in its place.
It has relation to the - terminal of battery. I would think it is a current sense resistor Rsns (see circuit diagram of page 4 of datasheet), but my colleague says that it does not look like resistor but rather like semiconductor; I measured it to be a short (voltage is 0 across it and Ohmmeter shows the shortage), and if it would be a current sense resistor then battery would start or/and catch fire?
Battery pack was replaced and is fully charged.
I have another battery controller with current sense resistors, and they really look differently:
I did not desolder the battery pack yet, seems will have to do it to perform signal tracing.
I removed the batt pack, and desoldered the device. It appeared to have two terminals. Also found out that fuse is blown - and that's why there's no further damage.
This "resistor" is going to the notebook battery connector. I can not trace it more precisely because I have no datasheet for bq8030.
I shorted the fuse with solder (expected to melt in case of emergency), and replaced defective current sense resistor with two R010 resistors in parallel.
No change. OS still says 0%, and "Online, Critical". There's something else, up to gas gauge chip's firmware defecting the assembly because it thinks pack is damaged.