Boron LTE - Permanently flashing green after running out of battery

Hi,
I have a Boron LTE (v1.4.2) which was running on solar power + battery for months. But at some point it has stopped and when I visited I saw it was out of power and once battery was replaced it was flashing green. I have replaced the batterpower cycled multiple times, no change.
I have brought the Boron home, replaced the 3rd party SIM card - no change.
Upgraded the firmware to the latest (v1.5.0) via USB - no change.

I have flushed the cloud debugging tool (https://github.com/rickkas7/boron-clouddebug) and got the following logs:

manufacturer=
model=
firmware version=
ordering code=
IMEI=
IMSI=
ICCID=
0000710976 [app] INFO: enabling trace logging
0000710977 [ncp.at] TRACE: > AT+CGDCONT?
0000720979 [ncp.at] TRACE: > AT+CSQ
attempting to connect to the cellular network…
0000730982 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000730982 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000730987 [hal] TRACE: PPP netif -> 8
0000730988 [net.ifapi] INFO: Netif pp3 state UP
0000730988 [net.ifapi] INFO: Netif pp3 state UP
0000730992 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000730992 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000730992 [hal] TRACE: Powering modem on
0000731148 [hal] TRACE: Modem powered on
0000731150 [hal] TRACE: Setting UART voltage translator state 1
0000732151 [ncp.at] TRACE: > AT
0000733151 [ncp.at] TRACE: > AT
0000734152 [ncp.at] TRACE: > AT
0000735152 [ncp.at] TRACE: > AT
0000736153 [ncp.at] TRACE: > AT
0000737154 [ncp.at] TRACE: > AT
0000738154 [ncp.at] TRACE: > AT
0000739155 [ncp.at] TRACE: > AT
0000740156 [ncp.at] TRACE: > AT
0000740766 [sys.power] TRACE: re-enabling charging
0000740796 [sys.power] TRACE: Battery state UNKNOWN -> CHARGED
0000741157 [ncp.at] TRACE: > AT
0000741801 [sys.power] TRACE: Battery state CHARGED -> DISCONNECTED
0000742157 [ncp.at] TRACE: > AT
0000743158 [ncp.at] TRACE: > AT
0000744158 [ncp.at] TRACE: > AT
0000745159 [ncp.at] TRACE: > AT
0000746160 [ncp.at] TRACE: > AT
0000747161 [ncp.at] TRACE: > AT
0000748162 [ncp.at] TRACE: > AT
0000749163 [ncp.at] TRACE: > AT
0000750163 [ncp.at] TRACE: > AT
0000751163 [ncp.at] TRACE: > AT
0000752163 [hal] ERROR: No response from NCP
0000752163 [hal] ERROR: No response from NCP
0000752165 [hal] TRACE: Setting UART voltage translator state 0
0000752168 [hal] TRACE: Hard resetting the modem
0000763168 [net.pppncp] TRACE: Failed to initialize ublox NCP client: -210
0000763170 [hal] TRACE: Setting UART voltage translator state 0
0000763172 [hal] TRACE: Modem already off
0000763273 [hal] TRACE: Powering modem on
0000763424 [hal] TRACE: Modem powered on
0000763426 [hal] TRACE: Setting UART voltage translator state 1
0000764428 [ncp.at] TRACE: > AT
0000765429 [ncp.at] TRACE: > AT
0000766430 [ncp.at] TRACE: > AT
0000767431 [ncp.at] TRACE: > AT
0000768432 [ncp.at] TRACE: > AT
0000769433 [ncp.at] TRACE: > AT
0000770434 [ncp.at] TRACE: > AT
0000771435 [ncp.at] TRACE: > AT
0000772435 [ncp.at] TRACE: > AT

Inspect shows the following:

$ particle serial inspect
Platform: 13 - Boron
Modules
Bootloader module #0 - version 501, main location, 49152 bytes max size
Integrity: PASS
Address Range: PASS
Platform: PASS
Dependencies: PASS
System module #1 - version 1102
Monolithic module #0 - version 1404, main location, 802816 bytes max size
Integrity: PASS
Address Range: PASS
Platform: PASS
Dependencies: PASS
Radio stack module #0 - version 202, main location, 192512 bytes max size
Integrity: PASS
Address Range: PASS
Platform: PASS
Dependencies: PASS

Could this be the ublox module dying following a power out event?

I have read that that can be fatal to Boron LTE (see Boron LTE Fails to Connect), which is a hardware bug to me - an iOT device should die because it runs out of power. I hope that is not the case.

Any ideas?

Hi there,

Correct, there’s not a reasonable scenario where the Boron loses power and the device fails. However, there is an exceedingly rare issue when this may occur. Given the logs you’ve provided, it does seem that the modem has been bricked (it is unrecoverable). This is through no fault of your own. Please reach out to us via support@particle.io and we will handle the replacement process.

Hi @DJ_Volt,
Thanks for your reply. I will reach out to support for the replacement as suggested and will refer to this discussion.
Thanks!