• PS3HEN is now supporting 4.93 Firmware

    View Official Release Post for additional information HERE
PS3HEN

PS3HEN PS3HEN - Official Release Thread (Homebrew Enabler for the PS3) v3.5.0 (4.93 support)

I was like that yesterday I had dev_blind and dev_rewrite. First was as clean dev_hdd0
Dev_hdd1
♦️!⚡ dev_blind
Dev_flash 2
Dev_flash 3
♦️!⚡ dev_rewrite
Media
Usb...
Kept me all night up couldn't download save any packages .. few hours dev_blind was able to save. . But they need a tool box that will be able to open all their versions. As well as a phone data transfer. And when they say reboot. They 4 different choices + the restart. In the hybrid firmware.
if you just need to write to flash, then dev_rewrite replaces dev_blind to make dev_flash re-writable

but yeah, the double mount has some issue and is not present in 2.3.1 as the original readme would suggest. The OP has been updated for this.

WMM will mount dev_blink AFAIK
 
yeah, wmm will mount dev_blind. it's off by default, I think, so you just need to enable it. very handy if a modified flash file becomes corrupted, since you can just ftp and replace the file without having to reinstall the firmware.
 
if you just need to write to flash, then dev_rewrite replaces dev_blind to make dev_flash re-writable

but yeah, the double mount has some issue and is not present in 2.3.1 as the original readme would suggest. The OP has been updated for this.

WMM will mount dev_blink AFAIK

Yes, mount the same device with 2 names have issues... have you tried remapping /dev_blind instead of try to mount it?

sys_map_path((char*)"/dev_blind", (char*)"/dev_rewrite");

IMO it's better to return to the original standard "/dev_blind", instead of have 2 standards.
https://github.com/Joonie86/PS3HEN/commit/c2c14b1735137929badfe655c3c8e8876acc0cd5#comments
 
Yes, mount the same device with 2 names have issues... have you tried remapping /dev_blind instead of try to mount it?

sys_map_path((char*)"/dev_blind", (char*)"/dev_rewrite");

IMO it's better to return to the original standard "/dev_blind", instead of have 2 standards.
https://github.com/Joonie86/PS3HEN/commit/c2c14b1735137929badfe655c3c8e8876acc0cd5#comments

It would be nice but apps like multiMAN disables dev_blind once you boot into it. So it can cause issues if someone tries to update HEN and dev_blind is disabled. That's why they chose to do this. I just use webMAN to enable dev_blind upon boot and doesn't seem to cause any issues but for some odd reason when it's enabled by HEN issues arise. So not sure what can be done about that.
 
hi guys, since today i use latest hen, from today i can't enable hen. If (after a lot of try) it enable, webman doesn't load any game. Anyone have this issue? Enable hen in an online enabler? thanks
 
remove the webman mod (annoying), and correct the problem of detection of the Bluray disk (game) in multiman, every time I change the game with the multiman in both the XMB and the multiman. plis
 
Hi, i have PS3 fat CECHL with Hen 2.3.1 and it was working great but after I installed webMan, Multiman, sMan - not sure which one caused it but when I power on PS3 now the fan is loud as a vacuum :eek new: . I think its going 100% and only stops being so loud until I start Hen :chewie:

I've tried uninstalling these apps but doesn't fix it?
 
Hi, i have PS3 fat CECHL with Hen 2.3.1 and it was working great but after I installed webMan, Multiman, sMan - not sure which one caused it but when I power on PS3 now the fan is loud as a vacuum :eek new: . I think its going 100% and only stops being so loud until I start Hen :chewie:

I've tried uninstalling these apps but doesn't fix it?

WebMAN MODs fan control is kicking in. That's why jet engine. Also, if it is jet engine after webMAN, that's a sign your Ps3 is too hot.
Go to game column on Xmb "webMAN Games/webman setup/Ps3 webMAN [setup]"
It will open a webpage with webmans setup.
Click "Setup" on the left.
Change fan from "Auto at... " to "manual".

This will be less jet engine, but still cools better than syscon.

Also, your Ps3 model is CFW compatible. So you can have better than HEN.
 
It would be nice but apps like multiMAN disables dev_blind once you boot into it. So it can cause issues if someone tries to update HEN and dev_blind is disabled. That's why they chose to do this. I just use webMAN to enable dev_blind upon boot and doesn't seem to cause any issues but for some odd reason when it's enabled by HEN issues arise. So not sure what can be done about that.
Yeah, caused a lot of issues to solve one small issue IMO. It would have been very easy to explain to people that multiman unmounts dev_blind, so just say " if updating HEN dont run multiman first", problem solved, super simple. Instead we now have constant issues with people trying to use wrong one, and now all custom.pkgs need to be made separate for CFW and HEN, So it will be causing issues forever. Complete disaster if you ask me.

Aldo had posted a solution ages ago, obviously webman can keep dev_blind mounted so MM issue is not even an issue really and could have been solved easily other ways like we have on CFW.

Code:
My suggestion is to keep using /dev_blind instead of /dev_rewrite
Two standards for the same function cause incompabilities, confussion, more work for devs, etc...
For the issue of /dev_blind being unmounted by some homebrews (which was the reason of /dev_rewrite), the solution is simple: automount /dev_blind in mappath.c when an application tries to use it (e.g. pkg installer).
 
Last edited:
hallo i have som issuse
Zg01rTP
IMG_20190709_150844.jpg

after installing hen 100% it is failed
model no cechj04 fat
update with 4.84 HFW
 
Yeah, caused a lot of issues to solve one small issue IMO. It would have been very easy to explain to people that multiman unmounts dev_blind, so just say " if updating HEN dont run multiman first", problem solved, super simple. Instead we now have constant issues with people trying to use wrong one, and now all custom.pkgs need to be made separate for CFW and HEN, So it will be causing issues forever. Complete disaster if you ask me.

Aldo had posted a solution ages ago, obviously webman can keep dev_blind mounted so MM issue is not even an issue really and could have been solved easily other ways like we have on CFW.

Code:
My suggestion is to keep using /dev_blind instead of /dev_rewrite
Two standards for the same function cause incompabilities, confussion, more work for devs, etc...
For the issue of /dev_blind being unmounted by some homebrews (which was the reason of /dev_rewrite), the solution is simple: automount /dev_blind in mappath.c when an application tries to use it (e.g. pkg installer).


While I agree people just don't read what comes with the files. There is always going to be those that complain. They chose the lesser of two evils in my opinion. People like us that have been around know what we have to do and if using webMAN we get this anyhow upon boot. I'm sure there would be even more complaints the other way.

And to get rid of the conflicts with webMAN and multiMAN just disable dynamic fan control and use static fan control. Issue solved between the two. That or just webMAN vanilla not mod. Problem solved.
 
Hi, i have PS3 fat CECHL with Hen 2.3.1 and it was working great but after I installed webMan, Multiman, sMan - not sure which one caused it but when I power on PS3 now the fan is loud as a vacuum :eek new: . I think its going 100% and only stops being so loud until I start Hen :chewie:

I've tried uninstalling these apps but doesn't fix it?
Inside the config of the webManMod, change the fan settings to Syscom or manual (42~44)
 
They chose the lesser of two evils in my opinion.
I don't agree, I have seen tonnes of people are still getting the 8001003A error still since dev_rewrite was implemented, so really it solved nothing IMO. Keeping dev_blind enabled would have solved everything with no changes to explain to anyone, so they would not have needed to read anything, Really not sure how current situation could be be called a better solution, it has just doubled the possible mount points and generated confusion, and will be generating confusion forever.

Main issue is that there is no way to tell which one a pkg uses, so you dont even know which one needs to be enabled now when installing a pkg, and this will be an issue forever now.
 
I don't agree, I have seen tonnes of people are still getting the 8001003A error still since dev_rewrite was implemented, so really it solved nothing IMO. Keeping dev_blind enabled would have solved everything with no changes to explain to anyone, so they would not have needed to read anything, Really not sure how current situation could be be called a better solution, it has just doubled the possible mount points and generated confusion, and will be generating confusion forever.

Main issue is that there is no way to tell which one a pkg uses, so you dont even know which one needs to be enabled now when installing a pkg, and this will be an issue forever now.


I'm not here to disagree with you just I haven't had any issues with dev_rewrite myself but admittedly I have had to adapt a bit. I haven't noticed it as I don't use multiMAN often and I have dev_blind with webMAN. And if I need it I know what to do. I will say it does at a bit of confusion. But I guess I don't notice it as I do my mods/tweaks before going in game and I don't switch between games etc. I stick with one game till I have completed it 100% then move on to the next. So I can see where this can be an issue with those swapping games or installing now software etc. I'm just one user and I adapt where needed but even on my CFW system dev_blind isn't enabled upon boot unless webMAN does this.
 
Its cool to have different opinions.

For my side, for example from now on any XMB mod like even a coldboot pkg, or xml mod, that would normally be universal for HEN and CFW will now need separate versions, and you know people will not read info and will try to install wrong ones as they keep doing already. So if I had to weigh up the errors this solution has caused and will cause in future, compared to the few errors it has saved I would definitely not call it the lesser of 2 evils.

My main problem with it is that there were tonnes of different ways to handle this small issue, and instead going with a smart solution, the "easiest" method was used, without thinking of the consequences. For a start it instantly made all HEN theme pkgs obsolete, so it created a tonne of 8001003A errors as soon as it released, when this was what it was meant to solve.

I dont see how this issue can ever go away now unless both CFW and HEN start mounting both paths which is just completely stupid. :D
 
Its cool to have different opinions.

For my side, for example from now on any XMB mod like even a coldboot pkg, or xml mod, that would normally be universal for HEN and CFW will now need separate versions, and you know people will not read info and will try to install wrong ones as they keep doing already. So if I had to weigh up the errors this solution has caused and will cause in future, compared to the few errors it has saved I would definitely not call it the lesser of 2 evils.

My main problem with it is that there were tonnes of different ways to handle this small issue, and instead going with a smart solution, the "easiest" method was used, without thinking of the consequences. For a start it instantly made all HEN theme pkgs obsolete, so it created a tonne of 8001003A errors as soon as it released, when this was what it was meant to solve.

I dont see how this issue can ever go away now unless both CFW and HEN start mounting both paths which is just completely stupid. :D


Very true as now my XMB mods I just FTP over and use your truck of entering remote play then exit for it to take without a reboot.
 
Back
Top