Editing VTRM

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

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:
The PS4 VTRM functionality seems to be similar with the one of the PS3. We can either dump it via HW or via SW method. Tools to unpack and dump the VTRM can be found here [http://www.psdevwiki.com/ps4/Flash-Main Tool] on the Top, under sources.
The PS4s VTRM functionality seems to be similar with the one from the PS3. We can either Dump them via HW or via Software methode. Tools to unpack and dump the VTRM can be found here [http://www.psdevwiki.com/ps4/Flash-Main Tool] on the Top, under sources.


On the PS4 a Dev/Test units only have one Region whilst a Retail unit has two Regions. One of those regions is used for deactivation and the other one for activation.
On the PS4 a Dev unit only hase one Region where a Retail unit will have two Regions. One of thoes regions will be used for deactivation and the other one for activation.


=== Region0 ===
=== Region0 ===
SCEVTRM Magic on 0x380048.
SCEVTRM Magic on 0x380048.


Line 17: Line 16:
or
or


If VTRM0 is marked as in use then the console is deactivated and if VTRM1 is marked as in use then PS4 is activated.
If VTRM0 is marked as in use then the console is deactivated and if VTRM1 is marked in use then PS4 is activated.


Following some examples. Remember mark 0xFC and count 0x00 == factory state.
Following some examples. Remember mark 0xFC and count 0x00 == factory state.
Line 54: Line 53:
|}
|}


So we have more ways to identify if a dump is from a Retail or a Dev/Test console. Either we can check if there are any incremental counters used on the VTRM or we can check if the VTRM has any mark like 0xFC or 0x00000000 or 0x03000000 then it is a Retail else Dev/Test. Or we also can check the first 4 bytes of both VTRMs against 4x 0xFF bytes, if true == Dev/Test else Retail.
So we have more ways to identify if a Dump is from a Retail or a Dev/Test console. Either we can check if there are any incremental counters used on the VTRM or we can check if the VTRM hase any mark like 0xFC or 0x00000000 or 0x03000000 then it is reatail else Dev/test. Or we also can check the first 4 bytes of both VTRMs against 4x 0xFF bytes, if True == Dev/Test else Retail.


NOTE: Dev/Test Consoles only do use one VTRM. The array for the second VTRM is completely empty on this SKU models beside that they don't have any mark and also no counter. (yea sure why if they only use one ^^)
NOTE: Dev / Test Consoles only do use one VTRM. The array for the second VTRM is completely empty on this SKU models beside that they don't have any mark and also no counter. (yea sure why if they only use one ^^)


NOTE²: There is another byte that will change during this process. On offset 0x3A0078 for factory the byte is 0xFF. As soon as the console would be the first time activated (so count 0x01) then this byte change to 0xFE. After this (so count 0x02 and upwards) the byte will always be 0xFC.
NOTE²: There is another byte that will change douring this process. On offset 0x3A0078 for factory the byte is 0xFF. As soon the console would be the first time activated (so count 0x01) then this byte change to 0xFE. After this (so count 0x02 and upwards) the byte will always be 0xFC.


=== Region0 Digest? ===
=== Region0 Digest? ===
 
This region of 0x60 ~= 96 bytes is the exact same on the same console of diffrent FW and BIOS versions. We can use thoes 96 bytes to identify dumps as diffrent or as from one and the same device. It's kind of a unique Console identifyer. I will add a new entry to the SystemFlash Extractor and hash this array with SHA1 which we then can use to store it in the DataBase. That gives us the ability to even identify a Dump and his informations from the DataBase out as one and the same device or as a diffrent one, while to same time to protect the privacy of the user in case we use a checksum to store and not the console specific unique vlaue.
This region of 0x60 bytes is the exact same on the same console of different FW and BIOS versions. We can use those 0x60 bytes to identify dumps as different or as from one and the same device. It's kind of a unique console identifier. I will add a new entry to the SystemFlash Extractor and hash this array with SHA1 which we then can use to store it in the DataBase. That gives us the ability to even identify a dump and its informations from the DataBase out as one and the same device or as a different one, while at same time to protect the privacy of the user in case we use a checksum to store and not the console specific unique value.
 
'''(From a already dead console)'''
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00380170                          BE AF 32 B6 91 8A CF 6B          ¾¯2¶‘ŠÏk
00380180  87 67 90 C3 93 8B 71 A5 02 7D 24 B3 BA E3 C1 1F  ‡g.Ó‹q¥.}$³ºãÁ.  "
00380190  50 18 52 A2 70 B8 21 E7 C0 7E 2C CF B9 B5 19 BF  P.R¢p¸!çÀ~,Ϲµ.¿  "
003801A0  79 33 BA CF 8D 50 3D 03 32 BD 8A 25 00 DA A5 2B  y3ºÏ.P=.2½Š%.Ú¥+  "
003801B0  4B 1E 27 27 96 07 87 52 7F DD 05 ED A5 DA 51 C8  K.''–.‡R.Ý.í¥ÚQÈ    "
003801C0  AB F6 48 B9 08 FF CF 89 83 B2 76 37 51 75 8D 87  «öH¹.ÿωƒ²v7Qu.‡  "
003801D0  F8 A1 06 69 F7 73 58 36                          ø¡.i÷sX6          "
 
=== Region0 UserRegion ===


=== Region1 ===
=== Region1 ===
SCEVTRM Magic on 0x3A0048
SCEVTRM Magic on 0x3A0048


Line 139: Line 124:


=== Region1 Digest? ===
=== Region1 Digest? ===
 
The same like for Region0 applys here but with the diffrence that thoes both digest? from Region0 and Region1 do differ on the same console and also on diffrent versions. But Region0 do match Region0 of diffrent FW and BIOS versions and the same apply for Region1. Thoes 96 bytes from Region1 are always the same on diffrent FW and BIOS versions of the same console.
The same like for Region0 applies here but with the difference that those both digest? from Region0 and Region1 do differ on the same console and also on different versions. But Region0 do match Region0 of different FW and BIOS versions and the same applies for Region1. Those 0x60 bytes from Region1 are always the same on different FW and BIOS versions of the same console.
 
=== Region1 UserRegion ===


== Structure ==
== Structure ==
==== Header ====
==== Header ====
 
- size always 96 bytes
* size is always 0x80 bytes
* integer values are endian swapped


{| class="wikitable"
{| class="wikitable"
Line 155: Line 134:
! From !! To !! Description
! From !! To !! Description
|-
|-
| 00 || 03 || '''Flag''' Marks the VTRM status. Factory state = 0xFC (1 byte). Activation state = 0x03000000. Deactivation state = 0x00000000.
| 00 || 03 || '''Flag''' Marks the VTRM status
|-
|-
| 04 || 3F || '''Padding0''' Nothing only 0xFF bytes.
| 04 || 3F || '''Padding0''' Nothing only 0xFF bytes
|-
|-
| 40 || 43 || '''Constant''' always 0x01000000.
| 40 || 43 || '''Constant''' always 0x01000000
|-
|-
| 44 || 47 || '''Padding1''' Nothing always 0xFF bytes.
| 44 || 47 || '''Padding1''' Nothing always 0xFF bytes
|-
|-
| 48 || 4F || '''Magic''' The VTRM Magic.
| 48 || 4F || '''Magic''' The VTRM Magic
|-
|-
| 50 || 53 || '''Count0''' The activation / deactivation count.
| 50 || 53 || '''Count0''' The activation count
|-
|-
| 54 || 57 || '''Padding2''' Nothing always 0x00 bytes.
| 54 || 57 || '''Padding2''' Nothing always 0x00 bytes
|-
|-
| 58 || 5B || '''Count1''' The control byte for the activation / deactivation count. It need to be the same like '''Count0'''.
| 58 || 5B || '''Count1''' The control byte for the activation count
|-
|-
| 5C || 5F || '''Padding3''' Nothing always 0x00 bytes.
| 5C || 5F || '''Padding3''' Nothing always 0x00 bytes
|-
|-
| 60 || 6F || '''Ukn''' Unknowen always the same 16 bytes.
| 60 || 6F || '''Ukn''' Unknowen always the same 16 bytes
|-
|-
| 70 || 76 || '''Padding4''' Nothing always 0xFF bytes.
| 70 || 76 || '''Padding4''' Nothing always 0xFF bytes
|-
|-
| 77 || 77 || '''Ctrlflag''' Tigthen with the '''Flag''' variable. Factory state = 0xFF. First activation state = 0xFE. Else it will be always state = 0xFC.
| 77 || 77 || '''Ctrlflag''' Tigthen with the '''Flag''' variable
|-
|-
| 78 || 7F || '''Padding5''' Nothing always 0xFF bytes.
| 78 || 7F || '''Padding5''' Nothing always 0xFF bytes
|}
|}


Line 201: Line 180:
  } vtrmHeader;
  } vtrmHeader;
</source>
</source>


'''CSharp'''
'''CSharp'''
Line 224: Line 204:


== Function Calls ==
== Function Calls ==
From 1.76. [http://pastebin.com/gWg1JeA8 pastebin]
From 1.76. [http://pastebin.com/gWg1JeA8 pastebin]
<pre>
<pre>
VtrmCipherCalcHeaderDigest            LOAD FFFFFFFF827CF0E0 00000141 00000138 00000000 R . . . B . .
VtrmCipherCalcHeaderDigest            LOAD FFFFFFFF827CF0E0 00000141 00000138 00000000 R . . . B . .
Please note that all contributions to PS4 Developer wiki are considered to be released under the GNU Free Documentation License 1.2 (see PS4 Developer wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:

Cancel Editing help (opens in new window)
Retrieved from "http://www.psdevwiki.com/ps4/VTRM"