XEKEX

it depends on the emulator u are using try to redownload the x86 version of it, keep in mind that the memory from emulator and android not the same ( emulator most data on OTHER and on mobile ANON ) download the x86 version of the emulator that's it

you forget to put ~A8 FMOV D16, X0 befor the last line

it depends on the emulator u are using try to redownload the x86 version of it, keep in mind that the memory from emulator and android not the same ( emulator most data on OTHER and on mobile ANON )

likes and comments won't add anything to your accomplishments that's my thoughts we doing it for comunity and you gain experience from it that's it

@g1doz this is double xor encryption here is a video for it :

@Rxhacker No you can't create thread using GG the only solution is by trampoline hooks, explaination : all games and apps are compiled and there is a linkage between it's functions(methods) and calls. read more it's either you jmp or pointer replace -> if the addCoins(int coins) is an actual method within the lib you can alloc mem with gg set up R1 (<- R1 not R0 bc R0 is the caller address / class field ) then call the original addCoins using BL ( or other branch instructions ) finally sweap the field pointer to the new allocmem this method is helpful if you have a global method like dmg or range ( changing it cause the enemy to have the same hack as u )

try this instructions (both are the same ) ~A8 MOV W0, #0x3333, LSL #16 ~A8 MOVK W0, #0x4083, LSL #32 ~A8 FMOV S0, W0 ~A8 RET

Good luck , if you have any other questions feel free to ask.

when dealing with processor you need to be more strict even an upper and lower naming can affect the instructions you can learn more about arm: https://developer.arm.com/documentation it's too complicated topic and not simple

I'm not a 64 user I can't test it however ,the error you're encountering is likely due to the fact that the value 0xC28F3D75 cannot be directly used as a floating-point constant in the FMOV instruction In AArch64 assembly, when using immediate values with FMOV, you typically need to represent the floating-point constant in a specific format: 0.06 FMOV S0, #0.06 or FMOV S0, 0.06 ( depending on the system ) In the 1st case #0xC28F3D75 is a 32bit value and the your instruction set it to 64bit value with the register X The third line (FMOV s0, w8) moves the value in register w8 into scalar floating-point register s0. This might be an issue depending on the context. If w8 contains a valid 32-bit integer, this conversion could be appropriate. However, if w8 contains a floating-point value, this operation might lead to unexpected results You should use W register instead to convert the register W8 to a valid 32bit floating-point: MOV w8, #0xC28F MOVK w8, #0x3D75, LSL #16 FMOV s0, w8 ret

you are using register X8 then sending register W8 to the fpu and this is wrong try this instead : FMOV S0, #0xC28F3D75 ret or try to change W8 to X8