<< 360 XM360 v2.0d Incl. Updated DLC and XBLA files (Homebrew 4 RGH/JTAG)
XM360 v2.0d Incl. Updated DLC and XBLA files (Homebrew 4 RGH/JTAG)
Category Games
PlatformXbox 360
FormatDLC
FormatPatch
Date 1 decade, 9 months
Size 17.27 MB
 
Website https://nzbindex.nl/search/?q=XM360+v2.0d+Incl.+Updated+DLC+and+XBLA+files+%28Homebrew+4+RGH%2FJTAG%29
 
Sender RGHacked360 (IQoTRQ)                
Tag XBLACollections360        
 
Searchengine Search
NZB NZB
 
Number of spamreports

Post Description

1. Unlocking DLC:
- Download XM360 referenced above and install it onto your console as Homebrew (if using FreeStyle Dash), or on your internal/external harddrive in your location of choice for easy execution within Xexmenu. (I personally run it from within FreeStyle Dash, aka FSD).
- Launch XM360
- Select "Rescan All", and run a scan (XM360 will scan your console for DLC, XBLA, TU's, and Gamesaves)
- Select "Show DLC"
- Then "Unlock DLC"
- XM360 will then unlock your DLC, and display a pop-up message advising the amount of DLC that has been unlocked
*NOTE: Some of your DLC and game Titles may appear within blue font with a message (No matching title is in the database)<----if you see this message, you will need to update your .csv files for both your dlc_titles and xbla_titles by doing the following:


2. Title Updates:
Most, if not all, DLC requires a TU to work with the DLC you have downloaded. The majority of the forum members do an excellent job with including the required TU with the DLC (& XBLA) whenever posting. Either download the TU manually with the the included DLC (or from places like the JQE Marketplace, XBUC, etc.) and then install the TU manually via FTP or automatically using 360 Content Manager to the following location:

- Internal Harddriver: HDD:\Cache\<PLACE TU HERE>
- Flashdrive: USB:\Cache\<PLACE TU HERE> *NOTE: You will need to create and inject this folder directory manually into your flashdrive as you did with the DLC folder described above following the posted link.

If you are using FSD as your dashboard, allow it to download and install the TU for you. To do this, follow these steps:
- Navigate to your select game
- Press Y (to display the options menu)
- Navigate down to "Manage Title Updates"
- Press A
- Press Y again (FSD will download and install your TU)
- After it is finished downloading select the TU and press A to activate it
*NOTE: If FSD downloads more than 1 TU, ONLY activate the latest one. You DO NOT need to activate them all.

Also, at times you will be required to place your TU within a folder labeled "000B0000" if your TU has been downloaded manually and consists of a short filename similar to something like this: tu00000008_00000000
Then place the "000B0000" folder within the same directory as your DLC folder under the Title ID folder. (Example again using Batman Arkham City referenced below)

HDD:\Content\0000000000000000\57520802\000B0000\tu00000008_00000000

3. DashLaunch Setting:
DashLaunch is an application installed onto your console which allows you to boot into a hacked dash like FSD and also provides you with the ability to tweak the nature in which your console behaves. DashLaunch has a settings file called launch.ini which sets the parameters of how your console behaves with this app installed. Within it is a setting called contpatch. If you have followed all of the steps above and your DLC still isn't working, and you have DashLaunch installed, you will need to locate your launch.ini file (in most cases it will be in the root of either your internal/external harddrive, but can also be placed within Flash Memory, BB MU or USB). Once located, you will need to transfer that file (using FTP or a flashdrive) to your PC and edit it within Notepad. If the setting contpatch does not exist within your launch.ini, do not add as it is already within it's default value of false. If contpatch = true is defined as a setting, change the value to false or remove the entry altogether. Save your file, copy onto your flashdrive or FTP to your console, and overwrite your existing launch.ini file. Rerun XM360, and then test your DLC.

(*NOTE: With the newer releases of DashLaunch, it is important to confirm that both fakelive and nonetstore have been disabled as these two settings have been known to cause issues with DLC not functioning correctly.)

Comments # 0