Editing User talk:Lordv

== CEX2DEX pro versus con discussion ==
Moved discussion thread from [http://www.ps3devwiki.com/wiki/Talk:Flash#CEX2DEX_pro_versus_con flash talk page]

[[user:Euss|Euss]]

=== Lordv ===
# ''Loosing Retail functionality''(You could always just mod a DEX PUP and boom you got dvd,ps store etc)
# ''PSN not possible -> You can't play online''(Hmmmm... LIE)
# ''More Stress to the console (Phats prone to YLOD)'' (Rly???)
# ''You can't play backups (obvious exception of MultiMan 3.55 DEX, having a CFW DEX)'' (Or Knowing how load bdemu)

[[user:Lordv|Lordv]]

=== RUT Dark Ronin ===
Explain your statements step by step. Otherwise, plain troll with BS. This is wiki, not twitter or forum or smth like that. Keep things clear and understandable.

[[user:RUT Dark Ronin|RUT Dark Ronin]]

=== Lordv ===
Instead of having an edit war could we discuss it on irc? I can prove that what you write here are (un?)intentional lies.

1) What do you mean retail functionality? You can restore dvd playback and ps store to name a few by some sprx copying and xml editing. Just unpack a dex fw for 3.55 and a cex fw for 3.55 and note the differences in sprx. Then just add the correct xml keys. For example for ps store add the #seg_commerce_new key to category_psn.xml.

''Answer from [[user:Mathieulh|Mathieulh]] : You can't play blurays/dvds on 3.60+ DEX because you do not have the keys to craft a custom DEX firmware and the bd/dvd player app will check your console's idps target and see 0x82 and will fail one (of too many) check(s) and will issue an error code and not proceed. (not to mention 0x82 leads to an invalid region)
I don't know/care about ps store but as far as I know, the DEX vsh.self will not display it'' 
	
2)I did, however i can't prove it. Should you cex2dex and have latest dex fw you too will be able to sign in to PSN.

''Answer from [[user:Mathieulh|Mathieulh]]: You can't because your idps is NOT in sony's database, as such it will not pass PSN authentication, there is nothing you can do to fake this, you would need to use a real debug idps, end of story.'' 

3) Can't comment on that one but would very much like a statement from whoever wrote it.
	
''Answer from [[user:Mathieulh|Mathieulh]] : This is obviously not true, however you CAN brick/ylod if you rebuild your EID wrong (the likeliness is high)''

4)Do you want a video of it? Use ps3 generator tools to create a master disc or a usb image. Ever wondered what that item labeled Blu-Ray Disc Access in Debug Settings did? Now you can find out.

''Answer from [[user:Mathieulh|Mathieulh]] : The retail selfs are signed with special capabilities that make them only able to run from original discs (Masterdiscs != Original discs, lv2 can tell the difference) That's why you need decrypted selfs/fself to run games from masterdiscs or bdemu images, forget about running your "backups" (or should I say ,warez) Because ps3gen creates masterdiscs does not mean you can magically warez on the box. 
You can however play originals ! (I strongly advise you to start BUYING your games, (just saying))''
	
5)Can't comment on that one.

''Answer from [[user:Mathieulh|Mathieulh]] : I can comment that most of your so called affirmations are a bunch of BS. (in fact I just debunked most of them, feel free to try though and see for yourself.)''

Well First off I said 3.55 for dvd /bd. 
Secondly I was on psn. Give me the 4.20 pup and will gladly make a video of it. 
Thirdly i posted a video of me running my BLES-01275 backup/warez using retail update. 
I do not wish to create drama, if you want pm me on hax forums. 

[[user:Lordv|Lordv]]

=== RUT Dark Ronin ===
join #ps3dev channel and write to DarkRonin, we'll discuss it there.

[[user:RUT Dark Ronin|RUT Dark Ronin]]

=== Proposal split ===
Seeing most discussion is about the /modified/ Debug/DEX firmware (which was never the scope of the Pro/Con), it would be wise to split things up.

[[user:Euss|Euss]]

==== 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 binairy first
|-
| Downgrading || {{Yes}} || {{Yes}} || {{Yes}} || Restricted to minver of that SKU/type (either metldr minver locked, or because of drivers - same limmitations as Retail/CEX, but without hardware flasher)
|-
|}

==== Con ====
{| class="wikitable sortable"
|-
! Function !! 3.55 !! 3.56 !! 3.60+ !! Remarks
|-
| 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 //-->
|-
| Backups : &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 : &gt;=3.60 keyed || {{No}} <br />(same as Retail) || {{No}}<br />(see 3.55) || {{No}} || 
|-
| 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 />(latest is 4.11) || 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}} || 
|-
|}
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).