


Personally, I would advise you to somehow parse the documentation and get a list of thods() and their versions, so that you know exactly what you can't pull. However, the libraries will have to be binary patched, at least I do not know the tools of the apktool level for simple reassembly. You can try to do the same with a binary. For example, if we are trying to turn to a support service for some event, we can safely replace it with a simpler call, or even throw it out altogether. To do this, it is better to try to deobfuscate the exhaust that gives us apktool, or at least identify the libraries. Knowing, where the fall occurs, we are trying to isolate this area. The application must first be installed, and it does not want to? I think it's not worth talking about unpacking via apktool. As a rule, millions of messages fall into the console about what the application is doing right now, or even entire traces, indicating the classes where the crash occurred. And to find out exactly where it falls, you can use adb logcat or logcat itself, launched directly on the device. If I have missed something, I hope that the venerable community will complement it. This is the worst (well, at least for me, within my competencies). They use some kind of system API that is not visible to the user, and in the case of using binaries collected from the NDK, we get a binary binding. They use a new fashionable API for drawing glamorous buttons that require a fresh system. There are many options, from banal chiseling in older versions, replaced by in the new versions, ending with the fact that everything was rewritten 20 times and the old servers were turned off. To begin with, let's think about what actually may not work and why:Ĭhanged the API. But here is a resource for programming, and not for commissioning. Of course, you can search for the old distr (that's why I have been storing packages since the year I bought the tablet and learned how to extract them through adb). I also want to fix the tablet driver so that I can work with a broken touchscreen, because buying a new tablet is about 100 bucks, and I I'm unemployed, I can't find a job, and this hundred bucks is a huge amount of money for me. And moreover, people are ready to spend thousands of hours of their time to realize their dreams, so as not to spend an extra penny, which simply does not exist. But in the post-Soviet countries there is no such definition (I was taught from childhood with the phrase "there is no word "I can't", there is a word "I don't want", which was just fucked up).
