xboxscene.org forums

Xbox360 Forums => Xbox360 Hardware Forums => Xbox360 Backup Forum - DVD DL help / ISO Building => Topic started by: sosotiit on December 19, 2006, 12:17:00 PM

Title: Star Trek Legacy, Crackdown
Post by: sosotiit on December 19, 2006, 12:17:00 PM
I did backup of all my games before without any problems using a SH-D162C(0.81) and Xbox backup creator (v2.3), but can't make it for star trek legacy.

I took all my other originals and tried them again, without any problems. So my pc/Drive seems still as functional as it was.
Also tried with Schtrom and same problem. Only this game that I cannot backup.

The following happens when I follow my usual routine for backup:

-start XBC,
-put dvd in
-it reports
Getting media info [F]
   Uknown Partition size. Used bytes = 5.32 MB
   Media Type: DVD-ROM
   Bytes Used: 5.32 MB (5,578,752 bytes)
if I eject/insert again I get
Getting media info [F]
   Media Type: DVD-ROM
   Bytes Used: 7.05 GB (7,572,881,408 bytes)

when I start the extraction it tells me
''unable to determine current visible partition''
and stops

I can extract ss, pfi,dmi apparently ok if done from the drive tools tab

any feedback?
thks, soso

This post has been edited by sosotiit: Jan 23 2007, 01:47 AM
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on December 19, 2006, 06:03:00 PM
anyone tried the extracting Star trek legacy.
Still trying here but it still does not see the game partition, the rest  seems ok???

rgds, soso

This post has been edited by sosotiit: Dec 20 2006, 02:03 AM
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on December 20, 2006, 05:44:00 AM
Finally made it work, but I had to use Isobuster to extract the game.iso and then merge it with the SS, DMI, PFI using SSMerger.
 
First time  I have to do this. Usually XBK can do the whole thing.

Anyway, just FYI, incase you encounter the same prob with STL.

rgds, soso
Title: Star Trek Legacy, Crackdown
Post by: ILLusions0fGrander on December 20, 2006, 10:02:00 AM
thanks for posting back your solution in case someone else has the same problem
Title: Star Trek Legacy, Crackdown
Post by: dpderr on December 20, 2006, 07:08:00 PM
How did you do it with ISObuster?  When I select the drive, all I see are the video_TS and audio_TS folders.
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on December 20, 2006, 08:02:00 PM
Where you trying to extract with a SH-D162C or a X360 drive?
If you look around there is a tutorial
How_to_rip_games_with_the_Samsung_SH-D162C.doc
that describes this in more detail.
I will give you the short version but it is similar to what you get in the Hitachi/samsumg tutorial

-DVDinfopro and you send custom command FF 08 01 11 01, close DVDinfopro
-isobuster, click on dvd, rightclick and choose Extract From-To and enter 0 and 3567872, start extraction.
call it game.iso (even if it suggest .tao)
you can extract your SS, DMI, PFI with Xbox Backup creator.
merge with ssmerger (or other )

hope it helps, sorry I am a bit short on time tonight. (IMG:style_emoticons/default/sad.gif)
rgds, soso

This post has been edited by sosotiit: Dec 21 2006, 04:05 AM
Title: Star Trek Legacy, Crackdown
Post by: dpderr on December 21, 2006, 10:51:00 PM
Oops!  Sorry I wasn't more specific!  I used a Samsung SH-D162C drive with Kreon .81.  I used DVDInfo to get the SS.BIN and to unlock the drive so I could extract the ISO using ISOBuster.  Used ISOBuilder to merge the SS.BIN and rebuild the ISO with the video file to make the game a full 7.05 GB.  Works like a champ!  Thanks for the help!
Title: Star Trek Legacy, Crackdown
Post by: ydgmms on December 22, 2006, 03:08:00 PM
do you have to extract the video.iso portion?
Title: Star Trek Legacy, Crackdown
Post by: dpderr on December 22, 2006, 04:01:00 PM
"do you have to extract the video.iso portion?"

No, I only extracted the game portion.  When you use the ISORebuilder, it will inject a blank video file to take up the proper space on the disc.
Title: Star Trek Legacy, Crackdown
Post by: someguyinwaterloo on December 22, 2006, 03:26:00 PM
Is it possible to give a complete how to for this?
I am trying it and I am definitely missing something and I would love to stop making coasters.
Maximum detail would be greatly appreciated but I am at your mercy smile.gif

Thanks!
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on December 22, 2006, 03:53:00 PM
Hi ydgmms,
dpderr used the Isobuilder that is in the Garyopa package, it is the simplest solution you can find.
If you want to include DMI, PFI and a Video.iso you should use ssmerger. I used SSmerger but did not include a video.iso (instead I used Pad with blank option), also I did not take the NME Iso option (needed only if you have an NME chip).
Two options: one simplest , the other a bit more versatile, same good result biggrin.gif .

@someguyinwaterloo,
in order to help you and if you want more detailed info, you need to do the same for us  wink.gif  .

I see it is your first post, have you made functional backups before? and is it only STL that is causing you problems? Just to be sure we are chasing the proper issue, and that it is not extraction from a 47dj, bitsetting, incompatible burner... if that is your first backup I suggest you start with some of the tutorial here,here or here.
If it is only STL: What version/drive you have? are you using PC drive like (SH-162C) to extract or X360 Drive? Which software (Xbox Backup Creator, Schtrom, isobuster...)?
Really , I am not trying to make you life though, just want to be sure we are looking for an answer to appropriate problem. As they say, there is nothing more useless than a good solution to the wrong problem (after translation biggrin.gif ),
rgds, soso
Title: Star Trek Legacy, Crackdown
Post by: chaospie on December 22, 2006, 09:13:00 PM
I've been having the same problem all day.  I also have a Samsung SH-D162C.  I tried using Schtrom 3.1 and got nothing.  Then i tried XBC v2.3 and was able to get an iso, 6.80 GB.  I did this by going to the Drive Tools tab and unlocking the drive (The program says that the drive is already unlocked).  But when i look at the "bytes used" info it changed from 5.32MB to 6.81GB.  Then I went into the READ tab and selected current partition. Clicked start and was able to get an image.

Questions:
1. Is this image patched? (SS, PFI, DMI, video.iso?)
2. How can i get all these files?
3. What should i use to inject the image to make it 7.05GB?

Please help thanks.

This post has been edited by chaospie: Dec 23 2006, 05:15 AM
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on December 22, 2006, 09:26:00 PM
It seems you have the game.iso only.
The only other one you absolutely need is the SS, and you can extract it with Xbox creator in the drive tools. you can get DMI and PFI as well at the same place if you want (not mandatory).
WIth SS merger you select the two files (or four), choose pad with blanks, do not select NME compatible and then do merge, and burn. (as per message above you can also use the Isobuilder that can with the firmware package).
rgds, soso

This post has been edited by sosotiit: Dec 23 2006, 05:29 AM
Title: Star Trek Legacy, Crackdown
Post by: chaospie on December 22, 2006, 10:53:00 PM
thanks a lot for your help.  just curious what does the insert iso do?  and how can you extract a video iso without using schtrom
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on December 23, 2006, 07:57:00 AM
just to clarity on the video.iso, it is a small set of dvd files that will play if you put your dvd in a PC. It plays a 3 second clip that says to play this disk put it in a Xbox 360.

WHen you backup with XBK or schrtom, the backup includes the video.iso.

now to your question, with ssmerger you have the choice to use a dummy video.iso filled with blank files (will not play the clip in a PC) or to insert a copy of a real video.iso (that is why you have the insert iso option).

You can extract the video.iso with schtrom. In the case of STL where schtrom does not work, you still can use schtrom to extract from another game since the video.iso is always the same from game to game.
Or you can go in the firmware package for Samsumg drive in the folder XBox360Stealth , there is a video.iso that can be used.

Note it is not really need, but here you go.
rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on December 23, 2006, 09:26:00 AM
Before you use isbuster you must unlock the drive (even with kreon 0.81), so use dvdinfopro and send the custom command FF 08 01 11 01, close dvdinfopro and then extract using Isobuster. When ask for the name enter game.iso (even if it says .tao ) the file generated is then game.iso (no cue file or changing extension required, not sure if it has an impact but that is how it worked for me.). The game.iso file should be 7,307,001,856 bytes if you right click on it in windows (6.8G)

Then use xbox creator (that part was working for me) to extract ss.bin (and PFI , DMI if you want them) and ssmerger (pad with blank, no NME compatible), layerbreak and ssoffset as per xbox360, burn 2.4X on good media.
IPB Image
hope it helps, rgds, soso
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on December 23, 2006, 10:20:00 AM
in dvdinfopro
bottom left make sure you have the sh-d162 selected,
just right of this select in the advance command, the one that says send custom command (a window will open cdb 0 to 11 field. Enter FF 08 01 11 01 in the first five field as per image below(from a tut I refer in previous post), and send it.

IPB Image

It is not permanent in any way, do not worry.
then it is isobuster time.
It is worthed, great game (all but one mission which is a pita)
rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on December 23, 2006, 11:08:00 AM
QUOTE
1) What do I need to do with DVDInfoPro BEFORE I use isobuster
2) What do I extract (SS.bin? what is that ... etc)
3) How do I merge (I see some references to a batch file which I can't locate)


for 1) See post 17 and 19 , you need to unlock the drive yourself with isobuster (something XB creator and schtrom does for you)
for 2) With isobuster : click on dvd, rightclick and choose Extract From-To and enter 0 and 3567872, start extraction. call it game.iso (even if it suggest .tao enter exactly game.iso as name)
With xbox creator go in Drive tools extract to the same folder as game.iso the Security sector (SS.bin), PFI and DMI.
for 3) If you do not know about the batch file in the firmware package I suggest you rather download ssmerger 1.7b.
and select the four files you have just created, put the options as per post 17  and hit the big merge sign (get a coffee it is 15 minutes to process smile.gif )
Burn with imgbrun @2.4x (or your favorite prog) on good quality media.

rgds, soso
Title: Star Trek Legacy, Crackdown
Post by: sdeens on December 23, 2006, 04:00:00 PM
SOSOTiiT:
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on December 23, 2006, 05:07:00 PM
QUOTE
let's keep this strickly an XBC v2.3 solution and avoid IsoBuster and DVD.infoPro

If you have a different solution you are welcome to present it, but in a proper way. if you are not interested to participate in a constructive way in this thread, I politely invite you not to do so.

From your message, you say that you believe the way to do this and
 I will test tonight for XBC v2..3 complaince so you have not even tested your assumptions!!!
When I presented to Redline99 (author of Xbox creator) the difficulty to extract the whole disc of STL, he confirmed he had seen this behavior before, that he would look into it as he wanted to correct this.

What I presented here is one way (tested and working) to address this backup of STL.
I will stop it at that.
rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on December 23, 2006, 05:26:00 PM
@PSPPSP
If your command in dvdinfopro

IPB Image

is done Ok (besure to do send) then you should see only this in Isobuster
- DVD
- session 1
- track 01

I believe the Dvdinfopro did not work, sorry, try again as they say under the cap biggrin.gif .

in ssmerger it is ok to choose the four lines as
game.iso  (if that is what you called it)
SS.bin
pfi.bin
dmi.bin

and
IPB Image


happy to help,

rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on December 23, 2006, 09:12:00 PM
Happy it worked, and the game is good,
merry xmas,
rgds, soso
Title: Star Trek Legacy, Crackdown
Post by: sdeens on December 23, 2006, 11:03:00 PM
just follow the procedures I laid out earlier in this thread and its an easy backup, you don't need to use Isobuster or DVdinfoPro at all..that's old school and redundant...as long as you have an SH-D162B drive flashed with Kreon v.81 connected to your PC....if you use your XBOX360 drive instead to perform the RIP then you have to unclock drive with DVDinfoPro, but after xtreme v4.2a I am not sure you need to do even that anymore.

simplest method:

1.  launch XBC v2.3
2.  select Drive Tools
3.  Unlock Drive--press this twice to get it to recognize the partition size correctly (that's the bug in it--no big deal--its NOT always automatically detected)--ignore the response that says drive is already unlocked--tha';s the KREON firmware doing its job, I suspect.
4.  READ image--select "current partion" NOT "complete backup--I mis-stated that in my first tutorial---ooops type too quickly.
5.  It will be 7,135,744 (or: 7,307,001 if you go into Properties---that;s why I don't use the PROPERTY values)
6.  XBC v2.3--go back to Drive Tools and extract all three (SS, PFI and DMI)--YES definately all 3!
     ---2kb each in size
7.  save to same folder as the .iso that XBC v2.3 created earlier
8.  Launch SS Merger 1.7b--use those settings in thread posted above--#25--select ALL 4 files
9.  ignore the request to do an on-line Xtereme verfication--select NO when prompted.
10. press the MERGE button--this takes about 30-45 minutes to merge the new complete ISO
11.  Burn wih ImgBurn v2.1..same deal as before--I used 4x speed on Verbatim DVD +R DL media

works exactly as it should, this is the DEFACTO STANDARD for ripping and burning these newer 360 games with SH-D162B KREON v.81 drives.


BTW this game has no way to save the game progress during a MISSION...what a tremendous mistake by the game developers...no doubt that will be frustratinbg later in game on more difficult levels..


as I said before you don't need Isobuster ($30 program)  or DVDinfoPro if you have the kreon flashed sammy drive..

p.s.

sometimes knowing a way to do a thing "old school" is good, but NOT this time

Title: Star Trek Legacy, Crackdown
Post by: sosotiit on December 24, 2006, 07:09:00 AM
As per my first message, I have backed up all my game before this one with Xbox Creator and absolutely love that software. In fact the majority of my post are in the Xboxcreator threads.

There are many things I could tell you on your posts , but it would only feed your apparent inclination for confrontation; things like the Kreon FW default is unlock 2 ( as indicated in NFO) and that is why you need to send the FF08011101 in order to have unlock 1 and get an Xtreme style (instead of Wxripper style in unlock 2);     In the end your approach requires to extract all separately and merge so there is little gain why make such a fuss;     If everything must be Xboxcreator or nothing why burning with imgburn (use xboxcreator) ?.

All of that is irrelevant, my point is that if you find another way to do things you can present it in a respectful way without telling everyone they are wrong and that all threads in X-S should follow your authority (that after 12 posts!!!). Many people are using Wxripper and isobuster ( i am not one of them) and I fully respect that. If you do not want to do that, do not participate.

again, what I presented here is one way (tested and working) to address this backup of STL. It has helped many people it seems.


rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on December 24, 2006, 08:41:00 AM
QUOTE(PSPPSP @ Dec 23 2006, 10:56 PM) View Post

THANK YOU Sostiit!!!  You are the man!!  I got it going and works great!!  The only thing was when in isobuster the file that was created this time was a little smaller than you indicated "The game.iso file should be 7,307,001,856 bytes if you right click on it in windows (6.8G)"  It was actually a little bit small than what you stated, but when I sent the command and saw what I indicated in post #23, it came out to the exact size as you stated.  In any case it seems to have worked out!  Thanks for ALL your help.  

Sometimes trying to figure out the "how to part" is just as fun as the Playing part.  Thanks for ALL YOUR HELP!!
 laugh.gif  love.gif



You may have been in windows explorer in which case it is shown in KB (kiloBytes) which would be 7,135,744 KB. That is the same as 7,307,001,856 Bytes or 6.8 GigaBytes (GB). To see it in Bytes you need in explorer , to right click on the file and choose properties. But if you get 7,135,744 KB it is the same thing.

rgds, soso
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on December 29, 2006, 10:02:00 AM
The author of XBCreator (redline99) says he knows this problem, but he does not have access a STL. He mentionned he might look into it later.

I beleive it is the only title doing this. It seems to have something to do with the unlock of the game partition.
Some people had success by unlocking manually then using Xboxcreator to extract the game.iso.

But you still need to extract separatelly ss, dmi, pfi and then merge so it is not a big gain.

Hope it helps,
rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: Yateball on January 03, 2007, 09:25:00 AM
I followed Soso's instructions for this game and it works perfectly, I originally had the same partition problem with XBC, first time ever I've had any problems with it.

Didn't even know about the ISObuster method but the game works perfect. Thanks a lot Soso!
Title: Star Trek Legacy, Crackdown
Post by: Dravor on January 03, 2007, 08:57:00 PM
QUOTE(Yateball @ Jan 3 2007, 05:32 PM) View Post

I followed Soso's instructions for this game and it works perfectly, I originally had the same partition problem with XBC, first time ever I've had any problems with it.

Didn't even know about the ISObuster method but the game works perfect. Thanks a lot Soso!


So is the only real change here that some of the new games will require a different unlock sequence?  I'm not as familiar with XBC, but after using it, it seems that Schtrom most likely works very similiar, except in that it hides all of the different steps (ripping game.iso, ripping the ss file and the two others, remerging all three)?

If so, shouldn't the fix be easy?
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on January 03, 2007, 09:39:00 PM
That is interesting,

The game has is info set slightly differently then the others it seems. Why this game would require verbatim and not others???  Some people in this thread succeeded with other brand.  But huge thanks for the info.

Not sure if from redline and schtrom standpoint it is only a question of unlock (because they must have been doing if before anyway). Not expecting it to be a big thing, but I honestly do not know by expertise, it is only intuition.

rgds,soso


Title: Star Trek Legacy, Crackdown
Post by: sosotiit on January 03, 2007, 10:06:00 PM
It is the only one like that,
so like you not expecting to be big thing as far as correction.

rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: rykon9 on January 04, 2007, 09:57:00 PM
I wanted to thank everyone for the hardwork that is done figuring this stuff out.  It is great to be able to have someone work this out for the masses.  Thanks again, I know this might not be a lot of thanks, but I wanted anyone who works and figures this stuff out my gratitude for taking the time out to learn this stuff.
Title: Star Trek Legacy, Crackdown
Post by: VVaI2LoCk on January 08, 2007, 10:03:00 PM
QUOTE(VVaI2LoCk @ Jan 9 2007, 04:34 AM) View Post

First off cudos to both methods on here. It's great that we have a choice and I'll leave it at that.

Sdeens:
I'm trying to use your method. And on the step where you say to click the Merge button on SS Merger v1.7b I get a dialog box that opens up. I try to put the name of a new file and it doesnt work. Then I try to put the name of the original ISO i created using your instructions with XBC2.3 and I get an error: You must select a video partion. Can you elaborate a little more on your instructions relating to after you select the .iso,ss.bin,PFI.bin.DMI.bin then you press merge and ?????? I get an open dialog box and dont know what to do next.

Thanks a bunch.

Title: Star Trek Legacy, Crackdown
Post by: VVaI2LoCk on January 09, 2007, 05:15:00 AM
Just wanted to confirm sdeens method works perfect.
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on January 09, 2007, 06:37:00 AM
Great news, the more options the better  biggrin.gif
rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: Lucky1201 on January 21, 2007, 10:39:00 AM
how do you backup star trek:legacy ripping with xbox 360 drive TS-H943A?
can't seem to unlock with dvdinfopro.

sdeens "if you use your XBOX360 drive instead to perform the RIP then you have to unclock drive with DVDinfoPro, but after xtreme v4.2a I am not sure you need to do even that anymore."
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on January 21, 2007, 11:35:00 AM
never tried a THS943 but
you may try sending FF 08 01 01  or  FF 08 01 11 01 to unlock

agreed it should not be needed, but STL seems to respond slightly differently than  other games.

rgds, soso
Title: Star Trek Legacy, Crackdown
Post by: Lucky1201 on January 21, 2007, 04:12:00 PM
QUOTE(sosotiit @ Jan 21 2007, 01:42 PM) View Post

never tried a THS943 but
you may try sending FF 08 01 01  or  FF 08 01 11 01 to unlock

agreed it should not be needed, but STL seems to respond slightly differently than  other games.

rgds, soso

tried both got DVDinfopro: sense error
                             XBC:Found ODD: TSSTcorp DVD-ROM TS-H943A ms28 at [E]
   Uknown Partition size. Used bytes = 5.32 MB
Getting media info [E]
   Uknown Partition size. Used bytes = 5.32 MB
   Media Type: DVD-ROM
   Bytes Used: 5.32 MB (5,578,752 bytes)
   Uknown Partition size. Used bytes = 5.32 MB
   Uknown Partition size. Used bytes = 5.32 MB
Action: Unlock Disk (Xtreme)
DeviceIoControl Error: 0x0000045D
The request could not be performed because of an I/O device error.

Sense Error: 0 / 00 / 00
NO ADDITIONAL SENSE INFORMATION
CDB: Undefined
0xFF 08 01 01
Getting media info [E]
   Media Type: DVD-ROM
   Bytes Used: 5.32 MB (5,578,752 bytes)
Action: Unlock Disk (Xtreme)
DeviceIoControl Error: 0x0000045D
The request could not be performed because of an I/O device error.

Title: Star Trek Legacy, Crackdown
Post by: sosotiit on January 21, 2007, 04:28:00 PM
Is this only with this game? and others are detected OK.

Does it go in 0800 mode? and is SS, DMI, PFI extract correctly?

rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: Lucky1201 on January 21, 2007, 04:45:00 PM
QUOTE(sosotiit @ Jan 21 2007, 06:35 PM) View Post

Is this only with this game? and others are detected OK.

Does it go in 0800 mode? and is SS, DMI, PFI extract correctly?

rgds,soso

First game I have had a problem with. Yes,if you are referring to star trek, it goes in 0800 I believe because the drive is recognized in windows, but I can't read or extract anything
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on January 22, 2007, 05:04:00 PM
It seems there is a similar problem with Ncaa March Madness 07 .
So you can try one of the two methods presented here.

1)you could use isobuster if xbcreator is not working.

and this is the best tutorial , only in step 2 change the FF 08 01 01 for FF 08 01 11 01 as per image below

IPB Image

or
2) as per sdeens in post #28



hope it helps,


rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on January 30, 2007, 11:38:00 AM
QUOTE(cocojo @ Jan 30 2007, 01:35 PM) View Post

i have followed exactly you instruction, but what if i have the nme chip, how do i convert the image file?



To my knowledge, same as any other game with an nme, use associator from  the site of NME.
Some members reported that Associat0r sometimes as a prob to extract the ss and move it to the proper location using the Convert tab. Some people made it work by extracting the ss.bin from their image (use ssmerge, schtrom, XBCr) and then they called associator to do the merge+conversion using the seperate files in the Merge tab. For some it seems to do a better job at inserting a ss at the right place then moving it.

nothing specific to STL or NCAA Madness, maybe should have been in another thread wink.gif.

rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on February 02, 2007, 08:04:00 AM
looks like your kreon is not seen that well, could it be drivers?
went PIo instead of DMA
Maybe reflash the the SHD126c (some had to reflash it once or twice), other conflict Hardware , soft???

rgds,soso

Title: Star Trek Legacy, Crackdown
Post by: Biby on February 02, 2007, 08:58:00 AM
QUOTE
Action: Read Security Sector
Sense Error: 6 / 29 / 00
POWER ON, RESET, OR BUS DEVICE RESET OCCURRED
CDB: READ DVD STRUCTURE
0xAD 00 FF 02 FD FF FE 00 08 00 03 C0


any suggestion?
Title: Star Trek Legacy, Crackdown
Post by: miremare on February 10, 2007, 07:36:00 AM
Hi

i have tried the above.
i get as far as getting all the 4 bits together the iso and the other 3 files.
when i try to merge i get this:-

***.iso is extreme file lenght

it wont let me do anything else.

is this something to do with the patch on my sh-d162 dvd rom
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on February 10, 2007, 07:39:00 AM
when you hit the big yellow merge and create, nothing happens?

if you run the stealth check of XBCr (or schtrom) on the game.iso after what does it say??

rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on February 18, 2007, 07:30:00 AM
Is that your first backup? if not are other backup working fine?
after you finish, try schtrom 3.1/tools/stealth check to see if all pieces are there.
If it is you first, Iwould try with another game if you have one, make sure the rest of the process is OK  smile.gif .

rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on February 18, 2007, 07:54:00 AM
pre burn on the iso ( or .000) image on your disk.
soso
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on February 18, 2007, 11:49:00 AM
too big,
are you sure you have removed the selection of NME compatible?
before burning, run the test again

rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: TWilly on February 18, 2007, 01:13:00 PM
OK...I see it, under the SS merger app.  Uncheck the Create NME compatible ISO.  Yes this was checked.  OK I will redo the merge without it and see what happens.  Thanks!

TW
Title: Star Trek Legacy, Crackdown
Post by: StrictPuppet on February 18, 2007, 01:23:00 PM
QUOTE(TWilly @ Feb 18 2007, 05:19 AM) View Post

Have I done something wrong or do I have to modify the 360 firmware? (which I have not done)


If the drive has not been flashed with modified firmware, there is no way your backup will ever boot, no matter how you make it.
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on February 18, 2007, 02:21:00 PM
you can look in the faq section of hacking/technical dvd-rom forum ( Releases and Tutorials ) and this doc here.

Also suggest you give a look at the posting rules, many discussion on XBL to be careful.

AS far as the fw being detected?? who knows. One strict rule at XS, only original (no Bup) to be played on Live.
and yes the warranty is gone.

rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: StrictPuppet on February 19, 2007, 10:08:00 PM
CODE
Found ODD: TSSTcorp DVD-ROM SH-D162C TS04 at [G]
   Additional Info: XB360 KREON V0.81
Getting media info [G]
   Uknown Partition size. Used bytes = 5.32 MB
   Media Type: DVD-ROM
   Bytes Used: 5.32 MB (5,578,752 bytes)
<*unlock drive again*>
Getting media info [G]
   Media Type: DVD-ROM
   Bytes Used: 6.81 GB (7,307,001,856 bytes)


Not sure if this has been mentioned yet or not, just adding it to the list...
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on February 20, 2007, 05:09:00 AM
HI strictpuppet,
yes and most of the new games have the new smaller video partition, so I am guessing that a good part of the new releases will have this problem.
Redline and schtrom are working on this , question of time only for this to be resolve.
rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: andjelko on February 20, 2007, 10:36:00 PM
When backing up Crackdown - I use xbc v2.3 to create ss.bin, pfi.bin, dmi.bin.  I twice click unlock drive in drive tools and then extract the current partition.  I then take these files and use xbox 360 stealth (included with xtreme 4.2) and run build360 with video provided and I get image.000.  I then run ss merger 1.7b with my current partion game iso and the ss, pfi and dmi created earlier.  Turn NME off and insert video iso image.000.  All goes well except when I run stealth check.  I get "unable to determine the validity of the PFI sector"  with other checks coming back ok.  I haven't tried to burn this yet.  Was wondering what I was doing wrong or if I should be concerned.

Using SH-D162C with kron 0.81.

Thanks.
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on February 21, 2007, 05:17:00 AM
the pfi is also slightly different, try the imag stealth check in schtrom which I beleive is ok for that new PFI.
anyway it should be correct.
rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: Rippster on February 21, 2007, 06:30:00 AM
NME 1.2 with Crackdown

I picked up Crackdown yesterday and figured I would try and make a backup of it. Well, like everyone has said here, Schtrom gives the error that it is not an XBox disc. I hit this forum and after getting home from work, I’m happy to say I made a perfectly working backup.

My Specs:

XBox 360 with Samsung MS28 Drive
NME 1.2 Chip Installed

PC:
Pioneer 111D
Samsung D163A w/ Kreon .80

I used SDEENS method although logically the other methods listed here should work as well.

Once you’re done using SDEENS method from line #28 and the SSMERGER settings from line #25, you will have an image you can use NME Associat0r on. I started to do the SS extraction and insertion method but figured I would just first give the little application a chance to just Convert. Wham Bam, the conversion went off perfectly creating an image set at 7.525.056KB. I then let CloneCD burn it and it works great.

Hope this helps any of you NME users out there.

Ripp
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on February 21, 2007, 06:39:00 AM
you mean conversion with associator "convert" tab instead of "merge" tab or do you mean with ssmerger?

thks for the info, soso
Title: Star Trek Legacy, Crackdown
Post by: andjelko on February 21, 2007, 08:09:00 AM
QUOTE(sosotiit @ Feb 21 2007, 01:24 PM) View Post

the pfi is also slightly different, try the imag stealth check in schtrom which I beleive is ok for that new PFI.
anyway it should be correct.
rgds,soso


thanks for your response sosotiit.  When you say the pfi is different I'm assuming that when xbc2.3 verifies pfi - the fact that its slightly different is why the check comes back as failed (again this is for pfi only).  Is this a limitation of xbc 2.3 - and don't get me wrong the software is great and I appreciate all the help and software thats been provided.
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on February 21, 2007, 08:28:00 AM
QUOTE(andjelko @ Feb 21 2007, 11:16 AM) View Post

thanks for your response sosotiit.  When you say the pfi is different I'm assuming that when xbc2.3 verifies pfi - the fact that its slightly different is why the check comes back as failed (again this is for pfi only).  Is this a limitation of xbc 2.3 - and don't get me wrong the software is great and I appreciate all the help and software thats been provided.


yes there is a small bug in 2.3, it makes it tell that something is wrong when in fact it is just the a different format of a valid PFI. Redline knows about it , and pretty sure it will be fixed in the next release he mentioned in his thread.

rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on February 21, 2007, 11:21:00 AM
file size is OK,
run the stealth check of  Schtrom  to see if all pieces are seen?

if so your prob may have nothing to do with the image.
how is it burned: drive/media to be used on which x360 drive/fw?

rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: cjf28 on February 23, 2007, 02:53:00 AM
ok,  i  got ss merger to open up.  had to download the .net program
Title: Star Trek Legacy, Crackdown
Post by: SF2MJ on February 23, 2007, 05:30:00 AM
I used your xbc v2.3 method for backing up crackdown.

1)I started xbox backup creator
2)selected ASPI
3)selected driver tools
4)click unlock x 2
5)then went to read tab
6)selected read "current partition"
7)it dumped an iso that was 6.80gig in size i called it "crack"
8)then i went to drive tools and selected extract "ss,pfi,dmi...i extracting them into the same folder as the iso i just created.
9)I opened ss merger v1.7b...and then proceeded to set it up like the user sosotiit stated in his thread.
10)then when i went to add my iso it added it then came up with a box that said "crack.iso extreme style length".
And the SS bar is lit up in red...i guess meaning the security sector bin file is wrong.Even if i ignore all this and still try to merge the files with the iso file.I still get a message popping up saying "crack.iso extreme style length".
What am i doing wrong?.
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on February 23, 2007, 06:53:00 AM
nothing wrong you are OK,
Xtreme style is good  biggrin.gif ,
It is not a problem if you have the two red fields at the bottom, I have never used the database (always got the two red fields) and it works.
It is not needed for the merge to be done correctly and we do not support the use of such database at XS
the result is probably already good.


rgds,soso
Title: Star Trek Legacy, Crackdown
Post by: cjf28 on February 23, 2007, 08:43:00 AM
when i try to extract the SS , DMI, and PFI,  into my Iso folder, it is asking me if I want to overwrite the Iso.  Is that correct?  When it makes my .iso  it doesnt make a folder, it simply does the icon with the 3 books and strap.  Am I even doing that right?

When I attempt to put my iso into   into the ss merger, i get a message telling me "crackdown.iso is smaller than Xtreme style lenght"

I dont understand if im missing something.  I create two crackdown icons on my desktop.  one is .dvd and the other is the .iso  (its always created two icons with all my games.  I use xbc 2.3)
Title: Star Trek Legacy, Crackdown
Post by: SF2MJ on February 23, 2007, 09:00:00 AM
Just follow these steps like sosotiit and VVaI2LoCk mentioned.
For the ss merger settings look at post number 25.

1. launch XBC v2.3 Done
2. select Drive Tools Done
3. Unlock Drive--press this twice to get it to recognize the partition size correctly (that's the bug in it--no big deal--its NOT always automatically detected)--ignore the response that says drive is already unlocked--tha';s the KREON firmware doing its job, I suspect.Done
4. READ image--select "current partion" NOT "complete backup--I mis-stated that in my first tutorial---ooops type too quickly.Done
5. It will be 7,135,744 (or: 7,307,001 if you go into Properties---that;s why I don't use the PROPERTY values)Done
6. XBC v2.3--go back to Drive Tools and extract all three (SS, PFI and DMI)--YES definately all 3!
---2kb each in sizeDone
7. save to same folder as the .iso that XBC v2.3 created earlierDone called it STL.iso
8. Launch SS Merger 1.7b--use those settings in thread posted above--#25--select ALL 4 files Done
9. ignore the request to do an on-line Xtereme verfication--select NO when prompted. Done
10. press the MERGE button--this takes about 30-45 minutes to merge the new complete ISO.
I used clone cd to burn the iso.
Title: Star Trek Legacy, Crackdown
Post by: cjf28 on February 23, 2007, 10:47:00 AM
Ive done all of that, and now i get a dirty disk read error on the xbox.  I use  verbatims, and the samsung drive to copy.   When XBC makes my iso, it doesnt put it in a folder, it puts it on my desktop as an icon.  So, when I try to add the 3 .bin folders to it,  it just overwrites it.  So, i made a folder called crackdown and put the iso in there.  then I added the 3 .bin files to it.  used ss merger.  It said it was done and ready to copy.  I copied, and it came out with a dirty disc read error when i put it in the 360.

I cant think of anything else I can do. any help is appreciated.  Im down to my last verbatim.  lol


thanks
Title: Star Trek Legacy, Crackdown
Post by: Navillos on February 23, 2007, 12:13:00 PM
heres my method:

1)open XBC and unlock drive
2)select current partition and dump (6.81GB)
3)select drive tools and dump DMI, PFI, SS.bin files put in same folder as game.iso
4)leave XBC open (so drive is still unlocked), open Schtrom and dump video.iso into same folder
 as all other files. run mouse over folder and see if it says 7.05GB
5)open SS merger check xtreme style and check imgburn fixes, uncheck nme, check insert iso, load up files in correct order and merge
6)burn with imgburn 2.4x, layerbreak at 1913760 booktype dvd-rom (just for the hell of it)

worked for me. a few steps but a 1:1 image.
Title: Star Trek Legacy, Crackdown
Post by: billynomates on February 23, 2007, 01:53:00 PM
wow guys thanks for the read  cool.gif  six pages of good solid info i have just done crackdown  biggrin.gif
Title: Star Trek Legacy, Crackdown
Post by: xboxconfused on February 24, 2007, 03:35:00 PM
Just wanted to thank soso and everybody on here..With this info i read on here I now have a working copy of my crackdown...Thanks EVERYBODY......
Title: Star Trek Legacy, Crackdown
Post by: satori317 on February 26, 2007, 08:17:00 AM
It seems like when I run SS Merger 1.7b, I place all the necessary files where they need to be, adjust the settings as suggested in previous posts, then merge.  But after all that, it seems like the program freezes, has anyone else experienced a problem like that?
Title: Star Trek Legacy, Crackdown
Post by: Navillos on February 26, 2007, 09:22:00 AM
QUOTE(satori317 @ Feb 26 2007, 09:24 AM) View Post

It seems like when I run SS Merger 1.7b, I place all the necessary files where they need to be, adjust the settings as suggested in previous posts, then merge.  But after all that, it seems like the program freezes, has anyone else experienced a problem like that?


i doesnt freeze just doesnt have a progress indicator if you right click on start bar and open task manager you can see it using memory and working let it sit for about 20 or 30 min depending on your comp. performance.
Title: Star Trek Legacy, Crackdown
Post by: johnm92627 on February 26, 2007, 11:03:00 AM
QUOTE(johnm92627 @ Feb 26 2007, 09:25 AM) View Post

I am trying to back up NBA Street Homecourt and I am getting the same error when I extract the SS.
PFI and DMI had no problem.

I restarted and unlocked and I was able to extract it.
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on February 26, 2007, 02:25:00 PM
QUOTE
GOOD NEWS, there is a new version of XBCreator 2.4 out,
no more problems with STL, Crackdown..
XBCreator 2.4


rgds,soso jester.gif
Title: Star Trek Legacy, Crackdown
Post by: Yateball on February 28, 2007, 03:23:00 PM
Just an FYI to everyone, this thread now also applies to the newly release Major League Baseball 2K7.... just follow all the same steps and it will work too.

Cheers,
Yateball
Title: Star Trek Legacy, Crackdown
Post by: sosotiit on February 28, 2007, 03:38:00 PM
QUOTE
GOOD NEWS, there is a new version of XBCreator 2.4 out,
no more problems with STL, Crackdown..
XBCreator 2.4


rgds,soso jester.gif