BRN402 and TAN004

Welp, this is a long shot but I wonder if anyone has ever managed to get out of this one.
I have an old Boron (BRN402) that I tried playing arround with today. And I'm pretty sure I have a TAN004 situation. Below are the device doctor logs.
Today I have soldered wires to the USB pads for the uBlox Sara and I am going to try to unbrick it by flashing maaaaybe SARA-R410M-02B-04-P1-L0000000512A0221-000K00.dof to it. Keep you all posted
Has anyone had any success recovering your Boron from a TAN004 or TAN001? What did you do?

Serial monitor opened successfully:
0000001474 [mux] INFO: Sending CLD (multiplexer close down)
0000002377 [mux] INFO: Received response to CLD or timed out, exiting multiplexed mode
0000002428 [mux] INFO: GSM07.10 muxer thread exiting
0000002429 [mux] INFO: GSM07.10 muxer stopped
0000002430 [ncp.client] TRACE: Initialized muxer @ 115200 baudrate
0000002431 [mux] INFO: Starting GSM07.10 muxer
0000002432 [mux] INFO: GSM07.10 muxer thread started
0000002731 [mux] INFO: Stopping GSM07.10 muxer
0000002732 [mux] INFO: Gracefully stopping GSM07.10 muxer
0000002733 [mux] INFO: Closing all muxed channels
0000002734 [mux] INFO: Muxed channel 1 already closed
0000002734 [mux] INFO: Muxed channel 2 already closed
0000002735 [mux] INFO: Muxed channel 3 already closed
0000002736 [mux] INFO: Muxed channel 4 already closed
0000003320 [app.deviceInfo] INFO: DeviceInfo e4360a84-c13a-4dad-a516-2d801935ec4e
{"platform":"Boron","target":"6.3.4","fwVersion":14,"sysVersion":"6.3.5","deviceId":"e00fce680f6255aae992178c","serial":"B40KAB841AMYL2X"}
0000003387 [mux] INFO: Sending CLD (multiplexer close down)
0000004290 [mux] INFO: Received response to CLD or timed out, exiting multiplexed mode
0000004341 [mux] INFO: GSM07.10 muxer thread exiting
0000004342 [mux] INFO: GSM07.10 muxer stopped
0000004344 [ncp.at] TRACE: > AT
0000005262 [app] INFO: Auto-connect disabled
0000005344 [ncp.at] TRACE: > AT
0000006345 [ncp.client] TRACE: Not responsive @ 460800 baudrate
0000006347 [ncp.at] TRACE: > AT
0000007347 [ncp.at] TRACE: > AT
0000008348 [ncp.at] TRACE: > AT
0000009349 [ncp.at] TRACE: > AT
0000010350 [ncp.at] TRACE: > AT
0000011351 [ncp.client] TRACE: Not responsive @ 115200 baudrate
0000011352 [ncp.client] ERROR: No response from NCP
0000011353 [ncp.client] TRACE: Hard reset
0000011354 [ncp.client] TRACE: Waiting up to 30s to power off with PWR_UC
0000052354 [net.pppncp] TRACE: NCP event 3
0000052355 [net.pppncp] TRACE: NCP power state changed: IF_POWER_STATE_DOWN
0000052356 [system.nm] TRACE: Interface 4 power state changed: DOWN
0000052357 [ncp.client] TRACE: Deinit UART
0000052358 [net.pppncp] ERROR: Failed to initialize cellular NCP client: -210
0000052458 [ncp.client] TRACE: Powering on, ncpId: 0x44
0000052460 [net.pppncp] TRACE: NCP event 3
0000052460 [net.pppncp] TRACE: NCP power state changed: IF_POWER_STATE_POWERING_UP
0000052461 [system.nm] TRACE: Interface 4 power state changed: POWERING_UP
0000052611 [net.pppncp] TRACE: NCP event 3
0000052612 [net.pppncp] TRACE: NCP power state changed: IF_POWER_STATE_UP
0000052613 [system.nm] TRACE: Interface 4 power state changed: UP
0000052614 [ncp.client] TRACE: Powered on
0000053815 [ncp.at] TRACE: > AT
0000054816 [ncp.at] TRACE: > AT
0000055817 [ncp.at] TRACE: > AT
0000056818 [ncp.at] TRACE: > AT
0000057819 [ncp.at] TRACE: > AT
0000058820 [ncp.at] TRACE: > AT
0000059821 [ncp.at] TRACE: > AT
0000060822 [ncp.at] TRACE: > AT
0000061823 [ncp.at] TRACE: > AT
0000062824 [ncp.at] TRACE: > AT
0000063826 [ncp.at] TRACE: > AT
0000064826 [ncp.at] TRACE: > AT
0000065827 [ncp.at] TRACE: > AT
0000066828 [ncp.at] TRACE: > AT
0000067829 [ncp.at] TRACE: > AT
0000068830 [ncp.client] ERROR: No response from NCP
0000068831 [ncp.client] TRACE: Hard reset
0000068832 [ncp.client] TRACE: Waiting up to 30s to power off with PWR_UC

That is typical log for TAN004/TAN001, however it's unlikely that even using the u-blox flash tool will be able to recover the modem. It won't make things any worse, so I guess it's worth a try, however.

Hi @JochiPochi,

I’ve tried to recover a BRN402 with TAN004 with the u-blox flash tool and unfortunately, I was unable to recover. Figured I would pass this along to save you the effort.

Thank you for the responses. I didn't spend too much time on it, and yeah, as expected it didn't work.
I learned a few things in the process so not a waste of time, but it's time to buy a new device.