qq_tracker_code_advanced_default

Due to the very many requests I receive asking how to burn XBox360 backups on a mac, I’ve decided to put together a guide. This will be a very detailed step-by-step guide. The guide will begin with the XGD2 discs and go on to cover burning XGD3 discs.

What You Will Need to burn successful XGD2 and XGD3 XBox360 backups.

  • Latest iXtreme Firmware update for your XBox360

      iXtreme LT+ 2.0 Firmware (12.1 MiB, 1,750 hits)

  • A DVD burner compatible with iXtreme Burner Max Firmware (Buy on Amazon)
    • Liteon iHAS124B = baseline model
    • Liteon iHAS224B = 124 + LightScribe
    • Liteon iHAS324B = 124 + SmartErase
    • Liteon iHAS424B = 124 + LightScribe + SmartErase
    • Liteon iHAS524B = 124 + LabelTag + SmartErase
    • Liteon iHAS624B = 124 + LabelTag + LightScribe + SmartErase
  • iXtreme Burner Max Firmware

      iXtreme Burner Max Firmware (11.5 MiB, 2,868 hits)

  • Verbatim Dual Layer DVD’s (Buy on Amazon)
  • isoBurn 1.3 or later (Mac App Store) – to support burning XGD3 with the recently released iXtreme Burner Max Firmware. isoBurn 1.2 will still burn XGD3 discs but will force truncating of your ISO. isoBurn 1.3 has been submitted to the App Store for approval and should be available sometime this week if all goes well. There are already plans for isoBurn 1.4 that will have more features and functionality. 1.4 should be available at the beginning of next month.

What are XGD2 discs?

XGD2 (XBox Game Disc 2) is the original disc format used by Microsoft for all XBox 360 games. This format is basically the capacity of a Dual Layer DVD.

What are XGD3 discs?

XGD3 (XBox Game Disc 3) is a new format developed by Microsoft to help prevent piracy by using the extra layer of the outside of the disc basically increasing the capacity and therefore using more space then is currently available on all dual layer dvd’s on the market.

What is Truncating?

Truncating is a process by which the item being truncated is sized to a particular length. Taking a number for example 3.141592654. What if we only have 3 available boxes to fit this number into? By using truncation we could truncate this number down to 3.14, do we need the other numbers? NO we don’t. Does 3.14 change drastically because we’ve truncated it to 3 digits? NO it doesn’t.

When we truncate an ISO, all we are doing is cutting off the end of the file, most of it being meaningless data that is not needed. We do this to change the size of the ISO so that it can fit onto a standard dual layer disc.

A word of warning about truncating. In some circumstances the data being cut off while truncating contains important security information that is sometimes required for validation and could quite possibly get you banned from XBox Live. You should only use truncation as a last resort for burning XGD3 discs and when you do, make sure that you do not game online.

Layer Breaks

What is a Layer Break? A Layer Break simply put, specifies at which point on the disc, the first layer should end and the second layer should start. It has been my experience that you can set the layer break lower but not higher then what the maximum layer break supported by the media is.

Layer Breaks were first introduced to the XBox 360 scene when making backups became available. To burn a successful backup, you would have to enter a layer break that was different from the one that would be set by default.

Since we first started hearing about layer breaks several years ago, there hasn’t been much of a change, until recently. Microsoft developed a new disc format which would hold a slightly higher capacity then what is supported on all current Dual Layer DVD’s. With that came a new layer break.

It just so happens that this Layer Break is higher then the maximum supported layer break for current Dual Layer DVD’s. What does this mean? Well, on a Mac, if you try to set a layer break that is higher then the max supported by the media, the mac doesn’t know what it should do and will kindly give you your media back.

So how do we get around this issue? The very first fix was to truncate the ISO file since it was believed that the information at the end of the file was not relevant to game play. So to burn, you would truncate the ISO to the full size available on the blank Dual Layer DVD and then burn with the maximum supported layer break and your XBox360 drive firmware would take care of the rest. Keep in mind that this layer break again, was different then that used for XGD2 discs. So we are now at 3 separate Layer Breaks.

The most recent fix which seems to be the most successful is a firmware by iXtreme that will enable you to burn Dual Layer DVD’s at a higher capacity by way of overburning allowing you to use the correct layer break without having to truncate the ISO file. This method requires a special burner as well as the iXtreme Burner Max firmware.

So, what are the 3 layer breaks and when should you use them?

  • Layer Break 1 – 1913760
    - This is the original layer break and should be used with all XBox360 backups that are not labeled as being XGD3 discs.
  • Layer Break 2 - 2086912
    - This layer break can be used for XGD3 discs but only if you are truncating the ISO file to fit onto a Dual Layer DVD.
  • Layer Break 3 – 2133520
    - This layer break can be used for XGD3 discs. ONLY use this layer break if you are burning with an iXtreme Burner Max firmware updated burner that can burn the full ISO file without truncating. If you attempt to use this layer break without the special burner, your disc will be ejected.

Media

So, what media should you use when burning XGD2, XGD3, backups? Let’s take a quick second and address this. Why? because this is where most people do not believe us when we say ONLY USE VERBATIM MEDIA. Do not attempt to use anything other then Verbatim. Verbatim has been proven to be the most successful when burning backups. So unless you want to burn coasters / have your burn fail have way through, have problems with verification, etc… buy Verbatim.

Let’s put it this way, if you post a comment asking why your burn failed and I ask you what media you are using, you better answer with. “Verbatim”. If you say anything other then Verbatim, I will not help you.

Let me also add… ONLY BURN AT 2X / 2.4X. Never Never Never burn any higher then 2X. If you are impatient and you can’t wait 45 minutes for a backup to finish burning, then go ahead, burn at 4X or even at 6X and watch your burn fail or experience glitches while playing, etc… Bottom line, the amount of time you would spend burning again and again because you are using crappy media and or using a burn speed that is set too high could have been spent playing the game had you used VERBATIM MEDIA and burned at 2X speed.

So, what Media do you use and what speed do you burn at?

  • Verbatim Media (Particularly MKM-003) I’ve heard from a trusted source that they are much better because of the specific dye being used
  • 2x

Burners

So what about burners? Can the internal burner on your Mac burn XGD2 / XGD3? For the most part, yes it can. I’ve tested backups on early iMacs and MacBooks as well as a Mac Mini without issues but with the occasional coaster of course. Why do the burns sometimes work perfectly and other times they don’t? It’s because the internal burners that come with your Mac are pretty much crap, its as simple as that.

So what can you do? You can try to go through the hassle of replacing your internal burner which is a real pain or you can go purchase an external burner.

The latter leaves you with a plethora of options, in an almost overwhelming way… Which burner should I get, there are literally thousands of different ones. I will make a suggestion for you and even provide you with a link to the burner you should purchase. This particular burner I am talking about will allow you to in conjunction with isoBurn, burn backups without having to truncate your ISO file. All you have to do is flash the burner with iXtreme Burner Max firmware and voila just like magic you have now turned your Dual Layer DVD media into a higher capacity disc, that now has just enough space to hold a full XGD3 format ISO.

So, what is this magical burner? There are several models that are compatible with the firmware.

  • Liteon iHAS124B = baseline model
  • Liteon iHAS224B = 124 + LightScribe
  • Liteon iHAS324B = 124 + SmartErase
  • Liteon iHAS424B = 124 + LightScribe + SmartErase
  • Liteon iHAS524B = 124 + LabelTag + SmartErase
  • Liteon iHAS624B = 124 + LabelTag + LightScribe + SmartErase
As you can see here, you’ve got plenty of models to choose from. So if you are going to purchase an external burner you may as well purchase one that is compatible with the iXtreme Burner Max firmware so that you can burn XGD3 discs at 100% without having to truncate. You can pick these up from Amazon, NewEgg, etc… or if you’re lucky, check out your local Walmart. I found that Walmart is currently selling the iHAS324B for $25.00.
Hey, so I thought this was supposed to be a burning guide and not an informational post? Well, I thought I would educate everyone, bring them up to speed so that when I go through the guide, that everyone can understand it and then maybe there won’t be so many people out there who are confused and have no clue how to get their backup to burn.
So without further delay or blabber, here’s the guide.

Burning XGD2 / XGD3 on Mac OS X Definitive Guide

The guides below assume the following:

  • You’ve acquired an ISO file, either XGD2 or XGD3
  • You’ve purchased isoBurn 1.2, 1.3 or 1.4
  • You’ve verified your ISO file using abgx360 (Note: At the time of this post abgx360 is unable to verify XGD3 ISO’s)
  • You have Verbatim media and understand that using anything other then Verbatim could result in bad burns aka coasters.
  • You understand that you must burn at 2x
  • You understand Layer Breaks and their differences
  • You understand the difference between XGD2 and XGD3
If you’ve read the more info

first part of this guide then all of the above items should make sense to you.

Burning XGD2 / XGD3 with isoBurn 1.2

Note: isoBurn 1.2 currently does not support iXtreme Burner Max Firmware. You can still burn XGD3 discs with isoBurn 1.2 but the ISO file will need to be truncated which for the most part is not an issue. XGD2 games burn normally.

isoBurn 1.2, the version currently available on the Mac App Store is able to burn both XGD2 and XGD3 discs without issues. isoBurn will produce 100% playable backups.

To use this guide you will need the following:

  • isoBurn 1.2 (Mac App Store)
  • Verbatim Media
  • An ISO of an XBox 360 backup
After you’ve downloaded and installed isoBurn, go ahead and launch it, you will see a window similar to the image below:
This is the main interface for isoBurn 1.2. As you can see, there are not very many options. This makes isoBurn very simple to use. The following are the steps to burn XGD2 / XGD3 backups with isoBurn 1.2:
Burning XGD2 backups with isoBurn 1.2:
  • Drag your ISO / DVD file into the “Drop your disc image here” box. isoBurn will tell you the File Name, File Type and File Size.
  • Select your burner
  • Insert your blank Dual Layer DVD ONLY VERBATIM
  • Select your write speed, ONLY BURN AT 2x
  • Set your layer break - 1913760 – NOTE: If you used the .dvd instead of the .iso file the layer break will be auto populated for you
  • Check the box next to Layer Break to enable it.
  • Click Burn
  • Wait for isoBurn to finish. You’re Done
Burning XGD3 backups with isoBurn 1.2:
  • Drag your ISO / DVD file into the “Drop your disc image here” box. isoBurn will tell you the File Name, File Type and File Size.
  • Select your burner
  • Insert your blank Dual Layer DVD ONLY VERBATIM
  • Select your write speed, ONLY BURN AT 2x
  • Set your layer break - 2086912 – NOTE: If you used the .dvd instead of the .iso file the layer break will be auto populated for you and will be INCORRECT. You must manually set the layer break to 2086912 or isoBurn will eject the disc and will not burn.
  • Check the box next to Layer Break to enable it if it isn’t checked already.
  • Click Burn
  • An alert box will pop up asking you to truncate your ISO
  • Click OK
  • Wait for isoBurn to finish. You’re Done

Burning XGD2 / XGD3 with isoBurn 1.3

Note: isoBurn 1.3 will not be available until it has been approved by Apple. isoBurn 1.3 fully supports XGD3 burning and is 100% compatible with iXtreme Burner Max firmware so it will burn XGD3 without having to truncate the ISO file. XGD2 games burn normally.

isoBurn 1.3, currently awaiting approval from Apple is able to burn both XGD2 and XGD3 discs without issues. isoBurn will produce 100% playable backups.

To use this guide you will need the following:

  • isoBurn 1.3 (Mac App Store)
  • Verbatim Media
  • An ISO of an XBox 360 backup
  • A burner flashed with iXtreme Burner Max (Optional – If you want to burn full XGD3 without truncating)
After you’ve downloaded and installed isoBurn, go ahead and launch it, you will see a window similar to the image below:
Although not very apparent, you’ll notice a very small change in isoBurn 1.3 from isoBurn 1.2. With isoBurn 1.3 a verification option was added which is needed to verify 100% successful  burns of XGD3 discs… YES, ALWAYS VERIFY YOUR BURN. The following are the steps to burn XGD2 / XGD3 backups with isoBurn 1.3:
Burning XGD2 backups with isoBurn 1.3:
  • Drag your ISO / DVD file into the “Drop your disc image here” box. isoBurn will tell you the File Name, File Type and File Size.
  • Select your burner
  • Insert your blank Dual Layer DVD ONLY VERBATIM
  • Select your write speed, ONLY BURN AT 2x
  • Set your layer break - 1913760 - NOTE: If you used the .dvd instead of the .iso file the layer break will be auto populated for you
  • Check the box next to Layer Break to enable it.
  • Click Burn
  • Wait for isoBurn to finish. You’re Done
Burning XGD3 backups with isoBurn 1.3 – Truncating Method:
  • Drag your ISO / DVD file into the “Drop your disc image here” box. isoBurn will tell you the File Name, File Type and File Size.
  • Select your burner
  • Insert your blank Dual Layer DVD ONLY VERBATIM
  • Select your write speed, ONLY BURN AT 2x
  • Set your layer break - 2086912 - NOTE: If you used the .dvd instead of the .iso file the layer break will be auto populated for you and will be INCORRECT. You must manually set the layer break to 2086912 or isoBurn will eject the disc and will not burn.
  • Check the box next to Layer Break to enable it if it isn’t checked already.
  • Click Burn
  • An alert box will pop up asking if you would like to Truncate, Try Without Truncating or Cancel
  • Click OK to Truncate
  • Wait for isoBurn to finish. You’re Done
Burning XGD3 backups with isoBurn 1.3 – iXtreme Burner Max Firmware Method:
  • Drag your ISO / DVD file into the “Drop your disc image here” box. isoBurn will tell you the File Name, File Type and File Size.
  • Select your burner
  • Insert your blank Dual Layer DVD ONLY VERBATIM
  • Select your write speed, ONLY BURN AT 2x
  • Set your layer break - 2133520 – NOTE: If you used the .dvd instead of the .iso file the layer break will be auto populated for you
  • Check the box next to Layer Break to enable it if it isn’t checked already.
  • Check the box to Verify After Burn
  • Click Burn
  • An alert box will pop up asking if you would like to Truncate, Try Without Truncating or Cancel
  • Click Try Without Truncating
  • Wait for isoBurn to finish burning
  • Wait for isoBurn to finish verifying. You’re Done

Burning XGD2 / XGD3 with isoBurn 1.4

isoBurn 1.4, currently available on the Mac App Store is able to burn both XGD2 and XGD3 discs without issues. isoBurn 1.4 fully supports XGD3 burning and is 100% compatible with iXtreme Burner Max firmware so it will burn XGD3 without having to truncate the ISO file. XGD2 games burn normally.

To use this guide you will need the following:

  • isoBurn 1.4 (Mac App Store)
  • Verbatim 2.4x Media
  • An ISO of an XBox 360 backup
  • A burner flashed with iXtreme Burner Max (Optional – If you want to burn full XGD3 without truncating)
Enhancements to this version:
  • Added Optimal Layer Break button, for auto setting the layer break for XGD3 discs (Truncating / Full Burn)
  • Added Cancel button to the burn dialog so that you can cancel the burn process
  • Added Alert Popup to alert you if an error occurred
  • Added Alert Popup to alert you when the burn finished
  • Added Alert Sound to alert you if an error occurred
  • Added Alert Sound to alert you when the burn finished
  • Added Data Transfer Rate to the burn dialog
  • Added Burn Speed to the burn dialog
After you’ve downloaded and installed isoBurn, go ahead and launch it, you will see a window similar to the image below:

Although not very apparent, you’ll notice a very small change in isoBurn 1.4 from isoBurn 1.3. With isoBurn 1.4 an Optimal Layer Break button was added which helps you set the layer break by detecting the media size and determining the maximum layer break. isoBurn with the help of the Optimal Layer Break button will auto set the layer break for you for XGD3 discs. For XGD2 it is still necessary to enter 1913760 for the layer break. The following are the steps to burn XGD2 / XGD3 backups with isoBurn 1.4:
Burning XGD2 backups with isoBurn 1.4:
  • Drag your ISO / DVD file into the “Drop your disc image here” box. isoBurn will tell you the File Name, File Type and File Size.
  • Select your burner
  • Insert your blank Dual Layer DVD ONLY VERBATIM
  • Select your write speed, ONLY BURN AT 2.4x
  • Set your layer break - 1913760 - NOTE: If you used the .dvd instead of the .iso file the layer break will be auto populated for you
  • Check the box next to Layer Break to enable it.
  • Click Burn
  • Wait for isoBurn to finish. You’re Done
Burning XGD3 backups with isoBurn 1.4 – Truncating Method:
  • Drag your ISO / DVD file into the “Drop your disc image here” box. isoBurn will tell you the File Name, File Type and File Size.
  • Select your burner
  • Insert your blank Dual Layer DVD ONLY VERBATIM
  • Select your write speed, ONLY BURN AT 2.4x
  • Set your layer break by clicking on the Optimal Layer Break button or enter it manually - 2086912 - NOTE: If you used the .dvd instead of the .iso file the layer break will be auto populated for you and will be INCORRECT. You must manually set the layer break to 2086912 or isoBurn will eject the disc and will not burn.
  • Check the box next to Layer Break to enable it if it isn’t checked already.
  • Click Burn
  • An alert box will pop up asking if you would like to Truncate or Cancel
  • Click OK to Truncate
  • Wait for isoBurn to finish. You’re Done
Burning XGD3 backups with isoBurn 1.4 – iXtreme Burner Max Firmware Method:
  • Drag your ISO / DVD file into the “Drop your disc image here” box. isoBurn will tell you the File Name, File Type and File Size.
  • Select your burner
  • Insert your blank Dual Layer DVD ONLY VERBATIM
  • Select your write speed, ONLY BURN AT 2.4x
  • Set your layer break by clicking on the Optimal Layer Break button or enter it manually - 2133520 - NOTE: If you used the .dvd instead of the .iso file the layer break will be auto populated for you
  • Check the box next to Layer Break to enable it if it isn’t checked already.
  • Check the box to Verify After Burn
  • Click Burn
  • Wait for isoBurn to finish burning
  • Wait for isoBurn to finish verifying. You’re Done

 

If you have any questions that this guide doesn’t cover, feel free to ask. If you think any of the information in this guide is incorrect, please contact me and I will verify and correct the guide.

If you’ve read the entire guide and followed it word for word, number for number and you are getting coasters then you haven’t followed the guide word for word, number for number OR you may have a batch of defective media which isn’t likely but possible or your burner is defective which is more likely.

I hope that you all have enjoyed reading this guide as much as I’ve enjoyed writing it. Seriously, I’m probably the only person with a blog that hates writing.. haha.

It’s been a while since I’ve put up a tutorial regarding anything dealing with XBox360. There is a reason for that… Quite simply, God of War III came out on the PS3 as well as Gran Turismo 5 so I had no choice but to ditch the 360 and get a PS3. In my opinion it was a good move. I don’t want to make this post about comparing the 360 to the PS3, so with that in mind, I would like to post up a quick tutorial on how to burn Xbox 360 backups using a new app I developed called isoBurn. isoBurn, simply put is an app that burns ISO’s and DMG’s for the Mac. It is the only app that I am aware of that can correctly burn backups of 360 games using native Mac OS X API’s, better yet, I have tested this app on OS X 10.7 (Lion) the next release of Apple’s operating system and it works flawlessly.

Tools you will need for a successful Burn:

  • isoBurn 1.0 (Available at the Mac App Store – Link) NOTE: As of 10/4/2011, Version 1.2 has been submitted to the Mac App Store with support for XGD3
  • abgx360 for Mac (Available on the abgx website – Mirror 1)
  • Blank Dual Layer Verbatim Media (All the others suck in my opinion and will not constantly burn a working game)
  • A Mac running at least OS X 10.6 (Snow Leopard)
  • A good DVD burner. The ones that come with the Mac’s are not the best and you would be better off with a good external burner.
  • A backup of a 360 game that you would like to burn
  • A modded Xbox360 running firmware iXtreme LT + for best compatibility

Ok, so now that you’ve got everything you need, fire up abgx360. We use abgx360 to verify the ISO and make sure that everything is properly patched and to generate a .dvd file if there isn’t one already. At the end of the tutorial I will cover briefly how you can use isoBurn to verify your disc to ensure that it has been burned properly. This is a good way to check some discs that you may have burned previously that don’t work, at least you will be able to know why they don’t work.

Verify your ISO with abgx360:

Open abgx360 and then open up your ISO file of the game by clicking on the blue folder icon to the right of the text input field. You should have something similar to the below illustration.

Now click on the AutoFix tab and copy the settings below.

When you have everything set correctly you can click on the blue Launch button at the very bottom it should turn green when you hover over it with your mouse.

After clicking on the Launch button, a Terminal window should open and you should start seeing a bunch of text similar to the below. DO NOT INTERRUPT THIS PROCESS. Let it do its thing.

Notice the lines in Red, the game I am working with has a blank DMI, a blank PFI and my Stealth check has failed. These are all bad things and fortunately are all things that abgx360 will fix for us.

You will notice that towards the bottom you’ll see some nice green lines of text. PFI, DMI, Video and Stealth have all been fixed, now it just needs to verify the CRC of the ISO. Let it finish, be patient this could take a few minutes. Finally we know that the program has finished when we see the line AutoFix was successful!

You can now close the Terminal and abx360. We can now move on to burn our game using isoBurn… Do me favor, when you get a chance, please rate isoBurn on the Mac App Store.

 

Burn your ISO with isoBurn:

Go ahead and open up isoBurn, if you haven’t downloaded it yet you can get it here from the Mac App Store. The interface of isoBurn is pretty simplistic which makes it a very easy tool to work with.

Opening isoBurn should present you with an interface as shown below:

Let’s quickly go over the interface. The big square on the top left is where you drag your ISO or DVD file into. Tip: If you drag your DVD file into the square, isoBurn will automatically set the correct layer break for you. If you drag in the ISO you have to set the layer break manually. To the right of the square you have File Name, File Type and File Size, these should all be obvious.

The Drive drop down will allow you to choose which burner you want to use if you have more then one. The speed allows you to select your burn speed, which should be 2x. isoBurn displays some general information about your chosen burner below the drive selection and speed pop ups. There is also a button that allows you to eject your disc if you need to.

The last section of the Burn interface is Burn Settings, this is where you would manually set your layer break if you used the ISO instead of the DVD file. From here you have the option of selecting to eject the disc or mount the disc after burn. Last but not least, we have the Burn button, when you’re ready to burn, click it. Now for the tutorial with a few screen shots.

With isoBurn opened, drag your DVD or ISO onto the big square on the left hand side, you will know that it worked when isoBurn shows you the File Name, File Type and File size of your image. See the screenshot below for an example:

If you used the DVD file you should have noticed that the layer break was automatically set for you, please reference the screen shot above.

If you used the ISO file you will need to enter the layer break manually, the proper layer break is 1913760. You should enter this into the layer break text field under Burn Settings.

Select your burner if you have more then one.

Select the Burn speed, IMPORTANT: Do not burn faster then 2x, it does not produce consistent results and may very well leave you with coasters.

Click the burn button. Wait about 45 minutes and your game should be ready.

 

Verify your burned disc with isoBurn:

isoBurn, is not just an ISO / DMG image burner but is also a tool that can provide you with useful information about any of your discs. One thing I’ve noticed with coasters is that for the most part, either the layer break was incorrect or the session was not properly closed. isoBurn can verify this for you, with the Media Info tab.

With isoBurn opened, go ahead and click on the Media Info Tab and put a burned 360 game in your burner. isoBurn will immediately analyze the disc and give you a few important pieces of information. See screen shots below for a game that has been correctly burned and one that will never play in a 360.

Screen Shot A

Screen Shot B

If you’ll notice on screen shot A, the key pieces of information are the layer break, Sessions and Appendable. A correct layer break should be 1913760 and there should be 1 session and Appendable should be No.

Now if you’ll look at screen shot B, you’ll notice that the Appendable is set to yes and that there is no session. This is an example of a disc that will never play on a 360.

This feature adds a valuable troubleshooting ability to your tool set. This will allow you to rule out if there is anything wrong with the burn itself or if there is another issue. How many times have you asked yourself after a burn and finding out that it doesn’t play if its because of a bad burn or because of outdated firmware that doesn’t support Wave ‘X’

Well with this tool at least you will know that the layer break is correct and that the session is closed and if abgx360 verified before you burned then there must be an issue with your 360 or the firmware you are using.

Please don’t forget to rate isoBurn on the Mac App Store, it only takes a minute, do it while your waiting for a burn to finish :)

Tutorial Disclaimer: This tutorial or the software isoBurn does not claim that it is able to produce working backups of Xbox360 games. This tutorial is only based from my own experiences and does not guarantee results. Use this tutorial and isoBurn at your own risk.

Legal Disclaimer: Copying or downloading games that you have not legally purchased or own is illegal in all countries. This violates not only laws in your own country, but international copyright laws as well. The purpose of this turoial is for making backup copies of games that you legally own. Software piracy is illegal carries a huge penalty if convicted, is ethically wrong, and hurts the game companies. Support the game developers by purchasing the games you play. You wouldn’t work for free would you? I am offering a SERVICE to those who cannot make backups of the games they legally own. Chris Fletcher is not affiliated with ANY of the companies, Microsoft, Xbox 360 or any others.

I’m sure many of you have seen the recent E3 event either from a live feed or if you were lucky enough, you were there. I really enjoyed Nintendo’s conference and am really excited about the new Wii that will be coming out. The one thing I think that the conference lacked is the amount of information and visuals about the new console. It seems that the conference was centered mostly around the new controller which in my opinion is great but should not have been the highlight of the new console. Being curious like I am, I started looking around for more information on the console.

Nintendo actually has all of the technical specs as well as an image of the new console on their site. The image below is what I am guessing the new console will look like, according to the image on Nintendo’s own site.

 

A lot of people are wondering if the Wii U is just a new controller that will work with the old console but that is untrue based on the above image as well as the tech specs I’ve listed below. These have been copied and pasted from Nintendo’s website.

  • Launches: 2012
  • Size: Approximately 1.8 inches tall, 6.8 inches wide and 10.5 inches long.
  • New Controller: The new controller incorporates a 6.2-inch, 16:9 touch screen and traditional button controls, including two analog Circle Pads. This combination removes the traditional barriers between games, players and the TV by creating a second window into the video game world. The rechargeable controller includes a Power button, Home button, +Control Pad, A/B/X/Y buttons, L/R buttons and ZL/ZR buttons. It includes a built-in accelerometer and gyroscope, rumble feature, camera, a microphone, stereo speakers, a sensor strip and a stylus.
  • Other Controls: Up to four Wii Remote™ (or Wii Remote Plus) controllers can be connected at once. The new console supports all Wii™ controllers and input devices, including the Nunchuk™ controller, Classic Controller™, Classic Controller Pro™ and Wii Balance Board™.
  • Media: A single self-loading media bay will play 12-centimeter proprietary high-density optical discs for the new console, as well as 12-centimeter Wii optical discs.
  • Video Output: Supports 1080p, 1080i, 720p, 480p and 480i. Compatible cables include HDMI, component, S-video and composite.
  • Audio Output: Uses AV Multi Out connector. Six-channel PCM linear output through HDMI.
  • Storage: The console will have internal flash memory, as well as the option to expand its memory using either an SD memory card or an external USB hard disk drive.
  • CPU: IBM Power®-based multi-core microprocessor.
  • Other: Four USB 2.0 connector slots are included. The new console is backward compatible with Wii games and Wii accessories.

All in all the tech specs appear vague at best. Video up to 1080p is supported but it doesn’t specify what type of graphics adapter the new Wii will be using. All we know about the CPU so far is that it will be a Power-based multi-core processor from IBM. I’m thrilled that they are finally giving us 1080p. Gaming on the Wii will finally be in HD like the rest of the competition.

The only game they have listed with pictures is Super Mario Bros Mii, which I’m not sure will be an actual release based on the E3 conference. It would be a fun game to play and it would be great if they decide to release it. If anyone has any more information about upcoming games, feel free to comment. Here are some images of the game:

All in all, this looks like a winner and I think that Nintendo has once again done a tremendous job designing a great console and being innovative. I will probably be one of those people pre-ordering the new Wii because that’s just how I am when new things come out. I’m a tech geek at heart…

What do you guys think about the new Wii? Pre-Order or not? Ideas? I’d like to hear from you…

We thought it would be a great idea to have an installer for the cocos2d game engine to make it quick and simple for everyone to install the latest stable cocos2d build. The cocos2d installer app is a native Mac OS X app that after installation allow you to, with a click of a button, download the latest stable build of the cocos2d game engine, install it and the Xcode templates to get you up and running and making games simple and quick.

You can download Cocos2d Installer by clicking on the link below:

  cocos2d Installer (368.6 KiB, 988 hits)

As new cocos2d builds become available we will update the Cocos2d Installer app so that you can grab the latest version of cocos2d.

We were going to list this app for free on the Mac App Store but because of some of Apple’s guidelines, specifically file locations, we have had to remove it and host it here. If you find the app useful or can think of something else to add to it to make it more useful then feel free to leave a comment.

I would like to start this post by introducing some new software that will make the lives of developers much easier. When I first starting developing my new game Elementals HD for the iPhone I had no idea that loading individual PNG’s as textures for sprites would result in a final memory consumption of over 130MB on load. That’s really bad considering that the newest iPod Touch only comes with 256MB of RAM which to this day I will never understand. Apple added the hi-res display to the iPod Touch which means that images will use twice the amount of memory that they were using before. With the iPhone 4 they did it right and doubled up on the memory which helps a lot with the HD images taking up twice the amount of memory as the SD ones do. So anyway, back to the topic.

I needed some way to minimize the amount of memory utilization, so I started reading about sprite sheets and image sizes in the power of 2, etc… I found a neat utility called Zwoptex to create sprite sheets of all my images. This ended up helping me quite a bit, not only did it reduce the amount of disk space but it also reduced the amount of memory being used. At this time I was able to get my memory utilization down to about 90MB. To me, this is still quite high and I was not satisfied with the result, so I continued to look for a solution. I started reading about PVR’s and how fast they load and then I read about compressed PVR’s. Next, I needed to figure out how to use these PVR’s to lower my memory utilization and speed up my loading times.

I found an awesome app called TexturePacker which runs natively on Mac OS X. TexturePacker is a very similar tool to Zwoptex in that it creates sprite sheets from images but is very different and far more advanced when it comes to optimization. Long story short, I was able to use TexturePacker to create *.pvr.ccz sprite sheets for HD and SD images and reduced my memory utilization down to 50MB… WOW.. Now that is a lot better then the 130MB I started with. What I’d like to do now is present a tutorial on the usage of TexturePacker and walk you through step-by-step to get HD images loaded into TexturePacker, optimize them, publish them and finally write the code in Xcode to make them work. I’ll also share some best practices for memory management at the end of the tutorial.

Software you will need:

  1. Texture Packer

After you are done downloading the software above, you can follow the below steps to install TexturePacker and start up the Demo Project

Install TexturePacker:

If you haven’t downloaded Texture Packer yet, you can download it here. After the download has completed you can double click on the DMG file so that it mounts a disk image. The disk image contains the Texture Packer installer package. The screen should look like the screen shot below:

Texture Packer - Disk Image Contents

Double-Click the TexturePacker Package File and you will see the install screen, like the one below:

Texture Packer - Install

Texture Packet - Install

From there just follow all of the prompts until Texture Packer has completed the install process. You will find Texture Packer within your applications folder. Go ahead and launch Texture Packer. You will get the following screen:

Texture Packer Essential vs Texture Packer Pro

Texture Packer Essential vs Texture Packer Pro

Unless you’ve purchased a license you should choose Essential. The main difference is that with the Essential (Free Version) anything you export will be exported in red. In the next section I will give a brief overview of Texture Packer and the features we will use the most.

Note: All typos within the installer have been fixed since version 2.1.3

Importing Sprites:

Texture Packer - Import Sprites

Texture Packer - Import Sprites

Referring to the screen shot above I used the Import Sprites button to import a selection of sprites to work with. Once I imported the sprites, Texture Packer automatically adjusts the sprite sheet size to fit the 3 sprites I imported. If you look to the bottom right of the application on the status bar, Texture Packer displays the size of the resulting sprite sheet and the amount of memory it will consume. In this case with the above images, my sprite sheet will be 128×128 and consume 64 kB of memory. 64kB of memory isn’t a whole lot but lets go ahead and do some optimization anyway and see if we can cut down on memory usage.

On the left hand side of the app you will see the Texture Settings menu that is divided into 3 categories; Geometry, Layout and Output. Scroll down to Output and find the Image format setting. The default for this setting is RGBA8888 which results in a sprite sheet with the highest quality and the most memory usage. Change this setting to RGBA4444 and watch what happens to the memory usage. 32kB is what the memory usage is now… WOW we just cut memory usage in half but at the cost of quality. Why? The reduced quality comes from taking a 32-bit image and converting it to a 16-bit image. Make sense?

Ok, lets fix the quality to make it look a little better. Two fields down, you’ll see Dithering. The default Dithering setting is NearestNeighbour which makes for some ugly gradients when going from 32 to 16-bit. Go ahead and change this to FloydSteinberg+Alpha and watch in amazement as your gradients start to look like gradients again. You may notice that this results in your sprites looking a bit noisy but remember, we are working with hi-res images here and every 4 pixels will equal 1 point so the image should look pretty sharp, at least that’s what I’ve experienced.

Let’s take a minute to go over the Output Category that’s in the Texture Settings Menu:

  • Data Format – This setting is for defining in what format the sprite sheet data should be processed in. We need to select cocos2d for this. What this will do is generate a plist file that we will load into frame cache a little later.
  • Data File – This will be the output location and name of the data file (plist file for cocos2d) You don’t need to set this as it will automatically be filled when you set the Texture File
  • Texture Subpath – Not sure what this is for, I’ve never used it
  • Trim sprite names – Leave this unchecked, I’m not sure what this is used for
  • Texture Format – Here you will choose the output format of your sprite sheet. You can choose any format you like, they are all compatible with cocos2d but I recommend Compressed PVR (.pvr.ccz). This will give you the most compression and pretty quick load times.
  • Image format - This is where we will get most of our optimization from. For most of the sprite sheets we create we should choose RGBA4444 as it will give you the best result. RGBA4444 is used for sprites with transparency’s. If you have a sprite that doesn’t use any transparency you should use RGB565. If you have a sprite sheet that absolutely needs to have the highest quality then use RGBA8888 but we aware that this will result in high memory use, especially if your sprite sheet is 2048 x 2048.
  • Texture File – This is where you would set the name of your texture file. Click on the browse button to select your location and then give a name. If you are working with hi-res images be sure to add -hd at the end of the filename, you’ll see why, later.
  • Dithering – I covered this earlier but just to re-cap, if you are using RGBA4444 you should use FloydSteinberg+Alpha and if you are using RGB565 then use FloydSteinberg
  • Premultiply alpha – This is used to limit the amount of artifacts and possible thin black borders around your sprites when sprite anti aliasing is on. Also semi-transparent pixels might get too dark without this setting. If this is enabled be sure to add the following to your code:
    [CCTexture hasPremultipliedAlpha:YES]
  • AutoSD – This is one of my favorite features of TexturePacker. What this little nifty checkbox does is automatically create a low-res sprite sheet and plist file for you but you have to make sure that you named your Texture file with a -hd at the end.

A Note from the author of TexturePacker: Whenever possible, you should use Add Folder to import your sprites because this uses smart folder. Every time you add sprites to the folder and update your sprite sheet it re-scans the contents of the folder and adds all sprites. This makes sprite handling much easier than adding single sprites.

Ok, so now we have our sprites imported and have everything optimized. Next we will talk about Publishing.

Publishing Sprite Sheets:

Before you click on the Publish button be sure that you’ve got all of your settings configured the way you want them. Here’s a quick step-by-step re-cap of the steps above:

  1. Import sprites either by using the Add Sprites or the Add Folder button.
  2. Set Data Format to cocos2d
  3. Set Texture format to Compressed PVR (.pvr.ccz)
  4. Set Image format to RGBA4444
  5. Set Texture file to something-hd
  6. Set Dithering to FloydSteinberg+Alpha
  7. Check AutoSD

With all of the above completed go ahead and click on the Publish button. Texture Packer will now export your hi-res and low-res sprite sheets and associated plist data files.

You should have something similar to the following screen shot:

There isn’t too much to say about publishing, the next section will cover how to get your sprite sheets to work with cocos2d.

Writing The Code:

After publishing your sprite sheets with Texture Packer, the next and last step would be to add this into your project and get them to show up in your scene. I’ll be walking you through adding your sprite sheets to your project and showing you code examples of how to make the best use of your new sprite sheets.

Open up Xcode, create a new cocos2d Project from one of the cocos2d templates and copy the 2 sprite sheets and 2 plist files that were exported from TexturePacker into your Resources folder within your Xcode project, make sure that copy files is checked.

Copy Items

Copy Items

Once the sprite sheets and plist files have been added go ahead and click on your HelloWorldScene.m and find your init method. Once you’ve located your init method replace what’s inside the if statement with the following lines of code:

[CCTexture2D setDefaultAlphaPixelFormat:kCCTexture2DPixelFormat_RGBA4444];
CCSpriteBatchNode *spritesDemoNode;
spritesDemoNode = [CCSpriteBatchNode batchNodeWithFile:@"demosprite.pvr.ccz"];
spritesDemoNode.tag = 805;
[self addChild:spritesDemoNode];
[[CCSpriteFrameCache sharedSpriteFrameCache] addSpriteFramesWithFile:@"demosprite.plist"];

The code above does the following:

  1. Sets the current Pixel format to RGBA4444 to match that of our sprite sheet that we set in TexturePacker
  2. Creates a sprite batch node using the Compressed PVR
  3. Sets a tag ( has nothing to do with texture packer but I use tags for other reasons )
  4. Adds the node as a child to your current Layer
  5. Adds the sprite frames to cache from the plist file that was exported by Texture Packer

Next we need to create a CCSprite from the frames that are in cache, we do this with the following code:

CCSprite *spriteDemo = [CCSprite spriteWithSpriteFrameName:@"fireball.png"];
spriteDemo.position = ccp(size.width/2, size.height/2);
spriteDemo.tag = 1;
[self addChild:spriteDemo];

The above code does the following:

  1. Creates a sprite from the frames in cache. In this case I had an image named fireball.png that was one of the images that was imported into Texture Packer. When Texture Packer creates the plist file it uses the names of your sprites for the frame names, which makes it easy to use.
  2. Next I am setting the position to the center of the screen. size is a variable that I’ve setup that has the height and width of the screen as properties.
  3. Again I am setting a tag, not something you have to do
  4. Last we are adding the new sprite to our layer.

If all went well and you’ve followed all of the above directions then you should be able to build your project and see your sprite on the scene. Granted, this is more work then copying individual PNG’s into your project and just creating sprites from the PNG’s but that is a big waste of memory and will eventually crash your app. Remember, with Texture Packer I was able to reduce my memory to more then half of the original memory utilization even using Zwoptex did not make a huge improvement with memory usage. I would definitely recommend Texture Packer to anyone that is interested in optimizing memory.

If anyone has any questions or comments please feel free to leave them. If anyone has any more optimization tips, please share, I would love to hear them and I’m sure everyone else would appreciate it as well.

It’s relatively simple to Jailbreak your PS3 using your iPhone but to figure out the entire process from beginning to end was actually quite a challenge for me. I couldn’t find a single tutorial that explained in detail steps what you have to do to prepare your iPhone to Jailbreak the PS3 and then how to use the iPhone to Jailbreak the PS3 and then how to load packages like Open Manager, FTP Server, SNES9x, etc.. and finally how to go about putting game backups on the PS3′s internal Hard Drive.

This Tutorial will provide you with a complete overview of what is required to Jailbreak your PS3 using your iPhone 2G and will be broken up into the following sections:

  • Preparing your iPhone 2G for Jailbreaking
  • Jailbreaking your PS3 with your iPhone 2G
  • Installing Packages ( FTP Server, Open Manager, Backup Manager, SNES9x )
  • Copying a backup game to your PS3′s internal hard drive

You will need to download the following files below:

  • Download:

      iPhoDroid 2G Mac PSFreedom (59.6 MiB, 1,365 hits)

    (iPhoDroid for Mac)
  • Download:

      PS3 FTP Server (517.9 KiB, 1,187 hits)

    (FTP Server for PS3)
  • Download:

      Open Manager 1.17.1 (1.3 MiB, 1,058 hits)

    (Manage Game Backups)
  • Download:

      Backup Manager 1.1 (527.5 KiB, 1,011 hits)

    (Manage Game Backups)
  • Download:

      Backup Manager 2 (525.8 KiB, 1,013 hits)

    (A modified version of Backup Manager that allows you to load a backup without a disc in the drive. I haven’t tested it)
  • Download:

      SNES9X PS3 (14.1 MiB, 1,032 hits)

    (An SNES Emulator)
  • Download:

      Cyberduck 3.7 (19.9 MiB, 1,339 hits)

    (A Mac FTP Client, I’ve tried FileZilla but it had issues)

IMPORTANT NOTE: As of the writing of this tutorial, there is no way of jail breaking any PS3 with firmware above 3.41. Also, this tutorial is written with the Mac user in mind, if you are using Windows you should be able to apply the same processes mentioned here.

Preparing Your iPhone 2G for Jailbreaking:

Note: This tutorial assumes that your iPhone 2G is already Jailbroken. If your iPhone 2G is not jailbroken then lookup redsn0w and perform the Jailbreak.

  1. Connect Your iPhone 2G to your Mac and make sure iTunes is not running.
  2. Launch iPhoDroid
  3. Click Shoot!
  4. iPhoDroid will now install Openiboot and the Android Operating System as well as PSFreedom
  5. On the final screen iPhoDroid will tell you that your phone will enter recovery mode
  6. You will notice that your phone will have openiboot loaded up.
  7. Scroll down to Install using the Volume Buttons.
  8. Press the Home Button
  9. Disconnect the iPhone from your Mac
  10. Wait for init to scroll on the screen

Your iPhone is now ready to jailbreak your PS3. It is currently running in a loop basically waiting to detect the playstation. It is important that you do not let your phone sit in this loop for an extended length of time. Allowing your iPhone to stay in this loop for hours will eventually brick your phone. Please be warned.

Note: To boot your phone back into iOS push the Lock and Home buttons at the same time and hold them until the screen turns off. You are now presented with the openiboot menu. iOS should be selected by default. Push the home button. The first time after loading openiboot and trying to get back into iOS might not work as the phone may still be in recovery mode. If this is the case plug the phone back into your Mac and launch iPhoDroid once again but instead of clicking on Shoot! click on Exit Recovery Mode. This will allow your iPhone to properly boot into iOS.

At any time you can have your phone back in the init loop by pressing and holding the Lock and Home button and then selecting Android and pressing Home. So go ahead and get your phone into the init loop mode and follow the next part to jailbreak your PS3.

Jailbreaking your PS3 with your iPhone 2G:

Assuming that you’ve followed all of the steps above correctly, your iPhone 2G should be running in the INIT loop.

  • If you have a PS3 Slim, unplug the power from the back, then plug in your iPhone to the USB port then plug the Power Cable back in.
  • If you have a PS3 Phat, flip the power switch to Off, then plug in your iPhone to the USB port then flip the Power Switch to On.

With the iPhone plugged in, press the power button on your PS3 and then immediately press the eject button. You should now start seeing some lines of text appear in-between the INIT’s. When the iPhone comes to a stopping point there should be about 4 lines of text. Unplug the USB and plug it back in immediately. Then wait for a bunch more text to scroll on the iPhone. When this text stop scrolling you, you have successfully jailbroken your PS3.

Using your controller navigate to the Games section of your XMB and you should notice 2 extra folders that weren’t there before. The folder that we are interested in is the Install Packages folder. The Install Packages folder will be used in the next section to install Open Manager, Backup Manager, FTP Server and SNES9x.

At this point I think you can disconnect your iPhone but lets keep it plugged in until we have all of the packages installed. Leave your PS3 on and your iPhone connected.

Installing Packages ( FTP Server, Open Manager, Backup Manager, SNES9x ):

Assuming that you’ve followed all of the steps above correctly and have the FTP Server, Open Manager, Backup Manager and SNES9X packages downloaded, you will need a flash drive.

  1. Plug your Flash Drive into an available USB port on your Mac
  2. Copy all of the .pkg files onto the root of the flash drive.
  3. Unplug the Flash Drive from your Mac
  4. Plug the Flash Drive into an available USB port into your PS3
  5. Navigate to the Install Packages Folder
  6. You should see all 4 of the Packages that you added to your flash drive
  7. One by one click on each and install them.

When all of the packages are installed you will be able to run each of them by clicking on their icon within the Game section of your XMB.

Here is a brief overview of the packages we have just installed:

  • FTP Server – This package adds an FTP server to your PS3 and will allow you to remotely connect to your PS3 so that you can move and copy files and folders. We will use this FTP server in the next section when I go over how to copy game backups from your Mac to the internal HDD of your PS3
  • Open Manager / Backup Manager – Open Manager and Backup Manager are essentially the same thing. They allow you to manage games loaded onto your PS3 either from your Mac or from Blu-Ray Disc. You can copy, delete and launch your games using either of these packages. We will be using these to launch the backup game that we will be copying from the Mac to the PS3.
  • SNES9X – I’m sure everyone has heard this name before. SNES9X is a Super Nintendo emulator and has been ported to just about every console on the market. It allows you to play Super Nintendo Roms. This is always good to have for those nostalgic days when you just have that need to play some retro games. I’ll briefly cover this package and how to add ROMS to your PS3 so you can play them with SNES9X.

At this point of the tutorial you should have a jailbroken PS3 with all of the necessary packages installed. In the next section I will go over how to copy a backup from your Mac to the PS3′s internal hard drive and how to launch the game using Backup Manager.

Copying a backup game to your PS3′s internal hard drive:

Now, this is the part of the tutorial that I’m sure everyone has been waiting for. If you’ve made it this far, congratulations because you are only a few steps from playing a backup of your PS3 game. Now I’m going to go ahead and state a warning.

Warning: I do not condone software piracy. I am simply providing instructions that will aid consumers in making backup’s of their originally purchased games so that they may keep their purchased games in a safe place and play only their game backups. I do not and will not host game backups for download. I will only provide a way of searching for available backup downloads, this is only in case there is something wrong with your original game ( scratched, broken in half, melted, etc… ) which means that you have already purchased the game and the store will not offer you an exchange or a refund.

Ok, with the warning aside, lets proceed.

  1. Start the FTP Server from the Games section within your XMB
  2. You will notice an IP address at the top. This address will be used for CyberDuck
  3. Navigate to Start FTP Service ( This should already be selected ) Click X on your controller

From your Mac

  1. Launch the Cyber Duck Application
  2. In the Quick Connect Text Field, enter the IP address that is displayed on the FTP Server, from Step 2 above, and press enter.
  3. Once the connection Completes, you should see a folder “dev_hdd0″, this is the internal HDD of your PS3.
  4. Double Click on dev_hdd0
  5. Find the “game” folder and Double Click on it.
  6. Find the “LAUN12345″ folder and Double Click on it.
  7. Find the “GAMEZ” folder and Double Click on it. If there is no GAMEZ folder then we will have to create one. This is very simple. Right Click anywhere in the white space and then click on New Folder and give the folder a name of GAMEZ in all caps.
  8. Double Click on the GAMEZ folder. It should be empty. This is the location where we will copy the game backup to.
  9. Drag the extracted game folder into the Cyber Duck Window and wait for it to finish copying. Depending on your network connection (Gigabit Ethernet, 10/100, wiFi), this can take a while. So go do something but leave your PS3 alone.

When the copy process has finished go back to your PS3, Exit FTP Server by navigating to Exit to XMB and pushing the X Button on your controller. When you are back at the XMB, scroll to Backup Manager and push X to Launch it. If all went well then your game should appear there. You will need to insert an original Game disc for this to work.

When you launch your game from within Backup Manager it will require you to have an original game in the drive, doesn’t matter which one just be sure its an original. Once the game is launched it will take you back to the XMB, now when you scroll to the game disc in the drive, the actual name of the original will be replaced with the name of the backup you are loading. So go ahead and push the X Button. on the game disc and your game should load. Remember to say no or cancel to ANY AND ALL UPDATES. Try to not be signed into PSN, I am not sure of the repercussions of playing backups online.

NOTE: The game folder that you are copying to the GAMEZ folder via FTP should have a similar file structure to the below:

BCUSXXXX ->

  • PS3_DISC.SFB
    PS3_GAME
    PS3_UPDATE

If you’ve downloaded the game from NewZBin or any other USENET site then this will most likely be the format after extraction.

Well that’s it for this section. I will now briefly cover SNES9X and will list some links to an example game NZB and a link to a great SNES Roms site.

SNES9X How To for the PS3:

If you’ve followed all of the above steps, which you should have, then SNES9X should already be installed. If you didn’t install it then please scroll up to installing packages and install SNES9X. If you’ve already got it installed then follow the steps below:

On The PS3

  1. Launch FTP Server
  2. Start FTP Server

On The Mac

  1. Launch CyberDuck FTP Client
  2. Type in the IP Address into the Quick Connect Text Field and press enter.
  3. Navigate to dev_hdd0 and double click.
  4. In here we will create a folder called ROMS. Right click anywhere within the window and click on New Folder.
  5. Name the folder roms
  6. Double Click on the roms folder. This will be the folder to copy all of your downloaded roms to. This procedure is the same as copying a PS3 game you just drag the SMC file to the roms folder. See below for a site that has many SNES roms available for download.

On The PS3

  1. Exit the FTP Server by navigating to Exit to XMB and then pushing X on your controller.
  2. Launch SNES9X
  3. Navigate to the dev_hdd0 folder and push X
  4. Navigate to the roms folder and push X
  5. Select the ROM you wish to load and push X

You should now have SNES9X running with your selected ROM. If it isn’t working feel free to leave me a comment. Now as promised the next and last section has some links for you.

Links:

Last but not least an NZB file for Mortal Kombat vs. DC Universe for PS3

Hopefully you’ve found this tutorial useful, as you can imagine it takes a lot of time to put something useful together and make sure that its 100% correct. If I missed anything or have made a mistake along the way or if you’ve got questions feel free to comment as always.

NOTE: Just wanted to mention that after you have booted your PS3 with the Jail Break hack, you can disconnect your iPhone and turn it off. The iPhone is only needed in the beginning when you turn your PS3 on. Any time you reboot your PS3 you must reconnect the iPhone and perform the Jail Break hack in order to use any of the installed packages or play backed up games. Remember that leaving your iPhone running for an extended period of time in the INIT loop can eventually brick your iPhone.

I take no responsibility for any hardware damage or PSN banning that might result in performing any of the above steps.

So apparently there are some tutorials floating around that show you how to convert wave 4 games to wave 3 games. What most of them don’t tell you is that by doing this, you are setting yourself up to get banned from Xbox Live.

Patience truly is a virtue here. I know everyone is eager to play Tekken 6 and a few of the other wave 4 releases. I honestly don’t see problem with it as long as you play those games offline. Is it really worth the risk of getting banned ?

For those of you that absolutely must play wave 4 games, I have listed the tutorial for you below on how to convert wave 4 games to wave 3 games, but again please don’t play on Live with these games because there is a very good chance that you will get banned. What this hack does is it uses a wave 3 video file and since the sizes between the wave 4 and wave 3 video files differ, you will receive CRC errors in abgx360.

Here’s the tutorial:

You’ll need the following software:

NOTE: You can use either Xbox Backup Creator or abgx360 to patch the wave 4 game to a wave 3 game. I’ve put together 2 tutorials. One using Xbox Backup Creator to patch and then abgx360 for verification. The other one is at the bottom and uses abgx360 for both patching and verification.

Using Xbox Backup Creator

  1. Under Action, change it from extract to inject
  2. Click on PFI Sector and choose the ISO of the game and then choose the PFI file provided with the wave 4 to wave 3 packs.
  3. Click on Video Section and choose your game ISO and then choose the provided video file
  4. That’s it for Xbox Backup Creator

Using abgx360

  1. Open your ISO
  2. Put check marks in the following on the Options Tab
    Check/Create .dvd file
    Check Stealth
    Verify is Stealth Passes
    Check/Fix Video padding
    Use Colors
    Check for updates
    Check Game Partition CRC when needed
  3. On the Manually Patch or Extract Files Tab make sure nothing is selected.
  4. On the AutoFix Tab Check Mark the following
    Adjust angle 359 for iXtreme < v1.4
    Fix C/R Table if data is invalid
    Adjust angles that deviate more than 3 degrees from their CCRT targets
    AutoFix Threshold – Level 3
  5. On the Misc Tab
    SplitVid: Add it if it doesn’t exist or isn’t valid
    Images: Extract images when using HTML output
  6. Click on Launch
  7. abgx360 will most definitely present you with CRC errors because the game is no longer stock.
  8. When abgx360 has completed you can go ahead and burn your game using the regular burning method

Using Only abgx360 to perform the hack and verify

  1. Open your ISO
  2. Put check marks in the following on the Options Tab
    Check/Create .dvd file
    Check Stealth
    Verify is Stealth Passes
    Check/Fix Video padding
    Use Colors
    Check for updates
    Check Game Partition CRC when needed
  3. On the Manually Patch or Extract Files Tab do the following
    Check Patch even if stealth passes
    Check Patch even if these files are invalid
    Check Patch Video
    Check Patch PFI
  4. Still on the Manually Patch or Extract Files Tab, next to Patch Video you should see an empty text box and a gray button with 3 dots, click on that button and choose the Video File from the pack. Do the same thing for Patch PFI and choose the PFI file from the pack
  5. On the AutoFix Tab Check Mark the following
    Adjust angle 359 for iXtreme < v1.4
    Fix C/R Table if data is invalid
    Adjust angles that deviate more than 3 degrees from their CCRT targets
    AutoFix Threshold – Level 3
  6. On the Misc Tab
    SplitVid: Add it if it doesn’t exist or isn’t valid
    Images: Extract images when using HTML output
  7. Click on Launch and wait for abgx360 to finish patching the ISO when abgx360 reads Press any key to exit … then it has completed patching.
  8. You can now close abgx360 and re-open it to verify that the ISO is indeed a wave 3 now.

I myself haven’t tried this particular tutorial, I just placed it here from gathering bits and pieces online. I would urge you to do this as a last resort and remember not to play these modified / downgraded to wave 3 games on Live.

Requirements:
- Mac OS X 10.4 or later
- Intel Processor
- Dual Layer DVD Burner

Installation:

So today I have decided to release the an Alpha Version of ISOx360. You can download it from my projects page.

ISOx360 makes burning XBOX 360 games on your Mac just about as simple as it can get. Simply download ISOx360 and extract the .dmg then open the .dmg and drag ISOx360 to your Applications folder to install. Once installed you can launch ISOx360 and you should be presented with a screen similar to the illustration to the left.

Read more

UPDATE 6/23/2011 – isoBurn has been submitted to the Mac App Store, to read more about it and see some screen shots please visit http://empoc.com/isoburn

OSx360 probably the only application that is available for Mac that can properly burn XBOX 360 games. It seems as though the developer has abandoned the project. I have checked the developers website and a few forums where he interacted with a few people that had issues with OSx360.

I’ve tried to contact him to see if he would release the source code to the application so that I could continue development and work out all of the bugs, including the ability to verify stealth on the newer released games. However, I have not been able to make any contact so I will be developing a new burning application for Mac OS X that will burn XBOX 360 games.

I’d like to ask my readers to please leave me comments with feature requests, etc…

In the meantime, OSx360 will still properly burn XBOX 360 games even if stealth is not verified. What I would suggest is this, use abgx360 to verify the ISO to ensure it has been properly patched. You can follow my tutorial on how to do that by clicking the link here. http://chris-fletcher.com/2009/06/07/how-to-stealth-patch-xbox-360-games-on-a-mac/

After you’ve finished with abgx360 and everything appears to look good, you can proceed to open OSx360. Follow my tutorial by clicking the link below on how to burn XBOX 360 games using OSx360.

http://chris-fletcher.com/2009/06/05/how-to-burn-xbox-360-games-on-a-mac/

You’ll want to follow the tutorial step by step, here’s the exception, If everything checked out fine in abgx360 but you are seeing stealth not verified in OSx360 then you must make a minor change to the configuration.

  • Configuration
  • Burn Options Pane
  • Uncheck Require Stealth Verification

 

OSx360 - Configuration - Uncheck Stealth

OSx360 - Configuration - Uncheck Stealth

After you’ve made the configuration changes you can proceed to burn your game. I have been able to this without any problems, but don’t blame me if this ends up producing coasters for you.

Just wanted to mention again that I will be developing a new burning application for Mac OS X to burn XBOX 360 games and urge anyone reading this blog to submit any type feature requests.

The goal of the application will be to mimic OSx360 in that you can open an ISO it will verify stealth, dmi, pfi, etc… and allow you to burn the game. I’d like to try and keep it as simple as possible but will consider all feature requests.

That’s it and thanks for reading.

This tutorial should work no matter which operating system you are on, however I am writing it with more emphasis on how to do it on a Mac, since there isn’t any software that will help with backing up original Wii Games on a Mac.

The best thing about this Guide is that if your Wii has a mod chip installed and you have an SD card and a home network, then you wont have to spend any money on any additional hardware. So on to the guide.

Prerequisites:

  • Wii with a mod chip
  • Wii with Version 3.2 ( If your version is higher then 3.2 then you must downgrade )
  • Wii connected to your network
  • A Mac connected to your network
  • An SD Card ( Must be less then 2GB )

Required Software:

  • WiiOSx Tool - A custom application I developed to aid the process and make life easy. WiiOSx Tool will format your SD Card to the proper specifications, prepare your SD card to install the Homebrew Channel, prepare your SD card to install custom IOS and the Wii HTTP server. Finally, WiiOSx will make it easy to download your ISO. Go ahead and download WiiOSx Tool, install and launch it and then proceed to Step 1.NOTE: Only works on OS X 10.5 ( Leopard ) 

 

Step 1: Preparing Your SD Card

The first thing we need to do is prepare the SD card. We will need to format the SD card with FAT16 and then add the necessary applications to it. To do this follow the steps below:

Formatting Your SD Card:

Format SD Card

Format SD Card

  1. Launch WiiOSx Tool
  2. Click the Format SD Card Tab
  3. Select your SD Card from the Drop Down
  4. Enter A New Name for your SD Card ( It can be the same name as the current card name )
  5. Click Format SD Card

Preparing the SD Card for Homebrew Channel Installation:

If you already have the Homebrew Channel installed, you can skip this part and go on to Step 2

BannerBomb Hack

BannerBomb Hack

  1. In WiiOSx Tool click on the BannerBomb Hack Tab
  2. Select your SD Card from the Drop Down
  3. Choose a version from the Drop Down ( Start with the first and work your way down until one of them works )
  4. Make sure Erase Card is checked.
  5. Click Make BannerBomb SD Card
  6. Take the SD Card and put it into your Wii’s SD Card Slot
  7. Press (Wii), Data Management, Channels, SD. It should either pop up Load boot.dol/elf? or freeze. If it freezes then repeat steps 1 through 5 and choose a different version.
  8. Click Yes and Install Homebrew Channel

 

Step 2: Checking Your Wii’s Current Version

The first thing we need to do is check which menu version your Wii currently uses. To do this follow the steps below:

  1. Turn on your Wii
  2. On the bottom left hand corner of the Wii menu you should see the Wii Logo. Click on it
  3. Then Click on Settings
  4. On the top left corner of the screen you should see your version
  5. If your version is higher then 3.2 then continue to Step 3.
  6. If your version is 3.2 then continue to Step 5.

 

Step 3: Fixing Your Wii

This is a step you need to take if your version is above 3.2 before we begin, we need to prepare the SD Card with the necessary files. If you haven’t formatted your SD Card yet, then follow the beginning of the tutorial. If your SD card has been formatted already then all you need to do is as follows:

Additional Apps

Additional Apps

  • Launch WiiOSx Tool
  • Click on the Additional Apps Tab
  • Select your SD Card from the Drop Down
  • Make sure Erase Card is selected
  • Then click on Add Applications
  • Wait for it to finish and then insert your SD Card into the Wii’s SD Slot

Follow the steps below to Fix your Wii (This fix will enable WAD’s to run properly on your Wii)

  1. Update your Wii to the latest version. 
  2. Using “The Homebrew Channel”, open “WAD Manager”.
  3. Press “A” on the Wii Remote once. The Wii should detect a SD Card. Press “A” again to see a list of WADs on the SD Card. Use the “D-Pad” to select “IOS16-64-v257-prod.wad”. Press “+” to install the WAD. Once installed, press the “Home” button, to restart you Wii.
  4. Using “The Homebrew Channel”, open “Custom Manager”. Using the same method as in “Step 3″, install the “cIOS_Fix.wad”. Once installed, press the “Home” button, to restart you Wii.
  5. Using the ‘Homebrew Channel’, open ‘IOS Downgrader’. Just follow the instructions on the screen and wait until it finishes installing the necessary IOSs.
  6. Using “The Homebrew Channel”, open “Install Shop IOS51″. Use the “D-Pad” to select “Yes”, and install “IOS51″, by pressing “A”. Use the “D-Pad” to select “Yes”, and install the IOS Patch, by pressing “A”. Use the “D-Pad” to select “No”, and DO NOT install the “Wii Shop Channel”.
  7. Using the ‘Homebrew Channel’, open ‘WAD Manager ’. Install ‘WAD MANAGER 1.3’. 
  8. The Wii is now able to install WADs and Homebrew Apps should work properly now. 

 

Step 4: Downgrading Your Wii To 3.2

  1. Using “The Homebrew Channel”, open “Firmware Downgrader”.
  2. Press the ‘A’ button on the Wii Remote. You should be presented with a list of different firmware versions. Select and press ‘A’ on one of the following:
    - 3.2J = Japan Firmware
    - 3.2U = American Firmware
    - 3.2E = Europe Firmware
  3. Press the “Home” button on the Wii Remote to restart the Wii. 
  4. Using “The Homebrew Channel”, open “Install Shop IOS51″.
  5. Use the “D-Pad” to select “Yes”, and install “IOS51″, by pressing “A”. Use the “D-Pad” to select “Yes”, and install the IOS Patch, by pressing “A”. Use the “D-Pad” to select “Yes”, and install the “Wii Shop Channel”
  6. Using “The Homebrew Channel”, open “Mii Channel Updater”.
  7. Use the “D-Pad” to select “Yes”, and install “Updated Mii Channel”, by pressing “A”.
  8. You are now on the Wii Firmware 3.2X and can use the Mii Channel and Shop Channel. 

 

Step 5: Installing cIOS249

  1. Start the Homebrew Channel
  2.  Launch the Custom IOS249 Installer. 
  3. It should only take a few seconds before the IOS is installed.

 

Step 6: Starting The HTTPD Server

  1. Start the Homebrew Channel
  2. Launch the WiiHTTP Dumper
  3. Once it loads, it will connect to your network, and display the IP address of the Wii.
  4. Insert the Wii Game that you want to backup!

 

Step 7: Downloading Your ISO

  1. Launch WiiOSx Tool
  2. Click on the ISO Tab
  3. Type the Wii IP Address that is displayed from the HTTPD server into the Wii IP Address box
  4. Click on Save ISO To, to select a location to save your ISO to.
  5. Select the type of ISO you are creating, the choices are do-wii-sl.iso (Wii Single Layer Disc), do-wii-dl.iso (Wii Dual Layer Disc), do-gamecube.gcm (Game Cube Disc).
  6. Click Save ISO, the process can take anywhere from 1.5 to 5 hrs. depending on your connection speed.
WiiOSx Tool - ISO

WiiOSx Tool - ISO

 

[poll id="8"]

I will not charge for WiiOSx Tool but I’m hoping that I’ll at least receive some donations for my hard work. You can use the form below to donate any amount you wish.

[donateplus] [donorwall title='Donor Recognition Wall']