[GUIDE/TOOL] Make a new odex file (1by1_ReOdexer batch file) - Android

WHAT IS THIS, AND WHAT IS IT FOR?
This is a guide for creating a new odex file from a deodexed file, one at a time – manually, or with the tool provided. There are tools/methods for doing the entire system at once, but I have not had any luck with those. Plus, typically, one does not need the entire system re-odexed. This is more for those who want to personally mod their stock odexed systems, or create an odexed ROM maybe.
For starters, you can get away with modding a lot on an odexed system, without needing to deodex. You really only need to deodex in order to edit the smali files within the classes.dex (which is required to achieve the cooler mods). See cogeary’s great guide for deodexing tips.
-------------------------
MANUAL METHOD:
I will use the services.jar in this example. Just change the file name and path to existing .odex accordingly for other files. (thanks! to jhotmann for helping me to nail down this method)
Requirements:
odexed system
root
adb
busybox installed
dexopt-wrapper
Put this dexopt-wrapper file in /system/bin with 775 permissions:
X X X
X....X
X....X
Put the deodexed services.jar (or other jar/apk file you want to make a new odex of) on the root your /sdcard (on some phones that means internal storage).
Make sure USB Debugging is enabled.
Put your USB connection to MTP or PTP mode.
The bootclasspath is located in the /init.rc file at the root of your phone. Just make sure that all jars listed in init.rc are actually in your /system/framework folder and only include those in your bootclasspath in the command below. The one from Moto A2/Razr/other ICS is used below (minus the extra jar paths). To replace it with that of a different device, change the word bootclasspath with yours, using the path style as shown in the example below: dexopt-wrapper services.jar new.odex bootclasspath...
Connect with adb (do a adb devices check to make sure you're all good).
To create the new odex, enter the following one line at a time:
Code:
adb shell
su
cd /sdcard/
dexopt-wrapper services.jar new.odex /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework-ext.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/filterfw.jar:/system/framework/com.motorola.android.frameworks.jar:/system/framework/com.motorola.android.widget.jar:/system/framework/com.motorola.frameworks.core.addon.jar
To copy the signature from the existing odex (change path to /system/app/.. if necessary):
Code:
busybox dd if=/system/framework/services.odex of=new.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
Done! Rename new.odex (created on your /sdcard) to services.odex since that is your new signed odex file... and move to your phone using the method of your choice.
---------------------
SCRIPT METHOD (using the 1by1_ReOdexer):
I made this script to speed up the process a little bit (thanks! to jimbridgman and cogeary for their input). Note: This will not hurt your phone if you are on an odexed system and just want to play around with it…
Requirements:
Windows OS (for now – Linux coming soon)
odexed system
root
busybox installed
DOWNLOAD the 1by1_ReOdexer_v1.0.zip for Windows
Unzip it on your desktop or other convenient place (with no spaces in the file path)
Place the DEODEXED file you wish to make an odex out of on your /sdcard
Make sure you have busybox installed (in /system/bin or /xbin)
MAJOR NOTE: The script is currently set up based on the SystemUI.apk/.odex and Motorola’s ICS bootclasspath.
To change the file name/path and/or the bootclasspath, right-click on the .bat file and open with a text editor (preferably something like Notepad++) and edit accordingly for the proper path to the apk/jar and odex. The bootclasspath was taken from /init.rc minus the jars that are not in /system/framework.
Connect to PC in MTP or PTP usb mode
Make sure usb debugging is enabled
Double-click 1by1_ReOdexer.bat to begin.
Here’s a successful screenshot (look for the bytes transferred to confirm it worked):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When finished you should have a new.odex file on your /sdcard.
CHANGE LOG:
8/25/12 (v1.0)
-initial release
Thanks to the following for testing!:
-DX2Trip on the A2 ICS
-RETIEF on the RAZR Maxx ICS
-iwabashu on the RAZR ICS
(I tested it on GB - but I am not high-fiving myself )
-----------------
Some vague notes on what to do next:
Depending on what you are after by re-odexing, there are different routes. For example, if you only edited or copied smali files, then you only need the new.odex file. Meaning that all of the smali code was inside of that classes.dex of the deodexed file on your sdcard, and you just made that into a new odex file (and copied the signatures from the existing .odex in /system).
If you have a deodexed apk with more edits than just smali (you could really just copy those edits over to your existing odexed apk with 7-zip or similar), but – if you want to, you will need to remove the classes.dex from the deodexed apk, and make sure that the signatures (/META-INF folder) and AndroidManifest.xml are the same as your existing apk (check, and or copy with 7-zip or similar).
.
.
.

---

It worked! I have new.odex on the /sdcard! But it is significantly smaller than the original Mms.odex. 1.08mb compared to 1.21mb. Will there be a problem? Do I now change new.odex to Mms.odex and push it to system/app with the same permissions as the original one??

---

daveyannihilation said:
It worked! I have new.odex on the /sdcard! But it is significantly smaller than the original Mms.odex. 1.08mb compared to 1.21mb. Will there be a problem? Do I now change new.odex to Mms.odex and push it to system/app with the same permissions as the original one??
Click to expand...
Click to collapse
Thanks for trying! - I see another method also worked for you.. what was the size of the resulting odex created by that method? But, it should be no problem with the smaller size - all of my new odex files were smaller also and worked fine. I believe the process just compresses the new odex more.
And, yes, you would rename it and replace your existing with the same permissions. Good luck!
Sent from my phone's mind

---

links broken
Dude I want to do it...but your links are broken.

---

i need help
i'm trying to re-odex services.jar and i'm getting process failed error
what seems to be the problem ?

---

Thanksfor info
Thanks for this info but links do not seem to be working

---

The best tutorial for editing/creating .odex files. Thanks a lot for this!

---

Help me please
Hi, I have Huawei Phone, to be specific, here are the short spec:
Honor 4C
Android 5.1.1
ROOTED
My concern now is, I really don’t like the Stock Music Player ( V7.1.12 ) its because it does not support online music streaming and downloading, but I have an old version of it ( V6.10 ) which is it support online streaming and downloading. I really want to replace my system music app to my old version, just like before. By the way, before I update my phone to lollipop, my OS is Kitkat ( obviously ) and was able / successfully replace my stock music player to my old version, but now I can't even do it in lollipop. I tried several times to replace and update it, but it result boot problem, my phone needs to reflash OS and root again and again, Im tired of that ( honestly ). Im afraid my phone will go to trash if do it again.
I search on the google and found out about .odex file ( something like that ) I also check my stock player directory and found HwMediaCenter.odex under system/app/arm64.. so. I am wondering if someone can help me create .odex file out of my old version of music player, so that I can replace both APK and ODEX file in my system and use old version again
THANK YOU SO MUCH!
[email protected]