[tool] odex_tool

[Notronic]

Please press thanks button when you like my work

I´d make some mods last weeks and I thought it were great to have a tool who make moding more comfortable.
So I´d wrote a little batch tool last days.

General

Version
1.0

Functions of the tool

All functions are only for system/framework files,
because system/apk files need a special bootclasspath

1.- Decompile .odex files
2.- Decompile .dex files
3.- Deodex decompiled files in .dex files
4.- Reodex deodexed .jar files

Versions

Version 1.1 is out now

Changelog:
- Implements Error Messages by incorrect reodexing...

Download

ODEX_TOOL_V1.1

Passwort: ODEX_TOOL1

Credits

:good: @ sphinx02 implements reodex function

 

[sindweller2]

Can I use this for other Android device?

 

[Notronic]

I don't test it on other devices but normally only the bootclasspath is an other. And the tool read out the bootclasspath from the connected device. So always the correct device specific bootclasspath is used

Gesendet von meinem GT-I9300 mit Tapatalk 2

 

[DakiX]

Great work buddy. Gruss

Sent from my Note 5.3" using Tapatalk

 

[Notronic]

Can anybody give a feedback to my work please?

 

[criscan]

My first impression is OK. Nice tool. Thank you for this!

Sent from my GT-I9300 using xda premium

---------- Post added at 01:06 PM ---------- Previous post was at 12:44 PM ----------

It´s not possible to get a Deodexed Framework File? (classes.dex inside a .jar file). A Classical deodexed framework?

 

[criscan]

I don' understand:
1 - If i decompiled odex file whit the option 2, how can i recompile it?

2 - I try reodex android.policy.dex file in folder 1(modded_files), whith the 2 originals(.jar & .odex) in folder 2, and there's no output in folder 3.
Some advice?

Solved - I Have to put the 2 files (jar and odex decompiled and modded) inside the folder 1. Its al OK now!

 

[Notronic]

I don' understand:
1 - If i decompiled odex file whit the option 2, how can i recompile it?

2 - I try reodex android.policy.dex file in folder 1(modded_files), whith the 2 originals(.jar & .odex) in folder 2, and there's no output in folder 3.
Some advice?

Solved - I Have to put the 2 files (jar and odex decompiled and modded) inside the folder 1. Its al OK now!

First you should deodex the decompile odex files with option 4.
The resulting .dex should be renamed into classes.dex and implements in the original .jar file.
Now the Deodexed one has finished and you can import it in your flashable zip file.

For reodexing the finished deodexed one, copy it in the directory 01. Also copy original .jar and .odex in folder 02.
Well, you can start reodexing. The result of your reodex process were turn into directory 03. You can place this
files into your flashable zip for flashing it on an odexed ROM

All right now, or more questions?

 

[criscan]

its perfect, thank you!

Sent from my GT-I9300 using xda premium

 

[core90]

Under Option 2, I get an error message:
See the screen:

http://s7.directupload.net/file/d/2968/657g7x5r_jpg.htm

 

[Notronic]

Hey, I confess that my explanation not so exactly.
To perform option two, you need the files from the /system/framework directory.
You can import this files with Option 1. After import it would work

 

[Notronic]

I´ve take your problem to make a little update to V1.1 :good:

 

[criscan]

I try on android.policy.odex making Ext Power Menu and works fine for me.
Great tool!

 

[Notronic]

Well, the tool can also handle all files in the special directories. For example, when you copy more than one files in the odex decompile folder, you can all these decompile in one step. This is a comfortable feature and economize your work

Gesendet von meinem GT-I9300 mit Tapatalk 2

 

[pglmro]

hallo notronic, congratulations for the work.
I will try to implement the call rec mod for ODEX but I did not understand the steps to do to use the tool

 

[Notronic]

First you must take the original framework folder from your device without any modded files. After that you must decompile the file you want and make your changes in the folder from decompiled one. Next you deoxex and last but not least reodex the files. In the help you can find exact informations about the individual steps

Gesendet mit der Macht der vier Kerne xD

 

[pglmro]

the file secphone.odex not decompiles
I can only android.policy.odex: (

 

[Notronic]

the file secphone.odex not decompiles
I can only android.policy.odex: (

Of course, show in post one:

All functions are only for system/framework files,
because system/apk files need a special bootclasspath

The odex file, do you want to decompile is an apk odex file. To decompile this one you have more dependencies to other .jar files, which should implement in the bootclasspath... You can change the Bootclasspath in the batch file, or you must decompile it manual with the changed path.

Gesendet mit der Macht der vier Kerne xD

 

[Notronic]

Info: the tool works on Jelly Bean too, because the bootclasspath is not include manual. The tool get always the right standard bootclasspath direct from your device over adb

Gesendet mit der Macht der vier Kerne xD

 

[eybee1970]

working like a charm on Galaxy Note official Jelly Bean XXLSZ

Great stuff, dude!