4.30 vsh.elf results compared to yours
0x3AF884=4BFFCDE1
0x300A34=38A00318
4.30 VSH.elf doesnt have 4831EE1D hex
dont know if this helps, I'm new to patching VSH
Last edited by PatrickBatman; 10-31-2012 at 10:29 PM.
PS3 Slim w/ Rebug Rex 4.30.2, 500GB Internal, 1TB/3TB External; PS2 Fat McBoot w/ Hard Drive; Windows 7 x64 Ultimate
Last game finished: Crysis 3 | Currently Playing: Dead Space 3
It was just my best guess, they start with 4831 and 4B, they are approximately in the same range as values that needed to be changed in 3.41-3.55 vsh.elf's, and interval between them was always 5A0, so I decided this is the case. I may be mistaken, of course.
The danger is not that a particular class is unfit to govern. Every class is unfit to govern. - John Emerich Edward Dalberg-Acton
I also found the bytes in PatrickBatman's decrypted vsh.self, but offsets are a little different.
No HW Flasher here, so I will wait for anyone who can test and confirm.
were these the offsets used in the original or REBUG's
rebug required more patches, like 3 patched vsh files. We are trying to guess the new offsets as the old ones arent in newer VSH from what i saw
PS3 Slim w/ Rebug Rex 4.30.2, 500GB Internal, 1TB/3TB External; PS2 Fat McBoot w/ Hard Drive; Windows 7 x64 Ultimate
Last game finished: Crysis 3 | Currently Playing: Dead Space 3
Well now we can just extract patched 421 VSH self and decrypt REBUG CFW/4.31 SPOOFER to get this info
I found it in VSH.elf by using IDA and some scripts when i finally took a break from it I see rebug released CFW hahaha
PS3 Slim w/ Rebug Rex 4.30.2, 500GB Internal, 1TB/3TB External; PS2 Fat McBoot w/ Hard Drive; Windows 7 x64 Ultimate
Last game finished: Crysis 3 | Currently Playing: Dead Space 3