it's in the OP last line- download link
---------- Post added at 22:20 ---------- Previous post was at 22:20 ----------
use an older version ? maybe
Xbox Backup Creator v2.9 Build:0350 by Redline99
- Thread starter Ubergeek
- Start date
---------- Post added at 22:20 ---------- Previous post was at 22:20 ----------
I wouldn't say "slow" but thought I was asking a community for help with a question that could have been summed up with a yes or no. Instead I was berated, I'm not new to the scene but been out for a while. I do remember a time when the scene was starting out and people seemed much more helpful and willing to lend constructive advice.
These instructions don't seem exactly correct so that may be confusing people. The only way to I can see to load an iso is the click AP25 Sector first. So the order should perhaps be...
Image Tools > select inject > click AP25 Sector > load iso > load median.bin and patch > burn with iHas Driver + BurnerMax Firmware
Or am I just not looking properly? :redface:
STRATEGIZER
Senior Member
Thats the order I did it in to, Patched the iso all the same.
Typo maybe ? Not a big problem, Im sure people will figure it out.
Right. And just to complete the circle of understanding, for median.bin I assume we can use either of the two .bin files
XGD2.COD-BO.COD-MW2.Halo-Reach.top.data.v1.bin
or
XGD3.Profile.ID.F87A804E.top.data.v1.bin
These are the medians of all the 35+ measurements that were taken, right?
However, I loaded my halo reach.iso, then it asks for a file to 'merge' (note 'patching' not actually mentioned) and I selected the first one of the two. It then reports
"AP25 Sector file injected at LBA sector 129808"
I saw that the iso file had its modifed date updated, so I burned it but it still boots on LT+2.0.
Not sure what's going on.
XGD2.COD-BO.COD-MW2.Halo-Reach.top.data.v1.bin
or
XGD3.Profile.ID.F87A804E.top.data.v1.bin
These are the medians of all the 35+ measurements that were taken, right?
However, I loaded my halo reach.iso, then it asks for a file to 'merge' (note 'patching' not actually mentioned) and I selected the first one of the two. It then reports
"AP25 Sector file injected at LBA sector 129808"
I saw that the iso file had its modifed date updated, so I burned it but it still boots on LT+2.0.
Not sure what's going on.
Fisticuffs
VIP Member
It says not for halo reach tingedace
edit: taken from the topology data nfo
2) XGD3.Profile.ID.F87A804E.top.data.v1.bin
Suitable for all XGD3 games with this disc profile ID:
0C3DF524599094E6CB87ECC8-F87A804E
This covers all current XGD3 releases (at the time of writing) except for
the Halo: Reach XGD3 beta.
edit: taken from the topology data nfo
2) XGD3.Profile.ID.F87A804E.top.data.v1.bin
Suitable for all XGD3 games with this disc profile ID:
0C3DF524599094E6CB87ECC8-F87A804E
This covers all current XGD3 releases (at the time of writing) except for
the Halo: Reach XGD3 beta.
Last edited:
Right, but I'm using Halo Reach XGD2.
SUITABLE FOR THE FOLLOWING GAMES ONLY:
a) Call of Duty: Black Ops
b) Call of Duty: Modern Warfare 2
c) Halo: Reach (XGD2 ONLY, don't use this on backups of the XGD3 beta)
SUITABLE FOR THE FOLLOWING GAMES ONLY:
a) Call of Duty: Black Ops
b) Call of Duty: Modern Warfare 2
c) Halo: Reach (XGD2 ONLY, don't use this on backups of the XGD3 beta)
STRATEGIZER
Senior Member
The answer is in your post...
Your using a XGD2 version of halo reach, So you use topology patch for CoD BO, MW2, Halo Reach XGD2.
The XGD3 version of Halo reach (Beta) cannot be patched/played.
Just to recap, I have the XGD2 halo reach iso.
I patched it with XGD2.COD-BO.COD-MW2.Halo-Reach.top.data.v1.bin.
Burned it, and it still boots on my LT+2.0 drive.
I patched it with XGD2.COD-BO.COD-MW2.Halo-Reach.top.data.v1.bin.
Burned it, and it still boots on my LT+2.0 drive.
Instructions on how to patch here
---------- Post added at 17:06 ---------- Previous post was at 17:05 ----------
:rolleyes2:
---------- Post added at 17:06 ---------- Previous post was at 17:05 ----------
On Xbox Live with the latest metro dash ?
:rolleyes2:
Thanks for posting the instructions, simple though they are, it is good to see it is exactly what I did.
I didn't boot the disc on live, no. I had to revert my only phat console from RGH to retail metro dash to try this out.
If it's patched properly with topology data then LT+2.0 can't boot it can it? (regardless of live)
I'm starting to wonder if I burned the correct image now :crazy:
I guess I might sacrifice another disc to find out for sure.
For starters you should be on LT+ v3.0
So dont waste your own time doing anything else until youve done that first
So dont waste your own time doing anything else until youve done that first
I should. I'll try that next thanks.
I just wanted to see that it DIDN'T work with LT+2.0 first. And was thrown off when it did work....
OK so my burn of halo reach XGD2 patched with XGD2.COD-BO.COD-MW2.Halo-Reach.top.data.v1.bin boots perfectly on both ofa) Jasper with xeBuid "retail" 14699 image NAND and LT+2.0
AND
b) Several consoles modified only with LT+3.0
I'd be interested to know how this can be so. I'm wondering if the xeBuild retail image has no interest in checking AP25. Strange as it does include a dae.bin in there.