[JustThatDude]

ok so today i started reading the Ps3devwiki and it had said:

''I have traced the Cinavia DRM checks to 4 separate sprx files and after a long time trying to patch these files I have found that 3 of those files are present in the DEBUG (DEX) firmware don’t have the Cinavia DRM checks enabled. Files are videoplayer_util sprx, videoplayer_plugin sprx and videoeditor_plugin sprx. I have successfully copied these 3 sprx files from DEBUG (DEX) FW 341 over to my retail PS3 unit running OFW 341 using dev_blind and Cinavia seems to be now disabled. I’ve confirmed this by playing back a number of Cinavia affected video files. This means that Cinavia is now disabled for all DLNA playback and copying, but Cinavia checks on AVCHD and BD playback are still present with Message Code 3 that mutes the audio as the sprx file with the Cinavia check bdp_plugin sprx is not present in DEX firmware because BD playback is disabled in DEBUG. If someone is able to patch Cinavia out of bdp_plugin sprx this will be solved too. I have created a new task for PS3MFW so this can be easily made part of any new MFW’s as needed. Any FW version that has had the DEX firmware leaked should be able to be used to create a CFW of the same version. eg DEX 3.41 -> MFW 341 or DEX 355 -> MFW 355 etc etc. Don’t use sprx files from different FW versions! See git hacks for change_cinavia_files task source.

So basicly what this says that if we have a Dex Fw Say 4.11 then we can create a CFW for 4.11. Correct me if im wrong but if this is true wouldn't it be easier to find and exploit for a new CFW this way.
Source:
http://bit.ly/L2qjMj

[DEFAULTDNB]

When it says CFW it means modified/customised firmware, not CFW as in backup playing homebrew running all singing all dancing update to 3.55CFW.

The cinavia files can be unpacked from the dev flash afaik, so they are easily replaceable with modded ones.

I'm sure deeper customisation has been looked into (probably team acid) or who ever added the package files options to 4.11 mfw, but I dont think it's useful .... yet.

[JustThatDude]

Originally Posted by DEFAULTDNB When it says CFW it means modified/customised firmware, not CFW as in backup playing homebrew running all singing all dancing update to 3.55CFW. The cinavia files can be unpacked from the dev flash afaik, so they are easily replaceable with modded ones. I'm sure deeper customisation has been looked into (probably team acid) or who ever added the package files options to 4.11 mfw, but I dont think it's useful .... yet.

Ok so what you are saying is that the CFW we would be able to make would be just a CFW that has the " install package files" option but can't actually install package files that aren't signed due to the missing keys? So basicly what your saying is the only thing we would be able to tamper with is the way the xmb looks? Also why couldn't we make a new FSM FW so we can downgrade because back then we had those dongles and they did the trick of putting us in FSM.

[DEFAULTDNB]

Yep. Without keys, there is no CFW as most people would like it.

AFAIK FSM mode requires alternate method to enter/exit after 3.60+. LV2diag wont work probably due to how its signed (with old/revoked keys (?) )

[JustThatDude]

Originally Posted by DEFAULTDNB Yep. Without keys, there is no CFW as most people would like it. AFAIK FSM mode requires alternate method to enter/exit after 3.60+. LVdiag wont work probably due to how its signed (with old/revoked keys (?) )

Okay do you know any good information about FSM maybe a link cause i would like to read up on it now and i don't really know how to navigate on the Ps3devwiki

[DEFAULTDNB]

Did you try searching?

http://www.ps3devwiki.com/index.php?...ice+mode&go=Go

void process_utils::create_initial_system_process(). Called to start the first userspace process, which is normally "sys_init_osd.self" but it can also launch recovery mode or update mode.

http://www.ps3devwiki.com/wiki/SIG_File_Format

PS3LV2DIAG The functions available with this object will likely vary with the LV2DIAG used. Open WaitEvent ReadAscii WriteRead Close GetScErrLog UpdateSYSCON (Unleaked .SIG file in combination with a modified downgrade lv2diag)

I'm not sure if thats useful, but it sounds like a good place to start?

@euss is the wiki master, and I think @CrashSerious might be the man to ask about FSM

[JustThatDude]

Originally Posted by DEFAULTDNB Yep. Without keys, there is no CFW as most people would like it. AFAIK FSM mode requires alternate method to enter/exit after 3.60+. LV2diag wont work probably due to how its signed (with old/revoked keys (?) )

Also any idea on how to run a script on the ps3 like i said i just started reading the Ps3devwiki

[DEFAULTDNB]

No idea about PS3 scripts sorry

[JustThatDude]

Originally Posted by DEFAULTDNB No idea about PS3 scripts sorry

It's okay but you think that FSM could be hidden in CORE_OS_PACKAGE.pkg because i couldn't find the ps3dm_usb_dongle_auth.sh. It says that FSM is in the /PS3UPDAT.PUP on this wiki(2nd one from the bottom): bit.ly/K1Dg7J
Also found this on the wiki:

usb_dongle_auth.sh This script will get you into Factory/Service mode, without using dongle: echo Generating a challenge ps3dm_usb_dongle_auth /dev/ps3dmproxy gen_challenge echo Generating a response '(0xAAAA)' ps3dm_usb_dongle_auth /dev/ps3dmproxy gen_resp 0xAAAA echo Verifying response '(0xAAAA)' ps3dm_usb_dongle_auth /dev/ps3dmproxy verify_resp 0xAAAA echo Checking if 'Product Mode is enabled The returned value shouldn't be 0xff ps3dm_um /dev/ps3dmproxy read_eprom 0x48C07

Source:
http://bit.ly/JxUxG1

[DEFAULTDNB]

The dongle masterkey generator hasnt worked since 3.55. I believe it was patched out by sony in 3.56+ rendering current dongles useless.

I looked into this a while back.