I'm not using the RGB one and I'm getting the strange error, I never used the RGB. When using the installer I left the options for nkpatcher blank and I never changed the setting for it in ndts.

Big thanks to kingroach! Much appreciated for helping me mod my Xbox's!

where is this in xbins?
i looked all around and i can't find it.
and will this work with the ndure softmod tutorial stickied here?
are there any changed options or anything??

thanks!

Roughly, console apps/exploits/_packages/kingroach.

Does this release include the fixed backup script that version 3.0 requires, as per the "How to Softmod Your Xbox Using XboxHDM (Ndure)" thread?

it has all the updates..

Can somebody explain to me how the LED.BIN file works. All i want is the led to be always green. But when i use the standard install option its always orange.

I'm about to use this on my second xbox , and I had a question.

On my first box I had your ndure3 release, and after modifying a file for an n64 emulator, I was unable to get back into the unleashx dash. Even after doing 2 hotswaps, fresh installing, and successfully having ndure install, I still couldn't get unleashx to start. (though I could get into the M$ dash np, with booting on the eject button)

The UnleashX Logo would just flash over and over, no matter what. (this being the reason why I'm doing the second box.)

To the question: If I end up encountering the same problems on this box with the 3.1 release; what could be causing this, and what can I do to fix it?

create a 1 byte file with a hex editor

I have the same problem and downloading Slayers disk, and I just wonder, what is Slayers disk? Is it a new copy of MS dash?
I've a mistake not updating MS dash before softmodding, thats, probably, why I have this error 21.
I'm waiting for this disk and I'll try to replace C:\, but if I fail do I need to re-softmod again?

Tried replacing MS Dash from slayers disk - didnt help

Sorted out reinstalling softmod from AIDeluxe

I was impressed, even if I, accidently, formated C:\ drive it recreated files and started Ok.

Thanks kingroach. Ne1 know why when I try to run xbox live it just returns me to the main menu. Do I need to choose one of the 2 xbox live options from the installer. Thx

I have used NDURE 3.1 and XboxHDM on 3 different Xboxes. I copy the "C" and"E" folders that NDURE creates into the "C" and "E" folder in XboxHDM - no other files. All works well, except for the following (same for all 3 boxes):

1) When I look at drive "C" (via FTP or local filemanager) there are NO files and I cannot copy any files to "C".

2) In XBMC, the changes to the screen settings (widescreen/normal, 480P/720P/1080i) do not "stick" when the XBox is restarted.

3) I cannot "boot" into the MS dash.

Any help for any or all of the above?

Also, I do not use XBL for these XBoxes at all, so I do not need any "protection" for this.

Thanks

easy fix
the shadowc is write protected (bug in xboxHDM)
add any file named E:\NKP11\shadowC_off.bin
reboot then FTP the C:\shadowc\shadowc.img to your PC and check it's attributes, uncheck read only if set,
FTP it back...
delete the shadowC_off.bin
reboot and add MS dash the files to the C:\

add any file E:\NKP11\eeprom_off.bin
leave it or update the eeprom.bin file after setting the HD settings in the MS dash

Alright...

I successfully (after painful problems) modded my Xbox last night.

Few questions for you out there....


I think I am getting Unleashx dash when using both power and reset.
Correct me if I am wrong... but all I need to do is run NDTS and FTP in Ndure's Retail installation files instead?
OR ... Do I just mess around with the xodash files (xbe) ???
OR... Do I just need to place the boot1.bin file directly into E drive ??? That does some toggling thing right?
Is all this related?

Another question is... I will want to play games with Xbox Live.... Do I need to be able to boot to the original MS Dash?


I read somewhere this quote "disable virtual eeprom if you change HDTV frequently"
Any dangers to having the virtual eeprom permanently disabled?

Last question....
Is there anyway I can have two MS dashes at the same time? Like I can jump from one to another? I would like both XBMC and Unleashx. Is this possible, or can I just have one or the other in E:/dash and then have to reboot the Xbox???

I have no idea how to get this NKPatcher to work. I'm trying to get it to run 480i ONLY so I can use my component cables. I saw someone else earlier in the thread say they fixed the problem by creating a video.bin file, but I don't know what to put in the file, and if it can be with a text editor or a hex editor only.

I went in and edited the config and config_runtime files and commented out the force progressive option. Then I ran make_runtime, then I ran make_nkp11. What am I supposed to do now?

Can I just make a video.bin file and put something in there to make it force to go 480i?

text "0" or hex "00"
but the MS dash must be set first to 480i only (using E:\NKP11\eeprom_off.bin)

where abouts on xbins ftp is this file? cant find it

Issue "site search kingroach" custom command with your ftp client.

well i have the following problem: i been working with uxe then updated to ndure 3.0 but someone deactivate ndure and no game for activate again so now i will update to 3.1 by hotswap, do you think that ndure will work again?, thanks

Kingroach Ndure 3.0 doesn't use game disc to activate the softmod. Are you referring to Krayzie's Ndure 1.1?

If hotswapping is correctly done, your hdd will be temporarily unlocked and you have access to its contents. I suggest you get a clean set of msdash files from Slayer's or CASH 1.1. Together with Kingroach Ndure 3.1, you can apply the softmod again after formatting everything on C drive. The prior deletion is to prevent residue files from earlier softmods from interfering with the softmod process. Read the pinned topic for the details on how to apply the softmod correctly.

After you are done, grab your eeprom backup to your PC.

I took a clean C and E installation, copied over the files to my PC, along with the EEprom. Went in XBoxHDM, created a new drive with non-modded files, locked it.

Then I loaded the evox exploit to get FTP access, and deleted the entire C drive, put the Ndure 3.1 patched C drive and the E drive on the hard drive. Everything seems to be working fine.

Did I follow a proper install procedure?

You could have installed the kingroach ndure files during the xboxhdm stage. But the end outcome is the same - you have a working softmodded xbox

I softmodded bij Xbox using ndure 3.1 and xboxhdm the other day. Thanks guys for such a complete and easy to use product.

I tried to backup to EEPROM using the Unleashx in E:\ndts. After the backup utils starts the xbox resets and the "default" unleashx starts. I now have an EEPROM.BIN in E:\NKP11 (256bytes).

However, when I try to copy this file to my computer using FTP I get "file not found", although the file seem to be just sitting there. (It show up in the directory listing).

I started "E:\ndts\unleashx.xbe" instead of "E:\ndts\default.xbe". Using default.xbe the ndure toolset now works! I just grabbed my EEPROM.

ive been trying to find this file. can someone elaborate as to where its at? without the hoopwork of running around irc?

I installed this softmod on another Xbox with the non-online, singleboot method. One problem though. How do I access the msdash to change video settings? Do I need to just disable virtual eeprom, and go into NTDS, so I can see the shadowc? What will the file for the original msdash be called?

Thanks!

Did the original unmodded xbox have msdash ver 5960? e:\ndts\default.xbe will temporarily disable virtual eeprom. What does this mean? Did you invoke the ndure script with xbrowser during installation or your C drive was a total replacement with kingroach ndure's C folder?

Check if you have a xb0xdash.xbe (there's a zero) on C drive after you invoke ndts

I installed Ndure 3.1 (again: THANKS so much!) but without the LBA48 nkpatcher option.

Afterwards I stumbled upon an old IDE Seagate 200Gb drive that was lying around, so I used xboxhdm (and the tutorial on this site) to put that in.

Xboxhdm created an F: drive (120 Gb or so) and a G: partition that I cannot see (I saw it using xboxpartitioner). I guess I need to activate the LBA48 bios patch before I can use the G: drive.

I googled, read the readme's but I can't seem to figure it out. How do I enable the LBA48. Do I have to reinstall NDure 3.1? (I originally installled ndure without LBA48)

Might be simpler - enable G drive in unleashX.

Anyway the nkpatcher .67 option (F and G drives) is available from e:\ndts\default.xbe (Ndure toolset).

Thanks for the swift reply! Anyway, I enabled nkpatcher .67 in the ndure toolset. I know it works because I changed to retail and the CD open button launches the Xbox Live dash.

When I enable G in UnleashX I do not see a G: drive, but the F: seems empty [in UnleashX as well as xbmc]! (Ouch! I didn't dare to write to F:) Disableing G: and rebooting returned the F: drive back to "normal".

... now I'm confused!

Okay, so after reading more about nkpatcher .67, I figured out what .67 means, partition 6 (F) and 7 (G) become one big F:
Unfortunately, I seem to lose the data on partition 6 (old F) by enabling this.

So my question is: Can I enable G: whilst DISABLING nkpatcher .67 and use F: and G: as seperate partitions without dataloss??

no Nkpatcher .67 means that you will get F and G drive and nkpatcher .06 means that only F drive will be present. If you want F and G drive, best method will be to disable G drive in unleahx so that you can access F drive and then backup F drive contents to your computer. Now, turn on G drive and format both F and G drive using "xbpartitioner".

Okay, thats what I will try. Thanks again.

Just reporting back the results for others:

Turning on nkpatcher .67 did not really help me as UnleashX refused to give me "G" even after enabling it in the settings/storage menu. Enabling Nkpatcher .67 did however increase F: to 180+Gb. (size of partition 6+7).

After formatting with UnleashX I ended up with a big partition 6 (F) with 180Gb. (16kb clusters). Because I was afraid of data corruption, I repartitioned/formated with xboxpartitioner to 120Gb F: and 50Gb G:

This seems to work in both UnleashX and XBMC...

Now I'm ftping back 50Gb...

Hey everyone, I just used the Ndure installer for the first time and I was able to successfully softmod my Xbox, but I didn't realize until afterwards that I was selecting too many options to allow for booting to the MS dash with the eject button. How would I go about installing the mod correctly now to allow for dual booting? I tried re-using the installer to create the appropriate files on my computer, and then I ftp'ed into the real C:, deleted everything, and uploaded the newly created C:, but I'm assuming that this wasn't the right thing to do because it didn't work (I get a service error when booting with the eject button). I can still boot into my regular dash with the power button, so I'm not too alarmed (yet), but I'd like to get this working. Thanks.

1. Backup your eeprom with e:\ndts\default.xbe and ftp to PC first.
2. Do you have a source of msdash files ver 5960? CASH 1.1 disc or Slayer's 2.7 will have those.

Thanks ldotsfan. I tried using the ndts UnleashX to make a backup of my EEPROM, but I'm not sure where it stored it. I had already used ConfigMagic to backup my EEPROM before I started messing around with the files, so I'm assuming that this would suffice? I'd still like to know where UnleashX stores its EEPROM backup though for future reference. And I'm getting Slayer's 2.7 now, so just let me know what the next steps I need to take are. Thanks for your help.

Try E:\NKP11 for the eeprom location.

Next steps:
1. Disable shadow C through executing ndts's default.xbe
2. Ftp msdash files over to C drive.
3. Select nkpatcher retail setup in the installer. (Check the document that comes with kingroach installer)
4. Ftp contents of C folder created by Kingroach's Ndure installer to C drive, ensure ernie.xtf is copied over before xbox.xtf to hdd, both files are in xodash folder. Allow it to override any existing files.
5. Ftp contents of E folder over to E drive.

There might be a way to do it from within ndts itself but I can't recall now. Maybe if kingroach himself comes by, he'll be able to advise.

In Slayer's 2.7, the msdash files are located at "/SYSTEM/ALL/c/", correct? Also, do these options look ok for the installer? Am I supposed to select Core files as well? And I'm choosing my own kernel in the selection?



Thanks.

1. dash location is correct.
2. Options look Ok, you can refer to the pdf documentation or mouse-over the options.
3. If you know the kernel version, select the specific one. Otherwise generic one will be applied.

I tried to follow your directions, but when I got to overwriting the retail dash files with the ndure ones, I think the C: drive was too full and didn't allow all of the files to transfer over. I didn't realize this until after I restarted the Xbox, and now it can't get past the flubber animation. I guess I'll have to recover the hard drive now, but is the C: drive getting too full a known problem?

1. Did you delete away everything on C drive prior to the copying of files?
2. Not to worry, with eeprom.bin on PC, you can always use xboxhdm to recover.
3. I think the pdf documentation mentioned about this:

Did you get down to reading the pdf before starting?

I did read the pdf before starting, and I do remember reading the part about settings_adoc.xip, but forgot to check it when it came time to delete everything in the C: drive, which I did. Could that be the cause of the C: drive becoming full? Also, just for my own education, is there a reason why ernie.xtf has to be transferred before xbox.xtf?

Not possible to tell now unless you have a file listing of C drive. Ernie.xtf before xbox.xtf? http://xguides.xbox-scene.com/tikiwiki/tik...ure+XBE+Exploit
something to do with the font exploit itself. Resultant is a blank screen.

What happens if the XBMC does not start and the default.XBE is overwritten with the XBMC one (I plan to use the XBMC Shortcut utility)?
The file called shadowc_off.bin can be any file with that name or there is a dedicated one ?
I've read that for having a shadow C write enble, I have to replace the shadowC.IMG with the one on the computer crated under NDURE\C\SHADOWC. Is this because the SHADOWC.IMG on the E folder is read only ?
What happens if I write a wrong file ?


Sorry if I'm making so many questions but it's the first time I play with a soft mod and I don't want to open again the XBOX for a new hotswap.

Thanks in advance.

miazza

You can boot using Frosty's or Slayers or CASH, or any boot disc, and use ftp to fix the problem.



Any file. Why do you want to disable virtual C?



Not sure what you mean. The standard virtual C is created in NDURE\C\ShadowC\, and is writeable. You just copy it across as part of the NDURE softmod.

If the default.xbe started by the softmod is not a dashboard, it is possible that you need to fix it by connecting the xbox harddisk to a pc again. That's why it is important that you have a backup of the xbox eeprom.bin file. If the softmod can't locate a default.xbe, it will search alternative locations like the dvd drive for a valid file.



The softmod only checks the existance of that filename. The contents of the file don't matter. The location is different between nkpatcher10 and nkpatcher11. If you have a NKP11 folder on your E partition, you will need to place the file there.



With a wrong file, you will end up again with an unwritable shadowc partition. It is not the shadowc.img file on the E that is "read only", it is the one on the C in the "shadowc" folder. Even if that file contains nonsens, a format of the shadowc partition should solve the issue. If the file is only 5MB long, the shadowc partition will only have that size as well. (and the M$dash files won't fit on it.)
In a perfect world, you indeed don't need to touch the shadowc.img file. If you can't read and format your shadowc partition, you will need to fix it.

regards.

Thanks for the help.
I have now installed XBMC as a default dash and I also decided that the Shadow C is not a major Issue because the file image was only 64 Mb.

When I use the default.xbe in the ndts folder, i see that there are about 250 Mb free space.
Does this mean that i can have a shadow C of 200Mb ?

Thanks

miazza

When you run ndts default.xbe you can see shadowC.img somewhere on C drive.