I'm trying to install an unsigned apk file for testing purposes and i'm getting the following error.
pkg: /data/local/tmp/AL-Android.apk
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
Is there any way to bypass or disable the cert check and get it loaded so I can test?
You can download zip signer from the market and if will sign any apk or zip from your device.
I'm trying to use Zip signer, but it's teling me that it can't find the output file name I gave it (which is true becasue it doesn't exist) but when i leave both input and output file names the same, it says to change the name. What am I doign wrong?
the apk i have is in /system/app. Should I move it?
Related
Hi all,
I modifed an app so that it would run on my phone--I have a cyanogen ROM, and it doesn't play well. The app runs fine on my wife's stock G1. Anyway, I used baksmali and smali to make the necessary changes, and it recompiles fine. I also "decrypted" the AndroidManifest.xml (from binary to text), resigned the package, and I get the dreaded "file does not contain AndroidManifest.xml" error.
Apparently, the AndroidManifest.xml doesn't get built back to its binary mode during the package signing.
1. How do I get AndroidManifest.xml back into its proper binary format?
2. Is there anything else I am missing?
Thanks.
The XML files are converted during the process of building the .apk file, i.e. by "aapt". You can do this manually if you want.
http://developer.android.com/guide/developing/tools/aapt.html
derfolo said:
I also "decrypted" the AndroidManifest.xml (from binary to text)
Click to expand...
Click to collapse
By what means did you accomplish this? Did you use aapt or did you do it manually?
lbcoder,
There is a handy tool to do this called AXMLPrinter2.jar. It is available here:
http://code.google.com/p/android4me/downloads/detail?name=AXMLPrinter2.jar&can=2&q=
I am having problems using aapt to "binarize" only the AndroidManifest.xml file. I can't package the entire app, because the baksmali files are not recognizable by Eclipse as java files, and when I use smali, it is all converted back into classes.dex. Any ideas?
Just to be clear, I am doing:
Code:
./aapt package -z -u -A ./app.directory -F ./app.name.apk
An .apk file pops up with no errors, but: 1) AndroidManifest.xml is not converted to binary, and 2) the same error "does not contain AndroidManifest.xml" occurs.
Thanks for any help.
I had posted this in another forum but did not get any reply. Its a noob question so please bear with me. I wanted to know how to go about modifying an existing apk file. Below is what I am doing.
1. Copied the .apk file to my computer
2. Used apk_manager to decompile the apk
3. Made a small change in one of the xml files
4. Used apk_manager to recompile the apk and the sign it
5. Sideload it using the Sideload Wonder Machine
I am not able to sideload the app. Do I need to uninstall the existing app before sideloading its modified version? Or just giving it a new name would work? Thanks.
-mm
mm1983 said:
I had posted this in another forum but did not get any reply. Its a noob question so please bear with me. I wanted to know how to go about modifying an existing apk file. Below is what I am doing.
1. Copied the .apk file to my computer
2. Used apk_manager to decompile the apk
3. Made a small change in one of the xml files
4. Used apk_manager to recompile the apk and the sign it
5. Sideload it using the Sideload Wonder Machine
I am not able to sideload the app. Do I need to uninstall the existing app before sideloading its modified version? Or just giving it a new name would work? Thanks.
-mm
Click to expand...
Click to collapse
Try using adb instead of Sideload Wonder Machine. just CD your android sdk tools folder and type
"adb install ~path to file"
or on mac
"./adb install ~path to file"
Thanks. I tried it, below is the output:
* daemon not running. starting it now *
* daemon started successfully *
1172 KB/s (464719 bytes in 0.387s)
pkg: /data/local/tmp/GMMM.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
I guess this means I need to uninstall the existing application. The app I am trying to tweak is Gallery3D.apk. I made the change and remamed it GMMM.apk. The original app also had an .odex file which I did not touch.
I've done my searching and experimenting to try to get this to work, but I'm stuck.
I've got a font (Rockwell) that I'd like to package up into a nice .apk so I can just install it now, and have something simple to reinstall in the future should I need to.
What I've done so far is to pull a font .apk out of my phone already (Armani font, in this case), decompiled it with apktools, and then edited the following files:
/assets/fonts -> replaced fonts with rockwell.ttf files
/assets/xml -> updated xml file with appropriate filenames
/res/values ->updated strings.xml only with new app name
/res/layout & /res/drawable -> did not touch these folders
/smali/com/monotype/android/font/Armani ->replaced all references to Armani with Rockwell
/AndroidManifest.xml ->updated package name
/apktool.yml ->updated to show correct output name for apk
I then used apktools to package up the files into an .apk file, and then transfer it to my phone. When I attempt to install it, it sees the file, tries the installer, but then says "package not installed successfully" (or something similar).
My questions are:
1. Did I edit something incorrectly?
2. Did I follow the wrong steps to package up the files?
3. Is it possible that Rockwell just isn't a .ttf file that can be used?
4. Did I install the .apk wrong? (i.e. is it a system file and needs to be installed in a root environment/pushed with adb)?
Thanks in advance - I'll post any additional information that is needed.
(Oh, and I do realize this is a question - I didn't post in Q&A because everything I've seen posted font-wise has been in this section. If I'm mistaken, please move this.)
Update:
I retraced my steps through this post, and realized that I hadn't signed the file in APK Manager.
I was able to install the font file, and it's all better now.
hi all
I want to change versionName but after recompile the app don't show in the phone ,and if I don't rename it work . Why ???
android:versionName="7.9.A.0.1_sinhhoa"
to android:versionName="7.9.A.0.1"
thanks
P/S : after many tried I had found the problem apk wasn't sign properly . I always copy META-INF folder from original apk to modded apk so it won't work.
The signature is somehow linked to manifest more than to the apk itself. If you change anything in apk except manifest, you cannot install it either way, except as system app. But if you change something in manifest, you cannot install it even as system app.
You can disable signature check or resign the rom or some system apps can be signed with different signature.
I Decompile apk app and recompile it without any edit but the app is didn't install the error message : the package appears to be corrupt after Recompile
I tried
apktool + dex-tools + signapk
apk easy tool
apk editor studio
what is a problem?
i want edit mediabox launcher
how can i do it?
please help me.
this error
Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Package couldn't be installed in /data/app/com.droidlogic.mboxlauncher-1: Package com.droidlogic.mboxlauncher has no signatures that match those in shared user android.uid.system; ignoring!]
Any luck in similar situations? Anybody?
Abo Battal said:
I Decompile apk app and recompile it without any edit but the app is didn't install the error message : the package appears to be corrupt after Recompile
I tried
apktool + dex-tools + signapk
apk easy tool
apk editor studio
what is a problem?
Click to expand...
Click to collapse
The error message "the package appears to be corrupt" usually indicates that there is an issue with the APK file itself, such as missing or corrupted files, incorrect file permissions, or a problem with the signing process.
It's possible that the decompilation process may have introduced some errors or corrupted files in the APK, even if you did not make any edits to the code. When you recompiled the APK, these errors may have been carried over, resulting in the "corrupt" package.
To troubleshoot this issue, you could try the following steps:
Make sure you are using the latest version of the APK tools (apktool, dex-tools, signapk, etc.), as older versions may have bugs or limitations that could cause issues.
Check the log files generated during the decompilation and recompilation process to see if there were any errors or warnings that may have contributed to the issue.
Try recompiling the APK using a different tool or method, to see if that resolves the issue.
If none of the above steps work, you may need to examine the APK file more closely to determine the root cause of the problem. This could involve examining the file structure, checking file permissions and signatures, or even using a more advanced debugging tool such as Android Studio.