-
XBoxHDM2 SourceForge Project Page
Some caveats and disclaimers:
1. This is designed to boot from USB flash drives. If your PC's BIOS does not support that, stop.
2. It is meant for advanced users as it assumes you are already familiar with xboxhdm.
3. It may not work at all and may thrash your drive. Ensure you already have eeprom.bin and can recover with the original xboxhdm.
4. Additional features over old version:
a. Boots from USB.
b. Any of the 4 IDE connections may be used now to connect Xbox HDD. No CD-ROM drive needed.
c. No reboots between HDD rebuilds and locking.
d. Automatically formats F partitions with 32k clusters if larger than 256Gb, and 64k clusters if larger than 512Gb.
e. A little GUI.
How to use:
1. Download and extract "xboxhdm2.1.zip" from the above linked project page. Copy all the folders inside the "xboxhdm2" folder to the root of your USB flash drive. Download "ltools21.lzm", rename it to "ltools.lzm", and place this in the "modules" subfolder of "slax" folder (overwriting the file that is already there). "hdtool2" and "hdparm" are also available on the project page. Copy them to the "slax" folder if you wish to use them.
2. Run "bootinst.bat" from the "boot" folder of flash drive.
3. Grab a copy of XBoxHDM v1.9 and create "linux.iso" in the usual way (populate the C/E/F folders, run "make-iso-win.bat"). Copy the ISO to the root of your flash drive. Place your "eeprom.bin" file in the "eeprom" folder located on the flash drive, NOT the "eeprom" folder within v1.9's "linux" folder.
4. Boot your PC using the USB drive. Choose option 1 in the boot menu, or wait a few seconds and it'll be automatically selected. Note that start up times will be greatly extended if you have a locked HDD attached.
5. From here, follow this tutorial written by scullc.
By the way, it is possible to use "make_iso.bat" from the "slax" folder to create an ISO version of the tool for those who have a SATA DVD drive.
Appreciate your feedback. There's probably many bugs but I need your input to fix them. Thanks.
scullc has also devised a dual-boot version (between Slax and FreeDos), see here to test it out.
-
Stickied for now. Would hate to see such a project lost and forgotten.
-
Very nice, can't wait to test, answer your PM ldots.
-
cant seem to get it to work..
http://img232.imageshack.us/img232/1088/img0094fb2.jpg
This post has been edited by kingroach: May 4 2008, 04:06 AM
-
Finally somebody willing to test it (IMG:style_emoticons/default/biggrin.gif)
@kingroach
Sorry it was a typo: it should be xboxhd2
I followed the naming convention of ldots: the tool is called xboxhdm2 but the command is called xboxhd2
All shell scripts/locking binaries are stored in /usr/local/bin
This post has been edited by ldotsfan: May 4 2008, 02:47 AM
-
I dont see any xboxhd2 scripts..
-
On the flash drive, is there a ltools file in the modules folder of the slax folder? I'll check things at my end - I might have missed out uploading the file as well.
-
there is ltools.lzm file.
-
Sourceforge ftp service is failing on me, I will PM you the link to download the correct version. Unzip the files to the slax folder so that you get a changes folder inside the slax folder of the flashdrive.
I'll fix this for good when I get sourceforge working.
Thanks for your patience for this alpha release.
-
QUOTE(ldotsfan @ May 3 2008, 11:09 PM)

Sourceforge ftp service is failing on me, I will PM you the link to download the correct version. Unzip the files to the slax folder so that you get a changes folder inside the slax folder of the flashdrive.
I'll fix this for good when I get sourceforge working.
Thanks for your patience for this alpha release.
I can always host it for you 
-
applied the patch, still xboxhd2 script doesnt show up.. also couldnt seem to mount xbox hard drive in /dev/hda. tried these commands:
mkdir /mnt/XC
mount -t fatx /dev/hda51 /mnt/XC
says no filesystem type fatx.. will try again tommorow if I have time.
-
The host OS is kernel 2.6 with no FATX support so the mount command won't work. I will look into the missing xboxhd2 problem and figure out what's wrong - when I have time again.
-
Problem reported by kingroach has been solved, updated version: Alpha 2 has been uploaded to sourceforge as per 1st post.
If you have the earlier version, just get ltools.lzm and override the file in modules folder of slax folder on usb drive.
If you don't have the earlier version, get xboxhdm2-alpha2.zip which includes the latest files.
This post has been edited by ldotsfan: May 4 2008, 02:41 PM
-
Source files uploaded to sourceforge link in first post. If anybody wants to enhance it or mess around with it. It's a bunch of shell scripts and one C language source code file with header. The rest of the functionalities depend on SLAX 6, qemu and the existing xboxhdm.
-
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.
-
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
-
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
-
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?
-
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.
-
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
-
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.
-
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?
-
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.
-
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?
-
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.
-
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
-
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.
-
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.
-
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.
-
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.
-
QUOTE(Usuario-X @ Aug 10 2008, 01:12 AM)

Ok firts copy "hdtool" to root of the USB and when Im in Linux copy to /usr/local/bin and them execute the lock or unlock command?
Thanks
Yes
-
Im having trouble getting it (Xboxhdm2 USB Edition) to load up. I have the Slax and Boot folders on my Flash Drive along with the new Linux.iso I created. So how to get the program to load up so I can use it? I followed the directions compltely and still nothing? What did I do wrong?
-
QUOTE(Infamous Ob @ Aug 15 2008, 05:55 AM)

Im having trouble getting it (Xboxhdm2 USB Edition) to load up. I have the Slax and Boot folders on my Flash Drive along with the new Linux.iso I created. So how to get the program to load up so I can use it? I followed the directions compltely and still nothing? What did I do wrong?
You need to run the bootinst.bat from the flash drive. Anyway it won't help you as my testers have yet to report back on the locking feature which was last reported by them as not working yet.
-
Well Im not worried about the locking feature if I cant even get the Program to even run....
I ran the the bootinst from my flash, and now what?
-
QUOTE(Infamous Ob @ Aug 16 2008, 02:14 AM)

Well Im not worried about the locking feature if I cant even get the Program to even run....
I ran the the bootinst from my flash, and now what?
CODE
How to use:
1. Copy all the folders and files except xboxhdm to USB flash drive.
2. Run bootinst.bat from slax folder of flash drive.
3. Copy xboxhdm folder to PC and populate the C/E/F folders as normal, run make-iso-win and copy the linux.iso to the flash drive to replace the iso there. In eeprom folder on flash drive, place your eeprom.bin
4. Boot from USB. Choose option 1 in boot menu.
5. Click on the terminal icon (looks like a PC screen) and type xboxhdm2. Follow the menu options.
6. For cloning, type clonehd in the terminal.
7. Once stage 2 done, type xboxhdm2 again to lock.
From the first post.
-
I already did, but nothing happened, Im just going to try to run the XboxHDM off of CD rom.
-
Like I said, I've been using the CD-Rom edition alot lately. I mastered it but theonly problem is I need to redo it. Im missing important files.
-
QUOTE(Usuario-X @ Aug 19 2008, 03:53 PM)

I got the error
invalid option - - d
and the drive is not locked
Seems that the command line options of hdlock from CVS differ from the version used in xboxhdm original. Or it could be the lockhd shell script. This will take a while to fix - if I can figure out how to do it and I'm not entirely sure at this point.
-
Hello
I came across Xboxhdm2 a few days ago after finding this very thread from google.
I decided to give it a go as no matter what i done i could not get Xboxhdm booting from CD, the iso would boot in a VM but burn it to CD and it failed.
So a USB version is keeping my pile of coasters down 
I have followed the set up instructions, and boot from the USB drive, Slax starts up and runs fine 
Open a terminal and type xboxhd2
that starts up and gives the warning, I type yes
i select option 1 for primary master
read the warning and type Yes
I then get an error
qemu: could not open disk image /mnt/sda/linux.iso
reading other posts in this thread i think i find the answer as i do not have sda but do have sda1
so at the prompt i type
/usr/local/bin/qemu -hda /dev/hdb -cdrom /mnt/sda1/linux.iso -boot d
but then i get a "can not open (or it might have been mount) /dev/hdb image (something along those lines should have written it down)
So i play around a bit with that line, leaving bits out changing bits see if i can get any where with it but no luck.
So i come back here hoping some one can help?
The set up is as follows
The USB drive to boot from.
The new hard drive set as primary master on IDE channel,
No other drives connected to the system at all.
The drive is windows partitioned if this makes any difference ? i just assumed that xboxhdm would sort that out.
I am very much a linux noob with work and play making me 99.9% a windows user
But i am willing to learn and try.
Hope someone can point me in the right direction as i really want to complete this and so far this utility has got me further along than any other i have given a go.
Thanks
Keith
-
CODE
/usr/local/bin/qemu -hda /dev/hda -cdrom /mnt/sda1/linux.iso -boot d
-
OK last night i set up the usb flash drive, booted the PC from it twice, it booted into Slax

Tonight i strip down the PC again and stick in the new drive for the xbox, boot from the same flash drive,
It will not boot.
Get to "looking for data directory" and then get fatal error occured - slax data not found, then a load more stuff about maybe fixing by copying slax data to c:/slax (or the linux equal)
so back into windows, format the usb stick and re do the process,
Boot form it and same error again,
So now i cant even get into slax to run xboxhdm
-
Well problems solved and the xbox is now running a bigger drive,
No need for boot CD's or boot USB sticks,
Connect new drive as pri master, old xbox drive as sec master,
Boot windows from 3rd master
Fire up VMWare
create new virtual machine, add 2 disks (the 2 real disks) as pri master and sec master,
mount the linux.iso in virtual cdrom
Boot virtual machine and away you go, pick the option to clone drives and let it do its thing.
Lock drive and pop it in the xbox, FTP into it and format F
So much easyer wish i thought on doing that before,
It must be something to do with the hardware as to why my system keeps failing to boot from cd's or USb with this on them, i have not had any problems with other boot disks. yet VMware will boot the iso that i burn to disk no problems.
-
QUOTE(Usuario-X @ Jun 26 2008, 11: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.
Same error here /sda1
cant find the eeprom.bin file
help
ho to put path manually?
-
lol after alot of trial and error i figured that your could just do
mkdir /mnt/sda
umount -a
mount -t vfat /dev/sda* /mnt/sda
where * is the number usually 1 anywayz but everything will werk fine after that but i get only that far and it formats the partitions correctly....but rebuildin it dosent seem to work
maybe need to restart xboxhd2 script after each time u use it?
-
ah figured it out lol
turns out u cant use the xboxhdm 1.9 thats included with it u need a fresh new copy lol i feel kinda stupid
-
Oh no, xboxhdm2 does not support kingroach Ndure3.1.
I made from xboxhdm1.9 so that I included Ndure3.1 installation files. Then made out of that linux.iso.
I then made usb bootable hdm2 and replaced the 10mb linux.iso with my ndure linux.iso.
The problem is that there is no xbrowser command, and I cannot find my cd anywhere.
Also in my system I have only 1 ide port and 6 sata ports. Sataports are default hda hdb etc..
my xbox hd on primary ide is sdb or similar. the xboxhd2 command works only 4 default linux names. I need xboxhdm2 to see available hard disks, where I can chose hard disk out of. Also I would need that virtual cd browser to be able to locate ndure script and mod my xbox.
-
QUOTE(Jeroi @ Mar 25 2009, 10:28 AM)

Oh no, xboxhdm2 does not support kingroach Ndure3.1.
Kingroach Ndure C folder to C folder of iso, E folder likewise. The script just copies files. Or if you have msdash ver 5960 files, you can copy those to C and E folder inside the iso followed by the Kingroach Ndure files, overriding them if necessary.
I never finished xboxhdm2. You can try using qemu or vmware (see my sig under usb/ide) to overcome the SATA limitations of the original xboxhdm.
-
QUOTE(Usuario-X @ Aug 25 2008, 10:19 PM)

Revisiting an old problem, the lack of locking in xboxhdm2. I think hdtool is a dead end so I started looking at the source of hdparm 9.15 instead. Seems that this version doesn't check for ASCII strings
CODE
static void get_security_password (int handle_NULL)
{
unsigned int maxlen = sizeof(security_password) - 1;
if (argc < 2) {
fprintf(stderr, "missing PASSWD\n");
exit(EINVAL);
}
argp = *argv++, --argc;
if (!argp) {
fprintf(stderr, "missing PASSWD\n");
exit(EINVAL);
}
if (strlen(argp) > maxlen) {
fprintf(stderr, "PASSWD too long (must be %d chars max)\n", maxlen);
exit(EINVAL);
}
memset(security_password, 0, maxlen + 1);
if (!handle_NULL || strcmp(argp, "NULL"))
strcpy(security_password, argp);
printf("security_password=\"%s\"\n", security_password);
while (*argp)
++argp;
}
So if we could take the hex conversion code from hdtool:
CODE
188 for (i=0; i 189 char ch[2];
190 ch[0] = password[2*i];
191 ch[1] = password[2*i+1];
192
193
194 if ( !((ch[0]>='0' && ch[0]<='9') || (ch[0]>='a' && ch[0]<='f') || (ch[0]>='A' && ch[0]<='F')) ||
195 (!((ch[1]>='0' && ch[1]<='9') || (ch[1]>='a' && ch[1]<='f') || (ch[1]>='A' && ch[1]<='F')))) {
196 printf("Error - invalid character in password - must be ");
197 printf("between 0-9, and a-f\n");
198 exit(0);
199 }
200 ide_password = strtoul(ch,0l,16);
201 }
there is some basis for a working hd lock in linux kernel 2.6 via hdparm. Of course, my C language proficiency isn't up to par so I'll need help. Now I need to find a modern linux distribution with a toolchain which will support hdparm compiling.
-
QUOTE(ldotsfan @ May 2 2009, 12:09 PM)

I think hdtool is a dead end so I started looking at the source of hdparm 9.15 instead.
Found that SLAX kernel lacks the CONFIG_IDE_TASK_IOCTL switch but Knoppix does have this set. hdtool might still work.
-
QUOTE(ldotsfan @ May 3 2009, 12:40 PM)

Found that SLAX kernel lacks the CONFIG_IDE_TASK_IOCTL switch but Knoppix does have this set. hdtool might still work.
CONFIG_IDE_TASK_IOCTL is the key, was able to lock the hdd in Knoppix 6.1 with the hdtool2 binary
Now a matter of moving the kernel into SLAX or alternatively remaster Knoppix with the necessary xboxhdm2 files. Finally locking with xboxhdm2 is near reality.
-
QUOTE(ldotsfan @ May 3 2009, 05:34 PM)

Now a matter of moving the kernel into SLAX
Uploaded the kernel compiled with CONFIG_IDE_TASK_IOCTL set to sourceforge. Now to figure out how to get SLAX to boot the kernel..
-
QUOTE(scullc @ May 4 2009, 01:11 AM)

you are doing great work with this ldotsfan
i am watching this with keen interest.
i will offer testing support if necessary
Thanks for the interest and it's done - the hdd locking
I'm uploading the new version which is based on SLAX 6.1.1 as I type - takes a while as my ISP caps the upload bandwidth. Unzip the file contents to your usb flash drive and you should have the slax folder, boot folder and eeprom folder at the root of the flash drive. Grab a copy of xboxhdm1.9 (the original version by ldots) , create the linux.iso as per the original instructions and place the linux.iso at the root of the flash drive. Start a command prompt in Windows to run bootinst.bat from the boot folder to make the flash drive bootable (as per the the first post in the thread).
The command to use should be xboxhd2 in step 5 and 7 of the original post. After choosing the partition to activate, choose boot option 2 (from the original xboxhdm1.9)
I welcome feedback on the tool from your testing.
By the way, it is possible to use make_iso.bat in slax folder to create an ISO version of the tool. For those who have a SATA DVD drive.
-
Looks to be a very useful tool.
your efforts are greatly appreciated
I'll be trying this out on my next XBOX hdd format (soon)
-
QUOTE(scullc @ May 5 2009, 05:59 PM)

**first a little warning. I could not get the flash drive bootable from within Vista
.the bootinst.bat executed perfectly within XP.
Heres how I did it:
1. I put the HDD (as master) on the IDE slot. I disconnected any SATA HDD.
2. Booted USB Slax.
3. Noted how my USB drive was mounted in Slax (sdb1)
4. Typed xboxhd2 into the console
5. Selected No 5 (lock HDD..) it failed to find the right path.
6. I selected No 1 (type path manually) which was /mnt/sdb1/eeprom
7. The HDM locking screen appeared
8. Locked as per screen instructions
Thanks scullc for the very detailed instructions and testing procedure - it's good to know somebody else had success as well with the tool.
The path for the eeprom is a bit surprising - it might be:
/mnt/sdb/eeprom
/mnt/sdb1/eeprom
/mnt/sda1/eeprom
/mnt/sda/eeprom
etc, I wonder why
I need to think about how to automatically figure it out in the script so to ease it for first-timers or non-linux users.
I'll see if I can do anything about the Vista booting of usb. In the meantime, are there any guinea pigs for end to end testing - from hdd rebuilding to locking?
-
The end to end testing has been done and it all works…with just a little persuasion.
Here’s how I did it – I’ll assume you know how to boot Slax, note your USB mount point & run xboxhd2 in the console.
Selected No 1(work on primary master – that being hda)
Followed the on-screen instructions
Then it got stuck when I was asked:
Are you sure to use Primary Master [yes/no]? : I typed yes.
This was the response:
Warning: No DNS servers found
qemu: could not open disk image /mnt/sda/linux.iso
I assumed it cannot ‘see’ the mounted image at sdb1 (the installer keeps looking for it at sda). I therefore entered this (slightly adjusted) code from page 2 of your thread into the console to match my mounted USB drive & HDD mount points:
/usr/local/bin/qemu -hda /dev/hda -cdrom /mnt/sdb1/linux.iso -boot d
…which worked straightaway (!!) and booted the familiar HDM console. I then rebuilt the stock HDD from scratch quickly & painlessly. I then exited HDM and retyped xboxhd2 to gain access to the locking console (see my previous post for instructions). After locking & booting my XBMC dashboard was gone and the familiar MSDash appeared which confirmed it has been rebuilt & locked successfully.
Hope that helps
-
Thanks, once again , your detailed instructions are very helpful. I guess the tool is working - it just needs a fix to the pathname problems to be more newbie-friendly. I'll get to it once I find the time.
Good to know finally we have an alternative to good old xboxhdm. Anybody else wants to volunteer to test it please?
-
I think I fixed the path problems, get ltools21.lzm from sourceforge, delete away ltools.lzm in modules subfolder of slax folder on usb drive and replace with this file.
Before executing xboxhd2, use kmenu (bottom left most icon in slax desktop). Navigate to system option, information center, and select partitions. Use the partition size as a guide to take note of the path to your usb flash drive, for example:
/mnt/sda1 or
/mnt/sdb1 or
/mnt/sdc1 or
/mnt/sda or
/mnt/sdb etc
When you execute xboxhd2, you will be prompted to enter this value, for example /mnt/sda1
If this is working, xboxhdm2 will be complete.
-
I fear I'm somewhat useless as far as testing goes (I'm away from home for the next few days), but lemme say congratulations anyway.
So if I'm understanding this at all (and I'm suspecting I'm not), could this perchance be used to temporarily open the lock on a drive and play with the contents, without rebooting (and hence closing the lock on the drive again)? Something the original XBoxHDM can't do?
-
the updated ltools21.lzm module works!
well done (again) ldotsfan
I just had to remember to type the full mount point in i.e: /mnt/sdb1
piece of cake after that (rebuilt & locked with no problems)
you are still however required to input the full path for locking i.e: /mnt/sdb1/eeprom
btw - alternative way i used to see mount point:
double click system icon (on desktop)
double click storage media
I then hovered over my USB stick (slaxxbox) and it showed mount point (sdb1) in attributes.
-
QUOTE(Bomb Bloke @ May 6 2009, 08:24 PM)

I fear I'm somewhat useless as far as testing goes (I'm away from home for the next few days), but lemme say congratulations anyway.
So if I'm understanding this at all (and I'm suspecting I'm not), could this perchance be used to temporarily open the lock on a drive and play with the contents, without rebooting (and hence closing the lock on the drive again)? Something the original XBoxHDM can't do?
Thanks.
The honest answer to your question is I don't know - but the command to use would be hdtool -e /mnt/sda/eeprom/eeprom.bin -o UNLOCK -d /dev/hda followed by xboxhd2. May I know what scenario do you have in mind for doing this?
QUOTE(scullc @ May 7 2009, 01:11 AM)

small query ldotsfan - is their any value in an unlocker (like original HDM) or even is that possible?
Sorry I didn't get the question. Could you rephrase it for me?
QUOTE(scullc @ May 7 2009, 05:27 PM)

the updated ltools21.lzm module works!
well done (again) ldotsfan
I just had to remember to type the full mount point in i.e: /mnt/sdb1
piece of cake after that (rebuilt & locked with no problems)
you are still however required to input the full path for locking i.e: /mnt/sdb1/eeprom
btw - alternative way i used to see mount point:
double click system icon (on desktop)
double click storage media
I then hovered over my USB stick (slaxxbox) and it showed mount point (sdb1) in attributes.
Thanks again for the detailed testing and for the tip on the alternative way to view the path.
-
QUOTE(scullc @ May 8 2009, 06:42 AM)

I was thinking - can this tool unlock the xbox drive or not?
But is seems you may have already given a solution from Bomb Blokes post?
Is that right?
I realized what is the problem. I never described the unlocking capability in xboxhdm2 or documented it - did I?
Bomb Bloke was asking for a temporary unlock before a reboot, you are referring to an permanent unlock like xboxhdm (original).
Good news - unlockhd command is available too. The syntax is exactly the same as the original xboxhdm, unlockhd -a /dev/hda or unlockhd -a /dev/hdb and so on. I recycled the same hdtool binary from ldots' xboxhdm that does the underlying locking/unlocking work - there is no magic in this
-
QUOTE(ldotsfan @ May 7 2009, 10:49 PM)

May I know what scenario do you have in mind for doing this?
This.
That is to say, could this be used to temporarily unlock those stock drives that have masterpasscodes, then slap on a softmod without the EEPROM and without hotswapping?
To my understanding, while the old XBoxHDM could unlock the drive in this manner, you couldn't get back to the file copying console thingies without rebooting the system (hence the lock'd snap shut again before you could take advantage of it).
Granted, it wouldn't work for all X-Boxes. I've no idea as to what percentage. But it'd still be pretty cool.
Presumably if "unlockhd" is available, "hdunlock" is too?
-
QUOTE(Bomb Bloke @ May 8 2009, 09:57 AM)

That is to say, could this be used to temporarily unlock those stock drives that have masterpasscodes, then slap on a softmod without the EEPROM and without hotswapping?
How does unlockstockhd command sound? It will come with the option to select either Western Digital or Seagate stock hdd. Then the known master password for either hdd will be automatically applied.
Shouldn't be too difficult to implement . But of course whether it actually works is a separate issue - are there anybody out there willing to test this with a stock unmodded xbox - preferably with a Western Digital hdd?
-
QUOTE(ldotsfan @ May 8 2009, 09:44 PM)

Shouldn't be too difficult to implement . But of course whether it actually works is a separate issue - are there anybody out there willing to test this with a stock unmodded xbox - preferably with a Western Digital hdd?
Heck, I'll go out and buy another stock box next week...
QUOTE(scullc @ May 9 2009, 01:00 AM)

i have a Seagate HDD here. in facts its the one i have being doing the testing on.
if this HDD is reverted back to MSDash via HDM and locked with its epproom - does this not constitute a stock drive?
Probably not... It's hard to say. Unlocking a drive probably removes the stock master passcode. Probably.
Locking a different drive in such a way that it'll end up with a master passcode (eg through ConfigMagic - the code'll be TEAMASSEMBLY), then fully unlocking/relocking it with something that doesn't (eg ATAPWD), would be the way to test this. If the master code set by ConfigMagic is still there, then it can be assumed that your stock drive would've also maintained it's stock code.
Of course, if your drive was re-locked using the Linux based tools, then it certainly won't have it's original master code anymore (it'll've been changed to XBOXSCENE).
-
QUOTE(Bomb Bloke @ May 9 2009, 09:23 AM)

Heck, I'll go out and buy another stock box next week...
Probably not... It's hard to say. Unlocking a drive probably removes the stock master passcode. Probably.
Locking a different drive in such a way that it'll end up with a master passcode (eg through ConfigMagic - the code'll be TEAMASSEMBLY), then fully unlocking/relocking it with something that doesn't (eg ATAPWD), would be the way to test this. If the master code set by ConfigMagic is still there, then it can be assumed that your stock drive would've also maintained it's stock code.
Of course, if your drive was re-locked using the Linux based tools, then it certainly won't have it's original master code anymore (it'll've been changed to XBOXSCENE).
Thanks for the faith in the tool but it's really difficult to predict the outcome.
The command to use (assuming WDC hdd on primary master)
CODE
hdtool -d /dev/hda -p 5744435744435744435744435744435744435744435744435744435744435744 -o UNLOCK
for Seagate
CODE
hdtool -d /dev/hda -p 536561676174652020202020202020202020202020202020202020202020202020 -o UNLOCK
-
QUOTE(ldotsfan @ May 9 2009, 11:01 AM)

The command to use (assuming WDC hdd on primary master)
I uploaded hdparm to sourceforge. It has a flag to toggle between master and user password and natively uses ASCII passwords - which is useful for the scenario Bomb Bloke wants to test.
Subsequently it will probably evolve into the xboxhdm's ATAPWD equivalent in xboxhdm2 but runs from SLAX (like the rest of the tool) instead of DOS.
-
QUOTE(ldotsfan @ May 10 2009, 07:44 AM)

I uploaded hdparm to sourceforge. It has a flag to toggle between master and user password and natively uses ASCII passwords - which is useful for the scenario Bomb Bloke wants to test.
Subsequently it will probably evolve into the xboxhdm's ATAPWD equivalent in xboxhdm2 but runs from SLAX (like the rest of the tool) instead of DOS.
To install hdparm, copy it to slax folder on usb drive. Navigate to the folder and start a console.
Parameters supported
CODE
--security-set-pass PASSWD Lock drive, using password PASSWD:
Use 'NULL' to set empty password.
Drive gets locked if user-passwd is selected.
--security-unlock PASSWD Unlock drive.
--security-disable PASSWD Disable drive locking.
The above commands may optionally be preceded by these options:
--security-mode LEVEL Use LEVEL to select security level:
h high security (default).
m maximum security.
--user-master WHICH Use WHICH to choose password type:
u user-password.
m master-password (default).
Example of a temporary unlock of primary master hdd (until the next reboot)
CODE
hdparm --user-master m --security-unlock XBOXSCENE /dev/hda
To check security status
CODE
hdsecinfo /dev/hda
-
testing has slowed...
the unlockhd command worked perfectly. no probs at all. thanks again for your great work.
i then tried a rebuild of the HDD and am fairly sure i encountered the familiar path problem & had to reinput the path manually to find the .iso (/usr/local/bin/qemu -hda /dev/hda -cdrom /mnt/sdb1/linux.iso -boot d)
this was a few days ago - and my memory now hazy
i'll retest as soon as and let you know.
the work is on hdparm is coming along nicely. good work, man!
-
QUOTE(scullc @ May 12 2009, 04:42 PM)

the unlockhd command worked perfectly. no probs at all. thanks again for your great work.
Great
QUOTE(scullc @ May 12 2009, 04:42 PM)

i then tried a rebuild of the HDD and am fairly sure i encountered the familiar path problem & had to reinput the path manually to find the .iso (/usr/local/bin/qemu -hda /dev/hda -cdrom /mnt/sdb1/linux.iso -boot d)
an elusive bug. Do you remember the sequence that triggered it?
QUOTE(scullc @ May 12 2009, 04:42 PM)

the work is on hdparm is coming along nicely. good work, man!
It's intended to give ATAPWD like capability, I didn't write hdparm, it's another sourceforge hosted open-source project , I merely compiled it in SLAX.
Can I appeal for more testers for xboxhdm2? Thanks..
-
ok so I have followed all the steps but when i try to boot it the prompt tells me that it is unable to find the kernel image:linux... Can I please get a hand with this?
-
QUOTE(lordcukraz @ May 13 2009, 10:48 AM)

ok so I have followed all the steps but when i try to boot it the prompt tells me that it is unable to find the kernel image:linux... Can I please get a hand with this?
Tell us more:
1. OS you are using: XP, Vista, Windows 7 RC etc
2. Brand of usb drive and size.
3. Folders and files on usb drive.
4. Steps and sequence you used, from which posts.
5. Does your PC support USB booting? Have you ever booted from usb drive successfully prior to this?
-
QUOTE(ldotsfan @ May 12 2009, 01:58 PM)


an elusive bug. Do you remember the sequence that triggered it?
managed to repeat that 'bug' ldotsfan,
1. booted slax with locked HDD - boot takes about 5 mins with my locked drive!
2. used the unlock command (unlockhd -a /dev/hda) - worked no prob
3. started xboxhd2
4. choose to go for a rebuild using selection 1.
5. inputted path (sdb1) & as heeded usual warnings...until 'Are you sure to use Primary Master [yes/no]? - it then replied 'No DNS Servers found....'
6. i then inputted full path (/usr/local/bin/qemu -hda /dev/hda -cdrom /mnt/sdb1/linux.iso -boot d) but saw a warning 'could not open 'dev/kqemu' in the console background.
i just quickly looked at the HDM screen & selected HD generate code part. it displayed a qemu harddisk?
AM i right in assuming that a reboot will be needed to re-build once unlocking done?
have downloaded hdparm - will test when i get time
cheers
-
QUOTE(lordcukraz @ May 14 2009, 01:23 AM)

3:The contents of xboxhdm2 just as they were when I downloaded them and my linux.iso from xboxhdm as well as the eeprom.bin from my xbox.
4:Followed your initial post.
5:Yes it does support USB booting. It starts to boot from USB and then tells me it can't find the kernel image : linux
1. Navigate to the root folder of your flash drive , start a command prompt and execute this command
CODE
dir /s .
There's a dot after the /s Copy the contents to pastebins and give the link here.
2. Did you read post #68 and #76 for the updated instructions?
Need a mod's help to modify post #1 since the instructions are obsolete.
QUOTE(scullc @ May 14 2009, 02:52 AM)

AM i right in assuming that a reboot will be needed to re-build once unlocking done?
I may have to modify the xboxhd2 script since a reboot may not be necessary as xboxhdm2 is different in this aspect from xboxhdm. Will have a look at the bug when I get more time - thanks again for the detailed reproduction of the steps needed to duplicate the error. You are a great tester
-
QUOTE(lordcukraz @ May 15 2009, 02:24 AM)

Here you go... I just hope I can get this issue solved... A friend of mine paid to mail me his hard drive so I could format it for him (he also sent me his linux.iso) since his comp doesnt use IDE cables...
http://pastebin.com/m3ad02fd5
Seems that the file listing is missing the first few critical pages, try this instead
CODE
dir /s . > listing.txt
Then copy/paste the listing.txt into pastebin.
And the truth is your friend doesn't need your help - his xbox has 2 IDE connections, he can use xbox based tools to format his hdd: lxhdm, chimp. Check my sig for details.
-
QUOTE(lordcukraz @ May 15 2009, 10:58 AM)

Is it me or the link is dead?
QUOTE(scullc @ May 14 2009, 02:52 AM)

1. booted slax with locked HDD - boot takes about 5 mins with my locked drive!
2. used the unlock command (unlockhd -a /dev/hda) - worked no prob
3. started xboxhd2
4. choose to go for a rebuild using selection 1.
5. inputted path (sdb1) & as heeded usual warnings...until 'Are you sure to use Primary Master [yes/no]? - it then replied 'No DNS Servers found....'
6. i then inputted full path (/usr/local/bin/qemu -hda /dev/hda -cdrom /mnt/sdb1/linux.iso -boot d) but saw a warning 'could not open 'dev/kqemu' in the console background.
Found an unrelated bug in unlockhd - it ignores the drive parameter - will fix that
will continue to look for this bug you described
-
QUOTE(ldotsfan @ May 14 2009, 02:33 PM)

You are a great tester
Cheers
All down to your great coding/compiling skills!
update..
hdparm worked flawlessly on a Slayers locked HDD (password being TEAMASSEMBLY). I then immediately & successfully rebuilt the (temporarily) locked HDD with a base MSDash (but encountered the familiar path issue again) - at least i know a reboot isnt necessary. I am definitely using updated ltools21.lzm. Great not having to lock HDD again - just plugged it back into XBOX & all systems go!!
I dont have access to stock/unmodded drives. So no testing there i'm afraid - but i am pretty confident the tool will unlock a stock drive. Can anyone else help with this?
-
Ok, so I'm finally making a start to my tests...
Got a new (read: old) victim (read: console) to work on. Seagate drive. Used Krazie's NDure installer to rip the EEPROM (in case I accidentally take the unlocking process a bit too far), but otherwise the initial file system should be intact (If you discount the ton of old save games I had to delete. Why is it that every second-hand system I come across has Playboy Mansion saves on it?).
Constructed the bootable flashdrive, hooked the HDD up to a spare computer system and away it went.
The early boot process succesfully detected the Seagate, then launched into a few million HDA related errors because it couldn't read it. Eventually it decided to look for "livecd.sgn". This took about ten to fifteen minutes (plenty of time for me to note down that the USB drive was SDA1). Eventually the Slax GUI loaded up.
Attempted to go into the System thing (to be on the safe side re the USB drive path) but the screen just blacks out, the Slax loading screen appears again and I'm presented with a fresh desktop...
Booted the terminal thingy, ran HDTool and told it to do an unlock (you put one too many 20s in your sample incedently). Dunno if it worked or not, it didn't give me any errors at least. I suppose I coulda rebooted and tried again with a code I knew was wrong to see if that gave the same result, but seriously, rebooting with this locked drive takes an age and I figured someone here would already know.
Figured I couldn't try HDPArm with this drive due to the spaces in the passcode.
Ran XBoxHD2, gave it the Linux image path and took option one (drive on primary master). Confirmed the "Are you sure to use Primary Master [yes/no]?" thing and got told I was out of RAM.
It gave me some commands to unmount then remount "tmpfs" or "/mnt/shm" or... something... to 144mb. I entered them, re-ran XboxHD2 and this time a black QEMU window appeared briefly before the screen blacked out once more and a clean desktop came back up...
I tried playing with the various other shiny buttons around the place, about the only thing I could get to load was that terminal window. The other buttons (eg for the paint program) seemed to either do nothing or make the desktop reload again.
Rebooted, told the initial loading screen thingy I wanted text mode instead of the Slax GUI. After the "Are you sure to use Primary Master [yes/no]?" question it'd tell me that "svgalib" couldn't find "/etc/vga/libvga.config" (which if I was to guess means I need to be in a GUI environment).
So I dunno. Maybe I need a testing rig with more then 256mb RAM. The startup screens seemed to indicate I'd want at least 300mb. Unfortunately, my usual system is somewhat... dysfunctional... so I'm hesitant to turn that off in order to play with it's IDE cables (It can take about twenty minutes to boot under normal circumstances, and that entire time has to be spent rebooting it until it finally fires up correctly. That + extended boot time due to the locked drive might well finally drive me mad).
-
@bomb bloke
sounds like mem issue there - i think you need more ram.
for the record i have been testing on 2gb ram on my media centre - can be brain melting having to change inputs etc...and the wait for the locked xbox to boot is a right pain...but it works
@ldotsfan,
the 'fix' that you did in ltools21.lzm seems to be 'broken' on my set up here. i have been seeing that missing path too often (thought it was something i had done). so i downloaded everything again, wiped the stick (expect the eeprom), installed as required & tried a rebuild on an unlocked HDD. still asked me for the path...i know previously that part worked...but not this time! any suggestions..? went to the full hdm screen with the usual (full) input path.
-
Scavenged an extra 512mb chip, Slax became far more stable/responsive - no more random resets with 768mb, nor did it bug me about tmpfs.
Couldn't get a few things to work once QEMU was loaded though (eg xboxhd). It just gives the message "Looking for CD-ROM in /dev/hda..." (which is where my locked HDD was attached) and hung indefinitely. Longest I let it sit there was five minutes before closing the window. I assume that just means I didn't manage to deal with the lock on the drive.
(I also timed the boot sequence to be just over twelve minutes).
I tried a few variations of the capitalisation of "Seagate" with HDTool, then tried codes I knew to be outright wrong. It gives the same feedback regardless of what you use, so there's no way of knowing whether you get the code right or not (or even if it's attempting to do it's job). Is there a way to get HDTool/HDPArm to give some info on the locking status? I checked the parameter listings but couldn't see anything I thought relevant to try.
I guess I should use a standard XBoxHDM disc to try ATAPWD on the drive, see what that lets me do.
At one stage the QEMU window gained a "Press Ctrl-Alt to exit grab" tag in the title text. When this happened, the mouse cursor went bye-bye and I couldn't seem to get it back. The system hadn't frozen (the clock was still updating itself in the lower right corner), I just couldn't seem to do anything. Not sure what I did to cause that (I'd been clicking on something at the time), but even pressing "Ctrl" + "-" + "Alt" wouldn't get me out of it...
-
QUOTE(lordcukraz @ May 17 2009, 12:52 AM)

http://pastebin.com/m6f8ee52eThis is my only way to be able to do this cuz I am out of cd-r's and dvd-r's to use linux.iso and I tried the chimps way and I could never telnet to my console.
Sorry couldn't find anything obvious - have you tried wiping the usb stick clean , start afresh and run bootinst.bat again?
You could always describe your problem with chimp and telnet in another thread and I'm sure others will step in to help.
QUOTE(Bomb Bloke @ May 18 2009, 06:00 PM)

Scavenged an extra 512mb chip, Slax became far more stable/responsive - no more random resets with 768mb, nor did it bug me about tmpfs.
Couldn't get a few things to work once QEMU was loaded though (eg xboxhd). It just gives the message "Looking for CD-ROM in /dev/hda..." (which is where my locked HDD was attached) and hung indefinitely. Longest I let it sit there was five minutes before closing the window. I assume that just means I didn't manage to deal with the lock on the drive.
(I also timed the boot sequence to be just over twelve minutes).
I tried a few variations of the capitalisation of "Seagate" with HDTool, then tried codes I knew to be outright wrong. It gives the same feedback regardless of what you use, so there's no way of knowing whether you get the code right or not (or even if it's attempting to do it's job). Is there a way to get HDTool/HDPArm to give some info on the locking status? I checked the parameter listings but couldn't see anything I thought relevant to try.
1. I have some ideas on a mini edition of xboxhdm2 with less memory requirements, but need some time to test it out.. will have tighter integration between the xboxhdm portions and xboxhdm2 portions and hence avoid the qemu problems and have other benefits like drop-in C and E folders. Let' see if I can sort it out.
2. Try pressing tab key at the SLAX boot prompt and type the parameter nohd in additional to the boot parameters and see if it helps with the long boot time for a locked hdd.
3. hdparm supports this syntax:
CODE
hdparm --user-master m --security-unlock "Seagate " /dev/hda
Don't think hdtool will work the master password side of security.
4. hdsecinfo gives you the security status of the hdd:
CODE
hdsecinfo /dev/hda
QUOTE(scullc @ May 18 2009, 06:59 PM)

i am winding down the testing. it's seems complete to me and it runs bug free. great work ldotsfan
hope you have more success bomb bloke.
will keep checking your progress
Will you be interested to write a tutorial-style thread complete with pictures scullc? Many thanks in advance.
-
QUOTE(scullc @ May 19 2009, 08:23 PM)

the syntax nohd made no difference at all. in fact - it can make it slower.
best stick with the delayed boot for now - unless there are other ingenious solutions.
Not sure what happened but sourceforge removed the project hosting
Have to look for another place to host the project/files. Maybe code.google.com? In the meantime , you can find the files at sourceforge mirror sites.
EDIT: sourceforge hosting seems back to normal..
On a side note, I'm seriously thinking of moving away from SLAX due to the memory requirements and boot time issues:
xboxhdm2 = SLAX + xboxhdm.iso + a couple of shell scripts + hdtool from xboxhdm + hdparm
xboxhdm2.1 = SliTaz / TinyCore Linux and the rest of the recipe. Stay tuned..
QUOTE(scullc @ May 19 2009, 08:23 PM)

dont want to commit myself to that tutorial but it does sound interesting. wait & see...as it will definitely be a while...maybe when i get time
I'm also struggling on the "time to work on this" part
QUOTE(scullc @ May 19 2009, 08:23 PM)

one thing - i cannot seem to get internet access booting off the USB. does it work for anyone else? would make my (testing) life easier. lol
What is your NIC /wifi card?
-
QUOTE(scullc @ May 20 2009, 03:59 AM)

i will watch your adventures on this one...where will you post any news on that?
My ethernet is definitely working on my (SLAX 6.0.2) bootable/rescue USB stick.
I will post it in this thread
Maybe my kernel compiling adventure to enable hdd locking in SLAX broke other things or things changed between SLAX 6.0.1 and SLAX 6.1.1 (unlikely)
Do you have the chipset for the Ethernet connection? That will help to narrow things down.
-
Righto, with those new commands in hand I gave it another go... Unfortunately HDPArm threw back "Security-Unlock: Input/Output Error" for every code combination I tried (had to reboot once I first exceeded the security attempt counter). So I guess this particular drive just doesn't have a master code on it. Ah well.
But XboxHDM2 itself seems to be working ok. Other then the "looking for CDROM in /dev/hda" thing I mentioned, which I'm sure is down to the drive being locked.
The one other thing I was thinking of would be to include any relevant documentation/tutorials (both for XBoxHDM 1 and 2) on the Slax desktop. Would be convenient to just be able to pull them up from there as required.
-
QUOTE(Bomb Bloke @ May 21 2009, 01:01 PM)

Righto, with those new commands in hand I gave it another go... Unfortunately HDPArm threw back "Security-Unlock: Input/Output Error" for every code combination I tried (had to reboot once I first exceeded the security attempt counter). So I guess this particular drive just doesn't have a master code on it. Ah well.
CODE
hdparm -I /dev/hda
will tell you via the 0xFFFE value if the master password from factory was changed.
I also went to get a used xbox - which turns out to be a 1.6 with a WDC hdd. Have already backup the eeprom with Krayzie's Ndure - will taste my own medicine very soon. Need to find more memory for my testing PC or come up with the next version first.
QUOTE(Bomb Bloke @ May 21 2009, 01:01 PM)

The one other thing I was thinking of would be to include any relevant documentation/tutorials (both for XBoxHDM 1 and 2) on the Slax desktop. Would be convenient to just be able to pull them up from there as required.
Great idea - will do that in the next release. The xboxhdm for dummies thread can be converted via the scene's download thread tool, as for xboxhdm2, still need somebody to pen down the equivalent.
QUOTE(scullc @ May 21 2009, 01:51 AM)

the ethernet chipset is Intel® 82562V-2 - does that help?
Could you do a lsmod in SLAX 6.0.2 and see if you find a e100 module?
-
QUOTE(ldotsfan @ May 21 2009, 03:08 PM)

Could you do a lsmod in SLAX 6.0.2 and see if you find a e100 module?
no e100 module listed after typing lsmod in the console. want to see the full lsmod output?
i tried insmod e100 (?dont know if that right) but error popped up (directory doesn't exist) and I can't acess etc/rc.d/rc.modules.
in the scheme of things networking not that important to me in this build. would have been useful during testing, but we got there.
funnily enough SliTaz's network is working fine. another reason to jump ship there?
prob best if i hold off with that FAQ until/if that's done.
-
QUOTE(wer2 @ May 22 2009, 12:45 AM)

Man, I cant wait for the 2.1 to be up and going!
I just got a new HDD and I was about to set it up with XBHDM and now I see this so.... I must wait!
Don't wait , no definite time frame for the next version, I took over a year to complete 2.0
Seriously xboxhdm2 is quite usable already - unless you have low memory in your PC or other specific problems.
xboxhdm2.1 is addressing the coldswapping scenario - which is still theoretical at the moment , the long boot time with a locked disk and low memory issues. I don't even know if my approach really solves those issues or if they can be resolved in a reasonable time. So don't put it off - using xboxhdm2 as it is 
QUOTE(scullc @ May 22 2009, 03:52 AM)

funnily enough SliTaz's network is working fine. another reason to jump ship there?
prob best if i hold off with that FAQ until/if that's done.
I'm now fairly certain my kernel compilation broke the ethernet driver support as I took some shortcuts there - only updated the vmlinuz and didn't rebuild the initrd.gz with the updated kernel modules.
Anyway might not want to hold back the FAQ too long - I don't know when the next version will be done.
-
For my own benefit mainly, i kinda solved the network access problem. Its not pretty but it (mainly) works.
I also noticed that your compiled version of Slax didn't run much of the included programs.
I have my own rescue USB stick with Slax 6.0.9 on it.
I moved the files from your build into my Slax build and after a few tweaks (i.e moving eeprom to root etc..) its up & running.
Network/screen capture is working fine.
This should allow me now to start work on the FAQ.
For the record my new build will allow rebuilds of a HDD but cannot seem to lock it at all, although it goes through the motions. It will not boot with a Slax GUI if the HDD is locked. I did not test hdparm.
-
QUOTE(ldotsfan @ May 21 2009, 10:08 PM)

I also went to get a used xbox - which turns out to be a 1.6 with a WDC hdd. Have already backup the eeprom with Krayzie's Ndure - will taste my own medicine very soon.
For the record, the WDC stock hdd was locked at maximum security mode so master password was useless.
QUOTE(scullc @ May 27 2009, 04:15 AM)

This should allow me now to start work on the FAQ.
For the record my new build will allow rebuilds of a HDD but cannot seem to lock it at all, although it goes through the motions. It will not boot with a Slax GUI if the HDD is locked. I did not test hdparm.
Good to hear that and looking forward to that FAQ.
This post: http://forums.xbox-s...&...t&p=4477390 should help if you want to get hdd locking in SLAX 6.0.9.
-
QUOTE(scullc @ May 30 2009, 03:18 PM)

Never got to say - but just before the downtime - I had a brainwave.
I put the core from my slax build into yours, added kde apps & open office modules and guess what...all working
The network is working fine. kds apps (with screen capture) works great but the real success is that all features of xboxhd2 seem to be working. I have successfully un/locked using both xboxhd2 & hdparm methods. Rebuilds too have been successful.
Does it make sense to release this as a mega edition of xboxhdm2? Not sure if anybody else needs network access.. How's the boot time for the locked hdd for your edition of xboxhdm2?
QUOTE(scullc @ May 30 2009, 03:18 PM)

The FAQ (prob .pdf format) may take some time...but i will try & keep working on it. Like you, no firm date yet for it

I've given up on Slitaz - not having much luck with it as the design is too different from SLAX and usb booting is difficult to achieve for the non-Linux savvy user.
-
scullc has completed the quick user's guide for xboxhdm2: xboxhdm2 tutorial, credit to be given for the effort, thanks. Hope users of xboxhdm2 find this useful.
Could a mod update post #1 to reflect the link to the tutorial - thanks.
The forum's javascript functions seem to be broken still...wanted to create a persistence copy of http://forums.xbox-s...howtopic=244043 to upload to sourceforge... oh well...have to wait then.
-
What is a "persistence copy"? How do you wish the thread to appear?
Edit: I've made various edits to your first post. Lemme know if I got anything wrong. I'm a bit unsure about the "renaming ltools21.lzm" thing, but that's the way I did it and it worked for me...
-
QUOTE(Bomb Bloke @ Jun 2 2009, 09:24 AM)

What is a "persistence copy"? How do you wish the thread to appear?
Edit: I've made various edits to your first post. Lemme know if I got anything wrong. I'm a bit unsure about the "renaming ltools21.lzm" thing, but that's the way I did it and it worked for me...
1. I was referring to this feature:
CODE
At the top of each topic, there is a 'Topic Options' button. Selecting 'Options' will expand the topic options box.
From this box, you can select from the following options:
* Download / Print this Topic - will show the topic in a number of different formats. 'Printer Friendly Version' will display a version of the topic that is suitable for printing out. 'Download HTML Version' will download a copy of the topic to your hard drive, and this can then be viewed in a web browser, without having to visit the board. 'Download Microsoft Word Version' will allow you to download the file to your hard drive and open it up in the popular word processing application, Microsoft Word, for viewing offline.
Then the MS Word/PDF version of the xboxhdm for dummies thread can be included as part of the xboxhdm2 download.
2. The new instructions in post #1 looks good, thanks.
-
QUOTE(ldotsfan @ Jun 2 2009, 07:49 PM)

Then the MS Word/PDF version of the xboxhdm for dummies thread can be included as part of the xboxhdm2 download.
Word format it is!
-
QUOTE(Bomb Bloke @ Jun 3 2009, 02:34 PM)

Converted the xboxhdm for dummies (Word version) to PDF and uploaded to : sourceforge
-
Inspired by FrostytheSnowman's 360 Modification USB Drive, I'm doing some work with FreeDOS to see if that xboxhdm's boot option 4 - DOS tools can be integrated into xboxhdm2, but replacing floppy support with USB drive of course. Will report back if the concept is sound in execution.
-
QUOTE(ldotsfan @ Jun 6 2009, 10:05 AM)

Inspired by FrostytheSnowman's 360 Modification USB Drive, I'm doing some work with FreeDOS to see if that xboxhdm's boot option 4 - DOS tools can be integrated into xboxhdm2, but replacing floppy support with USB drive of course. Will report back if the concept is sound in execution.
Frosty's USB booting method proved to be uncompatible with SLAX's syslinux USB booting so this tool - the FreeDOS based hdd locking/unlocking tools for xboxhdm2 will have to be standalone from the rest of xboxhdm2 tool for now - but it will offer USB booting of course.
I'll send Frosty a PM to thank him for his idea and as I've reused files from his tool, will give him credit here as well.
Will upload the tool to sourceforge and write down the instructions on how to use. For those who have used Frosty's 360 Modification USB Drive, it's nothing new
-
QUOTE(ldotsfan @ Jun 6 2009, 01:05 PM)

I'll send Frosty a PM to thank him for his idea and as I've reused files from his tool, will give him credit here as well.
Will upload the tool to sourceforge and write down the instructions on how to use. For those who have used Frosty's 360 Modification USB Drive, it's nothing new

Uploaded to sourceforge.
Instructions:
1. Get Frosty's 360 Modification USB Drive from the usual place and follow his tutorial's instructions to make the usb drive bootable. But point the USB Format Tool to the files from the unzipped folder from freedos.zip instead. Likewise for step 11-12 of the tutorial - to point it to the freedos folder's contents.
2. The DOS locking/unlocking instructions - unchanged from xboxhdm.
CODE
The first two tools require that you have booted xboxhdm to linux (option 1 or 2) and made the DOS floppy from the xboxhd tool.
* lockhd, will prompt you to choose a drive and will lock the HDD with the password written to the floppy by xboxhd
* unlockhd, will both unlock the HDD and disable locking with the password written on the floppy
Should the password generated by xboxhdm be incorrect (bad eeprom dump, or a bug in the password tool <- you can never rule this out completely), you should still be able to unlock the drive again with the password stored on the floppy in : input/hdpass.txt
* hdlock, Only locks a HDD
* hdunlock, Only unlocks a HDD but doesn't disable locking. The drive will relock after reboot if you only run this tool.
* hdddisabl, Disables locking. To be used after hdunlock so that locking stays off after rebooting.
* unlockx, One option locks a drive, another option unlocks and disables locking in one go. Warning! This tools has been known to not work well with some drives. I recommend hdlock/hdunlock.
* atapwd. Good for checking the drive security status. Can also be used to unlock with the Master password. If you locked your HDD using the linux tools the Master Password is 'XBOXSCENE'. If you locked it with ConfigMagic the Master password is set to 'TEAMASSEMBLY'
-
QUOTE(scullc @ Jun 9 2009, 03:40 AM)

Ldotsfan,
I have a work in progress dual boot USB that can boot Slax (xboxhdm) and the DOS tools (which i have no experience with). Early signs are good that its working (xboxhdm & FreeDOS both boot)...but remain untested.
The dual-booting is accessible from an on-screen menu and would mean you not having 2 USB sticks to have both tools on.
Are you using the kernel memdisk method in syslinux to boot both SLAX and FreeDOS? The DOS tools create a log file which in the original xboxhdm is saved to the floppy and I've chosen not to use this method as I want the FreeDOS files on the FAT/FAT32 partition of the usb drive - exactly like how Frosty does it so that the recovery log files are saved there.
I'll be interested to hear if you are using another method that serves the same purpose.
-
I am not that familiar with the details on the boot method but the great work done by fuwi led to the multiboot system Bootable USB-Drive Utility
I am pretty sure it uses the kernel memdisk method as thats within the file structure see here
I havent got as far as FrostytheSnowman's Modifications. I am stuck with an error code 09 XBOX HDD & I want to see if it can be 'rescued' with atapwd/DOS version.
-
QUOTE(scullc @ Jun 10 2009, 03:28 AM)

but the great work done by fuwi led to the multiboot system
Bootable USB-Drive Utility
Not familiar with that, but I'll take a look, thanks.
-
QUOTE(scullc @ Jun 10 2009, 05:56 PM)

i used grub4dos to get the USB to boot using the mbr.
heres the windows
grub4dos gui version which makes it so much easier.
So grub4dos boots both xboxhdm2 and the freedos tools on FAT partition?
-
QUOTE(scullc @ Jun 11 2009, 05:13 PM)

grub4dos boots both xboxhdm2 and freedos (and other OS's like Puppy Linux) from a single FAT32 partition.
I've looked at syslinux but was unable to get the chainloading of kernel.sys (freedos) to work - I see that grub4dos has similar support for chainloading dos so it's a good option to attempt.
-
QUOTE(scullc @ Jun 15 2009, 05:33 AM)

i managed to rescue that 'locked' 640gb HDD. The Samsung (SATA) HDD - using a SATA convertor - had been previously locked using the xboxhd CD method. For whatever reason, it would not boot (error code 09) on target XBOX drive & attempts at unlocking it using xboxhdm or xbohdm2 had failed.
I solved it by using hdparm (unlocking & disabling with Master password). Anny, the owner of the HDD and developer of my multiboot USB stick, wishes to extend his thanks for your work.
Are you saying unlocking via eeprom didn't work and only master password worked?
Thank hdparm's authors - I merely packaged it into the tool
-
DOS tools work! great stuff again ldotsfan
I took a stock drive, unlocked it on my chipped machine and put i on the master IDE.
I set up a dual boot on USB using grub4dos which boots xboxhdm2 & FreeDOS.
I booted FreeDOS & successfully locked**, unlocked & disabled the HDD using the DOS locking commands. After locking, i rebooted back to FreeDOS (<1 min) and predictably reported errors on trying to read HDD. I then unlocked the drive easily using the master password. I then disabled the locking using hddisab command (btw - that's different as to what's in your earlier instructions which was hdddisabl).
This means as long as you know the password - theres no need to wait 10+ mins to unlock via xboxhdm/hdparm - DOS it in less than 1 min
I then tested xboxhdm2 on the USB boot partition. It booted perfectly with the unlocked/disabled drive. I tried to lock using the inbuilt tools but failed. I seen a new line in the locking screen 'master password revision code = 32769). Have i permanently disabled locking on this drive?
I am pretty confident that the dual boot method works. If there is any demand and as long as Anny agrees (his work), we will make available a customised download for others to test/use.
** i used XBOXSCENE as the master password. It however reported that my password was set to XBOXSCENE0 (that's a zero). I ignored the zero when unlocking it and just typed in XBOXSCENE and it worked fine.
-
QUOTE(scullc @ Jun 16 2009, 04:12 AM)

This means as long as you know the password - theres no need to wait 10+ mins to unlock via xboxhdm/hdparm - DOS it in less than 1 min
I have a development thread discussing the possibility of a DOS based version and the merits/pitfalls in this thread
QUOTE(scullc @ Jun 16 2009, 04:12 AM)

I then tested xboxhdm2 on the USB boot partition. It booted perfectly with the unlocked/disabled drive. I tried to lock using the inbuilt tools but failed. I seen a new line in the locking screen 'master password revision code = 32769). Have i permanently disabled locking on this drive?
I searched T13, couldn't find anything on revision code 32769. Not sure if a permanent unlock is possible - at least from the ATA specs - it is not. But
I honestly don't know. So both hdparm and lockhd failed to lock the SATA hdd?
QUOTE(scullc @ Jun 16 2009, 04:12 AM)

I am pretty confident that the dual boot method works. If there is any demand and as long as Anny agrees (his work), we will make available a customised download for others to test/use.
If you need hosting at sourceforge, I could add both of you to the xboxhdm2 project as developers. Send me a PM if you are keen.
-
I started again from scratch as unlocking by eeprom (using dual boot) was a non-starter (i am still using the dual boot)
i followed the instructions on page 1 to the letter (even renaming ltool21.lzm to ltools.lzm)
here's what i found & not solved - and need some help.
hdparm & command line works perfect. it unlocked the segate HDD with the master password TEAMASSEMBLY (locked by Slayers). i couldnt get hdunlock in DOS to do that.
i had also tried previously to unlock using xboxhdm but received error 'no drive found...'
the mount point for the USB drive appears to be: /mnt/live/mnt/sda1
i inputted that in but get nowwhere (apart from the error message of no drive found) after attemptign to unlock. any suggestions?
-
i know where i have being going wrong (apart from the different USB path)
i did not enter the full unlocking path
(unlockhd -a /dev/hda) DOH!!
unfortunately my slax desktop has gone missing (missing ocetet or similar) on bootup (!) so i cant retest the above currently.
time for a break i think.
-
I have figured out where things were going wrong on the dual boot:
1st - wrong initrd had creeped into my slax build - now unlocking by eeprom back in working order
2nd - I have disabled the persistent build of slax - thats fixed the missing desktop on reboot
We now have 3 ways of un/locking (xboxhdm/DOS tools/hdparm) - now thats just great!
Anny & I are ready to release the dual boot setup. Both xboxhdm & FreeDOS appear to be working solid (within my testing). Are you happy for me to upload your slax/freedos files with my muliboot setup in one large zip file (currently 130mb approx)? This would allow users to extract the contents to the root of the USB stick file & run the grub4dos gui to get the USB stick to boot.
Of course users would need to supply their own linux.iso & eeprom
-
QUOTE(scullc @ Jun 18 2009, 02:37 AM)

Anny & I are ready to release the dual boot setup. Both xboxhdm & FreeDOS appear to be working solid (within my testing). Are you happy for me to upload your slax/freedos files with my muliboot setup in one large zip file (currently 130mb approx)? This would allow users to extract the contents to the root of the USB stick file & run the
grub4dos gui to get the USB stick to boot.
Send me a PM with details of your email addresses and sourceforge accounts
I think we also need a new tutorial for the multiboot setup or at least the howto instructions, right?
-
Success. The dual boot is done and ready for download

We now have a working solution for enabling xboxhdm2 & FreeDOS HDD tools on 1 USB stick.
Credit is owed to many others - I have just repackaged what's available. Notable thanks go to:
- fuwi for his great work on multibooting.
- Anny for developing the above idea into a working solution 
- Ldotsfan for advice & help.
The multiboot is not difficult to achieve - and we have minimised the amount of steps needed. ** However please be advised - this is generally for advanced users - you could mess things up if you dont follow the instructions.
1. Follow the instructions on Page 1 for getting the normal xboxhdm2 set up files (remember you need to supply your own linux.iso & eeprom).
2. Make sure you also download FreeDOSAddOnNew.zip (<1mb)
3. Download grub4dos gui
4. Do not (Run "bootinst.bat" from the "boot" folder of flash drive) as in the original posting (to create a bootable USB stick). We'll sort that later.
5. Extract all files as instructed and extract FreeDOSAddOnNew.zip to root of USB stick.
You should therefore have in the root of your drive something similar to screenshot below

Now using the file you downloaded in step 3 - follow these instructions to install the MBR to get your USB drive to multiboot (**make sure you select the right drive to install the MBR to. Get it wrong and you could brick your PC!)
That's it! Reboot and if all gone well, you should see the grub4dos boot screen. Incidentally, there are several txt files contained within the FreeDOSAddOnNew.zip file (hdparm, DOS un/locking instructions) that may help you.
For the record:
DOS un/locking instructions can be found on Page 9 of this thread
hdparm guidance can be found on Page 6 of this thread
Good luck
-
QUOTE(scullc @ Jun 23 2009, 04:22 AM)

Success. The dual boot is done and ready for download
That's it! Reboot and if all gone well, you should see the grub4dos boot screen. Incidentally, there are several txt files contained within the FreeDOSAddOnNew.zip file (hdparm, DOS un/locking instructions) that may help you.
Now all we need is somebody to actually try this and report back on the results - sometimes I get the feeling we are the only two around interested in this tool
Actually before you came along, I thought I was the only one lol
-
I'm definitely interested, I'm just a bit busy at the moment....
-
as an end point on development of the dual boot - here is an XBOX themed grub4dos splash screen i have put together. looks better IMO.

download here
add the above file to your \grub4dos folder on the root of your stick overwriting (i'd suggest a backup 1st) the bluefractal file already contained in there.
incidentally, grub4dos splash screens are fixed at 14 colours & 640x480. so this is good as it gets
-
QUOTE(scullc @ Jun 24 2009, 07:59 PM)

as an end point on development of the dual boot - here is an XBOX themed grub4dos splash screen i have put together. looks better IMO.
add the above file to your \grub4dos folder on the root of your stick overwriting (i'd suggest a backup 1st) the bluefractal file already contained in there.
File being uploaded to sourceforge...
Thanks for the finishing touch
QUOTE(scullc @ Jun 24 2009, 07:59 PM)

as an end point on development of the dual boot
I intend to carry on this - to chainload the USB version from the CDROM version using this technique and also cross-fertilize FrostyTheSnowMan's 360 Modification USB Drive by informing him of this possibility , hope you don't mind.
So xboxhdm2 will boot from CDROM as well as USB soon...
-
QUOTE(ldotsfan @ Apr 30 2008, 12:05 AM)

d. Automatically formats F partitions with 32k clusters if larger than 256Gb, and 64k clusters if larger than 512Gb.
1. Need a mod's assistance to strike out this line on post #1 - thanks. In the early days of xboxhdm2 development, I was messing with the FATX stuff inside xboxhdm1.9 but never got this to work reliably. Now that the tool is more mature, users are better off using xbpartitioner for the large hdd support.
2. Also when re-reading scullc' xboxhdm2 howto, the comment on the lack of hdd cloning struck me -
I remembered something. I have actually moved the hdd cloning function from xboxhdm into xboxhdm2 during development phase but have completely forgotten about it.
I have never tested this but the clonehd command is available. It is untested but the cloning functionality is exactly like xboxhdm's cloning option - I merely repackaged that option into a separate shell script - YMMD.
3. qemu also has a virtual fat feature and ability to boot a Linux kernel directly - what this means is that we can potentially integrate the C and E folders inside the ISO onto the usb drive as physical folders and avoid the extra step of creating the ISO. Some testing to be done to see if this actually works.
-
QUOTE(scullc @ Jun 25 2009, 03:07 AM)

Slax booted fine but FreeDOS refused to boot - missing kernel etc...
I'll leave that one for you to figure out
I followed the instructions for grub4dos and was able to get the CD to boot and then chainload the USB files.
Here's what I did:
1. Create a folder called cdboot in the xboxhdm1.9 folder - I'm going to reuse the mkisofs command.
2. From FreeDOSAddOnNew.zip, extract grldr file and the GRUB4DOS folder to cdboot folder.
3. Create a menu.lst file in cdboot folder:
CODE
## Menu for Grub4Dos
timeout 30
default 0
splashimage = /grub4dos/bluefractal.xpm.gz
foreground = white
background = light-gray
title Slax Linux (6.0.9) & Xboxhdm2
find --set-root /kernel.sys
kernel /boot/vmlinuz ramdisk_size=6666 root=/dev/ram0 rw autoexec=xconf;telinit~4 ##changes=/slax/
initrd /boot/initrd.gz
title FreeDOS
find --set-root /kernel.sys
chainloader /kernel.sys
title Reboot
reboot
4. Start a Command Prompt and run this command at the xboxhdm1.9 folder (parent folder of cdboot folder)
CODE
mkisofs -R -b grldr -no-emul-boot -boot-load-size 4 -o grldr.iso cdboot
5. Burn grldr.iso to a CD and boot with it. I used ImgBurn. Of course the USB drive needs to be plugged in at boot time.
That's it. The CD was able to chainload both SLAX and FreeDOS after booting. FreeDOS complained on the size of my usb flash drive but booted properly. I was able to run ATAPWD. Likewise, I was able to reach the SLAX desktop with the CD boot.
-
QUOTE(scullc @ Jun 29 2009, 01:56 AM)

great surprise. thanks
i will update the quick users guide to acknowledge that relevation & also include an update on FreeDOS. Throughout all my time on the XBOX scene, i never cloned a HDD (always preferred to build my own). But its good to know - that the clone feature is included too.
Thanks for offering to update the howto. I have never used xboxhdm's cloning function myself so I conveniently forgot about it
QUOTE(scullc @ Jun 29 2009, 01:56 AM)

stunning idea...can offer to test. Unfortunately, I may lose my testing PC soon - but will try to hang on it until we get this finished
It's somehow working - had to do some quick vi hacks to xboxhd (in /ldots/2.4) and /usr/bin/find-cd and /usr/bin/find-cd2 to expect a vfat (fat32) partition instead of iso9660. But couldn't get xbrowser to work yet.
Anyway here's the qemu command to try this out
CODE
qemu -hda /dev/hda -hdc fat:/mnt/sda1/linux -kernel /mnt/sda1/linux/isolinux/fatxImage -initrd /mnt/sda1/linux/isolinux/initrd.gz -append "load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=24000 rw root=/dev/ram pci=biosirq"
I simply copied the linux folder from xboxhdm (which was previously used to create the linux ISO) over to the usb drive.
QUOTE(scullc @ Jun 29 2009, 01:56 AM)

great guide - i will try & test soon.
i knew you would solve it

thanks!
wish i had tried this way orginally as it would have been a real timesaver.
in fact your guide highlighted where i went wrong. my code is the same as yours expect for the line...'find --set-root /kernel.sys' - for some reason mine reads 'find --set-root /grldr ' - no wonder FreeDOS wouldnt boot.
I spent a fair bit of time re-reading the grub4dos guide before attempting this so it's not as simple as it looked
-
Hi,
I did some modifications to the scripts (xboxhd2, lockhd, unlockhd) to improve usability.
So you do not have to enter any path.
Maybe you want to have a look at it. Just replace ltools.lzm at slax/modules.
http://rapidshare.co...ls.lzm.zip.html
regards
f
-
hey, i downloaded this tool, and it looks great, but unfortunately all my computers that can boot off of a usb drive are sata not ide. whatev, i guess its still xboxhdm 1.9 for me.
anyway just wanna say thanks
-
QUOTE(bc54 @ Jul 5 2009, 03:10 AM)

hey, i downloaded this tool, and it looks great, but unfortunately all my computers that can boot off of a usb drive are sata not ide.
Not really a limitation anymore now that xboxhdm2 is capable of booting off CD and chainload USB. But if xboxhdm1.9 works great for you, you don't need xboxhdm2 
QUOTE(scullc @ Jul 4 2009, 07:25 PM)

here is the very slightly adjusted xboxhdm FAQ which has (minor) updates on cloning/DOS tools
@scullc: You know you can link to individual posts? Clicking on the post no will yield the URL. But thanks for the quick update.
QUOTE(fwz @ Jul 4 2009, 10:02 PM)

I did some modifications to the scripts (xboxhd2, lockhd, unlockhd) to improve usability.
@fwz: Not having much luck with the file sharing site you used, possible to reproduce the relevant changes in the scripts you did here with base64 encoding?
-
Hi.
ldotsfan, I hope you can download it this way, thanx scullc.
I also did some (very quick) modifications to xbrowser and xboxhd to work with qemu given a directory with c: & e: as fat partition instead of using the linux.iso. (just comment out cd check, and mount data to /xboxhdm or /CD.)
But there a 2 problems:
- there's a size limitation of 504mb for the fat partition (not that important, but can be annoying)
- the qemu in slax refuses to load a fat partition, I had to do it on my desktop linux
regards
f
-
QUOTE(fwz @ Jul 5 2009, 08:40 PM)

I hope you can download it this way, thanx scullc.
Got the file and started dissecting the changes
. Thanks scullc and fwz.
QUOTE(fwz @ Jul 5 2009, 08:40 PM)

But there a 2 problems:
- there's a size limitation of 504mb for the fat partition (not that important, but can be annoying)
- the qemu in slax refuses to load a fat partition, I had to do it on my desktop linux
My copy of qemu loaded the fat partition but I didn't notice the size limitation. Did a quick google and saw some references to a 512Mb limit. I suppose the xboxhd and xbrowser will need some rework to work around that. Are we better off with linux.iso?
-
QUOTE(fwz @ Jul 6 2009, 01:04 AM)

you also can handover the whole stick again as an additional drive to qemu and do some links from xboxhdm/ and CD/ to the "linux" dir on the mounted stick in qemu
Brilliant lateral thinking
Have you already made the changes to the scripts?
-
QUOTE(ldotsfan @ Jun 28 2009, 03:03 PM)

I followed the instructions for grub4dos and was able to get the CD to boot and then chainload the USB files.
that method worked for me too
I did not run any tests on it - but all seems to be working OK.
just a footnote to bc54's post as i too have a full SATA system here.
I don't have any IDE ports/connectors on that PC & am using a HTPC to run all the XBOX tests. Its way more advantageous having IDE/USB bootability on 1 system...and not ideal the way i have it at the minute.
I guess i will tackle that issue when i build my next PC
-
QUOTE(ldotsfan @ Jul 6 2009, 04:17 AM)

Have you already made the changes to the scripts?
... yes I did to xbrowser and xboxhd. The missing point is to figure out which device the usb drive is and to start qemu. (in stage1)
Thanks for feedback, scullc.
-
QUOTE(fwz @ Jul 8 2009, 07:37 PM)

The missing point is to figure out which device the usb drive is and to start qemu. (in stage1)
I thought you already did that to xboxhd2 - the autodetection of the mount point for the usb drive? Am I missing something here 
QUOTE(scullc @ Jul 8 2009, 02:22 AM)

that method worked for me too
Thanks for verifying
QUOTE(scullc @ Jul 8 2009, 01:51 AM)

It has also had the effect of making the FAQ a little redundant now - as that was generally written to cover the path issues. Nearly no need now

All in the name of progress. I'm sure the nameless users who used the tool before fwz's changes appreciate the effort you put in writing the FAQ. I know I did
-
here it is:
http://www.filefacto.../n/xboxhdm2_rar
copy linux-folder from xboxhdm1.9 to your stick and replace linux/isolinux/initrd.gz with the one in the archive.
replace ltools.lzm in slax/modules/
f
-
better try this: (just cleanups)
http://www.filefacto.../n/xboxhdm2_rar
(there's pretty short time period to edit one's post )
-
QUOTE(ldotsfan @ Jul 8 2009, 01:17 PM)

All in the name of progress.
couldn't agree more. lol
-
QUOTE(fwz @ Jul 8 2009, 02:57 PM)

I don't think I have got the gist of this development quite right as I attempted to test this for you.
I assume (?) we can delete the linux.iso and use the C:\ & E:\ folders in the xboxhdm_v1.9 folder. I followed your instructions but xboxhd2 failed to boot properly stating there is no linux folder/linux.iso. I had deleted the iso but the linux folder is definitely on the root of the drive (i followed your instructions).
incidentally - i forgot to move the eeprom from the root of the drive to the new linux folder (as in the old days)
xboxhd2 kindly reminded me!
-
...argh. sorry, there was an error. It still looked for the .iso but used the linux folder.
Forgot to change it.
http://www.filefactory.com/file/ahcc5ca/n/ltools_lzm
-
great work again fwz - it works!! no linux iso used - all files coming from c:\ & e:\ in linux folder.
i added that new ltools.lzm to the build and all booted smoothly. no errors at all.
i rebuilt a stock 8gb HDD easily but did not lock or test on xbox. will do sometime (but i am sure will work)
i like the fact that qemu does not now take over your whole screen.
-
QUOTE(scullc @ Jul 9 2009, 09:34 PM)

great work again fwz - it works!!
Is it too much to ask - to integrate the dual-booting and fwz's work into a single tool and single download: xboxhdm2.1 ?
I'll be doing my own testing of fwz's work soon.
-
@ldotsfan,
do you mean, prepare a zip file of all the files that are needed so far which would incorporate:
1. dual booting of xboxhdm2 & FreeDOS hdtools
3. fwz's script changes
(in short how my USB is set up at the minute). The end user would only then extract all contents to the root of their USB drive & get their USB bootable using this method explained previously.
The filesize would be approx140mb. Of course users would have to supply the C:\ & E:\ drive contents.
Anyhow, that would be no problem.
-
QUOTE(scullc @ Jul 10 2009, 02:42 AM)

(in short how my USB is set up at the minute). The end user would only then extract all contents to the root of their USB drive & get their USB bootable using this
method explained previously.
Exactly how I wanted it but couldn't find the words for it 
Unless fwz is planning to do some more work with the scripts?
-
here is xboxhdm2.1 in one rar file. download is approx 140mb.
this file brings incorporates all the latest developments to date (10th July 2009) including:
- dual boot set up for xboxhdm2/FreeDOS
- fwz's superb script changes
- ldotsfan continual improvements
what to do: **please note part 3 is optional but you must perform the other steps - otherwise expect to see some errors.
1. extract the zip to the root of your USB stick
2. supply your own m$ dashboard files in \linux\C
3. supply your own files (?soft mods) in \linux\E
4. supply your own eeprom in \linux\eeprom
5. use the guide here to get your USB stick bootable.
help files now located in a help folder including the xboxhdmFAQ_8.1.pdf. Although fwz's changes ensure you are no longer required to input paths manually (its all done automatically (IMG:style_emoticons/default/biggrin.gif) ) - the FAQ should help you get started.
This post has been edited by scullc: Jul 10 2009, 09:02 PM
-
QUOTE(scullc @ Jul 11 2009, 04:01 AM)

this file brings incorporates all the latest developments to date (10th July 2009) including:
- dual boot set up for xboxhdm2/FreeDOS
- fwz's superb script changes
- ldotsfan continual improvements
Thanks scullc. Did you also slip in the CD->USB chainload iso? Maybe this should be an optional download.
I'll be testing this 10th July version
We probably need to clean up the instructions on post #1 with assistance from a mod and get proper hosting - at the usual place once the testing is done.
-
QUOTE(ldotsfan @ Jul 11 2009, 12:41 AM)

Did you also slip in the CD->USB chainload iso? Maybe this should be an optional download.
(IMG:style_emoticons/default/dry.gif) Forgot! Leave that with me.
I will upload a 11th July version later if you think its necessary/find any bugs with the 10th July version.
The ISO is only 400k or so - pity about that
-
QUOTE(scullc @ Jul 11 2009, 02:29 PM)

I will upload a 11th July version later if you think its necessary/find any bugs with the 10th July version.
Maybe I'm a bit confused with the different versions of the files but I encountered some errors inside qemu. The xboxhd2 command worked but once qemu was running, xboxhd gave me errors looking for the CD and xbrowser bombed out. I found a xboxhd1 and xbrowser2 command though - are we supposed to use those?
-
... yes you are. the modified scripts are xboxhd1 and xbrowser2.
please keep in mind, that all modifications are very minimalistic, just to make it work quickly.
Maybe I can spend some more time after the exams, to get them clean and safe.
reg.
f
PS: it is still the /eeprom folder on root of the usb device to store eeprom.bin to lock from "stage1".
-
i'm a little confused too. i can fully rebuild a HDD here as long as i have M$ dashboard files in \linux\C - i just used the standard rebuild commands (xboxhd2 to run, xboxhd to launch stage 2 etc...) - if i don't have M$ dashboard files in \linux\C i get the 'can't find CD error' - not sure what that xboxhd1 commmand is for.
never ran xbrowser til now. got same error as you ldotsfan.
@fwz - thanks for clearing up what commands we're meant to be using - as 'xbrowser2' command works. thats useful to know about the eeprom. Does that mean we need two copies of the eeprom to lock using all the available methods?? i have not tried any locking yet on this new build.
if you can make sense of we're at ldotsfan, then i will upload as necessary.
-
QUOTE(scullc @ Jul 12 2009, 02:24 AM)

i'm a little confused too.
I'm still confused because of the following 
QUOTE(fwz @ Jul 12 2009, 12:50 AM)

PS: it is still the /eeprom folder on root of the usb device to store eeprom.bin to lock from "stage1".
I peeked at the source of xboxhd2 but the eeprom folder is with reference to the linux folder?
QUOTE(fwz @ Jul 12 2009, 12:50 AM)

... yes you are. the modified scripts are xboxhd1 and xbrowser2.
Alright, at least we are clear on this part.
I'll have a go at the scripts if I can find the time, my preferred folder structure is:
CODE
hdm----->C
|
|
---->E
eeprom
slax
boot
hdmboot
GRUB4DOS
help
logs
-
QUOTE(ldotsfan @ Jul 12 2009, 03:08 AM)

I'll have a go at the scripts if I can find the time
good luck with this (IMG:style_emoticons/default/wink.gif)
unfortunately due to other commitments (IMG:style_emoticons/default/sad.gif) i will be unable to run any tests/offer any input for at least 2 weeks.
However, i have decided to keep my test equipment for a while yet, so will pick this up again after 27th July.
-
QUOTE(ldotsfan @ Jul 12 2009, 04:08 AM)

I'm still confused because of the following

I peeked at the source of xboxhd2 but the eeprom folder is with reference to the linux folder?
...
hm, no it is still /eeprom/eeprom.bin
summary:
stage1:
script: /usr/local/bin/xboxhd2
requires: /linux/ (with isolinux, etc. ) on stick to lauch qemu. And and /eeprom/eeprom.bin on stick to (un)lock drive.
stage2:
scripts: /ldots/2.4/xboxhd1, /ldots/2.4/xbrowser2
requires: the complete /linux/ dir (c,e,f, "check", xbox/, etc.) mounted to xboxhdm for xboxhd1 and symlink from xboxhdm to CD for xbrowser2. (it's all done at boot)
there's still no locking at stage2, because I don't think it is possible to lock a qemu drive. (and I thougt that was the reason to take it to stage1, wasn't it?)
-
QUOTE(fwz @ Jul 12 2009, 09:09 PM)

hm, no it is still /eeprom/eeprom.bin
Yes, you are right.
QUOTE(fwz @ Jul 12 2009, 09:09 PM)

stage2:
scripts: /ldots/2.4/xboxhd1, /ldots/2.4/xbrowser2
requires: the complete /linux/ dir (c,e,f, "check", xbox/, etc.) mounted to xboxhdm for xboxhd1 and symlink from xboxhdm to CD for xbrowser2. (it's all done at boot)
there's still no locking at stage2, because I don't think it is possible to lock a qemu drive. (and I thougt that was the reason to take it to stage1, wasn't it?)
1. Which boot file was modified?
2. Yes, locking only possible in stage 1.
3. I've started modifying hdm2.1 to use the folder structure I gave in the previous post.
-
QUOTE(domezone1 @ Jul 13 2009, 03:00 PM)

Giving me the worst headache, i cant even attempt to fix this stupid thing becuase of this problem. On top of that i dont have the backup eeprom from when i softmodded it though im pretty sure i set a master password as XBOXSCENE when i soft modded it so i dont think that will be a problem.
Actually this is the biggest of your problems - no backup of the eeprom. It's unlikely the master password was set to XBOXSCENE as this is usually used by PC based linux tools like xboxhdm/xboxhdm2. Unless you intentionally unlocked the hdd with ConfigMagic/EvoX on the xbox and then locked it back during the lifetime of the softmodded xbox (this will set the master password as TEAMASSEMBLY), the installation of the softmod package itself doesn't set the master password of the hdd.
You'll going to need to do a hotswap in lieu of the missing eeprom backup. I haven't tried xboxhdm2 with hotswapping but it should work.
EDIT: You have an alternative choice for error 16, xplorer360 beta 6 which runs in Windows. The hotswapping is still needed.
As for the issue with the third master
, it can be overcome, provided the SLAX linux underlying xboxhdm2 recognizes the IDE/SATA connection. You can do a dmesg | grep hd to ascertain.
Depending on the dmesg output, varying the parameters to qemu and hdtool will allow the tool to work with /dev/hde , /dev/hdf ( the third master , third secondary etc).
CODE
/usr/local/bin/qemu -hda /dev/hde -cdrom /mnt/sdb1/linux.iso -boot d
/usr/local/bin/lockhd -a /dev/hde
-
QUOTE(ldotsfan @ Jul 12 2009, 05:05 PM)

Yes, you are right.
1. Which boot file was modified?
...
... sorry for delay. /etc/rc.d/rc.S is modified for mounting the usb drive.
-
QUOTE(fwz @ Jul 14 2009, 08:56 PM)

/etc/rc.d/rc.S is modified for mounting the usb drive.
I've followed your instructions and uploaded to sourceforge following the directory structure.
-
QUOTE(ldotsfan @ Jul 18 2009, 09:24 AM)

I've followed your instructions and uploaded to
sourceforge following the directory
structure.
From here, the simplified steps for the unified download are:
QUOTE
1. Download grub4dos gui
2. Do not (Run "bootinst.bat" from the "boot" folder of flash drive) as in the original posting (to create a bootable USB stick). We'll sort that later.
3. Extract all files as instructed and extract hdm2.1.zip to root of USB stick.
4. Now using the file you downloaded in step 1 - follow these
instructions to install the MBR to get your USB drive to multiboot (**make sure you select the right drive to install the MBR to. Get it wrong and you could brick your PC!)
5. In the hdm folder, you will find C,E,F folders corresponding to the xbox's partitions. Copy the desired files to these folders.
6. Into the eeprom folder, copy eeprom.bin (note that filename is case sensitive)
Reboot and boot off usb and you should see the grub4dos screen.
-
QUOTE(TheMattybee @ Jul 20 2009, 12:49 AM)

The boot function repeatedly insists that it can't find the kernel image even though linux.iso is in the root of my flash drive. What gives? Is there somewhere else I'm supposed to boot it? Am I supposed to extract linux.iso and dump the whole thing into the root, or what?
Reformat the flash drive to FAT (Open "My computer" and right-click on your USB drive. Choose format.. and format with FAT. instead of FAT32) and re-execute bootinst.bat. Re-extract the files to the flash drive.
-
Compiled and updated to qemu 0.10.5 for the curses support. What this means for xboxhdm2 is that the required memory footprint should be lowered as there's no need for SLAX's KDE based GUI support. It's back to basics like the original xboxhdm - a console based tool without the KDE GUI. But with the recent changes:
1. Boots from USB.
2. fwz's contributions: Drop-in C and E folders onto the usb drive without the need to create the ISO and cleaner integration between stage 1(the new stuff) and stage 2(the original xboxhdm stuff).
3. scullc's contribution: dual-boot between FreeDOS and SLAX.
4. Hdd locking/unlocking without needing a reboot after stage 2.
5. Chainloading from CDROM to USB for those machines which cannot boot from USB.
-
QUOTE(scullc @ Jul 28 2009, 06:50 AM)

is the updated qemu a new download - as i didn't find it at sourceforge?
I was still toying with the new qemu and reducing the library dependencies. I'm now done and uploaded the new file to sourceforge.
Here's the steps:
1. Download ltools-new.lzm
2. Delete ltools.lzm and qemu-0.9.1-i386.lzm from slax folder's modules folder.
3. Copy ltools-new.lzm to the modules folder.
4. Delete away 002-xorg.lzm , 003-desktop.lzm from slax folder's base folder.
5. Modify menu.lst:
CODE
kernel /boot/vmlinuz ramdisk_size=6666 root=/dev/ram0 rw autoexec=xconf;telinit~4 ##changes=/slax
to
CODE
kernel /boot/vmlinuz ramdisk_size=6666 root=/dev/ram0 rw telinit~3 ##changes=/slax
6. Login with root username and password: toor
7. At the prompt, type xboxhd2.
This version of xboxhdm2 is now very lean. I hope this helps to reduce the boot time and memory footprint requirement.
-
Had a play with hdm2.1.zip (gui) & xboxhdm2 (console).
hdm2.1.zip (gui):
- has missing eeprom folder in root of stick?
- dual boot working
- HDD rebuilt, locked, unlocked with no probs. xbrowser working. hdparm working. looks rock solid
xboxhdm2 (console):
- lean & working nicely fast (when gets to console). must admit after all this time, strange looking at console only version
- HDD rebuilt, locked, unlocked with no probs. xbrowser working. seems fine to me
- locked HDD booted in 9mins (slight improvement as was 12 mins+ with GUI version)
Personally I prefer GUI version
but the console version will help those out with a lower specced PC. I have an old PC (<512mb) around somewhere. Will test the kickerCD out on that and see if console version runs OK.
I should probably add in the kickerCD to the hdm2.1.zip build. I think it would be better providing seperate versions as in gui/console so users can download what they need. I'll get those 2 builds up as soon as testing done.
-
QUOTE(scullc @ Jul 30 2009, 06:08 PM)

I think it would be better providing seperate versions as in gui/console so users can download what they need. I'll get those 2 builds up as soon as testing done.
I concur on releasing 2 versions: console who will be called xboxhdm2.1 (Lite edition) and the GUI one xboxhdm2.1 (Full edition) and thanks for the extensive testing
Thanks also to fwz for making the recent changes possible
Don't think there's any more enhancements I can think of. Once you are done, let's request a mod's help to update post #1.
-
long story short...i can't test this in my old PC. feckin' thing wouldn't boot etc...
i decided to try the grubloader CD out on my main test PC here using the console version of xboxhdm on USB - Slax complained about missing kdm etc...I redid the menu.lst using your instructions in post206, rebuilt the iso - it then worked fine. So we need (slightly) different grubloaders for gui/console xboxhdm2.
while i did the testing, i never actually tried FreeDOS - until today. The hdm2.1zip is missing the command.com & took me a while to notice that. I put the original command.com back in - but it asks for date/time before it runs FreeDOS? Odd
I just 'returned' on those date/time entries and FreeDOS then booted fine. ATAPWD worked fine & the rest i left untested.
I'll build the iso soons with their respective grub loaders in place.
-
here are the new updates:
xboxhdm2.1-full-gui.rar approx 140mb
xboxhdm2.1-lite-console.rar approx 70mb
notes:
- i estimate you need >512mb to boot the full-gui version. it may run <512mb but your risk. in case of unexpected errors/non-boot use the lite-console version on systems <512mb
- there is a grub_cdkicker folder within each build with its own modified iso for chainloading from CD >> USB
- as usual you will need your eeprom & M$dash files
- as usual you will need to follow these instructions to get your USB to multiboot
This post has been edited by scullc: Jul 31 2009, 09:11 AM
-
QUOTE(scullc @ Jul 31 2009, 04:10 PM)

here are the new updates:
Thanks, uploading to sourceforge.
-
I tip my black hat to you all.
I just finished reading through the entire thread what an accomplishment.
I am active on many projects on several boards, I have never seen so many (talented) individuals work so well on the same project. BRAVO.....
The strangest thing; over the july fourth holiday I was working on the same/similar project ie: usb boot tools, in order to mod/clone/repair/ xbox.
I decided to take another stab at it and ran into this thread. SWEET..
From previous project I utlilzed USB_MultiBoot_10 which streamlined alot of the booting issues (boot floppy image function(console specific data) on grub4dos menu). I ran out of time and never finished.
1) Thnkx a lot for all of your work
2) Thankx a lot for SHARING your work/problem/soulitions.
Yall ROCK!
I will be testing the latest release and post any nit-piky bs I can...
☆☆☆☆☆SIKDIDIT☆☆☆☆☆
-
QUOTE(SIKDIDIT @ Aug 1 2009, 05:22 PM)

I tip my black hat to you all.
I just finished reading through the entire thread what an accomplishment.
I am active on many projects on several boards, I have never seen so many (talented) individuals work so well on the same project. BRAVO.....
There are many such examples of people collaborating on stuff in this scene: For the softmods: UDE, UDE2, UDDAE, Ndure, nkpatcher. VGA bios also benefited from contributions over a period of time - IND bios to nkpatcher which in turned contributed to those by FrostyTheSnowMan. Recent development work include the development of XBPartitioner 1.1 and an upcoming boot disc which I will leave to the author to announce in due time
.
Anyway, to all those involved in xboxhdm2 development

QUOTE
1) Thnkx a lot for all of your work
2) Thankx a lot for SHARING your work/problem/soulitions.
Yall ROCK!
I will be testing the latest release and post any nit-piky bs I can...

You're welcome to contribute as well
Since the source code is available, anybody is free to extend and enhance this tool.
-
QUOTE(SIKDIDIT @ Aug 1 2009, 10:22 AM)

I tip my black hat to you all.
I just finished reading through the entire thread what an accomplishment.
welcome to the thread & glad you enjoyed it. glad we may be able to help you
I had got hold off an old 'recycled' PC. unfortunately no room for a CD-Rom within its case (IMG:style_emoticons/default/dry.gif) - was going to test the minimum specs for the tool. i recall earlier that Bomb Bloke struggled to boot on anything less than 144mb ram - specs are listed here for safe boots of Slax.
I rebuilt a bootable CD Version of the USB tool and tested it in Sun Virtual Box
while i don't want to cloud the muddy water - i was able to boot the full gui version in 128mb - sluggish but it had booted (IMG:style_emoticons/default/smile.gif) tried 70 mb ram - booted to desktop & then sat there & failed to load desktop counterparts. incidentally - it booted nicely fast on 256mb.
Given this, its entirely possible that Slax will boot with less specs than I first thought (minimum 128mb) and the console version (currently not tested in Virtual Box) will run in much less than that. I'll try the console version sometime soon.
-
OK - made a bootable CD iso of xboxhdm2.1 lite/console & tested again within Sun Virtual Box
booted fine (& quick) at 64mb. errors at 30mb (couldn't find chroot...etc)
i am unsure how these results translate in real world situations but I hope that sheds some light/guidance on the probable working memory minimum of xboxhdm2.1 gui (128mb) & xboxhdm2.1 lite (64mb)
incidentally - no testing was done on the actual builds as Virtual Box bombs out (cant find hdm folder on iso - but is there?!)
-
QUOTE(scullc @ Aug 4 2009, 06:05 AM)

i am unsure how these results translate in real world situations but I hope that sheds some light/guidance on the probable working memory minimum of xboxhdm2.1 gui (128mb) & xboxhdm2.1 lite (64mb)
In the real world, on my test machine with 128Mb, I had issues running lite as qemu will complain and won't start stage 2, I was toying with swap memory but couldn't get it to work. I presume gui edition will need even more resources.
-
QUOTE(ldotsfan @ Aug 4 2009, 02:07 PM)

In the real world, on my test machine with 128Mb, I had issues running lite as qemu will complain and won't start stage 2
too good to be true?! does qemu grab a load of mem then?
I currently don't have the necessary parts to test this at minimum specs - maybe some other testers have & can test & report for us?
we'll leave the original specs until proven otherwise (>512mb for GUI version & <512 for lite version)
-
I just finished reading this whole thread all i can say is wow you guys ddid alot. This question may have ben answered in one of the posts, but im not sure. I have a stock xbox I added a usb port to it for file transfering. I was going to try one of the game exploits, until i saw this thread. Now to get the 2 files from the xbox that are required, would i be able to use this program to unlock it copy files over and then redo the hd or do i need the 2 files eeprom an m$ first? Also i use a laptop so i have no available ide an not about to crack laptop open, would an external hd casing work as well? Thanks in advance
-
QUOTE(dragonsbane4381 @ Aug 10 2009, 02:27 PM)

I was going to try one of the game exploits, until i saw this thread. Now to get the 2 files from the xbox that are required, would i be able to use this program to unlock it copy files over and then redo the hd or do i need the 2 files eeprom an m$ first? Also i use a laptop so i have no available ide an not about to crack laptop open, would an external hd casing work as well? Thanks in advance
Thank you for reading the thread from end to end
Actually you are better off with the gamesave exploit, you need a Windows program xplorer360 to copy the gamesave onto the usb drive. Alternative xboxhdm2 should work with hotswapping (and Kingroach Ndure 3.1) to get the files onto the temporarily unlocked hdd but nobody has actually reported success with that but it should work.
Only when the xbox is softmodded, then you have easy access to the eeprom backup.
-
Ok cool thanks for the info. Keep up the great work
-
QUOTE(ldotsfan @ Aug 11 2009, 07:30 AM)

Thank you for reading the thread from end to end

Actually you are better off with the gamesave exploit, you need a Windows program xplorer360 to copy the gamesave onto the usb drive. Alternative xboxhdm2 should work with hotswapping (and Kingroach Ndure 3.1) to get the files onto the temporarily unlocked hdd but nobody has actually reported success with that but it should work.
Only when the xbox is softmodded, then you have easy access to the eeprom backup.
Found some time tonight, if the kids stay asleep and my wife remains bitchy I will report success in the next hour or so..Cross your fingers..
☆☆☆☆☆SIKDIDIT☆☆☆☆☆
-
I did not contribute to this impressive work, and I would like to make that VERY clear. I am ONLY REPORTING MY EXPERIENCES AND OBSERVATIONS.
Objective Achived
1.Using this software "package" successfully cloned ST 310014ACE TO A ST 310014ACE FOR USE ON XBOX V1.3
2. FORMATED and assigned necessary eeprom files TO A 30 GIG excel-STOR FOR use in Xbox (have not booted yet not sure if locking function required. Although file table is in place as reported by Xplorer 360.! Sweet
Eloquent, the XboxHDM2 usb addition.
Flawless excutition and totally W.A.D.
I am not sure as to proof of success execpt for this..No one was more SHOCKED then I having (limited Linux experience none of which slax related).
Not a shot at the collaborators, I have made previous public statements regarding my opinion of them. (Read)
I am a realist; and a professional software Q/A. (Ahh the truth comes out. Accounting software specialist fun!).
My experience offers little room for anything; besides healthy skepticism.
I can not think of any related software experience I have read OR heard of involving no less than three separate operating systems XP, LINUX, D.O.S, NO LESS THAN three or four completely different file structures ALL working in true independent isolation, off key cross platform non conformity. Beautiful! What a mind f()$)k.
1. NTFS,
2. Fat-16/32 USB DRIVE
3. .ISO yeh Im counting that as a pivotal file structure..Wanna debate it?? I'm a master-de-baiter..
in addition to the true target
4. FATX Xbox file table/structure/type ish I think.
AND MORE I AM SURE
I did not contribute to this impressive work, and I would like to make that VERY clear. Although I would have cajoled, irritated and interfered as much as possible given the opportunity.
The people HEROS who have successfully completed what they set out to do, are listed below.
Sorry to those not listed, I only omitted your name cuz I hate you. 
Additionally efforts and time spent developing software utilized in this build,
I deem insignificant, inconsequential, FAR below any honorable mention. 
Thakx a CRAP LOAD
ldotsfan
Kingroach
HD10291
Usuario-X
thefuNkpuNk YEH YEH YEH YOU HELPED TOO
BIG LOSERS
Dr. Zoidburg LITTLE BITCH
SIKDIDIT "what a jerk" just what is he claiming to have done anaways?
FIND THE TYPOS, MOCK THE ERRORS. LOVE IT!
Good Show!
-
QUOTE(SIKDIDIT @ Aug 15 2009, 02:29 PM)

Good Show!
Glad you found the tool useful. I have my own opinions on who were the various key contributors to this project and I think I will keep those thoughts private
I just hope more nameless users will come forth to share their experience with the tool - be it good or bad.
Anyway the learning journey was as exciting and rewarding as the finished end product for me.
-
QUOTE(ldotsfan @ Aug 15 2009, 10:52 AM)

the learning journey was as exciting and rewarding as the finished end product for me.

couldn't agree more
i assume that the tool is doing well - since theres been no reports.
i will look at a quick re-write of the 1st post to account for the new changes and get a mod to update when needed. i'll PM you a draft when i get it done.
you OK with that ldotsfan?
-
QUOTE(scullc @ Aug 17 2009, 08:29 PM)

i will look at a quick re-write of the 1st post to account for the new changes and get a mod to update when needed. i'll PM you a draft when i get it done.
Yes, please. I've forgotten about that
Let's get post #1 updated
-
QUOTE(ldotsfan @ Aug 17 2009, 03:29 PM)

Yes, please. I've forgotten about that

Let's get post #1 updated

updated instructions on using XboxHDM2.1 (USB Edition) - Final Release has been posted in this new thread
it is intended to lock this thread from any further posts
therefore please post any issues in the above thread (soon to be stickied)
thanks