andy-man / ps4-wee-tools

PS4 tools for NOR and Syscon manipulations
GNU General Public License v3.0
154 stars 21 forks source link

Document as many board ids as possible (and assign them to the respective board types) #10

Open zecoxao opened 1 year ago

zecoxao commented 1 year ago

Thanks to master hacker flatz (and this not only applies to ps5 cp box but to ps5 sflash and ps4 sflash as well) it has been discovered that 0x1C4000 (or the start of nvs) size 8 corresponds to board id. my suggestion would be to note down these digits and make notes to which type of board they have (region, model, hw info, etc) and draw a pattern of sorts. i suggest putting pictures here with the latest wee tools and respective board id pasted as text. also, if possible adding support for displaying board id would be great

zecoxao commented 1 year ago

Board ID 01:01:01:01:01:01:01:01 -> Syrup Board Board ID 02:01:01:01:03:01:0B:01 -> CVN-K04 Board Board ID 03:02:01:01:02:01:06:01 -> DUH-T1000AA SAA-001 Board Board ID 03:02:01:01:02:01:06:01 -> CUH-1003A B01 SAA-001 Board Board ID 03:02:02:01:01:01:05:01 -> CUH-1116A B01 SAB-001 Board Board ID 03:02:03:01:01:01:05:01 -> CUH-1216A B01 SAC-001 Board Board ID 03:02:03:01:01:01:03:02 -> CAP-CH00XK-M0 SAC-001 Board Board ID 03:02:04:01:01:03:05:01 -> CUH-2016B B01 SAD-00X Board Board ID 03:02:05:01:01:07:05:01 -> CUH-2116A B01 SAE-00X Board Board ID 03:02:06:01:01:05:05:01 -> CUH-2215B B01 SAF-00X Board Board ID 04:01:01:01:01:01:05:01 -> DUH-D7000JA HAC-001 Board Board ID 04:01:01:01:01:01:04:01 -> DUT-DBW00JK-S0 HAC-001 Board Board ID 05:02:01:01:01:01:05:01 -> DUH-T7000AA NVA-00X Board Board ID 05:02:01:01:01:01:05:01 -> CUH-7016B B01 NVA-00X Board Board ID 05:02:02:01:01:07:05:01 -> CUH-7116B B01 NVB-00X Board

First 4 bytes are likely related with versioning (you can see that third byte increases from SAA (01) to SAB(02) to SAC (03), and since SAD isn't here (04?) it goes to SAE (05)

andy-man commented 1 year ago

Good idea, I've added board_id info + mb version suggestion to info screen (since 0.8.7)

CUH-7115B B01 [05:02:02:01:01:05:05:01] NVB-003

MohammedTayyab6339 commented 1 year ago

CUH-7115B [NVB-003]

DonZott commented 1 year ago

CUH-2116A B01 [03:02:05:01:01:03:05:01] SAE-002

Region : [16] Europe / Middle East / Africa Southbridge : Baikal B1 Torus (WiFi) : Version 2


CUH-7016B B01 [05:02:01:01:01:01:05:01] NVA-001

Region : [16] Europe / Middle East / Africa Southbridge : Belize A0/B0 Torus (WiFi) : Version 2

RustyRaindeer commented 1 year ago

CUH-2216B B01 [03:02:06:01:01:07:05:01] SAF-006 Region: [16] Europe / Middle East / Africa Southbridge: Baikal B1 Torus (Wifi): Version 3

tikyuchan commented 1 year ago

SKU / Board ID : CUH-7200B B01 [05:02:03:01:01:07:05:01] ~NVG-004 Region : [00] Japan Southbridge : [0x24, 0x00] Torus (WiFi) : Version 3

MSXCelulares commented 1 year ago

Hello my friend, with the data obtained so far I came to the conclusion that the motherboard is made up of Prefix + Suffix - Revision, where: 0x1c4000 - is prefix (02=CV, 03=SA, 04=HV, 05=NV) 0x1c4001 - is Non-Retail or Retail (01=N-r, 02=R) 0x1c4002 - is suffix: if prefix=02: suffix=N, e.g.: CVN-k04 if prefix=03: suffix=Alphabet seq ... if prefix=05: suffix=A,B or G ... The review is still unknown to me. The addresses: 0x1c4006 and 0x1c4007 compared to a BeW report as far as I could analyze are flags to check if the HDD was replaced or is original from the factory. Below is a copy of the sFlash.py file with some changes I made and they worked perfectly with the dumps.bin I have dados de placas.txt sflash.zip Test1_v0 8 7b Test2_v0 8 7b