Print

[silentnite2608]

QUOTE(TheSpecialist @ May 22 2007, 09:48 AM)

That 'error' in Hex Workshop is normal, just ignore it. No need to manually make your own hddss.bin file, with the modified xplorer360 example, that i posted in this thread a few posts above yours, you can do it very easily too.

Um so how do I make my own hddss.bin from here I can't even get in to a drive.
Also I don't have a 360 HDD nor  the  360 hDD 120GB if I need one for this I'm done because I just waste 85$ of my money and tons of my time.
The reason why I doing manually is so I can make hddss.bin since I don't have nethier drives.

[TheSpecialist]

QUOTE(rolly poly @ May 24 2007, 01:31 AM)

almost the same as the above guy

sil3112 pci card, wd1200bevs lat

same error drive not compatible.

any idea whats going on?

Are you guys sure the hddhackr found the WD BEVS HDD and not some other device ? If in doubt, disconnect ALL SATA/IDE devices except for the WD BEVS drive and try again.

[Antman1]

Here is what I understand..................................  You are trying to get the hddss.bin from the WD BEVs drive..   This is not were you get it.   You get the HDDSS.bin from the Microsoft 120GB Drive then use hddhackr to make the BEVs Drive work for the 360.  so first step is to hook up a 120GB Microsoft HDD and use Xplorer360 Xtreme2 that TheSpecialist was talking about and backup the HDDSS.BIN using that, Also backup Partition2 while you are in Xplorer360 Xtreme2 cause you will need that.  Then place HDDSS.BIN in the same folder as the hddhackr tool and run it as specified in the readme file.  then format it with your 360 (Not the PC).  and place the drive back in the PC and run Xplorer360 Xtreme2 and restore Partition2 with the bin you made of it.  Now unhook from PC and use it in your 360.  

**Important** If you hooked up the Microsoft 120GB Drive to the PC and had windows initialize or do anything to it, the HDDSS.BIN will not be possible because those sectors will be destroyed.  If this is the case you will more than likely have to get another 120GB Drive to get those sectors from.

[SlickWilly440]

Does anyone know if main reason that the Xbox 360 hdd breaks is due to the actual hdd itself or the hdd case that it's housed in?

Because I was thinking of buying a broken 360 hdd off of eBay and replacing the hdd using HDDHackr .91.

Does anyone see any problems with this idea?

Thanks!

[Antman1]

QUOTE(SlickWilly440 @ May 25 2007, 03:08 PM)

Does anyone know if main reason that the Xbox 360 hdd breaks is due to the actual hdd itself or the hdd case that it's housed in?

Because I was thinking of buying a broken 360 hdd off of eBay and replacing the hdd using HDDHackr .91.

Does anyone see any problems with this idea?

Thanks!

I did it and it works great..  

[SlickWilly440]

So was it the hdd that was broken and were you still able to extract the hddss.bin from it perfectly in your case?  Or did you run into some problems?

[rolly poly]

QUOTE(TheSpecialist @ May 24 2007, 02:58 AM)

Are you guys sure the hddhackr found the WD BEVS HDD and not some other device ? If in doubt, disconnect ALL SATA/IDE devices except for the WD BEVS drive and try again.

i borrowed my girl's floppy drive and i tried it with my nforce mobo and it worked fine (after editing the port).

i will be ordering another 120gig for my brother soon, i shall test it again with all drives disconnected.

i did however read all the info printed on screen to make sure it had found the bevs drive, and everything checked out.

[mikey808]

I need a bit of help please.

I have an image of a 20Gb drive but I do not have the physical drive here.
I want to extract partition 2 containing the emu, from this image, and place it on a new 120Gb BEVS which I have ready.
However using Xplorer360 extreme2 I can load this image, but when I try to extract partition 2 it reports this error, "Unable to retrieve drive size! Is this a drive image or a physical drive?" and the program quits.

Is there any way to resolve this please?

[TheSpecialist]

@mikey808: You can only dump partition 2 from the drive itself, not from an image.

[mikey808]

Many thanks for that information.

However, would it be possible to write this 20Gb image to the new 120Gb drive to enable extraction of the partition ?

[Antman1]

QUOTE(mikey808 @ May 26 2007, 02:57 PM)

Many thanks for that information.

However, would it be possible to write this 20Gb image to the new 120Gb drive to enable extraction of the partition ?

yes quite possible.  and as a matter of fact do that then restore your hddss.bin back to the 120gb hddss.bin cause it will be overwritten once restored then place the drive in the 360 and let it format and you will notice partition2 is already on the drive and ready to go!  

[TheSpecialist]

QUOTE(Antman1 @ May 26 2007, 08:25 PM)

yes quite possible.  and as a matter of fact do that then restore your hddss.bin back to the 120gb hddss.bin cause it will be overwritten once restored then place the drive in the 360 and let it format and you will notice partition2 is already on the drive and ready to go!  

Yep, exactly, only keep in mind that you'll lose your data from partition 3 on the drive you're writing the image to this way. But if you haven't used the drive in your x360 for save games etc yet, then that's not a problem of course.

I might add an option to extract the partition from an image instead of a drive, but the problem with things like this is that if you have the source code, it's a trivial modification, done in a few minutes. Without source code (i don't have the source code), it's a few hours of analysing, reverse engineering and patching....

But maybe I'll find motivation for it next week

[xbox360sexual]

QUOTE(TheSpecialist @ May 24 2007, 02:58 AM)

Are you guys sure the hddhackr found the WD BEVS HDD and not some other device ? If in doubt, disconnect ALL SATA/IDE devices except for the WD BEVS drive and try again.

Tried it with just the floppy, same error It says something about "sector 16 not the same as firmware", I type 'Y' and it errors out with it being the wrong drive.

[TheSpecialist]

QUOTE(xbox360sexual @ May 26 2007, 08:59 PM)

Tried it with just the floppy, same error It says something about "sector 16 not the same as firmware", I type 'Y' and it errors out with it being the wrong drive.

Ok, thanks for testing. So now we're sure the hddhacker is communicating with the WD BEVS.

The error you're getting means that the HDD does not react correctly to the 'unlock' command, that the hddhacker sends to the drive. This is used to put the drive in the secret 'factory mode' in which the firmware may be altered. The only reason I can think of is that your SATA card does not transmit that command correctly to the drive. On the previous page of this thread is another report of the same error on also that same SATA card: SIL3112. So I'd say that this SATA card somehow does not work correctly with that command. Therefore I'd advise you to test it on another brand. VIA/Intel/Nforce have all proven to work correctly.

It's probably not the answer you had hoped for, but at the moment, I really think that the SATA card might be the problem ... Maybe it somehow filters these commands, not sure why it would do that, but it would certainly seem so ...

I hope you can test it on another SATA controller and report if that fixes your problem.

Cheers,

TS

[xbox360sexual]

Interesting. I have a VIA6421 I can try, I'll post back with the results