Post by: obcd on April 07, 2009, 02:23:00 PM
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.
Post by: rutny on April 07, 2009, 02:39:00 PM
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?
Post by: Heimdall on April 07, 2009, 03:08:00 PM
Post by: Heimdall on April 07, 2009, 04:10:00 PM
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.
Post by: Heimdall on April 07, 2009, 06:50:00 PM
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/
Post by: rutny on April 07, 2009, 08:45:00 PM
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?
Post by: obcd on April 08, 2009, 02:00:00 AM
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.
Post by: Heimdall on April 08, 2009, 02:54:00 AM
QUOTE
ALL files from the slayer extraction I put in xboxhdm/linux/C
No, just the files and folders from System/All/C/.Post by: Heimdall on April 17, 2009, 03:33:00 AM
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.
Post by: rutny on April 17, 2009, 09:43:00 AM
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?
Post by: Heimdall on April 17, 2009, 09:51:00 AM
Post by: rutny on April 18, 2009, 12:32:00 PM
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!
Post by: Bomb Bloke on April 18, 2009, 08:33:00 PM
Post by: rutny on April 19, 2009, 11:22:00 PM
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!
Post by: Bomb Bloke on April 20, 2009, 02:04:00 AM
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.
Post by: Heimdall on April 20, 2009, 09:47:00 AM
Post by: xbnubi on June 05, 2009, 07:10:00 PM
QUOTE(Heimdall @ Apr 7 2009, 06:10 PM) 
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/
Couple of things here (assuming that -all- you've got is a valid eeprom.bin file, and a new blank HD):
- Is your original kernel relevant when creating C/E with Ndure 3.1, if you're going to be using the new kernel from Slayer's disc? Should you not select kernel 5960 in Ndure to match Slayer's files? (is there some sort of firmware issue with the kernel selection as well?)
- you say "...leave all other options at default." (during the Ndure 3.1 install) The default "Ndure Retail" setting has NOTHING selected but "Core Files". Is that what you mean, or should you select the other 4 install options as well? (i.e. check: softmod & nkpather options, UDDAE, xboxhdm installer, as well as the Kernel)
- as you corrected later, Slayer's 2.7 does not have an "aid" directory. You might want to make your quick tip post a full tutorial referring to Slayer's 2.7, as this is the first comprehensive, and understandable, solution I've seen to re-build a new HD without your original backup.
Thanks.
Post by: unmesh on June 05, 2009, 07:25:00 PM
I have a Xbox that was softmodded using Krayzie's Ndure installer. In the process of upgrading the hard drive, I copied the eeprom.bin file and the contents of the C and E drives to my PC, created a CD using xboxhdm, booted with it and created a new hard drive. Unfortunately, the Xbox with the newly created hard drive boots to the MS dash instead of the UnleashX dash as the original disk does.
Am I running into the "shadow" problem that was referenced earlier in the thread? If so, what do I do to get the new drive to work just the same as the old one?
Thanks.
Post by: xbnubi on June 05, 2009, 07:34:00 PM
QUOTE(xbnubi @ Jun 5 2009, 09:10 PM)
Couple of things here (assuming that -all- you've got is a valid eeprom.bin file, and a new blank HD):
- Is your original kernel relevant when creating C/E with Ndure 3.1, if you're going to be using the new kernel from Slayer's disc? Should you not select kernel 5960 in Ndure to match Slayer's files? (is there some sort of firmware issue with the kernel selection as well?)
- you say "...leave all other options at default." (during the Ndure 3.1 install) The default "Ndure Retail" setting has NOTHING selected but "Core Files". Is that what you mean, or should you select the other 4 install options as well? (i.e. check: softmod & nkpather options, UDDAE, xboxhdm installer, as well as the Kernel)
- as you corrected later, Slayer's 2.7 does not have an "aid" directory. You might want to make your quick tip post a full tutorial referring to Slayer's 2.7, as this is the first comprehensive, and understandable, solution I've seen to re-build a new HD without your original backup.
Thanks.
Another thing I noticed:
- The step: "...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/..." is a bit confusing, and unneeded, as Ndure will do all that for you if you simply point the installer to the: xboxhdm/linux folder.
Thanks again for a good solution.
Post by: ldotsfan on June 05, 2009, 07:34:00 PM
QUOTE(unmesh @ Jun 6 2009, 09:25 AM)
Am I running into the "shadow" problem that was referenced earlier in the thread? If so, what do I do to get the new drive to work just the same as the old one?
For Krayzie's Ndure, use Krayzie's Extras Professional Mode to ftp the real C drive contents over. Alternatively boot with Frosty's Xbox rescue disc and ftp the contents of C over when you are building the contents of C in xboxhdm iso.
Post by: Bomb Bloke on June 05, 2009, 08:02:00 PM
QUOTE(xbnubi @ Jun 6 2009, 09:10 AM)
- Is your original kernel relevant when creating C/E with Ndure 3.1, if you're going to be using the new kernel from Slayer's disc? Should you not select kernel 5960 in Ndure to match Slayer's files? (is there some sort of firmware issue with the kernel selection as well?)
There's no "kernel 5960". Your kernel version represents the BIOS that gets loaded out of your TSOP chip on the motherboard. Unless you're planning on flashing that TSOP or installing a modchip, your kernel cannot be changed - so the kernel the MS dash says it's using is the kernel you tell NDure you're using.
When installing NDure, you're best off to update your MS dash (which is something completely different) to 5960 before proceeding. Throw in a copy of Halo 2 then attempt to logon to Live. You don't need a network cable or Live account, it should just update the dash. A newer X-Box Live enabled game will also work.
QUOTE(xbnubi @ Jun 6 2009, 09:10 AM)
- you say "...leave all other options at default." (during the Ndure 3.1 install) The default "Ndure Retail" setting has NOTHING selected but "Core Files". Is that what you mean, or should you select the other 4 install options as well? (i.e. check: softmod & nkpather options, UDDAE, xboxhdm installer, as well as the Kernel)
Also select your kernel version, and if you're planning on using XBoxHDM... well, I'm sure you can guess what to tick for that. By all means tick the other options if you know what they do and want them, but otherwise leave them unticked.
Post by: Bomb Bloke on June 05, 2009, 10:18:00 PM
QUOTE(xbnubi @ Jun 6 2009, 11:33 AM)
But I guess the bottom line is that since kernel is related to on-board firmware (not R/W media of any sort), it's probably the best bet that you select the correct version, right?
Technically that firmware IS re-writable, but you need a working softmod to do that (though the softmod can be removed entirely afterwards). This is my preferred method of console modding.
But yes, while using the NDure softmod, it's a good idea to give it the correct firmware info.
QUOTE(xbnubi @ Jun 6 2009, 11:33 AM)
Anyhoo, did the clean HD install with Ndure 3.1 and Slayer's 2.7 and got it working, but I'm still a little fuzzy on whether or not you -need- any of the other Ndure options. There are other tutorials (http://www.boards.ie/vbulletin/showthread.php?t=2055256404) that suggest you select everything in Ndure 3.1, but as I found out this is actually a bad idea!
The problem lies with inadvertently selecting the "use Nkpatcher RGB" checkbox, which will seriously screw-up your component HD output!
The problem lies with inadvertently selecting the "use Nkpatcher RGB" checkbox, which will seriously screw-up your component HD output!
You certainly do not need, nor usually want, to select all options.
RGB mode, for example, patches the system so that you can use a VGA out (and connect to a computer monitor, for example) - but is useless if you wish to use a TV. Stuff like the clock check is quite pointless due to XBMC/UnleashX's ability to set the time using an internet based server, and the NKPatcher settings regarding partitions layouts are all made redundant in that XBPartitioner overrides them anyway (and you need to use XBP for pretty much all decent sized drives).
There's a PDF file included with Kingroach's NDure 3.1 which explains the other options.
Post by: unmesh on June 06, 2009, 01:35:00 AM
QUOTE(ldotsfan @ Jun 5 2009, 06:34 PM)
For Krayzie's Ndure, use Krayzie's Extras Professional Mode to ftp the real C drive contents over. Alternatively boot with Frosty's Xbox rescue disc and ftp the contents of C over when you are building the contents of C in xboxhdm iso.
I have an earlier Xbox version with the Thompson optical drive and have not yet been able to get it to read anything from burned media, whether CD-R or DVD+R or DVD-R
I have found the link for the Extras download and will try that out.
I might also try out the "Clone HD" function in xboxhdm
Thanks much.