I quickly learned how to spot what jar was needed in the error message. I then ran into a problem where
that did not work so well. Then I discovered that you can disassemble the framework jars and find which
one has that class by entering in baksmali.jar core.odex instead of baksmali.jar -x core.odex
It took a lot of time to disassemble each and every jar until finding the right one. So I made a batch
script to do all the work for me. This combined with a folder search of the output files made finding those
dependencies much easier.
For those of you who wish to use this tool also here it is
For use with Windows
How to use this tool
- Unzip to desktop (or any folder you wish)
- Place your apps and odex files into the app folder
- Place your jars and odex files into the framework folder
- Start tool by clicking on main.bat
- Select option 1 to disassemble your apps
- Select option 2 to disassemble your framwork
- Option 3 to quit
- Two new folders have been created to store your disassembled files (disassembled_APK and disassembled_FrameWork)
- Use your favorite folder search to find that dependency you are looking for
