Subscribe to AfterDawn's weekly newsletter.
What's wrong with Halo Reach??
#1
07 Jan 2012 @ 19:31
TonyJer
Send private message to this user
Member
Hi
Know it's XGD2 with AP25 and need to reburn following update to 13644 dash and LT 3.0 etc. Ripped the game and re ran ISO through AGBX 1.06 and confirmed that new topology added etc etc.
Thing is when I burn and try it I get the unsupported disk error. Procedure worked fine with ACB which has same protection. Use Burner Max with 124B and using Verbs 2.4. Used 4 speed for first time so maybe this is the issue (followed advice from this forum).
Is there something slightly different about Reach?
Bit frustrated.
Know it's XGD2 with AP25 and need to reburn following update to 13644 dash and LT 3.0 etc. Ripped the game and re ran ISO through AGBX 1.06 and confirmed that new topology added etc etc.
Thing is when I burn and try it I get the unsupported disk error. Procedure worked fine with ACB which has same protection. Use Burner Max with 124B and using Verbs 2.4. Used 4 speed for first time so maybe this is the issue (followed advice from this forum).
Is there something slightly different about Reach?
Bit frustrated.
AfterDawn
Advertisement
#2
07 Jan 2012 @ 19:31
Originally posted by TonyJer:Forgot to say that using LT 2.0 not 3.0!!
Hi
Know it's XGD2 with AP25 and need to reburn following update to 13644 dash and LT 3.0 etc. Ripped the game and re ran ISO through AGBX 1.06 and confirmed that new topology added etc etc.
Thing is when I burn and try it I get the unsupported disk error. Procedure worked fine with ACB which has same protection. Use Burner Max with 124B and using Verbs 2.4. Used 4 speed for first time so maybe this is the issue (followed advice from this forum).
Is there something slightly different about Reach?
Bit frustrated.
#5
08 Jan 2012 @ 0:14
Originally posted by TonyJer:
Ripped the game and re ran ISO through AGBX 1.06 and confirmed that new topology added etc etc.
From my abgx360 guide: -
Quote:
The current version of abgx360 patches all AP2.5 games for use with LT+ 3.0, so please bear that in mind before using it as games patched for LT+ 3.0 are not compatible with earlier versions of LT+!
http://forums.afterdawn.com/t.cfm/f-152...r_guide-921089/
Click HERE for up to date 360 tutorials that may help you!
#6
08 Jan 2012 @ 5:09
Originally posted by funksoulb:Oh shit! Many thanks, diddn't realise that.
Originally posted by TonyJer:
Ripped the game and re ran ISO through AGBX 1.06 and confirmed that new topology added etc etc.
From my abgx360 guide: -
Quote:
The current version of abgx360 patches all AP2.5 games for use with LT+ 3.0, so please bear that in mind before using it as games patched for LT+ 3.0 are not compatible with earlier versions of LT+!
http://forums.afterdawn.com/t.cfm/f-152...r_guide-921089/
The odd thing is that the old version of AGBX (1.05) kept saying there is no AP25 in online verified database....Unable to fix reply data... Is there anyreason why AGBX 1.05 worked for ACB and not reach when they are both XGD2 with the same AP25 protection?
Thanks again
#7
08 Jan 2012 @ 6:21
I don't know for sure mate. Maybe your particular rip of the game isn't in the database. They don't actually use the same protection, as in 1.0.5 the AP2.5 data that was patched in was game specific. With 1.0.6 and LT+ 3.0, all XGD3 games apart from the XGD3 version of Halo: Reach (only given out by MS in that beta test) use the same topology data and 3 of the 6 XGD2 games protected by AP2.5 use the same topology data, but the other 3 have their own patches.
The way forward is LT+ 3.0 and to patch with abgx360 1.0.6 though.
The way forward is LT+ 3.0 and to patch with abgx360 1.0.6 though.
Click HERE for up to date 360 tutorials that may help you!
#8
08 Jan 2012 @ 9:18
Originally posted by funksoulb:Many thanks again
I don't know for sure mate. Maybe your particular rip of the game isn't in the database. They don't actually use the same protection, as in 1.0.5 the AP2.5 data that was patched in was game specific. With 1.0.6 and LT+ 3.0, all XGD3 games apart from the XGD3 version of Halo: Reach (only given out by MS in that beta test) use the same topology data and 3 of the 6 XGD2 games protected by AP2.5 use the same topology data, but the other 3 have their own patches.
The way forward is LT+ 3.0 and to patch with abgx360 1.0.6 though.
