HDD Compatibility Partition Fixer v1

I am adding this as it helps people with devkits get backwards combatibility working on their devkits, without having to connect their hdd to a pc and manually add it.

http://forums.xbox-scene.com/index.php?showtopic=703973

I have not tested it yet as my devkit already has this partition.

 

It works... Trust me.

 

Drop the petty bickering or take it to PMs.

-hl718

 

It didn't work for me...said it worked onscreen, rebooted the kit, no partition.

 

Head over to XeDev forums and post what happened. I remember that one of the members had this issue but they couldn't see the partition due to the xbox not indexing it because the partition is empty. Try using Xport or xplorer360 if that doesn't help send a file to it in ftp. The people who tested it got it to work, I'll talk to some people about this though if your having problems. I had a lot of confirmations that it worked after a fresh format.

 

All off-topic posts in the thread have been deleted.

Discuss the topic at hand all you want. Don't discuss other users.

Underhanded insults have no place here.

-hl718

 

I had XBR format a 640GB harddrive and used this hdd partition fixer to add the missing partition. But I am still having problems using the xbox 1 emulator to boot my retail games can anyone here help me as to what I am doing wrong?

 

care to elaborate?

 

Sure thanks for the reply, after I used this hdd partition fixer to install the missing partition for xbox 1 compatibility I then used the official default.xex for backwards compatibility. It installed a $systemupdate folder and a $titleupdate folder and also installed some files in the cache folder. It installed nothing in the new partition and wouldn't boot any of my retail games that are on the list.

After reading I found that there has to be a Compatibility folder in the new partition and found a hacked emulator for xbox 1 games compatibility. Installed a Compatibility folder in the new partition put xbox.xex and xefu.xex in this folder. I put the rest of the files that came with the hacked emulator in the $titleupdate folder. Now it recognizes my games but get a Dirty Disc Error on start up. I checked the new partition and now besides my xbox.xex and xefu.xex their is now a dash folder with to things in it called xodash folder and xboxdash.xbe. The xodash folder has xonlinedash.xbe.

This is as far as I have gotten to be able to boot an xbox 1 retail game on my jtag system.

Like I said Xbr formatted my 640GB harddrive but from what I read xbr doesn't add this missing partition. So I used this program to try an be able to fix that. Now I'm really not sure what to try next and would thank you to anyone with any help.

 

Do you have an official hard drive? If so start there. Don't mess with hacked stuff until you have the basic stuff working first.

1) Boot up official hard drive.
2) Copy emu files from official hard drive to new hard drive.
3) Boot off new hard drive and try emu.

-hl718

 

That's were I am stuck I no longer have an official hard drive. I was hoping there was another way since I don't have the tools to hook this harddrive up to a computer. I found some one elses file online that is called partition2.bin that is around 256MB. They said to use this with xplorer and hit restore. But since I have nothing to hook this Hard drive up with computer I wanted to know if there was another way. When I found that they released this program I was hoping I could use this in some way instead.

If not is there a way I can extract this partition2.bin and transfer files with xexmenu?

 

Use XeXMenu 1.1. to FTP the compatibility from an original HDD to the new one. Thus no need to open your HDD. Just ask for a friend or someone to help you if you have physical access to a hard drive (via friend with 360) or if you can get someone online to send you the compatibility folder then your set. Otherwise I think you can actually mount .bin files in xplorer360 without actually having to connect a drive just drag it out of their and into your hacked drive via ftp.

 

They said you need to copy a file from xexmenu before its visible by ftp.
Stick on a usb and copy it over with xexmenu.

Edit I re read your post, it seems more like you dont have the right combat files, because if you can see the partition its not the hdd

 

Okay, so, I'm having problems getting the compatibility files working correctly too. I have an Xbox 360 Test Kit, running recovery 9328. Hopefully no one minds if I bump this topic...

Firstly, I installed the official compatibility update (2007), converted to dev, which (like problemchild said) didn't do anything besides install 2 folders on my retail emulation root. I then ran the partition fixer, which then allowed the partition to be mounted over xexmenu. I then copied all files on the retail's hddx partition to my comp, overwrote xefu.xex and xbox.xex in the copied Compatibility folder with the hacked ones (along with any file included in the hacked compat files package), made sure everything was signed to dev, and then ftp'd the modified folders to the dev's hddx partition.

When I try to run a retail copy of Halo 2 (also debug signed), it just throws a generic error "the game cannot be loaded." No white xbox 1 screen, no nothing. I've tried two different packages using the same steps, and still haven't made any progress. Thanks if you can help me.

 

Try running retail signed version.

 

Of the game or the compatibility files?

Just tried both, same error.

 

It doesn't work like that you need another version of compatibility files.

 

So you can't just copy the files off of a retail's harddrive, overwrite the xex's with the patched ones, and transfer them to the dev?

(just restating, because the first post of mine was rife with mistakes, and wasn't very clear >_<)

 

I think what lllsondowll was saying was you need the dev compatibility.

 

I've found this problem on dev: using an original game, it'll result in 0xC000008B from xexploadfile if loaded straight from launcher - I suppose dev doesn't like retail games eh?

Loading xbox.xex from neighborhood results in xamloadergetlaunchdata giving bad data and hence, branching into the bad section. This can be easily patched.
xamloadergetlaunchdata must result in 0 and the loader data must be valid. I don't have the valid loader data.


What's this information for? I don't know, I thought since the people who want to play xbox1 games on a 360 devkit are people who have devkits, I thought they should be able to use the debug feature, right?

Have fun girls