Cheat Engine

[Zaladine]

I'm hacking games on an android emulator, and to do so i need to access Physical Memory. There are 2 problems:
- CE 6.2 seems work smother for, in CE 6.3, the game (NOT the emulator) often closes when i search for specific values.
- in both version, CE unable to attach debugger to the emulator.

What i have to do to resolve this matter? Thanks in advance.

[Dark Byte]

Try 6.2 but 6.3 has made no changes at all in that part though, so shouldn't matter

Also, it doesn't make sense that reading memory by a memoryscan crashes one process inside a emulator. If anything your whole system should have crashed if you acceswed hardware memory like apic

You're sure you don't edit the memory? Also, it could be the game crashes because it's idle

Also, if you have root on that emulator try ceserver. There is an android build you can use (requires root)

[Zaladine]

For the 1st aforementioned problem, it was my mistake and i am sorry. I've just do some quick experiments, and it appears that when scanning address with CE 6.3 i was left my browser (chrome) opened in several tabs. While the previous attempt with CE 6.2 was done in clean state (only the emulator and CE 6.2 running).

So, the problem left is debugging the Physical Memory, at which CE 6.3 (and CE 6.2) still unable to attach the debugger to the process...

Also, i'm about to find out how to use this ceserver. Thanks for the quick reply, Dark Byte. Surely, CE is getting better and better...

[Dark Byte]

Debugging physical memory is impossible for now. Perhaps in the future when i add physical memory emulation to dbvm i might add it (slow as a snail glued to a table)

Also, debugging an emulator will not help you with anything, as it's the emulator's code you get and not the game, and even if it was the game the instruction set would be ARM which ce doesn't yet support

Your best bet is to launch the target in debug mode and debug with jdb's remote debugging, or if it's using native code gdbserver might be useful (but i think you might need root for that but not sure)

[Zaladine]

I am hacking through BlueStacks by the way. And unlike what i've been through with SNES Emulators while ago, the found addresses are keep changing in BlueStacks so creating pointer trails is what i've been trying to do to avoid the burden of finding the address over and over again.

[Dark Byte]

You can't root bluestacks?

Pointer paths will be extremely difficult because pointer values are relative to the virtual memory inside android
You first need to find a way to convert the physical address to a virtual address in the windows os, then convert that address to a physical address in the android os, and then convert that physical address to a virtual address in the android os

Also, i only know very little about ARM, but last time i screwed around with those the memory controller was something you could add yourself, so it's possible each arm based system might have their own special way to deal with address translations