As far as I understood it patches odex files in dalvik cache and does not touch the original apk. If you installed some apk to your system, dalvik extracts your classes.dex file from apk, optimizes it for this phone and android version and puts odex file into dalvik cache. After that your app starts using this optimized odex file not the classes.dex from apk. Patcher changes odex file in the cache and leaves untouched your apk, so checking apk for consistent gives you nothing. As far as I know (correct me if I'm wrong) you can't access dalvik cache file from within your app, you need root access to do it.
On Wednesday, October 10, 2012 6:23:40 AM UTC+4, Gabriel Simões wrote: > > Hello, > > It has been sometime now since this app was first saw in town but I still > can´t find much about how it bypasses some key java resource protections. > LVL patching has been there for quite sometime and isn´t the problem here > at all: receiving wrong validation information from dalvik seems to be the > issue, which no code based on those can help. > > While I really don´t expect to find a magic formula to fight this (and > keep the dogfight between developers and crackers), I´d like to know if > anyone has found/figured out information on how it works so we can start > thinking about fighting back strategies. > Any news to be shared? > > Thanks, > Gabriel Simões > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
