![]() There is no traceable cause because the freezing crashing is inconsistent. There is no specific action, task, or anything I do that causes freezing or crashing, it seems to happen at random, sometimes in build/buy, sometimes on the Sims Freeplay Logo screen when switching to a new area, sometimes it is when I tell a sim to do something, or I build something on the map. Sometimes this freeze crash results in a loss of save data, because of which I now back up the app_doc folder after every play because not only is the freezing crashing unpredictable, but whether my save file survives or not is also unpredictable. This freezing and crashing only occurs with The Sims Freeplay. The software has no problem running any other app or game. This only occurs while I am playing The Sims Freeplay. When it freezes, it will say in Windows "Nox App Player is not responding" and the sound sounds like a skipping CD or if it decides to crash, it is "Nox App Player has stopped working" in Windows. This would allow to use Frida for this specific app on a non-rooted device.I am having a major issue with the Nox App Player becoming completely frozen or Nox App Player crashing while I play The Sims Freeplay in Nox. There is also the possibility to modify an app by including the Frida gadget for Android into the app. There are some tools available that automate the decompiling, modification and signing like apk-mitm. Don't forget to re-sign the recompiled/repackaged app e.g. You can use apktool to decompile/recompile the app. To let the app trust user certificates you have to modify network_security_config.xml (see e.g. Note that some apps will detect that they have been modified and will refuse to work. On a non-rooted device there is only the option to modify the application before you install it onto the device. AFAIK the Frida based framework Objection has some scripts to do so. Therefore only do this on a device you use just for hacking!Īlso possible is installing and run Frida-Server on the device and hook into the app you are interested to modify the SSL/TLS certificate checking at run-time. This allows to disable certificate checking system wide - WARNING: this eliminates the security of SSL/TLS against active attacks, for all apps on the phone. If you have rooted the phone using Magisk, there is a Magisk module that seems to be able to install user certificates automatically as system certificates: Īlternatively you can install Magisk + Edxposed + TrustMeAlready Xposed module. The Mitmproxy documentation contains a how-to for manually installing the mitmproxy certificate. If your device is rooted you can try to install the Fiddler root CA certificate as system certificate. In such a case clearing the browser cache is usually removing those pinning data. Therefore even if the Fiddler root CA certificate is installed as system certificate the app won't trust this certificate as it fails on the certificate pinning.Ĭertificate pinning is also a web site feature, hence some sites save a certificate hash in the web browser cache that pins the site to a certain certificate. ![]() Note that some apps further use certificate pinning (leaf or root CA pinning). So using Chrome for testing if the proxy and the installed root CA certificate works is a bad idea, as it may only work in Chrome but not for apps. One of those rare apps that respect user CA certificates is Chrome. And unless explicitly configured in an app those user certificates are not trusted. The main problem is that if you install the Fiddler root CA certificate in Android it is marked as user certificate (not system certificate). The target API level of an app is defined it's AndroidManifest.xml file in the entry. On modern Android devices using apps developed for target API Level 24 (Android 7) or higher sniffing traffic is not that simple anymore.
0 Comments
Leave a Reply. |