Not for sure. Info you get from bq_27200 module is read-only data, independent from bme (battery monitor entity), which MAY or MAY NOT think the same - unfortunately, AFAIK we can't check this, thank to Nokia closed source bme (curse them 1000 times for that, for MANY reasons).

So, ID PIN is definitely probed correctly. Ho ever, at least bq_module think, that battery capacity at full charge is still 0 - this may be symptom of problem, but may also mean that bq module haven't had a chance to perform internal calibration of values (which shouldn't cause the problem on itself).

I think You could try 2 things, independent from each other:

1. Flash some framebuffer kernel, and see on which point normal boot-up fails

2. In R&D mode, install HEN + shadowjk charge script (this one surely work outside backupmenu) - You can find it in HEN thread (normally, it's used to charge while USB hostmode. Then, monitor voltage using bq_27200 module, and when it's close to 3,300V, enable HEN (this is easiest way to stop bme without risk of restart after 32 seconds, ho ever may be also possible by executing "kill bme" from terminal as root - I don't know if it triggers restart after 32 seconds in R&D also, so using HEN is 100% sure and won't hurt in any case), then wait for voltage to drop lower than 3,200 V. Then, quickly enable shadowjk's charge script, and charge it to the full (without disabling HEN!). After charge cycle is done, check again if charge_full is still reported as 0 by bq_27200.

Explanation:
bq_27200 module perform "learning cycle" (referred by me earlier in this post, as "calibration of internal values") IF voltage drops below 3,248 AND device doesn't shut down before being charged to 100%. Unfortunately, bme shuts down device @ ~3,200 (little lower), so it's hardly to ever happen. That may be (or may not) be the cause, why Your charge_full is reporting 0.

Doing that, we at least check it all bq_27200 reports can be correct - this way, it's most unlikely that bq_27200 chip is damaged. Still, nothing sure for 100%, but at least we can filter out one possible symptom.