PS3 Problem with hdd of ps3

Till Harpax

Till Harpax

Forum Noob
Please help me I try to access ps3 hard drive from the pc and now the ps3 asks me to format it


I'm not sure what I did, but these are some of the events on the hard drive. Or can I eliminate the privileges of using the hdd as a storage device or can I do something so that the ps3 recognizes the hdd again without having to format it?
The USBSTOR \ Disk & Ven ____ Mass & Prod_Storage_Device & Rev_ \ 116AC2101219 & 0 device was configured.

Driver name: disk.inf
Class GUID: {4D36E967-E325-11CE-BFC1-08002BE10318}
Date of the controller: 06/21/2006
Driver version: 6.3.9600.16384
Driver Provider: Microsoft
Controller section: disk_install.NT
Classification of the driver: 0xFF0006
Corresponding device ID: GenDisk
Top drivers: disk.inf: GenDisk: 00FF2002
Updated device: false

The USBSTOR \ Disk & Ven ____ Mass & Prod_Storage_Device & Rev_ \ 116AC2101219 & 0 device was started.

Driver name: disk.inf
Class GUID: {4D36E967-E325-11CE-BFC1-08002BE10318}
Service: disk
Bottom filters:
Superior filters:

please tell me there is something I can do or should resign myself to lose everything, my games, my games, the updates of the games.
Or can I extract the save data from the hdd?
 
If you hit yes to initialising the drive when you connected it to the PC, she's most likely a goner. :/

If you have your eid_root_key you can try using aldostools to attempt to read the data, but sounds like it's already gone.
 
Last edited:
If I delete the partition overwritten of the HDD , It´s possible that I can recover my information? Because I see that my ps3 hdd has a partition of 128 MB
 
Don't do any further writes to the hdd or your chances of recovery will be zero.
Wait and hope somone has some solid information on trying to recover it.

The drive is encrypted so the tiniest change can destroy everything.
 
I think I already found the old contribution of 3141card and quote it verbatim
"He wrote a pm asking if I formatted the hdd already. and since I was unable to say I quit, in my mind, I left it alone and did not give up. then he told me about how first sector is only overwritten by windows and how can I use winhex to restore it. so I made a hdd image of the bad ps3 with HDD Raw Copy v1.10 then I formatted the exact same drive, installed cfw I had on it originally. then I hooked it up to PC, opened that hdd in winhex, exported first sector. then I restored that bad image to that drive. opened it in winhex, pasted the first sector and saved. and it worked just fine. PS3 booted as if nothing ever happened :) a big lesson here for me and I got scott free, whew, sad that you were not that lucky. "
if with this information is enough or I would need to know something more than Impaler I do not mention?
 
Last edited:
Yes, that is atm the only you can do.
The same PS3 will choose the same partitioning scheme for the same HDD based on total size of HDD.
But it will not work if you have made changes to the original HDD, like extending vflash for linux.
 
So, I just have to make a backup to the hdd with HDD Raw Copy to later format the hdd with the ps3, then make a copy also to that new partition and then open the Winhex editor with those two partitions, copy the difference of the first sector of the new partition and paste it into the old partition and finally restore that old partition modified to HDD, to leave the system as if nothing had happened?
By the way, how can I modify the protected savedata of some games if the content of the HDD is encrypted?
the Xploit of my PS3 is HAN
 
Last edited:
Yes, make a RAW copy of your brocken HDD, including the first broken sector.
Format the broken HDD with FAT32 and then with your PS3.
Plug the new formated PS3 HDD to your PC, do not initialize the HDD under windows ;)
Copy the first sector from HDD, with the proper start of PS3 partition table, on the same place into your backup to fix it.
Copy the fixed backup back to HDD.

Regarding write to an encrypted PS3 HDD, only posible under linux.
Look e.g. here:
https://playstationhax.xyz/forums/t...ubles-mounting-the-encrypted-ufs2-filesystem/
or here:
https://playstationhax.xyz/forums/topic/4671-mounting-ps3-hdd-on-newer-linux-kernels/
 
Muchas gracias por la información [USER = 21] @ 3141card [/ USER] y gracias a todos los que se tomaron la molestia de comentar y ponerse en contacto con @3141card
 
Last edited:
stranger_2.jpg
original_1.jpg
stranger_1.jpg
I still have doubts and is that I do not know from which sector to which sector is where I change Windows, since sector 00000000000 to sector 00000004096 have the same values and from 00000004096 is where things start to change ....
the image in the middle is from the clean partition of ps3
 
Last edited:
A sector is 0x200(512) byte in size. Your pics make no sence for me.
What kind of PS3 it is, NAND or NOR(vflash on HDD)?

Have you init the HDD with a GPT? If yes, that kill more sectors than a
simple MBR. Then you can try to copy the first sector back to the broken
backup. Maybe the HDD Reader is able to read at least dev_hdd0(gameOS) partition.
A way to save at least games, gamesaves and so on. For PS3 the broken HDD
image will not longer work.
 
My ps3 is eMMC ,and I have not started with GTP, because I did not know what a sector was.
I think that the "hdd reader" will not work because I do not have the eid_root_key file, as far as I could only get it if my ps3 had a cfw firmware, but mine has OFW
 
Last edited:
Ok, than I cant help you. For old NAND or NOR PS3s its clear, but no idea about new PS3s.

In case of old NAND or NOR HDDs the methode above is working. If we compare
the old backup and the new(with the same PS3 formated) HDD, only the first sector
differs. And the replacing of this sector is enough for repair the backup.

If you had init your eMMC PS3 HDD with a MBR, than the first sector on HDD is killed,
that is all we know.

You format the same HDD on the same PS3 and say the data from offset 0 to 4096 are equal?
That is the whole PS3 partition table, all 8 sectors. If this is equal in your old backup
and the new formated HDD, than there is no killed sector. Sry, but this make no sence.

(Regarding WinHex, one click on the decimal values into column "offset" and it switch to hexadecimal)
 
Last edited:
Till Harpax said:
My ps3 is eMMC ,and I have not started with GTP, because I did not know what a sector was.
Click to expand...
In the hexeditor there are 16 bytes in every row (16 in decimal) but everything is in hexadecimal, you need to open calculator while counting
1 sector is 512 bytes (in decimal) = 0x200 bytes (in hexadecimal)
At left in the hexeditor you can see the counters in hexadecimal... so to select a sector you need to select starting from 0x0 up to 0x200

But it doesnt makes sense the screencaptures you posted with big offsets/positions around 0x4900 because this is a lot of sectors (bit more than 32 sectors, counting them in decimal)
Till Harpax said:
If I delete the partition overwritten of the HDD , It´s possible that I can recover my information? Because I see that my ps3 hdd has a partition of 128 MB
Click to expand...
And this probably is related... but still doesnt makes sense because 128mb is way bigger
So... dunno but if you are still interested in trying to fix this you need to step back and give us better info

And forget about the pc hdd reader tool btw, because if is a PS3 superslim it means you cant get the eid key, so no hdd decryption in pc posible
The only way is what is explained before... using the same hdd (or a different hdd of the same brand and model) to regenerate this sectors at begining... then "patch" them over the backuped hdd image... and finally write the patched image in the hdd

But if the amount of sectors that was overwritten is too big is not going to work, usually the people that have this problem only have the data on the first sector damaged
 
Last edited:
sandungas said:
But it doesnt makes sense the screencaptures you posted with big offsets/positions around 0x4900 because this is a lot of sectors (bit more than 32 sectors, counting them in decimal)
Click to expand...

He use decimal offsets: byte offset 00000004069 = 0x0000001000, the laste two screenshots start at sector 8.
The first screenshot start at byte offset 00000004240, this is offset 0x90 into sector 8.

BTW he say, up to this offset(the first 7 sectors)the data are equal, and this make no sence. If this is right, then the first sector in his old backup is not killed by windows. ????
And the long line of zeros in the second screenshot, into a encryptet sector from the new formated HDD?
Make all no sence for me.

I would say, he can save the backup, maybe someday it is posible to repair the problem
by knowing more about all this. And more importend, a way geting the right keys for
decrypting this HDD from a sMMC PS3. Without proper data in plaintext it is imposible
to work and also to encrypt data back, that the PS3 can read it again.
 
Ops, now i realize the column at left in his screenshots is in decimal, still the sector number is too high as you mentioned

My suggestion is use the option to "open device" (not sure if winhex have it) so he can see the hdd "fresh formatted" by the PS3... and at the same time open also the hdd_backup.bin (huge file with the damaged data)
This way can be compared side by side in the same app, and change the view mode to "dual window"

*And dont write \o/ or anything in them \o'/
 
Sure is WinHex able to open a HDD as device in sector view,

Tools --> Open Disk or by pressing F9, and then open of the Physical Media, the HDD

and also to interpret a file like the backup of the original HDD as a device,

open the image in WinHex then: Specialist --> Interpret Image File As Disk

Its a powerful forensic tool. ;)

But the problem are the data he have not the view.

sandungas said:
*And dont write \o/ or anything in them \o'/
Click to expand...
Hehehe, I think that he has understood finally... things are broken very quickly. :(
 
You must log in or register to reply here.

Similar threads

Back
Top