Print

[trigger_]

Hi

I just wanted to know the best way to "Stealth Check" a copy of my backup (after I have burnt it). Note my setup is a Samsung Kreon drive, Xbox Backup Creator v2.3 and a dvd-burner drive that I can't remember the name of.

So ideally I'd like to put the backup disc into one of the drives and use some sort of app to test if its Stealthed.

ps: I know there is a Stealth Check button in Xbox Backup Creator but I have only used this button to test the .dvd file. I want a similar check after I have burnt the file onto a dvd.

[ILLusions0fGrander]

all i know is kreon auto patches those sectors, so i personally dont worry about it.

however that doesnt help you make sure... will a backup without those sectors still boot in the latest extreme?
because i know some documentation says "do not use this method with older firmware"

[Perplexer]

I'd try extracting PFI/DMI from your backup using SchtromXtract.  If you get an error in either step, then your backup is not stealth.

[pb_05]

hey i really hate the bust in a thread....but whats the purpose of making a stealth backup... :/ ?  if im running OPA v2.3 on a H47-dj? do i need to? i likewise have the samsung with kreon and just plan on using xbc to make backups

[IntestineMan]

pb_05 think of it as futureproofing... maybe one day Gary-OPA may support all the media stealth features. Plus, with most of the latest utilities they do the stealth automatically so one would have to go out of their way to make a non-stealth backup!



trigger,

If you are real curious want to manually look/verify at those sectors on backup, load up isobuster and look at following sectors...


PFI = 129821
DMI = 129822
SS = 129823


Compare them with the individual bins.


FYI, those are last 3 sectors of the Video partition, where xtreme style firmwares re-direct the original requests to. If you wanna understand more... a sector is 2048 bytes. Since sectors start at zero we will count like 0-129822 instead of 1-129823. Now go look at the video360.iso in xtreme and notice it is 265,873,408 bytes long, divide by 2048 and you get a length of 128921 sectors (or sectors 0-128920). After that there is PFI, DMI and SS at sectors 128921, 2 and 3 respectively. You will notice the build360.bat does a binary copy of all these files and ends up with the desired results - pretty simple really. I realize you are using XBox Backup Creator but sometimes it is interesting to know how it works instead of just clicking a button.

Consider the PFI and DMI as copies of the original and they are put in an unused spot on the backup. When a request for this PFI or DMI data is made from the Xbox 360, the hacked firmware intercepts this, looks up the original info at these sectors and returns the data (making it look like a normal disc... hopefully). If these PFI or DMI sectors are not there (all 00's instead), the firmware has embedded PFI and will return the real DMI from the backup (possibly flagging it as a copy).

Maybe if C4E is reading this, could update future version to make it return a read-error or something to the console if these sectors are requested from non-stealth backup - this way if MS does implement media DMI check later on, accidentally putting in a non-stealth backup will cause a disc read error and not much evidence for MS to ban because how could they presume the disc wasn't damaged?

This post has been edited by IntestineMan: Dec 12 2006, 08:51 AM

[Creamy Goodness]

QUOTE(IntestineMan @ Dec 12 2006, 08:21 AM)

Maybe if C4E is reading this, could update future version to make it return a read-error or something to the console if these sectors are requested from non-stealth backup - this way if MS does implement media DMI check later on, accidentally putting in a non-stealth backup will cause a disc read error and not much evidence for MS to ban because how could they presume the disc wasn't damaged?

thats a good idea... but i'm sure they could use some logic like "if you have more than one game that fails the DMI check with a read error, ban console..." because the chances of more than one disc having those sectors unreadable is pretty slim, right?
the best would be to have some space in the firmware set aside with a database of the PFI/DMI info for some popular games, but i'm guessing there isn't much spare room in the flash memory to do this type of thing. since i dont think the firmware can read from any external sources, maybe such info could be retrieved from a disc. you could put in a game, firmware remembers what game it was, then you put in some generic dvd with pfi/dmi info for all your games on it, and the firmware finds whichever pfi/dmi it needs, then you put the game back in and it boots. sure, its a lot of swapping, but it's probably easier / cheaper than re-ripping all your backups that don't already have correct pfi/dmi on them.

that Schtrom360Xtract thing was hard to find btw... well not so hard if you google the filename (IMG:style_emoticons/default/wink.gif)
Schtrom360Xtract_V3.1.rar

looks like it only works if you have a xbox dvd drive hooked up to the computer... not quite what i wanted
since any dvd drive can read the pfi and dmi sectors of a backup disc since they're on the video partition. i'm sure theres some way to read those sectors without making an image of it. not sure what the easiest way would be. if anyone knows, please update this thread (IMG:style_emoticons/default/wink.gif)

This post has been edited by Creamy Goodness: Dec 16 2006, 03:05 AM