So i unistalled messenger, to install messenger with old chat head bubbles for android 11 from this forum and that one crashed on start then i unistalled that one and installed messenger from google play and that one is now crashing too so i realized that is not a problem with the apk file. This is the report i am getting when i am launching :
java.lang.RuntimeException: java.io.FileNotFoundException: /data/user/0/com.facebook.orca/crash_log: open failed: EACCES (Permission denied) path: /data/user/0/com.facebook.orca/crash_log exists: false canWrite: false parent exists: true parent canWrite: false user id: 0 is system user: true openFileOutput error: /data/user/0/com.facebook.orca/files/crash_log: open failed: EACCES (Permission denied) at com.facebook.messenger.app.MessengerApplication.A051436) at X.003.AL95) at X.02s.run15) at Z.init(unknown) Caused by: java.io.FileNotFoundException: /data/user/0/com.facebook.orca/crash_log: open failed: EACCES (Permission denied) path: /data/user/0/com.facebook.orca/crash_log exists: false canWrite: false parent exists: true parent canWrite: false user id: 0 is system user: true openFileOutput error: /data/user/0/com.facebook.orca/files/crash_log: open failed: EACCES (Permission denied) at X.03r.<init>228) at X.00M.A0A167) at com.facebook.messenger.app.MessengerApplication.A05134) at X.003.AL95) at X.02s.run15)
I saw permission denied in report so i allowed every permission but that doesnt help too. My phone is Poco x3 Pro and it is on miui 12.5.2 EU version.
did you fixed this? i have the same problem
ignorujem said:
did you fixed this? i have the same problem
Click to expand...
Click to collapse
No actually, no one known the fix for this so far.
-deleted
CikaMare said:
No actually, no one known the fix for this so far.
Click to expand...
Click to collapse
I found a solution for myself.
I deleted the FACEBOOK FOLDER under "/root/Data/App/" and under "root/data/User/0/".
Then I deleted the app and reinstalled it from Play Store and it worked.
But your device must be rooted!
Samo671 said:
I found a solution for myself.
I deleted the FACEBOOK FOLDER under "/root/Data/App/" and under "root/data/User/0/".
Then I deleted the app and reinstalled it from Play Store and it worked.
But your device must be rooted!
Click to expand...
Click to collapse
Ah i think its worth a try. Will let you known if that fixes the problem for me
Samo671 said:
I found a solution for myself.
I deleted the FACEBOOK FOLDER under "/root/Data/App/" and under "root/data/User/0/".
Then I deleted the app and reinstalled it from Play Store and it worked.
But your device must be rooted!
Click to expand...
Click to collapse
Thank god it works! My Facebook app crashing after fresh installing from play store.
After uninstalling the app then just remove "com.facebook.katana" folder from "root/data/User/0/" and reinstall from play store it will work.
Kudos!!
If someone else has same problem then just open Titanium Backup, search for messenger app and (wipe data - frost - defrost) and then it should work again.
Root needed.
Related
Hi there!
I bought Runtastic PRO when I was using my Sensation with its stock ROM.
Recently I started rooting and flashing my HTC Sensation with this ROM: CM10. (The version from 19th of Oct. 2012)
The rooting was done via HTCdev.com, the Sensation is S-OFF.
Actually, I am using CWM 6.0.0.0, I wiped the cache, data and so on, cleared the Dalvik cache.
The problem, that arises is, that I am unable to (re-)install Runtastic PRO:
The market says the app is now incompatible with my device.
I changed the build.prop so it stated Nexus S, cleared the Store cache before and afterwards, rebooted.
adb install run.apk gives these entries in logcat:
Code:
E/PackageManager( 346): Package com.runtastic.android.pro2 requires unavailable shared library com.google.android.maps; failing!
W/PackageManager( 346): Package couldn't be installed in /data/app/com.runtastic.android.pro2-1.apk
I was looking around the internet and also here and the solution I found was to put two files from the gapps zips directly into /system:
com.google.android.maps.jar => /system/framework/
com.google.android.maps.xml => /system/etc/permissions/
Afterwards, I fixed the permissions and rebooted the device.
I tried copying the apk directly to /system/app/, fixed permissions and rebooted again, but the App does not show up at all.
Is this a ROM-based problem, a App-based problem or is it my fault?
Surely it's the last one...
Thanks in advance,
vista200
vista200 said:
Hi there!
I bought Runtastic PRO when I was using my Sensation with its stock ROM.
Recently I started rooting and flashing my HTC Sensation with this ROM: CM10. (The version from 19th of Oct. 2012)
The rooting was done via HTCdev.com, the Sensation is S-OFF.
Actually, I am using CWM 6.0.0.0, I wiped the cache, data and so on, cleared the Dalvik cache.
The problem, that arises is, that I am unable to (re-)install Runtastic PRO:
The market says the app is now incompatible with my device.
I changed the build.prop so it stated Nexus S, cleared the Store cache before and afterwards, rebooted.
adb install run.apk gives these entries in logcat:
Code:
E/PackageManager( 346): Package com.runtastic.android.pro2 requires unavailable shared library com.google.android.maps; failing!
W/PackageManager( 346): Package couldn't be installed in /data/app/com.runtastic.android.pro2-1.apk
I was looking around the internet and also here and the solution I found was to put two files from the gapps zips directly into /system:
com.google.android.maps.jar => /system/framework/
com.google.android.maps.xml => /system/etc/permissions/
Afterwards, I fixed the permissions and rebooted the device.
I tried copying the apk directly to /system/app/, fixed permissions and rebooted again, but the App does not show up at all.
Is this a ROM-based problem, a App-based problem or is it my fault?
Surely it's the last one...
Thanks in advance,
vista200
Click to expand...
Click to collapse
The app itself might not be compatible with Jelly Bean. All that other stuff you did shouldn't be necessary.
If installing the APK by itself (not through the Play Store) doesn't let it run, then Android Version incompatibility would be my guess. But it's just a guess without knowing anything about that app.
Hi,
I can't update to 4.4.2, because "TelephonyProvider.apk" has unexpected data. I'm not aware of any changes I did to it. Where can I download the 4.4.1 version? I found something here*, but it'll still not update to 4.4.2. Is there any other possibility of fixing this issue?
I use the Xposed Framework and AdAway, but deactivated both of them, rebooted and wiped the cache before trying to update.
Here is the whole message:
Code:
Installing: /sdcard/0/airdroid/upload/KitKat4.4.2.zip
Finding update package. . .
Opening update package. . .
Installing update. . .
Verifying current system. . .
" /system/app/TelephonyProvider.apk" has unexpected contents.
E: Error in /data/media/0/airdroid/upload/KitKat4.4.2.zip
(Status 7)
Installation aborted.
Thanks in advance!
*Not allowed to post outside links yet, sorry: http: //storagecow.eu/index.php?dir=Xda/Nexus%205/System%20Dump/app/&sort=size&order=asc
EDIT: Despite backing up TelephonyProvider.apk and TelephonyProvider.odex I can't use my N5 as a phone any more. The error message "Unfortunately, Phone has stopped." pops up every second or so. The only reason to avoid is is to enable Airplane mode. I copied the original files to /system/app using Root Browser, but it seems not to be recognized as installed. I can click on it and choose "Install". Anyways, after verifying the permissions it gets, there's a simple "App not installed." Sorry for being such a noob
I found it in this post. Now everything works just fine again
After several programs updated, the chrome icon changed to the generic android icon and the program would no longer start.
It doesn't show up in my apps list or in the package list returned by the adb shell.
Reinstallation from the play store fails with error -110.
Logcat shows me this error
Code:
W/PackageManager( 974): Trying to update system app code path from /data/app/com.android.chrome-2.apk to /data/app/com.android.chrome-1.apk
E/installd( 276): couldn't symlink directory '/data/data/com.android.chrome/lib' -> '/data/app-lib/com.android.chrome-1': File exists
W/PackageManager( 974): Failed linking native library dir (user=0)
W/PackageManager( 974): Package couldn't be installed in /data/app/com.android.chrome-1.apk
I know what this means (I think), but I haven't been able to find out what to do about it.
I'm using an unrooted Moto G with Kitkat 4.4.2 Build number KXB20.9-1.8-1.4
I'd like to make restoring the phone to factory defaults a very last resort.
Try doing a search in file manager and deleting all of the instances of Chrome, and then re-download from the play store.
Sent from my SCH-I535 using xda app-developers app
TDSJR said:
Try doing a search in file manager and deleting all of the instances of Chrome, and then re-download from the play store.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Chrome is a system app and, unless there's another way, I don't have access to the particular folder stated in the logfile to delete the offending file.
I have installed an apk file previously and now intend to install another updated apk file to my android phone. However the installation of the new apk file failed with message "an existing package by the same name with a conflicting signature is already installed".
I had tried to uninstall the first apk and then install the new apk file but the installation failed with the same message appeared. My phone is not rooted. Is there any way to rectify the error ?
Thank you in advance.
kclimkc330 said:
I have installed an apk file previously and now intend to install another updated apk file to my android phone. However the installation of the new apk file failed with message "an existing package by the same name with a conflicting signature is already installed".
I had tried to uninstall the first apk and then install the new apk file but the installation failed with the same message appeared. My phone is not rooted. Is there any way to rectify the error ?
Thank you in advance.
Click to expand...
Click to collapse
I found another user who could fix a similar issue with YouTube.apk: [Q] Installing the new YouTube V5 apk Issues (task's AOKP).
Maybe it works for you too.
Alternatively you can check if the un-installed (first) app is really completely uninstalled. Maybe it's a system app which still has some left-overs in another folder and is just "de-activated" or "disabled".
However, completely uninstalling of system apps requires root access.
If you still have issues and you can't contact the app/update dev for help, you can post your questions in the Android Development and Hacking > Android Q&A, Help & Troubleshooting forum.
Hy guys,
as already written in the topic I have accidentally uninstalled the calender app wich comes with emui.
now when I install e.g. the google calender app and open the app it says the calender storage is deaktivated. It gives me also the posibilety to activate in the settings but when I type it it comes back again.
So is there any possibilety to bring the original calender app back so I can activate the calender storage?
So I figured out that I have to reinstall the calendar storage APK . Can maybe somebody upload this APK for emui 5 or share a link where I can download the file.
I believe you can find a generic one online, nonetheless, here it is. Hopefully it works.
thanks a lot.
It's not working. I get the message "package appears to be corrupt".
Ok got it via adb.
now its working.
ChrisChros said:
Ok got it via adb.
now its working.
Click to expand...
Click to collapse
@ChrisChros how doid you solve the ADB error:
Code:
Failed to install Calendar_Storage_com.android.providers.calendar.apk: Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES: Failed to collect certificates from /data/app/vmdl499526276.tmp/base.apk: /data/ap
p/vmdl499526276.tmp/base.apk: File res/drawable-xhdpi-v4/app_icon.png in manifest does not exist]
Thanks for the help!
Might be a bit late, but if any others stumble upon this:
place the apk provided above in system/priv-app. Make sure it has all r/w permissions and then restart phone! Should work then.