PS3 resign 4.90fw ps3 back up? to clone ps3

Serial Killer said:
can you extract files using this tool? it seems from the instructions it will just decrypt the drive? and if i decrypt the drive, can i initilize it in windows and extract the data? or will that stop the drive from working in the ps3? or will the ps3 just re encrypt it?
Click to expand...
no, this will not work with ps3encdec and only hdd_reader from 3141card can extract. this tool can only decrypt and reencrypt hdd images, but only completely for a PS3 Slim

and as Berion already has said, Windows initialization always kills the allocation table from a PS3 hdd
 
Windows not understand partition table format used in PS3 (let's call it PS3PT, it have not any official name). So for him, PS3 disks always be treating like empty. That's one of the reason why application like PS3 HDD Reader has been written. Initialization in Windows means writing MBR or GPT partition table, overwriting PS3PT and making Your life very hard in the process if You value Your data. PS3 not understand anything else than PS3PT for internal drive. Changing partition tables will not adopt partitions from earlier partition table. So You can now answer to Your question. :)

Anyway, logic structure on PS3 HDD looks like that there are so called regions (that's official name, but technically they are partitions). Each region (partition) can be separate device. So partition with VFLASH contain its own partition table and partitions, and partition with OtherOS have also its own partition table and partitions.

Main regions: user partition (mounted on PS3 as dev_hdd0), cache partition (mounted on PS3 as dev_hdd1), vflash (only on NOR models), otheros (only on fw up to and include 3.16 if user create one, and only on cfw with otheros++ if user create one).
  • Cache using FAT32.
  • User partition using UFS2.
  • VFLASH sub-partitions using FAT16, FAT32 (mounted as dev_flash, dev_flash2, dev_flash3), raw without any fs
  • OOS is the same as PC, so i.e sub-partitions with EXT4 or whatever, lies on MBR partition table.
Each region is encrypted, vflash twice, otheros probably also twice but how it is done is unknown yet.
 
Last edited:
haxxxen said:
no, this will not work with ps3encdec and only hdd_reader from 3141card can extract. this tool can only decrypt and reencrypt hdd images, but only completely for a PS3 Slim

and as Berion already has said, Windows initialization always kills the allocation table from a PS3 hdd
Click to expand...

ok thank you for the suggestion, i wont use ps3encdec to decrypt drive as i don't think it will help me with my goal to simply extract the data, but i appreciate the help,

Berion said:
Windows not understand partition table format used in PS3 (let's call it PS3PT, it have not any official name). So for him, PS3 disks always be treating like empty. That's one of the reason why application like PS3 HDD Reader has been written. Initialization in Windows means writing MBR or GPT partition table, overwriting PS3PT and making Your life very hard in the process if You value Your data. PS3 not understand anything else than PS3PT for internal drive. Changing partition tables will not adopt partitions from earlier partition table. So You can now answer to Your question. :)

Anyway, logic structure on PS3 HDD looks like that there are so called regions (that's official name, but technically they are partitions). Each region (partition) can be separate device. So partition with VFLASH contain its own partition table and partitions, and partition with OtherOS have also its own partition table and partitions.

Main regions: user partition (mounted on PS3 as dev_hdd0), cache partition (mounted on PS3 as dev_hdd1), vflash (only on NOR models), otheros (only on fw up to and include 3.16 if user create one, and only on cfw with otheros++ if user create one).
  • Cache using FAT32.
  • User partition using UFS2.
  • VFLASH sub-partitions using FAT16, FAT32 (mounted as dev_flash, dev_flash2, dev_flash3), raw without any fs
  • OOS is the same as PC, so i.e sub-partitions with EXT4 or whatever, lies on MBR partition table.
Each region is encrypted, vflash twice, otheros probably also twice but how it is done is unknown yet.
Click to expand...

ok thank you i will follow the previous post and see how that goes, on a side note my external usb corrupted so i have to re rip my games wich is gonna take forever again changeing discs, once its done do i need to keep the update folder for each game or can i delete them to save space? i tried googleing but there isnt definiteive answer
 
I'm not sure if I understood You.

Disc games keeps in "dev_hdd0/game/<GameID>/" cache, patches and dlc (only few cases have separated those data). Digital versions the same, plus itself. So Your question don't have much sense to me. Sorry.

Keep in mind that some patches and DLC are no longer available on Sony servers (Singstars DLCs, Motorstorm patches).
 
sorry ill try again. so when i use multiman and recopy my games to my external hdd, the games have a folder PS3_UPDATE can i delete this folder to save space or do i need to keep it, and if i can delete it do i need to change anything else in like the sfo or eboot?
 
Oh, this one You have in mind. Yes, they contains only firmware update. Useless.

No. You should keep games untouchted anyway, ripped from original disc to disc image form. By this way, You keeping 100% game compatibility and less stress for HDD.
 
@Berion Ok i finally had a chance to follow your instructions (i had some health issues), and unfortunately it didn't work with the 1000gb drive, but it did work with the 500gb

i copied this from terminal window.

3
Device /dev/sdg/ does not exist or access denied.
Device /dev/mapper/ps3hdd-bs does not exist or access denied.
failed to stat() /dev/mapper/ps3hdd
mount: /home/mint/ps3/storage/hdd/dev_hdd0: special device /dev/mapper/ps3hdd2 does not exist.
lsblk: /dev/sdg/: not a block device

All done. Press any key to exit.

but it worked fine with the 500gb drive i dont understand why not? and once i again i put drive in ps3 and its working np
 
i just tried it again but copied both terminals heres the results.


first time is 1000gb drive

PS3 HDD Mounter Micro v1.7 by Berion
Script allows to mount only GameOS partition.
If You want mount all partitions, use normal Mounter script.

Confirm root permissions everytime You will be asked for!


STEP 1: Devices
Choose your HDD from PS3 (type eg: /dev/sdx) from below device list:

MODEL SIZE NAME
2.4G /dev/loop0
Samsung SSD 860 EVO 500GB 465.8G /dev/sda
450M ├─/dev/sda1
99M ├─/dev/sda2
16M ├─/dev/sda3
464.7G ├─/dev/sda4
516M └─/dev/sda5
WDC WD30EZRS-00J99B0 2.7T /dev/sdb
128M ├─/dev/sdb1
2.7T └─/dev/sdb2
WDC WD30EZRS-00J99B0 2.7T /dev/sdc
128M ├─/dev/sdc1
2.7T └─/dev/sdc2
ST31000528AS 931.5G /dev/sdd
931.5G └─/dev/sdd1
Storage Device 0B /dev/sde
Flash Disk 30G /dev/sdf
30G └─/dev/sdf1
048-2E7172 931.5G /dev/sdg
TSSTcorp CDDVDW SH-224BB 1024M /dev/sr0

/dev/sdg
Ok, so You've chose: "/dev/sdg".

Press any key to continue.

STEP 2: Mounting
Choose WISELY:
1. Mount HDD came from Fat NAND without OtherOS.
2. Mount HDD came from Fat NOR without OtherOS.
3. Mount HDD came from Slim NOR without OtherOS.

3
mount: /home/mint/ps3/storage/hdd/dev_hdd0: wrong fs type, bad option, bad superblock on /dev/mapper/ps3hdd2, missing codepage or helper program, or other error.
NAME SIZE FSTYPE MOUNTPOINT
sdg 1000204886016
└─ps3hdd-bs 1000204886016
└─ps3hdd 1000204886016
├─ps3hdd1 268435456
├─ps3hdd2 974166638592 ufs
└─ps3hdd3 2147479552 vfat

All done. Press any key to exit.

and this sceond one is the 500gb drive

PS3 HDD Mounter Micro v1.7 by Berion
Script allows to mount only GameOS partition.
If You want mount all partitions, use normal Mounter script.

Confirm root permissions everytime You will be asked for!


STEP 1: Devices
Choose your HDD from PS3 (type eg: /dev/sdx) from below device list:

MODEL SIZE NAME
2.4G /dev/loop0
Samsung SSD 860 EVO 500GB 465.8G /dev/sda
450M ├─/dev/sda1
99M ├─/dev/sda2
16M ├─/dev/sda3
464.7G ├─/dev/sda4
516M └─/dev/sda5
WDC WD30EZRS-00J99B0 2.7T /dev/sdb
128M ├─/dev/sdb1
2.7T └─/dev/sdb2
WDC WD30EZRS-00J99B0 2.7T /dev/sdc
128M ├─/dev/sdc1
2.7T └─/dev/sdc2
ST31000528AS 931.5G /dev/sdd
931.5G └─/dev/sdd1
Storage Device 0B /dev/sde
Flash Disk 30G /dev/sdf
30G └─/dev/sdf1
WDC WD5000BEVT-11A03T0 465.8G /dev/sdg
TSSTcorp CDDVDW SH-224BB 1024M /dev/sr0

/dev/sdg
Ok, so You've chose: "/dev/sdg".

Press any key to continue.

STEP 2: Mounting
Choose WISELY:
1. Mount HDD came from Fat NAND without OtherOS.
2. Mount HDD came from Fat NOR without OtherOS.
3. Mount HDD came from Slim NOR without OtherOS.

3
NAME SIZE FSTYPE MOUNTPOINT
sdg 500107862016
└─ps3hdd-bs 500107862016
└─ps3hdd 500107862016
├─ps3hdd1 268435456
├─ps3hdd2 474069614592 ufs /home/mint/ps3/storage/hdd/dev_hdd0
└─ps3hdd3 2147479552 vfat

All done. Press any key to exit.
 
@Serial Killer
Hello. I hope You will go back to full health.

Everything You have done is fully properly.

Oh, that's extremely bad news. And very unexpected. :( It looks like disk has been decrypted successfully (properly parsed PS3PT proved that) but kernel cannot mount partition with UFS2. That's why probably also PS3 HDD Reader cannot mount it. Which means UFS2 is damaged in a way that cannot be retrieved by standard tools or UFS2 in PS3 is in some way none standard and for some reason, there is problem with parsing inodes. Which is even more interested, PS3 itself have problems with perform file system checks on disk beyond TiB barrier. Maybe Sony made some terrible mistake in code somewhere and this UFS2 is broken by design!

I don't have enough knowledge to forensic UFS2 (good documents are beyond paywall and UFS2 is plenty of variants :/) but You could make dump of fs table and attach it somewhere, so maybe in future someone figure this out (personally I'm interested too). If You have time and will, do:
1. Run umounter script IF you mounted 500GB drive earlier in this session. If this is clean Linux start, You don't need to.
2. Run mounter micro and do what You did for 1TB disk in post no.28.
3. Open terminal and type this:
Code: 
sudo dd if=/dev/mapper/ps3hdd2 of=${HOME}/ufs2_sample.img bs=512 count=65536 status=progress
This will make 32MiB of decrypted start of UFS2 in home dir (so copy it somewhere because it is in RAM disk if You using Linux live environment). I don't know how large is table so it is possible that this gather more than table alone.
 
Last edited:
@Berion thanks im getting there, and im happy to help in anyway i can especially if it helps others in the future, here is the file hopefully i did it correctly :)

edit: i cant upload the img file it keeps saying file is too large for server to process its 32mb, i tried rar and split the archive into 10mb didnt work then i tried smaller 5mb archives didnt work same error
 
You can upload it to eg. mediafire and paste link here. If someone in future would want such image but on MF will be deleted, still he can ask me for it because I do not plan to purge it.

AFAIK, psx-place allows max 2MiB attachments.
 
You must log in or register to reply here.

Similar threads

Back
Top