Deodexing Android can be a time-consuming process which involves pulling /system files from your Android device, deodexing them using PC tools, and installing them back on your phone. Not to mention that whenever Google releases a new Android version, the process for deodexing ROMs alters – which means tools for deodexing need to play catchup. Many deodexing tools have become defunct due to lack of update from the developers.
A new tool called TOAD (The Open Source Android Deodexer) has been released, which aims to not only be incredibly easy, its open-source nature allows the development community to keep it updated with the latest deodexing methods. TOAD utilizes batch files for processing odexed files, so new batch files can easily be added or modified by the development community.
In this guide, we will show you how to deodex Android files using TOAD – and if you’re development-savvy, maybe you’ll join the TOAD community in keeping it updated for the latest Android updates.
TOAD comes in a self-extracting EXE file, so you can just place it on your C:\ (to minimize any potential issues).
After launching the .EXE, you’ll have a folder structure which contains the following folders:
- Method_files: Contains all the batch files which TOAD will use for deodexing.
- Tool_Files: Files that TOAD needs for its operations.
- Your_Files: This is where your files will go.
How to Deodex in TOAD
- So to begin using TOAD, you need to copy your “build.prop” file and entire “framework” folder from your Android device into the Your_Files folder of TOAD.
- You can copy anything else you’d like deodexed as well, for example the folders “app”, “priv-app”, “vendor app”, “vendor priv-app”, “vendor framework”, etc.
- Now you need to run TOAD. It will ask if you want to deodex the entire framework folder, the choice is yours. However, for any Android version higher than KitKat, you absolutely need an odexed framework folder.
- TOAD will read your build.prop file to determine your Android version – it discovers the API used in your ROM. Every Android version has its own unique API (build numbers). You can see a full list of official Android APIs here.
- So for every Android API that TOAD can handle, TOAD has its own Method file. Hence why Method_Files is full of them. So if TOAD finds a matching Method_File for your Android API, it will ask if you would like everything in Your_Files deodexed.
- If you choose ‘Yes’, TOAD will begin its process, at which point you just need to relax and wait. TOAD will go through its operation according to the method in the appropriate Methods file. If TOAD cannot deodex a file, it will display a note of the error and continue the operation.
- When TOAD is finished deodexing, it will put together a ZIP file of all the deodexed files.
- Now you just need to flash this .ZIP file in your recovery, and all the files that were deodexed will now be on your phone.