Database Info

[IDEA][APP] AnyMorph

I have an idea to write a new Morphing tool that will work with any apk on your phone. (except ones moved to sd using froyo's a2sd. don't know how to get the apk from there)
Features: (Please let me know if you have better/more ideas)
1) Target apks with wildcards. (Since Froyo apks have -1, -2, -3... appended to the name.) If more than one file is found the user can choose which file to morph.
2) Backup the old apk and provide an option to restore the backup. If the morph is cancelled or fails restore the backup.
3) On-phone signing so non-system apks can be morphed too.
i.e. The old apk is uninstalled and the morphed+signed apk is installed if its a non-system app. For system apks the old apk is simply overwritten.
4) Simple property style text configuration file that maps morph folders (in the morph zip) to apks.
example: launcher-files=launcher2*.apk
5) Search /data/app for the target apk first, next search /system/app
6) Pick up keys to use from a specified sdcard folder, if not found use the standard test key.
7) Option to download a morph .zip from the web via a url (using wget).
i.e. you send a URL to your phone using chrome/*-to-phone and then paste the URL in.
8) zipalign the morphed+signed apk.
System requirements (so far):
root/su
busybox
signapk installed
wget binary for android installed.
If someone is already working on something similar, let me know. Dont want to duplicate effort. This will be an open source app though.

britoso said:
3) On-phone signing so non-system apks can be morphed too.
i.e. The old apk is uninstalled and the morphed+signed apk is installed if its a non-system app. For system apks the old apk is simply overwritten.
Click to expand...
Click to collapse
Isn't this going to break updating those apps tho? For example if I was to morph/resign angry birds, when angry birds gets a market update it's going to fail to install due to signing mismatch.

gIMpSTa said:
Isn't this going to break updating those apps tho? For example if I was to morph/resign angry birds, when angry birds gets a market update it's going to fail to install due to signing mismatch.
Click to expand...
Click to collapse
correct, but you will know when there is a market update and can uninstall the morphed version. Its the price for the morphability.

britoso said:
correct, but you will know when there is a market update and can uninstall the morphed version. Its the price for the morphability.
Click to expand...
Click to collapse
Got ya. Figured you had already thought of that but wanted to point it out just in case. I assumed uninstall/update would be the suggested course for said apps, but again just wanted to make sure you had thought of that issue!

gIMpSTa said:
Got ya. Figured you had already thought of that but wanted to point it out just in case. I assumed uninstall/update would be the suggested course for said apps, but again just wanted to make sure you had thought of that issue!
Click to expand...
Click to collapse
yeah, you could restore the backed up apk and then update, or uninstall manually and install again.

[Q] Is copying an .apk into /{system, data}/app sufficient to install an Android app?

If not, what else is done under the covers?
Also, what are the differences when installing applications
•From the android market
•sideloaded from web download
•sideloaded using adb install
•sideloaded using adb push
I copied this question from another place (I cannot put link here because I am new here) because I also have the same question and want to know more about this.

oldyoungguy said:
If not, what else is done under the covers?
Also, what are the differences when installing applications
•From the android market
•sideloaded from web download
•sideloaded using adb install
•sideloaded using adb push
I copied this question from another place (I cannot put link here because I am new here) because I also have the same question and want to know more about this.
Click to expand...
Click to collapse
Some .Apk's can be placed in system/data/app while others can't , make sure the .apk you're trying to place in system/data/app is supported or you may end up restoring your device. if the apk can run from the system /data/app then yes with the right permissions ...
Apk's from the market will give you detailed info from the apk like permission needed , supported devices ect, even the developers contact info ( in other word they are approved by Google.
while "sideloaded" apk or web apk (not coming from Google) are pirates apk,modified apk ect. who knows what permissions it needs or what info you are sharing with whoever modified the apk...
So be careful what you get into your device and where is placed on your device
Sent from my SPH-M930BST using Tapatalk 2

oldyoungguy said:
If not, what else is done under the covers?
Also, what are the differences when installing applications
•From the android market
•sideloaded from web download
•sideloaded using adb install
•sideloaded using adb push
I copied this question from another place (I cannot put link here because I am new here) because I also have the same question and want to know more about this.
Click to expand...
Click to collapse
Simply placing the apk into the correct folder is not enough. You will also need to set the permissions to the same as the other apps in that folder (I can't remember the permissions off the top of my head). This can easily be done using Root explorer, or using an adb shell and the chmod command.
Play Store installs and sideloaded installs achieve the same result, however you will want to be careful where you download apk files from. Apps from the Play Store are less likely to be malicious in nature, and , of course, you should never be pirating paid apps.
Adb push would not be enough as you would still need to set permissions. Unless you are installing a system app, it is better just to use adb install.

rootedVette said:
Adb push would not be enough as you would still need to set permissions. Unless you are installing a system app, it is better just to use adb install.
Click to expand...
Click to collapse
Are you saying the "adb push" will only copy file into the target location but "adb install" will copy the file into the target location AND also set the proper permission for you?

With all of the usual warnings about the source/safety of "side-loaded" apps aside. . .
I simply put the .apk file onto the SD card (anywhere), and then use a file manager like Astro to "open" it (root access not required). You will be prompted to see if you really wanted to install the app. Then let Android do its thing. The app will be installed where it belongs, with all the permissions it needs.
For this to work, you must first tell the device to allow installation of apps from unknown sources. Go to Settings | Security, and check Unknown Sources.

[Q] "google play services" requirement without gapps

Hi,
I run OmniRom without gapps (with NOGAPPS actually) and there's an app that refuses to start with the error "google play services is not installed, contact the device manufacturer".
Is there anything I can do to "fool" the app in thinking GSF is installed? I don't care about the push notifications the app is using.
Thank you.

wkwkwk said:
Hi,
I run OmniRom without gapps (with NOGAPPS actually) and there's an app that refuses to start with the error "google play services is not installed, contact the device manufacturer".
Is there anything I can do to "fool" the app in thinking GSF is installed? I don't care about the push notifications the app is using.
Thank you.
Click to expand...
Click to collapse
What is this problematic app?

thenookieforlife3 said:
What is this problematic app?
Click to expand...
Click to collapse
Hello. Thanks for your reply. It's:
https://play.google.com/store/apps/details?id=nz.co.asb.asbmobile
I tried using apktool to decompress it, remove the dependencies from AndroidManifest.xml but I couldn't compile it back.
Thoughts?
Thank you

wkwkwk said:
Hello. Thanks for your reply. It's:
https://play.google.com/store/apps/details?id=nz.co.asb.asbmobile
I tried using apktool to decompress it, remove the dependencies from AndroidManifest.xml but I couldn't compile it back.
Thoughts?
Thank you
Click to expand...
Click to collapse
The hard thing about decompressing, editing, and recompiling apps is that when you recompile it you also have to resign it. See, when you take apart an app the signature is stripped, and the signature is what allows the app to install properly.
Fortunately, there are several utilities out there that will help you do this.

thenookieforlife3 said:
The hard thing about decompressing, editing, and recompiling apps is that when you recompile it you also have to resign it. See, when you take apart an app the signature is stripped, and the signature is what allows the app to install properly.
Fortunately, there are several utilities out there that will help you do this.
Click to expand...
Click to collapse
The problem wasn't the signing part, I wasn't reaching that step since the apk wasn't building anymore afterwards, it was giving out errors about not finding some files (I don't recall exactly as I haven't tried lately).
Would you recommend a particular app (ideally to run under linux but can manage with Windows if need be) to decompile and compile an apk?
Thank you

wkwkwk said:
The problem wasn't the signing part, I wasn't reaching that step since the apk wasn't building anymore afterwards, it was giving out errors about not finding some files (I don't recall exactly as I haven't tried lately).
Would you recommend a particular app (ideally to run under linux but can manage with Windows if need be) to decompile and compile an apk?
Thank you
Click to expand...
Click to collapse
What I meant to say was, don't actually decompile the app and then try to recompile it! It will give you errors, as you've seen.
Instead, try the following steps:
1. Copy the .apk file to a safe, secure place as a backup.
2. Download and/or open up an archive management program, i.e. 7zip or WinRAR.
3. Navigate to the directory where the .apk you want to mod is located. Not the backup one, of course!
4. Extract the .apk to a folder of your choice. Folder name example - "[name_of_app] modding" (without quotes).
5. Open up your regular file manager and navigate to that folder you just extracted to. Modify the files you want to modify.
6. Now, pay close attention to this part - In your archive manager, go into the acual .apk file you want to modify. It will just open right up as if it was a .zip.
7. Navigate to the directory in the .apk where the files you modded belong.
8. Now, back to your file explorer, click-and-drag the file(s) you modified from the file explorer window to the archive manager window. Drop the file in the archive manager window. It will ask you if you're sure that you want to overwrite, hit "Yes".
9. Once the file's in place, close the archive manager to finalize the change.
10. Now, all you have to do is put the modified app back on your device, use a tool like ZipSigner (find on Google Play) to resign it, and install!
Please do give me a few post thanks if the above instructions helped you. :good:

thenookieforlife3 said:
What I meant to say was, don't actually decompile the app and then try to recompile it! It will give you errors, as you've seen.
Click to expand...
Click to collapse
Thanks for the detailed instructions, however, to modify AndroidManifest.xml (where the GSF requirement is put) you need to decompile the apk using apktool or similar.
Simply unzipping the APK will not allow you to change AndroidManifest.xml.
I wish it were that simple

wkwkwk said:
Thanks for the detailed instructions, however, to modify AndroidManifest.xml (where the GSF requirement is put) you need to decompile the apk using apktool or similar.
Simply unzipping the APK will not allow you to change AndroidManifest.xml.
I wish it were that simple
Click to expand...
Click to collapse
That's odd, because that method is what has consistently worked for me!

APK compatibility

Hi guys. Im trying to install mobile NFC payment app of my bank. As Im rooted, I can not see it in device play store. I managed to download a copy using friends non rotted phone and install it manually. Unofortunately that did not work, it just said "App not installed". Then I learned, that AndroidManifest.xml file from decompiled apk can tell me what are the compatibility restrictions of the app to change build.prop accordingly. However, looking at AndroidManifest.xml did not give me any clue what should cause an issue. Could anyone who is more skilled in this topic tell me what are the restrictions from attached decompiled file? Thanks.

How to manually, I said manually, install an APK

I have an APK that will not install. Just will not. "Package conflicts with another package with the same name", it says. The truth is that the package DOES NOT conflict with any package of the same name, but the system believes it does. So I need help. I've tried to troubleshoot this various ways, looking for any traces of old installations, but so far, I haven't been able to remove anything that makes a difference.
So listen, here's what I want to know. How do I manually install an apk? And when I say manually, I MEAN MANUALLY. I find all kinds of search results that claim to tell me how to manually install an APK, BUT THEY'RE LYING. They just tell me how to install an APK that I have downloaded using the existing system installer, WHICH DOESN'T HELP ME. Sorry, but I'm frustrated with all the guides that claim they're going to tell me what I need but don't deliver.
Manually. I mean manually. I want to put the APK into a folder in data/app, create any other folders that are needed, add the application info into whatever files Android has that tell it what is installed, do whatever else is necessary. I want to do a fully manual installation. No using the system installer. No using any root installers. Putting all the files where they go and making all the changes MANUALLY.
Can anyone please tell me how to do this?

Can you install the app via adb? adb install appname.apk? Sorry, I don't know how to install one manually. I understand what you're asking for but I don't know the answer.

I'd like to give the update that I did finally manage to install the app. I'm pretty sure what finally got me there was deleting its information from /data/system/packages.xml and rebooting. But I'd still like an answer to this question for the future. Failing that, though, if need arises, I would be inclined to take the steps in this guide, https://android.stackexchange.com/questions/200974/how-to-manually-remove-an-app, and follow them in reverse.

"Package conflicts with another package with the same name".
In fact, what identifies an app is its package id. So it means that they have a same package id.
For example, the package id for Instagram is 'com.instagram.android'.

FailSafeNow said:
I want to put the APK into a folder in data/app, create any other folders that are needed, add the application info into whatever files Android has that tell it what is installed, do whatever else is necessary. I want to do a fully manual installation. No using the system installer. No using any root installers. Putting all the files where they go and making all the changes MANUALLY.
Click to expand...
Click to collapse
I need a way to install an app manually without using package installer, by putting the apk and any related files in the correct places, anyone know how to do this? i have a rooted phone, I'm just not sure which files need to be edited so the phone "knows" the app is installed. Please help! Thanks!