Checksum mismatch

[Dhina17]

I ain't sure how to use this app. I checked the source and tried it like I understood.

I made an sample apk (just shows a text view) and installed in my device.

Then I modified the app source to show some other text. Compiled and pushed to my device storage.

I tried to patch the installed (old app) (target) with the new apk file (input) using the odex patcher app.

I checked the log. I have seen 'dex checksum mismatch. Expected: some value. Actual: some value'.

Is it the right way to use the app?

Does this app replacing the old dex with the new dex ref in the oat/vdex file? Or is it working in some other way?

[giacomoferretti]

Hello, sorry for the late response.

I am aware of the poor documentation, as soon as I rewrite the patching logic I will also create a small example of use. I would have some ready but have not committed them yet.

Can you share with me:

• Device used
• Android version
• Odex Patcher version
• Original APK
• Patched APK

[Dhina17]

I figured out the issue. It's happening in the multidex apk. While patching the checksum in the oat, we have to ensure that we are patching checksums in the classes{N}.dex in the right order. (ascending). I assumed you don't accept patches since you are rewriting that's why didn't make a PR.

[giacomoferretti]

Oh, nice discovery. I thought I had already fixed that. Nevermind.

I accept pull requests because I can't keep up with it as much as I would like to these days, so if you can fix this problem I would be glad, at least it won't happen to other users. Thank you!

[Dhina17]

Sure will do.

[Dhina17]

Fixed in #14