HDDHackr v1.40 Build 20130303

[MODFREAKz]

Little bird told me

An exe packer is not only used to reduce the executable size, it's also used in many cases to protect the exe from disassembling, so if you can't disassemble the exe then it was packed right! The packing process can't be reversed in this case.

by the way, these questions are lowbrow.

[.ISO]

Oh yea? Well I've just dumped the source code.
Pay me $1000 if you don't want it leaked
 
 ||
 \/

lol jk

[Intersect]

Anything packed can always be unpacked. Kinda like a certain popular tool with it's asprotect 2.3 ske.

[itsfakemon]

Anything packed can never be unpacked (by myself). Kinda like a certain popular tool with it's asprotect 2.3 ske.

fix'd

[MODFREAKz]

New version of HddHackr is ready, see first post.
Hope that all known issues are fixed now.

People with problems should contact me!

[Intersect]

Well, just because you were a jerk about it itsfakemon,  I unpacked 1.10. I will not post the unpacked file unless team modfreaks and schtrom don't mind, since schtrom is a friend. But if you guys don't care, I will post.

http://img44.imageshack.us/img44/9582/hddhacker.jpg

[itsfakemon]

oh, how cute
what's the point of it? that you can use (un)packing algorithms using trial and error?
I'm very impressed 

[Intersect]

Hey, you said I couldn't do it, and I did. Get me something with securom and I'll do that too. You have a pretty horrible ego there itsfakemon, too bad you have nothing to back it up with. And it's a dos app, if you don't know how to dump it without "trial and error" you're retarded and should not speak on these subjects.

[GuffeDK]

Hey all why works WD VelociRaptor not? I try to flash the drive its flash succes but now i turn the pc of and on after 10 seckunds its still has the same model number and all the other things is the same still. And The xbox cant dont see it? What i do wrong herre? Now i try to undo it write this. Cannot write firmware to the drive

[GuffeDK]

Hmmmmm is there a bug / problem whit the new version? :S I has get 2 totally dead veloci raptor drives and my original 360 elite drive wont work more in my 360 and ind 360 Explorer is there only 3-4 files on partion 2. I had dump the key from the original harddrive. What is going on here

[MODFREAKz]

Again small update for Hddhackr.

Sorry for the trouble!

[jhonnyp0lak]

Hi guys,

I'm experiencing the same exact error as scanna_gt

I've got a WD1600BEKT-00F3T0 drive

I've tried using HDDHackr 0.91, 1.00 and the latest 1.11

I've tried mucking around with BIOS settings, AHCI, legacy mode and even tried using my VIA PCI adapter that i used to flash DVD drives on this drive, and even though each version detects the HDD no problem, it doesnt want to dump the sectors. I've dumped the sectors for my original XBOX 20GB fujitsu drive no problems, so its not a matter with my controllers it seems, its something to do with the drive ?

HDDHackr 0.91 detects the drive however when i try to dump sectors 16 - 22 it gives me the following error:

Error, data on sec 16 til 22 incorrect

HDDHackr 1.00 detects the drive however when i try to dump sectors 16 - 22 it gives me the following error:

Sector checksum 0 is wrong!

HDDHackr 1.11 detects the drive however when i try to dump sectors 16 - 22 it gives me the following error:

Sector checksum <0000> is wrong!

[TenchiStyle]

I haven't seen this problem yet, so here goes...

I have a wd1200bevs and was able to get through the flashing process using v1.11 with no errors.  I tried to run it through the process again to check that it worked, and the program will actually flash the drive again. (Same thing happened using v.91; no confirmation of XBOX compatibility) I decided to try it in the XBOX, but the memory screen reads "No Storage Device Found."

Solutions?

[MODFREAKz]

I've got a WD1600BEKT-00F3T0 drive
I've dumped the sectors for my original XBOX 20GB fujitsu drive no problems, so its not a matter with my controllers it seems, its something to do with the drive ?
I've tried using HDDHackr 0.91, 1.00 and the latest 1.11
HDDHackr 0.91 detects the drive however when i try to dump sectors 16 - 22 it gives me the following error:
Error, data on sec 16 til 22 incorrect
HDDHackr 1.00 detects the drive however when i try to dump sectors 16 - 22 it gives me the following error:
Sector checksum 0 is wrong!
HDDHackr 1.11 detects the drive however when i try to dump sectors 16 - 22 it gives me the following error:
Sector checksum <0000> is wrong!

why are you trying to dump sector 16 from WD drive?? You must be joking! 
Of course hddhackr gives you warning message becouse there is no data on that sector.

I have a wd1200bevs and was able to get through the flashing process using v1.11 with no errors.  I tried to run it through the process again to check that it worked, and the program will actually flash the drive again. (Same thing happened using v.91; no confirmation of XBOX compatibility) I decided to try it in the XBOX, but the memory screen reads "No Storage Device Found."

ok you are now the second person with this problem. 
1. Tell me full model name, WD1200BEVS-? ? ? ?
2. mainboard and chipset model name
3. send me your undo.bin

[jhonnyp0lak]

why are you trying to dump sector 16 from WD drive?? You must be joking! 
Of course hddhackr gives you warning message becouse there is no data on that sector.

Sorry matey, i thought we had to dump it as a part of the backup process

But it seems im still having problems. When i now do the FLASH procedure and if i use my onboard SATA ports (i've tried both Legacy and Native mode)
HDDHackr says its completed everything successfully... However when i shut down my pc and turn it on again after 10 seconds it still picks it up as a WD1600BEKT.

I've tried using my VIA PCI card too, and that gets stuck half way through the process. It says:

Sectors 16-22 rewritten successfully!
Partition 0/2/3 created successfully!
\ _

And it just sits there, stuck on that prompt

My motherboard is a Gigabyte GA-G33M-DS2R (Southbridge: Intel® ICH9R)
VIa card is a: VIA VT6421A
My HDD is a: WDC WD1600BEKT-00F3T0
Firmware Revision: 11.01A11

Here's another problem i just encountered, when I wanted to restore my drive from UNDO.BIN it tells me that.

Can't write firmware to drive!

I've created multiple UNDO.BIN files every time i tried flashing the drive and compared UNDO.BIN (the 1st undo file) to UNDO5.BIN (the 5th iteration) and I compared them in a hex editor and they differ. Hence why I wanted to restore my drive from UNDO.BIN but i get an error. And now when i restarted my PC the drive doesn't get detected at all :/

[darandon]

I just ordered a BEVS 120 gig from new egg and the bozos sent me a Blue series drive. Now i tried to use hddhackr 1.11 and the whole process worked fine. It said everything completed and all the green messages. It made me soo happy but once i rebooted, nothing was flashed and it still reported as a WD drive... Here is the info that might help with the error hunting. The hard drive is BEVS 120 00vat0 and the motherboard is using a ICH10 southbridge controller. The program recognises the drive in automatic mode that i used but the stupid lba is smaller than what it should b  thanks to WD.... Any word on what might get this sucker flashed properly? I tried 0.91 and 0.91b and once i flash it it just says that the data is not same (due to the LBA size i assume)...

Any help is appreciated


Another question that i have is why cant i use the 60gb hddss, on the 120? I know the reason why the first time it fails is because of the smaller lba size than the required for 120gb due to the HBA being present that i cant seem to get rid of. Now when using a 60gb the lba size should b 1/2 of the 120gb and when i flash the drive with the 60gb ss, it still cant seem to confirm to me that its a valid drive      Personally i will b happy even if i can use the 120gb hd as a 60 cuz i still got it cheaper than the 60s cost in store.

[Warclock]

darandon
- I got the same probelm with WD2500BEVS, flashed with 1.11 successful but the hd still the same as orginal after reboot. I did 3 times but hd is not damaged. Then I gave up, put back 0.91b with command -F, that took less than 2 mins. I didn't remember exactly why but I got 0/2/3 partitions, I don't know if I booted up again and checked with version 1.11 that would do something or not. I did reflash again with 1.11 but it said "hd compatible or work with with xbox 360" .....Then ran in windows, I could see all 0/2/3 partitions.

BTW, modded with 120gb bin

[fui]

I had also the same problem with WD320BEVT. I tried to flash with 1.10 and 1.11 many times, got succsessfull flashed message. But when I boot, I saw that HD was still as the original WD320BEVT. Then, for a last hope I have flashed with 0.91 in first try, and checked after reboot. It was now Fujitsu 120 GB HD and "ready to work with xbox360". xplorer360 show that it has also 0/2/3 partitions.  Now it works in Xbox360 with 107 GB in size.

I had only many problems with the xplorer360 during backups. Hanging during Backups, Extracting und Restoring of the partition 3. I have discovered that, it is caused because can not read the file patition3/Compatibility/xbox1/TDATA/FFFF000/Music/st a single file. Then I copied and restored the files in patition3 manully without that file, simply skipped. And at the end it works with profiles and game saves.

I thing that everybody using this hddhackr tool should share their experience to contribute devolopment of the tool. 

Thanks to the Team.
 

[darandon]

U c here is what is going on with mine so far. when i use 0.91 or 0.91b it flashes the firmware but the lba size is invalid so it always says that sectors 16- something needs to be patched to make it compatible. Now i tried 1.11 on another pc (AMD SB-700 chipset) and it failed to write firmware... I dont know if i am screwed or not. I did make an undo file before with 0.91 cuz that is the only 1 that i used first so i have that. Now i will have to hunt down another pc with a via chipset to c if that will get 1.11 to work fine... The 1 thing that is pissing me off is that WD no longer makes the RTS series of the BEVS hard drives... So now when u order a 120gb hard drive u get  a Blue version... Those have 2mb of HBA on the damn disc that u cant get rid of... or i am not aware of how to get rid of so far.. Tried many things and still no go. and that makes the LBA to be smaller than what the full 120gb lba is. causing the 360 not to recognise the hd as well as for hddhackr not to say that the image will work with 360... I have been searching the net like crazy and cant seem to find a damn solution on how to get rid of that stupid HBA that the blue series have. I

If any 1 knows how to and has done it i would really appreciate to hear what was used and how it was done.

Also Team MODFREAKz... What chipset did u test your program on that u confirmed working so that i can go out and try to find a machine with it...

Thanks

[GuffeDK]

I have a new problem    i try to flahs a new WD Scorpio drive but i say bad drive or firmware or something and now is the drive dead What is wrong?