After updating to Lollipop on my Nexus 5, it restored all of my apps except for about 10. One of them is a widget that I use everyday called Simple Calendar Widget by MYCOLORSCREEN. When trying to download the app, it gives me the message "Unknown error code during application install: -505". It seems to download fine, but the message pops up during the install process. Anybody know about this issue or experiencing the same thing if you try to download this application? I also tried downloading the apk file online but that also fails to install. I can't find any info regarding this issue. Thanks.
I had this issue on certain apps as well. The dev of those apps needed to change something for it to work on Lollipop.
RoomTenONine said:
I had this issue on certain apps as well. The dev of those apps needed to change something for it to work on Lollipop.
Click to expand...
Click to collapse
I've had this problem. Did a search with Google and it seems others are having this issue. Hopefully Google will have an update to fix.
Do a search in this forum. I replied with the cause and solutions. Was posted last week.
Sent from my Nexus 5 using Tapatalk
nikon120 said:
Do a search in this forum. I replied with the cause and solutions. Was posted last week.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Code 505 is a permissions code. This typically means that the APK file already exists in your /data/app folder. You'll need to locate the APK files in question in the /data/app folder and remove them. You will need root to perform this action.
You came across this problem because you didn't do a wipe of your userdata partition when you jumped from Kitkat to Lollipop. I encountered the same issue because of that reason. I just ended up wiping and starting fresh as my phone hadn't been wiped since I got the device last November.
Click to expand...
Click to collapse
Are you sure? I flashed the factory image of Lollipop on my phone and it wiped everything. Afterwards, I had to also do a factory reset of my phone from the settings due to a storage issue. Why would that get left behind?
Edit: I checked (phone is rooted) and the app isn't in the /data/app folder
PMamba said:
Are you sure? I flashed the factory image of Lollipop on my phone and it wiped everything. Afterwards, I had to also do a factory reset of my phone from the settings due to a storage issue. Why would that get left behind?
Edit: I checked (phone is rooted) and the app isn't in the /data/app folder
Click to expand...
Click to collapse
I spent an hour combing through Google group threads trying to get a real answer to this outstanding question. I was perplexed that only two applications of mine refused to install due to this error. The consensus was that the APK file was still there, or some remnants of data related to the application remained on the device that the Play Store service didn't like.
I ended up wiping my device twice:
Once by flashing both the userdata.img and cache.img files, which ended up giving me the storage issue bug on Lollipop. (Showing 16GB instead of 32GB)
Second by performing a factory reset from within the booted OS, which resolved the storage issue.
After that, everything was good to go. Have yet to encounter this error code again.
PMamba said:
After updating to Lollipop on my Nexus 5, it restored all of my apps except for about 10. One of them is a widget that I use everyday called Simple Calendar Widget by MYCOLORSCREEN. When trying to download the app, it gives me the message "Unknown error code during application install: -505". It seems to download fine, but the message pops up during the install process. Anybody know about this issue or experiencing the same thing if you try to download this application? I also tried downloading the apk file online but that also fails to install. I can't find any info regarding this issue. Thanks.
Click to expand...
Click to collapse
I just had to click install again after the error and it worked for me. It was a PITA.
sigh, I've had this issue with terminal emulator
C:\>adb install Term.apk
3966 KB/s (515876 bytes in 0.127s)
pkg: /data/local/tmp/Term.apk
Failure [INSTALL_FAILED_DUPLICATE_PERMISSION perm=jackpal.androidterm.permission
.PREPEND_TO_PATH pkg=com.jrummy.liberty.toolbox]
Click to expand...
Click to collapse
So yeah...duplicate permissions, in this case i had ROM Toolbox Lite installed which had the same permission sooooo it's one or the other at the moment
bleets said:
sigh, I've had this issue with terminal emulator
So yeah...duplicate permissions, in this case i had ROM Toolbox Lite installed which had the same permission sooooo it's one or the other at the moment
Click to expand...
Click to collapse
Hm alright. Where does the apk file need to be in order to use the adb install command? I want to see which app is conflicting with.
PMamba said:
Hm alright. Where does the apk file need to be in order to use the adb install command? I want to see which app is conflicting with.
Click to expand...
Click to collapse
as long as you have adb working it can be anywhere as long as you know the path
so adb install c:\path\to\file.apk
as it happens with terminal emulator i could download the apk seperately, with other apps i'd probably download on my tablet and pull it off that
bleets said:
as long as you have adb working it can be anywhere as long as you know the path
so adb install c:\path\to\file.apk
as it happens with terminal emulator i could download the apk seperately, with other apps i'd probably download on my tablet and pull it off that
Click to expand...
Click to collapse
Wow it looks like GTasks is conflicting. Without GTasks this app is useless. :crying:
Thanks though.
PMamba said:
Wow it looks like GTasks is conflicting. Without GTasks this app is useless. :crying:
Thanks though.
Click to expand...
Click to collapse
https://code.google.com/p/android-developer-preview/issues/detail?id=1668
hopefully it'll get sorted...
You'd have thought people testing would have installed enough apps to come across it and if google knew about it in october why not fix it
I had this issue trying to install Rom Toolbox. I uninstalled Terminal Emulator and the issue went away, probably because Terminal Emulator is included in Rom Toolbox.
How I solved it
In bootloader mode I flash from the factory image userdata and cache, then I wipe Dalvik, data and cache in TWRP after the first boot I skip the setup just too full factory data reset, in the second boot, I set up everything normal, but instead of restoring from previous devices I set it up as a new device, then I manually download the app that was giving the error, it installed without a problem.
I know is a little too much for an app, but it works for me.
onetraakmind said:
I had this issue trying to install Rom Toolbox. I uninstalled Terminal Emulator and the issue went away, probably because Terminal Emulator is included in Rom Toolbox.
Click to expand...
Click to collapse
Exactly.
Thank you very much for the tip.
onetraakmind said:
I had this issue trying to install Rom Toolbox. I uninstalled Terminal Emulator and the issue went away, probably because Terminal Emulator is included in Rom Toolbox.
Click to expand...
Click to collapse
I'm currently having the issue everyone mentions, except I already have ROM Toolbox Pro and was trying to install Terminal Emulator. Terminal Emulator in ROM Toolbox currently FC's on Stock (rooted) 5.0.1. But I use other features, like the Rebooter that I don't wanna sacrifice for just Terminal Emulator haha. Wish they'd fix this issue permanently
Jleeblanch said:
I'm currently having the issue everyone mentions, except I already have ROM Toolbox Pro and was trying to install Terminal Emulator. Terminal Emulator in ROM Toolbox currently FC's on Stock (rooted) 5.0.1. But I use other features, like the Rebooter that I don't wanna sacrifice for just Terminal Emulator haha. Wish they'd fix this issue permanently
Click to expand...
Click to collapse
Uninstall ROM toolbox, install terminal emulator, install ROM toolbox... Someone said that worked.
rootSU said:
Uninstall ROM toolbox, install terminal emulator, install ROM toolbox... Someone said that worked.
Click to expand...
Click to collapse
You really should look in the rom toolbox pro app a little better. There is an emulator built in
Sent from my One M8 using Tapatalk
mattie_49 said:
You really should look in the rom toolbox pro app a little better. There is an emulator built in
Sent from my One M8 using Tapatalk
Click to expand...
Click to collapse
I know, that's why you can't install jackpal terminal emulator if you have ROM toolbox installed as it uses the same permissions.
Although you should read up yourself because if you did, you'd know the terminal emulator in rom toolbox force closes on lollipop on the nexus 5.
I understand this is a old thread but I fixed it a way that wasn't mentioned in this thread. Just thought I'd share for anyone googling this issue and finding this. What I did was go into the guest account and uninstall the app that was causing the issue such as snapchat. The way I caused it in the first place was installing snapchat on aptoide which installed it on both my account and the guest account and I decided I didn't want snapchat anymore so I uninstalled it but it was still there on the guest account which caused the error 505 whenever I tried to reinstall snapchat.
Related
So I spent a lot of time trying to get this working, and I finally did and I figured I'd share how I did it. It works for me, and a user of Google + confirmed it too. It's pretty simple. Thanks to Dustin Evans on Google+ (https://plus.google.com/u/0/108019745978944993252/posts) and XDA user garner.
first, find your build.prop in /system. Please use Root Explorer, I'm not sure if other file browsers save it correctly. Mount Read/Write and long press on build.prop and hit "Open in text editor".
Change the following lines to look like this:
ro.product.model=SPH-L710
ro.product.name=d2spr
ro.product.device=d2spr
reboot after.
after that head here http://forum.xda-developers.com/showthread.php?t=1965895 and download the wallet apk. (not all the gapps, just the wallet apk). It should work!
Im running cm 10.1 but it also worked on cm 10.
also this is my first post, feedback?
EDIT: I know that there are other posts describing how to do this but I found that they either didn't work for me or involved more complex steps. I'm sharing this because i found it to be easier and completely successful.
You should have used the search function on here. Would have saved you tons of time trying to get it to work. Also you should be able to download the apk from the market once you change these settings inyour build.prop file as well.
http://forum.xda-developers.com/showthread.php?t=1794727
Or you could just use this http://forum.xda-developers.com/showthread.php?p=34896632 and it will change build.prop for you and install wallet!
Sent from my SCH-I535 using xda premium
stearic said:
You should have used the search function on here. Would have saved you tons of time trying to get it to work. Also you should be able to download the apk from the market once you change these settings inyour build.prop file as well.
http://forum.xda-developers.com/showthread.php?t=1794727
Click to expand...
Click to collapse
thanks, but i knew that. i dont think you can just download it, as i did that and it didnt work so well. i know there are other methods, but those are sketchy and involve flashing a new recovery (the all in one installer). this is a more clean way that i got it to work.
just trying to share my experience
also this does not involve flashing anything
Nope, i changed the build.prop file, rebooted and it showed up in the market. Installed it and it works perfectly. The method i mentioned did say you to flash stuff, but that's with the touchwiz based roms. But it also does say pretty much do what you have said as well.
Insufficient privleges
I changed the build prop like shown and was able to download. But when app is ran it states that I have insufficient privileges for this system image. I am just running a rooted image of stock do I need to flash a new rom for it to work?
GSHARPE3 said:
I changed the build prop like shown and was able to download. But when app is ran it states that I have insufficient privileges for this system image. I am just running a rooted image of stock do I need to flash a new rom for it to work?
Click to expand...
Click to collapse
Yeah I got the same error, running rooted stock.
crazymadbaby said:
Or you could just use this http://forum.xda-developers.com/showthread.php?p=34896632 and it will change build.prop for you and install wallet!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Doesn't work.
It tells me i'm an unsupported device.
Santinelli said:
Yeah I got the same error, running rooted stock.
Click to expand...
Click to collapse
Yeah that just means you need to flash the Touchwiz libs zip file that's floating around the forums, then Wallet will work. I have the .zip file here: https://www.dropbox.com/s/lp7qj8odmhobwtu/D2VZW-Wallet-TW-JB-R81.zip
bogedy said:
So I spent a lot of time trying to get this working, and I finally did and I figured I'd share how I did it. It works for me, and a user of Google + confirmed it too. It's pretty simple. Thanks to Dustin Evans on Google+ (https://plus.google.com/u/0/108019745978944993252/posts) and XDA user garner.
first, find your build.prop in /system. Please use Root Explorer, I'm not sure if other file browsers save it correctly. Mount Read/Write and long press on build.prop and hit "Open in text editor".
Change the following lines to look like this:
ro.product.model=SPH-L710
ro.product.name=d2spr
ro.product.device=d2spr
reboot after.
after that head here http://forum.xda-developers.com/showthread.php?t=1965895 and download the wallet apk. (not all the gapps, just the wallet apk). It should work!
Im running cm 10.1 but it also worked on cm 10.
also this is my first post, feedback?
Click to expand...
Click to collapse
Can I change these values in build.prop back after google wallet is working, or no?
not for stock samsung
Santinelli said:
Yeah I got the same error, running rooted stock.
Click to expand...
Click to collapse
this is for cm 10/10.1
specialkcf said:
Can I change these values in build.prop back after google wallet is working, or no?
Click to expand...
Click to collapse
nope, but why would you need to? it basically makes it so that you able to get through any barriers verizon put in your way for any app
Device not Ready
I am getting the following error when trying to run Google Wallet.
Deviice Not Ready
Wallet is unable to proceed until this device is fully initialized. Make sure the device has network access and try rebooting if the problem persists.
I have rebooted to no avail. Any suggestions?
krmtdfrg said:
I am getting the following error when trying to run Google Wallet.
Deviice Not Ready
Wallet is unable to proceed until this device is fully initialized. Make sure the device has network access and try rebooting if the problem persists.
I have rebooted to no avail. Any suggestions?
Click to expand...
Click to collapse
sorry i didnt see this. if its still an issue, which im assuming its not, more details please?
My Google account was being wiped out in front of my eyes almost every other time i rebooted. After some thread reading and trial and error I finally figured it out. Its been about 18 hours and over 15 reboots (EDIT: Few days now ) either via reboot menu, wanamXposed module and adb, I have not lost my account so far.
This is still being tested, so affected users please test and comment how it worked for you.
There are hundreds of posts out there that tell you the fix is to be on Google play Store version 4.4.21 and many of them have reported that it works. Unfortunately many including me, were on the very same version and yet Google account was being wiped no matter what. Thats when i realized, it is not just being on 4.4.21, but having that version as a system app, instead of having the version installed as an update. The difference is, when you have version 3.x.x installed as a system app, which updates itself to 4.4.21, it does not update the original app, but instead installs updates in the /data partition. So seeing version 4.4.21 in the Playstore app 'About' settings does not mean anything.
Verify if you are on an affected release.
Go to Setting >> more >> Application Manager >> Downloaded. If you see 'Google Play Store' you may be affected.
Now go to the application managers "All" Section (swiping leftward from 'Downloads' section) and navigate to 'Google Play Store'
You will see the version number of your app. Next to it, you will see two buttons, One of them may be "uninstall updates" If you see this option, your version number means nothing. Don't be fooled by it, you have may 4.4.21 installed, but in your /data/app directory.
If the above was true, you have an older version of playstore installed as a system app, and have the latest version installed as an update over the old version in the /data partition.
Instructions
Flash GoogleWipeFix_Flash_CWM.zip from Clockworkmod.
PS: This really only removes your existing Google Play Store, flashes v 4.4.21 and clears data. You may as well flash it, nothing to loose.
Click Show content for Manual Instructions (Not needed if you chose to flash instead).
You do not need this if you flash using my zip. This is for Manual Testing only.
If you are not already on PlayStore version 4.4.21 then download version 4.4.21 and place in in your SDCard as /sdcard/Phonesky.apk
DOWNLOAD
Google Play Store 4.4.21
Instructions for shell users :
Code:
su
mount -o remount, rw /system
cp /system/app/Phonesky.apk /system/app/Phonesky.apk.bkp
mv /data/app/com.android.vending-1.apk /data/app/com.android.vending-1.apk.bkp
cp /sdcard/Phonesky.apk /system/app/Phonesky.apk
chmod 644 /system/app/Phonesky.apk
reboot
Instructions for Root explorer users
Re-mount /system as read-write
Backup /system/app/Phonesky.apk
Backup and Delete /data/app/com.android.vending-1.apk (TIP: you may see warnings that PlayStore Stopped, Thats ok!)
Copy /sdcard/Phonesky.apk and overwrite /system/app/Phonesky.apk
Give the new apk appropriate read permissions to all. rw-r--r--
reboot
Click to expand...
Click to collapse
Troubleshooting help
If it does not work for you, it would be of great help if you could post below details.
What rom are you on?
Please check the following:
Go to application manager >> Google Play Store and tel me if you see the button "Uninstall updates" next to "Force Stop"
If you have "Uninstall updates" you need to click it, and then repeat the whole procedure again.
Do you have access to adb or terminal emulator app? if yes, please give me the output of the following.
Code:
su
ls -l /data/app/com.android.ven* /system/app/Phonesky.*
Click to expand...
Click to collapse
I added a CWM flashable zip. Try that if it didn't work earlier.
XDA:DevDB Information
GoogleWipeFix, a Tool/Utility for the Samsung Galaxy Note II
Contributors
kkoolpatz
Version Information
Status: Testing
Created 2013-11-02
Last Updated 2013-11-05
I use my own cooked rom which is posted in the forums as well.. I have hardly had any gapps issues.. Had them once in the beginning but flashing the latest gapps solved everything..!
Thanks for sharing
kkoolpatz said:
Verify if you are on an affected release.
Go to Setting >> more >> Application Manager >> Downloaded. If you see 'Google Play Store' you may be affected.
Now go to the application managers "All" Section (swiping leftward from 'Downloads' section) and navigate to 'Google Play Store'
You will see the version number of your app. Next to it, you will see you buttons, One of them may be "uninstall updates" If you see this option, your version number means nothing don't e fooled by it. you have may 4.4.21 installed, but in your /data/app directory.
Click to expand...
Click to collapse
I am using Tigra v.3 ROM, which has the 4.4.21 version as system app and still I had the Google account wiped yesterday after a reboot from Wanam Xposed.
So maybe your fix solves some problems, but in my case...
Thanks anyway!
My ROM users are already on 4.4.2.1 by default (removed everything related to old versions) and they still have account lost.
The problem is only in XXUEMI6, XXUEMJ2/5 don't have this problem.
Thanks for sharing
tried this on my n7105T
no i no longer get the force close / crash message
just no connection (like i was getting prior to trying a million other fixes)
including factory reset
I haven't been on the forums much lately but can't see anything about this - what is the bug exactly? All your google data being deleted on just the account being removed from the phone? Or something else entirely?
dhuewes said:
I am using Tigra v.3 ROM, which has the 4.4.21 version as system app and still I had the Google account wiped yesterday after a reboot from Wanam Xposed.
So maybe your fix solves some problems, but in my case...
Thanks anyway!
Click to expand...
Click to collapse
Its just been one day, so i'm hoping this fix stays permanent. Are you sure you do not have /data/app/com.android.vending-1.apk installed?
fliptechnologies said:
tried this on my n7105T
no i no longer get the force close / crash message
just no connection (like i was getting prior to trying a million other fixes)
including factory reset
Click to expand...
Click to collapse
What do you mean by no connection? I am not sure if this will apply to your device since this caters specifically to Note 2 leaked roms.
Tamen said:
I haven't been on the forums much lately but can't see anything about this - what is the bug exactly? All your google data being deleted on just the account being removed from the phone? Or something else entirely?
Click to expand...
Click to collapse
If you are on one of the affected roms, after you reboot Google account is totally removed. As if it was never added. Its known to happen on Note 2 android 4.3 leaked MI6 rom
I've tested your possible Fix.... Had 3 reboots in total now... so far so good... No G account yet....
Sent from my GT-N7100 using XDA Premium 4 mobile app
I just did try.
I didnt have vending-1.apk in my data folder so didnt do anything with that.
Also when we copy phonesky.apk , do we need to set permission to rw.r.r ???
I actually did it. And now trying.
Sent from my GT-N7100 using xda app-developers app
I just moved the updated version to /system/app and removed Phonesky.apk.
I'm gonna check out if it does anything, smart tip btw, never thought of this.
I've given it a try, thanks.
Thanx man
Sent from my GT-N7100 using XDA Premium 4 mobile app
Yes,the fix works...rebooted nearly ten times today,no google account loss.
Just remember to set permission as rw-r-r for phonesky.apk after replacing the old one.
akp.ajinkya said:
Yes,the fix works...rebooted nearly ten times today,no google account loss.
Just remember to set permission as rw-r-r for phonesky.apk after replacing the old one.
Click to expand...
Click to collapse
Thanks, I'll add the permissions part to OP
I followed your full procedure, the problem persists, wanam v4.0 (mi6).
hi
I have noticed that whenever i fiddle with xposed, my account gets wiped. Otherwise no loss on reboot. Just what i have observed.
kkoolpatz said:
Thanks, I'll add the permissions part to OP
Click to expand...
Click to collapse
Worked for me on Hurricane v5, note3 apps and Superwolf theme 10.5 -- Thanks
Alipk52 said:
I followed your full procedure, the problem persists, wanam v4.0 (mi6).
Click to expand...
Click to collapse
Thanks for reporting. I wonder if you need to remove .odex file since wanam is an odex rom
Please check the following for me.
Go to application manager >> Google Play Store and tel me if you see the buttons "Uninstall updates" and "clear data"
If you have "Uninstall updates" something went wrong in your procedure.
Do you have access to adb or terminal emulator app? if yes, please give me the output of the following.
Code:
su
ls -l /data/app/com.android.ven* /system/app/Phonesky.*
I can't install the google camera apk, it says there is a conflicting package, but google camera is not installed on my phone :/
I've tried looking for it in the settings/apps and with tools like titanium backup
I also tried adb shell pm list packages, not there!
but I can't install it! help!
Nexus 5 android 7.1.2
GizmoTheGreen said:
I can't install the google camera apk, it says there is a conflicting package, but google camera is not installed on my phone :/
I've tried looking for it in the settings/apps and with tools like titanium backup
I also tried adb shell pm list packages, not there!
but I can't install it! help!
Nexus 5 android 7.1.2
Click to expand...
Click to collapse
Root your phone with superSU, open lucky patcher, select install. Click on google camera apk. Select uninstall and install done!! Reboot
GopalKaul said:
Root your phone with superSU, open lucky patcher, select install. Click on google camera apk. Select uninstall and install done!! Reboot
Click to expand...
Click to collapse
whats lucky patcher?
my phone is already rooted with supersu
GizmoTheGreen said:
whats. . .
my phone is already rooted with supersu
Click to expand...
Click to collapse
It is actually warez and is not allowed to even be talked about on XDA. Should a mod come across this topic, both of your replies will be deleted for even mentioning it.
RoyJ said:
It is actually warez and is not allowed to even be talked about on XDA. Should a mod come across this topic, both of your replies will be deleted for even mentioning it.
Click to expand...
Click to collapse
oh I see, I had no idea! I won't be looking into it.
but it there a good tool that can fix glitched packages? my system thinks com.google.android.GoogleCamera is installed but I can't find it anywhere and any install of it is blocked x'D
for now I installed a modded one I found on xda that let's you have older + latest 4.2 with modified package name com.google.android.GoogleCameraMOD and it's working....
Are you on Pure Nexus, by chance? I know you're not stock since you mentioned 7.1.2. If you're using that ROM, in the download section underneath the ROM and gapps, there's a camera fix zip and you need to flash that as well. @GizmoTheGreen
RoyJ said:
Are you on Pure Nexus, by chance? I know you're not stock since you mentioned 7.1.2. If you're using that ROM, in the download section underneath the ROM and gapps, there's a camera fix zip and you need to flash that as well. @GizmoTheGreen
Click to expand...
Click to collapse
I'm on santhoshm aosp rom, looking at that zip it seems to be a fix for hdr+ on nougat roms... which is not my problem
I can try it later anyway see if it shows up in my system
you maybe need to wipe data :crying:
GizmoTheGreen said:
I can't install the google camera apk, it says there is a conflicting package, but google camera is not installed on my phone :/
I've tried looking for it in the settings/apps and with tools like titanium backup
I also tried adb shell pm list packages, not there!
but I can't install it! help!
Nexus 5 android 7.1.2
Click to expand...
Click to collapse
Use a root file explorer like ES and check for old Google camera folders in system and delete them, then try again
Char_G said:
Use a root file explorer like ES and check for old Google camera folders in system and delete them, then try again
Click to expand...
Click to collapse
I've done that, no such folder or file in the system app folder
GizmoTheGreen said:
oh I see, I had no idea! I won't be looking into it.
but it there a good tool that can fix glitched packages? my system thinks com.google.android.GoogleCamera is installed but I can't find it anywhere and any install of it is blocked x'D
for now I installed a modded one I found on xda that let's you have older + latest 4.2 with modified package name com.google.android.GoogleCameraMOD and it's working....
Click to expand...
Click to collapse
welp now I need that APK again and can't find it for the life of me been googling for an hour checking all possible results x'D
Hi ..My Phone Is Samsung S8 plus
when download and apk installed eror in installed
app not installed the package conflicts with an existing package by the same name
works of
I did the following, but the error did not correct
I did do all the methods
1- Reinstall the orignal
2- Delete cache and Data
3-Uninstall your original apps
4- shortcut app tohome screen
4-Restart your phone
and ....
but when download and apk installed eror in installed or download in market again eror instaled
pleas help me How to solve this problem
َSoftware information : android securiy 1 august 2017
android 7.0
samsung experience version 8.1
pleas help me
you can't install apps that have been signed by a different developer, and replace with the current one. metaphor, you have a girlfriend, but your trying to get another girl who looks, and smells like your current girl, but her name is different. Since your in a beta OS, you can definitely expect bugs.
have you tried Factory data reset? there may be residual files from previous OS.
Sent from my SM-G955U using Tapatalk
mojirezaie198888 said:
Hi ..My Phone Is Samsung S8 plus
when download and apk installed eror in installed
app not installed the package conflicts with an existing package by the same name
works of
I did the following, but the error did not correct
I did do all the methods
1- Reinstall the orignal
2- Delete cache and Data
3-Uninstall your original apps
4- shortcut app tohome screen
4-Restart your phone
and ....
but when download and apk installed eror in installed or download in market again eror instaled
pleas help me How to solve this problem
َSoftware information : android securiy 1 august 2017
android 7.0
samsung experience version 8.1
pleas help me
Click to expand...
Click to collapse
If you have secure boot on disable it, restart your phone, try Again. Worked for me couple times
It's a vice versa situation. If your secure boot is on then disable it else vice versa. And reboot your phone and then install the app. It will surely install. Its not like you've a girlfriend situation?
djnikkofb said:
you can't install apps that have been signed by a different developer, and replace with the current one. metaphor, you have a girlfriend, but your trying to get another girl who looks, and smells like your current girl, but her name is different. Since your in a beta OS, you can definitely expect bugs.
have you tried Factory data reset? there may be residual files from previous OS.
Click to expand...
Click to collapse
You're** and it's not beta tester.
britchel said:
You're** and it's not beta tester.
Click to expand...
Click to collapse
No Itsnot Beta
eddyo1993 said:
If you have secure boot on disable it, restart your phone, try Again. Worked for me couple times
Click to expand...
Click to collapse
Please help me
How do i do this
djnikkofb said:
you can't install apps that have been signed by a different developer, and replace with the current one. metaphor, you have a girlfriend, but your trying to get another girl who looks, and smells like your current girl, but her name is different. Since your in a beta OS, you can definitely expect bugs.
have you tried Factory data reset? there may be residual files from previous OS.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Android version of my phone is not beta
Android 7
samsung experience 8.1
version G955fxxuaqi7
djnikkofb said:
you can't install apps that have been signed by a different developer, and replace with the current one. metaphor, you have a girlfriend, but your trying to get another girl who looks, and smells like your current girl, but her name is different. Since your in a beta OS, you can definitely expect bugs.
have you tried Factory data reset? there may be residual files from previous OS.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
when me phone factory reset all program is install
but 2 week after not installed version Higher version
mojirezaie198888 said:
Please help me
How do i do this
Click to expand...
Click to collapse
Go to settings-lock screen and security-and scroll till you see secure start up. If it's on disable it. Restart your phone and try to install again.
eddyo1993 said:
Go to settings-lock screen and security-and scroll till you see secure start up. If it's on disable it. Restart your phone and try to install again.
Click to expand...
Click to collapse
security is disable but app not installed
mojirezaie198888 said:
security is disable but app not installed
Click to expand...
Click to collapse
Reboot your phone and as soon as it starts up try to install it
I'm pretty sure you just can't, the only way to do it it's through root... unfortunately
eddyo1993 said:
Reboot your phone and as soon as it starts up try to install it
Click to expand...
Click to collapse
but now not installed app
britchel said:
I'm pretty sure you just can't, the only way to do it it's through root... unfortunately
Click to expand...
Click to collapse
Are you sure you solve the problem?
Clear cache partition in recovery helped with this issue.
mojirezaie198888 said:
Are you sure you solve the problem?
Click to expand...
Click to collapse
Didn't say I was solving it... just saying facts
not resolved problem
I use ESFile Explorer to copy the new APK into the folder where the old APK is located - firstly delete the old app then replace with the new app (ensure the same name is used). Some apps are hard to find so I use BKDisabler to find the exact path of the APK I want to replace.
It worked for me as I replace the Device Maintenance App on my S8+ with a newer version off APKMirror
If still having issues, the method below may work too:
TAKE A BACKUP FIRST IN CASE IT GOES TITSUP
Download AromaFM here: https://forum.xda-developers.com/showthread.php?t=1646108&page=2 ((its a file manager that doesnt install on the phone, just runs in recovery)
Download the APK to are trying to update and put it either on an sd card or in the download folder on your phone: You will need to know where the current APK is located on your phone (usually apps are located in /data/app or /system/priv-app/ or system/app/ before going to the next step...... so for this example the APK is located in /system/priv-app/camera)
Reboot into TWRP Recovery
Install AromaFM
Go to your downloaded APK and either cut or copy it
Then navigate to the /system/priv-app/camera folder and delete the old APK then paste the new APK
Reboot
Now you should have the updated APK installed
Guys, what are you trying to solve here, he didn't even state which apk he is trying to install....
This is for the Fire HD 8 8th generation rooted with xyz's exploit
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
I've seen a couple people run into problems with this so rather than have xyz's thread clogged I figured I'd
make a seperate thread just for this.
I've made an update to the debloat.zip so it can be flashed at any time rather than flashing after rooting
[seperate zip instead of a modifed finalize.zip ]
==Debloating==
DISCLAIMER : Per testing and input from other members, Amazon Apps will NOT be able to be reinstalled after flashing this. I've yet to figure out if this is a direct result of this script or due to the nature of xyz's exploit, either way
after rooting, do NOT expect to be able to use Amazon Apps (defeat's the purpose of this script anyways lol)
1. Download debloat.zip from here
2. Reboot to TWRP, and flash
3. Reboot to system and say goodbye to Amazon Bloatware
==Replacing FireLauncher==
1. Install a launcher of your choice (Tested with CPL and Nova Launcher)
2. Install Terminal Emulator
3. Run 'su' from terminal emulator and grant it root permissions, then type 'pm disable com.amazon.firelauncher'
4. Press the home button and your new launcher is ready to go !
Thanks to xyz for the amazing work :highfive:
delessio100 said:
This is for the Fire HD 8 8th generation rooted with xyz's exploit
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
I've seen a couple people run into problems with this so rather than have xyz's thread clogged I figured I'd
make a seperate thread just for this.
I've made an update to the debloat.zip so it can be flashed at any time rather than flashing after rooting
[seperate zip instead of a modifed finalize.zip ]
==Debloating==
1. Download debloat.zip from here
2. Reboot to TWRP, and flash
3. Reboot to system and say goodbye to Amazon Bloatware
==Replacing FireLauncher==
1. Install a launcher of your choice (Tested with CPL and Nova Launcher)
2. Install Terminal Emulator
3. Run 'su' from terminal emulator and grant it root permissions, then type 'pm disable com.amazon.firelauncher'
4. Press the home button and your new launcher is ready to go !
Thanks to xyz for the amazing work :highfive:
Click to expand...
Click to collapse
Thanks for this! Will flashing this debloat.zip allow me to install and use the Amazon Prime Video or the Alexa app from the Playstore later on or will it stop the app from working?
ryknow27 said:
Thanks for this! Will flashing this debloat.zip allow me to install and use the Amazon Prime Video or the Alexa app from the Playstore later on or will it stop the app from working?
Click to expand...
Click to collapse
Per my testing, the Play Store version of Amazon Apps are working (I've tested Alexa, Prime Video, and the Kindle App so far), so yes you should be able to
delessio100 said:
Per my testing, the Play Store version of Amazon Apps are working (I've tested Alexa, Prime Video, and the Kindle App so far), so yes you should be able to
Click to expand...
Click to collapse
Awesome, thanks for the reply. I'll give it a shot.
---------- Post added at 09:49 AM ---------- Previous post was at 09:38 AM ----------
delessio100 said:
Per my testing, the Play Store version of Amazon Apps are working (I've tested Alexa, Prime Video, and the Kindle App so far), so yes you should be able to
Click to expand...
Click to collapse
Sorry, one more question. When you tested the Amazon apps, did you also previously install the finalize.zip?
ryknow27 said:
Awesome, thanks for the reply. I'll give it a shot.
---------- Post added at 09:49 AM ---------- Previous post was at 09:38 AM ----------
Sorry, one more question. When you tested the Amazon apps, did you also previously install the finalize.zip?
Click to expand...
Click to collapse
Yes, xyz's finalize.zip only removes system apps related to OTA updates, so it prevents accidental / forced OTA updates from overwriting things modified by the exploit
delessio100 said:
Yes, xyz's finalize.zip only removes system apps related to OTA updates, so it prevents accidental / forced OTA updates from overwriting things modified by the exploit
Click to expand...
Click to collapse
Thank you
delessio100 said:
Yes, xyz's finalize.zip only removes system apps related to OTA updates, so it prevents accidental / forced OTA updates from overwriting things modified by the exploit
Click to expand...
Click to collapse
I followed the instructions for Tailborn form your post on xyz's thread except for installing Root Essentials and then followed the instructions from this thread and after installing several Amazon apps, they start to open and then force close. I could be wrong but I think it may be due to the finalize.zip because after the first time I successfully rooted with xyz's method it did the same thing. Since it works for you, do you know if you did anything different than what I did?
ryknow27 said:
I followed the instructions for Tailborn form your post on xyz's thread except for installing Root Essentials and then followed the instructions from this thread and after installing several Amazon apps, they start to open and then force close. I could be wrong but I think it may be due to the finalize.zip because after the first time I successfully rooted with xyz's method it did the same thing. Since it works for you, do you know if you did anything different than what I did?
Click to expand...
Click to collapse
What apps specifically aren't working ? I've only tested the Kindle App, Alexa, and Prime Video. Are these giving you errors? I haven't fully tested all Amazon apps as I don't really use them but if you can give me a list of the apps that aren't functional I can take a look when I get home. If you'd prefer I can modify my debloat script to not remove the Amazon apps you want to keep Also if you could provide a logcat from one of the apps that's crashing I can try to determine what's causing the crash. The instructions I provided for Tailborn were just to fix the error with his SD card
delessio100 said:
What apps specifically aren't working ? I've only tested the Kindle App, Alexa, and Prime Video. Are these giving you errors? I haven't fully tested all Amazon apps as I don't really use them but if you can give me a list of the apps that aren't functional I can take a look when I get home. If you'd prefer I can modify my debloat script to not remove the Amazon apps you want to keep Also if you could provide a logcat from one of the apps that's crashing I can try to determine what's causing the crash. The instructions I provided for Tailborn were just to fix the error with his SD card
Click to expand...
Click to collapse
Yes I did see that your instructions were to help him with his SD card issue. I was basically just using it as a guide to start over except for anything to do with the SD card since I didn't have that issue.
The main apps I'm wanting to work that I'm having an issue with is Alexa and Amazon prime video. It will be a little bit before I can attach a logcat. I've never created one before but it should not be that hard to figure out and I'm on my way to work right now.
ryknow27 said:
Yes I did see that your instructions were to help him with his SD card issue. I was basically just using it as a guide to start over except for anything to do with the SD card since I didn't have that issue.
The main apps I'm wanting to work that I'm having an issue with is Alexa and Amazon prime video. It will be a little bit before I can attach a logcat. I've never created one before but it should not be that hard to figure out and I'm on my way to work right now.
Click to expand...
Click to collapse
I'm on my way home from college (on the bus ) so I can guide you through it when I get home. Alexa worked without errors for me so I'm not sure why it wouldn't work for you but I'm sure we'll get it sorted it out soon
Getting Logcat (assuming you're on windows and running command prompt on the desktop)
1. Connect the kindle to your computer, run adb logcat -c (clears logcat)
2. Run adb logcat | findstr "com.amazon.dee.app" > logcat.txt (This will store the logcat for the Alexa app to a text file on your desktop)
3. Go back to your kindle, open the Alexa App and wait for it to crash
4. After it crashes, hit CTRL + C in command prompt (stops logging)
5. Copy and paste logcat.txt and send it in your reply
This will help me figure out what's causing the crash and from here I'll be able to fix it
delessio100 said:
I'm on my way home from college (on the bus ) so I can guide you through it when I get home. Alexa worked without errors for me so I'm not sure why it wouldn't work for you but I'm sure we'll get it sorted it out soon
Click to expand...
Click to collapse
Thanks
delessio100 said:
I'm on my way home from college (on the bus ) so I can guide you through it when I get home. Alexa worked without errors for me so I'm not sure why it wouldn't work for you but I'm sure we'll get it sorted it out soon
Getting Logcat (assuming you're on windows and running command prompt on the desktop)
1. Connect the kindle to your computer, run adb logcat -c (clears logcat)
2. Run adb logcat | findstr "com.amazon.dee.app" > logcat.txt (This will store the logcat for the Alexa app to a text file on your desktop)
3. Go back to your kindle, open the Alexa App and wait for it to crash
4. After it crashes, hit CTRL + C in command prompt (stops logging)
5. Copy and paste logcat.txt and send it in your reply
This will help me figure out what's causing the crash and from here I'll be able to fix it
Click to expand...
Click to collapse
Sorry, I've been really busy here at work this evening and unfortunately, the computers here will not let me retrieve a logcat through ADB. They have them locked down to where we can't use them for much except for work stuff.
I did get a logcat from an app called "aLogcat" from the Playstore but it is really long and I don't know if it will be good enough. I can attach it here or if it is best I can get one from adb later tonight after getting home. I'm in no rush
ryknow27 said:
Sorry, I've been really busy here at work this evening and unfortunately, the computers here will not let me retrieve a logcat through ADB. They have them locked down to where we can't use them for much except for work stuff.
I did get a logcat from an app called "aLogcat" from the Playstore but it is really long and I don't know if it will be good enough. I can attach it here or if it is best I can get one from adb later tonight after getting home. I'm in no rush
Click to expand...
Click to collapse
Id prefer you get one from adb as it'll make narrowing down the problem much easier :good: but I can just use grep on my PC to filter out the other things, so if you can send over what you have and attach the logcat from adb at your leisure when you get home, I'll take a look
delessio100 said:
Id prefer you get one from adb as it'll make narrowing down the problem much easier :good: but I can just use grep on my PC to filter out the other things, so if you can send over what you have and attach the logcat from adb at your leisure when you get home, I'll take a look
Click to expand...
Click to collapse
Hopefully I attach this right...lol.
I will get it from adb later tonight. Thanks again.
ryknow27 said:
Hopefully I attach this right...lol.
I will get it from adb later tonight. Thanks again.
Click to expand...
Click to collapse
I just skimmed through it and grepped for 'com.amazon.dee.app' but nothing crash related has come up. The only crash related thing I noticed in the logcat was related to Amazon's Device Metric's app which shouldn't be affecting the Alexa App ( as i have that app removed and Alexa functioned fine in previous tests). I think a regular adb logcat is gonna be our best bet to narrow the issue down. If you haven't done this already try these suggestions
1. Clear App Data & Cache from settings and try opening it
2. Clear App Data & Cache, then from Settings grant the app all requested permissions, then try opening it
3. Uninstall the app then repeat step 2 after installing (don't open the app before granting permissions)
I have a suspicion it's related to the removal of Amazon's Account Management App (if you go to settings -> My Account , settings crashes) yet only my debloat zip removes this app, and you said you experienced this before flashing it. I'm installing the Alexa app now and I'm going to see if i can reproduce the crashes. I won't be letting Amazon get the best of us
Edit : I was able to recreate the crash by uninstalling the app, reinstalling, and then i got it to crash after signing in, however, after opening the app again it went right to the main screen and hasn't crashed since
Edit 2 : Try uninstalling, installing, signing in, and after it crashes open the app (it will crash again) then open it again (it shouldn't crash this time and should bring you to the main screen)
It seems that there's permissions included in the app that are only allowed for system priv-apps (which might be causing the crash) so if after doing this you still aren't able to get into the main screen try moving the app to /system/priv-app
delessio100 said:
I just skimmed through it and grepped for 'com.amazon.dee.app' but nothing crash related has come up. The only crash related thing I noticed in the logcat was related to Amazon's Device Metric's app which shouldn't be affecting the Alexa App ( as i have that app removed and Alexa functioned fine in previous tests). I think a regular adb logcat is gonna be our best bet to narrow the issue down. If you haven't done this already try these suggestions
1. Clear App Data & Cache from settings and try opening it
2. Clear App Data & Cache, then from Settings grant the app all requested permissions, then try opening it
3. Uninstall the app then repeat step 2 after installing (don't open the app before granting permissions)
I have a suspicion it's related to the removal of Amazon's Account Management App (if you go to settings -> My Account , settings crashes) yet only my debloat zip removes this app, and you said you experienced this before flashing it. I'm installing the Alexa app now and I'm going to see if i can reproduce the crashes. I won't be letting Amazon get the best of us
Edit : I was able to recreate the crash by uninstalling the app, reinstalling, and then i got it to crash after signing in, however, after opening the app again it went right to the main screen and hasn't crashed since
Edit 2 : Try uninstalling, installing, signing in, and after it crashes open the app (it will crash again) then open it again (it shouldn't crash this time and should bring you to the main screen)
It seems that there's permissions included in the app that are only allowed for system priv-apps (which might be causing the crash) so if after doing this you still aren't able to get into the main screen try moving the app to /system/priv-app
Click to expand...
Click to collapse
Ok well, I tried everything you listed here and it still just closes right after opening. I do not get the chance to log in or anything. Also to clarify what I said originally because it may have been a little misleading, the first time I rooted it I did not actually install the Alexa app but I did try to log into the Amazon services within the Fire Launcher and it would crash. At that point, I re-did the root and did not install the finalize.zip and it would then let me log in to Amazon services but that leaves all of the OTA stuff in there. So I tried it all again and that's when I first messaged you about it.
ryknow27 said:
Ok well, I tried everything you listed here and it still just closes right after opening. I do not get the chance to log in or anything. Also to clarify what I said originally because it may have been a little misleading, the first time I rooted it I did not actually install the Alexa app but I did try to log into the Amazon services within the Fire Launcher and it would crash. At that point, I re-did the root and did not install the finalize.zip and it would then let me log in to Amazon services but that leaves all of the OTA stuff in there. So I tried it all again and that's when I first messaged you about it.
Click to expand...
Click to collapse
At this point I'd recommend talking to xyz as it doesn't seem to be an issue with my debloat script, he's going to have a much better understanding of the issue and is more knowledgeable. I'll look at your adb logcat when you get time to grab one but I've wiped my Kindle clean reflashed everything including finalize.zip and my debloat script and I'm still able to log in and use Amazon Apps
No problem and thanks for the assistance. I'll still get the adb logcat later tonight. [emoji3]
Sent from my HTC 10 using Tapatalk
ryknow27 said:
No problem and thanks for the assistance. I'll still get the adb logcat later tonight. [emoji3]
Click to expand...
Click to collapse
I'll take a look whenever you get time to send it :good:
delessio100 said:
I'll take a look whenever you get time to send it :good:
Click to expand...
Click to collapse
Sorry it took me a day to get back to you. I didn't get time to mess with it due to some stuff going on. I tried something different this time. I followed the directions from xyz's thread except I did not install the finalize.zip. I then did everything from this thread, then I used a root explorer and deleted all of the OTA stuff from system/priv-app. Now, the Alexa app will run just fine but the Prime Video app crashes. So, I tried doing what you said a couple of times using "com.amazon.avod.thirdpartyclient" but the .txt file would always be empty. So I just used adb logcat -v long > logcat.txt to catch the crash. Hopefully you can make sense of it...lol.