Post by: atomiX on January 25, 2005, 04:12:00 PM
i included a command in my scripts to open the tray when the 1st part of the install process is finished and when it does, the tray ejects fine but the xbox reboots when the tray is half-out, then goes back in because of the reboot.
this also happens when manually opening the tray when in the dash.
before jumping to conclusions...it is NOT a bios/kernel patcher issue because ROJ is deffinately disabled. i'm pretty sure it's an issue with UX. and yes, it's the newest UX version.
i've seen a few similar problems but have yet to see an explanation.
anybody know of a fix for this?
Post by: pepsik on January 25, 2005, 04:59:00 PM
Post by: atomiX on January 25, 2005, 05:56:00 PM
Post by: atomiX on January 26, 2005, 02:12:00 PM
i tried compiling nkpatcher with different variations of IRG and ROE to no avail.
Post by: Jezz_X on January 26, 2005, 03:41:00 PM
I suggest you go search in the GameSave forum because it was discussed manytimes when I used a softmod, things might of changed since then though it was before UXE and NKPatcher
Post by: atomiX on January 26, 2005, 05:12:00 PM
but this is not the case. regular gamesaves that you get from xbins will have ROE because they only modify the kernel's public key in memory, meaning that the kernel is still in a retail state except for the public key. this is why there is ROE on those gamesaves.
however, my save boots a habibi-signed nkpatcher which in turn will boot the dash. so when UX is loaded, all hacks implemented in nkpatcher are already loaded which means that ROE is also disabled.
the weird thing is that is doesn't reset the moment you press the button like when you have ROE enabled...it only restarts when the tray is about half-out :huh:
EDIT: I've done a bit more pokin around and now I don't think it's an UX issue. I think it has to do with nkpatcher since when i load apps with my save's UX filemanager, the same thing happend when i reset...weird that this happens with the save and not when nkpatcher is booted with the UXE exploit...
This post has been edited by atomiX: Jan 27 2005, 01:27 AM
Post by: Jezz_X on January 26, 2005, 08:50:00 PM
QUOTE(RiceCake @ Dec 19 2004, 01:56 PM)
Here's the low down. This forum is for gamesave exploits. This means an exploit thats loaded through a gamesave. With these exploits, you can only really run homebrew programs because you can't eject the DVD tray Now if you want to eject the DVD tray, I suggest you install an XBE exploit. Gamesave exploits are however, the most recommended way to get into your Xbox to install an XBE exploit.
Where can you find these XBE exploits? Well on the Xbox-Scene forum its directly below this forum.
Or here even for you lazy people!
If by any chance you come across tutorials on things like font hacks, FreeX tutorials, Bert And Ernie guides, etc, these are just highly outdated XBE exploits. DO NOT USE THESE. The current top exploit is UXE, and works on any model or region Xbox.
Where can you find these XBE exploits? Well on the Xbox-Scene forum its directly below this forum.
Or here even for you lazy people!
If by any chance you come across tutorials on things like font hacks, FreeX tutorials, Bert And Ernie guides, etc, these are just highly outdated XBE exploits. DO NOT USE THESE. The current top exploit is UXE, and works on any model or region Xbox.
Post by: atomiX on January 26, 2005, 09:43:00 PM
i use the gamesave to load nkpatcher (embeded in the save). the gamesave exploit itself does have ROE because it doesn't patch the kernel to disable it.
i use the gamesave exploit to load nkpatcher (embeded in the save) INSTEAD of a dash (like evox in most downloadable hacked gamesaves). plus, that nkpatcher is customised to boot the dash inside the save (in my case, UX) that i use as the installer portion.
my whole gamesave goes beyond a simple hacked save that you can get on xbins...
in short:
1. regular hacked save is loaded
2. boots habibi-signed nkpatcher INSTEAD of habibi-signed dash
3. nkpatcher runs and patches kernel in memory to enable various bios hacks (like lba48, live block and others including ROE fix)
4. when patching is done, nkpatcher loads the installer interface (UX) from the gamesave folder.
the quote you posted doesn't apply to my save. if you want proof, ask the softmod mods like devz3r0 and rmenhal. i know quite a lot about exploits myself...
and like i said above, the ROE prob is related to nkpatcher and not UX like i thought at first. i already PM'ed rmenhal about it
Post by: Jezz_X on January 26, 2005, 10:45:00 PM
The reason it dosn't effect things loaded from font/xbe exploits is that it the bios gets changed either by nkpatcher or a bios loader before the ROE flag is set. And loading nkpatcher after the flag is set on the hardware would not make any difference because the xbox thinks that as soon as the drive opens reboot
I would like to point out that I'm not trying to argue with you just help I could be 100% wrong and I would love to hear what rmenhal has to say about it
This post has been edited by Jezz_X: Jan 27 2005, 06:47 AM
Post by: atomiX on January 27, 2005, 08:46:00 AM
i've never heard about this impossibility to reverse the ROE flag with a gamesave but it might be true...just hope this isn't the case.
the reason i think it might be something else is because when the ROE flag is set, the xbox reboots immediately after pressing the eject button but with my setup, it only reboots a few seconds after (when the tray is half-open).
if any moderator reads this, you can move the thread to the gamesave or xbe exploits forums (whichever that seems more appropriate) since it really doesn't belong here anymore.
Post by: atomiX on January 27, 2005, 08:41:00 AM
if anyone has TECHNICAL details on how the ROE flag works, please post here. thx
Post by: eh. on January 27, 2005, 09:38:00 AM
This post has been edited by eh.: Jan 27 2005, 05:42 PM
Post by: DaddyJ on January 27, 2005, 09:24:00 AM
Once ROE has been set, it cant be unset, until a power cycle has occured.
Post by: atomiX on January 27, 2005, 01:33:00 PM
Post by: eh. on January 27, 2005, 01:46:00 PM
Post by: DaddyJ on January 27, 2005, 01:47:00 PM
Post by: garyopa on January 27, 2005, 09:28:00 PM
I wish we could find the hardware signal on the mainboard for this ROE problem,
maybe it could be solve by "cutting" the trace or installing a switch. I know, a
little worse than software solution, but a possible solution.
Post by: cmiz on January 27, 2005, 09:39:00 PM
Post by: eh. on January 27, 2005, 11:15:00 PM
QUOTE(atomiX @ Jan 27 2005, 10:46 PM)
i don't think music mixer removes the ROE flag that is the problem with gamesaves...i think it just doesn't set the flag in the first place. (i'm guessing its ROE flag is probably 8 and not 0 so it doesn't get enabled at all)
You are entirely correct; the 8 in the 0x80000002 below tells the kernel "don't enable reset on eject" eh:
CODE
*Default.xbe*
Certificate
~~~~~~~~~~~
Size of certificate : 0x000001EC
Certificate timestamp : 0x3F3D58D6 Fri Aug 15 18:04:06 2003
Title ID : 0x4D53005A
Title name : "Xbox Music Mixer"
Alternate title ID's : 0xfffe0000
Allowed media types : 0x80000002
: XBE_MEDIA_XBOX_DVD
Allowed game regions : 0x00000001
: XBE_REGION_US_CANADA
Allowed game rating : 0x00000004
Disk number : 0x00000000
Version : 0x00000004
Certificate
~~~~~~~~~~~
Size of certificate : 0x000001EC
Certificate timestamp : 0x3F3D58D6 Fri Aug 15 18:04:06 2003
Title ID : 0x4D53005A
Title name : "Xbox Music Mixer"
Alternate title ID's : 0xfffe0000
Allowed media types : 0x80000002
: XBE_MEDIA_XBOX_DVD
Allowed game regions : 0x00000001
: XBE_REGION_US_CANADA
Allowed game rating : 0x00000004
Disk number : 0x00000000
Version : 0x00000004
Edit: and if it was already enabled it would remain enabled, alas eh!
Post by: eh. on January 27, 2005, 11:22:00 PM
QUOTE(garyopa @ Jan 27 2005, 09:59 PM - part)
Only one program knows how to disable this HARDWARE flag. It is the XBOX Music Maker DVD, but NO gamesave HACK has been found for this certain disc.
(There are a few others, but hardly any that's for sure [and none of them disable ROE/J] eh.)
Post by: garyopa on January 28, 2005, 02:29:00 PM
flags, and study the assembly code used to SET the "ROE" feature, and
then from the actual code doing the "flag setting", figure out the "port"
the kernal is writting to, and then write test code in trying to "rewrite"
this port.
Post by: DaddyJ on January 28, 2005, 03:20:00 PM
Post by: cmiz on January 28, 2005, 03:31:00 PM
Post by: DJB on July 05, 2005, 07:39:00 AM
From the reading I've post of this post it seems like it's came to a dead end, but it would be interesting to know if something has been found.
I apologise in advance if there's newer posts etc but I DID use the Search to find this one.
TIA