Jbro129

it didnt work at first but after I waited a bit it worked and I got it on log LogV4-GG-GalaxyS8.zip

GG didnt load at first but then loaded after I stopped recording as I was saving the log LogV3-GG-GalaxyS8.zip

Ok here is the logcat from the second apk you sent. LogV2GG-GalaxyS8.zip

That was, I uninstalled the other one I had and those logs are from the test apk you sent.

That zip file sent above and this one is the log and the device info as a zip. I don't know why it does that but it is. GGLog-TestAPK-GalaxyS8.zip

Daemon still does not start GGLog-TestAPK-GalaxyS8.zip

No denied X's show in the logs ;-;

SuperSU has GG granted and the logs it shows says that it allowed it

How do I check the root interface of GG? I changed the root manager to another but nothing changed I tried using GameKiller also but it wouldn't load the app manager to select the app to mod. I feel like it's not a root issue rather something changed in the Galaxy s8 that makes it not work. :/

There is no other root methods for the Galaxy s8 Snapdragon :/

Ok here is log #2 GGLog2-GalaxyS8.zip I am using a rooting method called SamPWN which is basically stock root. Here is the XDA thread where it was released in case this helps - https://forum.xda-developers.com/galaxy-s8/development/samsung-galaxy-s8-root-snapdragon-t3659305

Ok I used CatLog and recorded the log ZIP has the log and device info. GalaxyS8-GGLog.zip

Hello, ever since I rooted my Galaxy s8 GG has not worked on my device. It works on all of my other devices but not on my galaxy s8. Does GG have Galaxy s8 Snapdragon support? I have tried with other memory hacking apps like GameKiller and none of them work either... All are not able to "Start the daemon" I tried all the way from v8.30.0/somwhere around there - v8.39.0 and none have worked and have given me the same error. Does GameGuardian not have support for galaxy s8? or is it just me? I rooted using SamPWN for galaxy s8/s8+ snapdragon on XDA I understand the pictures show 8.38.0 and there is a newer version, I get that error on the newest version also. Those images are just older screesnshots. _______________________________________________ added 3 minutes later Like I said same errors on 8.39.0