Editing Talk:Cex2Dex

= External references =
* http://www.ps3hax.net/showthread.php?p=400529#post400529

= CEX2DEX - pro versus con =

== Pro ==
{| class="wikitable sortable"
|-
! Function !! 3.55 !! 3.56 !! 3.60+ !! Remarks
|-
| Using the features of a debug console || {{Yes}} || {{Yes}} || {{Yes}} || To effectively use features, need to use SDK related files, e.g. TargetManager etc
|-
| Using FSELFs || {{Yes}} || {{Yes}} || {{Yes}} || To create fselfs, you must have the decrypted binary first
|-
| Downgrading || {{Yes}} || {{Yes}} || {{Yes}} || Restricted to minver of that SKU/type (either metldr minver locked, or because of drivers - same limitations as Retail/CEX, but without hardware flasher)
|-
|}

== Con ==
{| class="wikitable sortable"
|-
! Function !! 3.55 !! 3.56 !! 3.60+ !! Remarks
|-
| Retail Functionality : Packages || {{No}} <br />(patchable) || {{No}}<br />(see 3.55) || {{No}}<br />(Disabled for that [[Target ID]]) || 
|-
| Retail Functionality : BD-Movies || {{No}} <br />(patchable) || {{No}}<br />(see 3.55) || {{No}}<br />(Disabled for that [[Target ID]]) || 
|-
| Retail Functionality : DVD-Movies || {{No}} <br />(patchable) || {{No}}<br />(see 3.55) || {{No}}<br />(Disabled for that [[Target ID]]) || 
|-
| Retail Functionality : PS Store || {{No}} <br />(patchable) || {{No}}<br />(see 3.55) || {{No}}<br />(Disabled for that [[Target ID]]) || 
|-
| PSN/SEN || {{No}} <br />(only when patched/spoofed to Retail AND passphrase is available) || {{No}}<br />(see 3.55) || {{No}}<br />(Server Whitelisting and nondebug IDPS fail) || 
|-
| More Stress to the console || {{Yes}} || {{Yes}} || {{Yes}} || Using TargetManager/Debugger increases memoryload, also heats up RSX more (there are known CECHA/CECHC that gotten YLOD after few weeks of usage, and behaved normally when converted back to Retail/CEX)
<!--// note: this was originally seen as urban legend, but factual real world proved otherwise. bottomline: calculated risk. 
COUNTERPRODUCTIVE EDIT WARRING: to people persistantly editing this away, please provide realworld data, not your basic 'it happens to all FAT' (this mention is about the _added_ risk, not the basic riskfactor that is common for all all 90nm RSX), as that does _not_ explain why consoles that are converted back work normaly //-->
|-
| Backups (via Manager) : &lt;=3.56 keyed || {{Yes}}<br />(same as Retail, would need lv1.self : mmap114 and lv2.self : peek/poke patches + Manager with DEX detection/payload) || {{Yes}}<br />(see 3.55) || {{No}} || 
|-
| Backups (via Manager) : &gt;=3.60 keyed || {{No}}<br />(same as Retail) || {{No}}<br />(see 3.55) || {{No}} || 
|-
| Backups (using ps3gen/bdemu) : &lt;=3.56 keyed || {{Yes}} || {{Yes}}<br />(see 3.55) || ? {{Yes}}  || 
|-
| Backups (using ps3gen/bdemu) : &gt;=3.60 keyed || {{No}} || {{No}} || {{Yes}} || 
|-
| OtherOS++ : Linux/BSD || {{Yes}} <br />(same as Retail, need patches) || {{No}}<br />(No one ported OtherOS++ MFW tasks to 3.56 yet, if someone does, see 3.55) || {{No}} || 
|-
| Firmware availability || {{Yes}} || {{Yes}} || {{No}}<br />(leaks always will lag behind) || Getting firmwares will always be a handicap, as they are not openly distributed/announced like Retail, only on SCEDevnet
|-
| Easily detectable and banned || {{Yes}} || {{Yes}} || {{Yes}} || 
|-
| HDCP off || {{No}} || {{No}} || {{No}} || Hardware limitations in the HDMI out chip (OTP ?) prevent from switching hdcp off even by forcing the setting <small>(see note below)</small>, HDCP would then appear off in the system settings but would actually still be on
<small>Note:<br />
Can use [http://www.ps3devwiki.com/wiki/QA_Flagging#Debug_Menu_settings_not_in_Retail.2FCEX_QA QA debug] (&lt;=3.56) or setmonitor.self (ProDG Target Manager - Monitor Settings Utility). See also [http://www.ps3devwiki.com/wiki/XRegistry.sys XRegistry.sys /setting/display/0/hdcp] to enforce it to "off" setting.</small>

|-
| Burned Master Discs || {{No}} || {{No}} || {{No}} || Hardware limitations in the Drive Id's (OTP not set to 0xFFFFFFFFFFFFFFFF) prevent from using burned ps3 and ps2 masterdiscs (they are recognized as data discs), this is a check performed by the drive's firmware.
|-
|}
Note about 3.56 : would need to use custom generated keys for signing, as the random fail is fixed since that version, thus no private keys can be acquired with Scekrit).

= Alternative method of writing back flash  (jaicrab / bad idea) =
Put these, including your target NOR file, named rflash.bin on a stick
 https://dl.dropbox.com/u/35197530/Lv2diag.self
 https://dl.dropbox.com/u/35197530/advance.cfg
Either use PSgrade/JIG and let the lv2diag.self be executed by lv1.self automaticly, or use MultiMAN self loader<br />
Will take a LONG time (35 minutes) until console stops blinking and shutdown with red led.

Tested working on CECHG fat(256mb nand), I suspect the reason for people bricking was they were flashing dumps of different lenghts and offsets(such as from memdump) and not the one provided by dumping with this -sk1080


----
= Cex2Dex NOR Guide =

==Prerequisites==
* [http://www.ps3devwiki.com/files/devtools/dumpers/memdump_0.01-FINAL/memdump_0.01-FINAL/memdump_0.01-FINAL.gnpdrm.pkg Memdump v 0.01]
* [http://www.ps3devwiki.com/files/devtools/Cex2Dex/eEID_RKDumper/eEID_RKDumper.pkg eEID_RKDumper]
* [http://store.brewology.com/get/homebrew.php?id=24&fid=385 Multiman] or MMOS anything above 4.0.3 will work

==NOR guide==
# Put above mentioned 3 packages in root of USB stick and install them on the PS3 using *Install Packages*
# With the USB stick still inserted, run Memdump v 0.01 and select the option "Dump Flash Storage"
# Run eEID_RKDumper. It should give 5-10 seconds black screen, beep and shutdown the console.
# Reboot the console, start MultiMan and use the filemanager to navigate to /dev_hdd0/tmp/eid_root_key and copy this file to the root of your USB stick.
# Now you should have the PCK1 (eid_root_key) and complete flash dump (flash_stor_35500.bin) of that console. Backup these 2 files for safe keeping/debricking. If you have multiple consoles, mark them as needed (e.g. serial from white sticker) to avoid confusion.

<!--// 7. download Cex2Dex.exe and place it on your desktop load the flash_stor_35500.bin for the top and rename eid_root_key to dump and load that for the bottom, next click on cex to dex.
8. If all went to plan then it will ask you to save your converted flash as my-DEX-flash.EID0.NORBIN
9. place that file on your usb (I suggest removing other files to avoid accidental flash) so you have my-DEX-flash.EID0.NORBIN on the usb.
10.Open multiman file manager and locate the my-DEX-flash.EID0.NORBIN on your usb and click it it will go through 3 pages of verification just press x on each page
Note: you must start Multiman in debug mode by holding the triggers as you start or restart MM and then update MM. Running the NORBIN file now brings up the prompts about overwriting your flash and not the HEX viewer
11. Reboot ps3, and you will be able to install any Dex Firmware //-->

= conversion diff =
 
 Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
     
 0002F070  <span style="background-color:white; color:green;">00 00 00 XX 00</span> <span style="background-color:white; color:red;">XX</span> <span style="background-color:white; color:green;">00 XX XX XX XX XX XX XX XX XX</span>
 0002F080  <span style="background-color:white; color:green;">00 XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX</span>
 0002F090  <span style="background-color:white; color:red;">XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX</span>
 0002F0A0  <span style="background-color:white; color:red;">XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX</span>
 0002F0B0  <span style="background-color:white; color:red;">XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX</span>
 0002F0C0  <span style="background-color:white; color:red;">XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX</span>
 0002F0D0  <span style="background-color:white; color:red;">XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX</span>
 0002F0E0  <span style="background-color:white; color:red;">XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX</span>
 0002F0F0  <span style="background-color:white; color:red;">XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX</span>
 0002F100  <span style="background-color:white; color:red;">XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX</span>
 0002F110  <span style="background-color:white; color:red;">XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX</span>
 0002F120  <span style="background-color:white; color:red;">XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX</span>
 0002F130  <span style="background-color:white; color:red;">XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX</span>
 0002F140  <span style="background-color:white; color:red;">XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX</span>


----


= EID correctness =

   [8/31/2011 1:41:13 AM] xxxxxxxxxxxxxx: the information on the PS3 dev wiki was intentionally faulty
   [8/31/2011 1:41:15 AM] qqqqq: Use the creativity or fail to find it.
 [...]
   [8/31/2011 1:41:34 AM] xxxxxxxxxxxxxx: so people can't use the 'knowledge'
 [...]
   [8/31/2011 1:41:43 AM] qqqqq: xxxxxx, uuuu has done a very good job at fixing what IS wrong. If you saw something wrong, why didn't you ask uuuu about it to fix it?
   [8/31/2011 1:41:55 AM] xxxxxxxxxxxxxx: that's not what guys like rrrrrrr have told me
   [8/31/2011 1:41:58 AM] xxxxxxxxxxxxxx: it's intentionally faulty
   [8/31/2011 1:42:03 AM] qqqqq: Instead you left it  how it was and bitched about it.
   [8/31/2011 1:42:07 AM] xxxxxxxxxxxxxx: to prevent any meaningful extraction of keys
   [8/31/2011 1:42:11 AM] qqqqq: If it was fault again talk to uuuu
   [8/31/2011 1:42:24 AM] xxxxxxxxxxxxxx: no - uuuu could not have even known about it
   [8/31/2011 1:42:28 AM] xxxxxxxxxxxxxx: it was something only a kkkk could know
   [8/31/2011 1:42:45 AM] qqqqq: You'd be surprised what uuuu knows. he really is a walking encyclopedia of the ps3.
   [8/31/2011 1:42:48 AM] xxxxxxxxxxxxxx: that wiki is compromised with purposeful misinformation
   [8/31/2011 1:42:59 AM] xxxxxxxxxxxxxx: and that's what rrrrrrr actually said and thinks
   [8/31/2011 1:43:17 AM] xxxxxxxxxxxxxx: I'm talking about ps3 dev wiki BTW here
   [8/31/2011 1:43:25 AM] qqqqq: if it's providing false info, then why not make a site to provide the right info? *gasps*
   [8/31/2011 1:43:34 AM] xxxxxxxxxxxxxx: well he did make the suggestion
   [8/31/2011 1:43:38 AM] xxxxxxxxxxxxxx: but it didn't go over well with these people
   [8/31/2011 1:43:45 AM] yyyyyyyy: kkkk wasn't the only one with cex-dex shit
   [8/31/2011 1:43:50 AM] yyyyyyyy: hell he's not even the one who wrote it
   [8/31/2011 1:44:01 AM] yyyyyyyy: so you can stfu about that
   [8/31/2011 1:44:09 AM] xxxxxxxxxxxxxx: hell do I know who the fuck wrote CEX-DEX
   [8/31/2011 1:44:27 AM] xxxxxxxxxxxxxx: all I know is that there are a bunch of connivant shits that want a wiki intentionally 'disinfoed' like that
   [8/31/2011 1:44:35 AM] xxxxxxxxxxxxxx: people in the know
   [8/31/2011 1:44:49 AM] yyyyyyyy: and one conniving shit here trying to save his hide
   [8/31/2011 1:44:57 AM] qqqqq: xxxxxx, again as i said. If there was false info (Which uuuu would never do) Why not fix it
   [8/31/2011 1:45:21 AM] xxxxxxxxxxxxxx: go ask rrrrrrr - I dunno
   [8/31/2011 1:45:26 AM] qqqqq: DO you think he purposesly makes changes so that it's wrong? That'd create an even bigger headache if a noob attempted it and bugged us in the chat
   [8/31/2011 1:45:32 AM] xxxxxxxxxxxxxx: the EID/CEX-DEX info was incomplete
   [8/31/2011 1:45:33 AM] xxxxxxxxxxxxxx: faulty


----

= Trophy errors =
If you are getting trophy errors preventing you to play backups then make sure you perform the following steps:
# Go to recovery menu and restore default settings.
# Rebuild ps3 database from recovery menu.
# If you had a playstation id then add the playstation id/password in the playstation network settings. Try to connect once, it will ask you to upgrade your console. DONOT upgrade! Keep the playstation id/password saved in the psn settings.

----

= Trivia =

Neither the [http://ps3devwiki.com/wiki/SC_EEPROM#EEPROM_Offset_Table_-_Flags_and_Tokens FSELF Control Flag] nor the [http://ps3devwiki.com/wiki/SC_EEPROM#EEPROM_Offset_Table_-_Flags_and_Tokens Debug Support Flag] is changed, nevertheless, no functions of the DEX firmware are restricted, it behaves like a original one. Sony could just add checks in the upcoming DEX firmwares and patch this CEX -> DEX conversion method. Also this isn't a full cex-dex conversion, seeing as only the IDPS is changed only in EID0 and not also in EID5.

= DEX2CEX safe way / debricking =
<ol><li>take that console DEX dump and convert it to the [[Target ID]] of that CEX console region (with targetID changer and that console eidrootkey)<br />
&nbsp; ''or'' <br />
take that console CEX dump.</li></ol>

the next steps are same as [http://www.ps3devwiki.com/wiki/Downgrading_with_Hardware_flasher#Patch_the_dump_.26_Reflash_it_to_the_console Downgrading with Hardware flasher], see there for more in depth information.

# make sure byteorder is correct, if needed use Flowrebuilder to bytereverse
# take Rogero NOR patcher or Flowrebuilder+downgraderpatches and prepatch that CEX converted dump with downgrader. Flash it.
# use Recover or Factory Service Mode to install Rogero 3.55 V7 PUP (the basic downgrader that is always used to downgrade consoles)
# on install success, activate QA and do buttoncombo to check QA-debug menu comes up. then goto Recovery and install OFW 3.55 CEX /twice/ in a row, to make sure both banks are dehashed


An Italian indepth guide : http://www.nextrl.it/forum/topic/86174-guida-downgrade-e-%E2%80%9Cdex-to-cex%E2%80%9D