Timeline for frida hook `loc_*` or `sub_*`
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 26, 2022 at 17:30 | vote | accept | hmngwn | ||
| Nov 26, 2022 at 17:30 | answer | added | hmngwn | timeline score: 1 | |
| Nov 8, 2022 at 8:19 | comment | added | Robert | An example for an method address calculation in the app main binary is shown here: reverseengineering.stackexchange.com/a/30881/1848 | |
| Nov 7, 2022 at 22:00 | comment | added | Robert | Such methods don't have a name and thus need to be accessed using their address. You need to check the used base address of the used decompiler (IDA, Ghidra or want else?) Substract that from the shown address in the function name and in Frida at runtime add the base address of the module the function belongs to. That is the address you can hook in Frida. Frida has the capability to patch memory, check Frida API documentation. I assume you have to know the address and the new hex value of the encoded b.eq command. | |
| S Nov 7, 2022 at 19:18 | review | First questions | |||
| Nov 12, 2022 at 23:40 | |||||
| S Nov 7, 2022 at 19:18 | history | asked | hmngwn | CC BY-SA 4.0 |