With the app DicePlayer I want to stay at version 2.0.53, because from 2.0.54 on AC3 support was removed.
To not accidently update to a version >2.0.53 (e.g. by hitting Update All) I've used the function Detach from Market that is offered by Titanium Backup.
Unfortunately this detachment is being resetted on every reboot of the phone (Nexus 5 with 4.4.4).
Is there a way to permamently detach an app from Android Market?
Sharky444 said:
With the app DicePlayer I want to stay at version 2.0.53, because from 2.0.54 on AC3 support was removed.
To not accidently update to a version >2.0.53 (e.g. by hitting Update All) I've used the function Detach from Market that is offered by Titanium Backup.
Unfortunately this detachment is being resetted on every reboot of the phone (Nexus 5 with 4.4.4).
Is there a way to permamently detach an app from Android Market?
Click to expand...
Click to collapse
Hi, I realise this is an old post but it's something I've been trying to do for a while too. I've finally accomplished it successfully so I thought I'd share it on in some of the topics.
It works by changing the apk signature so the app typically becomes 'different' to the one on the Google Play Store and therefore doesn't appear in your Google Play Store list. But by doing this, you won't be able to update the app from Play Store.
How to:
Need Root.
First do a TB backup of current apk just to keep it.
With a file explorer, go to root\data\app and copy the app apk that you want to change and paste it somewhere on SD card.
Now uninstall the app
Download and install: ZipSigner by Ken Ellinwood from Play Store.
Open ZipSigner, choose input file and navigate to earlier copied apk
I used key/mode: auto-testkey
Sign the file
The new signed apk will be put in the same directory the original file was.
Now install that signed apk and your're done. Check market.
Worked for me - hope it works for you!
Thanks. Unfortunately, doesn't work with Barclays UK app. Has this worked with this app for anyone? thnx
Related
I looked EVERYWHERE for a solution to this problem and finally figured it out on my own, so I thought I'd share and hopefully have this thread show up on a Google search for everyone else who has been pulling their hair out. Every other so called "solution" (fixing the time, clearing the cache, reverting back to the old Android Market, etc) has NOT worked at least for my phone, which is the HTC Desire Z, (AKA HTC Vision) with Android 2.2 (Froyo) installed.
I'm talking about getting a "No Connection" error when attempting to download an app from the play store. This error happened ever since they updated from version 3.9.17 to 3.10.9 and beyond. Uninstalling the updates for play store reverts you back to the old Android Market, which works, but which is, quite simply, unacceptable. The problem is when you download and reinstall play store 3.9.17, (or any other for that matter), after a couple of minutes it automatically updates to the newest play store version, which just brings us back to square one! So the solution here is to trick the phone into NOT auto updating the play store app.
Sorry, non rooted users, but you need root for this. You also need to have terminal emulator and a root file explorer such as ES File Explorer. (Of course, in order to download these things from Google Play, you'll have to uninstall the updates to Google Play via the app manager and use the old Android Market).
1) Download Google Play Store version 3.9.17
androidpolice.com/2012/11/02/download-latest-google-play-store-3-9-17/
If you want to try installing later versions just to see if a later version might work for your particular phone, here's a list:
androidpolice.com/tags/series_google_play_store_download/
Put whichever version you downloaded into your phone somewhere, I put it on the SD card.
2) Uninstall all the updates to your current Google Play via the app manager if you haven't done so already.
3) In ES File explorer, go into /data/app
4) Create a new file called "com.android.vending-2.apk"
5) In Terminal emulator, type su and hit enter to get superuser permission.
6) Type "cd /data/app" and hit enter.
7) Type "chattr +i com.android.vending-2.apk" and hit enter.
8) Go back to ES File explorer and browse to the Google Play apk that you downloaded. Click it and install it.
That's it! You should now have an older version of Google Play installed that does NOT automatically update. Like I said, for my phone, the newest version that works is 3.9.17.
mudesi said:
I looked EVERYWHERE for a solution to this problem and finally figured it out on my own, so I thought I'd share and hopefully have this thread show up on a Google search for everyone else who has been pulling their hair out. Every other so called "solution" (fixing the time, clearing the cache, reverting back to the old Android Market, etc) has NOT worked at least for my phone, which is the HTC Desire Z, (AKA HTC Vision) with Android 2.2 (Froyo) installed.
I'm talking about getting a "No Connection" error when attempting to download an app from the play store. This error happened ever since they updated from version 3.9.17 to 3.10.9 and beyond. Uninstalling the updates for play store reverts you back to the old Android Market, which works, but which is, quite simply, unacceptable. The problem is when you download and reinstall play store 3.9.17, (or any other for that matter), after a couple of minutes it automatically updates to the newest play store version, which just brings us back to square one! So the solution here is to trick the phone into NOT auto updating the play store app.
Sorry, non rooted users, but you need root for this. You also need to have terminal emulator and a root file explorer such as ES File Explorer. (Of course, in order to download these things from Google Play, you'll have to uninstall the updates to Google Play via the app manager and use the old Android Market).
1) Download Google Play Store version 3.9.17
androidpolice.com/2012/11/02/download-latest-google-play-store-3-9-17/
If you want to try installing later versions just to see if a later version might work for your particular phone, here's a list:
androidpolice.com/tags/series_google_play_store_download/
Put whichever version you downloaded into your phone somewhere, I put it on the SD card.
2) Uninstall all the updates to your current Google Play via the app manager if you haven't done so already.
3) In ES File explorer, go into /data/app
4) Create a new file called "com.android.vending-2.apk"
5) In Terminal emulator, type su and hit enter to get superuser permission.
6) Type "cd /data/app" and hit enter.
7) Type "chattr +i com.android.vending-2.apk" and hit enter.
8) Go back to ES File explorer and browse to the Google Play apk that you downloaded. Click it and install it.
That's it! You should now have an older version of Google Play installed that does NOT automatically update. Like I said, for my phone, the newest version that works is 3.9.17.
Click to expand...
Click to collapse
Sorry but this did not work for me.
Device: Samsung SCH-i509
Android Ver: 2.3.6
Rooeted: Yes
Internal Memory: 160MB
Ext memory: 2GB microSD partitioned as: 1st Partition: 1455MB FAT, Second Partition: 515 EXT2 (I am using Link2SD for linking apps to SD card)
Superuser App: SuperSU
Rom Management: RomToolBox lite
I rooted my phone about a fortnight ago, first time rooting, things went fine, and apps were responsive.
2 days back I not only uninstalled the Google Play Store updates but also uninstalled the app, hoping I would install the latest google store APK from Android Police ( Ver: com.android.vending-4.8.22.apk )
I am new to rooting and installing apks, so after installing the above mentioned Google Play Store apk to the SD card and finding it was not responsive (I was getting a blank screen and an error message shortly thereafter which disappeared instantaneously for me to note what it said). I googled and found on a forum, (sorry don't recall which one) that the APK needs to be copied to the system/app folder and any previous apk of Google Play Store needs to be replaced. So using Root Browser in ROMToolBox I copied the apk to system/app.
Doing so did open the 'first run' of Google Play Store, as in I was prompted to allow permission via google account and opened the interface with my apps etc normally. But trouble started when I tried to update the apps. The moment I do that, I get the downloading bar AND then I get the force close screen. The same would happen in the case if I try to download any apps.
I froze the Google Play Store app through ROMToolBox App Manager.
On doing a search on XDA forums before I posted here I came across: http://forum.xda-developers.com/showthread.php?t=2129881
And did as suggested in this thread: went to the system/app folder through Root Browser and set permission to rw-r--r-- as suggested there.
UNFORTUNATELY things are the same as before: once the app fires up either by clicking on a Google Play Store linked ad or by just opening it, I am back to force close screen.
I would be really thankful if someone could help me out on this.
Also, I am not quite sure how much it makes a difference I was using Link2SD to link all user apps to SD card (I uninstalled this app as well hoping to install the latest version)
You rebooted after changing the apk permissions, right? Also perhaps try force stopping the plays store, wiping the app data then reboot.
Thanks
jr67 said:
You rebooted after changing the apk permissions, right? Also perhaps try force stopping the plays store, wiping the app data then reboot.
Click to expand...
Click to collapse
Thanks for the reply. I had rebooted and clear app data but the app was still unresponsive/
The issue resolved when I downloaded an older version of the Google Play Store app and installed it in the sys/app folder after removing the previous one, reconfigured the permissions and rebooted. things are working fine now.
Cheers, have a great weekend!
I found this "-505" error prevalent on two of my MediaTek MT6735 MKU82ZPZ/A devices, it's probably common with China Phones, which install a certain list of stock Google apps, the QuickSearch Box not being included.
I have found a solution for this, based on my issues with blocking forced updates with Google Play services and the Google Play Store:
http://forum.xda-developers.com/showthread.php?t=3091832
I figured since these two added folders in the system / data / app folder prevented Google Play services from updating:
system/data/app/com.google.android.gms-1.apk/
and
system/data/app/com.google.android.gms-2.apk/
And that adding the specific folder for the Play Store also prevents Play Store from unwanted updates, then I should be able to actually Force an app to install as if it were a stock app (but it will not really be installed as a system app, it will still be "user").
I chose, not the latest beta for the Google Search app, but one from a couple of days ago:
http://www.apkmirror.com/apk/google...gle-app-6-0-17-21-arm64-android-apk-download/
So that would be Google search v6.0.17.
Next, I renamed the APK file into the format that I used to block the Google play services update, and then I created a path in the proper system folder:
/data/app/com.google.android.googlequicksearchbox-1/
In this case, there was no need to add the dot-APK extension to the folder.
What's next? Okay basically you take the APK file that you had named "com.google.android.googlequicksearchbox-1" and then you place it in that folder.
After you have moved it in there, you're just going to have to rename it to "base.APK".
And then using the app "FX", install it using "root package installer". Basically, just tap the APK file and you'll see a popup, just choose "root package installer" and then install it. Then reboot your device and you will have Google search on your springboard or in your appdrawer when it comes back up.
Needless to say, you have to be rooted in order to do this. It works best with the "FX" explorer app as it allows installing an The APK as a root package, which allows it to be installed. Because if you try to install it manually, it just fails.
This is for specific Lollipop 5.1 MediaTek MT6735 systems, maybe some other systems do it too, whenever you come across the "-505 error" - I don't know if this error is specific for this particular package or if will occur with other Google apps.
Whatever happens, if this succeeds in installing quicksearch for you, leave the base.APK file in that folder otherwise the app will stop working.
Oh yes, I dictated all of this into my MTK device using the regular stock keyboard with its new dictation button provided by Google search.
Hello guys
I'll explain here how to stop Google Play Store/Services from updating itself as the self update function draining the battery, using the data plan and reducing the free storage space.
There is a similar method but unfortunately that method doesn't work on android 5.1.1.
Instructions:
1. Uninstall all of the installed Google Play Store/Services updates through app info.
3. Install root file manager.
2. Navigate to /data/app.
3. Create 2 empty files.
4. Rename those files to "com.google.android.gms-1" and other one to "com.android.vending-1" (their permissions would be 0600)
That's it updates are gone
Hit thanks if I helped
Work on Android 7.1.1 ?
Hello, work this trick on Android Nougat ?
Thx
If you do that you can't sign in with Google so you need to sign in first but it works so far.
eyal7 said:
Hello guys
I'll explain here how to stop Google Play Store/Services from updating itself as the self update function draining the battery, using the data plan and reducing the free storage space.
There is a similar method but unfortunately that method doesn't work on android 5.1.1.
Instructions:
1. Uninstall all of the installed Google Play Store/Services updates through app info.
3. Install root file manager.
2. Navigate to /data/app.
3. Create 2 empty files.
4. Rename those files to "com.google.android.gms-1" and other one to "com.android.vending-1" (their permissions would be 0600)
That's it updates are gone
Hit thanks if I helped
Click to expand...
Click to collapse
It's only a temporary fix as the Play Store automatically updated today and I had to uninstall the update.
I recently upgraded from an Android 7 phone (Moto G5) to an Android 9 phone (Moto G7). I like to back up all of my apps that I plan on using in the future, using a backup app like ML Manager, and installing them locally with a file browser, like FX. On my new phone, there are some APK backups that I can't install from a file browser; even if I actually download them though the Google Play Store, back them up, uninstall them, and then try to install that backup on the same phone, it won't work. Not every app does this, and at first, I thought it was only paid apps that were giving me problems, so I chalked it up to DRM, but a bunch of free apps won't work, either.
I've tried alternate methods of installation, too, like using a terminal emulator (see the screenshot, using the app Manual Camera as an example), and ADB on a PC, which results in an INSTALL_FAILED_VERIFICATION_FAILURE error. I've searched for this error and followed directions, like disabling Play Protect (which I never enabled on this phone, anyway), but nothing works. Is this just how Android is now? Did something change so that it's harder to install backups? I tried all of this on my wife's phone, too, which also runs Android 9, and I got the same errors. Any help would be appreciated, because I'm out of ideas. Thanks in advance!
pedrovay2003 said:
I recently upgraded from an Android 7 phone (Moto G5) to an Android 9 phone (Moto G7). I like to back up all of my apps that I plan on using in the future, using a backup app like ML Manager, and installing them locally with a file browser, like FX. On my new phone, there are some APK backups that I can't install from a file browser; even if I actually download them though the Google Play Store, back them up, uninstall them, and then try to install that backup on the same phone, it won't work. Not every app does this, and at first, I thought it was only paid apps that were giving me problems, so I chalked it up to DRM, but a bunch of free apps won't work, either.
I've tried alternate methods of installation, too, like using a terminal emulator (see the screenshot, using the app Manual Camera as an example), and ADB on a PC, which results in an INSTALL_FAILED_VERIFICATION_FAILURE error. I've searched for this error and followed directions, like disabling Play Protect (which I never enabled on this phone, anyway), but nothing works. Is this just how Android is now? Did something change so that it's harder to install backups? I tried all of this on my wife's phone, too, which also runs Android 9, and I got the same errors. Any help would be appreciated, because I'm out of ideas. Thanks in advance!
Click to expand...
Click to collapse
Some apps are different for noghat and pie Android
So there is no grantee that you can install all APK that you backed up on noghat for pie
Download them from Google
It should completely work
Make sure that you have free space on internal storage and when you wanna download them make sure that download arm/arm64 version
amirizad_7436 said:
Some apps are different for noghat and pie Android
So there is no grantee that you can install all APK that you backed up on noghat for pie
Download them from Google
It should completely work
Make sure that you have free space on internal storage and when you wanna download them make sure that download arm/arm64 version
Click to expand...
Click to collapse
Yeah, downloading from the Play Store definitely works, I'm just curious as to why backing up an app downloaded from the Play Store won't install from the APK *on the exact same device.* I'm a stickler for keeping local backups of everything, but I'm more curious than anything at this point.
pedrovay2003 said:
Yeah, downloading from the Play Store definitely works, I'm just curious as to why backing up an app downloaded from the Play Store won't install from the APK *on the exact same device.* I'm a stickler for keeping local backups of everything, but I'm more curious than anything at this point.
Click to expand...
Click to collapse
Well there is a another reason
That is some app install with APK
And other one install with APKS
which you should install them with SAI and have two or three file to install (even more)
And when you backup from apks apps it doesn't backup all files to install it again
But at play store it install automatically
amirizad_7436 said:
Well there is a another reason
That is some app install with APK
And other one install with APKS
which you should install them with SAI and have two or three file to install (even more)
And when you backup from apks apps it doesn't backup all files to install it again
But at play store it install automatically
Click to expand...
Click to collapse
Holy crap, dude, I had NO idea that split APKs were a thing. I downloaded Split APK Installer from the Play Store, and I can make and restore local backups again. Thank you so much for the info, it was exactly what I needed!
pedrovay2003 said:
Holy crap, dude, I had NO idea that split APKs were a thing. I downloaded Split APK Installer from the Play Store, and I can make and restore local backups again. Thank you so much for the info, it was exactly what I needed!
Click to expand...
Click to collapse
Happy that it helped