Media checks

[delain]

It could be that when a drive or disc error occurs it triggers a check mechanism on suspicion that the disc is a backup. Or else it only performs these checks randomly. This seems like they would have to go out of their way to program in those conditions when checking for the PFI/DMI every time wouldnt slow down the load time by any significant amount. Quite odd.

[quicksilv]

what does a "drive inquiry" actually mean in regards to an original drive and hacked sammy/hitachi?

and fuzzylogic can you check if the kernel also does the tests if you are signed in to an gold account but with the cable removed? if it does it could mean ms is storing that information untill the user connects to xbox live

[whitedevil]

i've been reading up on how fw + backup-images work and hope someone can address some of my questions:
- video partition layer1 -> do any of the backup creation tools include layer1 or only layer0 atm?
  or are we not able to create 100% backups right now?
- bitsetting: DVD-ROM is suggested, but xtreme images with DVD+R DL boot just fine.
  Do both hitachi+samsung firmware report DVD-ROM back if queried? (and considering code upload with the hitachi this will be a problem, so the hacked fw should just reject these discs all together)
- physical properties of a disc ("pressed" as opposed to "ritek", etc), does the hitachi+samsung
  firmware return proper data?
- if an original disc is inserted does a modded fw act like an original fw? meaning does it get the desired sectors/requests using the nonhacked methods? just wondering if originals are safe offline
- "Most of my games have this on 1F1B1C or 1F1B1E instead - but all of them, including one that has zeroes there, passes the Stealth check in Xbox Backup Creator 2.5 when looking at the isos"
i am not liking this very much, shouldn't xbc fail here? i'll be checking my backups with all 4 methods just to be sure (xbox backup creator, xdvdmulleter, schtrom360extract and dvdinfo manually)
- spoofing a drive: when an ms25 is spoofed as ms28 wouldn't it be detected as the firmware now has firmguard which it normally woulnd't have (i'm not sure about this, don't have a sammy)


Fuzzylogic: when you checked doa4 were you signed in or had the lan cable connected? do the kernel itself run any checks offline?

I 2nd this question list.

[jelle2503]

look man this find it is really great, and work being done on it , is just as great.

nonetheless the new firmware will block bad copy's, but would someone be able to write an easy stealth checker (like acidflash stealthchecker), so people are able to scan their images if they're proper, with a samsung pc drive?

[XFear]

Xdvdmulleter can check a xbox360 backup disc in your pc-drive

[calvin940]

Any of the stealth checkers out there now don't work as they would have identified the bad SS extraction by some Hitachis that C4ever was talking about in a posting a few days ago.  He mentions that some SS while allowing the game to boot are not complete or contain bad data.  He cites some Hitachi drives as being the culprits and if the stealth checkers never identified those, then they currently aren't worth anything.  Those need to be fixed with a "complete" SS check and check for video partitions on the other layer (since vid partitions are supposed to be on both).

Cal

[FuzzyLogic]

Another thing to keep in mind when stealthing the firmwares:

MS could inject a fake challenge in the CR sequence, If the drive responds normally, it is obviously detectable.

I explain this with challenge type 1:
When the drive receives a challenge type 1, it's instructed to read 8 bytes from a particular sector on the disc.
The first 4 bytes should be equal to 4 bytes received in the challenge data. If this is the case, then the next 4 bytes will be send back in a response to the Xbox.

Problem is, currently there is no check if this data matches. (for Hitachi FW) It is assumed the Xbox will send the correct challenge data.
Something to remember when designing the iXtreme online fw for Hitachi.

[mcmanic]

Another thing to keep in mind when stealthing the firmwares:

MS could inject a fake challenge in the CR sequence, If the drive responds normally, it is obviously detectable.

I explain this with challenge type 1:
When the drive receives a challenge type 1, it's instructed to read 8 bytes from a particular sector on the disc.
The first 4 bytes should be equal to 4 bytes received in the challenge data. If this is the case, then the next 4 bytes will be send back in a response to the Xbox.

Problem is, currently there is no check if this data matches. (for Hitachi FW) It is assumed the Xbox will send the correct challenge data.
Something to remember when designing the iXtreme online fw for Hitachi.

nice, hope you've told c4eva and co about this, even if it means delaying the release, its better to have all ours bases covered rather than MS owning them, lol

[garyopa]

MS could inject a fake challenge in the CR sequence, If the drive responds normally, it is obviously detectable.
Something to remember when designing the iXtreme online fw for Hitachi.

"c4eva" mentioned last night, that this is also one of the things he is fixing in the new firmware.

[FuzzyLogic]

MS could inject a fake challenge in the CR sequence, If the drive responds normally, it is obviously detectable.
Something to remember when designing the iXtreme online fw for Hitachi.

"c4eva" mentioned last night, that this is also one of the things he is fixing in the new firmware.

Ah ok,  I assumed he patched that already, i only looked at the Hitachi FW.

[e5frog]

So, are us Hitachi users better off with swapping for a Samsung instead, since that FW seems to have better stealth ability? There's a lot of MS25 on eBay, would that be recommended? Will it be necessary to spoof it as the original drive?

OR - is the swap itself an even worse scenario?

[ruffrydaz]

If they do challange checks on a backup of a movie then what will happen? will it be the same as a game?

[MechEngineer]

Hello Everyone, I am a noob to this forum but not to Modding. I have 4 XBOX 360's three of which are still on XBlive running Extreme 5.3 flashed after the spring update. I have not allowed any backups to be played sence thursday the 17th when I first heard of the banning. Two of my DVD drives are Sam's MS28 and the third is a MS25. The fourth has the 3ROD and I am currently in the process of yanking that apart and modding it into a Sony 400 disk DVD changer. I want to thank all the Hackers here for all there hard work to give us the the tools to be able to do what we do. None of this would be possible without your hard work and dedication. I was and guess still am one of those kids that needed to know how it works so I can make it do what I want it to do. Well sorry to ramble and go off topic just wanted to say Hi to everyone. If I can offer any more information that might help anyone please ask, I will do what ever I can to help.


Mech.

[Spies]

@FuzzyLogic

Is there a command that can checksum each bank on the dvd-rom? I ask this because if theres only a single checksum for the whole firmware it's somewhat useless for Microsoft as everyones checksum will vary due to the unique key...

[FuzzyLogic]

The key is outside the area that is used to calculate the checksum. So the checksum will be the same for all drives with the same firmware version.
But there is no command that can do a checksum on the firmware and report it back to MS.

[MechEngineer]

Would make sense but A friend and I both have the exact same Setup/Games And I am banned he is not....Only difference is that I updated my firmware again after the update...That might have been the KILLER  for me

What would you do if you were MS. Would you ban in 1 go ALL people with back ups ? I know I wouldn't. I would start to ban slowly, randomly. You don't want to lose all gamers from your network, you just want them to stop using backups. And the most effective way to attain that is by banning randomly some people. "Fear" is the goal here.

So in other words, not getting a ban doesn't mean they haven't detected you. At least, that would make lots of sense to me.

I am really starting to see it this way also. When you take a look at the all the information being compiled on here and XBOX-Scene it just realy does'nt point towards any one thing for us to say what M$ uses for banning. I am still ok.......had three sytems flashed for almost a year on XBL... I am not banned on any of them.....

I took two of them back to the original state on the 17th, but I still play my MS28 on XBL. Each time there was new release of the hacked firmware I would apply it to he Orig. dump then flash that back to the drives. I played around several times with my MS28 drive flashing back and forth and playing backups and orig. Trying to provoke a banning to disprove some of the suggested reasons for banning. My backups have always been from the originals, never from WARZ or anything like that. I guess with all that said it is quite possible I have reached the threash hold and could be banned when the hammer is thrown again even if fllashed with a new method of protection in the future. The only way to know is to run the next firmware release on a new machine and take that risk. I am sure M$ is considering how not to lose to much revenue by banning all of us at once. they don't want to creat e more market space for sony to nab plus they can sell more counsels this way, win win situation for M$. Hard to see clearly this is with all the BS that comes with the forums......

[Obveron]

I'm curious about timing and spoofing.  Do the samsung and hitachis respond different to the timing queries?
Would an Ixtreme samsung spoofed as hitachi stick out because its firmware is emulating samsung timings and not hitachi?

[sasoseso]

This explains why I am not banned.. once the banning started (a day after halo 3 beta), I never started another game with the flashed FW, although I had a backup in the drive (but not launched). then I flashed back to original FW. so far I am still unbanned.

how did u powered the drive??