HDDHACKR v1.40 Build 20130303: format your WD Drive. Xbox hdd case and use it as a genuine xbox 360 HDD. Garmin Map Updater.exe. For 320GB and 500GB hard drives (HDDSS.BIN. Dec 04, 2011 How to hack a 250gb or 320gb sata drive to work in the Xbox 360 and. Hacking a 250gb drive or HDDSS320.bin to HDDSS.BIN if you are hacking a 320gb.

HddHackr — how it modifies a Western Digital drive for use in an Xbox 360 HddHackr — how it modifies a Western Digital drive for use in an Xbox 360 Introduction This article is my attempt to understand the method by which HddHackr modifies a Western Digital drive in order to make it compatible with an Xbox 360. As I don't have an Xbox, or a supported WD drive, I'm relying purely on research.

Therefore there may be errors. How HddHackr works HddHackr reads the HDD firmware version, serial number, model number, and capacity in LBAs from sector 16 of the original Xbox HDD, and then writes this information to a supported WD drive of equal or larger capacity. It does this by using WD's vendor specific commands (VSC) to modify the HDD's firmware. AIUI, in the case of a ROYL drive, the relevant firmware modules are 0D and 02.

The result of this hack is that the WD drive then identifies itself in the same way as the original drive, eg Fujitsu MHV2020BH. The WD drive's original modules are backed up in an UNDO.BIN file. LBAs 16 - 22 are referred to as the Hard Drive Security Sectors and are also copied from the source drive to the target drive. HddHackr backs up these sectors in a HDDSS.BIN file. The structure of the security sectors is described here: Here is an example for a 20GB Fujitsu HDD: Here is a hex dump of sector 16: HDDSS-20.BIN --- this file is a backup of LBAs 16 ->22 0000 20 20 20 20 20 20 20 20-4E 57 35 38 54 35 41 32 NW58T5A2 0010 35 4E 48 50 30 30 39 33-30 30 32 43 46 55 4A 49 5NHP0093002CFUJI 0020 54 53 55 20 4D 48 56 32-30 32 30 42 48 20 20 20 TSU MHV2020BH 0030 20 20 20 20 20 20 20 20-20 20 20 20 20 20 20 20 20 20 3B 0F D7 3F-82 77 FE 41 C6 F6 A2 5D.?w.A.] 0050 FC 17 2C 17 7A D4 F8 D6-80 29 54 02 D3 79 C9 61.z.)T.y.a. Offset Description Data 00 ->13 serial number (20 bytes) NW58T5A25NHP 14 ->1B firmware version (8 bytes) 0093002C 1C ->43 model number (40 bytes) FUJITSU MHV2020BH 58 ->5B total LBAs (little endian) 0x02542980 LBAs x 512 bytes/LBA = 20 003 880 960 bytes 5C ->encrypted stuff (256 bytes) Here are hex dumps of modules 0D and 02 from a WD2500BEKT drive: MOD 0D --- contains firmware version 0000 52 4F 59 4C 04 00 1E 00-0D 00 01 00 1F FF 0C 3F ROYL..? 0010 30 30 30 31 30 30 30 30-00 00 00 00 00 00 0000.

0020 31 31 2E 30 31 41 31 31-00 01 03 01 00 00 50 01 11.01A11.P. 0030 4E E2 01 AD 6F FB 00 01-FE FF 00 00 00 00 00 00 N.o.. 0040 01 00 00 00 00 00 00 00-00 00 64 00 00 00 00 00.d. MOD 02 --- contains serial number, model number, capacity in LBAs (and passwords?) 0000 52 4F 59 4C 01 00 30 00-02 00 03 00 30 75 7B EC ROYL.0.0u{. 0010 30 30 30 38 30 30 30 30-09 1D 09 00 00 00 0000.. 02A0 33 00 4E 04 02 00 00 01-57 44 2D 57 58 45 36 30 3.N.WD-WXE60 02B0 38 50 4C 37 31 30 39 00-00 00 00 00 00 01 10 3F 8PL7109.? 02C0 00 00 00 00 6F 59 1C 1D-6F 59 1C 1D 6F 59 1C 1D.oY.oY.oY.

02D0 6F 59 1C 1D 00 01 A4 03-00 00 00 00 07 7F 00 00 oY..

Good Afternoon - Thanks for the tutorial. Memory Sorrow And Thorn Epub Mobilism more. After reading it, I started doing it last night.

I'm having an issue, though, where I can't restore my original data onto the new drive. Below is what I did and the current state. Please let me know what you think needs to be done: What I Did - All steps performed on a workstation with fresh install of Windows 7 x64 1. Bought a new WD 2.5' drive which I thought would work: Western Digital WD3200BEVT Blue Series 320gb 2. Created bootable USB drive and flashed the hddss.bin for the 320gb drives. It did give message, but proceeded anyways.