Jump to content
OGXbox.com

CLONE XBOX with MODCHIP


Lexieye
 Share

Recommended Posts

11 hours ago, Lexieye said:

On the original 350gig HD I get 5838.01 on both channels. like you said I think this is M8 bios when I installed XBMC4GAMERS and removed Avon

I tried the upgraded HD in this original thread that should still contain the original bios in question..... but on my HardMod XBox I get error 06..... and on my softmoded XBox I get error 13?

I am not totally unsure that I have wiped the very rare bios & hopefully I can try again & again to get HEXEN to boot from CD

Is the new hard drive a SATA drive with IDE-to-SATA adapter? 

If so, are you using a high-speed 80-wire 40-pin IDE cable?

If not, replace the stock IDE cable with one.  Error 13 will go away.

 

Error 06 - Cannot UNLOCK hard drive - the password computed with the HDDKey stored in the motherboard's configuration EEPROM is not correct.  

  • Like 1
Link to comment
Share on other sites

On 4/24/2022 at 6:32 AM, KaosEngineer said:

Is the new hard drive a SATA drive with IDE-to-SATA adapter? 

If so, are you using a high-speed 80-wire 40-pin IDE cable?

If not, replace the stock IDE cable with one.  Error 13 will go away.

 

Error 06 - Cannot UNLOCK hard drive - the password computed with the HDDKey stored in the motherboard's configuration EEPROM is not correct.  

I used HEXEN to NULL all my XBox’s. I can’t remember correctly if I did this before or after I cloned the HD. 

Link to comment
Share on other sites

5 hours ago, Lexieye said:

I used HEXEN to NULL all my XBox’s. I can’t remember correctly if I did this before or after I cloned the HD. 

If you see error 06, either the HDDKey in this motherboard's configuration EEPROM is not NULLed or if it is NULLed, this hard drive was not locked using a NULLed HDDKey computed password.

You can connect the hard drive to a PC and use XboxHDM23USB's smartctl.exe application to attempt to unlock it with a NULLed HDDKey eeprom.bin file.  If it doesn't unlock, you can try several of the known MASTER passwords that may be the one used for this Xbox hard drive.  Once unlocked, you can use the NULLed eeprom.bin file, to relock it.

Link to comment
Share on other sites

  • 2 weeks later...
On 3/26/2022 at 11:16 PM, KaosEngineer said:

I'd like to get a copy of the 5033.01 BIOS.   Is it actually 5033 or is it 5035?

It's one that I can not find anywhere.  You can obtain a backup of the BIOS by running Evoxdash's Backup menu option.  The BIOS will be stored in the bios.bin file.  It will be saved in the backup subfolder where evoxdash is running from / installed to on the hard drive.

And, 4983.06 will only have F, no G drive in addition to the standard C, E, X, Y and Z drives.

 

To check the hard drive's partition configuration install and run XBPartitioner v1.3 to the Xbox. Take a screen shot of its main page and post it.  

I know this is bringing this topic back up, but UnleashX  says  BIOS: UNKNOWN 1.00.5032.01

BF9BAC8D-B4E4-427D-BE3F-27B2260CBE1C.png

  • Like 1
Link to comment
Share on other sites

On 5/3/2022 at 11:59 AM, Lexieye said:

I know this is bringing this topic back up, but UnleashX  says  BIOS: UNKNOWN 1.00.5032.01

BF9BAC8D-B4E4-427D-BE3F-27B2260CBE1C.png

 

Edit: There was an X2 BIOS release 5032.  Therefore, most of what I posted below is moot!  

 

 

That's not the replacement dashboard - UnleashX but Evoxdash. 

It will only show the name of a BIOS when the user has added the MD5 hash value for every modified version of a BIOS they want it to ID.

Which modchip is installed?  Team Xecuter's X3/X3CE or one of the many X2 releases or some other modchip.

Download Evoxdash's evox.ini file, open it in a text editor and find the line that reads:

  • Current = <BIOS's MD5 hash value>

What is the MD5 hash value on that line?

P.S.  Team Xeucter's X3 BIOS Build 3294 is kernel version 1.0.5034.1. Therefore, it may a prior build of the X3 BIOS; however, an X3 modchip is required to use Team Xecuter's X3 BIOS.  So, is an X3 modchip installed in your console?

P.S.S.  1.0.5033.1 from the original post may be another X3 BIOS version.   I've not used any of the prior releases on my X3 modchip in a long time.  Team Xecuter was good in assigned different kernel versions for each BIOS version they released unlike Evolution-X who used the same kernel version for many different releases based upon which original Microsoft BIOS it was based upon (e.g., Evox M8 and M8 plus are both 1.0.5838.1 just like the original v1.6 Xbox's kernel 1.0.5838.1).  By doing so, they made it harder to tell exactly which BIOS is in use just by knowing the kernel version.

 

Link to comment
Share on other sites

The MD5 hash value of the X2 5032 BIOS release will either be:

  • E515174A246C0940A5E06EBC9509C102 for the v1.0-1.4 Xbox version, or
  • 2A13311C0F68A46F8D5EB8B7CF8E4CA0 for the v1.6 Xbox version.

Evox.ini's Current = <MD5 hash line> should be equal to one of these values.

 

For Evoxdash to ID the BIOS, you need to add two ROM = lines under the [BIOS] section of this file similar to these examples:

  • ROM = "x2_5032_vOld_512k",0xE515174A246C0940A5E06EBC9509C102
  • ROM = "x2_5032_v16plus_512k",0x2A13311C0F68A46F8D5EB8B7CF8E4CA0

The X2 5032 BIOS is an earlier release. I suggest updating to their final X2 BIOS release - 5035.  For the most part, this BIOS's settings are not modified by a Windows application like Evox's M8/M8plus BIOSes.  5032 and 5035 settings are modified by editing the text file - E:\x2config.ini.

P.S. If you edit a BIOS with an application and reflash it to the modchip for settings changes to take place, for example Evolution-X's M8plus BIOS modified with EVTool or Team Xecuter's X2 4981 BIOS modified with XBTool, changing one setting/value from any other already ID'd BIOS that has been added to the file, you have to make note of the new MD5 hash after you edit it and add an additional line with some unique identifier to ID the BIOS.  Otherwise, no matching MD5 hash will be found, and UNKNOWN will be displayed for the BIOS's name.

 

Link to comment
Share on other sites

On 5/4/2022 at 7:40 AM, KaosEngineer said:

The MD5 hash value of the X2 5032 BIOS release will either be:

  • E515174A246C0940A5E06EBC9509C102 for the v1.0-1.4 Xbox version, or
  • 2A13311C0F68A46F8D5EB8B7CF8E4CA0 for the v1.6 Xbox version.

Evox.ini's Current = <MD5 hash line> should be equal to one of these values.

 

For Evoxdash to ID the BIOS, you need to add two ROM = lines under the [BIOS] section of this file similar to these examples:

  • ROM = "x2_5032_vOld_512k",0xE515174A246C0940A5E06EBC9509C102
  • ROM = "x2_5032_v16plus_512k",0x2A13311C0F68A46F8D5EB8B7CF8E4CA0

The X2 5032 BIOS is an earlier release. I suggest updating to their final X2 BIOS release - 5035.  For the most part, this BIOS's settings are not modified by a Windows application like Evox's M8/M8plus BIOSes.  5032 and 5035 settings are modified by editing the text file - E:\x2config.ini.

P.S. If you edit a BIOS with an application and reflash it to the modchip for settings changes to take place, for example Evolution-X's M8plus BIOS modified with EVTool or Team Xecuter's X2 4981 BIOS modified with XBTool, changing one setting/value from any other already ID'd BIOS that has been added to the file, you have to make note of the new MD5 hash after you edit it and add an additional line with some unique identifier to ID the BIOS.  Otherwise, no matching MD5 hash will be found, and UNKNOWN will be displayed for the BIOS's name.

 

Ok that is a little over my head with what you have explained, but I downloaded bios checker by CrackJack & DarkMoon and here is the Hash

XBOX BIOS CHECKER 4.0b - By CrackJack (www.darkmoon.org)

CHIP TYPE > MODCHIP unknown HomeBrew) Using genulne BIOS > Xecuter2 4983.06

BIOS MD6 Hash CDD618F786CEOC88OBC661D60B999E2E Press <START> to reboot your BIACKBOX!

945A44C2-AC46-4877-B844-053703844923.png

Edited by Lexieye
Link to comment
Share on other sites

4 hours ago, Lexieye said:

Ok that is a little over my head with what you have explained, but I downloaded bios checker by CrackJack & DarkMoon and here is the Hash

XBOX BIOS CHECKER 4.0b - By CrackJack (www.darkmoon.org)

CHIP TYPE > MODCHIP unknown HomeBrew) Using genulne BIOS > Xecuter2 4983.06

BIOS MD6 Hash CDD618F786CEOC88OBC661D60B999E2E Press <START> to reboot your BIACKBOX!

 

Ok, so it is booting Team Xecuter's X2 4983.06 BIOS.

One of the BIOSes BIOS Checker 4.0b's identification file, bioses.ini, actually contains an MD5 hash value of.

Edit:

However, this must be a different Xbox than the one you posted information about before which was running Evox dash. 

It showed the kernel version as 1.00.5032.01.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

Board Life Status


Board startup date: April 23, 2017 12:45:48
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.