Print

[Bomb Bloke]

It's possible to use another X-Box, but the exact process depends on the versions of the two different consoles.

It may be that you can get your PC(s) to co-operate by disabling automatic detection of the HDD within the BIOS settings screens (CMOS setup, set the drive to "none" or "disabled").

[ldotsfan]

Try connecting the IDE cable after bios has POST and PC has booted but before linux starts. Use the Pause button if necessary. This is to fool the PC into bypassing the security frozen.

[ldotsfan]

You can lengthen the duration before linux boots, edit the isolinux.cfg inside linux\isolinux\ folder and search and edit the timeout to increase your chances. Reburn the ISO.

CODE

default 1
prompt 1
timeout 1000

[cm0002]

QUOTE(cm0002 @ Jul 21 2010, 08:12 PM)

ok thanks hopefully it will work

ok sorry for the double post but i couldnt edit my above post for some reason, anyways i edited the file like you said and plugged the drive in after post but xboxhdm didn't detect the hard drive

[Bomb Bloke]

Regarding the "auto detection", it's not usually labeled as such: The CMOS screens will usually just show you the model of the drive that's detected. Move the selector thingy over that and try changing it.

If you can't get a computer to handle this (and you'll find things easier if you can; consider asking a friend if you can attempt this with their system(s)), the method I would use with your other console would be to:

First, TSOP flash it. "Old" version of the X2 5035 BIOS will be fine. Backup its EEPROM, being careful not to confuse this new copy with the backup you took from the broken box.

Once the TSOP is flashed, the machine will be able to boot with an unlocked HDD attached. You might consider unlocking the currently installed drive, as it might cause you problems some day and there's no further benefit to keeping it locked.

Install the formatted HDD in the TSOP-flashed machine. If the console won't boot off that for whatever reason, insert that UnleashX disc you made, reboot, and it should start up off that. Make sure the HDD has all the files you want it to have.

Run ConfigMagic and use it to flash the EEPROM chip with the backup you took from the broken system. Once that's done, have ConfigMagic lock the HDD, and then flash the EEPROM chip again with the backup you took from the currently working box.

[ldotsfan]

1. OP please also verify your eeprom.bin with LiveInfo against the serial no on the back of the xbox.

2. Do you have a molex Y splitter or power connector from USB-IDE enclosure? You can use chimp2618 to lock the hdd from the working softmod xbox with your eeprom backup assuming the backup is good. chimp2618 supports locking from an eeprom file that is ftped into chimp2618 - assuming the working softmod xbox has a working network connection.

[cm0002]

QUOTE(cm0002 @ Jul 22 2010, 11:40 AM)

i don't have a molex y spliter but i do have an AC to molex power adpater i can use, but for chimp do i have to take out the IDE from the dvd drive or the hard drive?

never mind i figured out its the dvd drive cable, but now when i select the fatx icon on the menu it says loading kernel ok then loading initrd ok then it says starting but seems to be frozen as i left it there for about 20 min and it doesn't do anything
i do the hotswap from the dvd drive to the hdd while im at the dashboard then i launch chimp the xbox hdd on master jumper settings are on master and the hdd on the slave has the jumpers set to slave

[ldotsfan]

QUOTE(cm0002 @ Jul 23 2010, 07:09 AM)

never mind i figured out its the dvd drive cable, but now when i select the fatx icon on the menu it says loading kernel ok then loading initrd ok then it says starting but seems to be frozen as i left it there for about 20 min and it doesn't do anything
i do the hotswap from the dvd drive to the hdd while im at the dashboard then i launch chimp the xbox hdd on master jumper settings are on master and the hdd on the slave has the jumpers set to slave

1. Which version of chimp are you using?
2. Are you using component cables?
3. You can try the version of chimp in LUD. That's the latest release. Usage instructions: http://forums.xbox-s...&...t&p=4715633 with a slight rearrangement of the menus. You will need to burn a DVD-R.
4. Navigate with your ftp client on your PC to /ramdisk/var/tmp directory and upload eeprom.bin to that folder.
Username: root, password: xbox. The network setting menu option will show the IP address of the xbox.
5. Choose the locking option for slave hdd.

[cm0002]

QUOTE(cm0002 @ Jul 22 2010, 07:26 PM)

1. 2618
2.no
3. ok will try that one

the LUD boot disc doesnt work either it gets to the gentoox loader i click cd/dvd but the it says could not read from disc, i tried 4 different mediems 2 of which is known to work in my xbox(verbatim,memorx,office max, and TDK)
TDK fully works im my xbox and memorx is like 90% chance it will work

[ldotsfan]

One of my test consoles for LUD is a ver 1.1 and it worked well on that console. Mine is a Samsung DVD drive, what's yours?

Please also report back on the serial no verification of eeprom.bin with LiveInfo on your PC. I thought of another method  to lock the hdd.

[ldotsfan]

1. Keep both copies of eeprom.bin safe on your PC.
2. I'll label working softmod xbox "S" and non-working xbox with the hdd unlocked "T" for ease of identification.
3. If you have another brand of dvd drive on T other than Thomson, you could swap that over to S. Remember to set hdd jumper of T's hdd (target to be locked) to slave as well. See if that dvd drive has any luck booting LUD successfully.

If step 3 still fails, the last option I can think of is to edit the hdd key of S to match that of T. Ref this thread: http://forums.xbox-s...howtopic=683310. We'll use a variant of this method but instead of zeroizing, we will edit the hdd key to match T's key. Copy down on paper or print out the hdd key displayed for T's eeprom.bin as shown in LiveInfo on your PC. Next do this:

QUOTE

1. For softmods, disable virtual eeprom.
2. In ConfigMagic, press Start button and select unlock hdd.
3. Edit on the fly eeprom in ConfigMagic.
4. Edit hdd key to match T's key
5. Select Update xbox eeprom option.
6. Load eeprom option in ConfigMagic.
7. Lock hdd option in ConfigMagic

If you are uncertain over any of the steps, report back here. If you are unsure how to disable virtual eeprom, you'll need Frosty's rescue disc. We will prepare a special edition of Frosty's disc using a variant of this thread: http://forums.xbox-s...howtopic=654467

1. Get UnleashX from the usual place. You won't need Kingroach's.
2. Extract Frosty's iso to a folder. I name it lxhdm.
3. Delete root.xbe from lxhdm folder.
4. Copy unleashX.xbe to the folder and rename as root.xbe
5. Delete away DVD2xbox folder in Applications.
6. Create a ConfigMagic folder in Applications and copy the relevant files there.
7. Create the xiso with qwix.
8. Burn to a DVD-R at 2x. (or whatever media works for your xbox's dvd drive - TDK).
If any of the steps are unclear, report back here.

Cold-booting with this disc will disable virtual eeprom. The final procedure is to perform error 5 hotswapping with lxhdm disc to lock T's hdd using S to boot lxhdm disc. Prior to this, S's eeprom hdd key should already match T's key. Error 5 hotswapping steps:

QUOTE

1. Eject dvd tray and insert lxhdm dvd. Power off.
2. Connect hdd IDE cable to T's hdd in S's. Supply power to T's hdd.
3. Power on xbox. You will get an error 5 which is expected.
4. Unplug hdd IDE cable but keep external power to T's hdd (in S's)
5. power off xbox and connect hdd IDE cable back to S's hdd.
6. power on and lxhdm dvd will load.
7. when unleashX is loaded, unplug hdd IDE cable from S's hdd and plug it to T's hdd.
8. Use UnleashX file manager , navigate to D drive and launch default.xbe.
9. When UnleashX is relaunched, use file manager again and navigate to ConfigMagic on D:\Applications\ConfigMagic\default.xbe and launch that.
10. Verify hdd details match those of T's in ConfigMagic.
11. Lock T's hdd in S with ConfigMagic.

If any of the steps are unclear, check back here again.

[cm0002]

nevermind i figured it out
YAY i locked my harddrive now both xboxs are hapilly booting with their respective hardrives, thanks for all the help