Topic: XboxHDM 2.2 (USB Edition) (Read 4942 times)

scullc · « **Reply #30 on:** December 08, 2009, 03:27:00 AM »

QUOTE(ldotsfan @ Dec 7 2009, 02:10 PM)

Anyway apart from xboxhdm2.1, there are many ways to get to Rome

thought I knew a fair about the scene - but i missed that one. excellent.
I think my xbox hacking days are behind me now

(too busy) but its great to see developments like this.
I used to do the 'hotswap method' - then stick on my game save from the xboxhdm CD to the XBOX HDD (but that changed with xboxhdm2

and run the soft mod that way.
anyway good luck welandB

welandB · « **Reply #31 on:** December 11, 2009, 11:10:00 PM »

I have had some difficulty with a specific hard drive while upgrading. After becoming frustrated with the process and taking a break from that hd, I opted to upgrade to a 120gb WD hd using xboxhdm2.1.

It is amazing how smooth this went. Thank you so much, ldots and scullc. You guys really made a kickass tool. Without a computer that has two PATA connectors, I'd have been hosed without this.

I'll run through my specific process for anyone who finds himself in my hardware situation in the future:

PC has one PATA (traditionally called IDE) connector on the motherboard that is NOT the primary IDE and 6(?) SATA connectors that aren't involved with the softmodding process
PC that can boot to USB flash drive
A flash drive <- My working size for this softmod/hd upgrade was 611MB. As I have a 2GB flash drive, I wasn't concerned with paring this down. These steps don't involve the paring-down, though you can by postponing transfer of the E drive.
Router/switch connecting PC and xbox <- not exactly necessary, look for the note
No memory card or xbox-USB connector <- I made the connector, but my xbox refused to format my flash drive, so I went a route that doesn't require either of these
Original Splinter Cell for xbox for game save exploits (the actual softmodding is done through these)

Process (repeat at your own risk!):

Download Xplorer360 to PC <- Please note if you use Vista, you must run this as administrator (right-click on program, select "Run As Administrator")
Download game save exploit (from the usual places) appropriate to the game you have. I used Splinter Cell.
Download xboxhdm2.1 archive to PC and extract (link on first post of this topic)
Download Grub4Dos installer to PC and extract (link on first post of this topic) <- please note that despite their tutorial, you only have to download and extract their installer. ldot/scullc graciously configured all of the necessary files and included them in the xboxhdm2.1 download
Copy xboxhdm2.1 files to root of flash drive
Run Grub4Dos installer on flash drive using their tutorial (tutorial link on first post of this topic) <- again, skip the copying of the other archive's files to the flash drive
Hotswap original xbox hd with PC booted in Windows <- I could do this while already booted in Vista. Do at your own risk.
Open Xplorer360 and "insert files" from game save exploit archive into appropriate folders on partition 3 <- you can try to "insert folder" but this never worked for me. I had to make a new folder and properly name it and manually select each file to transfer anything TO the hd
Copy all contents of partition 1 to a backup folder on your PC. This is your xbox's virgin C drive (system and dashboard files), which I found easier to work with upon upgrading the HD. You can do this after softmodding it via FTP, but using the original, unmodified C drive files was easier for me.
Copy all contents of partition 3 to a backup folder on your PC. This is your xbox's E drive (saved games and music(unsure on music as I had none on the hd)) with all of your saved games plus the game save exploit. Backing this up after copying over the exploit just saves a step when upgrading the hd.
Select "close drive" in Xplorer360's file menu <- this sometimes caused the program to crash in Vista Business 64bit, though I never saw any problems resulting from it
Copy your backup C & E folders to corresponding folders in the "hdm" folder on the root of your flash drive <- the reason you shouldn't copy directly from Xplorer360 to your flash drive is so you have a backup on your PC.
Disconnect original hd from PC, replace in xbox, and run the game save exploit <- I never shut down my PC before disconnecting. Do at your own risk.
Run through appropriate install, specific to your exploit package
Note your xbox's IP address (from system info in UnleashX/EvolutionX dashboard) and FTP into xbox (user: xbox, pass: xbox) from PC and copy over the backup folder on your xbox's E drive (backup folder locations vary from exploit to exploit) to an appropriate backup location on your PC <- if you do not have a network, you can hotswap again and work from partition 3 in Xplorer360
Copy the eeprom.bin from this backup folder to the "eeprom" folder on the root of your flash drive.
Shut down xbox and PC
Connect new hd to PC
Boot PC from flash drive <- my BIOS is odd and has two menus for boot priority. Even after I selected to boot from USB device in the first, or selecting it from the one-time boot menu, it would still boot into Windows from my PC's main hd. Only after a half-dozen attempts did I find the second menu, which overrides the first menu AND the one-time boot menu. Go figure.
Select to boot into Slax
If using the GUI version, open the "System" icon on the desktop and browse to storage media. Hover your mouse over the hard drive you're going to use and note its mounted location (ex- /dev/hda). This will be the last time you can see it in the storage media folder and this path is important to remember.
Once Slax is loaded run xboxhd2 (from a console if using the GUI)
Select the path you noted from the storage media folder
Select option #2 to continue with part 2
Once QEMU loads (in another console window if in the GUI), run xboxhdm <- As my hard drive was always at /dev/hda, I do not know if ldot's configuration will change a /dev/hdb (or hdc, hdd) path in Slax to a /dev/hda path in QEMU.
Select "create xbox hd from scratch" <- this will run you through self-explanatory prompts, pulling appropriate data from your flash drive's xdm folder.
This will prompt you to make an F partition and possibly a G partition. F (and G) will be your "extra space" on the hd for movies or games you want to save. Unless you've upgraded your BIOS to access partitions >137gb, consider making a G partition if your F partition will exceed this and xboxhdm prompts you to do so.
Once it finishes configuring the partitions and copying files, it will return you to xboxhdm's menu
Select option #6 to check your hd's pass key from eeprom.bin. <- I haven't needed either of these numbers so far, but I've written them down and keep the piece of paper taped underneath the hd in the xbox.
Other tutorials (for xboxhdm up to v1.9) will tell you to select option #7. You don't need to as you wrote down the keys and have the lock/unlock tools on your flash drive already. I don't have a floppy drive, but I suppose you could still select this option if you have one and want to make the disk.
Select option #8 to quit
Type "poweroff" to shutdown the QEMU program. <- Sometimes QEMU would hang after telling me to turn off the computer, so I just closed the window (hit ctrl+alt if you can't see the cursor).
Run xboxhd2 (the first console you used should still be there if using a GUI) again
Select option #3 to lock your hd <- the first time I did this on my new hd, it changed the "security supported" line from no to yes, but "security enabled" was still no. I ran it again and "security enabled" changed to yes.
Shut down your PC
Disconnect the new hd from your PC and change its jumper setting to "cable select" if not already
Reconnect it to your xbox
Power up xbox and run the softmod game save exploit again

I'm thinking about changing my name to ldotsfansfan (IMG:style_emoticons/default/happy.gif)

welandB · « **Reply #32 on:** December 12, 2009, 01:57:00 AM »

I confused the drive letters and corresponding partitions. Drive C is partition 3, Drive E is partition 4.

edwardar · « **Reply #33 on:** December 27, 2009, 06:35:00 PM »

Ok, this just isn't working for me. I tried the console version, but it gives me a "runtime 4" error, no KDE, etc

So I tried the GUI version. This tells me "hdm directory not found", "eeprom.bin not found", etc. I tried replacing the ltoolz.lzm file with an older one, but then it starts asking me about a linux.iso file. I thought the point of filling the "C" and "E" folders in hdm was that no iso file was needed?! I know the USB drive is mounted as mnt/sda, but how do I know what my xbox drive is?

Is it just me? I used xboxhdm 1.9 without problems on my old PC. Is the ltoolz.lzm file in the final version the correct file?

I'd really appreciate any help, this is driving me mad!!

Bomb Bloke · « **Reply #34 on:** December 27, 2009, 06:49:00 PM »

If memory serves, the older versions (eg 2.0?) required you to create a standard XBoxHDM ISO file and include that one the USB drive. I guess if you want to try the old code, you should be following this.

scullc · « **Reply #35 on:** December 28, 2009, 08:41:00 AM »

QUOTE(edwardar @ Dec 28 2009, 02:35 AM)

Ok, this just isn't working for me. I tried the console version, but it gives me a "runtime 4" error, no KDE, etc

So I tried the GUI version. This tells me "hdm directory not found", "eeprom.bin not found", etc. I tried replacing the ltoolz.lzm file with an older one, but then it starts asking me about a linux.iso file. I thought the point of filling the "C" and "E" folders in hdm was that no iso file was needed?! I know the USB drive is mounted as mnt/sda, but how do I know what my xbox drive is?

Is it just me? I used xboxhdm 1.9 without problems on my old PC. Is the ltoolz.lzm file in the final version the correct file?

I'd really appreciate any help, this is driving me mad!!

so i can understand your problem a little better:
1. whats your system specs? you got enough RAM to run the gui version?
2. you have definitely followed the install guide to the letter (populated the HDM folders with appropriate M$ files etc?)
3. eeprom.bin is in the root of the stick in the folder eeprom.

no ISO needed for 2.1 final (all done by populating the folders).
I suspect your stick is not 'built' properly and your files are either missing or not in the right place. have another go & feedback.
IIRC (although its been a while) fwz scripts automatically 'find' your HDD for you. see this post which may help 'getting you started'.

illtww · « **Reply #36 on:** December 29, 2009, 02:29:00 PM »

QUOTE(scullc @ Dec 28 2009, 04:41 PM)

so i can understand your problem a little better:
1. whats your system specs? you got enough RAM to run the gui version?
2. you have definitely followed the install guide to the letter (populated the HDM folders with appropriate M$ files etc?)
3. eeprom.bin is in the root of the stick in the folder eeprom.

no ISO needed for 2.1 final (all done by populating the folders).
I suspect your stick is not 'built' properly and your files are either missing or not in the right place. have another go & feedback.
IIRC (although its been a while) fwz scripts automatically 'find' your HDD for you. see this post which may help 'getting you started'.

I am ALSO having problems with XboxHDM2 (USB edition)
I have sued the XBOXHDM 1.9 on my Pii 440bx board with NO problems...

New System Specs:
Core2Duo
4 sata ports
1 Pata connector
2gb ram
E2100 CPU (not exactly sure)

I think the problem is with the Grub4Dos Installer. (Preparing the MBR of the USB-STICK)
If I prepare it and copy all the xboxhdm2.1 files to the root of the USB it does NOT boot.

IF I prepare the USB with BartPE and then copy over some of the files it boots....

I cannot get the GUI version running. THe Console lite version boots but than hangs at looking for the livecd.sXX (With the hard drives attached) (Without the drives attached it boots to the "SLAX" login page...)

Am i missing something here. Have about 3 hours invested in making the the USB bootable. I have a USB stick with winxp on it and it runs and boots fine.....

Any help is appreciated!

scullc · « **Reply #37 on:** December 29, 2009, 03:30:00 PM »

illtww:

what OS are you trying to run the grub installer on?
it was tested in (mainly) XP and to a less extent Vista. I did not test it all in Win7
small point - i extracted/prepared the USB drive 1st - then ran the installer (as per my instructions)

GISJason · « **Reply #38 on:** December 30, 2009, 12:45:00 AM »

QUOTE(ldotsfan @ Dec 7 2009, 07:10 AM)

Am I missing something here? Virgin xbox with eeprom.bin? You have to softmod the xbox first to get an eeprom backup.

Anyway apart from xboxhdm2.1, there are many ways to get to Rome

Dang nice tool! I wish I read this just a few hours ago... Just got done locking a HDD ./
I assume you can recover any xbox basically by using the correct version eeprom for your xbox? Correct region and all that ya know...I've got a couple xboxs that had dead hdds so I'm just now blowin the dust off em and gettin em fixed... Nice to come back into it and see these new apps and tools available now! There's the snazzy xbox eeprom reader & writer I'm plannin on grabbin off eBay and then I'm gonna be givin this new Xboxhdm a try!

Keep up the good work!

edwardar · « **Reply #39 on:** December 30, 2009, 03:47:00 AM »

Thanks for the replies. In the end I broke the hard drive!

I was using a SATA HD with a SATA-IDE adaptor. I think the problem I had with xboxhdm2 was to do with the way my motherboard recognises drives. It recognises SATA drives as HD1 (primary) master and slave and HD2 (secondary) master and slave. PATA drives are recognised as HD0, so I'm not sure how this is picked up in linux.

I had no problems creating the boot usb device, and loaded up slax without a problem.

I think what killed the drive was that I was using chimp 2.6 on the xbox, and started copying drives and locking the drive after already receiving device errors.

Anyway, it was a spare 320gb SATA drive, so I used a spare 160gb PATA drive in the end (with Chimp 2.6) and this worked first time.

illtww · « **Reply #40 on:** December 30, 2009, 01:00:00 PM »

QUOTE(scullc @ Dec 29 2009, 11:30 PM)

illtww:

what OS are you trying to run the grub installer on?
it was tested in (mainly) XP and to a less extent Vista. I did not test it all in Win7
small point - i extracted/prepared the USB drive 1st - then ran the installer (as per my instructions)

XP SP3...

Can you copy and past the USB Prepare section? or link it? (Pretty sure i followed to a t....)

Thanks!

scullc · « **Reply #41 on:** December 31, 2009, 02:32:00 AM »

QUOTE(illtww @ Dec 30 2009, 09:00 PM)

XP SP3...

Can you copy and past the USB Prepare section? or link it? (Pretty sure i followed to a t....)

Thanks!

no big secret - its the instructions at the top of this thread. i have been lucky in which 3 different sticks i used for testing always worked.
my 1gb USB Stick is formatted to Fat32 btw.
have you tried the CD Kicker method? Both the GUI/console ISOs have a folder containing a CD-Kicker ISO (this should allow non-bootable sticks/BIOS's that don't allow USB booting to load from USB after you first boot from the CD).
Burn the CK-Kicker ISO, then boot from Cd & see if its loads that way.

***************
This is a good time as any - to say that I am taking an extended break from the scene.
Life has just got busy and I no longer have the time for this project.
Many thanks to all those who I have 'worked' with during the last year.

Cheers

***************

Bomb Bloke · « **Reply #42 on:** December 31, 2009, 04:52:00 AM »

Good luck to you, then. Hope to see you around.

spraoi · « **Reply #43 on:** January 21, 2010, 05:44:00 PM »

Does this allow hotswap softmod via usb enclosure?

ldotsfan · « **Reply #44 on:** January 22, 2010, 07:17:00 AM »

QUOTE(spraoi @ Jan 22 2010, 08:44 AM)

Does this allow hotswap softmod via usb enclosure?

This is intended for booting off an usb drive. Not quite the same thing. But somebody did this with qemu off a Mac so they must have used an usb enclosure? I also wrote this guide some time back. Similiar to the first link but on a PC.

Author Topic: XboxHDM 2.2 (USB Edition) (Read 4942 times)