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.)
help
Thanks solved [emoji847]
Brilliant. Worked for me too. thanks a lot!
This solution works for WhatsApp?
Todesdoktor said:
This solution works for WhatsApp?
Click to expand...
Click to collapse
No idea, I don't use WhatsApp
Worked also for Honor 9, thanks!
ante0 said:
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.)
Click to expand...
Click to collapse
wonderful.. that worked for me too on honor 8 pro , thank you !!!!!!!!!
ante0 said:
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.)
Click to expand...
Click to collapse
jeez, that worked! I had no sms since the OTA update probably
thank you very much
p20 pro btw
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.
WOW~It did work!
Thank you very muuuuuch.
If this is a bug has anyone here informed Huawei? Would like to see it get fixed in EMUI 10.
Grumpy Cat said:
If this is a bug has anyone here informed Huawei? Would like to see it get fixed in EMUI 10.
Click to expand...
Click to collapse
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
If I unlock before upgrade, will it relock the bootloader?
Come to think of it can you even upgrade with an unlocked bootloader?
Grumpy Cat said:
If I unlock before upgrade, will it relock the bootloader?
Come to think of it can you even upgrade with an unlocked bootloader?
Click to expand...
Click to collapse
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.
ante0 said:
...(Someone could report back if restoring messages with HiSuite works after removing those dbs.)
Click to expand...
Click to collapse
No one every replied if the messages could be restored after this fix. Anyone know?
Related
I installed an application that sent my phone into a bootloop. I identified the culprit via adb logcat, but obviously cannot get into the phone to delete it. I don't want to do a wipe - I have a lot of time spent customising things as is and data I don't want to lose in some apps. Is there a way from within the recovery console to delete the offending application directly to stop the bootloop?
EDIT: N/m... thought it was the app, looking closer at adb logcat, looks like it isn't... and I found a way to delete the app but the issue remains.
Going to switch ROMs, the one I'm using now is fast, but appears to be way too buggy.
lotherius said:
I installed an application that sent my phone into a bootloop. I identified the culprit via adb logcat, but obviously cannot get into the phone to delete it. I don't want to do a wipe - I have a lot of time spent customising things as is and data I don't want to lose in some apps. Is there a way from within the recovery console to delete the offending application directly to stop the bootlopp?
Click to expand...
Click to collapse
omgggggggggg
http://forum.xda-developers.com/showthread.php?p=4529707
if you have apps2sd
Code:
adb remount
adb shell
rm /system/sd/app/xxxx.apk (or if that doesn't work put -r after rm)
if you dont have apps to sd, i believe apps are in /data/app
B-man007 said:
omgggggggggg
http://forum.xda-developers.com/showthread.php?p=4529707
if you have apps2sd
Code:
adb remount
adb shell
rm /system/sd/app/xxxx.apk (or if that doesn't work put -r after rm)
if you dont have apps to sd, i believe apps are in /data/app
Click to expand...
Click to collapse
i think my crappy typed-at-work commands have been quoted lol. I need to start a whole series of typed at work commands.
Also @lotherius what rom were you using?
Enomther's Rogers. May not have been the ROM but I am a bit frustrated as I have had several problems with it, and just went back to Cyanogen 4.0.4 for now. Thanks for the info.
Hi lotherius,
I'm in the same situation; How did you delete the app within the recovery? I have a Cyanogenmod 10.1 (android 4.2.2) based custom ROM with TWRP recovery right now.
Thanks in advanced!
lotherius said:
I installed an application that sent my phone into a bootloop. I identified the culprit via adb logcat, but obviously cannot get into the phone to delete it. I don't want to do a wipe - I have a lot of time spent customising things as is and data I don't want to lose in some apps. Is there a way from within the recovery console to delete the offending application directly to stop the bootloop?
EDIT: N/m... thought it was the app, looking closer at adb logcat, looks like it isn't... and I found a way to delete the app but the issue remains.
Going to switch ROMs, the one I'm using now is fast, but appears to be way too buggy.
Click to expand...
Click to collapse
adb uninstall badapp.apk
Or if this won't work try
adb shell
adb rm /data/app/badapp.apk
Or system app or wherever it is (may be able to just delete the data of the app too
Sent from my Nexus 4 using xda premium
Wow, thread necromancy
I'm just a guy, not a techophobe so I have no idea how to get to the shell inorder to type those commands. My daughter's Macbook Pro just endlessly restarts itself unless I put it in Recovery mode or Safe mode. I suspect it is 3rd party apps causing this, but I can't delete apps from Rec. or Safe mode and no one here has put it in layman's terms.
So, I followed the guide we all did here:
http://forum.xda-developers.com/showthread.php?t=1818502
And before someone asks: I have deleted the Backup app (IS11LG_SystemBackupTest.signed.apk) we had to install during rooting after the phone was rooted.
The phone then happily ran, rooted. SUpersu was installed/updated, the phones root check said it's all perfect, I was a happy camper. But today I had to reboot it. I can't say if it was the first reboot after rooting, sadly. The phone boots up, arrives at the lockscreen (some colorful defaultthing, before I get to see my GO Locker screen after login), and then stops being responsive, it basically at first feels like it's not reacting at all. Some things are responsive, strngely ... I get accurate sounds when touching the screen for instance. If I then wait, I eventually get to the SIM Unlock ... which is also totally unresponsive, it will maybe show two digits, then freezes up. Strangely, I could type the remaining digits and hit OK and the SIM would unlock ... but the screen no longer showed what I typed. I then arrive at GO locker, can unlock it (sluggish and slow again) and finally am properly logged in, but still totally sluggish and slow. Needles to say it's a pseudobrick that way, unusable.
What's going on and what could I check?
Please try the following:
alexp999 said:
REALLY SLOW AFTER ROOT?
Remove the "SystemBackupTest" app, if you haven't already.
On your phone, go to "Settings -> Developer options" and make sure "USB debugging" is TICKED
Connect your phone via USB to your computer.
Open a command prompt (may need admin privelages, right click, run as administrator)
Type without quotes "cd C:\o4xr" and press enter.
Type without quotes "adb shell rm /data/local.prop" and press enter.
Type without quotes "adb reboot" and press enter.
Click to expand...
Click to collapse
alexp999 said:
Please try the following:
Click to expand...
Click to collapse
Thanks, that fixed it! It's not easy to do, as the scrolling lists do not work, either, and you can't seem to get to the developer options, it won't scroll. Strangely enough "internally" it seems to do things ... if you re-enter the options, they're down to the end of the list, it looks like it doesn't update the screen properly (much like when I had to enter the SIM code).
Anyway, it's fast again, whew ... I was scared. What is the local.prop thing, if I may ask?
voon said:
Thanks, that fixed it! It's not easy to do, as the scrolling lists do not work, either, and you can't seem to get to the developer options, it won't scroll. Strangely enough "internally" it seems to do things ... if you re-enter the options, they're down to the end of the list, it looks like it doesn't update the screen properly (much like when I had to enter the SIM code).
Anyway, it's fast again, whew ... I was scared. What is the local.prop thing, if I may ask?
Click to expand...
Click to collapse
I'm not entirely sure, I just know it gives us temp root for the rest of the root script to run.
Hm, so its' not a systemwide ini file or so, that existed before ... it was created during the above rooting process and was an undesired leftover from it? I'm always a bit worried if I delete something with such an unspecific name in the OS
voon said:
Hm, so its' not a systemwide ini file or so, that existed before ... it was created during the above rooting process and was an undesired leftover from it? I'm always a bit worried if I delete something with such an unspecific name in the OS
Click to expand...
Click to collapse
Its actually created by the SystemBackupTest app.
The script then removes it just before issuing a reboot.
The only way it can come back, is if you accidently open that app again before uninstalling it.
alexp999 said:
Its actually created by the SystemBackupTest app.
The script then removes it just before issuing a reboot.
The only way it can come back, is if you accidently open that app again before uninstalling it.
Click to expand...
Click to collapse
I see, I might have done that ... good to know. Anyway, great that it works again, thanks again
laggy phone
My lg 4x hd is very slow after root...
I just tried to make this few steps above, but I got this message.
Any idea what to do?
Pls help me!
THX
66aaa
66aaaa said:
My lg 4x hd is very slow after root...
I just tried to make this few steps above, but I got this message.
Any idea what to do?
Pls help me!
THX
66aaa
Click to expand...
Click to collapse
It looks like you have either plugged in more than one android device, or you have an android emulator (from the SDK I guess) running. Unplug all USB devices (except keyboard and mouse) and then try again. Good luck!
If you have an emulator running try "adb -d shell rm /data/local.prop"
Edit: To see all adb-devices type "adb devices". This will return a list of all adb-devices connected (emulators + usb devices)
Dexxon said:
If you have an emulator running try "adb -d shell rm /data/local.prop"
Edit: To see all adb-devices type "adb devices". This will return a list of all adb-devices connected (emulators + usb devices)
Click to expand...
Click to collapse
I still don't understand and hope you do it...
THX for your help!
As you can see the same device is listed two times. Restarting the adb server may help. Just type "adb kill-server" and than launch the second command from your screenshot. Maybe this works.
Dexxon said:
As you can see the same device is listed two times. Restarting the adb server may help. Just type "adb kill-server" and than launch the second command from your screenshot. Maybe this works.
Click to expand...
Click to collapse
This is the result...what to do know?
THX
The devices is detected and the command is executed, but the file does not exist. Make sure that there is a file "prop.local" at /data. If not, you may have a different problem.
Maybe you have an emulator running or Bluestacks installed... Uninstall Bluestacks...
I don't think that this is the case as the device shows up with a serial number in the "adb devices" list.
To be sure it is the correct phone you could compare the serial number shown in the list with the serial number of your phone (you might find this information in settings -> about phone).
Dexxon said:
The devices is detected and the command is executed, but the file does not exist. Make sure that there is a file "prop.local" at /data. If not, you may have a different problem.
Click to expand...
Click to collapse
I don't have in the system/data "prop.local" file...sure....
What is emulator and Bluestacks?
I really don't understand this problem I have...
Could you help me pls?
THX
66aaaa said:
I don't have in the system/data "prop.local" file...sure....
What is emulator and Bluestacks?
I really don't understand this problem I have...
Could you help me pls?
THX
Click to expand...
Click to collapse
An emulator is a program which emulates Android so you can execute Android-Apps on your PC. BlueStacks is an emulator. It may show up as an adb devices, but this is not the case here.
Back to your problem: Are you sure the rooting process worked?
Did you reboot your phone after rooting?
I didn't root my phone under ICS so I don't have any experience with this
no one raised this question to confirm or did this info was provided anywhere
What version of ROM? ICS V10x? JB V20x? User could had used the wrong guide.
Best way out is to do a reflash and retry rooting if all fails.
Dexxon said:
An emulator is a program which emulates Android so you can execute Android-Apps on your PC. BlueStacks is an emulator. It may show up as an adb devices, but this is not the case here.
Back to your problem: Are you sure the rooting process worked?
Did you reboot your phone after rooting?
I didn't root my phone under ICS so I don't have any experience with this
Click to expand...
Click to collapse
I dont't have this Bluestacks emulatur, sure...
I have Superuser working properly on JB V20 stock ROM. The only thing it is very slow sometimes, Thats why I tried to make the process above...
I made the root few month ago...and rebooted many times since than...
Any idea what to do now?
THX
Hi, just now I upgrade to the the last Samsung update and now I got the error.
The AOD is work and I got notification tone but can not enter to the phone.
I enter to safemode and still the same.
I hope there is a way to solved it without erase the phone.
I can't enter to download mode because I can't close the phone
What should I do?
SAME TO MEE... OMG!!! ****ing samsung send me this update|
i even cannot call any one with this phone right now ..
I did a factory reset and now i need to spend hours to download and customized all over again!!
I think it's because the tweaks and system modes of Substratum.
I think that on the next time we should delete all of the system modes.
Hope some one can approve it because I really don't want to get through this again.
What make it to a sad joke is that the update is not what i thought it was, still I don't have the new Samsung VPN.
All for nothing!!!
soilentgreen said:
I did a factory reset and now i need to spend hours to download and customized all over again!!
I think it's because the tweaks and system modes of Substratum.
I think that on the next time we should delete all of the system modes.
Hope some one can approve it because I really don't want to get through this again.
What make it to a sad joke is that the update is not what i thought it was, still I don't have the new Samsung VPN.
All for nothing!!!
Click to expand...
Click to collapse
Correct, you have to uninstall all your layers and substratrum mods before accepting the OTA. I just saw this but you can boot into safe mode while system ui is fc and uninstall all the mods there and you should be good when you boot out of safe mode. No factory data reset needed.
soilentgreen said:
Hi, just now I upgrade to the the last Samsung update and now I got the error.
The AOD is work and I got notification tone but can not enter to the phone.
I enter to safemode and still the same.
I hope there is a way to solved it without erase the phone.
Click to expand...
Click to collapse
I posted this before in another thread...
I was able to fix it without factory resetting my phone. To do it, connect your phone to a pc (pc that you previously connected your phone to and always allowed access), in cmd with adb, run "adb shell pm list packages > whateveryouwanttonameit.txt" and look through the text file for apps you installed that changed your status bar. Then in cmd run "adb uninstall com.appyouwanttouninstall". I did 4 among many, checked my phone, and didn't get the system ui has stopped messages
houboy said:
I posted this before in another thread...
I was able to fix it without factory resetting my phone. To do it, connect your phone to a pc (pc that you previously connected your phone to and always allowed access), in cmd with adb, run "adb shell pm list packages > whateveryouwanttonameit.txt" and look through the text file for apps you installed that changed your status bar. Then in cmd run "adb uninstall com.appyouwanttouninstall". I did 4 among many, checked my phone, and didn't get the system ui has stopped messages
Click to expand...
Click to collapse
Thanks for the tip! Rather than saving to text I just used one window to output the packages to stdout, while I used another to do the uninstalls. Removing these two packages fixed the issue:
com.android.settings.SwiftDark.Android8defaultgrey.SamsungS8
com.android.systemui.SwiftDark.SamsungS8
how can u access to cmd with adb ?
houboy said:
I posted this before in another thread...
I was able to fix it without factory resetting my phone. To do it, connect your phone to a pc (pc that you previously connected your phone to and always allowed access), in cmd with adb, run "adb shell pm list packages > whateveryouwanttonameit.txt" and look through the text file for apps you installed that changed your status bar. Then in cmd run "adb uninstall com.appyouwanttouninstall". I did 4 among many, checked my phone, and didn't get the system ui has stopped messages
Click to expand...
Click to collapse
Hello, give me tutorial, how can i uninstall apk from pc ?
i can access cmd but how can i uninstalled apk ?
please help,,,
Thanks,
Thank you for all the answers.
ggrant3876 said:
Correct, you have to uninstall all your layers and substratrum mods before accepting the OTA. I just saw this but you can boot into safe mode while system ui is fc and uninstall all the mods there and you should be good when you boot out of safe mode. No factory data reset needed.
Click to expand...
Click to collapse
But I did boot into safe mode and the phone continued to stuck on "system ui has stopped"
houboy said:
I posted this before in another thread...
I was able to fix it without factory resetting my phone. To do it, connect your phone to a pc (pc that you previously connected your phone to and always allowed access), in cmd with adb, run "adb shell pm list packages > whateveryouwanttonameit.txt" and look through the text file for apps you installed that changed your status bar. Then in cmd run "adb uninstall com.appyouwanttouninstall". I did 4 among many, checked my phone, and didn't get the system ui has stopped messages
Click to expand...
Click to collapse
enrico.fm08 said:
Hello, give me tutorial, how can i uninstall apk from pc ?
i can access cmd but how can i uninstalled apk ?
please help,,,
Thanks,
Click to expand...
Click to collapse
I never knew how to use adb,
There is any tutorial about it?
soilentgreen said:
Hi, just now I upgrade to the the last Samsung update and now I got the error.
The AOD is work and I got notification tone but can not enter to the phone.
I enter to safemode and still the same.
I hope there is a way to solved it without erase the phone.
Click to expand...
Click to collapse
Edwanzhuang said:
SAME TO MEE... OMG!!! ****ing samsung send me this update|
i even cannot call any one with this phone right now ..
Click to expand...
Click to collapse
Did any of you have substratum installed?
EDIT: i just read up higher.
This also happened to me with substratum. One thing I did before however is I already had adb debugging enabled and trusted with my pc via adb.
I used these instructions found here for adb
https://www.reddit.com/r/GalaxyS8/comments/737y3j/helpfix_substratum_system_ui_has_stopped_issue/
What is the latest version of samsung update?
Mine is N950FXXU2BQKG/N950FOXM2BQKG/N950FXXU2BQKG.
My phone updat 6 days ago, and I don't have the new samsung VPN.
And just to be clear, in the next update after uninstall all the layers and substratrum mods and accepting the OTA, it is safe to install all the layers again after the update?
Thanks again
soilentgreen said:
What is the latest version of samsung update?
Mine is N950FXXU2BQKG/N950FOXM2BQKG/N950FXXU2BQKG.
My phone updat 6 days ago, and I don't have the new samsung VPN.
And just to be clear, in the next update after uninstall all the layers and substratrum mods and accepting the OTA, it is safe to install all the layers again after the update?
Thanks again
Click to expand...
Click to collapse
You should have the VPN under wifi advance settings.
Yes it's safe to install all your layers and substratrum mods I using it on 2BQKG.
Merry Christmas to all!
BluePhnx said:
You should have the VPN under wifi advance settings.
Yes it's safe to install all your layers and substratrum mods I using it on 2BQKG.
Merry Christmas to all!
Click to expand...
Click to collapse
I don't have the VPN, and we on the same version. It's weired.
I need to "open" it somehow?
How do you color your notifaction clock and icons?
hello i just uptdated my software and im stuck with the same thing can somebody walk me thru how to fix this?
houboy said:
I posted this before in another thread...
I was able to fix it without factory resetting my phone. To do it, connect your phone to a pc (pc that you previously connected your phone to and always allowed access), in cmd with adb, run "adb shell pm list packages > whateveryouwanttonameit.txt" and look through the text file for apps you installed that changed your status bar. Then in cmd run "adb uninstall com.appyouwanttouninstall". I did 4 among many, checked my phone, and didn't get the system ui has stopped messages
Click to expand...
Click to collapse
Thanks houboy, you're a lifesaver.
Tried to center the status bar clock and the phone crashed.
Your method worked like a charm
I was reading through the reddit thread posted earlier and found an alternative solution which worked for me.
Log into Samsungs Find My Phone website, unlock your device and then switch on Power Saving Mode, then reboot. Once in Power Saver you will regain control of your phone. Now, switch off power saver and go disable all substratum mods and reboot again.
Happened twice to me while setting up my new Note 8. Resolved to finally wipe through hard reset menu, and setup as new phone. Some Substratum addon was lingering when I did a restore which was likely causing the UI crash.
this happened 3 times to my note 8, the culprit seems to be android pay, once you add a credit card to be specific . To fix the phone you need to put the phone in powersaving mode via Samsung dive then reboot.
once the phone rebooted in power saving mode just put it back to normal , after this procedure all cards are removed from google pay.
davnav899 said:
Did any of you have substratum installed?
EDIT: i just read up higher.
This also happened to me with substratum. One thing I did before however is I already had adb debugging enabled and trusted with my pc via adb.
I used these instructions found here for adb
https://www.reddit.com/r/GalaxyS8/comments/737y3j/helpfix_substratum_system_ui_has_stopped_issue/
Click to expand...
Click to collapse
What's strange is that I have substratum installed but never ran it but I'm still getting the system UI error, thank good it hasn't totally blocked need but still doesn't make sense why this is all happening. I forgot I even installed it honestly.
I just uninstalled it so I'll see if that changes anything.
@squick You could try booting into safe mode to see if its a program causing it, but for me, i updated my phone software(update) with the substratum ui apk installed which caused me to get the force close error where only the screen showed system ui has stopped. I used adb to get a list of packages and remove the substratum system ui apk. A sure way to fix would be to reset the phone, but if you're able to use it, try removing apps you dont need from your applications in the settings. It's possible there could be another app interfering with the system ui
Hi guys,
does your settings/system/backup (app data, sms etc to Google disk) work?
Mine still says 'waiting for backup' except for Google photos.
Backup is enabled, correct account selected.
Had exactly the same problem and resolved it with adb. See here:
https://forum.xda-developers.com/nokia-7-plus/help/issue-google-backup-t3781848
fax2368 said:
Had exactly the same problem and resolved it with adb. See here:
https://forum.xda-developers.com/nokia-7-plus/help/issue-google-backup-t3781848
Click to expand...
Click to collapse
Ah, I missed that thread. I will give it a try.
Do you now need to manually backup data via adb all the time or has this fixed the issue and backups are made automatically by the phone itself now?
After this I left the phone during night on charge and connected via WIFI and it started to backup automatically. Since then no more problems... it needs just the initial push
thanks mate!
just for the others who may be having the same issue - the backup suddenly started working after a few days without me touching anything, so in the end I did not use the adb method.
Hi, I have been struggled with this wired issue on Android 11 and Android 12.
My Pixel 5 will reboot when I use "dismiss all" to clear google's notification.
I grabbed some ADB log and it says "E Zygote : java.lang.IllegalArgumentException: Unexpected cancel with surface 12"
Part of my ADB log (Google drive link, Can't insert more than 8000 characters in thread)
I can't figure out what cause this. My Pixel 5 is rooted and has LSPosed installed. I have tried to disable all XPosed module and this issue persist. Is there any way to fix it or is there any way I can get more detail about how this happened?
Thanks in advance.
Exactly the same issue here... The problem happens sometimes when I swipe to clear the Gmail notifications.
bitbot said:
Exactly the same issue here... The problem happens sometimes when I swipe to clear the Gmail notifications.
Click to expand...
Click to collapse
Try to use adb excute this command:
Code:
setprop persist.log.tag.NotificationService ""
and then reboot your phone
It works for me
lupohan44 said:
Try to use adb excute this command:
Code:
setprop persist.log.tag.NotificationService ""
and then reboot your phone
It works for me
Click to expand...
Click to collapse
Awesome! Thanks dude!