Print

[Wong Hung Lo]

QUOTE (shr00m @ Apr 16 2003, 11:34 PM)

the bios needed is 1 meg becasue the xbox bios is 1 meg, if you just follow the tut you wont have trouble the bios.bin which is included in the gamesave is evox d6 in 1 meg format...   i have now reflashed with x2     but the bin in the game save works fine

But if a person has one of the new 1.2 Xbox's with the 2 meg (256K) TSOPS then you could only use a 256K bios.

[shr00m]

yea this tut doesnt really cover 1.2s seeing as the game save has the last version of raincoat and it doesnt support the chip, the new version of raincoat does, and i think the jumpers are the same, but we'll need to get some input from a 1.2 user for that, this method could easily be adopted to a 1.2, by getting the gamesave partition image off a xbox with the new raincoat and a 256k bios file because yes the 1.2 is 256k....   i just didnt put any nfo on 1.2s in here because it wasnt confirmed and i didnt test it.   but with a partition image like the one were using only from a xbox with the newer version of raincoat (with winbond 1.2 support) and a 256k bios file it shouldnt be a problem, not sure if the jumpers are the same, but you can find info on jumpers pretty easily if you search the forums.

[shr00m]

thats normal it always says that when you first login from telnet, just procede to flash... it works as long as your jumpers are shorted

[Pulque123]

[shr00m]

sweet, glad it helped, thought i would add , ive noticed on the hot swap it seems every command you send to the drive, like say if you back it up or copy the image from irc over... it needs to be unlocked again after 1 command, maybe not every drive, but i have noticed it makes things to smoother, like if you back it up.... unhook pc ide, hook up to xbox, reboot xbox hook back up to pc... leave the pc on of course... after the original method...

[XeRpHoN]

[shr00m]

kickass glad to hear it!

[eznow]

will the bios in gamesaves.img work with a 1.1 xbox

[FOSI]

thanks people. you helped me a lot.

[shr00m]

it works with every version but 1.2 for 1.2 you need a gamesaves img that includes a 256k bios.bin becasue the 1.2s do not have the 1 meg tsops like all the other xboxs, but i personanlly have done this on 1.0s and 1.1s with about 4 or 5 different brand tsops

[ThingFish]

It all looks good on paper, but I had a huge problem:

1. I installed a fresh copy of Mandrake 9.1 on my PC, no problems there.

2.  I followed the directions to the letter, and did the swap, and pause and all that.

3. DiskDrake did detect the hdc, and I exited out.

So when I went to /dev to check on the hdc, there was none.  Also, I even tried to comamnd to transfer the savefile image to my Xbox HDD, but to no avail.

I wonder what's wrong?

Fish

[shr00m]

dunno, all i know is it works and there are many here who have done it successfully... you are hotswapping a drive, so some pcs will not respond the same,  the second method of hot swapping between each command will possibly  help... and if not you need a different pc....    read back up, a few posts to the post where i talked about re-unlocking the xbox drive after each command, i find it necessary on my pc. i have to unlock with xbox to detect in bios, then unlock again to actually boot linux after pausing at the bootloader screen... then once in linux i backup, then i hook the drive back up to the xbox ide, turn it off and back on to re-unlock it (during this leave the linux pc booted) and then do the write command to write the gamesave image over....   it should work fine... i never checked dev at all
i just did the commands and it worked. ive done it multiple times now, and so have many others

[bagel5009]

this shit is pretty cool, but its just easier to buy a modchip

[Optimus]

[sonix]

QUOTE (znark @ Apr 17 2003, 06:46 AM)

QUOTE (shr00m @ Apr 15 2003, 10:57 AM) i will [...] explain how to do it without EVER compiling a linux kernel Ok, nice tutorial! Let's take this a step further by adding in some hints on how to write the bzipped FATX gamesave partition image to your hot-swapped Xbox hard drive from Windows, without necessarily needing Linux on your PC. It appears that this step... QUOTE 3. TYPE THIS COMMAND EXACTLY WITHOUT QUOTES "bzip2 -cdk gamesaves.img.bz2 | dd of=/dev/hdc seek=5501 bs=512k" ...can be done from Windows, too - provided that you have the right tools at your disposal. In this case you would need the Windows versions of bzip2 and dd. Just download the GNU utilities for Win32 package and extract the dd.exe and bzip2.exe command line tools - preferably to the same directory where your gamesaves.img.bz2 image file is already located. The above Linux command line would then transmogrify to something like this for Windows: bzip2 -cdk gamesaves.img.bz2 | dd of=.PHYSICALDRIVE# seek=5501 bs=512k The "#" character above should be replaced with the number of your hard drive: 0 is the first hard drive in the system, 1 is the second, 2 the third one and so on. If you are unsure about the correct drive number, try reading some blocks from the drive to a file and checking the resulting dumps with a hex editor. If you read from the correct offset - preferably from an offset where some of the FATX partitions begins - you should see some distinct FATX filesystem identifiers, and then you can be sure that you are accessing the correct drive.

did this work for anyone?

CODE

C:cygwinbin>bzip2 -cdk gamesaves.img.bz2 | dd of=.PHYSICALDRIVE0 seek=5501 bs=512k bzip2: Can't open input file gamesaves.img.bz2: No such file or directory. dd: opening `\.PHYSICALDRIVE0': Invalid argument C:cygwinbin>bzip2 -cdk gamesaves.img.bz2 | dd of=.PHYSICALDRIVE0 seek=5501 bs=512k dd: opening `\.PHYSICALDRIVE0': Invalid argumentbzip2: Can't open input fil e gamesaves.img.bz2: No such file or directory.