Print

[obcd]

The second tutorial looks the best for a harddisk upgrade.

1. Backup your xbox eeprom and ftp the eeprom.bin to your pc.
Make sure you turn the virtual eeprom off also turn the shadowc off.

2. ftp your current drive C and E partition over to your pc.

3. Place the C and E contents in the xboxhdm C and E folder. Also place the eeprom.bin in the correct folder.

4. Make the xboxhdm iso and burn it to a cd.

5. Proceed with that cd and the new harddisk connected to your pc. Lock the harddisk once it's prepared.

You don't need to partition and format the harddisk. xboxhdm will do this job for you. There is no problem when the disk was used before. Just make sure the disk is lockable.

The C and E partitions of your new harddisk should contain the same files and folders as those partitions of the harddisk currently in your xbox.

regards.

[rutny]

Ok that looks simple enough really, one question:

QUOTE

Make sure you turn the virtual eeprom off also turn the shadowc off.

I do not know what these 2 are. I did FTP my  eeprom. Are the above two items....functions of the linux disc I will be creating?

[Heimdall]

You don't need to turn off virtual eeprom, but you do need to turn off shadow C. If you softmodded with Krayzie then run Krayzie extras, if you used Kingroach run System - NDURE toolset. If you aren't sure which softmod you used just boot with Frosty's Rescue disc. The LED will turn red, then you can back up your C drive and use it to build your xboxhdm disc.

[Heimdall]

SID 2.0 is a terrible softmod. Make your new disk with Kingroach NDURE 3.1 instead, and gain all the benefits of a recent, stable softmod.

Make sure that on your PC you have the following files easily to hand:
- the stock 5960 C dash files and folders from Slayers / AID / CASH
- a new set of Kingroach NDURE 3.1 C and E folders. Make these by running Kingroach NDURE 3.1 and simply selecting your Kernel version under "Kernel Selection" and "Create XBOXHDM Installer" - leave all other options at default.

Build your xboxhdm disc using the stock C from Slayers / AID, and the Kingroach NDURE 3.1 files you just made. Put the stock C in linux/C. Rename ndure.htm to ndure (no extension), and place it and the rest of the Kingroach 3.1 files in linux/ndure/, i.e. the Kingroach C and E directories should be in linux/ndure/C/ and linux/ndure/E/, with the ndure script named linux/ndure/ndure. Put eeprom.bin in /linux/eeprom/

Boot with xboxhdm, select option 1 - boot VGA Console, then type xboxhd, then select option 1 - Build A New Xbox HD from scratch. Once that has finished exit, then type xbrowser, run the ndure script, then select option 1. Exit the ndure script. Reboot the PC, select option 4 and type lockhd -a to lock the disk.

[Heimdall]

QUOTE

This whole Ndure thing is for the birds.

So why does everybody here recommend NDURE softmods? Perhaps it's because they work, and are reliable and fool proof.........unlike SID 2.0.

QUOTE

The files are impossible to locate.

You're not looking very hard....... Console Based Applications/exploits/_Packages/Kingroachs Installer/

[rutny]

Ok so let me see if I get this straight.
I want:
xboxhdm 1.9
Slayers 2.7
N-Dure 3.1

I extract the files from xboxhdm 1.9
I extract the files from  Slayers 2.7
I create files with N-Dure 3.1

ALL files from the slayer extraction I put in xboxhdm/linux/C
(2 Folders...Skins and SYSTEM then 6 files ... bios.bin, default.xbe, disk.bin, evox.ini, linuxbio.bin, and xecuter.bin)


Take files created by N-Dure (after selecting the proper kernel) and place them in
xboxhdm/linux/ndure
This folder would then C and E folders, and 1 file ndure after chaging the file name from ndure.htm

In the xboxhdm /linux/eeprom folder I will place my eeprom file.


How do I turn off virtual eeprom and shadow C? Will this be an option when I actually start the build?

[obcd]

The virtual eeprom and shadowc are 2 features of the ndure softmod on the xbox. The virtual eeprom uses a file on the harddisk (usually also named eeprom.bin) instead of the xbox eeprom chip to store the information unique for every xbox. The shadowc feature uses a file as C partition. This prevents the real C partition files with the softmod from being modified. You can turn those features off by creating a file with the name shadowc_OFF.bin and eeprom_OFF.bin on the E:\nkp11 folder or the E:\ root.

Those 2 features only exist with the ndure softmod.

If you don't turn off your shadowc, you will ftp the contents of the shadowc to your pc which do not contain your softmod. If you don't turn off your virtual eeprom, you can backup it's contents instead of those of the real eeprom. (Both are normally equal unless you modified one of them)

If you are using the Slayers files and the kingroach ndure 3.1 softmod, then you are building a xbox harddisk from scratch. The way I described it, you are simply using your existing softmod.

You can use a program like Qwix to extract the 5960 dashboard files from the Slayers iso. Yes, Slayers is for chip modded xboxes, but you are only using the stock M$dash files from it. Those files are on every xbox harddisk. If you updated your dashboard over the internet, it should be the 5960 version the softmod expects.

regards.

[Heimdall]

QUOTE

ALL files from the slayer extraction I put in xboxhdm/linux/C

No, just the files and folders from System/All/C/.

[Heimdall]

QUOTE

If so, at what point do you actually swap the drive?

You don't. You're building a new drive - no swapping involved. You have your CD / DVD drive on the second IDE, and your new 500GB drive as master on the first IDE. There are only four possible IDE locations, with the drive set at cable select and master that's 8 possible combinations - if you can't figure it out any other way then try them all, it will only take 10 minutes.

Then just follow the guide I gave you 8 posts back, last paragraph.

[rutny]

QUOTE

There are only four possible IDE locations, with the drive set at cable select and master that's 8 possible combinations - if you can't figure it out any other way then try them all, it will only take 10 minutes.

I have pretty much swapped the cables around and flip flopped everything...took me MUCH longer than 10 mins though
I didnt count the ways I tried though.

What 8 combos are you thinking?

[Heimdall]

4 IDE connectors for the new disk, 2 jumper settings (master and CS). 4 x 2 = 8......

[rutny]

Woot! I wanted to report back and let you know that I FINALLY got a 500GB Xbox! Thanks for the help gang!
A couple of  things:
1) Not sure why, but when I got the new HDD set up, I had to re-softmod it (not too big in issue)

2) Heimdall I can now say I stand corrected regarding my earlier comments on Ndure. I can now attest to the fact that it is/was a pretty user friendly softmod... it could not have been any easier once you get started. VERY user friendly I found.

3) The oddest thing is when my drive could not be found while trying to use xbhdm:
I SCOURED the net for the answer to this (even though the computer did recognise the drive)
The answer I got here is pretty much the same answer I found elsewhere. However, I stumbled on the real answer in a rather bumbling fashion. I do not have any idea why I did this, I just did ..and it worked.


Unlock the new drive before you start.    No seriously....I know  they arent supposed to be locked, but I want the locking/unlocking tool  to unlock it..then everything else went through with a breeze.


Thanks for all help!!!!!! I would NEVER have gotten here without it.

Cheers!

[Bomb Bloke]

There's one last step - all partitions larger then 256gb need to be formatted with XBPartitioner (reformatted in your case), or they'll eventually corrupt.

[rutny]

ugghh just re-read your post..refomatted ..damn ..what data will  I lose? Everything on F & G only?

EDIT: From what I have been reading, since I formatted an F and G (which neither would be over 256gb) I seem to be just fine...will wait on your answer though BB before I do much more tweaking.

Thanks!

[Bomb Bloke]

To my knowledge, the only way you can format a 500gb drive to have two partition each less then 256gb is to use XBPartitioner. All other formatting tools simply check to see what your BIOS expects to be used, and all known BIOS setups involve sticking the first ~129gb in the F partition then sticking what's left in the G partition (that'd be roughly 350gb in your case).

Reformatting a given partition affects only that partition but does wipe all the data it contains. That said, XBP does have options to wipe the entire drive. Read the documentation before using it.

XBP creates "custom" partitions, where the tables are stored on the drive itself (the ones defined in the BIOS get ignored). Only some BIOS types support this, but if you're using the NDure softmod you should be fine.