Print

[z6joker9]

Hey guys, I've been working on this for hours...

I too have a 1200BEVS (08VAT1) and I used 1.0 and I got the E69 error on my 360.  I restored using the undo file with no problems.  I reflashed it with 1.0, and again, same problem, so again I restored it.  Then I found this post.

Thus, I went and found v0.91b (which was very difficult... if anyone is reading this, the only place I could find it was by using the auto xbins downloader).  

It does work, except with one hitch.  When it is detecting the SATA drive (not in legacy mode) hddhackr gets "stuck", I have to power off/power on the HDD, and then it moves along like normal.  It flashes, and upon restart, the drive shows up as the flashed drive in the bios.  Running hddhackr -f again (after powercycling the drive during drive detection) says that the drive is ready for the xbox.  HOWEVER, when I put this v.91b flashed drive in the xbox, it gives me an e69 error again.  

I tried in legacy mode but it also has trouble detecting the drive until the drive is powercycled.  However, upon powercycling, it shows all of the information for the drive, asks to flash (y/n) but aborts before you have the option to choose.

I have two non-flashed 20gb's that work just fine, no error.

I wasn't planning on transferring any saves, I just wanted a blank 120GB drive.  Do I need to use xplorer or create the partitions manually somehow?

Any ideas?  Thanks!

[codiwar]

Hi already sorry for my English ^ ^ and then I'd like to know or find HDDHACKR 0.91b version because I search on xbins but I find I do not think the 0.91 is esque me give you a link I thank you in advance because I have a WD Scorpio Blue 160GB BEVS and with version 1.0 I get an error with the LBA and 0.91 I can not find the HDD So thank you to answer me

[z6joker9]

Get the automated Xbins downloader:

http://www.360mods.n...ownloads&get=29

Click on 5_xbins.exe

It works like an FTP client.  It will log in, click on XBOX 360, click on HDD tools, click on HDDHackr, click on Old, and click on the one that says v0.91B.

Anyone have any idea about my problem above?

[GrumpyG]

I did recover my 120GB HDD so this may help some that do not already have a dead drive.

HDD model - WD1600 BEVS 60RST0
I too made the mistake of trying to restore the image from my old 20GB HDD onto a newly hacked 120GB drive and after that the Xbox wouldn't recognize it any more.  Xplorer 360 Extreme2 did see the drive and showed partitions 0, 2 and 3 but the Xbox would not recognize it.

The firmware was good and HDDHacker said it should work in the Xbox but it was wrong.  The problem was that when I restored the image from the old HDD it also wrote the old HDD firmware data to sectors 16-22 on the disk.  When the Xbox checks the HDD it compares the firmware with these 7 sectors looking for a match and if it doesn't match then no HDD.  HDDHacker will only write the data to sectors 16-22 whenever it performs the flashing process.  It will not reflash the firmware if what you are loading is the same as what is already in the HDD so therefore will not rewrite the correct data to the 7 sectors.

I used a downloaded software called HDAT2 (DOS program from www.hdat2.com) and wiped the drive clean.  I tried it back in the Xbox but still no luck so I am not sure if wiping the HDD was actually useful but it did get rid of the 3 partitions!!

How I finally recovered the HDD.
I connected the HDD to the SATA port on my PC. I used HDDHacker 0.91b and flashed the drive with firmware for a 60GB HDD, restarted the PC and ran HDDHacker again to confirm that it looked like a 60GB HDD. Then I ran HDDHacker again and flashed once more with the 120GB firmware, restarted the PC and checked that it was now a 120GB HDD (Make sure to answer YES to the question about making sectors 16-22 compatible with the FW). Put it into the Xbox, formatted it and now have 107GB free.

I am going to use the HDD with a couple of games first and let the Xbox create the other partitions and then I may try to copy the folders from partitions 2 & 3 later.

I Found "HDDHACKR 0.91 with 20, 60 and 120 hddss.rar" on piratebay.  Worked fine for me.

[steevyhead]

any help with the hex edit part PLEEEASE hddhackr0.91 wont see my drive. should i use 1.00? is a wd1600bevs-00vat0 scorpio blue.

msinfo32 info

Name VIA VT6421 RAID Controller
Manufacturer VIA Technologies, Inc.
Status OK
PNP Device ID PCI\VEN_1106&DEV_3249&SUBSYS_32491106&REV_50\4&3B1CAF2B&0&20F0
I/O Port 0x0000DDA0-0x0000DDAF
I/O Port 0x0000DDB0-0x0000DDBF
I/O Port 0x0000DDC0-0x0000DDCF
I/O Port 0x0000DDD0-0x0000DDDF
I/O Port 0x0000DDE0-0x0000DDFF
I/O Port 0x0000DE00-0x0000DEFF
IRQ Channel IRQ 16
Driver c:\windows\system32\drivers\viamraid.sys (5.1.2600.540, 100.50 KB (102,912 bytes), 6/20/2009 9:31 PM)


i have another threat but i cant get a reply. ive been in the IT biz for years but more in harware intgr., devel., tech support etc not prog. i dont know hex and im STUMPED, i would realllllly appreciate any help. people keep trying to sell me drives already done on ebay, and i just want to learn. thanks

[z6joker9]

Just a note... I had a 1200BEVS that I used HDDhackr v1.0 on and it bricked the drive.  At first, I could UNDO, but the drive, for all purposes, wouldn't work in a computer, even trying to repair/format with low level software in a DOS boot.  It was recognized but not useful.

I picked up a 1600BEVS and used HDDhackr v0.91b and using the same computer hardware with the same configuration, it went off without a hitch.  Took maybe 2 minutes start to finish.

I'm beginning to think he released v1.0 just to be mean.  Anyone want a 1200BEVS?  I'll sell it cheap!

[jhonnypolak]

I can confirm that HDDHackr 1.0 and 1.11 have both stuffed my WD1600BEKT. When i tried to run UNDO on HDDHackr 1.11 it said it can't write firmware and exited. The drive was undiscoverable. None of my pc's could see it.

[anvil992]

well, my 1200bevs RST is killed too. The same way by flashing with hddhackr v1.0.

Guys, any news on that, has someone found a remedy?

Also the question of one of the previous speakers stil valid - I mean if i'd return HDD using warranty, is it possible to detect that hdd was modified and thats the reason of brick?

[ron6399]

QUOTE(RyLoS @ Jun 9 2009, 03:09 AM)

Can you confirm please the model of your 1200BEVS? Is it the 22ust0 or not?
Thank you.

I just got farther than I have before with the wd1200bevs 22ust0 , I tried a million and 1 times with a  VIA VT6421 and hddhackr 1.11 to no avail. It said it flashed but never did. I took my drive to work to try an intel sata cntrl. and with hddhackr 1.11 no go. Then I tried it with hddhackr .091 and finally got confirmation so when I ran the .091 again it said it should work with the xbox360. I'm at work so I can't confirm till tonight does the 360 see the drive but I'm felling it will, stay tuned. By the way this machine is a Gateway 4300 series with an intel chipset.

[ron6399]

QUOTE(ron6399 @ Jul 6 2009, 03:32 PM)

I just got farther than I have before with the wd1200bevs 22ust0 , I tried a million and 1 times with a  VIA VT6421 and hddhackr 1.11 to no avail. It said it flashed but never did. I took my drive to work to try an intel sata cntrl. and with hddhackr 1.11 no go. Then I tried it with hddhackr .091 and finally got confirmation so when I ran the .091 again it said it should work with the xbox360. I'm at work so I can't confirm till tonight does the 360 see the drive but I'm felling it will, stay tuned. By the way this machine is a Gateway 4300 series with an intel chipset.

Ps. the reason i believe it will work was upon running hddhackr .091 again the drive id itself as a fujitsu and not a western digital as before when it didn't flash.

[ron6399]

QUOTE(ron6399 @ Jul 6 2009, 03:32 PM)

I just got farther than I have before with the wd1200bevs 22ust0 , I tried a million and 1 times with a  VIA VT6421 and hddhackr 1.11 to no avail. It said it flashed but never did. I took my drive to work to try an intel sata cntrl. and with hddhackr 1.11 no go. Then I tried it with hddhackr .091 and finally got confirmation so when I ran the .091 again it said it should work with the xbox360. I'm at work so I can't confirm till tonight does the 360 see the drive but I'm felling it will, stay tuned. By the way this machine is a Gateway 4300 series with an intel chipset.

Well it worked, popped it in the xbox and yes its working. With .091 I guess the key was after it said it flashed ok, on reboot and running hddhackr .091 again it reported the drive as a fujitsu which means it flashed the drive as it would of said wb1200bevs. I did have more than 1 sata drive on the controller but I made sure the wd1200bevs was drv 0.

[fitsman]

Is there anyone that flash the western digital 120gb hard disk with hddhacker 1 and above without problems?

Why do you think all that problems happened?

Maybe because the program had bugs - problem design?

what you would do to correct "bricked" hard disk with hddhacker 1

The designers of the program what would it says for all these problems?

A lot of thanks.

[Zeta_WRX]

I just recovered my bricked WD1600BEVS 22UST0, here is how I did it.
Use hddhack91 -u with the undo.bin from hddhackr 1.0 or 1.11. Then boot up some linux partition manager (I used ubunto partition editor), and creat a partition with it. Now your drive should show up in windows.

Hope it works for all the bricked drive!!

[Spegs12]

I did this a while ago and my biggest problem was getting partition 2 on to the new drive. Oddly enough I did it by restoring a 20 GB image to my 120 GB and then having the Xbox reformat the drive. Without this partion backwards compatibilty will not work. The 360 cannot make this partition on the drive for you. It must be transfered from another drive. I did manage to kill a 3.5" drive in the process by forgetting to disconnect it and going through the flashing process. It flashed both, then I messed around with the 3.5", did something can't remember what, and now the computer cannot see it. All of the information that HDDHackr writes to the drive is missing, it will not  even spin up.

[ZprivateZ]

QUOTE(Spegs12 @ Aug 30 2009, 01:43 AM)

I did this a while ago and my biggest problem was getting partition 2 on to the new drive. Oddly enough I did it by restoring a 20 GB image to my 120 GB and then having the Xbox reformat the drive. Without this partion backwards compatibilty will not work. The 360 cannot make this partition on the drive for you. It must be transfered from another drive. I did manage to kill a 3.5" drive in the process by forgetting to disconnect it and going through the flashing process. It flashed both, then I messed around with the 3.5", did something can't remember what, and now the computer cannot see it. All of the information that HDDHackr writes to the drive is missing, it will not  even spin up.

After you format the drive in the 360, you can run the inital setup on the xbox and make an offline profile this will correctly make the partitons on the drive. The you can just copy over partition 3 from your backup and poof your done.