Topic: Hddhackr 1.0 Killed My Wd Scorpio Bevs 22ust0 120gb (Read 235 times)

RyLoS · « **on:** May 27, 2009, 03:35:00 AM »

I've tried using the automatic mode, the hdd was perfectly seen by hddhackr...and hddhackr told me the firmware was flashed correctly after warning to flash 360 compatible firmware or not.
I tried on my 360 and hdd was not seen.
Tried again...and discovered that all the times hddhackr tell me the firmware is flashed (using hddss.bin 120gb from usual places) but the drive is in reality untouched as it isn't recognized by 360 and work perfectly on windows.

After some attempts, i tried also to restore my first created UNDO.bin and PUFFF....hddhackr say in red it can't write the firmware. Ok I think, maybe it's my sata integrated the problem.
Restarted.

DRIVE KILLED. I explain better: hddhackr can see the drive only some times (random) again on the sata port, but there isn't the vendor string, only serial number is showed.
The drive is seen by windows some times but actually isn't working.

I tried again and again but i can't go out of this state (i also tried differents sata cards and integrated sata adapters, i work with PCs so i tried a lot of models).

How do i recover my drive? Maybe this "Western Digital Vendor Intro Power Brute" in the readme of hddhackr can help me, how to use it?

Thank you in advance.

This post has been edited by RyLoS: May 27 2009, 10:45 AM

Absent Crysis · « **Reply #1 on:** May 29, 2009, 10:20:00 PM »

Man, i literally JUST had this same thing happen to me, exactly the same thing (last night in fact). I too tried using an integrated sata connection, and i did manage to connect the hdd to my 360, but with the hard drive connected, it E 69 s right when it's turned on. And yeah, its not like we dont have the correct undo.bin (i made 5 in the process of trying to flash my drive), hddhackr just wont let us re-flash the drive. My computer however, is about 4 years old, so maybe that had something to do with the problem. I at least want to make the drive work normally, id rather not be down 55 bucks with a worthless piece of metal and silicon.
So any help with this problem would be dually appreciated.

This post has been edited by Absent Crysis: May 30 2009, 05:22 AM

Refferehtom · « **Reply #2 on:** June 02, 2009, 10:51:00 AM »

Well Hddhackr 1.0 wouldn't work for me. When it was about to flash it would just hang. I tried to restart the process and hddhackr didn't recognize my drive, (no data strings at the top). What I ended up doing was using the last version before 1.0 and was able to flash it in less than 2 minutes. Give that a try

apg2k4 · « **Reply #3 on:** June 04, 2009, 07:24:00 PM »

well not exactly that but something similar happened to me. I tried the same drive wd1200bevs-22rst0 with hddhackr 1.00, that didnt work. then i used hddhackr 0.91 and it worked flawlessly. i formated the drive with my xbox and had the 107gigs. after that i conected the drive back to xplorer 360 and only saw partition 1. then i made a backup of my 2nd partion from my real m$ 120gb hd and fataly chosed the option "restore image". now the drive couldnt be detected by the xbox anymore. after that i made a full backup of my 60gb drive and restored the backup on my faulty 120gb drive with no success. does anyone know what to do that the xbox will recognise the drive again? btw, xplorer 360 shows all partitions now (0, 2 and 3).

rossmac · « **Reply #4 on:** June 06, 2009, 05:33:00 AM »

QUOTE(apg2k4 @ Jun 5 2009, 02:24 AM)

well not exactly that but something similar happened to me. I tried the same drive wd1200bevs-22rst0 with hddhackr 1.00, that didnt work. then i used hddhackr 0.91 and it worked flawlessly. i formated the drive with my xbox and had the 107gigs. after that i conected the drive back to xplorer 360 and only saw partition 1. then i made a backup of my 2nd partion from my real m$ 120gb hd and fataly chosed the option "restore image". now the drive couldnt be detected by the xbox anymore. after that i made a full backup of my 60gb drive and restored the backup on my faulty 120gb drive with no success. does anyone know what to do that the xbox will recognise the drive again? btw, xplorer 360 shows all partitions now (0, 2 and 3).

I'm in the EXACT same position as you!

Anyone got any ideas? I tried formatting to NTFS, but Xplorer360 still recognises the Partitions 0 2 and 3...

Please help a brother!

rossmac · « **Reply #5 on:** June 06, 2009, 05:57:00 AM »

QUOTE(apg2k4 @ Jun 5 2009, 02:24 AM)

well not exactly that but something similar happened to me. I tried the same drive wd1200bevs-22rst0 with hddhackr 1.00, that didnt work. then i used hddhackr 0.91 and it worked flawlessly. i formated the drive with my xbox and had the 107gigs. after that i conected the drive back to xplorer 360 and only saw partition 1. then i made a backup of my 2nd partion from my real m$ 120gb hd and fataly chosed the option "restore image". now the drive couldnt be detected by the xbox anymore. after that i made a full backup of my 60gb drive and restored the backup on my faulty 120gb drive with no success. does anyone know what to do that the xbox will recognise the drive again? btw, xplorer 360 shows all partitions now (0, 2 and 3).

Actually, I think you just must load up hddhacker again, restore the drive back to its original WD BEVS state, and then load it back up and flash it to the 120gb ss once more. Now the 360 should recognise it and there you format the drive to 107gb again. Then connect back to pc and transfer the content from partition 3 backup to partition 3 of 120gb drive. It should then work after this. It did for me!

phantom8 · « **Reply #6 on:** June 06, 2009, 08:14:00 AM »

RyLos, I've encoutered very similar problem as you. Hddhacker 1.0 didn't allow me to restore the firmware and now my drive is dead. Here is what exactly I encountered. (I put that in another thread before I see yours.)

QUOTE

I used hddhacker 1.0 to flash a WD3200BEVT 320GB drive, it reported LBA mismatch and ask me if I wanted to proceed. I said yes and it flashed the drive, but it didn't work when I put it into the Xbox 360 console. The console didn't find any harddisk. Then I connected the drive back to the PC and tried to restore the original firmware. Hddhacker said "Can't write firmware" or something similar. Afterwards, I used the older hddhacker 0.91 as suggested by someone. It did flash the drive. However, after powering off the PC and on again, the harddisk can't be found. Basically, I now have a dead drive in front of me. Even the PC BIOS didn't detect the drive. Is there any way to recover my drive. Thanks in advance for any assistance.

RyLoS · « **Reply #7 on:** June 08, 2009, 07:03:00 AM »

I bought another BEVS 120gb 22ust0 drive and tried carefully.
Every SATA controller i've tried was not the problem, as the disk was recognized by hddhackr 1.0 and also 0.91; both says that the drive is flashed but after reboot, drive is untouched.

The big problem resides on hddhackr 1.0 and the restore firmware from undo.bin
After trying that, and getting the "hddhackr can't write firmware", you reboot and the drive is DEAD.

This is second drive i kill, so ok, i will stop on this hacking, but I will follow here to see if there is a remedy.

Col.Havoc · « **Reply #8 on:** June 08, 2009, 09:03:00 AM »

QUOTE(RyLoS @ Jun 8 2009, 10:03 AM)

I bought another BEVS 120gb 22ust0 drive and tried carefully.
Every SATA controller i've tried was not the problem, as the disk was recognized by hddhackr 1.0 and also 0.91; both says that the drive is flashed but after reboot, drive is untouched.

The big problem resides on hddhackr 1.0 and the restore firmware from undo.bin
After trying that, and getting the "hddhackr can't write firmware", you reboot and the drive is DEAD.

This is second drive i kill, so ok, i will stop on this hacking, but I will follow here to see if there is a remedy.

i'll let you know. I have two 120GB drives coming today, i'm not sure if they are 22ust0 drives or not, we will see. From what I have read on this forum, ever since hddhackr 1.0 came out, people have been having problems, so i'm going with the tried and tested 0.91 and seeing what happens.

Col.Havoc · « **Reply #9 on:** June 08, 2009, 04:43:00 PM »

Hey,

Just thought I would come back and say that I was successfully able to flash, undo, reflash, re-undo, and flash again, my WD1200BEVS hard drive, and I have it working in my xbox 360. I used hddhackr v 0.91B and it worked flawlessly. I'm not too sure what SATA chipset I have, but I have a dell inspiron 4700 and it has an intel 2 port S-ATA on it, and it worked great. The only problem I am having is with transferring my old save data, to my new drive, but I think I am on the mend. (tip, turn OFF UAC in Windows Vista to copy files back and forth from hard drives).

RyLoS · « **Reply #10 on:** June 09, 2009, 01:09:00 AM »

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

jboy41 · « **Reply #11 on:** June 10, 2009, 01:07:00 AM »

hey i have that model of BEVS hard drive and it appears i killed mine as well. I used 1.0 and had an issue something about LBA so I got paranoid and tried to restore from the undo.bin file i backed up. Now it just shows a blank name where the hdd drive name should be and when going further it does recognize a 120gb hard drive connected.
I try using hddhackr (.91 and .91b as well) to restore again and it looks okay i turn off my desktop etc same garbage. If i try flashing it shows a drive with no name and when choose that drive it just freezes

anyone have the undo files of a US20 maybe my backup was messed up?

thanks this sucks biiiiig time!

RyLoS · « **Reply #12 on:** June 10, 2009, 02:15:00 AM »

jboy41, this is exactly the same situation...the restore firmware from undo.bin kill the drive.
I think the firmware on the drive after that is garbage, infact, the drive some times show itself without name, sometime isnt recognized at all, sometimes the drive spin down after 10 seconds automatically etc etc.

For The_Specialist:
Some times it is possible to see the killed drive under hddhackr 1.0, could you make a way to recover the drive, or to reflash it correctly for xbox360 operation? Thank you.

PS
Trying to flash the killed drive with hddhacker 1.0 for xbox360, it always says firmware flashed correctly, but nothing change in reality.

jboy41 · « **Reply #13 on:** June 10, 2009, 10:47:00 AM »

well that is very sad news

do you think there is any chance for it to be fixed in the future?
also if i were to return it, do you think they will be able to tell it was raped by the user

phantom8 · « **Reply #14 on:** June 11, 2009, 02:56:00 AM »

After my first 320GB WD drive was killed by hddhackr 1.0, I've obtained another drive. This time, I used hddhackr 0.91b and it worked perfectly.

*** My advise is don't use hddhackr 1.0 and stick with the older 0.91b version ****

I think there needs to be a sticky to warn ppl about the potential bricking when using hddhackr 1.0. There seems to be many ppl bricked their drive with it.

This post has been edited by phantom8: Jun 11 2009, 09:57 AM

Author Topic: Hddhackr 1.0 Killed My Wd Scorpio Bevs 22ust0 120gb (Read 235 times)