How about add a similiar scan pattern when no-magic-dex is in the MIDDLE of the range
kiyadesu opened this issue · comments
00 00 00 00 00 00 00 00 ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? 70 00 00 00 ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? 70 00 00 00
This is good, but I think it is not credible of only match the size or offset fields (header_size, string_id_offset).
Maybe verify the address order of tables offset(string_ids_offset, field_ids_offset, ...) is better, because it‘s difficult to modify and clear, on current.
come on, pr~
but when header & maplist becomes not credible as you said, how to get the offset order?
header_size, string_id_offset is not credible, because in memory has many 0x70.
map_off, type/proto/field/method/class_def_off is relatively reliable.
and in the map_list, has many table offsets, also credible.
我的塑料英语快编不下去了
Oh, I thought maplist and header values could all be manipulated, that's a extreme situation. 💃
No pattern can ensure success of all match after all.
Adapation on by one is the ultimate solution. :(
頑張れ！英語をすること！:P
Thank you! :)