PS3 PS3Xploit v3 HAN Cold Boot Installer [raf/ac3]

Now Supports 4.88 HFW!
Ps3 developer @esc0rtd3w (of Team Ps3Xploit) has a new release to show off as PS3Xploit (v3.0) HAN user's will now have the ability to change "Coldboot" (the startup/boot logo), with the new HAN Coldboot Installer (.raf (logo) & .ac3 (sound) supported) StarMelter (logo) & d1mtr7 (sound) provided the first coldboot for HAN as they pay tribute to the PS3Xploit HAN in great fashion with this injection of HAN .Another great thing we are seeing progress on also with HAN is XMB MODs, DeViL303 recently start this thread "XMB Mods now possible on OFW with HAN" there is some interesting details within that thread and worth checking out if you are intrested in XMB modding. From here i will let developer @esc0rtd3w give you all the details of this latest advancement
-STLcardsWS

ps3xploit_coldboot.png


 
Last edited:
You can write to flash (usually mounted as dev_blind or dev_rewrite) as long as it's just resource files like coldboots, waves etc. Trying to replace any executable or signed files (SELF) will likely lead to a soft brick on HEN.
Cool thank you for the details :cool2:
 
I assume that this is 4.86 compatible, isn't it?
It is not compatible. The html webpage disables the tools features because of detecting the 4.86 fimware(obviously unknown in tools code). It is funny tho cause it states "Your ps3 is not on 4.81+! Your current running FW version is 4.86 which is not compatible..." "...all features have been disabled".
 
It is not compatible. The html webpage disables the tools features because of detecting the 4.86 fimware(obviously unknown in tools code). It is funny tho cause it states "Your ps3 is not on 4.81+! Your current running FW version is 4.86 which is not compatible..." "...all features have been disabled".
i think these will be updated soon...
 
So what exactly is needed to be added to the code to make this compatible for 4.87?

Or where is the location of the boot logo and boot sound(s) to manually inject my custom files?
As with all other ps3xploit tools, the javascript needs updated when a new firmware comes along.
For 4.87, the update is simpler than usual because 99.xx% of the system binaries haven't changed a iota so generally speaking the various memory offsets the exploits use haven't changed either and all the "4.86 fw related data" should be reusable for 4.87.
In short, for this tool's javascript,
1. The 4.86 cex offsets section needs cloned & its variables renamed appropriately.
2. The loadcex_486 function needs cloned & renamed loadcex_487, the variables it uses appropriately must be tweaked to reflect the variables in the 4.87 offset section cloned in 1.
3. The firmware version detection function needs to be updated to support 4.87, it means adding 4.87 in the array of compatible firmwares & cloning the switch case for 4.86 and tweaking it appropriately.
4. There would of course also be a need to update a few strings in the GUI to reflect the new changes, those tweaks would be minor & fundamentally they would not be necessary for the exploits to work.

Overall it would only take about 30mn to make the changes & test (or maybe 1h if fw installations are needed in order to test) however this tool is only one among many things that need updated regularly & ultimately all that stuff adds up.
Moreover esc0rtd3w has been busy with other things in recent months & I would assume that the "to do" list he mentioned will have grown significantly since his last post in this thread, between the old ps3xploit tools he maintains that still need updated to support 4.87 & the nopsn apps, some of them getting updated several times a year.

Regarding information such as the path of coldboot files or whatever, I suggest you refer to psdevwiki as a matter of course.
 
Last edited:
As with all other ps3xploit tools, the javascript needs updated when a new firmware comes along.
For 4.87, the update is simpler than usual because 99.xx% of the system binaries haven't changed a iota so generally speaking the various memory offsets the exploits use haven't changed either and all the "4.86 fw related data" should be reusable for 4.87.
In short, for this tool's javascript,
1. The 4.86 cex offsets section needs cloned & its variables renamed appropriately.
2. The loadcex_486 function needs cloned & renamed loadcex_487, the variables it uses appropriately must be tweaked to reflect the variables in the 4.87 offset section cloned in 1.
3. The firmware version detection function needs to be updated to support 4.87, it means adding 4.87 in the array of compatible firmwares & cloning the switch case for 4.86 and tweaking it appropriately.
4. There would of course also be a need to update a few strings in the GUI to reflect the new changes, those tweaks would be minor & fundamentally they would not be necessary for the exploits to work.

Overall it would only take about 30mn to make the changes & test (or maybe 1h if fw installations are needed in order to test) however this tool is only one among many things that need updated regularly & ultimately all that stuff adds up.
Moreover esc0rtd3w has been busy with other things in recent months & I would assume that the "to do" list he mentioned will have grown significantly since his last post in this thread, between the old ps3xploit tools he maintains that still need updated to support 4.87 & the nopsn apps, some of them getting updated several times a year.

Regarding information such as the path of coldboot files or whatever, I suggest you refer to psdevwiki as a matter of course.

Hey thanks for the replay bguerville. You explained it fully and answered my all my curiosities within the process I was examining the git source and looking over changes as it received updates I just didn't know where the cex offsets differed and the sources for them. I did end up updating and enabling flash mount to write the coldboot files and it worked. Originally with han flashing files wasn't as easily accessible but with hen it obviously is now which is pretty sweet for a non-cfw model like I have. I know that esc0rtd3w is busy and I appreciate all he has done and why I asked my question kinda in the air rather than purely bugging him again. lol Again thsaks for your response.
 

Featured content

Trending content

Back
Top