-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How Does classes.dex Get Updated #3
Comments
i think you tried manuel obfuscation and it is success but; 1- JADX making auto deobfuscation to final version that why you seen same original version and obfuscation apks. Try other viewers ; byte code viewer etc. 2 - Or try manuel convert dex to apk |
Thanks for this! I know what the problem was. Here goes:
So - to those who use a more recent apktool - make sure to go into obfuscators.py and update the backsmali and smali commands accordingly! |
Closing issue |
Good evening, my friends, sorry to comment on this question, but it was the only pulse that I found it, I can not in any way overshadow my apk, I did everything in the script but it did not work. They could donate me, present the script of yours that is working or fix me to solve, excuse the writing |
I have this code running - and I set my list of obfuscation tasks - and it runs. I am doing Reflection, Reordering, Renaming, and Indirection. So, some fairly sizable changes to the bytecode.
When it completes it goes, signs the jar file, and I have a new APK. But ... when I open up the APK the classes.dex file is the same size as the original. When I open and view both dex in a tool like JADX they are identical.
Am I missing something? Should not classes.dex be different? If so, why would it not update the file w/in the APK.
Very frustrating :(
The text was updated successfully, but these errors were encountered: