I'm a massive fan of GG and use it regularly on my rooted HTC U11. I recently bought a new Huawei MediaPad M5 (the 8.4" version) and was pleased to see that root is now no longer a requirement for GG - I'm quite nervous about rooting the new pad, as it breaks Widevine level 1 support. I set about downloading Parallel Space and began hacking away at Crashlands, conveniently sync'ing my gamesave from cloud storage into my Parallel Space.
Alas, I came upon the problem whereby I can attach to the Crashlands process, search and iterate to find addresses but I cannot edit or freeze values. Logcat shows errors when invoking the ptrace system call.
I've come across a few posts here that describe similar observations with Huawei devices and a few responses from the GG author that it looks like a firmware / core issue with the Huawei implementation of the ptrace system call.
I wondered what it would take to address this issue with my device and others? Could this be something that's fixed with an Xposed or Magisk module? Or is it a deliberate security measure / bug in the firmware that's just too deeply buried to do anything about?
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Question
mroshaw
I'm a massive fan of GG and use it regularly on my rooted HTC U11. I recently bought a new Huawei MediaPad M5 (the 8.4" version) and was pleased to see that root is now no longer a requirement for GG - I'm quite nervous about rooting the new pad, as it breaks Widevine level 1 support. I set about downloading Parallel Space and began hacking away at Crashlands, conveniently sync'ing my gamesave from cloud storage into my Parallel Space.
Alas, I came upon the problem whereby I can attach to the Crashlands process, search and iterate to find addresses but I cannot edit or freeze values. Logcat shows errors when invoking the ptrace system call.
I've come across a few posts here that describe similar observations with Huawei devices and a few responses from the GG author that it looks like a firmware / core issue with the Huawei implementation of the ptrace system call.
I wondered what it would take to address this issue with my device and others? Could this be something that's fixed with an Xposed or Magisk module? Or is it a deliberate security measure / bug in the firmware that's just too deeply buried to do anything about?
5 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.