PS3 [Tutorial] Fixing Windows disk initalization

Berion

Berion

Developer
I tested both: MBR and GPT and I can confirm that both ARE fixable by partition table transplantation. At least on CECHL04 with OFW 3.55. ;)

For MBR You need 512B, for GPT 17KiB. It is unfixable only if user additionally create partition on such disk.

I didn't test device with larger than 512B sector size, so I don't know if PS3 aligning logic sector to physical size. If she doing it, then for MBR will be 4KiB and for GPT 136KiB.

dmde_fix_gpt.png


Tutorial is in Polish, but can be blindly step by step based on images.
 

Attachments

Warning: since Windows 10 Home, build 10.0.19043 user @wln1337 claims that disk initialization goes automatically (so without user asking). If this is true, above tutorial is useless (because making unable to read untouched PS3 partition table) for people on this specific Windows 10 and all newer, probably including Windows 11 builds. I cannot verify it myself, but be warned.

Whole discussion and how to do the same but on Linux side, You can find here:
https://www.psx-place.com/threads/problem-with-ps3-hdd-initialized-by-windows.36820/
 
@SargentoGarcía What is Your model? User from link above claims that this method doesn't work on CECH-3xxx - which I cannot check myself. If this is true, high probability it also not work on CECH-4xxx. In addition, he said that current Windows 10 builds initializing drives without user asking, making above tutorial completely useless for such case, left You using Windows 8.1 or older, or just any Linux.

You can still get the data from this disk or its image but You need decrypt it, which means You need read EID Root Key, which means Your console must be CFW compatible or else You will not this key (HAN and HEN will not allow that). There is no tutorial how to do this and I'm not willing to write one, as it is a lot more complicated than normally.
 
Last edited:
Berion said:
@SargentoGarcía What is Your model? User from link above claims that this method doesn't work on CECH-3xxx - which I cannot check myself. If this is true, high probability it also not work on CECH-4xxx. In addition, he said that current Windows 10 builds initializing drives without user asking, making above tutorial completely useless for such case, left You using Windows 8.1 or older, or just any Linux.

You can still get the data from this disk or its image but You need decrypt it, which means You need read EID Root Key, which means Your console must be CFW compatible or else You will not this key (HAN and HEN will not allow that). There is no tutorial how to do this and I'm not willing to write one, as it is a lot more complicated than normally.
Click to expand...

Thank you for your response. I read the warning but tried the tutorial anyway.
I will detail everything as best as possible.
PS3 model: CECH-3011A (always official firmware)
HDD: Hitachi Z5K320-160 (160GB)
HDD was manually initialized to GPT in windows 10 LTSC 1809 (LTSC 2019 v.1809.17763.1192 x64). I don't remember the PS3 firmware version at the time.
Now I followed the steps in the tutorial exactly as it explains but with the following:
Windows 10 19044.1766 (I didn't notice the automatic initialization thing).
DMDE 4.0.0.800 Free Edition x64 (latest)
PS3 firmware: 4.89 official (latest).
The only difference in doing what is explained in the PDF was that the image extension is .bin instead of .img (the rest was all the same).



Translated with www.DeepL.com/Translator (free version)
 
@SargentoGarcía I'm sorry that I didn't answer to You earlier but I couldn't.

So, since You have CECH-3xxx it means You cannot put CFW on it and read ERK (EID Root Key), at least not today. And since above method not works for You (You are second person who reporting it and also with 3xxx series), it means You are now out of luck because You cannot restore it, and cannot read data from disk image with broken partition table.

But! Keep this disk image if You want get those data. One day it will be possible (when models with new bootloader like Yours, can be fully exploitable or just when we know how to get ERK from them).

PS3 fw version probably doesn't matter.
Extension doesn't matter, it is just part of file name. Can be any.

PS: Thank You for detailed informations. I appreciate it.
 
Berion said:
@SargentoGarcía I'm sorry that I didn't answer to You earlier but I couldn't.

So, since You have CECH-3xxx it means You cannot put CFW on it and read ERK (EID Root Key), at least not today. And since above method not works for You (You are second person who reporting it and also with 3xxx series), it means You are now out of luck because You cannot restore it, and cannot read data from disk image with broken partition table.

But! Keep this disk image if You want get those data. One day it will be possible (when models with new bootloader like Yours, can be fully exploitable or just when we know how to get ERK from them).

PS3 fw version probably doesn't matter.
Extension doesn't matter, it is just part of file name. Can be any.

PS: Thank You for detailed informations. I appreciate it.
Click to expand...
Hello, no problem. I also apologize for my late reply.
Too bad it is not possible, but I will keep the image file saved until it can be.

I am very grateful for your help.
Have a great day.
 
I just wanted to come on here and say, I did this yesterday on my PS3 Super Slim running HFW 4.90 and my PS3 was successfully restored. I followed the document that is in Polish. I found a way to translate and try to make sense of it.

1) Download the Polish PDF, Google search "Online Doc Translator" and upload the PDF to translate.
2) I had a spare hard drive and used a SATA to USB cable to connect to my computer.
3) I downloaded AOMEI Partition Assistant Standard Edition and used it to format the spare hard drive to FAT32 cause Windows wouldn't do it successfully.
4) Followed the doc all the way, used the DMDE software it tells you to use but skipped the MBR vs. GPT section, I just did what the pictures showed.
5) I didn't remember how it got reinitialized on Windows, but I went ahead and restored using the gpt.img and it was successful. Playing a game right now with no issues whatsoever.
 
Two weeks ago I have case when user initialize his disk. He decided to goes road describe in tutorial. For unknown reason, newly formatted drive have got partition table leading to partition(s) starts from different LBA (first on 32 (0x4000) instead 8 (0x1000) like usually). Which means guide is not 100% reliable because not always PS3PT are the same.
 
You must log in or register to reply here.

Similar threads

Back
Top