PS3 [Update v6.1.0] SEN Enabler v6.0.9 - Includes 4.83 Spoof (Restoring PSN Access on 4.82 CFW)

UPDATE (Oct. 17) - IMPROVED 4.83 CFW Support adding in v6.1.0
.Since the 4.83 firmware update PS3 CFW user's have been shut out of PSN, but developer @Evilnat comes to the rescue with the release of SEN Enabler v6.0.9 which contains support for 4.83 firmware by providing a spoof for current 4.82 CFW's, so that means PSN Access are now restored, Support for 4.83 CFW has been added, but since we have not seen any release's yet this aspect of the update has been untested, You can keep this page bookmarked as we will be updating it when CFW's and other hombrew / tools & utilities become available with new 4.83 support, You can view all the details of this update from Evilnat's release notes found below

WDLqqXK.png

If connecting on PSN with an exploited device, your ALWAYS risk the potential for a possible ban.


Download v6.1.0:
MEGA || MEDIAFIRE || SENDSPACE || RGHOST || ZIPPYSHARE

Source (Release & Support/Information Thread): psx-place.com

.See additional 4.83 CFW/Homebrew Releases and Updates > > > Link
 
Last edited:
Files are not per user, is safe to send/post them.
Can anyone with PS2 issue can send me 5 files from their PS3?
  • dev_flash/vsh/module *all files with vsh in name* (should be 3)
  • dev_flash/rebug/cobra/stage2.cex stage2.dex *name can be little bit different*

Files need to be from PS3 with ps2 issues. So after using SEN ENABLER. Maybe i can try to fix that.
Does it matter if the system is cex or dex ?
 
Ok, i tired to recreate issue on Rebug 4.82.2 , and i wasn't able to do this.

Tested all vsh versions, and all kernel/target id combinations, and PS2 games work fine. It seems that only thing that can do this is initial vsh mode detection, but i can't test installing spoof in all modes :D Is time consuming.

So, I installed spoof (enabled psn) while:

System mode set to: Normal
Target ID: DEX
LV2 Kernel: DEX

After that PS2 iso worked on every possible mode. Please post your settings while spoof was enabled first time. Maybe it will help somehow. Also if your System mode is set to: Rebug please post what XMB Operation mode was set. Retail, or Debug.

Fyi @Evilnat
 
Ok, i tired to recreate issue on Rebug 4.82.2 , and i wasn't able to do this.

Tested all vsh versions, and all kernel/target id combinations, and PS2 games work fine. It seems that only thing that can do this is initial vsh mode detection, but i can't test installing spoof in all modes :D Is time consuming.

So, I installed spoof (enabled psn) while:

System mode set to: Normal
Target ID: DEX
LV2 Kernel: DEX

After that PS2 iso worked on every possible mode. Please post your settings while spoof was enabled first time. Maybe it will help somehow. Also if your System mode is set to: Rebug please post what XMB Operation mode was set. Retail, or Debug.

Fyi @Evilnat
thank you for spending time to diagnose the issue,

my system is Rebug 4.82.2 Lite Cobra 7.55 CEX
when i first installed Sen Enabler the settings was
- Cobra Enabled
- XMB default didn't touch it
After that I signed in PSN normally but ps2 games became not working, I disabled Sen Enabler but ps2 games still not working,
I installed fresh rebug lite again and followed the claim of Dev. Jooney that I read in ps3hax, he said that sys call has to be disabled before installing sen enabler to avoid mismatch hashes , so I did disable sys call but the same issue is still appeared unfortunately.
 
thank you for spending time to diagnose the issue,

my system is Rebug 4.82.2 Lite Cobra 7.55 CEX
when i first installed Sen Enabler the settings was
- Cobra Enabled
- XMB default didn't touch it
After that I signed in PSN normally but ps2 games became not working, I disabled Sen Enabler but ps2 games still not working,
I installed fresh rebug lite again and followed the claim of Dev. Jooney that I read in ps3hax, he said that sys call has to be disabled before installing sen enabler to avoid mismatch hashes , so I did disable sys call but the same issue is still appeared unfortunately.

@kazarovv , I fount the post mentioned above, sorry it wasn't in ps3hax and the developer called Joonie , his idea to fix the issue was here in psx-place please check out this
 
I found the issue, Rebug Lite is detected as Rebug REX/D-REX.
  • To fix PS2 games enable cobra in rebug toolbox
  • Download this file (click on view raw): https://github.com/Joonie86/COBRA-7.3/blob/master/482/LITE/BIN/release/stage2.cex.release
  • Rename it to stage2.cex
  • Check that MD5 is EDDC669E75D9A08C65BDC324F917F3CA
  • then place this file in /dev_blind/rebug/cobra/
  • Overwrite old file, if asked (if you are not asked to overwrite, something is wrong).
  • Restart PS3.
  • Now you should have working PS2 games, and spoof


Note: You are messing with flash files, you are doing it at your own risk. USE ONLY ON REBUG LITE 4.82.2!
 
Last edited:
Hello, i'm confused, trying to block those domain adresses in router, but i don't understand what the "#443" is nor where to put it? Can someone help with this?
 
Hello, i'm confused, trying to block those domain adresses in router, but i don't understand what the "#443" is nor where to put it? Can someone help with this?
443 is the ssl port.

Where to input it into your router's settings depends on your router's GUI I guess.
Usually on a URL blocker, either the port needs to be typed into its own dedicated text box, separate from the URL, or it can be appended to the URL after a colon like this:
https://www.xxx.com:443
 
443 is the ssl port.

Where to input it into your router's settings depends on your router's GUI I guess.
Usually on a URL blocker, either the port needs to be typed into its own dedicated text box, separate from the URL, or it can be appended to the URL after a colon like this:
https://www.xxx.com:443
Thank you for your help, I understand what you are saying, however my router doesn't provide me with those boxes to fill in the ssl port. I've also tried to put the domain with the :443 appendix but it does not allow me to do so.
The only indication of a box for a port appearing is when I pick a random protocol. I am attempting this with the telnet ask protocol. Is this the right protocol to pick? Or am I choosing wrong?
 
I have tried it now with the https protocol which is displayed with the 443 number here in my rooter, but its still not working it's always saying that its failing to solve the hosts name. Im a bit stumped.

By the way this error is only happening with the https://es.np.adproxy.ndmdhs.com
adress i've been able to enter the others (without specifieing the 443 port) with sucess. Don't know if it will be okay with them like that.
 
Last edited:
I've tried it the other adress with the https protocol, it has worked but still the adproxy one is still giving me problems
 
Back
Top