That is false. I've been reversing bo3 for a few months and and the only checks/challenges answered by the client are:
1. 3 crc checks of the .text segment of the eboot, so editing the process via rtm, sprx or a modified eboot will be detected.
2. dvar checks, like cg_fov, g_speed etc... which...
That error happens because you did not link the needed library to your project, and iirc xsetting_CC56EB2D is a vsh export so you can't use it in an homebrew.
An alternative that you could use is this: https://www.psx-place.com/threads/getting-the-current-user.1419/#post-12506
I loaded the prx from your repo into ida, segments are not being created so I had to do it myself. The opd section isn't loaded into ida either which makes the module info not so useful
Hi psx-place!
I stumbled upon an interesting sprx, so I decided to yeet it into ida but the output seemed incorrect, so I decided to take a peek at the decrypted prx in HxD and that's when I realized it was no ordinary sprx.
I took a look around on psdevwiki and noticed that the start of the...
By compiling a project of mine and taking a look at it in ida, as well as taking a look into the sdk headers, I was able to create an artificial stdc import stub
C++ code:
Assembly output:
That was the easy part, but now I'm kinda stuck at making the actual function stubs and tables...
Hi,
I was wondering how the VSH exports stub libraries were made, I wasn't able to find much informations about those.
I do know how to use them in vsh plugin projects and that they were made by 3141card but that's about it.
Those exports are only used to get/set the layout factor and positions from an existing widget.
Exports that are related to the actual layout files are:
0x6BFD6A5A _ZN3vsh11LayoutTable4SwapEiiivsh::LayoutTable::Swap(int, int, int)
0xD7138829PhiSetLayoutTable
Heya, not sure if this will answer your question but it seems like ida use a different api in 7.X compared to 6.X, I tried kakaroto's scripts in ida 7.5 and it hangs so maybe they were talking about a compatibilty issue? Which is confusing considering mysis post here...
My bad, i didn't look properly, 0x805 is a PhXmList object but can only be created if is a child of PhXmBar while 0x806 a PhXmList object that can be created without a specific parent type.
Those types aren't present in the switch case statement in paf::View::InstantiateWidget():
0x80A, 0x80B...
I'm aware of that, i added the objects directly as childrens of page_xmb_indicator.
I've been messing around with the way vsh.self parse rco files, i attached some notes to this post.