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

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

Release Setup Instructions / Support

• 
  SEN Enabler UPDATE
  UPDATE (October 17) Improvements v6.1.0
  
  • Added support for CFW 4.83 Cobra
  • Added support for XMB modes in 4.83 CFW
  Improvements v6.0.9
  
  • Spoof to 4.83 (Online works again)
  • Added support for CFW 4.83 CEX/DEX (Not tested, there is no CFW 4.83 atm)
  • Updated Cobra data for Rebug 4.82 CEX/DEX
  • Updated SEN Plugin to v3.1
  • Fixed issue if plugins folder doesn't exist while installing plugin
  
  Remember to use Charles Proxy now along with SEN Enabler and block three URLs (you can add more if you want), this software will minimize ban risk, but a ban is not 100% avoided on CFW
  Block all these URLs on Charles or similar:
  
  • https://es.np.adproxy.ndmdhs.com:443 (Maybe you need to change "es" to your region, "us", etc...)
  • https://nsx.sec.np.dl.playstation.net:443
  • http://xmb-e.dl.playstation.net
  
  
• 
  See the official release thread:
  http://www.psx-place.com/threads/sen-enabler-tutorial-latest-releases.147/
  
  

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​

 

They did change QA toggle in 3.55.
Until 3.55, QA could be toggled using an official syscall (an update manager interface syscall iirc), any app could toggle QA.
Since 3.55, the syscall cannot be used for this purpose anymore. QA toggling from then on required a hack.
The kernel protection must first be be breached for devs to toggle QA on 4.xx fw. On CFW, that's obviously not a problem & QA toggle can be achieved using a lv1 function after patching the kernel memory appropriately.

And because the QA Flag code of 3.55 is featured in all CFWs it's impossible to install CFW on Super slims,and any console that isn't supported on 3.55
If you remove the 3.55 code and flash with a hardware flasher a CFW without the the 3.55 code in theory that CFW will work on any console.

 

Can you? I thought the QA flagging we had was fake, because they changed it around 3.55 time.

It's the same old QA flag from 3.55,and that's why you can't install CFW on super slims...

 

And because the QA Flag code of 3.55 is featured in all CFWs it's impossible to install CFW on Super slims,and any console that isn't supported on 3.55
If you remove the 3.55 code and flash with a hardware flasher a CFW without the the 3.55 code in theory that CFW will work on any console.

No. It doesn't work like that, QA toggle is not a jailbreak.

The reason you cannot install a CFW on super slim has nothing to do with QA & CFWs do not include any "3.55 QA code".
The cause is the new loaders, that form the chain of trust, will not allow execution of any binary signed with a different key from the official private key that is expected.
Up to 3.55, s#ny made the mistake of considerably weakening their key system by using a constant instead of a random number in their key algorithm.
So the private keys could be calculated & used to resign modified firmware binaries which could then be loaded at boot time as if they were official.
That mistake was corrected with 3.55 & private keys can still be calculated but they can no longer be derived in a reasonable amount of time anymore ie it could take decades to get just one key.

Being able to toggle QA on super slim would give us new capabilities we could use to downgrade the firmware, have access to older known kernel exploits, get some homebrew running without exploiting the kernel & possibly much more but it would not allow to directly install CFW on superslim.

 

No. It doesn't work like that, QA toggle is not a jailbreak.

The reason you cannot install a CFW on super slim has nothing to do with QA & CFWs do not include any "3.55 QA code".
The cause is the new loaders, that form the chain of trust, will not allow execution of any binary signed with a different key from the official private key that is expected.
Up to 3.55, s#ny made the mistake of considerably weakening their key system by using a constant instead of a random number in their key algorithm.
So the private keys could be calculated & used to resign modified firmware binaries which could then be loaded at boot time as if they were official.
That mistake was corrected with 3.55 & private keys can still be calculated but they can no longer be derived in a reasonable amount of time anymore ie it could take decades to get just one key.

Being able to toggle QA on super slim would give us new capabilities we could use to downgrade the firmware, have access to older known kernel exploits, get some homebrew running without exploiting the kernel & possibly much more but it would not allow to directly install CFW on superslim.

Thanks for correcting me,
And that is a case where i thought i knew what i was talking about but someone with better knowledge came and corrected me,
I should never again write what i think that i know like it;s a fact,
I will only write what i know in 100% that is true,
Sorry for the inaccuracy.

Like Stephen Hawking said "The greatest enemy of knowledge is not ignorance; it is the illusion of knowledge. "

Do not worry,in the rest of my posts i knew what i was talking about,
At least we all learned something out of it,especially me.

Sorry again.

(I am a hardware guy,i have ways to go before i will match my hardware knowledge with software)

 

Thanks for correcting me,
And that is a case where i thought i knew what i was talking about but someone with better knowledge came and corrected me,
I should never again write what i think that i know like it;s a fact,
I will only write what i know in 100% that is true,
Sorry for the inaccuracy.

Like Stephen Hawking said "The greatest enemy of knowledge is not ignorance; it is the illusion of knowledge. "

Do not worry,in the rest of my posts i knew what i was talking about,
At least we all learned something out of it,especially me.

Sorry again.

No harm done, don't worry about it.
Everybody can make a mistake or be wrong about something. I am no exception & most likely not any better than you might be in that department.

 

No harm done, don't worry about it.
Everybody can make a mistake or be wrong about something. I am no exception & most likely not any better than you might be in that department.

Thank you for your kind words
I am a hardware guy,i have ways to go before i will match my hardware knowledge with software
and i added this line in an edit in my pervious post.

 

Thanks for correcting me,
And that is a case where i thought i knew what i was talking about but someone with better knowledge came and corrected me,
I should never again write what i think that i know like it;s a fact,
I will only write what i know in 100% that is true,
Sorry for the inaccuracy.

Like Stephen Hawking said "The greatest enemy of knowledge is not ignorance; it is the illusion of knowledge. "

Do not worry,in the rest of my posts i knew what i was talking about,
At least we all learned something out of it,especially me.

Sorry again.

Don't let being wrong about something stop you. Sharing knowledge is what this is all about.
Like you said you learned something new so I see that as a win

If you are interested in learning all you can about the ps3 the psdevwiki is a amazing place, I still learn something new about every time I visit it.

 

The QA flag we have is real,That's how i downgraded from 4.82 to 4.81

According to psdevwiki QA flagging from 3.60 onwards should only work if you have patches installed as we don't have the signing keys to sign an official QA token.

http://www.psdevwiki.com/ps3/QA_Flagging#On_3.6x_Firmwares

If you install 4.83 OFW then you won't have those patches. Once ps3xploit works again then you could install the patches and downgrade, but right now you would need a hard mod to install them.

But the ps3 does keep two copies of recovery mode, so if you don't overwrite both then you might still have the patches there & be able to boot into recovery mode to downgrade.

 

According to psdevwiki QA flagging from 3.60 onwards should only work if you have patches installed as we don't have the signing keys to sign an official QA token.

http://www.psdevwiki.com/ps3/QA_Flagging#On_3.6x_Firmwares

If you install 4.83 OFW then you won't have those patches. Once ps3xploit works again then you could install the patches and downgrade, but right now you would need a hard mod to install them.

But the ps3 does keep two copies of recovery mode, so if you don't overwrite both then you might still have the patches there & be able to boot into recovery mode to downgrade.

1. Once ps3xploit works again on 4.83, he still won't be able to toggle QA. I thought I was clear about this in my post.
The kernel memory needs to be patched for QA to be toggled & ps3xploit isn't a kernel exploit so it doesn't allow the kernel memory to be patched.
QA will not be toggled on 4.8x OFW until a kernel exploit comes along.

2. I don't know what you mean by a hardware mod, but it would not help either for the same reason, binaries cannot be modified & a hardware mod would still need to exploit the kernel before lv2 memory space could be patched.

3. The recovery executable has nothing to do with the matter, it does not get patched so there is no point in trying to recover a copy of the file.

 

@Evilnat don't know how creditable if use was right.

seen a report that this version Sen Enabler was not working on Ferrox 4.83.
Anyone else confirm if this is working on 4.83 cfw

 

@Evilnat don't know how creditable if use was right.

seen a report that this version Sen Enabler was not working on Ferrox 4.83.
Anyone else confirm if this is working on 4.83 cfw

XMB modes doesn't work on CFW 4.83, i'm adding support right now. Other functions worked fine on my PS3 on Ferrox 4.83...

I will check it out, thanks @STLcardsWS

 

Good day everyone. I need help running Sen enabler v6.0.7 [4.82] on my system 4.82. I'm having trouble creating a secondary psn account, keeps on showing a message to update to version 4.83. I want to bypass the update message and create a secondary account. Please help, I've tried every tutorial ive came by. I'm new to this forum & ps3 jailbreak scene, I'd appreciate it if someone pointed my to the correct direction. Thanx in advance.

 

Good day everyone. I need help running Sen enabler v6.0.7 [4.82] on my system 4.82. I'm having trouble creating a secondary psn account, keeps on showing a message to update to version 4.83. I want to bypass the update message and create a secondary account. Please help, I've tried every tutorial ive came by. I'm new to this forum & ps3 jailbreak scene, I'd appreciate it if someone pointed my to the correct direction. Thanx in advance.

Hi @Pacson, try to reinstall your CFW from Recovery Menu, install SEN Enabler v6.1.0 and spoof to 4.83. After spoof check if you are on 4.83 through System Information, then try to log in on SEN

 

Hi @Pacson, try to reinstall your CFW from Recovery Menu, install SEN Enabler v6.1.0 and spoof to 4.83. After spoof check if you are on 4.83 through System Information, then try to log in on SEN

Will do. Thank you @Evilnat. I'll keep you posted on any progress.

 

I use one of my cfw ps3 for absolutely nothing but play online. Use only psn games, no hacks, no mods, no games in iso format. After the update I use the sen to spoof to 4.83. I use only rebug. Got ban. What have I do to get busted?

 

i have doubts i use Ferrox Cobra 4.82 and i wanted to know how to use it well. Bcuz i was used to use PSNpatch for online gaming but what happens is that any homebrew was working except mmcm.. but the problem with mmCM is that it booted but the start icon appears and it crashed after that. and didnt had a chance to boot other games. so i had to fomat my ps3. any help would be appreciated. Thanks

 

i have doubts i use Ferrox Cobra 4.82 and i wanted to know how to use it well. Bcuz i was used to use PSNpatch for online gaming but what happens is that any homebrew was working except mmcm.. but the problem with mmCM is that it booted but the start icon appears and it crashed after that. and didnt had a chance to boot other games. so i had to fomat my ps3. any help would be appreciated. Thanks

why not update to ferrox 4.83? I haven't tested mmcm with it, but wmm works without issue. it's just as @aldostools said: it (wmm) does display the wrong firmware version (think it shows 4.75), but it works.

 

Hi there
after installing and applying sen enabler on rebug 4.82 , ps2 games cant be started by webman !

 

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.

 

Files are not per user, is safe to send/post them.