KaosEngineer
-
Posts
4,872 -
Joined
-
Last visited
-
Days Won
458
Content Type
Profiles
Forums
Calendar
Store
Posts posted by KaosEngineer
-
-
On 4/14/2024 at 4:37 AM, flintboy22 said:
Hi guys
The service error code i'm getting is 21 when I attempt to run the xboxdash.xbe within file manager.
Would this normally be the correct way of running the file to load the MS dash or any dash for that matter.
It works when I run it for the Unleashed dashboard so that's what I did with this too.
I only have the .xmb file in the folder I put it in, in my file structure ,no others. is this normally correct.
Thanks
The stock dashboard files, IIRC, must all go on the C drive. Not on another drive letter or even in a Apps subfolder on C. Install the content in the root directory of the C drive. There will be subfolders of the stock dashboard on the C drive.
-
To create a properfly formatted version for a game's XISO disc image, run the XISO to HDD Installer script in XBMC4Gamers.
Upload the XISO files to the Games folder on your Xbox, run the script. It will prompt you for the source folder of the disc images. It then moves each to a game named subfolder and places the attach app named default.xbe file in each subfolder.
-
1
-
-
44 minutes ago, clak said:
My question is, what would you try next? I would really like to save this console, but I am running out of ideas on how to repair it. Any advice/insight/knowledge would be greatly appreciated.
Try a known working OEM / Microsoft controller.
-
1
-
-
42 minutes ago, clak said:
Xblast did not recognize the mod chip
Ignore the error about unsupported modchip. All of the XBlast OS's features are only supported on an XBlast Lite or Pro modchip. That's the reason it prints that message, you are not running it on a modchip that supports all of its features.
-
8 hours ago, The Wizard said:
Thank you for the quick reply. I only wanted to unlock the hdd with the actual key off a retail console just so I can copy game saves that were on it. This gives a error 6 so i think it belongs somewhere else, I just don't know where. I tried both the Western digital and seagate drives with the generic key and neither of them work. I wanted to write a script and try to brute force the key but from what I understand you need to power cycle if there are to many attempts in a row. I remember reading something about this and that becomes unplausible so I just have to accept the loss. Thank you though.
The HDDKey is not saved on the hard drive. It is stored in an 8-pin serial EEPROM on the motherboard. There are several methods available to read the data from this chip.
- Arduino and one of several sketches available on github.com
- Raspberry Pi and PiPROM software
- PC with a 9-pin serial port, DIY Xbox EEPROM reader/write cable and PonyProg software
just to name a few methods.
Each unmodded Xbox console's HDDKey value is unique to it. And, the password used to lock the hard drive is computed using it along with the hard drives model and serial number which makes the password unique for each different hard drive too.
Edit: If you have the eeprom.bin backup from the Xbox, you can use FATXplorer 3.0 beta or XBOXHDM23USB Beta 3 to unlock the hard drive.
-
18 hours ago, arfows said:
Was trying to download the "HDD fix for games.7z 1.0.0" off of the downloads section on this site and it bounces between 90 and 100 kbps every tenth of a MB and then after about 85% is downloaded I keep getting a "Couldn't download network issue". Tried it 3-4 times now, varying times of day and it always ends up the same. Tried to resume download after it happens and it immediately times out and says "couldn't download - no permissions". I'm able to download larger files from other sites just fine. I know there is a 2 downloads per day restriction on this site which may cause the second fault, but not sure if anyone else is having problems downloading things from here, if it might be this one file that has issues, or if its me.
Thanks!
No problem downloading it here.
-
19 hours ago, Bowlsnapper said:
It seems that the Debug Kit simply had 128MB of RAM and the only debugging came from the dashboard or bios and transferred through LAN. As far as I know nothing else is different from a stock/retail console. However...
IIRC, they also have a different MCPX chip v2 instead of the retail unit's v3 version.
-
36 minutes ago, BigPartyGuy said:
Sorry this is very late, but how do I "enable" the 720 xbe file as default. My game only launches at horrible resolution. I tried deleting the standard xbe, leaving only the 720 version. But then the game doesn't even show up on my Games list.
Is it default_720p.xbe or something similar?
If so, rename it to default.xbe for the game to appear in the Games menu list.
-
1
-
-
29 minutes ago, Nybbas said:
I have an unmodded japanese xbox (rev 1.0) with a dead HDD. I also have a working HDD from a USA xbox (rev 1.6) that has a softmod on it. If I extract the eeprom from the xbox with the dead HDD, can I use fatxplorer 3 to unlock the working softmodded HDD, then relock it with the extracted HDD password from the eeprom?
yes
you need both Xboxs' eeprom.bin files. Unlock the current softmodded HDD with the 1.6 Xbox's eeprom.bin then use the unmodded Japanese Xbox's eeprom.bin to relock it for that Xbox.
It's not the password that you are obtaining within the eeprom.bin file but an encryption key that along with the hard drive's model and serial number computes the correct password to lock the hard drive.
-
1
-
-
2 hours ago, FallOutBoyisRAD said:
I can't figure what step I'm missing or what I'm doing wrong here. Am I supposed to burn both the .ISO and .RAR files to the DVD-R rather than only the .ISO? OR am I missing something else entirely? Any and all help would be greatly appreciated.
To do the HDD Flash, you need to create the BIOS folder on the real C drive of a softmodded console. If you softmodding using Rocky5's Xbox Softmodding Tool, run NKPatcher Settings then FTP to the console to have access to the real C drive to create the BIOS subfolder and upload the bios's .bin file to.
-
1
-
-
On 3/22/2024 at 5:43 AM, verawarez said:
Hi guys now im recently splitting 1.0 bios to 4 banks, i backup bios with evox but gives me 1024 size backup
I know that with raincoat it doesnt autosize to 1024kb but the problem i dont know how to use it
Many questions...
1 could i split the 1024 bios to 4x 256kb bios? or 2x 512kb ones?
2 can i backup 256kb or 512kb bios size (tsop splitted one)
3 is there any option to have a 256kb backup of 1.0 1.1 bios xbox?
last, is there any option or tutorial to get raincoat working? or to make backup with raincoat?
All stock Xbox BIOSes and most modified Xbox BIOSes are only 256 KBs in size.
Microsoft (MS) installed a 1MB flash chip on v1.0 and v1.1 motherboards and Evox dumps the entire flash memory chip - 4 copies of the same BIOS. And, with v1.2 and later motherboards MS changed the flash memory chip to 256KBs; however, the replacement dashboard's backup routine did not change and the same chip is accessed 4 times to dump a 1MB file too. This occurs because the memory address decoding is incomplete throughout the entire 16MBs of memory space MS allocated for the TSOP.
For a v1.0 or v1.1s 1MB flash, it can be accessed at 16 different evenly divisible 1MB addresses throughout this space to dump the 1MB flash memory chip.
And for v1.2-1.4s, the 256KB flash can be accessed at 64 different 256KB starting addresses to dump the same data.
If the BIOS's base size is 256KBs, you can split the file into 4 256KB sections one after the other to obtain 4 copies of the same BIOS.
-
From the ScummVM-1.4.1.rar archive's README-XBOX.txt file, available from emuxtras.net's Download section [XBOX] - Emulators:
ScummVM 1.4.1 ported by A600
This is a ScummVM port for the Xbox1, possible thanks to the hard work of
the ScummVM team and the SDLx libs by Lantus.It features all the 1.4.1 supported engines, MP3, Vorbis, Flac, AAC
and FluidSynth (the MT-32 emu isn't included because the Xbox lacks
the power to handle it). All HQ scalers should work.The file xbox.patch is the diff patch against the 1.4.1 branch
https://github.com/scummvm/scummvm.git-
1
-
-
22 hours ago, TJ1 said:
I moved over the ROM and TSOP from the 1.2v motherboard to the 1.4v and have run into the same issue. Maybe I need to transfer over the GPU or CPU as well? The PCB layouts between 1.2/1.4v look the same.
I'm thinking of getting a donor 1.4v motherboard with MCPX 3 (Korea) and trying the swap again... I think it has something to do with the MCPX itself...
Didn't the first level boot loader and decoding key and algorithm change between a v1.2 and 1.4 motherboards? Or was that just v1.0 to later revs then again with v1.6 motherboards.
512 bytes of code are stored in a permanent masked ROM that is part of the MCPX3 chip. It contains the first-stage boot loader (1BL) , decryption algorithm of the second-stage boot loader (2BL) decryption key(s), and X-code interpreter.
For more about the boot process of the Xbox read Matt Borgerson's archived write-up available on archive.org's Wayback Machine:
https://web.archive.org/web/20220518102811/https://mborgerson.com/deconstructing-the-xbox-boot-rom/
Edit:
Excerpt from Microsoft's Copilot's reply when queried aboiut deconstructing the xbox boot rom:
Certainly! Let’s delve into the fascinating world of the Xbox boot ROM.
-
Xbox Boot ROM (MCPX):
- The Xbox has a 256 kiB ROM that contains the startup animation, sound, and crucial components like the kernel.
- The kernel is a stripped-down version of the Windows 2000 (NT 5.0) microkernel.
- When you power on the Xbox, the software in the ROM is decompressed into RAM, and the kernel initializes the hardware1. (Reference: Boot Process - xboxdevwiki)
-
MCPX Versions:
- There are two known versions of the MCPX ROM: 1.0 and 1.1.
- The 1.0 version, found in the original Xbox, used an RC4 algorithm to decrypt the 2BL (second bootloader).
- For the 1.1 version, Microsoft switched to a TEA algorithm2. (Reference: MCPX ROM - xboxdevwiki)
From the information provided above, one would think that a v1.1 or later motherboard rev's MCPX3 would work on any v1.1 or later motherboard.
-
2
-
1
-
-
5 hours ago, Bowlsnapper said:
Okay, if it is at a cold boot EVER (like the console is cold and things can't be hot yet), then yes, the temp sensor probably needs to be replaced. That is my assessment, but maybe Kaos can add his input as well.
I agree with @Bowlsnapper. If it does this at startup, the chip needs to be replaced.
The System Management Controller (SMC) - the PIC processor on v1.0-1.4 motherboards or Xyclops chip on v1.6s - handles the overheating condition at a hardware level. It flashes the eject ring LED orange and spins the fan(s) up to max speed to cool the system. If the temperature reading does not go down the SMC shuts off the console. The front panel buttons do not respond after the overheating condition has been sensed by the SMC.
Edit: A damaged trace from the CPU's temp diode to the ADM1032 temp sensor or from the sensor to the SMC could cause a false overheating condition to be sensed. As well, leaked clock cap electrolyte under the chip that cannot easily be cleaned without removing the chip could cause the error to occur.
-
1
-
-
2 hours ago, Mercenary said:
Good to know for future yes that the USB drive can be used for apps.
IIRC, they won't run from the USB drive. You have to copy the files from the USB device to the hard drive to run them.
-
1
-
-
There are other Japanese Xbox Manuals available to download on this page too:
https://web.archive.org/web/20031006104840/http://www.xbox.com/ja-JP/support/manual.htm
-
1
-
-
Rename those long-named folders to something much shorter. For example:
Doom 2 Minor Sprite Fixing Project v2 to simply Doom 2 Sprite Fix
and
Vanilla Smooth Weapons to VSW, etc.
There's most likely a limit to the length of the arguments in the cut file settings.
-
1
-
-
26 minutes ago, Jessicafligo said:
Is UnleashX purposely restarting when attempting to add icons to the Xbox games list, or is there a potential issue with the software causing this behavior?
How many and what size are the icon images?
UnleashX may be running out of memory thus restarting.
Also what's with the gambling URL spam. I'm removing it!
-
On 3/20/2024 at 7:15 PM, Mercenary said:
Also, the "extras" iso, it should be just a regular iso right? There is no "special" format like XISO or anything?
The Extras Disc ISO file is an XISO disc image. You burn the disc image to blank DVD-R medial.
On your PC, does the burned DVD show a directory listing in Windows Explorer? If so, the disc image was not burned but a data disc that holds the dot iso file was created.
-
On 3/20/2024 at 7:23 PM, Mercenary said:
Ok, I will just try to get a quality new unscratched DVD-R and if that fails then FTP it is. I assume I can't just load the iso on a usb drive and copy it to my xbox's HDD?
Yes, with the Extras default.xbe attach app uploaded to the same Apps/Applications subfolder to mount/play/load it from the Apps menu.
-
1
-
-
On 3/20/2024 at 4:20 AM, Eisbier said:
First say hello to the members!
After years i found my xbox again
. I have a 1.0 with a xecuter 1 modchip and i replaced the dvd drive to a Samsungs SD 616. I thought i would be nice to have a modifed box with more than my 80GB HDD. So tried my best. I solderd out the old modchip, replaced it with a cheap aladdin from aliexpress an removed the capacitor for the clock. Now i have the problems. I got an error 16 when i started up the box. No EvoX logo is shown on the screen. No DVD like OGXbox Installer ist working so far. The led on the modchip ist red when turned on.
I tried this with the old cable and old hdd.
I think the modchip is not working.
What are the possible problems? Did I some mistakes with soldering? Is the modchip garbage? Should i flash the chip out of the modchip. If this is correct. Witch cheap programmer should i use.
Thanks for your help!.
eisbier
If you don't see Evox logo during the startup animation, the modchip's BIOS is not loading. Check your D0 connection. Grounding this line tells the system to boot/load the BIOS from the modchip (LPC-attached device) instead of from the onboard TSOP flash memory chip.
-
On 3/21/2024 at 3:59 AM, southcamp said:
Thx for the comfort, really appreciate it.
@KaosEngineer: Do you have experience with this kind of issue?
Here is what I found out about the X2.5: https://www.xbox-hq.com/html/modules.php?name=News&file=print&sid=2722
Cheers!
Take a look at this manual:
-
On 3/21/2024 at 1:59 AM, southcamp said:
I also remember that one was able to flash the X-Changer with evolutionX if a line was added in its .ini. Is that correct?
Yes,
Flash = 0x20e3,"XChanger",0x40000
-
On 3/21/2024 at 3:59 AM, southcamp said:
Thx for the comfort, really appreciate it.
@KaosEngineer: Do you have experience with this kind of issue?
Here is what I found out about the X2.5: https://www.xbox-hq.com/html/modules.php?name=News&file=print&sid=2722
Cheers!
Even more information can be obtained from archive.org's Wayback Machine:
TeamXchanger - Home (archive.org)
Board Life Status
Board startup date: April 23, 2017 12:45:48
500 gig ssd only showing 123gigs
in Hardware Mods
Posted
Not that it matters now, but when cloning, did you use the Selective Cloning option in Chimp?
Was the original hard drive a stock 8GB drive or an already larger updated drive?
How is your Xbox modded: soft or hard mod?