Help! Searching for an working android mod menu template

[TheCraTer]

Hello,
I downloaded several versions of LGL mod menu but hooks and patches not working .... so i'am searching for a well working mod menu template without any errors.
Is there anyone has one?

 

[Smiley3rd]

Figure out why the hooks and patches are not working, use frida and logs to verify. Almost ALL templates share the same hooking and patching methods

 

[TheCraTer]

Figure out why the hooks and patches are not working, use frida and logs to verify. Almost ALL templates share the same hooking and patching methods

It gives no errors the game working without crashing but functions not working...is there a certain method to detect the cause?

 

[TheCraTer]

Up

 

[xyzhunter]

if not work then it's patched by dev
you need check one by one methods that actually work.

 

[Smiley3rd]

It gives no errors the game working without crashing but functions not working...is there a certain method to detect the cause?

Yes, logging is not only for printing errors. You can use it to for verifying also like printing that the hook has been called, bytes has been changed, fields has been changed, and many more. If your hook or patches doesn't work, there could be a million reason but to have a guide on how to tackle them you could follow a simple roadmap. Check if the target is correct, this involves target lib, target address, target field, etc. If target is correct then you can proceed with hooking or patching. As I said before, logging is the most useful part in debugging as it gives you idea on what is going wrong with your implementation

 

[kamran_k]

Make sure the offsets and hooks in the template match the current game version, updates break them all the time. Also double check the target lib name in the template config, some games rename or split their libs. Testing with one simple patch first helps narrow down whether it's the hook or the offset.

 

[TheCraTer]

Yes, logging is not only for printing errors. You can use it to for verifying also like printing that the hook has been called, bytes has been changed, fields has been changed, and many more. If your hook or patches doesn't work, there could be a million reason but to have a guide on how to tackle them you could follow a simple roadmap. Check if the target is correct, this involves target lib, target address, target field, etc. If target is correct then you can proceed with hooking or patching. As I said before, logging is the most useful part in debugging as it gives you idea on what is going wrong with your implementation

I tried many things until found a source using auto update hooks
auto Playerclassname = new LoadClass("namespace", OBFUSCATE("classname"));
DWORD mod1 = Playerclassname->GetMethodOffsetByName(OBFUSCATE("offsetname"), 0);
MSHookFunction((void *)("libil2cpp.so", mod1), (void *) new_mod1, (void **) &old_mod1);


But how to use it with aarch64?