xboxscene.org forums

Pages: 1 ... 4 5 [6] 7 8 ... 23

Author Topic: Reintroducing Kernel Patching - Nkpatcher  (Read 1373 times)

brianbtran

  • Archived User
  • Newbie
  • *
  • Posts: 1
Reintroducing Kernel Patching - Nkpatcher
« Reply #75 on: July 02, 2004, 05:05:00 AM »

sad.gif

basically, 5838 is a useless xbox for now. sad.gif
Logged

old engineer

  • Archived User
  • Full Member
  • *
  • Posts: 155
Reintroducing Kernel Patching - Nkpatcher
« Reply #76 on: July 02, 2004, 05:47:00 AM »

QUOTE (Spectracide @ Jul 2 2004, 01:47 PM)
Run your MechAssault save with Evox.  When you get FTP working, connect to your XBox and install Evox to your C: drive with Evox being evoxdash.xbe.  That is what nkpatcher looks for.
Now take your Mechassault Save and open it on your computer.  Remove default.xbe (and any other evox files if you wish) and put in nkpatcher.xbe (renamed to default.xbe).  Now MechAssault with execute nkpatcher, and look for evoxdash.xbe on C: and run it.

Tried this m8 still crunched out to error 21.

...Still, thanks for trying, anymore ideas appreciated.
Logged

pugnip

  • Archived User
  • Newbie
  • *
  • Posts: 8
Reintroducing Kernel Patching - Nkpatcher
« Reply #77 on: July 02, 2004, 07:17:00 AM »

I have a 5713 and running a gamesave exploit and the eject fix isn't working
can anyone have any ideas?



Pugnip.
Logged

old engineer

  • Archived User
  • Full Member
  • *
  • Posts: 155
Reintroducing Kernel Patching - Nkpatcher
« Reply #78 on: July 02, 2004, 07:32:00 AM »

Can u please explain how u got nkpatcher to work in the first place m8????
Logged

krayzie

  • Archived User
  • Hero Member
  • *
  • Posts: 3350
Reintroducing Kernel Patching - Nkpatcher
« Reply #79 on: July 02, 2004, 07:35:00 AM »

QUOTE (pugnip @ Jul 2 2004, 04:17 PM)
I have a 5713 and running a gamesave exploit and the eject fix isn't working
can anyone have any ideas?



Pugnip.

Yeah it's because the reset on eject stays present when running from a gamesave and can't be fixed. You can only play stuff of the hd.
Logged

pugnip

  • Archived User
  • Newbie
  • *
  • Posts: 8
Reintroducing Kernel Patching - Nkpatcher
« Reply #80 on: July 02, 2004, 07:50:00 AM »

Is there anyway to fix this?



Pugnip.
Logged

krayzie

  • Archived User
  • Hero Member
  • *
  • Posts: 3350
Reintroducing Kernel Patching - Nkpatcher
« Reply #81 on: July 02, 2004, 08:14:00 AM »

QUOTE (pugnip @ Jul 2 2004, 04:50 PM)
Is there anyway to fix this?



Pugnip.

Can't you read?
Logged

Deciphile

  • Archived User
  • Newbie
  • *
  • Posts: 27
Reintroducing Kernel Patching - Nkpatcher
« Reply #82 on: July 02, 2004, 08:17:00 AM »

2 nd to verify:


nkpatcher5 runs on 5838.
Logged

devz3ro

  • Archived User
  • Full Member
  • *
  • Posts: 229
Reintroducing Kernel Patching - Nkpatcher
« Reply #83 on: July 02, 2004, 09:13:00 AM »

To: old engineer & pugnip

I suggest the two of you start reading in the "GameSave Exploit" forum and learn how everything works before coming to this one. Most of us understand that ROE will *always* exist (with no fix ever) when you are using a gamesave exploit. Installing gamesave exploits with different *.xbes is not difficult at all. A quick explanation would be to go inside the gamesave folder, replace the xbe (usually in 000000000000) with the nkpatchers xbe and then place your favorite renamed to evoxdash.xbe dashboard in the root of your C drive. You may now execute unsigned xbes from your hard drive and not your dvd drive (Yes, you have to transfer whatever you want to execute via ftp to the xbox). Opening your dvd drive after you did all of the above will always cause the xbox to reboot.

-devz3ro

http://sh0x.tk/
Logged

old engineer

  • Archived User
  • Full Member
  • *
  • Posts: 155
Reintroducing Kernel Patching - Nkpatcher
« Reply #84 on: July 02, 2004, 09:35:00 AM »

sad.gif

...I'm not a n00b, I know how to softmod, TSOP flash and chip. I understand UDE, I know the difference between a gamesave exploit and a dashboard exploit!!!!!!!!!!

...I muck around with this stuff all the time, I understand about Kernal versions and ROE etc, etc, etc.

The ONLY reason I asked for an explanation from someone who got this working is that I've done EVERYTHING that I consider correct but it still won't execute nkpatcher, it just goes to a error 21 screen!!!!!!!!

K = 5713

evoxdash.xbe is on C:

nkpatcher5.xbe is renamed default.xbe and resides in mech assault save folder in Udata on E:

Any clues!!!!!!!!!






Logged

Spectracide

  • Archived User
  • Newbie
  • *
  • Posts: 21
Reintroducing Kernel Patching - Nkpatcher
« Reply #85 on: July 02, 2004, 09:48:00 AM »

tongue.gif
Logged

Deciphile

  • Archived User
  • Newbie
  • *
  • Posts: 27
Reintroducing Kernel Patching - Nkpatcher
« Reply #86 on: July 02, 2004, 11:26:00 AM »

@ OLD Engineer

I don't know if this helps since I'm running on 5838 but what I did was to:


1. Of course run the game save hack that came from easy pheonix loader . The one that defaults to MXM.

2. ftp'ed to xbox and transfered nkpatcher5 tarball contents to E:/  root

3. transfered all contents of the latest version of Evo-x (minus readmes and nfo's) folder to C:/ root

4. rebooted and ran gamesave hack again to go back to MXM dash.

5. went to dashboards folder and hit nkpatcher it then executed and put me into the evo-x dash which is where I wanted to be.

I tried hex editing the gamesave but it would frag everytime so I found this to be an alternative.

Logged

Deciphile

  • Archived User
  • Newbie
  • *
  • Posts: 27
Reintroducing Kernel Patching - Nkpatcher
« Reply #87 on: July 02, 2004, 11:36:00 AM »

Yes that is correct. every time I tried a different method it would frag. Glad I could help you out.
Logged

gronne

  • Archived User
  • Hero Member
  • *
  • Posts: 568
Reintroducing Kernel Patching - Nkpatcher
« Reply #88 on: July 02, 2004, 02:17:00 PM »

QUOTE (brianbtran @ Jul 2 2004, 10:27 PM)
man this sucks for 5838 users.  the gamesave exploit requires the original game.  a backup does not even work.

I rented 007 auf and have 4 more days to return. aaaaaaaahhhhhhhhhhhhhh! smile.gif

anyway that i can return the game and still can run the gamesave exploit hack?

That goes for every xbox not hardware-modded out there. No matter what kernel you've got. And I reckon you can't run the gamesave-exploit without it, no.
Logged

devz3ro

  • Archived User
  • Full Member
  • *
  • Posts: 229
Reintroducing Kernel Patching - Nkpatcher
« Reply #89 on: July 02, 2004, 06:25:00 PM »

QUOTE (old engineer @ Jul 2 2004, 06:35 PM)
Yeah, thanks devz3ro, but your post don't help me m8 sad.gif

...I'm not a n00b, I know how to softmod, TSOP flash and chip. I understand UDE, I know the difference between a gamesave exploit and a dashboard exploit!!!!!!!!!!

...I muck around with this stuff all the time, I understand about Kernal versions and ROE etc, etc, etc.

The ONLY reason I asked for an explanation from someone who got this working is that I've done EVERYTHING that I consider correct but it still won't execute nkpatcher, it just goes to a error 21 screen!!!!!!!!

K = 5713

evoxdash.xbe is on C:

nkpatcher5.xbe is renamed default.xbe and resides in mech assault save folder in Udata on E:

Any clues!!!!!!!!!

My post was not directed towards just you.

Why not TSOP down to your desired bios if you know how? I started with the 5713 bios, TSOP'd down to 5530 and now have UDE working with the latest xbox live present (which I use without a switch). I can't speak for mech assault, even though I own all 3 gamesave exploit games. The latest nkpatcher *does* execute fine on 007 and splintercell (K:5713). If you say that you tried *everything* TSOP seems like your last resort, when in my eyes it should have been the first.

just my 2 cents

-devz3ro

http://sh0x.tk/
Logged
Pages: 1 ... 4 5 [6] 7 8 ... 23