Hacker News

points by rickdeckard 17 hours ago | 0 comments

The page mentions that an adb command is required to recover the device, but I can't find details on what exact adb this is.

Overall a bit frustrating to have such a fancy webpage with a dedicated address, but then no description on how to actually #1 identify and #2 recover an affected device...

> "Once the database is corrupt, com.android.phone no longer needs a fresh message to fail: it crashes immediately on every boot as it reads the damaged store [..] a factory reset only helps temporarily"

Can't I delete the storage of com.android.phone instead of a full factory-reset?

[–] MarkBlah 15 hours ago

To recover I deleted the telephony.db, 2 minutes later carrier resent the messages…

Only fix is to place sim/esim into non Android device

[–] masfuerte 12 hours ago

Or wait four days, which is the typical network timeout for SMS delivery.

[–] ratdragon 17 hours ago

Just guessing - maybe that re-delivery from telcom is the cause as message reception is never acknowledged?

[–] rickdeckard 17 hours ago

yes, valid guess, I should have extended the quote.

The page describes that this part is resolved by putting the SIM into a non-Android device to receive the queued messages and acknowledge to the network.

To then recover the device it only vaguely mentions "adb commands" and "factory reset", but I can't find a description what actually needs to be done on the device.

I guess the specific question is: The message database that is corrupted due to this issue, is this DB owned by (and stored as part of) com.android.phone?