Print

[RiceCake]

Or run the wrong program and hose your EEPROM.

Or unlock your HD and not have an EEPROM backup.

Its all EEPROM problems still with Xbox exploits. Don't think that a dead Xbox clock problem is the only thing that threatens your softmods.

[Yuyu]

QUOTE(RiceCake @ Dec 24 2004, 10:36 AM)

Or run the wrong program and hose your EEPROM.

[devz3ro]

[micr0c0sm]

Checking xbins now....Please report about 10 after christmas - you can just leave us hanging there!!!! (well yeah you could but the anticipation could kill me)...

edit: not on xbins yet...

edit2: nevermind i am dumb thank you and merry christmas

[RiceCake]

"Regarding direct booting to update.xbe: whether or not you choose to
setup the real EEPROM contents such that the retail kernel will boot
C:\xboxdash.xbe directly does not really concern nkpatcher. Nkpatcher
10 can be used to make eeprom look good afterwards though. I haven't
tested it, but it looks like you don't need to zero out the whole
dashboard/user part in the real eeprom. It may be enough to just set
the language dword to zero (and recompute the checksum of course). I
don't know if you can do this with Config Magic already. It also looks
like update.xbe will default to English in that case so UXE should
work fine."

Bluh?
The EEPROM has nothing to do with booting the MS dashboard through the retail kernel. And what the rest of this stuff about languages...?

Anyhow, look cool. I'll have to check it out.

[micr0c0sm]

WOAH! Dear lord. Amazing. Best. Scene. Release. Ever.
I wonder if you know how much you really are appreciated (everyone involved in this project)...


Anyway for the questions:
Please tell me i read this right (its 3 am).
With nkpatcher10, if i used say UXE and nkpatcher10 i can go on xbox live as long as i keep my retail size hard drive? The reason I say this is because the eeprom feature - wasnt that the only thing being checked by xbox live along with the hard drive size?
Also, if this is the case....was it the entire hard drive that was checked or just the C? Because if we had a shadowed C to look like the retail AND the fake eeprom set up correctly...it seems like this means that nkpatcher can do things modchips cant!! If it was the whole drive... is it conceivable to shadow the entire xbox (maybe even the d with the .iso features) to allow for this?

I hope im not just dellusional...

Even so there is no absolutely no reason not to use nkpatcher over the bios loaders...
Softmod UXE with nkpatcher is the way to go.

Merry christmas indeed!

[emotion]

everything works fine except dash2gam 2.3 dashboard... it won't load from unleashx using nkpatcher 9,10 instead of nkpatcher 8.1 where dash2gam worked fine with  
(with modchip on dash2gam 2.3 works fine too)

i'm using dash2gam for dvd playback only and i won't switch to another player because i'm pleased with it

thanks for your great work anyway

[wafflezone]

QUOTE(micr0c0sm @ Dec 25 2004, 09:22 AM)

I hope im not just dellusional...

[Kyro]

let's say I have "ACTUAL_C_DRIVE" defined to partition "7" so now i have drive "c" & "g" identical (partition "2" & "7")
if i modify files on drive "c" (or "g"), it's also modified on "g" (or "c") ?

So basically, i can use a "shadowc.img" file on drive "g" (with "VIRTUAL_C_PATH" defined to '\Device\Harddisk0\Partition7\shadowc.img')

ok now the shadowc.img content is in drive "c" and, "g" drive is still the real "c" drive? Am i still right?

So, if i am right... let's say, i screw with "g" drive, my box may not boot properly ? cause the real "c" would be screwed?

My point is that i just didn t want real c drive to be accessible, but of course i may have not understand the feature  

Another thing, i guess it s not possible to :
define "VIRTUAL_C_DRIVE" to "2"
and "VIRTUAL_C_PATH" to '\Device\Harddisk0\Partition2\shadowc\shadowc.img'
nkpatcher would 1st boot thanks to an exploited "c" drive and then use the shadowc.img directly on drive "c"
is it?  

Anyway, merry xmas everyone, i gotta go eat my xmas family big lunch  

[RolfLobker]

nkpatcher9 does not appear to boot with:

%define VIRTUAL_C_DRIVE 2
%define VIRTUAL_C_PATH '\Device\Harddisk0\Partition2\shadowc\shadowc.img'

Assembled with:

%define VIRTUAL_C_DRIVE 2
%define ACTUAL_C_DRIVE 7
%define VIRTUAL_C_PATH '\Device\Harddisk0\Partition2\shadowc\shadowc.img'

The 'real' c-partition = G
The 'fake' c-partition = C
The Shadowc-file resides in E:\shadowc\

This way you have access to both the 'real' and the 'fake' C-partition.

Up until now I found no way to hide both the 'real' c-contents and the shadowc-file.

Some comments in the accompanying readme-file and in this thread suggest that it is possible to 'hide' the shadow-c file in the 'real' c-partition but allas, I did not manage to achive this (through countless hours of testing)

One possibilitie though is to actually have a G-partition (you'll need >137GB HDD for this. Put the shadow-c on the G-partition and instruct your software not to use the G-partition.
But this is farfetched and means at least 12,5 Gigabytes of unused space (you need at least a 160 GB HDD for this, only 137GB will be actually usefull for you)

Edit:
1) I allready contacted PedrosPad on this to see if it was my misinterpretation / faulty setup.
2) nkpatcher9 and 10 cannot be found on xbins yet, although bot onjoin allready claims they should be there.

[RolfLobker]

I wish everyone on the board a very merry christmas and a happy new year.
With special thanks to rmenhal without whom the modding-scene concerning softmods would have been primitive when compaired to where we are now.

Special thanks to all who helped in finding exploits and to rmenhal who made them feasable by creating the UXE-fonts and Nkpatcher which really show off his talents in assembler and creating a user-friendly approach to assembling @ home using well explained remarks in his sources and easy to adjust parameters/variables in his sources.

(*)
I created the 200 MB dummy file using old-skool dos-skills:

Start > Execute > CMD
COPY CON dummy.bin
(alt-255)(alt-255)(alt-255)(alt-255)(alt-255)
(CTRL-Z)
COPY CON cdummy.bat
COPY /B dummy.bin + /B dummy.bin + /B dummy.bin shadowc.img
DEL dummy.bin
REN shadowc.img dummy.bin
(CTRL-Z)
cdummy (times 16: cdummy (RETURN), cdummy (RETURN) etc etc)

[total_ass]

i am sort of confused to be honest. a shadow eeprom is what i am seeing? i actually was thinking of something like this a few days ago, but i thought it would be beyond anyone to do

so is this basically the same as shadow C? it mounts eeprom.bin as the 'real' eeprom and then any changes to it are all confined to the file? please correct me if im wrong as i don't fully understand what i am exactly reading here.

i take two days away, two damn days and i come back and two new versions of nkpatcher have been released. i suppose its time to go buy an exploitable game and then take ltools off and manually install UXE (i still use original UDE ) with nkpatcher 10. then the xecuter 3 can go to hell.

[Kyro]

QUOTE(RolfLobker @ Dec 25 2004, 02:49 PM)

I managed to do the following:

(For this to work you should not have an actual G-partition. Use '.06' (rest goes to F))

First create a 200 MB file containing NULL's (*)

Assemble nkpatcher with the following settings:

%define VIRTUAL_C_DRIVE 2
%define ACTUAL_C_DRIVE 7
%define VIRTUAL_C_PATH '\Device\Harddisk0\Partition7\shadowc.img'

This does the following:

Actual C becomes G
shadowc.img is located in the G which is in reality the real C
G:\shadowc.img becomes new 'fake' C

You can now format C (which is in reality c:\shadowc.img which became g:\shadowc.img)

Result:
An empty C-partition with 200 Megabytes of free space
A G-partition containing the real contents of the C-partition which contains shadowc.img

If you then proceed to adept all software you use to not use the G-partition you will in fact not be able to see the contents of the real c-partition and therefore also not be able to see the shadowc.img file.

A simple 'enable F drive = true' in your xbox apps will make the G-partition (which is the real C-contents including shadowc.img) visible and vulnerable again.[...]

I confirm this, i got it working this way, but now i have another pb...

i ve put all the files needed for the exploit to work on the real "c" drive, so nkpatcher needs to launch my dashboard (unleashx) from partition "7" (it cant launch from partition 2, cause it is being shadowed)

So when my box boot unleash shows up, but i cant see my skins, cant save any settings... it seems unleashx doesn t like to be launch from a virtual drive (even if i enable "g" drive in config.xml)

Maybe it s a specific unleashx pb, i ll try to launch evox or ava from the "g" virtual drive to see, but now i ve just put unleash on drive "e" and enough testing, i m back to the christmas eating eheh

[pSyCo]

Merry Christmas to all...

I have a question

Alright, I fully understand the point of shadow c drive (i had to use it yesturday when modding my nephews xbox which he will be unwrapping today.... because without doing so, his topspin/ncaa disc wouldn't boot that came with the xbox)... but, what i do not understand, is why on earth you would need virtual eeprom. You can't get on xb-live *period* if you have nkpatcher installed, am I correct? I mean, it's not like you can choose *reboot in orig mode* and hop online with halo 2 .... soooooooo .... what's the point?

I'm not being an ass, i'm really wanting to know.

--Polymira

[born4trance]

QUOTE(devz3ro @ Dec 25 2004, 07:22 AM)

Merry Christmas to all.