Hi All,
New here but I have been following a few of the posts.
It’s getting hard to locate the old models these days, so I went out and bought a new WD5000LPCX after reading that some people have had success with this model on various posts that I came across on the net, so I can create a new 500Gb x360 drive for more storage.
I’m using HDDHackr_v1.40_Build_20130303 which I believe this is the latest version.
If anyone can help explain what’s going on, it would be greatly appreciated.
Here is the back-story:
1. Successfully hacked a WD5000BEVT drive with the 500GB HDDSS.BIN for the HITACHI - HTS547550A9E384 model. All cool.
2. Successfully hacked a WD3200LPVX drive with the 320GB HDDSS.BIN for the SEAGATE - ST9320325AS model. All cool.
Here’s where it gets weird.
Hacked the WD5000LPCX drive with the 500GB HDDSS.BIN for the SEAGATE / SAMSUNG - ST500LM012 HN-M500MBB model with strange results:
a) The drive was flashed successfully and an UNDO.BIN was created.
b) Partitions 0/2/3 were created successfully.
At this stage I thought the hack was a success but not so because when I connected the drive to the x360 (A Black Elite Phat with the Falcon guts) in an original Phat enclosure, the drive would not show up as storage.
However, when I connected the drive to the x360 via an official MS USB transfer cable, the drive was there. I could transfer files back and forth with no problems but I couldn’t format the drive on the console. (PS: the game I tested still worked after being transferred back to the console drive).
At the end of the day, I figured that I failed to hack the WD5000LPCX drive, so I went back and tried to

restore the UNDO.BIN so I can use the drive as portable storage BUT I get an “UNDO.BIN is WRONG SIZE” message and I can’t restore it back to it’s original state. I used both methods, auto & manual with the same result.
ALSO:
LBA = 976773168, before and after flashing. I think this is standard for a 500GB drive, correct me if I’m wrong. According to the original drive’s specifications, this is correct.
Q1. Could it be the HDDSS.BIN file I’m using? It’s from one of the newer drives / models because I didn’t want to use the same HITACHI Security Sector.
I got the new BIN file here:
"team-xecuter.com/forums/threads/147502-500GB-Hard-Drive-SS-BIN-from-the-new-Winchester-Model-Xbox-360"
OR
".acidmods.com/forum/index.php?topic=43548.0"
FIle Link: ".speedyshare.com/ezcdY/500GB-360.zip"
Q2: Is it OK to try Re-Flashing and Re-formatting the drive using HDDHACKR with the HDDSS.BIN again?
Q3. Can I overwrite sectors 16-22 on the drive with the info from the UNDO.BIN using a HEX editor in WXP to get the drive back if all else fails or will this brick the drive and leave me with a $65 paper weight?
Thanking everyone on advance.
PS: If I can get to format the drive on the console, I’d be happy to make it a dedicated x360 storage drive.
Cheers.
BELDAM.