Print

[SimplexPL]

Hello,

This is my first post and I already have a problem (IMG:style_emoticons/default/wink.gif)

It all started with desire to swap 20GB for 120GB BEVS drive. This did not succeed, but something even worse happened - after opening xbox HDD case and backuping the drive using xplorer 360 extreme 2 and putting the HDD back to the case, xbox stopped detecting the disk.

This basically everything I did - I opened xbox hdd case, connected the HDD to my PC (XP SP2) using SATA and used Xplorer360 to access the disk and create backup image of everything, just in case.
In the meantime I tried using hddhackr to make bevs drive work with xbox360, but it failed. I temporarily put the 120GB bevs disk into the original hdd case, but xbox did not detect the disk.
When I put the original xbox360 drive back to the case and connected it to xbox, it also was not detected. It is as if no drive is connected to the console. I tried another original xbox 360 hdd in that hdd case and it worked, so it is not the case or console that malfunctions, but the hard disk, I'm afraid.
When I once again connected the disk to the PC and used xplorer360 i was able to browse the disk contents as if nothing happened. I tried restoring the disk from the backup image but that did not work too - the progress bar would relatively quickly (10-15 minutes) reach the end and then it would restart from the beginning, this time freezing on the very beginning- i waited long but nothing happened so I cancelled the operation. After that it was still possible to browse folder structure on the disk.
I tried many times to make the disk work with the console, but it just does not work. I even tried listening to the sounds the disk makes - there is a faint 'scratching' shortly after boot as if it tried to read data and then it is no longer 'scratching' (i.e. reading/writing) - i can only hear the platter spinning.

I would be extremely grateful on any suggestions as to how to fix this. Perhaps I could use hddhackr to somehoow upload the HDSS.bin file back into the disk? Or use hex editor to edit some properties of the disk that got somehow mangled?

The worst thing is that it's my friends disk so if I don't fix it, I'm toast. I am desperately hoping the community can help me with this.

[TIMxIRISH]

Dunno if you're still having a problem with the HDDs, but if so this information might help to know.

NEVER, EVER restore a 20GB or 60GB drive image to a BEVS drive. I tried it using Xplorer360 extreme 2, and afterward my BEVS saw the same problem-- Not detected in the 360. Now if I read your issue right, that's what you did. Basically, if you were to use Xplorer360 extreme 2 to dump the hddss.bin from the BEVS drive and compared it to the hddss.bin you ORIGINALLY flashed it with in a hex editor (ie. hex workshop), they look completely different. The hddss.bin that now comes from the BEVS drive is identical to the 20gb drive image's hddss.bin (don't believe me? open the image in a hex editor and go to line 2000. sorry if that's not correct lingo for it; i'm a little new to hex).

Here's how I got my BEVS detectable again:

At the time of the problem, I still had the original UNDO.bin in the folder I had hddhackr. I made backups of every file hddhackr made in the process of flashing just to be safe, so before you continue, if you haven't I suggest you do the same. Now what I did was loaded up hddhackr with my BEVS drive, and tried the usual "hddhackr -f". hddhackr reported that the drive should be readable in the 360. I knew this not to be true, and I found my proof of why from examining the hddss.bin dump from the drive just before trying to reflash.

So, at this point i did "hddhackr -u" to "undo" the flash, because it was the only way hddhackr was going to let me reflash (remember, my UNDO.bin was the original UNDO.bin I had-- the one that would restore my drive back to normal). After undoing, i shut down, waited 10 seconds, booted up and went to "hddhackr -f" and reflash. I had the 120gb hddss.bin I originally used to convert the drive to 360 compatible state in the folder. hddhackr asked me if I wanted to create an UNDO.bin, and since I already made a backup of my UNDO.bin, I said sure. hddhackr refused to flash it due to an existing UNDO.bin in the folder. I did "hddhackr -f" again, but this time without creating an UNDO.bin. Popped it into my 360 and it detected! Only odd thing is it said I had 3.5GB left of free space. I pressed the Y button on the 360 and reformatted the drive, and it showed 107GB free again.

Now what to do about partition 2? Absolutely nothing, because despite how much of a mistake it was to restore a 20GB image to a BEVS drive, it actually created partition 2, and is completely visible on the drive (hell, go check it in Xplorer360 if you don't believe me). At this point there is nothing more you need to do to your BEVS drive. Works, partition 2 is visible... life is good. But if you want to get data from an old HDD onto the BEVS drive, I highly suggest you manually copy the folders off of the old HDD into a temporary folder on your windows machine, then manually copy those folders onto the BEVS drive. I wouldn't take any more chances with the restore image feature, even if it seems safe.

Hope this helps you out, but if not, someone else will find it and it will hopefully fix their problem.  

[jhonnypolak]

Here's the fix to your problem

http://www.xboxhacke...p?topic=12062.0