Skip to content
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

Error #14

Open
blackjack4494 opened this issue May 23, 2015 · 3 comments
Open

Error #14

blackjack4494 opened this issue May 23, 2015 · 3 comments
Labels

Comments

@blackjack4494
Copy link

https://drive.google.com/open?id=0ByNGAVfceOvSbnJvbGNNazJEX3M&authuser=0

I guess it is the same error like in #10 #11 #12 #13
But i don't know if you need more "errors" to bring out a fix.

@pxb1988
Copy link
Owner

pxb1988 commented May 26, 2015

@blackjack4494
Copy link
Author

Yes the protector being used is ProGuard. I just could not efford the time to have a look into it with IDA Pro.
I can't get the apk without ProGuard since it is not my application.
I just could see how you can upgrade your app protection with those pdfs you wrote.

What do you mean exactly by getting the real dex on runtime?

@pxb1988
Copy link
Owner

pxb1988 commented May 28, 2015

as i known, proguard is a just an obfuscator, rename ids, optimize code. it does not encrypt code.

the dex is modified by a protector, the code is encrypted, and decrypt on runtime. so try get the decrypted dex (the real dex) on runtime

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants