Editing Talk:IDPS
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
<!--// <mysis> after model type....in short it was right-shift 10d / 0xA //--> | |||
. | |||
=== IDPS rms blogtext === | |||
You’re probably wondering: “What the hell is this sequence of bytes?”. This is the IDPS, a sequence of bytes which determine console type. This structure is relatively undocumented until now, anyway. The IDPS is contained in EID0. EID0 is on the console internal flash as the file eEID and has multiple sections. I had made a splitter application to make your life easier a long time ago. Now, EID is decrypted by metldr, and is passed over to the isolated loader, which may pass it to a self. We can see this in graf_chokolo’s original payload. The IDPS is also used in various other parts of the system which could be of interest to you, but I will not discuss those right now. The IDPS itself, isn’t decrypted. | |||
The IDPS contains your target ID, motherboard? and BD? revision. The IDPS shown at the beginning of this article is the dummy IDPS, the one that’s used when your IDPS fails to be decrypted. That IDPS belongs to a DECR-1000A. The one below belongs to a European PS3, and the one below that belongs to a Australian/NZ PS3. | |||
Source: http://rmscrypt.wordpress.com/2011/05/16/idps-what-the-hell-is-that-thing/ | |||
Note: The Reference Tool IDPS from above is static. aim_iso uses it. Retail/3.55 doesn't have it. | |||
===Change HWID=== | |||
Theory: If you give a slim console a fat IDPS, would that console have 3.15 OtherOS functionality? | |||
I would say it would, because most likely the check is done in firmware to either en/disable that option. However, it would still require a console that can be downgraded to that version (only CECH-20../DYN-001, because CECH-21../SUR-001 use different drivers for RSX). So classic OtherOS on a CellBE 45nm/RSX 40nm would be impossible (ofcourse you can use OtherOS++). | |||
= | === [Homebrew-App] PS3 Model Detection === | ||
http://www.ps3hax.net/2011/01/homebrew-app-ps3-model-detection/ | |||
<pre>Dumping PS3 Model Data: | |||
- PS3 System Target ID: 0x85 (Retail - Europe) | |||
- PS3 Motherboard Revision: 0x0B (JTP-001 Motherboard, Revision 1) | |||
- PS3 BD-Laser Revision: 0x04 (KES-400, SACD supported) | |||
Probable Model: CECH-2504A | |||
Raw Model Data: | |||
Byte 0: 0x00 | |||
Byte 1: 0x01 | |||
Byte 2: 0x00 | |||
Byte 3: 0x85 | |||
Byte 4: 0x00 | |||
Byte 5: 0x0B | |||
Byte 6: 0x00 | |||
Byte 7: 0x04</pre> | |||
'''footnotes:''' | |||
* '7th byte of IDPS' is ''not'' [[Bluray Drive]] (it was misunderstood at that time). You can see it in the example where it names incorrectly a [[CECH-25xx]] as Super Audio CD compatible with a [[KES-400]] laserslide (which in real life has either [[KES-460A]] or [[KES-470A]] without daughterboard (swap can be done without remarry). | |||
* also, it named bytes 0-2 "Byte 0", byte 3 "Byte 1", byte 4 "Byte 2", byte 5 "Byte 3", byte 6 "Byte 4", byte 7 "Byte 5", byte 8 "Byte 6", byte 9 "Byte 7" etc. | |||
=== [Homebrew-App] IDPS Viewer === | |||
http://www.tortuga-cove.com/hacking/31-ps3/8396-released-idps-viewer | |||
* Displays the IDPS | |||
* Shows Target ID | |||
* Displays Motherboard revision | |||
* Save <abbr title="(NAND @ 0x80870 / NOR @ 0x2F070)">IDPS</abbr> (16 bytes from EID) in dev_hdd0/IDPS.bin file |