Group: Members
Posts: 641
Joined: 23-April 04
From: Yoshi's Island
Member No.: 116006
Xbox Version: v1.0
I've changed my region in the eeprom to region 2 for a PAL xbox. Does this mean that PAL/NTSC-U games will not cold boot before nkpatcher does (UXE installed)...?
If so... great, can't think of ways to f*ck the exploit. otherwise... meh
Group: Members
Posts: 3225
Joined: 19-May 04
From: NB, Canada
Member No.: 120731
Xbox Version: v1.3
360 version: v1 (xenon)
that's pretty much the case. the game will only cold boot if it's own region is being used in the eeprom. the exception is multi-region games...they will always cold boot
Group: Members
Posts: 359
Joined: 4-May 04
From: the Under World
Member No.: 117949
Xbox Version: v1.4
360 version: v3.1 (opus)
If you change it to other region thats not 1,2 or 4 on the real eeprom you will have absolutely nothing to boot to because the bootstrap xbe for UXE can ONLY be run with one of the 3 regions.
Group: Members
Posts: 641
Joined: 23-April 04
From: Yoshi's Island
Member No.: 116006
Xbox Version: v1.0
krayzie, got a tutorial on this? i edited my region in the first place with ConfigMagic (appears THAT does get past shadow eep) but didn't see any language ID...
Group: Members
Posts: 254
Joined: 3-May 04
Member No.: 117780
Xbox Version: unk
360 version: unknown
It should be possible to set the region to 0x8, 0x10 or any other power of two up to 0x40000000, because the UDE/UXE update.xbe has region flags 0x7fffffff. Multiregion games (with any combinations of 1, 2 or 4) wouldn't then boot directly either. Not tested though so if you can't recover then don't do it.
It's cleaner to zero out the language ID, because the kernel won't even try to load d:\default.xbe then.
EDIT: note that xbedump will forcefully set regions only to 0x80000007, so that would need to be modified to e.g. 0xffffffff.
This post has been edited by rmenhal: Jan 9 2005, 02:36 PM