Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

But how to generate the binary XML file from a readable xml document? #6

Open
GoogleCodeExporter opened this issue Aug 28, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Is there a xml2Axml tool?


Original issue reported on code.google.com by [email protected] on 13 Mar 2010 at 8:11

@GoogleCodeExporter
Copy link
Author

There isn't one.
Do you want to replace the existing manifest file (AndroidManifest.xml) within 
the app, i.e. .apk file?

If yes - here's what I would try if I was you.
1. Create a project with has all the classes (activities, intent filters, 
services...) referenced in the source 
AndroidManifest file. This may be tedious for bigger apps, but might be the 
requirement to get the 
correct binary manifest file.
2. Include the binary manifest file that has been decoded into its source using 
axml2xml tool.
3. Compile this project. Fingers crossed. ;-)
4. Unzip the new binary manifest and zip it back into the original .apk file. 
If this doesn't go well with zip 
then try with pushing the newly crafted binary manifest onto the device and 
using NinjaMorph to replace 
the manifest file within the .apk

My assumption was that checksums in binary manifests do not depend on checksums 
on dex file, i.e. 
original class files, which you do not have. If that's the case, than this 
problem requires a bit more 
hacking. :-)

Original comment by [email protected] on 1 May 2010 at 10:39

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant