User User name Password  
   
Wednesday 27.11.2024 / 15:09
Search AfterDawn Forums:        In English   Suomeksi   På svenska
afterdawn.com > forums > consoles > xbox 360 - modding & hacking > what's wrong with halo reach??
Show topics
 
Forums
Forums
What's wrong with Halo Reach??
  Jump to:
 
Posted Message
TonyJer
Member
_
7. January 2012 @ 19:31 _ Link to this message    Send private message to this user   
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.
Advertisement
_
__
TonyJer
Member
_
7. January 2012 @ 19:31 _ Link to this message    Send private message to this user   
Originally posted by TonyJer:
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.
Forgot to say that using LT 2.0 not 3.0!!
Member
_
7. January 2012 @ 19:40 _ Link to this message    Send private message to this user   
you answered your own question....u need 3.0.
RIARA
Member
_
7. January 2012 @ 22:09 _ Link to this message    Send private message to this user   
maybe the box has had enough of Halo, lol, yeah you need 3.0
Senior Member
_
8. January 2012 @ 00:14 _ Link to this message    Send private message to this user   
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!
TonyJer
Member
_
8. January 2012 @ 05:09 _ Link to this message    Send private message to this user   
Originally posted by funksoulb:
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/
Oh shit! Many thanks, diddn't realise that.

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
Senior Member
_
8. January 2012 @ 06:21 _ Link to this message    Send private message to this user   
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.

Click HERE for up to date 360 tutorials that may help you!
Advertisement
_
__
 
_
TonyJer
Member
_
8. January 2012 @ 09:18 _ Link to this message    Send private message to this user   
Originally posted by funksoulb:
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.
Many thanks again
afterdawn.com > forums > consoles > xbox 360 - modding & hacking > what's wrong with halo reach??
 

Digital video: AfterDawn.com | AfterDawn Forums
Music: MP3Lizard.com
Gaming: Blasteroids.com | Blasteroids Forums | Compare game prices
Software: Software downloads
Blogs: User profile pages
RSS feeds: AfterDawn.com News | Software updates | AfterDawn Forums
International: AfterDawn in Finnish | AfterDawn in Swedish | AfterDawn in Norwegian | download.fi
Navigate: Search | Site map
About us: About AfterDawn Ltd | Advertise on our sites | Rules, Restrictions, Legal disclaimer & Privacy policy
Contact us: Send feedback | Contact our media sales team
 
  © 1999-2024 by AfterDawn Ltd.

  IDG TechNetwork