Topic: TheSpecialist's HDDHackr v0.82B - Install your own Xbox360 HDD (Read 779 times)

Antman1 · « **Reply #15 on:** February 16, 2007, 08:37:00 PM »

ok I just got this drive: http://www.newegg.co...N82E16822136072 but my problem is that when I let hddhacker make the hddss.bin file it goes good then I shut down hook up the 120gb and start back into dos on my flash drive and type hddhackr -f and it says:

_______________________
copied data from hddss.bin to sector 16-22
Serial IDENTIFY DEV: WD-WXE........
Serial in hddss.bin file: SOA......
Model IDENTIFY DEV: WDC WD1200BEVS-00LAT0
Model String in hddss.bin file: SAMSUNG HMO20GI
BIOS version IDENTIFY DEV: 01.06M01
BIOS version in hddss.bin file: YU100-06
Information on sector 16 does NOT match firmware info.
Want to flash this firmware to make it compatible with sector 16? (y/n) Y
Do you want to create an undo file?(y/n)yFatal error, Not enough room in FW for your BIOS string
________________________

I am stuck here. Is there anything I can do to make this work? Please help. Thanks in advance.

TheSpecialist · « **Reply #16 on:** February 17, 2007, 03:43:00 AM »

Let's find out what's wrong, check your PM please.

TheSpecialist · « **Reply #17 on:** February 18, 2007, 07:10:00 AM »

Problem fixed for Antman1. I'll make sure the download link on this site gets soon replaced with a link to version 0.83.

Version 0.82 should work for most people though, if you get the same error as antman1, come back soon to check the download link again for version 0.83 (IMG:style_emoticons/default/smile.gif)

BTW, i only just saw the link to newegg.com that Antman1 posted, amazing, how a 120 gb WD HDD is even cheaper than the official MS 20 gb HDD, LOL !

This post has been edited by TheSpecialist: Feb 18 2007, 03:15 PM

Antman1 · « **Reply #18 on:** February 20, 2007, 07:05:00 AM »

Drive is working great but I did find one thing that doesnt work. Xplorer360 does not see the drive on the PC so I cant use my PC to transfer files and such. but the 360 see it no probs. Is there something I can try on Xplorer360 to make it see it? it says it cant find a FatX drive but if I put the original on it sees it no probs,

TheSpecialist · « **Reply #19 on:** February 20, 2007, 03:31:00 PM »

QUOTE(Antman1 @ Feb 20 2007, 02:36 PM)

Drive is working great but I did find one thing that doesnt work. Xplorer360 does not see the drive on the PC so I cant use my PC to transfer files and such. but the 360 see it no probs. Is there something I can try on Xplorer360 to make it see it? it says it cant find a FatX drive but if I put the original on it sees it no probs,

Haven't tried xplorer360 myself yet. Did you format the drive on your 360 ?

ploggy · « **Reply #20 on:** February 20, 2007, 06:59:00 PM »

Does this mean you have a working 120gig hdd on your xbox360?

This post has been edited by ploggy: Feb 21 2007, 02:59 AM

Antman1 · « **Reply #21 on:** February 21, 2007, 04:21:00 AM »

QUOTE(TheSpecialist @ Feb 20 2007, 11:02 PM)

Haven't tried xplorer360 myself yet. Did you format the drive on your 360 ?

Yes I formated on the 360 and then redownloaded some of my content and all has been working very nice. I just wanted to move my saves and stuff from my old drive over and my original is seen on xplorer360 but the new drive just cant be seen.

QUOTE(ploggy @ Feb 21 2007, 02:30 AM)

Does this mean you have a working 120gig hdd on your xbox360?

Yes I have my 120GB Western Digital drive on my 360 and working beautifully. As stated previously it only sees the drive as a 20GB drive right now but that will change in the future and I will be ready.

TheSpecialist · « **Reply #22 on:** February 21, 2007, 07:06:00 PM »

Ok, I've checked it out for you. The thing is, an authentic xbox 360 HDD contains several partitions. If you format the WD with the x360, then your 360 will only create one partition. Now, to operate normally in your x360, it only needs that one partition (the 'main' partition). However, xplorer360 thinks that something is wrong and WANTS to see at least one more partition. What you could do:

1. Copy the first 0x130eb0000 bytes from an original HDD to your WD HDD. This is about 5 gb of data, 95% is 0 though. However, your WD HDD will then contain all the same partitions as an original HDD, this might be a good idea anyway (IMG:style_emoticons/default/smile.gif) OR:

2. Clone a COMPLETE original x360 HDD onto your WD: you could do that with any clone tool or even with winhex for example. OR:

3. Just make xplorer360 happy: edit sector 1024 (=0x400) = byte 0x80000. You need to make it look like:

58 54 41 46 00 00 00 00 00 00 00 10 00 00 00 01

So, the easy way to do this: open your drive with winhex, press <ALT>+G, use position 80000 (hexadec) and then edit these 16 bytes starting at 0x80000 to look like above. Save it and then xplorer360 will work.

I haven't tried the drive in the 360 again, maybe your 360 won't like option 3 (IMG:style_emoticons/default/smile.gif) If it doesn't just zero out these 16 bytes again (IMG:style_emoticons/default/smile.gif)

But to conclude, I think it's good practice to clone an original HDD onto your WD, so all partitions are correct. Your WD won't need these partitions to work, but MS *MIGHT* check for them in the future and if the partitions are not there, they know that the drive didn't come from any of their suppliers (IMG:style_emoticons/default/smile.gif)

Personally, I doubt that MS will ever try to stop any non MS HDD's from going onto LIVE, but you never know of course ...

This post has been edited by TheSpecialist: Feb 22 2007, 03:26 AM

Antman1 · « **Reply #23 on:** February 22, 2007, 10:13:00 AM »

GENIUS! I did option 3 because I had a backup I made with xplorer360 and just needed it to see it. I was able to edit just that one line and it showed up without any problems in xplorer360 and then I just restored my image from the original drive and all is great now. All my original files that came with my hard drive are back and all my saves are back. This is great man. I wonder if it would be possible to get the program to put that hex line on the drive while making it? You are a genius though bro. Thank you for checking on that for me.

PS: I didnt test the drive immeditaly back in the 360 after i changed those bytes I just restored my image but I dont see why it wouldnt work in the 360 with just that one line edited. I can confirm that restoring your image after editing that works great!

This post has been edited by Antman1: Feb 22 2007, 06:16 PM

woork · « **Reply #24 on:** February 23, 2007, 05:52:00 AM »

Yesterday I tried to flash my new 120GB WD BEVS Harddisk but this was much more complicated than I thought. Mainboards with Intel Chipset are not working, I tried 2 different brands (Intel and Gigabyte). So I went to a friend of mine who has an ASRock Board with VIA Chipset. That Board is crap btw but reading out the hddss.bin from the original HDD worked flawlessly

Now I am stuck at the same error like Antman1 (Fatal error, Not enough room in FW for your BIOS string).

For now I am waiting patiently for the announced 0.83 ..

Regards,
woork

TheSpecialist · « **Reply #25 on:** February 23, 2007, 08:28:00 AM »

I'm kinda busy with some things, forgot to send Xantium the new version to place on this site. I don't have it here, but maybe if you PM Antman he'll be kind enough to send you the .83 version (IMG:style_emoticons/default/smile.gif) I'll try to have it on this site in the files sections ASAP anyway.

About the Intel chipsets: my tool scans your PCI bus and tries to detect your SATA controller automatically. However, there are some differences between chipsets and some are not easy to autodetect. I'm quite busy with some other things right now, but I'm planning to add an option to manually input the port number (in case detection fails, you can look that number up in windows) and also to improve the auto detection a bit. But I can't promise this to be released in the VERY near future, like I said, pretty busy with some other stuff unfortunately ...

This post has been edited by TheSpecialist: Feb 23 2007, 04:44 PM

woork · « **Reply #26 on:** February 23, 2007, 09:33:00 AM »

Thanks for your fast reply!
PM to Antman is out, lets see who is faster

My time leaves also not much space for a hobby like this so you have my full understanding when things take longer than expected. Perhaps you could mention in the upcoming 0.83 readme.txt that the program is [/i]only working with VIA chipsets. This would save the others perhaps some time.

Greetings,
woork

Antman1 · « **Reply #27 on:** February 23, 2007, 10:43:00 AM »

I sent ya a PM. Let me know if ya have any questions.

TheSpecialist · « **Reply #28 on:** February 23, 2007, 11:09:00 AM »

QUOTE(woork @ Feb 23 2007, 05:04 PM)

Perhaps you could mention in the upcoming 0.83 readme.txt that the program is [/i]only working with VIA chipsets.

I didn't write the autodetector for a specific chipset, it is a very generic routine that scans your PCI bus for all hardware devices. Once it has found a harddisk controller, it tries to determine which ports it uses. I don't know why it's not working for (some/all ?) other chipsets, maybe it doesn't find the ports or maybe it doesn't find the controller at all. I hope to have some time next week to look at it, but I don't have an Intel/Gb controller, which complicates things (IMG:style_emoticons/default/smile.gif)

It would be helpful if you could send me the port lists. To do so, see this link: http://forums.xbox-scene.com/index.php?showtopic=514126

It would be helpful if you could send me your port lists for your intel controller. In the example on the link:

QUOTE
I/O Port 0x00006655-0x000066A2
I/O Port 0x00000000-0x00000003
I/O Port 0x00008877-0x000088A4
I/O Port 0x00000000-0x00000003
I/O Port 0x00000000-0x0000000F
I/O Port 0x00000000-0x000000FF

This post has been edited by TheSpecialist: Feb 23 2007, 07:21 PM

TheSpecialist · « **Reply #29 on:** February 23, 2007, 08:29:00 PM »

I found myself a computer with Intel chipset, hehe. My autodetector in hddhackr v0.82 works perfectly, it finds the controller and also the correct ports. However, the Intel SATA controller i tested it on has 4 SATA connectors. The VIA chipset only has 2. The thing is, the VIA chipset configures both its ports as 'master'. The intel also has only 2 ports available, but has a master AND a slave on each port. So, the reason it wasn't working for you, is that you had the drive attached as a slave and my tool currently only checks for master devices.

So, to get the hddhackr to detect your drive, just plug the drive into another SATA connector (a master) on your mainboard. You should be able to see in your bios or at system boot, if your WD is on a slave or master port.

I'll update the hddhacker next week, to also detect slaves, it's only a very minor patch, but in the mean time, just use a master connector (try all 4 connectors on your mainboard if you're not sure which 2 are the master ports).

TS

This post has been edited by TheSpecialist: Feb 24 2007, 04:41 AM

Author Topic: TheSpecialist's HDDHackr v0.82B - Install your own Xbox360 HDD (Read 779 times)