Print

[SS2Gohan]

Me again.  Update to my issue.  I used SodMod Deluxe Installer to mod orginal HD.  Used Chimp2.6 to clone hard drive.  When I use the clone HD I get the #5 Error.  I tried every option under Chimp2.6 to lock slave HD but it won't.  I did use the xboxhdm later to lock the clone HD and work great.  I only question is if the chimp2.6 was made so you didn't need a PC (which I did because xbox is 1.6)  to make a copy of an HD work with the XBOX then what do i need to do to get the hard drive to work.

[xbdeelo]

Can some one walk me through the process on a 1.6 via telnet.
my xbox pulls 192.168.1.101 on evox
then i run the chimp app I get a green screen. I know so far this is normal, next i try to telnet 192.168.1.101 from the command prompt  but the connection times out. I saw reference to a user and pass of root:xbox, how would I enter this.
Any help would be appreciated.
Thank You

[Keo-Keo]

as far as i know and see.. Chimps tool isn't using DHCP (at least i didn't see it working). The default ip is
192.168.0.3

so if your running a 192.168.1.1 block of address your going to need to change that block to match 192.168.0.1 block.. If you happen to have an extra ethernet card you could manually yet your PC's ip address to 192.168.0.1 then it should be cake work telneting it..

[jaxomgreen]

I've got a NTSC 1.6 xbox softmoded with ltools 1.8rc1 MA.  I'm in the middle of upgrading the hard drive using chimp26 since I've got a laptop.  Everything seems to have gone OK so far, but when I get to the lock slave HDD step my HDD password from EEPROM seems suspect.  The first 40 hex digits appear legit, but the last 24 are all zero.    I believe I've read elsewhere that having zeros at the end of the password means a bad EEPROM read.

Right now I'm not going to lock my HDD, although I need to lock it to boot with the new drive since I've got  a softmodded box.  Does anyone have suggestions on how to lock this drive?

Thanks.

[Keo-Keo]

QUOTE(jaxomgreen @ Mar 8 2005, 10:27 PM)

I've got a NTSC 1.6 xbox softmoded with ltools 1.8rc1 MA.  I'm in the middle of upgrading the hard drive using chimp26 since I've got a laptop.  Everything seems to have gone OK so far, but when I get to the lock slave HDD step my HDD password from EEPROM seems suspect.  The first 40 hex digits appear legit, but the last 24 are all zero.    I believe I've read elsewhere that having zeros at the end of the password means a bad EEPROM read.

Right now I'm not going to lock my HDD, although I need to lock it to boot with the new drive since I've got  a softmodded box.  Does anyone have suggestions on how to lock this drive?

Thanks.

 
Use evox to get the orginal eeprom from the xbox.. Get the hdkey and maually type it in.. I belive there is an option! NOTE:!!!!
WARNING! IF YOU MESS UP 1 KEY OUT OF THE SEQUENCE YOU ARE F***KED THAT NEW HARD DRIVE WILL BE LOST! DOUBLE AND TRIPLE CHECK THE SEQUENCE!

[jaxomgreen]

QUOTE(Keo-Keo @ Mar 9 2005, 01:03 AM)

Use evox to get the orginal eeprom from the xbox.. Get the hdkey and maually type it in.. I belive there is an option! NOTE:!!!!
WARNING! IF YOU MESS UP 1 KEY OUT OF THE SEQUENCE YOU ARE F***KED THAT NEW HARD DRIVE WILL BE LOST! DOUBLE AND TRIPLE CHECK THE SEQUENCE!

Since I posted last I used my original evox backup of the original (unmodded) box with the eeprom.bin.  I then ftp'ed that eeprom to /tmp in the chimp26 installer and dropped to shell.  I figured out that /initrd/bin/hdtool2 was what I wanted, so I did
/initrd/bin/hdtool2 -e /tmp/eeprom.bin -d /dev/hdb -o UNLOCK
(since doing UNLOCK first is how chimp's lockhdb script displays the password for you to approve).  I got the same password as chimp's script displayed.

Then I followed your advice and took the xbox key and used that (using -k), also getting the same password.

At this point I think somethings going wrong with my xbox and the linux eeprom tools.   Next I'll use config magic to get another eeprom backup and try using that.

Thanks.

[Keo-Keo]

QUOTE(jaxomgreen @ Mar 9 2005, 01:39 AM)

Since I posted last I used my original evox backup of the original (unmodded) box with the eeprom.bin.  I then ftp'ed that eeprom to /tmp in the chimp26 installer and dropped to shell.  I figured out that /initrd/bin/hdtool2 was what I wanted, so I did
/initrd/bin/hdtool2 -e /tmp/eeprom.bin -d /dev/hdb -o UNLOCK
(since doing UNLOCK first is how chimp's lockhdb script displays the password for you to approve).  I got the same password as chimp's script displayed.

Then I followed your advice and took the xbox key and used that (using -k), also getting the same password.

At this point I think somethings going wrong with my xbox and the linux eeprom tools.   Next I'll use config magic to get another eeprom backup and try using that.

Thanks.

Strange.. I thought evox could get 1.6's! Hmm.. When did you get this xbox? (me wonders)

[jaxomgreen]

QUOTE(Keo-Keo @ Mar 9 2005, 01:57 AM)

Strange.. I thought evox could get 1.6's! Hmm.. When did you get this xbox? (me wonders)

A few weeks ago, Feb 12th or 19th maybe?  From a Wal-Mart that had been out of stock the week prior.

I have now backed up the eeprom with configmagic-final and diff reports that the two eeproms I have differ, although the hd password and key for the stock drive reported by ltools and config magic are the same.

I'm going to try using that eeprom to see if it generates a better password.

[Keo-Keo]

Hmm 2 diffrent eeproms from config magic?

[DaddyJ]

evox can grab the correct eeprom from a v1.6 box, but your using xboxhdm or liveinof you must use there latest versions of those programs to correctly generate the correct key.

[jaxomgreen]

Success!  I was just so scared of bricking a new 300GB hard drive that I didn't trust the tool since I had read so many horror stories about bad HDD passwords.  It worked, all from the telnet interface on my 1.6(b?) xbox.

What made me realize I should just trust the scripts was when I triple checked my original HDD password.  It was only 40 digits long.  The 24 trailing zeroes using this tool confused me, but the first 40 digits were the important ones.

Thanks for all your help!

[chimpanzee]

the hdtool also locks it with a master password so even things went wrong, you can redo it though doing in on the Xbox remove the most probable cause of error, typo of those random characters ;-)

[ibnuts]

I've got a 1.6 softmodded with Evox using UXE.  I FTPed all the files from the "...UDATA\4d530017\62D648EBF155" folder into E:\Apps\Chimptools folder on my Xbox.  I then tried to telnet before connecting any drives to see how it would work (since I've never used telnet before etc.).  It connected just fine (says RemoteX Telnet Server V1.1) to the Xbox's C:\ drive , but the only command that seems to work is "dir"  When I try anything else (cd, e:, f: etc) it says "Unknown Command "xxxx"" (xxxx being whatever command).  

What am I doing wrong?  I tried logging in using root:xbox and xbox:xbox (separately, of course) as my user/pass, but then it doesn't even log in (note, xbox:xbox is what I use for FTP).

[jbwrxsti]

QUOTE(ibnuts @ Apr 10 2005, 02:12 PM)

I've got a 1.6 softmodded with Evox using UXE.  I FTPed all the files from the "...UDATA\4d530017\62D648EBF155" folder into E:\Apps\Chimptools folder on my Xbox.  I then tried to telnet before connecting any drives to see how it would work (since I've never used telnet before etc.).  It connected just fine (says RemoteX Telnet Server V1.1) to the Xbox's C:\ drive , but the only command that seems to work is "dir"  When I try anything else (cd, e:, f: etc) it says "Unknown Command "xxxx"" (xxxx being whatever command). 

What am I doing wrong?  I tried logging in using root:xbox and xbox:xbox (separately, of course) as my user/pass, but then it doesn't even log in (note, xbox:xbox is what I use for FTP).

ya i have the same problem as ibnuts ^^^^^^^^^^^^

[Trevante]

RemoteX=Evox. I don't think you'be loaded the chimptools yet...