HDDHackr v1.40 Build 20130303

[Intersect]

If I were you, I would try using a different pc.

[darandon]

Ok guys. I have some amazing news  I got the sucker to b working. Here is how.

This is for all of you guys that have the firmware flashed but keep getting the LBA does not match error

The tools that i used were hddhackr 0.91b and MHDD as discussed in a post in this forum.

Here is what i did... I used hddhackr to flash the fw and it does the whole conversion but because of the difference in LBA, it wont say the drive is compatible with 360 and even if u try after that the 360 wont recognise it.

So this is what u do. Flash it.. reboot, run MHDD and in there you select your drive.. It will appear as fujitsu, and then u have 2 handy options from the many that u can use. #1 is rhpa (shows u the hpa size... what is the factory and what is user accessible) and the 2nd 1 is nhpa which removes the hpa present on the drive that causes the lba size mismatch.

For those of u that dont know what hpa is wikipedia explains it way better than me so wiki "host protected area"

once u try to remove hpa odds r that it will fail... Dont worry. Unplug the power from the hard drive (THE POWER ONLY NOT THE SATA) wait 10 sec and plug it back in and try nhpa again and it should work. that will remove the hpa and have the whole lba accessible to the user.   once that is done just type exit and u will b back in dos.

To verify that this works, simply re run hddhackr 0.91b again and select the drive and it should tell u that u can run it.

once u get that message power off the pc remove the hard drive... (DONT POWER IT ON AGAIN WITH THE HARD DRIVE CONNECTED AFTER U POWER IT OFF)

Reason for this is because most modern motherboards inculiding my gigabyte p45 with ICH10 southbridge create that measly small 2mb hpa at the POST process which i thought was created by Western digital... so my appologies for previously stating that it was created by western digital.

Hope this helps many of u... It took me a freakin month to really figure out what is going on with the drive.

Thanks to every 1 involved in making these great tools u guys r the best.

Cheers. 

[cs@colorado]

Wanted to point out an issue I've been having. I am working with WD1200BEVT-22ZCT0

I am successfully able to flash and format these drives as follows:

HDDHACKR v.91 - Success, drive flashes, and when installed in xbox is recognized
HDDHACKR v1.0 - Failure, program exits, reports "Unable to write firmware to drive", drive not recognized in XBOX 360 system.
HDDHACKR v1.11 - Failure, program runs, reports "Writing to sector 16-22", "Installing partition..." "Unable to write firmware to drive", program exits, drive not recognized in XBOX 360 system.
**When I re-flashed the drive that failed on v1.11 with v.91, it works, and is already formatted when installed in xbox (probably the new partitioning feature)**

I would like to have greater success with the new version so I don't need to recommend formatting, however, I will continue to go with what works, I find this strange since anything AFTER version .91 is what is supposed to support BEVT (I am told BEVS is no longer in production).

Any advice, or just general comments about this bug let me know!

Thanks!

[Intersect]

It seems to me there are a lot of people having issues with any of the versions not from TheSpecialist. Is there a reason for the latest versions, because they seem to be causing more harm than good.

[GuffeDK]

It seems to me there are a lot of people having issues with any of the versions not from TheSpecialist. Is there a reason for the latest versions, because they seem to be causing more harm than good.

I has talk whit Modfreak he says its not the same source code an its program in turbo C++ now. But he work on a new version as I understand it.

[timedroid]

you won't see any major difference. the drive speed is limited by other factors too.

What do you mean? As far as I can tell, the black(7200rpm) and blue(5400rpm) have the same seek time, but the black spins faster and has a bigger cache. So why wouldn't it be overall faster? Or are you talking about something specific to the 360?
Although I am a bit confused as the WD pages list the latency time for the two drives to be the same, which makes no sense considering they spin at different speeds. And I guess you would run into diminishing returns. Has anyone done load time comparisons of a stock 120GB HDD vs. a Scorpio Black?

[warma2d]

All I welcome.

I have understood that is simple so difficult to wait a good right answer and has decided to create this theme smile.gif

I have: XBOX360 PRO, original HDD 20 гигов (has turned off, has disassembled, has got), bought WD Scorpio Blue 1600BEVT, PC, almost curve hands bb.gif)))

It is necessary for me to stitch bought HDD and all)

Has understood from DOS, from under it I start (v1.11), I press digit of mine HDD, I press F, I write HDDSS.BIN, UNDO2.BIN, I press Y, Y, it works and writes:
1) that here writes I do not remember ok
2) that here writes I do not remember ok
3) Can't write firmware to drive!

That is how much I have understood, it cannot probably make the last item.


For me in BIOS modes: Native IDE, RAID, Legacy IDE, SATA-> AHCI - tried on all these modes and all the same does not wish to write, that is necessary for it. sad.gif In any modes he simply does not see HDD...



Prompt please in what there can be a problem? blush.gif


Sometimes wrote: No ATA identify possible
And
No ATA devices present





All in advance Many thanks!! 

[neonpolaris]

Newegg has the original 1200BEVS back in stock again.  Right along side the BEVT drives.  Weird?  Maybe they were selling like hotcakes and they figured out why when the BEVT that replaced them didn't sell as well.

They're $5 more than the other, though.

I'm going to be preparing one for a friend and after reading all these horror stories I'm going with the BEVS and good ol' 0.91 which worked the first time on my own drive some time ago.

[tranzufsion]

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

Same thing happened to me - WD1200BEVS-22RST0

I can send you my undo.bin if you like just pm me

I resorted to hex editing v.91 to pick up my on board sata and ran the old tool - and the firmware stuck..  I haven't actually tried it in my xbox yet though

[krypto]

Doesn't work on WD1600BJKT-75F4T0
Works with WD1600BEVS-22VAT0

On the BJKT drive hddhackr v1.11 says that everything goes fine on onboard ICH10 chipset, but the HDD remains unchanged and the Xbox 360 doesn't regocnize it (no suprise there). On VIA chipset (PCI) the program hangs after writing partitions to the hdd on Auto mode and it hangs after writing the sectors on manual mode. HDD remains unchanged after rebooting or shutting the system down and waiting 10 seconds, so nothing gets written to the hdd with the VIA chipset either.

[carbv]

Hey guys, I'm having lots of trouble with flashing a VelociRaptor.
I've opened a topic with all details and procedure I've done.

If one of you can help me, I (and all the community) will be grateful. 

Here it is:
http://www.xboxhacker.net/index.php?topic=12161.0

[becktionary]

Version 1.1 says it successfully flashes my WD1200BEVT - 75ZCT2, but when I restart the drive still registers as having the firmware it had before.

My mobo is a Gigabyte P35 DS3L Rev 2.0, chipset is Intel® P35 Express.

I'll see if I can PM you my undo.bin.

[GuffeDK]

Version 1.1 says it successfully flashes my WD1200BEVT - 75ZCT2, but when I restart the drive still registers as having the firmware it had before.

My mobo is a Gigabyte P35 DS3L Rev 2.0, chipset is Intel® P35 Express.

I'll see if I can PM you my undo.bin.

HDDHACKR dont work whit Intel Chipset

I had talk whit Modfreakz he says that works whit NVIDIA chipset..


Hope there soon will com a new version of HDDHACKR there acutally work  I now he works on it

[darandon]

Version 1.1 says it successfully flashes my WD1200BEVT - 75ZCT2, but when I restart the drive still registers as having the firmware it had before.

My mobo is a Gigabyte P35 DS3L Rev 2.0, chipset is Intel® P35 Express.

I'll see if I can PM you my undo.bin.

HDDHACKR dont work whit Intel Chipset

I had talk whit Modfreakz he says that works whit NVIDIA chipset..


Hope there soon will com a new version of HDDHACKR there acutally work  I now he works on it

Ehm.... Read my post above. I used the model up from his motherboard... Same thing as him except INTEL P45 chipset.... Are you people that lazy to just read few comments above your current post?

The motherboard creates its own HPA area on the disk that stores the controller and bios settings on the hard drive itself as soon as it passes POST (wiki Post if you dont know what it is) that is when it creates 2MB on the hard drive that decreases the LBA down giving you the "LBA does not match" error... so basically when you use the tool it tells you that everything is fine and once you reboot, all of a sudden its not fine... Reason for it is because the program itself probably could delete the HPA but once you reboot to verify GUESS WHAT??? you go through POST again and voilla you have a new 2MB HPA on your hard drive again and you fail to verify that it will work with the 360....

Follow my steps above and you will get it going, i am pretty sure. 

for future READ EVERYTHING BEFORE YOU POST.

[GuffeDK]

Version 1.1 says it successfully flashes my WD1200BEVT - 75ZCT2, but when I restart the drive still registers as having the firmware it had before.

My mobo is a Gigabyte P35 DS3L Rev 2.0, chipset is Intel® P35 Express.

I'll see if I can PM you my undo.bin.

HDDHACKR dont work whit Intel Chipset

I had talk whit Modfreakz he says that works whit NVIDIA chipset..


Hope there soon will com a new version of HDDHACKR there acutally work  I now he works on it

Ehm.... Read my post above. I used the model up from his motherboard... Same thing as him except INTEL P45 chipset.... Are you people that lazy to just read few comments above your current post?

The motherboard creates its own HPA area on the disk that stores the controller and bios settings on the hard drive itself as soon as it passes POST (wiki Post if you dont know what it is) that is when it creates 2MB on the hard drive that decreases the LBA down giving you the "LBA does not match" error... so basically when you use the tool it tells you that everything is fine and once you reboot, all of a sudden its not fine... Reason for it is because the program itself probably could delete the HPA but once you reboot to verify GUESS WHAT??? you go through POST again and voilla you have a new 2MB HPA on your hard drive again and you fail to verify that it will work with the 360....

Follow my steps above and you will get it going, i am pretty sure. 

for future READ EVERYTHING BEFORE YOU POST.

Sorry. I just tried what you wrote. But can not get it to work. When I try to flahse my disk whit HDDHACKR with 1.1 and 0.91 does not. 1.1 writes that it has successfully flash (but it dont) and 0.91 for fatal error there are not enogh memory in FW or your bios string.
Have you some Ider? My hard drive is a Scorpio Black

[darandon]

I would guess that 0.91 will give u that because it is an incompatible Firmware... that drive is not a BEVS??? and my second question is y didnt u get a BEVS for cheaper and higher chances of it working?? If your answer is speed you are wrong... even though BEVS has slower rpm and less cache, the sucker runs way faster than the 20gb hd that it was replacing or the dvd rom in that matter... Back to your problem... try to reflash your undo.bin and try to swap that for a bevs.... I havent played with black series but i am sure that they are slightly different FW than BEVS.

[GuffeDK]

I would guess that 0.91 will give u that because it is an incompatible Firmware... that drive is not a BEVS??? and my second question is y didnt u get a BEVS for cheaper and higher chances of it working?? If your answer is speed you are wrong... even though BEVS has slower rpm and less cache, the sucker runs way faster than the 20gb hd that it was replacing or the dvd rom in that matter... Back to your problem... try to reflash your undo.bin and try to swap that for a bevs.... I havent played with black series but i am sure that they are slightly different FW than BEVS.

Okay. Last time i reflash whit 1.1 it kill my drive.. And is it a undo.bin from the black or the BEWS? and how i swap the drive?

[GuffeDK]

Where is MODFREAKz  or is there other there has any idea about how i get the scorpio black to work in my xbox?=

[Intersect]

I don't think they're going to answer because honestly, this software does not work, and I don't think they know why.

[Philippe1988]

Hello everybody. I'm new in the forum. Please help me. The HDDHACKR 1:11 destroyed with my WD1600BEKT 160GB. The PC recognizes the sometimes yes and sometimes not. Does anyone have the UNDO.BIN to WD1600BEKT? If someone has the UNDO.BIN add me on MSN or please send me by e-mail! philippe.osmari@gmail.com Thanks for your help!