Fix Messages and Dialer in 9.1 [Root required]

ante0

Senior Member
Dec 28, 2009
3,206
1,576
243
Stockholm
Checking logcat when using Dialer and Messages, I noticed it gets a lot of fail to open db which leads to app crash.
To fix it you can do this, requires Magisk:
Note that this will wipe contacts and messages! (contacts should sync again from google account or any other account you have linked)

adb shell
su
rm /data/user/0/com.android.providers.telephony/databases/*
rm /data/user/0/com.android.providers.contacts/databases/*

Go back to phone and wipe data of Phone and Messages
Go back to command prompt and:
reboot recovery

(or 'adb reboot recovery' if you closed adb shell session)
Messages and Dialer should now open fine.

(Someone could report back if restoring messages with HiSuite works after removing those dbs.)
 

simika

Senior Member
May 19, 2012
286
49
58
Rome
Checking logcat when using Dialer and Messages, I noticed it gets a lot of fail to open db which leads to app crash.
To fix it you can do this, requires Magisk:
Note that this will wipe contacts and messages! (contacts should sync again from google account or any other account you have linked)

adb shell
su
rm /data/user/0/com.android.providers.telephony/databases/*
rm /data/user/0/com.android.providers.contacts/databases/*

Go back to phone and wipe data of Phone and Messages
Go back to command prompt and:
reboot recovery

(or 'adb reboot recovery' if you closed adb shell session)
Messages and Dialer should now open fine.

(Someone could report back if restoring messages with HiSuite works after removing those dbs.)
wonderful.. that worked for me too on honor 8 pro :) , thank you !!!!!!!!!
 

mangusZen

Senior Member
Apr 10, 2011
735
369
0
Bologna,Italy
Checking logcat when using Dialer and Messages, I noticed it gets a lot of fail to open db which leads to app crash.
To fix it you can do this, requires Magisk:
Note that this will wipe contacts and messages! (contacts should sync again from google account or any other account you have linked)

adb shell
su
rm /data/user/0/com.android.providers.telephony/databases/*
rm /data/user/0/com.android.providers.contacts/databases/*

Go back to phone and wipe data of Phone and Messages
Go back to command prompt and:
reboot recovery

(or 'adb reboot recovery' if you closed adb shell session)
Messages and Dialer should now open fine.

(Someone could report back if restoring messages with HiSuite works after removing those dbs.)
jeez, that worked! I had no sms since the OTA update probably
thank you very much

p20 pro btw
 

SonOfTheRain

Senior Member
Oct 8, 2006
65
7
0
In my case only sms didn't work. I deleted sms dbs using rm /data/user/0/com.android.providers.telephony/databases/*, later I restored smses via Huawei backup (restore from sd card). Worked that way.
 

Pretoriano80

Senior Member
Jun 9, 2010
3,181
2,870
253
If this is a bug has anyone here informed Huawei? Would like to see it get fixed in EMUI 10.
This only occur on rooted devices, so there's nothing to be fixed by Huawei.
However, it seem that EMUI 10 will force bootloader lock and so far there's no way to unlock it, even if you have the unlock code. That will fix this issue too! xD
 

Grumpy Cat

Senior Member
Oct 23, 2015
722
190
73
If I unlock before upgrade, will it relock the bootloader?

Come to think of it can you even upgrade with an unlocked bootloader?
 
Last edited:

Pretoriano80

Senior Member
Jun 9, 2010
3,181
2,870
253
If I unlock before upgrade, will it relock the bootloader?

Come to think of it can you even upgrade with an unlocked bootloader?
Yes, it will re-lock the bootloader. Basically, with EMUI 10 you can't have an unlocked bootloader.
We will see if that changes with the official release, but i doubt.