Post by: Xbox-Scene on August 08, 2011, 09:07:00 PM
ABGX360 about new iXtreme v1.91 FW and AP2.6 Posted by XanTium | August 8 23:07 EST | News Category: Xbox360 |
| From abgx360.net: Quote
Official Site: http://www.abgx360.net |
Post by: Darkflame on August 08, 2011, 10:13:00 PM
But is it possible that Microsoft could simply push an update that says.
Flash the DVD-Drive like before, send the lock commands like before and update the system dashboard but randomly pick a DAE and have the dashboard quetly flash that DAE.
So we can all update our boxes, some of us might have challenge #5 stored in our nands, others might have challenge #28 stored, others #19 etc. On a original, all the responses are there yet on CFW + ABGX we have to preprogram our responses. Thus this would render ABGX and CFW more of a russian roulette rather then a viable means to play our backups?
I mean what good is patching the data with one set of credentials if your box is flashing a random choice of 1-50?
That's like 49 bullets and one free chamber after each system update.
Is this feasable or is the current implementation of AP2.5 not permissible of this.
Post by: specialguest on August 08, 2011, 10:29:00 PM
Post by: xxxDarkxxx on August 08, 2011, 10:34:00 PM
Post by: iateshaggy on August 08, 2011, 10:36:00 PM
Post by: BigSteel on August 08, 2011, 11:03:00 PM
Post by: iAmMasterF on August 08, 2011, 11:55:00 PM
This post has been edited by iAmMasterF: Aug 9 2011, 06:58 AM
Post by: khontos on August 09, 2011, 12:35:00 AM
QUOTE(iAmMasterF @ Aug 9 2011, 01:55 AM) 
my halo reach has ap25 from dash 13146... its that ok for LT+1.91 on dash 13599?
yep
Post by: XBOX360NYMODING on August 09, 2011, 01:32:00 AM
Post by: danthaman673 on August 09, 2011, 02:41:00 AM
QUOTE(Darkflame @ Aug 9 2011, 01:43 PM)
IIRC there are 50 possible replies that can be sent from a AP2.5 Challenge? Damn I might be way off please chime in and correct me if I am mistaken.
But is it possible that Microsoft could simply push an update that says.
Flash the DVD-Drive like before, send the lock commands like before and update the system dashboard but randomly pick a DAE and have the dashboard quetly flash that DAE.
So we can all update our boxes, some of us might have challenge #5 stored in our nands, others might have challenge #28 stored, others #19 etc. On a original, all the responses are there yet on CFW + ABGX we have to preprogram our responses. Thus this would render ABGX and CFW more of a russian roulette rather then a viable means to play our backups?
I mean what good is patching the data with one set of credentials if your box is flashing a random choice of 1-50?
That's like 49 bullets and one free chamber after each system update.
Is this feasable or is the current implementation of AP2.5 not permissible of this.
No, Fortunately AFAIK It doesn't work like that...
Think of it this way: M$ have rolled-out drive FW, it does what it needs to(inc. new reply to new challenges), to support new features. CFW emulates those responses the same way the original does. Because the current system means that we can't physically write the security layer to the disk, so it has to be written somewhere... AFAIK, that info is basically a 'replay' of the result of a physical test of the original security feature (Using varied angles) I would think there would be a formula that could be applied to model that test, probably better suited to emulation based devices. M$ could use Title updates and other sneaky things to do other challenges that silently fail, we would find-out an act accordingly ...but we're not there yet and neither of us wants to be there, just yet....
I think this post is addressing (apart form the usual noob FAQ stuff) some issues that have arisen lately over alternate means of patching AP2.5. Some ppl think some means are safe, that are generally believed not be so..
Brgds/Dan
This post has been edited by danthaman673: Aug 9 2011, 09:47 AM
Post by: mafla on August 09, 2011, 04:41:00 AM
not a good game of cod b.o Irish problem
What is the problem?
Post by: blackopsftw on August 09, 2011, 04:54:00 AM
Think about it, you're playing an AP2.5 game, all of a sudden it requests a dashboard update. You accept, then immediately after the update your AP2.5 game spins up, with now incorrect responses, immediately you're flagged for a ban. Where before all that would have happened was a black screen and you would have been saved by drive fw.
I'd say definitely the best advice would be to avoid dash updates until testers/banned consoles confirm dae.bin has been updated and new patches have been released. If this means going without live for a week or two then so be it, we're no longer protected by FW.
QUOTE(iateshaggy @ Aug 9 2011, 05:36 AM)
yes, because running an iso though a simple program is so hard to do before burning your backup.
abgx360 won't be immediately updated after a dash update and will show the disc as having correct replay data, when in actuality it won't
abgx360 won't save many people imo.
Post by: iateshaggy on August 09, 2011, 05:28:00 AM
Post by: tullyfish on August 09, 2011, 05:38:00 AM
As for all this talk about MS could do this or MS could do that. Worry about it if and when they actually do it. I am sure you will read about it on here first.
Post by: Gazc0igne on August 09, 2011, 07:17:00 AM
QUOTE(specialguest @ Aug 9 2011, 04:29 AM)
So I guess all this really means is that as of now there are only 6 games to stay away from... i dont care to mess with all of the AP25 patching stuff. The easy thing to do is not play them at all.
i'd bet good money that at some stage all games will have AP2.5 checks in place, the 6 used so far are only a trial run IMHO
Post by: danthaman673 on August 09, 2011, 08:40:00 PM
QUOTE(Gazc0igne @ Aug 9 2011, 10:47 PM) 
i'd bet good money that at some stage all games will have AP2.5 checks in place, the 6 used so far are only a trial run IMHO
I think perhaps they're sticking to the most widely used games, as the whole set-up is resource hungry to implement on a game by game basis, plus 100% implementation means 100% of sceners looking for a solution, and 100% ppl using the latest counter-AP methods, as opposed to ppl putting games in despite FW/patches and playing haphazardly there will be a large majority of ppl ignorant or in the dont care category, allowing M$ to gather stats/monitor behaviors and drop the temporary sales-increasing ban-hammer whenever they look like getting close to posting a loss for any given quarter (or whatever) The rest of the time, many would argue they actually make more money at the end of the day by allowing the use of backups. Like you said, they can guage the effectiveness and when the Xbox 720 roll's around you can bet it will have AP2.7 incorporating all the most effective features in all areas ;-)
I still think CFW should be able to model the c/r of orig somehow, failing that, we could use the SPI to add an SD Card in parallel with challenges etc.. the options are endless.. (I like darkflame's disc idea also, might be a little vulnerable to timing checks perhaps ..)
Brgds/Dan
Post by: Darkflame on August 10, 2011, 10:09:00 AM
1. You press eject. Xbox says tray open.
2 you put game dvd in within 3 secs tray auto closes. Xbox says tray open still.
3. Spins up reads GID tray opens. You remove game and insert dae disc.
4. 3 secs later tray closes Xbox still says tray open. Wait it reads and ejects.
5. Remove dae disc and re insert game. Now you push tray or eject button Xbox says tray closed and reading.
Using a cfw patcher you set the delays. 1-10 secs per swap rotation etc.
If you screw up the sequence it'll just not progress far enough to flag you since tray will remain open or it will act as if no disc was in the tray.
MS can't ban you for being a slow disc loader. Maybe I'm disabled and need 15-30 seconds to get the disc in the tray.
there's always a way to mask or justify your actions.
Post by: jamiebarrington on August 10, 2011, 11:15:00 AM
QUOTE(Darkflame @ Aug 10 2011, 05:09 PM)
One way to prevent timing checks is like this.
1. You press eject. Xbox says tray open.
2 you put game dvd in within 3 secs tray auto closes. Xbox says tray open still.
3. Spins up reads GID tray opens. You remove game and insert dae disc.
4. 3 secs later tray closes Xbox still says tray open. Wait it reads and ejects.
5. Remove dae disc and re insert game. Now you push tray or eject button Xbox says tray closed and reading.
Using a cfw patcher you set the delays. 1-10 secs per swap rotation etc.
If you screw up the sequence it'll just not progress far enough to flag you since tray will remain open or it will act as if no disc was in the tray.
MS can't ban you for being a slow disc loader. Maybe I'm disabled and need 15-30 seconds to get the disc in the tray.
there's always a way to mask or justify your actions.It does sound like a good plan and sorry but im not a genius on the firmware side but is it even possible to set the delays when writing the firmware?
Post by: Aldanga on August 10, 2011, 11:19:00 AM
Post by: LSU_P8tball on August 10, 2011, 04:11:00 PM
QUOTE(moh.sakhaii @ Aug 10 2011, 02:58 PM)
Exactly, your ideas are really getting ridiculous people. LOL, just stop pretending being technical while you know, you don't know jack
I know Jack. He just came over last night for dinner. Really nice guy even though he doesn't know "jack".
Post by: Gazc0igne on August 10, 2011, 04:13:00 PM
QUOTE(boflc @ Aug 9 2011, 02:05 PM)
this, tho i would change 'all' to 'almost all new' or 'big new'. btw, glad to see you (?back?) over here gaz.
Many thanks for the kind welcome back, its been a while since i was on this forum glad someone rememebrs me
some of the ideas put forth are a bit far fetched lol but a good read
it will be interesting to see how the upcoming ODD emulators will fare out with the AP2.X checks that we will see in future, as well as how c4eva keeps up.
i do remember reading somewhere once from a respected member that all games since certain date a few years back had the AP2.5 data on them, and that it was only a matter of time before m$ were finished their testing on certain titles, and hit the big red button to enable them all.
IMHO the development of the phat liteon and slim liteon drives and how the current AP2.5 tests have been progresssing lately to me points to only this end result.
m$ has upped its game considerably.
Post by: .:Dino:. on August 10, 2011, 05:00:00 PM
QUOTE
But is it possible that Microsoft could simply push an update that says.
Flash the DVD-Drive like before, send the lock commands like before and update the system dashboard but randomly pick a DAE and have the dashboard quetly flash that DAE.
Flash the DVD-Drive like before, send the lock commands like before and update the system dashboard but randomly pick a DAE and have the dashboard quetly flash that DAE.
Can anyone comment on this, seems a logical possibility to me
Post by: Trevante on August 10, 2011, 06:02:00 PM
Post by: pinkerton on August 10, 2011, 06:24:00 PM
QUOTE(Trevante @ Aug 11 2011, 01:02 AM)
I'm just going to play my originals lol.
What originals?
Just kidding!
Post by: Trevante on August 10, 2011, 06:48:00 PM
QUOTE(pinkerton @ Aug 10 2011, 07:24 PM)
What originals?
Just kidding!
LMAO!
On the real though if I ever need to play Halo Reach, I'm just going to use the original disc. All this re-burning, AP 2.5, AP 2.6, DAE, and other stuff is too much effort for me just to try and play those few games.