PS3HEN resigning Eboots to hen but goes back to xmb.

[esc0rtd3w]

i got debug setup for hen but confused how to connect socat

You just need to connect a lan cable to PC from ps3

 

[larry12222]

heres the logs

Socat0 is the one that sends back to xmb but socat1 works and runs into the app/homebrew

 

[esc0rtd3w]

What about the eboot that returns to xmb? Any logs?

Or is that the one?

 

[larry12222]

What about the eboot that returns to xmb? Any logs?

Or is that the one?

Both there.. they were separate messages but now is combined so it looks out of place. But socat0 is the one that doesn't work and socat1 is the one that works.

 

[larry12222]

What about the eboot that returns to xmb? Any logs?

Or is that the one?

Have u checked them?

 

[esc0rtd3w]

Have u checked them?

I looked over them. I'll compare the 2 when I get home to see if anything stands out. Nothing out of the ordinary stood out to me. The SELF loading seems normal for both.

 

[Charles_n_town]

I looked over them. I'll compare the 2 when I get home to see if anything stands out. Nothing out of the ordinary stood out to me. The SELF loading seems normal for both.

I checked one of his that wouldn't work. It was signed to 3.55, and it seemed like it was good, so I'm thinking something is wrong with his edit of the elf. Iirc, 80010017 is a common self encryption error, so if it's just returning to the xmb, I'm thinking something inside it is wrong.

 

[esc0rtd3w]

An easy test in the meantime would be just resign the original one without edits and see if it boots, then make a small edit and resign and test again.

 

[larry12222]

An easy test in the meantime would be just resign the original one without edits and see if it boots, then make a small edit and resign and test again.

i did that and took me back to xmb. its when its being resigned or encrypted. could be something with the new HEN update.. i could try older hen versions but im guessing theres no hosts for older hen versions.

also i looked at socat0 and saw this, socat1 didnt show this error on a working eboot. i can use the eboot from Devils101 ultimate toolbox and it works. but i want to change the installer made by xmb+ to my own one. if u want i can send the eboot i made myself a few yrs back?.

 

[esc0rtd3w]

i did that and took me back to xmb. its when its being resigned or encrypted. could be something with the new HEN update.. i could try older hen versions but im guessing theres no hosts for older hen versions.

also i looked at socat0 and saw this, socat1 didnt show this error on a working eboot. i can use the eboot from Devils101 ultimate toolbox and it works. but i want to change the installer made by xmb+ to my own one. if u want i can send the eboot i made myself a few yrs back?.

Nothing was changed in HEN to cause any self booting problems.

That error you pointed out is possibly a reason its terminating and exiting back to xmb.

If you want to test old versions, they are all still online in zips, but if you are on 4.91, you are limited.

EDIT:

https://ps3xploit.me/hen/release/PS3HEN_3.3.0_4.91_FW.zip

Actually after looking at releases, 4.91 only is supported for 3.3.0, older versions do not support 4.91.

EDIT2:

Is socat0 the working eboot? Because socat1 shows these values also

Those hash values are generated in modulespatch.c (modules_patching) and matched to values in modulespatch.h in payload (hash_to_name). Im not 100% sure whats going on there with the bad hash values.

EDIT3:

You can post the eboot if you want that you mentioned, or post the pkg. The payload can be tweaked to display more information for debug output if needed also

 

[larry12222]

Nothing was changed in HEN to cause any self booting problems.

That error you pointed out is possibly a reason its terminating and exiting back to xmb.

If you want to test old versions, they are all still online in zips, but if you are on 4.91, you are limited.

EDIT:

https://ps3xploit.me/hen/release/PS3HEN_3.3.0_4.91_FW.zip

Actually after looking at releases, 4.91 only is supported for 3.3.0, older versions do not support 4.91.

EDIT2:

Is socat0 the working eboot? Because socat1 shows these values also
View attachment 44258

Those hash values are generated in modulespatch.c (modules_patching) and matched to values in modulespatch.h in payload (hash_to_name). Im not 100% sure whats going on there with the bad hash values.

EDIT3:

You can post the eboot if you want that you mentioned, or post the pkg. The payload can be tweaked to display more information for debug output if needed also

socat0 is the non working. socat1 is the working.

Nothing was changed in HEN to cause any self booting problems.

That error you pointed out is possibly a reason its terminating and exiting back to xmb.

If you want to test old versions, they are all still online in zips, but if you are on 4.91, you are limited.

EDIT:

https://ps3xploit.me/hen/release/PS3HEN_3.3.0_4.91_FW.zip

Actually after looking at releases, 4.91 only is supported for 3.3.0, older versions do not support 4.91.

EDIT2:

Is socat0 the working eboot? Because socat1 shows these values also
View attachment 44258

Those hash values are generated in modulespatch.c (modules_patching) and matched to values in modulespatch.h in payload (hash_to_name). Im not 100% sure whats going on there with the bad hash values.

EDIT3:

You can post the eboot if you want that you mentioned, or post the pkg. The payload can be tweaked to display more information for debug output if needed also

ill post the pkg does it matter if its for mods etc? or just looking for the cause?

pkg: https://tinyurl.com/bdfu9vpp

i used the to unpack and pack the pkg: https://www.psx-place.com/resources/ps3-game-extractor.824/

 

[larry12222]

Nothing was changed in HEN to cause any self booting problems.

That error you pointed out is possibly a reason its terminating and exiting back to xmb.

If you want to test old versions, they are all still online in zips, but if you are on 4.91, you are limited.

EDIT:

https://ps3xploit.me/hen/release/PS3HEN_3.3.0_4.91_FW.zip

Actually after looking at releases, 4.91 only is supported for 3.3.0, older versions do not support 4.91.

EDIT2:

Is socat0 the working eboot? Because socat1 shows these values also
View attachment 44258

Those hash values are generated in modulespatch.c (modules_patching) and matched to values in modulespatch.h in payload (hash_to_name). Im not 100% sure whats going on there with the bad hash values.

EDIT3:

You can post the eboot if you want that you mentioned, or post the pkg. The payload can be tweaked to display more information for debug output if needed also

find anything?

 

[esc0rtd3w]

I added a few more debug DPRINTF to payload and got socat logs from each EBOOT. I am going to check them out on PC and try resigning to see if any different.

Not exactly sure where issue is yet.

EDIT1: Just looking at logs, it seems like the problem still lies here when loading config

 

[esc0rtd3w]

I got it working. I resigned your 3.55 one that was going back to xmb

I attached the EBOOT in zip and also the batch file i used

I used the np_content_id 1HGCAT-PS3CODMDR_00-PS3CODMDR0002017

I also put both the EBOOT.BIN and EBOOT.ELF in same folder then ran script

@echo off

cls
echo Enter Content ID and press ENTER:
echo.
echo Example: EP4183-NPEB00344_00-LOVEFILMFULL0100
echo.

set /p contentid=

scetool -v --sce-type=SELF --compress-data=TRUE --skip-sections=FALSE --key-revision=04 --self-ctrl-flags=4000000000000000000000000000000000000000000000000000000000000002 --self-auth-id=1010000001000003 --self-app-version=0001000000000000 --self-add-shdrs=TRUE --self-vendor-id=01000002 --self-type=NPDRM --self-fw-version=0003004000000000 --np-license-type=FREE --np-content-id=%contentid% --np-app-type=EXEC --np-real-fname=EBOOT.BIN --encrypt EBOOT.ELF EBOOT.BIN


pause

 

[Charles_n_town]

I got it working. I resigned your 3.55 one that was going back to xmb

I attached the EBOOT in zip and also the batch file i used

I used the np_content_id 1HGCAT-PS3CODMDR_00-PS3CODMDR0002017

I also put both the EBOOT.BIN and EBOOT.ELF in same folder then ran script

@echo off

cls
echo Enter Content ID and press ENTER:
echo.
echo Example: EP4183-NPEB00344_00-LOVEFILMFULL0100
echo.

set /p contentid=

scetool -v --sce-type=SELF --compress-data=TRUE --skip-sections=FALSE --key-revision=04 --self-ctrl-flags=4000000000000000000000000000000000000000000000000000000000000002 --self-auth-id=1010000001000003 --self-app-version=0001000000000000 --self-add-shdrs=TRUE --self-vendor-id=01000002 --self-type=NPDRM --self-fw-version=0003004000000000 --np-license-type=FREE --np-content-id=%contentid% --np-app-type=EXEC --np-real-fname=EBOOT.BIN --encrypt EBOOT.ELF EBOOT.BIN


pause

What happens if it's signed to 3.55?

 

[esc0rtd3w]

What happens if it's signed to 3.55?

it should work the same. I think 3.55 and lower should all be the same.

 

[Charles_n_town]

it should work the same. I think 3.55 and lower should all be the same.

I see. I just wasn't sure if there was a reason you were resigning the eboot to 3.40.

 

[esc0rtd3w]

I see. I just wasn't sure if there was a reason you were resigning the eboot to 3.40.

Its just the batch file I had from years ago during initial testing, and I knew it worked for HEN.

 

[Charles_n_town]

Its just the batch file I had from years ago during initial testing, and I knew it worked for HEN.

Iirc, there's a package.conf for some app that you can fill out to build a package instead of using a bat. I think that's how the ForcedInstallTo was discovered. That was supposed to install to "anywhere" on the hdd, I believe. I put it in quotes, because I don't know if it's actually anywhere.

 

[esc0rtd3w]

Iirc, there's a package.conf for some app that you can fill out to build a package instead of using a bat. I think that's how the ForcedInstallTo was discovered. That was supposed to install to "anywhere" on the hdd, I believe. I put it in quotes, because I don't know if it's actually anywhere.

You are right about that. Honestly, my knowledge about that is minimal. I just use what I know works lol.