Download dex-1.0.tar.gz edit dex file with android

Many transforms could be used during patch development to handle code obfuscation and for other reasons. Patch development happens under the transformed view of the code, including patch writing and patch application providing transformed diagnostics. Further down the workflow pipeline, after patching and before code generation, transforms are typically reverted to preserve the original code obfuscation and other characteristics.

This is fine for development, but distributing such a development patch is awkward: it requires accompanying the patch with transform metadata in the form of complex command lines, map files, etc, in order for it to apply as designed to the targeted code. Such distribution may also reveal confidential details about the targeted code or the patch itself.

A solution to this problem is to design the workflow pipeline so that all necessary transforms can be pre-applied to release versions of the patch. Such patches can be applied to the targeted code using a standard command line and no additional metadata.

The automated tests ran during DexPatcher-tool builds used to involve a single invocation of the tool. Now the tool is invoked twice, effectively running all tests a second time as if a release patch had been generated and then applied to the untransformed targeted code. The release patch file itself is not actually generated for efficiency reasons, but operations do happen on a internal representation of it.

Finally, after independently applying the development and release patches to the targetted test code, the resulting bytecode files are compared bit-for-bit as an extra correctness verification for the system. The DexPatcher Gradle plugins have not yet been updated to support the DexPatcher tool's new command line options. However, code transforms can still be used by manually adding the required command line options to the extraArgs properties of Gradle tasks of type lanchon. Support is provided by optional identifier renaming code transforms that decode instances of identifier codes found in bytecode.

A small sample patching obfuscated code is available: see source and patch. And the result of running the patched code is here. Note: This release fixes race conditions in prior alpha releases of v1. Prior alpha releases have been retired. The official soundtrack for DexPatcher v1. DexPatcher v1. Note: DexPatcher v1. Update: The very minor changes from dexlib2 v2.

Skip to content. Star Releases Tags. About beta1 Four months have gone by with zero commits, so it is as good a time as any to release beta1. Intro After years of avoiding the ever present issue of obfuscation, with v1. It is almost irresponsible of me to move it out of alpha this early, but my motives are: I want to communicate that the architecture of the v1.

What follows should be bug fixes. Lots of them. Though I would like to, I do not think I will be able to embark on an app patching project to test this release in the field myself. By this token, testing will have to happen as users take up patching projects, and I do not want to delay future developments until feedback trickles in.

I exercised extreme caution when modifying existing code, so likely no regressions where introduced in preexisting functionality. These are: A 'hollow' code transform that would create legal but mostly empty skeleton bytecode to be fed to decompilers to create skeleton classes that DexPatcher patch writers can use as templates.

Switching to dexlib2 v2. Obfuscation support This release adds support for processing obfuscated code. Support is provided by optional code transforms that deal with identifier coding and mapping. Identifier decoding transforms Identifier decoding transforms decode instances of identifier codes found in bytecode.

Assets 3 dexpatcher Changes: Bumped dexlib2 version to 2. Improved detection and diagnostics of suspicious code changes. Removed support for the DexTag type deprecated in DexPatcher v1.

Changed the default value of the targetClass annotation element from Void. ReDex Web Site. Please provide the ad click URL, if possible:. Oh no! Some styles failed to load. Help Create Join Login. Application Development. IT Management. Project Management. Resources Blog Articles. Menu Help Create Join Login. ReDex A bytecode optimizer for Android apps. SourceForge is not affiliated with ReDex.

Add a Review. Get project updates , sponsored content from our select partners, and more. Project Management. Resources Blog Articles. Menu Help Create Join Login. Home Browse Communications Mobile dex2jar. Get project updates , sponsored content from our select partners, and more. Full Name. Phone Number. Job Title. Company Size Company Size: 1 - 25 26 - 99 - - 1, - 4, 5, - 9, 10, - 19, 20, or More.

Get notifications on updates for this project. Get the SourceForge newsletter.