Open SyauqiMA opened 1 month ago
Same here. When disabling root, frida failed to run with error "unable to save selinux policy to the kernel permission denied"
Same here, using BlueStacks though. To workaround it I tried to trick the game: Copied the su command to /data/local/tmp/sx and disabled root access on emulator since that seemed to be first thing that was triggering the error. The new sx allowed me to use adb shell and start frida-server as root. Game was on title screen for few minutes without detection. Error showed again when I tried to launch game with ba.js
Update: I decided to just ditch the frida method entirely and use the mitmproxy method for redirecting server, and now it works (almost perfectly). My problem now is the club commands (for adding characters etc.) doesn't work, will open a new issue for this!
Update: I decided to just ditch the frida method entirely and use the mitmproxy method for redirecting server, and now it works (almost perfectly). My problem now is the club commands (for adding characters etc.) doesn't work, will open a new issue for this!
do you download the blue archive from play store? mine has a problem while connecting with mitmproxy
Update: I decided to just ditch the frida method entirely and use the mitmproxy method for redirecting server, and now it works (almost perfectly). My problem now is the club commands (for adding characters etc.) doesn't work, will open a new issue for this!
Can I ask how you did it in mitmproxy ? I'm not expert in this but i'm sure LDPlayer loaded the CA certificate, mitmproxy stopped all the connections to yostar server (which is expected) But when I touch to start, it display an error as if no connection to my local game server is established and the game server console does not receive anything. (before using frida, it would log that a connection had been made) Yes I have edited my local IP on redirect_server.py Idk if it's CA cert's fault or mitmproxy's. Can you help me with this ?
Update: I decided to just ditch the frida method entirely and use the mitmproxy method for redirecting server, and now it works (almost perfectly). My problem now is the club commands (for adding characters etc.) doesn't work, will open a new issue for this!
Can I ask how you did it in mitmproxy ? I'm not expert in this but i'm sure LDPlayer loaded the CA certificate, mitmproxy stopped all the connections to yostar server (which is expected) But when I touch to start, it display an error as if no connection to my local game server is established and the game server console does not receive anything. (before using frida, it would log that a connection had been made) Yes I have edited my local IP on redirect_server.py Idk if it's CA cert's fault or mitmproxy's. Can you help me with this ?
I've been trying all of this and its due to ssl certificates pinning.
Update: I decided to just ditch the frida method entirely and use the mitmproxy method for redirecting server, and now it works (almost perfectly). My problem now is the club commands (for adding characters etc.) doesn't work, will open a new issue for this!
do you download the blue archive from play store? mine has a problem while connecting with mitmproxy
I am using apk from QooApp. Not sure if it has any difference though.
@minhnguyenbk2909 I am not really sure either, actually, not an expert either. I really only followed the instructions on the mitmproxy method README, including adding the mitmproxy's CA certificates. What I did, though, after giving up with the frida method, was completely reinstalling LDPlayer.
I'm not expert in this but i'm sure LDPlayer loaded the CA certificate, mitmproxy stopped all the connections to yostar server (which is expected)
I never see such logs displayed when i running the server, what I'm getting is normal kind of packet info (?) logs.
If it would help, here is how i configure wireguard
Sorry for not being able to help much!
@minhnguyenbk2909 I am not really sure either, actually, not an expert either. I really only followed the instructions on the mitmproxy method README, including adding the mitmproxy's CA certificates. What I did, though, after giving up with the frida method, was completely reinstalling LDPlayer.
I'm not expert in this but i'm sure LDPlayer loaded the CA certificate, mitmproxy stopped all the connections to yostar server (which is expected)
I never see such logs displayed when i running the server, what I'm getting is normal kind of packet info (?) logs.
If it would help, here is how i configure wireguard
Sorry for not being able to help much!
what ldplayer version do you use?
@ArkanDash I use LDPlayer 9
@ArkanDash I use LDPlayer 9
full version to be exact
@ArkanDash I use LDPlayer 9
full version to be exact
aah, sorry, its this
@SyauqiMA can you explain each step to install the CA cert to LDPlayer ? I think this is my mitmproxy certificate problem since i always got the yellow text when turning on wireguard, even browsing chrome inside emulator gave me NET::ERR_CERT_AUTHORITY_INVALID
Update: I decided to just ditch the frida method entirely and use the mitmproxy method for redirecting server, and now it works (almost perfectly). My problem now is the club commands (for adding characters etc.) doesn't work, will open a new issue for this!
Can I ask how you did it in mitmproxy ? I'm not expert in this but i'm sure LDPlayer loaded the CA certificate, mitmproxy stopped all the connections to yostar server (which is expected) But when I touch to start, it display an error as if no connection to my local game server is established and the game server console does not receive anything. (before using frida, it would log that a connection had been made) Yes I have edited my local IP on redirect_server.py Idk if it's CA cert's fault or mitmproxy's. Can you help me with this ?
I've been trying all of this and its due to ssl certificates pinning.
Have you solved the ssl certificates pinning problem? I am encountering the same situation now and don’t know what to do.
I followed through the tutorial but when I executed the client and frida script I got this error in the game. Interestingly this error goes away when I deactivated root from the emulator. Is there any solution for this?