Print

[ldotsfan]

QUOTE(Usuario-X @ Jun 27 2008, 01:58 PM)

Hi I try to use your aplicattion but I have a problem

I get the error:

could not open disk image mnt/sda/linux.iso

and I serch for my USB devices and I look is mounted in mnt/sda1/

I have the same problem to lock HD because the eeprom.bin is not found.

From this:

CODE

$echo "             Are you sure to use Primary Slave [yes/no]? : \c"
      read cmd
      if [ "$cmd" = "yes" ]; then
    exec /usr/local/bin/qemu -hda /dev/hdb -cdrom /mnt/sda/linux.iso -boot d
      fi

so at the terminal command line, type this instead:

CODE

/usr/local/bin/qemu -hda /dev/hdb -cdrom /mnt/sda1/linux.iso -boot d

hdb is primary slave.  Secondary Master change to hdc, Secondary Slave hdd.

For locking,

CODE

/usr/local/bin/lockhd -a /dev/hdb

and so on.
When prompted for path to eeprom,

CODE

 while [ $retval -eq 0 ]; do
      $echo "           1. Enter a different path manually"
      $echo "           2. Exit"
      $echo "           Choose an option [1-2] : \c"

Enter 1

CODE

/mnt/sda1/eeprom/eeprom.bin

[ldotsfan]

QUOTE(Usuario-X @ Jun 28 2008, 12:03 AM)

Thanks for the help. The comand to worck with linux.iso works perfectly

but I have a problem with the lock comand

whent I enter the path manualy

/mnt/sda1/eeprom/eeprom.bin

then return to "chose option menu" an the disk not loked
only show again:

           1. Enter a different path manually
           2. Exit
           Choose an option [1-2] :

Sorry I made a mistake - has been more than one month since I last looked at the tool. It should be

CODE

/mnt/sda1/eeprom

The filename is case-sensitive. It should be all lower-case.

I checked against the code:

CODE

 read path
         if [ -f $path/eeprom.bin ]; then
            retval=1
            Epath=$path/eeprom.bin
         fi

[ldotsfan]

QUOTE(Usuario-X @ Jun 28 2008, 12:48 AM)

can you make a new release with unlock command?

What problems did you face for the unlock command? Path problem also?

[ldotsfan]

QUOTE(Usuario-X @ Jun 28 2008, 01:51 PM)

/usr/local/bin/unlockhd -a /dev/hda

That is correct if you're using primary master.

[Usuario-X]

CODE

root@slax:~# /usr/local/bin/lockhd -a /dev/hda
Working on /dev/hda

           eeprom.bin not found
           1. Enter a different path manually
           2. Exit
           Choose an option [1-2] :1
           Enter path to eeprom and push enter : /mnt/sda1/eeprom


HDD Serial                 : 5JRGRWLT
HDD Model                  : ST310014A
HDD Key                    : 771c7e69bfb79b1e8437c1f08b8103b9
HDD password from EEPROM   : ef8da429efdfc760a4502cab9acde990166649b9
Ready to attempt locking.
Are you sure you want continue [y/n] ? y

Detecting drive status...


/dev/hda
HDD Model Number                 : ST310014A
HDD Serial Number                : 5JRGRWLT
HDD Firmware Revision            : 3.09
        Master password revision code = 65534
Security supported               : Yes
Security enabled                 : No
Security locked                  : No
Security frozen                  : No
Security count expired           : No
Security enhanced erase          : No
root@slax:~#

Aparently the procedure is ok, but the drive is not locked

[ldotsfan]

QUOTE(Usuario-X @ Jun 29 2008, 09:34 AM)

For example when I try to lock the HD i get that:

CODE

root@slax:~# /usr/local/bin/lockhd -a /dev/hda
Working on /dev/hda

           eeprom.bin not found
           1. Enter a different path manually
           2. Exit
           Choose an option [1-2] :1
           Enter path to eeprom and push enter : /mnt/sda1/eeprom
HDD Serial                 : 5JRGRWLT
HDD Model                  : ST310014A
HDD Key                    : 771c7e69bfb79b1e8437c1f08b8103b9
HDD password from EEPROM   : ef8da429efdfc760a4502cab9acde990166649b9
Ready to attempt locking.
Are you sure you want continue [y/n] ? y

Detecting drive status...
/dev/hda
HDD Model Number                 : ST310014A
HDD Serial Number                : 5JRGRWLT
HDD Firmware Revision            : 3.09
        Master password revision code = 65534
Security supported               : Yes
Security enabled                 : No
Security locked                  : No
Security frozen                  : No
Security count expired           : No
Security enhanced erase          : No
root@slax:~#

Aparently the procedure is ok, but the drive is not locked

A reboot is necessary after the security command for the lock to take effect.

QUOTE(Usuario-X @ Jun 29 2008, 04:35 AM)

I use the comand line to try your aplication in all cases de procces works an a half of this pourpose

in the caseof slax the disck is only formated but the files to copi to dosck is not found

an in the unlock procedure the result is only a diplay info of eeprom and security status of the disck, but the disck not unlocked.

I coment this to make a better aplication

1. As with the original xboxhdm, the files to be copied are to be supplied by the user. The xboxhdm folder contains everything you need to remaster the linux.iso which will be used during the hdd rebuild. Of course make sure the usb drive has the new linux.iso.
2. Security commands like lock and unlock need a reboot to take effect.

[thefuNkpuNk]

ldotsfan, I sent you a PM, but the gist of it was:

This is a great idea for a tool - i have no idea how to get my hands on a computer with 2 ide channels right now... so this is my only option right now for a soft mod, so keep on developing it!

I've followed along everything in this thread, I was able to build my drive (i think), but I too, cannot lock it. When I run the lockhd command, it seems to work, but then when I try to boot - i get an error 13.

After reading the last post on this page: http://forums.xbox-s...howtopic=485838 it may be a seagate issue, so I'm trying that next.

Also - I'm also stuck using vista 64bit, so i had to use my laptop to make the usb drive bootable. Is there a newer version of the executable in bootinst.bat that runs in x64?

[ldotsfan]

QUOTE(thefuNkpuNk @ Jul 12 2008, 09:42 AM)

I've followed along everything in this thread, I was able to build my drive (i think), but I too, cannot lock it. When I run the lockhd command, it seems to work, but then when I try to boot - i get an error 13.

Also - I'm also stuck using vista 64bit, so i had to use my laptop to make the usb drive bootable. Is there a newer version of the executable in bootinst.bat that runs in x64?

Locking problems will give you an error 5 - xbox reports hdd is unlocked or an error 6 - xbox cannot unlock drive as it was locked with different password.

If you have used msdash files from a reliable source - either your own backup of real C drive (not from shadow C), Slayer's or CASH 1.1 and still hit error 13, let me know. There are so few users of this tool who come back to this thread that I don't know if there are other bugs. I'll try to help if more info. is given.

The bootinst.bat comes from SLAX 6, could you describe your problem with it in greater details?
I choose SLAX 6 as it supports USB booting out of the box, and qemu ran in it. Any other Live Linux distribution which fits the bill could be used. I've also released my source code.

Unless more users come forward and report problems, I don't think I'll be doing any more active development in it except to fix problems reported.

[ldotsfan]

QUOTE(thefuNkpuNk @ Jul 12 2008, 12:23 PM)

i don't think seagate ddo was the issue - the seagate disc didnt even recognize the drive
i copied the files from slayer's and tried the process again, but i am still getting a #13.

I guess im going to try a hotswap now, but that makes me a little uneasy.

The only info i can give you is that i am getting the same issue as usuario-x even with slayer's dash.

Are you doing a softmod for the first time or doing a hdd upgrade or trying to restore a corrupted drive?

I suspect something now. Can you download the original xboxhdm 1.9 , create the linux.iso and replace the one on the USB drive. But only use option 2 in the boot menu and don't lock from option 3. Use my xboxhdm2 menu option to lock. Am I making sense?

[thefuNkpuNk]

I WAS able to build the drive correctly with the old xboxhdm. There were less status/error messages than with the new version (i was getting a lot of read-only messages before).

I was not, however, able to lock the drive correctly. I am getting an error 5 instead of error 13 now. I'll give it a few more tries to see if i can get it to work.

[thefuNkpuNk]

Maybe this will help:

CODE

root@slax:~# lockhd -a /dev/hda
Working on /dev/hda

HDD Serial                 :             5ND5JEA6
HDD Model                  : ST3250824A
HDD Key                    : ecfc13874f9f855952d105a3e3aedd4f
HDD password from EEPROM   : 26e181bc6502eb4cc88850938558d0eed6fb3211
Ready to attempt locking.
Are you sure you want continue [y/n] ? y

Detecting drive status...

/dev/hda
HDD Model Number                 : ST3250824A
HDD Serial Number                : 5ND5JEA6
HDD Firmware Revision            : 3.AAH
        Master password revision code = 65534
Security supported               : Yes
Security enabled                 : No
Security locked                  : No
Security frozen                  : No
Security count expired           : No
Security enhanced erase          : No
root@slax:~# hdtool -d /dev/hda -e /mnt/sda1/eeprom/eeprom.bin -o LOCK
HDD Serial                 :             5ND5JEA6
HDD Model                  : ST3250824A
HDD Key                    : ecfc13874f9f855952d105a3e3aedd4f
HDD password from EEPROM   : 26e181bc6502eb4cc88850938558d0eed6fb3211
Ready to attempt locking.
Are you sure you want continue [y/n] ? y
root@slax:~# hdsecinfo
device name is required
root@slax:~# hdsecinfo /dev/hda
/dev/hda
HDD Model Number                 : ST3250824A
HDD Serial Number                : 5ND5JEA6
HDD Firmware Revision            : 3.AAH
        Master password revision code = 65534
Security supported               : Yes
Security enabled                 : No
Security locked                  : No
Security frozen                  : No
Security count expired           : No
Security enhanced erase          : No
 

I guess this is the same issue as usuario-x was having. I've tried to reboot after locking, but i get the same error 5

[ldotsfan]

QUOTE(thefuNkpuNk @ Jul 13 2008, 04:42 AM)

Maybe this will help:

CODE

root@slax:~# lockhd -a /dev/hda
Working on /dev/hda

HDD Serial                 :             5ND5JEA6
HDD Model                  : ST3250824A
HDD Key                    : ecfc13874f9f855952d105a3e3aedd4f
HDD password from EEPROM   : 26e181bc6502eb4cc88850938558d0eed6fb3211
Ready to attempt locking.
Are you sure you want continue [y/n] ? y

Detecting drive status...

/dev/hda
HDD Model Number                 : ST3250824A
HDD Serial Number                : 5ND5JEA6
HDD Firmware Revision            : 3.AAH
        Master password revision code = 65534
Security supported               : Yes
Security enabled                 : No
Security locked                  : No
Security frozen                  : No
Security count expired           : No
Security enhanced erase          : No
root@slax:~# hdtool -d /dev/hda -e /mnt/sda1/eeprom/eeprom.bin -o LOCK
HDD Serial                 :             5ND5JEA6
HDD Model                  : ST3250824A
HDD Key                    : ecfc13874f9f855952d105a3e3aedd4f
HDD password from EEPROM   : 26e181bc6502eb4cc88850938558d0eed6fb3211
Ready to attempt locking.
Are you sure you want continue [y/n] ? y
root@slax:~# hdsecinfo
device name is required
root@slax:~# hdsecinfo /dev/hda
/dev/hda
HDD Model Number                 : ST3250824A
HDD Serial Number                : 5ND5JEA6
HDD Firmware Revision            : 3.AAH
        Master password revision code = 65534
Security supported               : Yes
Security enabled                 : No
Security locked                  : No
Security frozen                  : No
Security count expired           : No
Security enhanced erase          : No
 

I guess this is the same issue as usuario-x was having. I've tried to reboot after locking, but i get the same error 5

1. You are familiar with Linux as I can see which is very helpful.
2. Part of the problem is I don't have the necessary hardware to test this, lol. My desktop is a mac mini and I 've an old laptop and the old PC I used for xboxhdm is too low spec to run this.
3. The locking/unlocking programs come straight from the original xboxhdm, I merely repackaged them to work with SLAX. Maybe they need to be recompiled for SLAX's kernel. I'm a bit surprised as the 2.6 kernel was used for locking stuff in original xboxhdm.
4. The read-only problems is probably related to the FATX changes I introduced for 32k/64k cluster size support. I can release a version with the old linux.iso to solve these problems.
5. I might need to create a SLAX development environment to solve 3 but I'm not sure how long that will take.
6. If you are OK with this, could you copy the hdtool binary to another desktop linux you might be using to try to see if it works.

[ldotsfan]

I may not be able to solve the problem as the source code for the hdtool locking ldots modified for xbox 1.6 eeprom was never released as far as I know, all I did was copy the binaries to SLAX but as you guys have reported the binaries don't want to work with the new kernel.

But let's see, maybe a new kernel will help or a search through BoardReader for the old xboxhdm development thread.. but don't hold your hopes too high on this and no definite timeframe for this.

Anyway the whole point of this is on my part I have released my source code so anybody in the future is free to take up the challenge of continuing this.

[ldotsfan]

QUOTE(ldotsfan @ Jul 23 2008, 10:26 PM)

the source code for the hdtool locking ldots modified for xbox 1.6 eeprom was never released as far as I know,

It seems the xbox linux cvs source has 1.6 eeprom support so I've compiled that and uploaded to sourceforge.

@testers: please copy the binary to your usb drive and then copy it to /usr/local/bin to replace the old tool. Please report if you are able to lock or unlock with it.  

[ldotsfan]

QUOTE(Usuario-X @ Aug 9 2008, 03:33 PM)

Hi man what I need to download?

    hdtool   ?

And The copy will be realized in Linux??

Thanks

From the sourceforge link in the first post. Yes, hdtool. To be executed in Linux.