Topic: Swapping New Hard Drive Into Real Debug Kit (Read 310 times)

torrentted · « **on:** May 01, 2006, 12:32:00 PM »

Ok. I found this post:

gavroche
Jul 26 2004, 05:04 PM
My Debug kit has a 120GB.

Just take out the old drive,

put in the new one.

Run the recovery disc.

Simple!

And no, the debug kit doent lock drives, even the original drive is unlocked.

http://forums.xbox-s...hp/t246208.html

Is this all true? Do I need to format the new drive in any way or just slap it in? Will it recognize the extra drive space (60 gig) or format it to operate as a 4 gig? Also, do I have to worry about the EEPROM getting flashed and being unusable or anything like that? Finally, do I need the original XDK Recovery disc or will a backup of it work as well? Anyone that can help will be most appreciated.

torrentted · « **Reply #1 on:** May 01, 2006, 12:42:00 PM »

Oh. And I have the Xbox XDK Remote Recovery. Will that work to format the drive--I'm thinking it wouldn't but am not sure.

Flexmaster Frag · « **Reply #2 on:** May 01, 2006, 01:00:00 PM »

If its a genuine debug kit, you should be able to pop in the larger hard drive and run the remote recovery tool. In order for NN to recognize the larger F partition, I believe there's a dxt file you will need to transfer to the debug.

EDIT: There is a dxt file you will need that is in the usual places. From the readme:

QUOTE

This file adds \\Device\\Harddisk0\\Partition6 (F: drive) support to the XDK Launcher. Place fdrive.dxt in E:\dxt on your debug xbox and reboot. Enjoy and happy hacking.

Flexmaster Frag · « **Reply #3 on:** May 01, 2006, 01:08:00 PM »

Good luck and let me know if you get it working.

Flexmaster Frag · « **Reply #4 on:** May 02, 2006, 01:42:00 AM »

Yeah, use the recovery disc.

torrentted · « **Reply #5 on:** May 05, 2006, 02:49:00 PM »

I messed with it and it booted up. After choosing which version of the dashboard, then it asked which version of the kernel. I chose the highest numbers for both--assuming this was the latest version--and after I chose the kernel it gave an error:

"Xbox recovery has failed because of an unexpected error (0x0000001a)."

It's stuck on this screen. I'm going to try it again, with different versions maybe. Can this mess up my Eeeprom?

I took the disc out and booted the Xbox up withouth the recovery disc and it seems to be working fine. Is that error just because the hard drive is bigger than 4.73 gigs? Is that supposed to occur with a larger hard drive? Is there anything I should be worrying about?

Flexmaster Frag · « **Reply #6 on:** May 05, 2006, 03:59:00 PM »

I moved the topic to the development section so the proper people can read this.

Pikkon · « **Reply #7 on:** May 05, 2006, 04:42:00 PM »

You still need to format the F drive,all the fdrive.dxt does is add support for the XDK launcher.Just format the F partition and you should be good to go.

Paintballpsyco2369 · « **Reply #8 on:** May 06, 2006, 11:00:00 PM »

I have been asking around for the same question, and from what I have been told so far, replace the hd, run the recovery disk, then do the dxt hack. From there you would need to format your f drive. I have used an old tutorial that I customized to format the f: and one for the g:. If you want this cod, pm me and I will send it to u. It is a customized version of evox that allows you to format drives. That should work. Let us know how it goes.

old engineer · « **Reply #9 on:** May 07, 2006, 01:53:00 AM »

'Almost' sounds like your DVD drive isn't reading the data off your discs, hence it can't complete, because it can't copy the data over. (tho I don't think this is the case)

...Although saying that, I've had the same errors as you mention, but only when I try forcing things that I shouldn't with a Debug Kit fitted with a 120gb HDD.

...In the end the 'only' (easiest) way I could get round the problem was to install the oldest recovery disc I had, which recovers automatically.

...This worked mainly because the early recoveries have less data to copy over and they 'force' the (correct)flash kernal/dash without giving you a choice. (where as later recoveries you can choose options in the recovery process which can bugger the process up, with incompatible choices/a fussy Xbox)

My advice would be use the oldest recovery you can find (Aug 2001 (final) - May 2002 are ideal ones), THEN recover using a a later one, this gets round the errors you mention with ease.

Hope this helps.

torrentted · « **Reply #10 on:** May 07, 2006, 04:15:00 PM »

All right. Thanks for the help everyone. I found out my burning software is messed up. It's just slightly screwing burns up, but obviously enough to cause problems. I'm a little concerned that it's messing up earlier in the process, but I'll let you guys know what happens after I know I have a good disc. I wish I would have thought to run the remote recovery when I had the chance.

Pikkon · « **Reply #11 on:** May 08, 2006, 06:06:00 AM »

Well I use Nero for burning,you have a thomson drive in your debug kit so a cdrw should work fine.I never had a problem using the recovery disc in a development kit and a debug kit,let us know if it works out fine.Also old engineer,can you run the recovery disc off the HDD,just a thought I just had.

Pikkon · « **Reply #12 on:** May 08, 2006, 07:50:00 PM »

QUOTE(programmingace @ May 8 2006, 09:14 AM)

You probably could start the process, but i don't think it would complete. You might have to change the media type on the xbe too.

If you think about it, if you're running the refresh disc the first thing it does is wipe the hard drive. So you would be overwriting the installer itself. It would be a lot like forcing an eject in the middle of a refresh. I wouldn't recomend it.

Your right Ace,I totally forgot about that.I should think more before I ask.

torrentted · « **Reply #13 on:** May 16, 2006, 05:46:00 PM »

As I was ftping to my f: drive, Xbox Neighboorhood froze and I restarted. To my dismay the F: disappeared.

I found this thread:

http://forums.xbox-s...owtopic=489464#

Is the HDD screwed or what? XBMC takes a minute to load and no videos are shown in f: The games that are on f: still show up in My Programs though. When I click them though they dissappear--not even cool; kinda traumatic actually.

I'm thinking I'm fucked?

programmingace · « **Reply #14 on:** May 16, 2006, 07:02:00 PM »

Kind of odd... are you running any .dxt files? Those are used to remap drive letters. Delete any .dxt files you may have except for the "hack_dev_kit", "f drive" and "vx". Reboot and see what happens.

If you still don't have your F: drive, then pop the refresh disc back in and refresh. Me is begining to wonder about the health of your mcpx chip...

And "xbox neighborhood" isn't really FTP, it's more like SAMBA (SMB, or windows filesharing for you windows folks). It's just a GUI wrapper around some dos SMB commands.

Author Topic: Swapping New Hard Drive Into Real Debug Kit (Read 310 times)