Incompatible*with*other applications(s) using the same shared user data
ave just installed Official JB Rom from sam mobile singapore version...
now downloading maps from playstore and get this error...
Anybody know how to fix?
Error fixed by factory reset and reinstall new samsung account.
maybe it updated from my old rom and kept or corrupted some files caused problems?.
anyway if anyone gets this problem a factory reset will fix it..
MRBR7 said:
Error fixed by factory reset and reinstall new samsung account.
maybe it updated from my old rom and kept or corrupted some files caused problems?.
anyway if anyone gets this problem a factory reset will fix it..
Click to expand...
Click to collapse
+1
after spending quite a few hours following "tips" and directions from various sources, factory reset was the only one that resolved the incompatible <blah> shared user id issue!!
I think my issues were when i flashed the JB rom with mobile odin..
First i was on PA3.5 and it wouldnt work for some reason although at the time i was very tired as waiting a very long time to download the rom with slow speeds so maybe i did something wrong?.decided to flash recovery back to earlier version of Skyhigh Rom that was working ok then from here i installed the new stock rom over the top with mobile odin.It booted up and gave the android is updating screen.then loaded up with my custom launcher from the skyhigh rom.I thought this was funny as really should have wiped everything.I didnt even get the language change screen or set up its like it kept my old settings from skyhigh.Its as though it updated it and kept everything similar to an OTA update.as posted had the problems with Maps But then factory reset fixed it and wiped it clean again.This time i got the Laungauge screen on start up and the new stock lock/home screens..
Related
Is anyone else experiencing market issues after updating firmware to 4.0.3? I can see my apps and search etc fine but when I try to download an app it says:
"... could not be downloaded because due to an error. (-101)"
I tried flashing the 4.0.1 firmware since market was working on it, but i still get the same issue.
I also tried clearing market cache and date, force closing it, and nothing works. I also tried reinstalling market and still same issue.
Anybody has an idea what the problem is and how to fix it?
Try clearing the cache and dalvik in recovery. also what i would do is go into cwm first reflash and then fix permissions then clear those things.
cameljockey1 said:
Try clearing the cache and dalvik in recovery. also what i would do is go into cwm first reflash and then fix permissions then clear those things.
Click to expand...
Click to collapse
Tried but it didnt fix it...
im having the same issue im running the newest elegancia rom everything is running fine except this issue with the market ..................NEED SOME HELP HERE
The problem went away for me last night but now all of sudden I'm getting the same error... then it went away again.
I can't really figure out how it went away... I did restore a nandroid backup yesterday before the problem went away, but I don't think that's what fixed it since I had tried that before...
Market Problems - Solution
I was having the exact same issues. I was running MIUI.us 1.12.23. I went online and found 1.12.30. Once I upgraded my problem was gone.
However, the new firmware is still eating up my battery!
David
I was having the same problems after 4.0.3 RUU install (rooted).
I cleared the market data and cache and UNINSTALLED MARKET UPDATE rebooted my device and everything was fine!
Hi
I have been using Jaggyrom 4.1 for last few months on my htc explorer
Few days earlier it started dispaying error android.process.acore and android.process.htccontacts stopped unexpectedely
I searched this forum and google for the resolution of this error but nothing worked
Finally I flashed the latest jaggyrom 5 after wiping everything i.e /facotry reset wipe all, /system, /data, /cache
After setting up all after first boot the problem again starts same error
Your help required
Regards
Rizwan
Can anybody suggest a solution for this problem?
I have reflashed the rom many time after wiping everything
rizwan65 said:
Can anybody suggest a solution for this problem?
I have reflashed the rom many time after wiping everything
Click to expand...
Click to collapse
If you are using OC then under clock it.. I havent used jaggyrom so cant tell about it perfectly..
And if you r using ext partition.. then format it through any partition wizard software..
If still facing FC's then create a new partition again through recovery.. then flash the ROM again and try..
Well thanks for your reply
I am not using OC version of Jaggy Rom
I have also tried to flash back 4.1 version the problem persists
I have also tried your suggestions but I came to know one thing
Yesterday I reflashed V.5 of Jaggy Rom from scratch and was not able to add google account in setup due to unavailability of WiFi for few hours
My phone was working fine no such problem occured for 5 to 6 hours
But as soon as I added google account in setup within few minutes the problem started process acore and htccontacts started crashing
After that I again reflashed and turned off my WiFi to check it again same occurred as soon as I added/linked google account with phone
Any suggestion in this view
Regards
Rizwan
rizwan65 said:
Well thanks for your reply
I am not using OC version of Jaggy Rom
I have also tried to flash back 4.1 version the problem persists
I have also tried your suggestions but I came to know one thing
Yesterday I reflashed V.5 of Jaggy Rom from scratch and was not able to add google account in setup due to unavailability of WiFi for few hours
My phone was working fine no such problem occured for 5 to 6 hours
But as soon as I added google account in setup within few minutes the problem started process acore and htccontacts started crashing
After that I again reflashed and turned off my WiFi to check it again same occurred as soon as I added/linked google account with phone
Any suggestion in this view
Regards
Rizwan
Click to expand...
Click to collapse
Well you can do is flash the rom after booting skip adding account.. Finish your setup.. Restart your phone..
Then using wi fi add your google account.. If still problem remains.. Reflash you rom again.. again skip adding account..
Install the two files attached.. Restart your device.. Then try to add acount..
I got a Nexus 5 been using CM on it for a while now. Currently i have 11-20140708-SNAPSHOT-M8
the build date is july 8. I've been getting CM update for a new version for like a month now, tried installing it a couple of times, when i press to reboot and install it says it installed it, and after the phone reboots, it's still the same old version, and i keep getting the notification to upgrade, but i can't.
So I waited for another new build, thinking this is just some bug in the update. Yesterday a new version prompted for a update, but the same happened. So i tried to download the zip from CM website and flash it on recovery manually. And i got an error:
Can't install this package on top of incompatible data. (Status 7) installation aborted.
I used to update with no problems, but I seem to be stuck on the july 8 build.
Anyone else dealing with this, or know how to fix this?
Is your bootoader up-to-date? CM often require you to have latest bootloader
No. I haven't upgraded it. I've found multiple threats about it, I'm not sure which one is the right to do so. As i'm not really familiar with this kind of stuff.
EDIT: My BL version is HHZ11K. From what i gathered it's the most recent one.
TheSidiO said:
Can't install this package on top of incompatible data. (Status 7) installation aborted.
Click to expand...
Click to collapse
Sounds like you're dirty flashing but something in your current set up has been corrupted. You may need to factory reset or do a clean install.
Wakamatsu said:
Sounds like you're dirty flashing but something in your current set up has been corrupted. You may need to factory reset or do a clean install.
Click to expand...
Click to collapse
Was thinking if I can salve the problem without doing that. But i did a factory reset and it fixed the problem.
Thanks for the responses.
problems updating monthly snapshots of CM
Hi, I have been looking everywhere to see why I am having difficulties updating Cyanogen snapshots every month. I found this post but I don't really know if it pertains to my problem. I have a google rooted nexus 5 and every month when I try to update my phone begins acting up. It starts saying unfortunately google play services has stopped working. I see my apps trying to install but all I get are error notification icons at the top and they won't download. I posted on g+ and someone says it has to do with titanium. Im at a loss. Its very frustrating as I've tried almost everything I can think of to no avail. I try to go to the playstore and it's like I have no connection. I do have and use titanium backup for the apps I want to restore. I spoke to someone that has the same phone and he tells me to just flash the update without wiping but it doesn't work for me. I don't know if its a setting I'm missing on titanium or what it is but it sucks. With the 2 last updates this has happened. Leaving me with no option but to download the CM snapshot along with gapps. Wipe my phone and flash both the snapshot and gapps and start from scratch. I hope you can help me. Hopefully I'm in the right place. Tx you
acf150 said:
Hi, I have been looking everywhere to see why I am having difficulties updating Cyanogen snapshots every month. I found this post but I don't really know if it pertains to my problem. I have a google rooted nexus 5 and every month when I try to update my phone begins acting up. It starts saying unfortunately google play services has stopped working. I see my apps trying to install but all I get are error notification icons at the top and they won't download. I posted on g+ and someone says it has to do with titanium. Im at a loss. Its very frustrating as I've tried almost everything I can think of to no avail. I try to go to the playstore and it's like I have no connection. I do have and use titanium backup for the apps I want to restore. I spoke to someone that has the same phone and he tells me to just flash the update without wiping but it doesn't work for me. I don't know if its a setting I'm missing on titanium or what it is but it sucks. With the 2 last updates this has happened. Leaving me with no option but to download the CM snapshot along with gapps. Wipe my phone and flash both the snapshot and gapps and start from scratch. I hope you can help me. Hopefully I'm in the right place. Tx you
Click to expand...
Click to collapse
So here is what i would try to do. reboot into recovery. do a factory reset, make sure you backup your files as this cleans them. And then make the update from the updater or download it manually from cm website.
updating CM snapshot monthly problems
TheSidiO said:
So here is what i would try to do. reboot into recovery. do a factory reset, make sure you backup your files as this cleans them. And then make the update from the updater or download it manually from cm website.
Click to expand...
Click to collapse
Almost what I did, i l always do a nandroid backup before flashing anything in recovery, I downloaded the snapshot and the gapps, wiped, and installed snapshots along with gapps. So your telling me to just do a backup in recovery before updating that it cleans my files, then without wiping to try to update just the CM update from either my phone or their website? No gapps? Will try next time thanks.
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
So anyone else having random restart issues no matter what firmware you are running?
I am having this issue even after updating the firmware (yes I managed to get it updated lol didn't realize need to do it in increments rather straight to the latest).
I found a work around sort of but it requires having my hotspot on and another device connected at all times to keep the phone from restarting randomly.
Has anyone else ran into this issue and have a fix? Could it be a battery optimization setting?
Thanks
i got it when i update the rog 5 to latest version so i factory reset it then worked well
messhary said:
i got it when i update the rog 5 to latest version so i factory reset it then worked well
Click to expand...
Click to collapse
Ok thank you for replying, I just finished backing up with Migrate and going to do a factory wipe and then restore all my apps. Hopefully that solves my issues.
I have the same problem for last two firmware updates, for each update I need to do a full factory reset in order to let it work again!