Print

[fluidmax]

i have done this many times but this time once the gamesave hack is loaded...it shows this

# cd /media/E/UDATA/4541000d/91633FEE2CF5/raincoat
cd: can't cd to /media/E/UDATA/4541000d/91633FEE2CF5/raincoat

i think this is the latest xbox update that does not allow gamesave hack to run... <

[speedbump47]

Just wondering, why is your raincoat under a 91633FEE2CF5 directory?  The package I've used has it under the 000000000000 directory.  Could it be that the directory you're trying to use doesn't exist?

Are you typing the "cd ...." commands in, or does that automatically come one once you boot the gamesave?  The standard hack requires you to telnet in, and log in.  It never has tried to go into raincoat by itself.

Could you provide further info, like what package (if any) you are using, and what the build date of your Xbox is?  <

[fluidmax]

my bad...i mean to type
# cd /media/E/UDATA/4541000d/000000000000/raincoat
cd: can't cd to /media/E/UDATA/4541000d/000000000000/raincoat

i don't think it's my solder or version of raincoat since i am using .501

people will see this new version of xbox soon which does not allow you to use game save hack with raincoat....well i didn't believe this could happen....but i just got one xbox that didn't let me even do 'ls" when i am in the "E" partition

did anyone else have this problem?  <

[Frag Daddy]

You should be typing this in as the command:

cd ../../media/E/UDATA/4541000d/000000000000/raincoat

Instead of:

# cd /media/E/UDATA/4541000d/000000000000/raincoat

 <

[fluidmax]

it makes no difference...try it without ../../ and you should still get it work....unless you got a xbox like mine  <

[Zedek]

guess what...


THERE IS NO XBOX THAT FORBIDS THAT GAMESAVE TO RUN

It's not controlled by the dashboard or anything else...it's run through the damn GAME


You have screwed up somewhere...it's simple as that.  <

[fluidmax]

the game save is running...but no access to any of the partitions with raincoat....that is why i can't cd into the folder i want...just did another xbox with the same setup and it worked....so i know this newer one is updated with some kind of protection about the raincoat in the game save hack. btw the xbox has a nov 2003 date

This post has been edited by fluidmax: Jan 9 2004, 01:17 PM <

[Exobex]

Are you definitely running the save from the HD and not the memory card?

If so, might be worth recopying from the memory card and trying again.  <

[fluidmax]

that was my first guess....i thought maybe the file on it was bad..so reuped many time and re loaded my game save on my memory card...still no go...btw...i tried both...load it of HD and memory...didn't works...the new xbox i got that was made in nov 03 has some extra protection unlike the one's made before nov 03...i guess once they get more popular we will see....
btw...i noticed it takes about 20 seconds to load the distro from the game save (you won't hear any sounds for like 20 seconds and then you hear it loads) unlike the other version which only takes about 10 seconds before you hear it is loading.....it is very strange....maybe this xbox(nov 03) is weird or maybe i did something wrong...but i really don't think it is human error...i know what i was doing...   <

[lordvader129]

try CDing one directory at a time instead of all at once, i had to do that once  <

[fluidmax]

tried that already...but no use...the moment i type
cd /media/E/ (up to this posint it still let me cd to partition E
but when i type
cd /UDATA/
it goes
cd: can't cd to /UDATA/

i think they did something to the newer xbox...just MHO  <

[DvS]

I have flashed the TSOP on a v1.4 and v1.5 using the raincoat method and I have not had a single problem. I think this lies more in the raincoat file you are using more then anything. make sure you check all the file names that you upped to your hardrive before you upped them to the memory card. I can't see the transfering of the save file from the memory card to the harddrive screwing up.
But it definately has NOTHING to do with when your Xbox was made or what version it is.  <

[fluidmax]

hmm....same memory card...will work on a V1.4 (Aug 18 03)
but didn't work on this weird xbox(Nov 14 03) ...i don't think it's the file on the memory card...i checked it many times.
i guess only time will tell.... when newer(Nov 03) xbox start to show up.
To Dvs
what is the latest Manufacture date you have ever encountered on an xbox?  <

[powercntrl]

Since I haven't encountered an Xbox with that late of a manufacturing date, I can't offer anything more than speculation.

What you're describing sounds like Linux isn't able to mount the filesystems on the hard drive...  If you're feeling adventurous, you could try using the 007AUF exploit to run EvoX, backup the Xbox to your computer, reformat the Xbox's hard drive, then reload it.  (Course, this assumes EvoX doesn't just call some APIs in the kernel to recreate the filesystem exactly the way it was.  I'm not sure how EvoX's format routine works on the low-level.)  Be warned though, IF MS did change something about the drive's partitions/filesystem, there's a chance the retail BIOS may no longer boot or even be able to read from the reformatted drive (if for example, MS made some change to FATX).

I think if it were me, I'd use 007AUF/EvoX to find out the hard drive's lock code, and lock a spare drive with it and futz around with THAT drive instead, while the original Xbox's hard drive is safely tucked away.  <

[domik100]

Yeah, I have the same problem with my 1.5, can't cd to E or any other partition except cdrom.
After typing ls, when in ./media dir it lists all part. and cdrom so i suppose it's mounted but i may be wrong (dont know linux). if it's caused by some new M$ protection, then many people would have same problem..  maybe will be released 007AUF exploit update working with 1.5, i hope so! please help  <