PS3HEN Error signing an EBOOT.BIN Debug with SCETools

Kevstah2004 said:
Do I need to use vsh.self also?
or any other files?
templat/4.92_rebug/ doesn't exist & the hashes folder from C:/Users/user/AppData/Local/Temp/PS3MFW
seems to stay empty then just autodelete,
PS3MFW-MFW & PS3MFW-OFW are created along with ps3mfw.log with the listed used curves ERK & IV keys.

Edit: I added vsh.self an now it complains vsh.self.nrm is missing in the devflash.
Click to expand...
I dunno. I don't know if I can help with that. I've never tried adding my own files to an update PUP. I know that rebug contains three vsh.self files, which seem to be listed in that image you have. I've never heard of vsh.self.nrm though.
 
Gregor said:
I dunno. I don't know if I can help with that. I've never tried adding my own files to an update PUP. I know that rebug contains three vsh.self files, which seem to be listed in that image you have. I've never heard of vsh.self.nrm though.
Click to expand...

https://www.psx-place.com/threads/u...fw-compatible-by-team-ps3xploit.15398/page-17

If Cobra is enabled vsh.self gets overwritten then restored to CEX or DEX from base firmware if disabled?
I noticed in rpcs3 EVILNAT D-PEX is still listed as CEX not DEX in the version.txt after you install the firmware & ps2_netemu is still listed as softemu just with a higher revision number.
I'll try an get the vsh.self from my real ps3 with both Cobra enabled & disabled, it's a CEX model spoofed to DEBUG DEX atm.
 
Last edited:
what it says in that task manager image of yours with .bk is how rebug disables cobra. it just simply adds .bk to the filename to disable it. I don't know if it's like that with evilnat.
 
These are the hashes I have so far for the templat folder.

basic_plugins.sprx.orig
b5988dba00020154
game_ext_plugin.sprx.orig
e274af7b0001e596
vsh.self.orig
a0001f45002e68f1

If you put the .self & .sprx files in the template 4.92_rebug folder it'll generate the hash an overwrite them with .orig files, it's now complaining about missing the hash for vsh.self.cexsp.orig
which I tried getting from vsh.self.cex but to no avail.
 
Kevstah2004 said:
These are the hashes I have so far for the templat folder.

basic_plugins.sprx.orig
b5988dba00020154
game_ext_plugin.sprx.orig
e274af7b0001e596
vsh.self.orig
a0001f45002e68f1

If you put the .self & .sprx files in the template 4.92_rebug folder it'll generate the hash an overwrite them with .orig files, it's now complaining about missing the hash for vsh.self.cexsp.orig
which I tried getting from vsh.self.cex but to no avail.
Click to expand...

do you mean you got it from vsh.self.cexsp? because that's one of the vsh.self files from rebug:
upload_2025-9-5_19-37-49.png


those hashes don't look right if you compare them with the originals. I don't really remember how to read the hashcalc readouts. it's been like a decade or something since I've messed with it.
 
Last edited:
Kevstah2004 said:
I don't think the swap files are included in the EVILNAT firmware .pup, I think certain files only get generated by the ps3 after enabling or disabling certain options?

https://github.com/aldostools/webMAN-MOD/blob/master/_Projects_/vsh_menu/include/rebug.h

Edit: Update I turned off the rebuilder options & now it generates the .pup without errors. The .pup seemed to fully install ok on rpcs3 but I haven't tried it on a real ps3 yet.

https://anonymfile.com/8pYEq
Click to expand...

oh, I thought you had some new rebug 4.92 or something. I got that file list from 4.84.2 rex. I think mfw is too old to accommodate evilnat pex, so that's probably why it asks for those specific files (it's only tailored to rebug rex as far as a cex/dex firmware goes). as for it installing on rpcs3, that's good, but you shouldn't use that as a guarantee it will install on hardware. afaik, rpcs3 doesn't install the coreOS of a firmware pup, just dev_blind (i.e. dev_flash1). I think dev_flash2 is the xregistry, and dev_flash3 is the bd firmware iirc. also, based on that firmware list, it sounds like it tries to install cobra disabled in mfw. there's now a safeguard to disable it if something is wrong with it where before it could brick the system. I only know how it does that with rebug. I've never installed evilnat on hardware.
 
Gregor said:
oh, I thought you had some new rebug 4.92 or something. I got that file list from 4.84.2 rex. I think mfw is too old to accommodate evilnat pex, so that's probably why it asks for those specific files (it's only tailored to rebug rex as far as a cex/dex firmware goes). as for it installing on rpcs3, that's good, but you shouldn't use that as a guarantee it will install on hardware. afaik, rpcs3 doesn't install the coreOS of a firmware pup, just dev_blind (i.e. dev_flash1). I think dev_flash2 is the xregistry, and dev_flash3 is the bd firmware iirc. also, based on that firmware list, it sounds like it tries to install cobra disabled in mfw. there's now a safeguard to disable it if something is wrong with it where before it could brick the system. I only know how it does that with rebug. I've never installed evilnat on hardware.
Click to expand...

Yeah somebody else made a 4.88.2 mod here but it's for lvl1 overclocking not devflash.
 
Kevstah2004 said:
Yeah somebody else made a 4.88.2 mod here but it's for lvl1 overclocking not devflash.
Click to expand...

yeah, overclocking isn't that difficult with a pup, but it's no longer necessary. a lot of people seemed to have bricked their systems by using too extreme of values. I don't know if it's safer now. does it disable itself on power off? mfw is pretty easy to handle, though they warn against reusing patches that are already in the firmware. however, I'd expect it to fail for not find the right hex sequence anyway, so it may not be that dangerous on a cfw pup. though, I'd suggest having an e3 or something if you dabble in mfw yourself on hardware. however, I know e3s are expensive these days. I think the only place to get them, legit versions, is Germany.
 
https://wiki.rpcs3.net/index.php?title=Help:Frequently_Asked_Questions

vsh.self / xmb works on rpcs3 if you use the PPU decoder : Interpreter (static),
it supposively works later on Recompiler (LLVM) after the initial setup, but it kept giving me unmapped memory errors.
File Manager & Apollo seem to work fine also for file access using Recompiler (LLVM) or Interpreter (static).
Still need to install the webman pkg to see if it'll even attempt to load the ps2_netemu.self.
 
You must log in or register to reply here.

Similar threads

Back
Top