View previous topic :: View next topic |
Author |
Message |
byteburner Cheater
Reputation: 0
Joined: 09 Feb 2023 Posts: 31
|
Posted: Fri Feb 10, 2023 12:33 am Post subject: Cheat Engine for Android and Android Emulators |
|
|
Hey everyone,
it's my first time here.
I would like to appreciate the tremendous work for this piece of art. thank you Dark Byte and everyone helped and supported this work.
recently I'm trying to make mods for Android games but got really frustrated when games are using shared calls for the player and enemy .
with game guardian you can only search for values in memory but no debugging. so any why that CE can debug directly on Android? I want to be able to do all kind of methods and conditions I can do with CE
in addition, I tried CE with MEMU emulator but it fails to find the values while GG can find them easily. so any why to use it with emulator ?
so much appreciated!
|
|
Back to top |
|
 |
Dark Byte Site Admin
Reputation: 470
Joined: 09 May 2003 Posts: 25796 Location: The netherlands
|
Posted: Fri Feb 10, 2023 1:05 am Post subject: |
|
|
for scanning emulators tick mem_mapped in settings
as for debugging you will be able to use ceserver and ce 7.5 in nox player (and your own hardware device)
_________________
Do not ask me about online cheats. I don't know any and wont help finding them.
Like my help? Join me on Patreon so i can keep helping |
|
Back to top |
|
 |
byteburner Cheater
Reputation: 0
Joined: 09 Feb 2023 Posts: 31
|
Posted: Sat Feb 11, 2023 5:41 am Post subject: |
|
|
mem_ mapped was already ticked but that didn't help, it got solved though. the thing is the emulator is running the instance in separated process called Hyperv Headless Fronted. and that's what I needed to attach CE to instead of the emulator's process itself ( I didn't encounter a similar thing for a very long time ). and now I can find values. still zero debugging of course
for the debugging part ( using CE 7.4 only, have to wait till 7.5 is being public ), after enabling root in emulator's settings I'm still having trouble installing Magisk on several emulators. ended up using Magisk Delta instead which is half the way there. the emulator's instances are acting weird and refusing to boot properly sometimes and I'm not able to get full root access. terminals are freezing and a lot weird behaviors. some Apps are being granted root access and working fine while others giving messages about failing to get root access even though I grant them permission in Magisk Delta. Thus I'm not able to install CEserver yet to test debugging. I'm still working on it. will see how far I can go on my own then will post back
|
|
Back to top |
|
 |
byteburner Cheater
Reputation: 0
Joined: 09 Feb 2023 Posts: 31
|
Posted: Mon Feb 13, 2023 6:03 am Post subject: |
|
|
For Root privileges , in MEMU it is a headache even though it gives the best 3D performance but stay away from it for modding.
just updated to the latest Nox and now it has Android 9 64Bit. Whenever I'm connecting CE to nox_adb_exe I keep getting "invalid ceserver version (cheatengine network 2.0)". in the terminal side it says "accept=4"
any idea what's wrong?
appreciated
|
|
Back to top |
|
 |
byteburner Cheater
Reputation: 0
Joined: 09 Feb 2023 Posts: 31
|
Posted: Fri Feb 17, 2023 4:07 pm Post subject: |
|
|
I suggest there should be a sticky thread regarding this topic. because it is really hard and time consuming to figure it out without any guideline.
had to scout for a long time by searching using specific keywords to find random topics from random people in random places regarding a solution for this.
The following are essential points which cannot be found in single topic ( best two points at a time in one topic because what worked for some didn't work for others) to check for workaround to make it work:
the worst part is that if any of the below failed CE will return "invalid ceserver version"
P.S: try to use the adb that came with your emulator for better success rate ( yes you read it right. it is still not guaranteed )
1. adb.exe version matching with the built-in adb protocols used by CE
2. adb.exe is not already running especially if is ruining automatically by some application at windows start up. in this case you need to kill adb server and start it again. "adb.exe kill-server" then "adb.exe start-server"
3. "adb.exe connect <provide an IP>" connect to localhost(127.0.0.1) always when using emulator ( don't bother with internal IP of the emulator that it is using to get internet access ). in case of a physicals Android then use that one instead of localhost.
4. don't use "adb.exe connect 127.0.0.1:52736" it will always throw an error; "time out no response". instead ""adb.exe connect 127.0.0.1" it will get port 5555 automatically assigned and will be successful ( hopefully in your case otherwise you need to trace back further)
5.you need to forward all the traffic for CE port 52736. avoid UDP and only use TCP for more reliability. "adb.exe forward tcp:52736 tcp:52736" and yes tcp parameter is used twice because the function needs two to work
6.all the above will fail if you didn't enable "connection bridge" from your emulator. you might find it under other names like: bridge connection, host bridge connection, client bridge connection, network bridge, bridge mode...etc.
7. emulator must be rooted. some of them can be so by a simple tickbox in the options others need magisk or magisk delta to have a true root. if needed to root using magisk then dont forget to turn off emulator's root option in settings AFTER magisk is installed ( you need it to install it first) or it will conflict with magisk.
8.the terminal must be in SU privileges using the su command.
9. ceserver***** must be set to executable in permissions. use total commander for that. for me root browser and es file explorer failed even with superuser permissions.
10. you need to restart your emulator's instance then go through adb commands in windows and only after running ceserver**** and having it listening then use the forward command.
your mileage may vary. and this is just a general guideline that is Not organized properly. it can be refined and expanded but this is just from the top of my head.
|
|
Back to top |
|
 |
byteburner Cheater
Reputation: 0
Joined: 09 Feb 2023 Posts: 31
|
Posted: Sat Feb 18, 2023 5:55 am Post subject: |
|
|
Eric, need your help my man.
whenever I try to debug any application its freezing or closing. exactly when trying to attach the debugger to see what's accessing something. tried all debugging methods but still the same. I can scan for values normally but some apps when I just try a simple scan it gives addresses with same values for current scan and previous scan the only different is first scan.
I'm using 7.5 for both CE and ceserver_x86. running nox latest version and android 9
copied all ceserver related files to system/xbin and all of them are executable.
for ceserver I'm getting " cannot find file or directory" this one is driving me crazy the files is there and it cannot see it. I even renamed the file to avoid any hidden characters.
for ceserver_x86_64 I'm getting
Code: |
130|:/system/xbin # ceserver_x86_64
process_vm_readv=0x727b667002b0
process_vm_writev=0x727b667002d0
listening on port 52736
---
&s=0x7ffdec3972e8
main=0x6444daee25f0
sizeof(off_t)=8
sizeof(off64_t)=8
sizeof(uintptr_t)=8
sizeof(long)=8
CESERVERPATH=/system/xbin/ceserver_x86_64/
Segmentation fault
139|:/system/xbin # |
for ceserver_x86 it is connecting normally but debugging make them crashes.
I triple checked and redownloaded the and extracted the files again but still getting same results. I'm out of ideas
|
|
Back to top |
|
 |
|