Search Results

Are you sure it really was one of your relatives sending this mail -- and not just a spammer using their address as sender (as the URL suggests)? I would for sure NOT install that, to me it looks like …

You'd need to check two things: whether the package names are identical see: Read the package name of an Android APK on our sister-site. … Again, see on our sister site: How to view the identity of person who signed the apk on Android device? // Getting certificate details from an apk. …

So most probably, the .apk you try to install manually has been tampered with. If it wasn't you doing so, I would refrain from using it. … - or you know the source to be trustworthy (e.g. the developer of the app provided you with an unsigned testing version), you have to first uninstall the original app before installing the "tainted" .apk …

Besides (and the last item implicitly mentions this), developers provide means to check the validity of their .apk files: they sign them with their certificates. … I definitely and strongly discourage using .apk files you found "somewhere in the wild" unless you know exactly what you do (i.e. either you can trust the source, or know how to check the .apk for yourself …

The way to do that is described here, and basically involves the following steps: unpack the .apk file. …

Here's what you need: the .apk in question the .apk of the same app in the same version from Playstore openssl Unzip both .apk (each into its own directory), and compare their certificates (stored … Unless the dev's key got compromised, that should mean the potentially sideloaded APK should be fine (no guarantees the dev himself didn't play games – but if size and MD5 of the APK also match, I'd say …

There are plenty of app-based solutions available specialized on this (also some file managers like Amaze mentioned in Robert's comment on your question cover this as well) – or you could simply use a …

Best choice for this is IMHO AppMonster, which backs up your *.apk files to sdcard. … To sum up: AppMonster would solve your problem with getting the *.apk files to the sdcard for transfer -- and even offer you features you surely will use even after completing that job. …

You can configure the app to keep all .apk files, or only the latest N (number freely configurable), even pinning of a "stable version" to always keep is possible. … AppMonster only takes care for the .apk files (not for app data). …

This app automatically captures each .apk installed and stores it on your SDCard (initially, you can do this also manually for all your installed apps). … But it (currently) only backups the apps (.apk) itself, not their data. …

You can e.g. use Raccoon for that – a phantastic Java app I'm using: Raccoon (source: Tutonaut; click image for larger variant) The app requires credentials of a Google account (you can either use …

INSTALL_FAILED_UPDATE_INCOMPATIBLE should tell you something. "app is already provided in stock Rom", "not rooted" and "I uninstalled it" don't match: w/o root, you cannot have uninstalled a system ap …

It's the way supposed to work: adb backup -f myapp.ab -apk com.myapp # backup on one device adb restore myapp.ab # restore to the same or any other device But an app can "opt out of …

If one wants to grab the .apk for distribution, that's easily possible using apps like AppMonster, which can back up the .apk file to SD card. … To sum up: At least for free apps, I'd even recommend to keep a direct download link to the .apk available, if possible. …

Mentioned for completeness: APK Multi Tool. …