So being the sort of person the leap without looking, I uninstalled Chrome from my phone without fully understanding the issues this would cause (aside from being incredibly hard to restore I cannot update my phone). I have since attempted to restore the app, through various means including manually moving the downloaded apk into the system directory, and manually adjusting the permissions, to using titanium backup to change it for me. But every time I try to update I am greeted with the same error message telling me I cannot update as the file cannot be found "assert failed: apply_patch_check("/system/app/Chrome.apk" etc etc.
Is there something I'm missing?
Related
Something happened to my over the weekend. I found it had reset and kept resetting on the loading screen. I took the battery out, popped it on and turned it on. It made it to the home screen but all the apps I had stored on the SD card would close unexpectedly. It looked like ext2 partition crapped out or something as none of those apps would run. So I restored a backup from Nandroid and everything was working again EXCEPT for my SMS/MMS.
Whenever I go into messages, it crashes with a "force close" prompt stating com.android.mms closed unexpectedly. I'm thinking if I could clear all the messages I had save that would solve the problem, but I have no clue where they're stored.
Any advice?
Found what I needed here: http://forum.xda-developers.com/showthread.php?p=2976069&highlight=messages+stored#post2976069
I deleted the DB with the messages, all is well.
same problem here,
clicking "sms" pops up an error msg "com.android.mms ended unexpected"
I have not found any .db files yet :-(
Hello,
Did you deleted mmssms.db or some of "PART_XXXXXXXXXX" files too?
Thanks!
Deleting the mmssms.db file
For no apparent reason my phone's messaging app suddenly started force closing. After multiple reboots, even taking the battery out while phone was on, changing the language settings, and even doing a data factory reset, nothing worked. Found this post and deleted the mmssms.db file, now messaging app works fine, tho I lost all the old messages. That's ok, I had all but the last day backed up to Gmail anyway. So, just delete the database file.
VirtuallyNadine said:
For no apparent reason my phone's messaging app suddenly started force closing. After multiple reboots, even taking the battery out while phone was on, changing the language settings, and even doing a data factory reset, nothing worked. Found this post and deleted the mmssms.db file, now messaging app works fine, tho I lost all the old messages. That's ok, I had all but the last day backed up to Gmail anyway. So, just delete the database file.
Click to expand...
Click to collapse
I have the same problem. Did you permanently delete the database or is it still there? Cos I tried to delete the database throught root explorer but it still remains altho it has deleted all the messages saved in it.
any news on the com.android.mms subject????? I feel very frustrated with my android and i looked everywhere on the internet and can't manage to fix it!
A possible fix
Here's what I did that fixed mine:
I think the root-cause of this error occurred from restoring old messages. There must have been a character/corruption somewhere that was screwing everything up.
Please note the following: I'm using an Evo 4G, running gingerbread-evo-deck-1.2 ROM. I realize this is a G1 thread, but this came up first on google, so I think it would be most helpful here. I was getting the error as described when using the "Messaging" app.
What I did:
Terminal Emulator
su (allow root if prompted)
rm /data/data/com.android.providers.telephony/databases/mmssms.db
Menu > Reset terminal (probably an unnecessary step, but it's what I did)
home screen > remove battery while running
wait 20 seconds
reboot
I don't know why removing the battery that way works. I did try force closing the "Message" app and it didn't work. I realize now I probably should have tried to figure out how to kill the underlying framework, but oh well. I'm not going to try breaking it again.
echoota said:
Here's what I did that fixed mine:
I think the root-cause of this error occurred from restoring old messages. There must have been a character/corruption somewhere that was screwing everything up.
Please note the following: I'm using an Evo 4G, running gingerbread-evo-deck-1.2 ROM. I realize this is a G1 thread, but this came up first on google, so I think it would be most helpful here. I was getting the error as described when using the "Messaging" app.
What I did:
Terminal Emulator
su (allow root if prompted)
rm /data/data/com.android.providers.telephony/databases/mmssms.db
Menu > Reset terminal (probably an unnecessary step, but it's what I did)
home screen > remove battery while running
wait 20 seconds
reboot
I don't know why removing the battery that way works. I did try force closing the "Message" app and it didn't work. I realize now I probably should have tried to figure out how to kill the underlying framework, but oh well. I'm not going to try breaking it again.
Click to expand...
Click to collapse
Works for me thanks
hi i am currently unrooted after i recently restored my phone using the 2.2 SBF. i redownloaded most of my old applications but a few of them for some reason will just not install and i just get the yellow /!\ mark that says "install unsuccessful" everytime. specifically angry birds and i few other paid apps do this to me and i really want to install them. i tried clearing market data and cache in settings but still did not work. so any help with this?
I know you sbf'ed. But is it possible some data got restored and possibly corrupted since when you log into your google account they automatically restore data for you? Have you tried using root explorer to browse through /data/app and see if there are any files there?
Of course you will have to be rooted to do that. just a thought. the only thing I could come up with.
Hi, i'm having an issue with this rom.
I factory reseted and both caches wiped. then installed base and reboot to this firmware and then back to recovery, flash update.
The issue is after I restore my backup with titanium backup pro (free version).
I get everytime "the process com.android.phone stopped unexpectedly"
What can I do to solve this, the dialer application works, but I don't know what keeps causing this error.
Thanks in advance.
what are you restoring from titanium? apps? or everything
i've just restored apps and system config. I unchecked all system files.
I only restore apps with data if I knew I wasn't having issues. I'll typically install fresh from the market no data just to make sure nothing corrupts the ROM. Sounds like like you are restoring an app that requires something that was blurred out. Try mega 2.0 then 4.3 update.
i personally wouldn't restore sys config. only apps plus data
i had a similar issue a while ago where the com.android.phone process was crashing all the time, it was due to a library that was inadvertently removed when i was modding some system apk files. if you could post a logcat capture it should show why it's crashing.
easiest way i found to do this is to forward the adb logcat output to a text file, from a command line type: adb logcat > logfile.txt
once you get the phone process to crash, you can hit ctrl+c to kill the command from the dos window. if you open up the logfile you just created, you should be able to search for com.android.phone and find a stack trace showing why the process ended.
May wanna try posting in Q&A or if you haven't, add your problem to the Homebase thread in development. May help, good luck.
avoid this rom...thats my solution.
Is anyone else able to install the latest update to Google Keyboard from the Market? I am unable to. I think I broke my Razr at some point, sadly. I manually updated to the new keyboard before they put it in the market (way back when). I have been able to get it to update in the past, but now, something is wrong, and it won't update...it keeps either telling me my certificate isn't correct, or it is already installed.
Things I have tried:
Making sure the following were the stock versions, and then removing all of them:
in /system/app:
Latin.apk, LatinIME.apk, LatinImeDictionaryPack.apk
in /system/lib:
libjni_latin.so, libjni_latinime.so
in /data/data:
com.google.android.inputmethod.latin
com.google.android.inputmethod.latin.dictionarypack
com.motorola.android.inputmethod.latin
I have tried wiping davlik-cache and cache, tried rebooting. Tried installing from market, and downloaded apk, using adb and pm install. It seems to either, if all the files are present, tell me that it can't install, as it is a different version of the certificate OR if I delete them all, it tries to install and reports the app is already installed.
Any suggestions?
Just to help anyone else find this post, some of the error messages I encountered that would help them find this in searching:
From the pm install, errors: INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES and INSTALL_FAILED_ALREADY_EXISTS
and from the dialogs in Android, when trying to do it from the market:
Application already exists, and Package file was not signed correctly.
Are you rooted? If so, have you tried uninstalling the keyboard with titanium backup, rebooting, then installing the new one from the play store?
Yep, I'm rooted, I should have mentioned that. I tried uninstalling with Titanium Backup, no luck. There must be some other thing that is colliding with the keyboard, something that I need to delete or clear, no idea. I am sure it is an odd problem to me, cause I got the keyboard manually before it came to market, but darned if I can figure this out. It really stinks, cause now I have only one choice, Swype. I really like and miss the Google Keyboard.
Only other thing that I can think of is if you are running a custom rom, do a dirty flash and then flash gapps. Otherwise you might have to do a complete wipe and start over.
RoboCuz said:
Is anyone else able to install the latest update to Google Keyboard from the Market? I am unable to. I think I broke my Razr at some point, sadly. I manually updated to the new keyboard before they put it in the market (way back when). I have been able to get it to update in the past, but now, something is wrong, and it won't update...it keeps either telling me my certificate isn't correct, or it is already installed.
Things I have tried:
Making sure the following were the stock versions, and then removing all of them:
in /system/app:
Latin.apk, LatinIME.apk, LatinImeDictionaryPack.apk
in /system/lib:
libjni_latin.so, libjni_latinime.so
in /data/data:
com.google.android.inputmethod.latin
com.google.android.inputmethod.latin.dictionarypack
com.motorola.android.inputmethod.latin
I have tried wiping davlik-cache and cache, tried rebooting. Tried installing from market, and downloaded apk, using adb and pm install. It seems to either, if all the files are present, tell me that it can't install, as it is a different version of the certificate OR if I delete them all, it tries to install and reports the app is already installed.
Any suggestions?
Just to help anyone else find this post, some of the error messages I encountered that would help them find this in searching:
From the pm install, errors: INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES and INSTALL_FAILED_ALREADY_EXISTS
and from the dialogs in Android, when trying to do it from the market:
Application already exists, and Package file was not signed correctly.
Click to expand...
Click to collapse
If your problem is in somewhere in data then a factory data reset is an option. But before you try that my restore thread allows you to try 3 different systems (stock, stock deodexed-debloat & if your are unlocked: a Telstra deodexed-debloat) and keep your data. They all need to be done is a series to keep data.
aviwdoowks said:
If your problem is in somewhere in data then a factory data reset is an option. But before you try that my restore thread allows you to try 3 different systems (stock, stock deodexed-debloat & if your are unlocked: a Telstra deodexed-debloat) and keep your data. They all need to be done is a series to keep data.
Click to expand...
Click to collapse
I managed to get this installed...I'm not sure exactly what I did to get it to work, and I still think I am somewhat broken, unfortunately. I removed the data directory, left all the .so and .apk files from stock, EXCEPT I took the Google Keyboard apk and manually stuck it into /system/app. I THEN did a pm install -r googlekeyboard.apk and it managed to install on top. I think I also (although not sure it helped) removed a rename line in /data/system/packages.xml about the package.
I don't have it linked in the market (in spite of trying with TB) and I don't have the Google Keyboard Settings app showing in my app tray, but the keyboard is there, selectable and seems to be working.
Cheers
RoboCuz
I am unable to install any version of google keyboard in my rooted Micromax A177.
I am on my second V20, H990DS this time and I am running Superv20 which I have been using the past few days and is a dream, bar these issues I have run into which seem to be related to each other.
I have been unable to get youtube vanced to install on this V20, and it returns with
'Installation failed for unkown reasons'
then in advanced
'java.io.FileNotFoundException: No such file or directory'
I was also restoring a backup with Titanium Backup from my other phone to get around snapchats root detection as magisk hide did not work. On restoring the app+data I am hit with a generic 'App not installed.' message, and then titanium hangs on the screen indefinitely until rebooting the phone (did manage to restore just Data after installing stock snapchat).
Then I remembered the first few times I attempted to setup the phone and update magisk and magisk manager. After updating magisk, the next time the phone was booted I got a simple grey background and small white writing filling half the screen with the first line stating something similar to
'Crash on the LK!' (might not be exact, didn't have my other phone to take a photo) and I had to reinstall the rom. I did this twice to test just in case it was a random issue.
My assumption is that it is related to storage somehow and I did manage to find one thread with a similar issue so I checked if internal was not the default install location, but pm get-install-location returns with
1[internal]
but also I have tried setting the storage to auto and external and neither worked (for vanced at least)
Unsure what to try next as my troubleshooting and searching for similar issues has run dry.
Help much appreciated and thanks in advance <3
-A9