Print

[wolfienuke]

QUOTE(ILLPLEASA @ Dec 20 2006, 04:16 PM)

4th Attempt)

- Made a 'Whole Disc (Stealth Xtreme 3.0)' iso. of Halo:Combat Evolved (USA) using Schtrom360Xtract V3.1.. The restulting .ISO came out to alittle under 7gb (I believe it was 6.95).

- Used Schtrom360Xtract V3.1 'XDVDXS XTR' feature to rip out the files from the ISO. This gave me a folder of all the files resulting in a 3.47gb sized folder (1,166 Files, 57 Folders).

- I then used Craxtion 4 to rebuild the ISO which gave me a 3.47 .ISO.

- I then burned the ISO using IMGBurn 2.1

- Loaded up the Xbox 360 with Xtreme 5.0B and placed the disc in.

- (This step I forgot to list it in my last 3 attempts but it did happen in those as well.) Xbox 360 goes to the White Screen with Xbox1 logo on it.

- While still in the white xbox logo screen, A window comes up from right side of screen saying "Original Xbox Game - Can't play this game. For more info, go to www.xbox.com/support.

Now I don't know why everyone elses ISO's are booting to the actual game and then crashing or giving DIFFERENT  error reports other than the one I'm posting. But it seems like my xbox KNOWS that these are valid games but just refuses to load them as from what I can gather from the message I'm getting.

Noone else has said that they recieved MY error. They have said that they either get another type of error or that their game loads and they get a Dirty Disc Error.  HAS ANYONE RECIEVED THE SAME ERROR THAT I HAVE BEEN GETTING? (Excuse the frustration folks, its been a long day and I apologize for it in advance.. )

I WISH I could atleast get my game to load so I know its not me doing anything wrong.. I may try updating my Xbox Backwards Compatibility  to the most recent but I doubt that will be doing anything since as I said earlier this game was compatible from the launch of 360 and my original Halo 1 disc loads perfectly from it...

And remember people.. Don't throw away your coasters.. Just because they didnt work now doesnt mean they won't work with a future firmware upgrade ..

You have the HArd Drive attached, correct? Also, are you connected to XBL to install the update, or have you burned the xbox compatibility update to disk and installed it? Also ensure that in Craxions preferences, Auto-patch xbe is not enabled. This will break the file's signature and prevent the game from working.

Sorry, missed the part of you saying your original works... check craxions preferences though.

[wolfienuke]

QUOTE(ILLPLEASA @ Dec 20 2006, 04:35 PM)

- HDD is attached...

- Never connected my box to Live.. Havent installed the update, if I decide to do it I will do it via CDR from downloaded ISO off of Xbox.com

- Craxion preferences has Auto-Patch dissabled (since I first started using Craxion on Attempt 3)

I am unsure what is wrong then. I personally do not use Craxion (GDFimage is prefered). The only time I have gotten that message is when I backed up a game which was not on the compatibility list (I forgot to check it). I also use CloneCD to burn and a Pioneer 111D (Updated to current firmware - 1.24 I believe). Can you post an md5 of your iso?

[ILLPLEASA]

Hey Guys, A couple of new updates..

- I went to the official site and downloaded and burned the "Original Xbox Game Support Update (DEC 06)" and placed it into my 360 to update..

- It updated the Game Support and then prompted me to update my system as well (and didnt let me play any discs until I did ggrrr   )

- After both of the updates, I tried all 4 of my Xbox 1 backups that didnt work before and this time I got a new error message...

"Original Xbox Game - This original Xbox game has encounted a problem and can't continue. For more info, go to www.xbox.com/support....... X: 5014.0 B: 1884.0"

Well theres some progress for me...

QUOTE(wolfienuke @ Dec 20 2006, 07:40 PM)

I am unsure what is wrong then. I personally do not use Craxion (GDFimage is prefered). The only time I have gotten that message is when I backed up a game which was not on the compatibility list (I forgot to check it). I also use CloneCD to burn and a Pioneer 111D (Updated to current firmware - 1.24 I believe). Can you post an md5 of your iso?

Remember Wolfienuke, my first 2 attempts were using GDFImage instead of Craxtion4 and those still didnt work.... I'll see if I could get you the md5 in a bit though..

[zaic3k]

Hello, I have a Toshiba Samsung ms28 drive flashed with Xtreme 4.2a firmware. I want to upgrade it to 5.0. Previously I did it with VCC Trick. How can I update it ? Now I have VIA Sata controller.

I have found faq for Via chipset (bad flash method) and there is a question, when do I have to put DVD Enable0800 in ?

Sorry 4 mu english ... i'm from BELARUS ;]

[ILLPLEASA]

QUOTE(modistru @ Dec 20 2006, 08:02 PM)

New conclusion (am I wrong?): MS28 = no go/at all/not even boot of Halo.

Well my drive is an MS25 (March 06) flashed with orig 5.0B (WITHOUT the 'Make file for MS25' as my console was manufactued before the end of May 06 and as such doesnt need it...) and I've yet to get a backup working...

[wolfienuke]

QUOTE(ILLPLEASA @ Dec 20 2006, 05:26 PM)

Well my drive is an MS25 (March 06) flashed with orig 5.0B (WITHOUT the 'Make file for MS25' as my console was manufactued before the end of May 06 and as such doesnt need it...) and I've yet to get a backup working...

I have a MS25 - MFR Date 12/09/2005 with xtreme 5.0B Keyed with X360SAM 0.6 (also didn't use make file for MS25, the x360SAM 0.6 works fine for me). I have gotten xbox backups to work but with limited results.

I will have a friend's ms28 tomorrow (hopefully) and will see if vcc/10 second wait tricks are required or not. I know I have needed to turn the 360 on, insert enable 0800 disc, turn it off and on again, wait until it reads the disc, and then eject it to enable flashing. I don't know if you can, but I highly recommend removing any media before flashing.

QUOTE(zaic3k @ Dec 20 2006, 05:02 PM)

Hello, I have a Toshiba Samsung ms28 drive flashed with Xtreme 4.2a firmware. I want to upgrade it to 5.0. Previously I did it with VCC Trick. How can I update it ? Now I have VIA Sata controller.

I have found faq for Via chipset (bad flash method) and there is a question, when do I have to put DVD Enable0800 in ?

Sorry 4 mu english ... i'm from BELARUS ;]

I am not sure on that now, I have not reflashed a ms28 yet. To flash it before, I used 10 second wait trick, which worked flawlessly, but it may prove more difficult if you need to do the 10 second wait AND enable 0800 disk at the same time. Honestly, I don't think the 10 second wait trick will be required, I think the firmguard in the xtreme 4.x will take care of that.

[Mysoundhurts]

QUOTE(mantagtj @ Dec 19 2006, 08:40 PM)

rubberband mod on youtube....http://www.youtube.com/watch?v=Df5xjUOcLlI

can i post that?

 it worked 100% thank you so much, i have been getting open tray errors for a few  onths this worked completely, 100% of my back ups work everytime, it appears that the dvd laser moves too far in and the rebber band stops it, thanx a million after doing mod I can now say xtreme5.0 is the best.

[Iriez]

QUOTE(modistru @ Dec 20 2006, 11:44 AM)

I have to tend to agree with you on this.

XB1 backups created the following ways:
   Orig in XB1 DVD drive, xfer to PC via FTP (XBMC, UnleashX, EvoX - tried all 3)
   Create ISO with GDFImage (and Yursoft xISO)
   Burned with Nero/CloneCD/Alcohol 120

Tried +RW(Imation), and -R media (Taiyo Yuden + TDK)

9 coasters (that all work in the XB1... and yes, the +RW is technically not a coaster)
all the ones that 'should' work report '...encountered an error' screen on 360.

360 stats:
MS28 (replaced a Hitachi 46DJ with this) running either 5.0a/5.0b same results.

If you have a working XB1 single layer backup, I'd love to know the following:
XB1 backup method
ISO creation method
Burn method
Media
360 drive/FW version
Thanks... sick of having to shred perfectly (as far as the XB1 is concerned) backups.  

I have taken games ripped to my HD, or availible through other 'online' resources, and imaged them with gdfimage and burned with imgburn. I have had 100% success rate with compatible, non-signature broken games. I use crappy TEON media DVD-R burned at 8x. I have a MS25.

It seems to me that you are doing everything correctly.

Im wondering if its the fact that you had a hitachi previously thats screwing things up. Perhaps they have updated the dashboard to do a check similar to that of what causes e66, except through xb1 games?

You know, i got a new xbox360 today...it had a brand spanking new ms28. I tried 4.2a, 4.2b, 5.0a, b (and c...not a public revision) and 5.1a/b (also not public) and i could only get ONE game to boot....ONE! Out of over 10 tried on EACH firmware. It was a ritek...the verbatims wouldnt even boot! Not xb1 titles...anything.

So i think that some drives are honestly plain fucked.

[wolfienuke]

QUOTE(Iriez @ Dec 20 2006, 06:37 PM)

I have taken games ripped to my HD, or availible through other 'online' resources, and imaged them with gdfimage and burned with imgburn. I have had 100% success rate with compatible, non-signature broken games. I use crappy TEON media DVD-R burned at 8x. I have a MS25.

It seems to me that you are doing everything correctly.

Im wondering if its the fact that you had a hitachi previously thats screwing things up. Perhaps they have updated the dashboard to do a check similar to that of what causes e66, except through xb1 games?

You know, i got a new xbox360 today...it had a brand spanking new ms28. I tried 4.2a, 4.2b, 5.0a, b (and c...not a public revision) and 5.1a/b (also not public) and i could only get ONE game to boot....ONE! Out of over 10 tried on EACH firmware. It was a ritek...the verbatims wouldnt even boot! Not xb1 titles...anything.

So i think that some drives are honestly plain fucked.

That maybe true. I have noticed the ms28 drive is more particular about what media it likes. Sometimes a firmware update for your DVD burner may help, but it may not. This is a totally seperate issue then xbox1 backup problems though. I had to update my pioneer 111D firmware from 1.06 (which worked fine with my ms25) to 1.24 so that my SONY DVD-R DL discs can be read on a ms28. Is your burner up to date? what model is it?

QUOTE(teegale @ Dec 20 2006, 06:39 PM)

I could be wrong, but aren't you supposed to be making the discs at 2.4x, not 8x?

You are thinking or DVD-R DL, he is talking single layer. Single layers do not have 2.4X

[Iriez]

QUOTE(sdeens @ Dec 20 2006, 05:20 PM)

TO SUM THIS UP:

1.  WE CAN STILL NOT MAKE XBOX1 BACKUPS PROPERLY WORK WITH V5.0A/B---PERIOD END OF STORY!

2.  UNCONFIRMED ISOLATED REPORTS THAT CERTAIN GAMES (I.E BLACK ETC..) MIGHT WORK INTIALLY AND HALO THru THE FIRST 2 LEVELS...IF EXTRACTED WITH AN OLD SCHOOL MODIFIED XBOX1 AND BURNED TO DVD -R;  BUT SINCE HALO CAN'T PLAY PAST THE SECOND LEVEL..THEN THIS IS ALSO USELESS AND THEREFORE IT IS NOT RIPPED CORRECTLY.

3.  THE CURRENT TOOLS: SCROTUM V3.1 AND XBC V2.3 ARE NOT THE SOLUTION YET..AND THERE IS NO DIFFERENCE IN FILE SIZES BETWEEN A BACKUP THAT USES SECTOR MAPPING ON OR OFF...IT MERELY SKIPS PAST THEM (OR AUTO-FILLS WITH ALL ZEROS) AND SPEEDS UP THE RIP.

4.  THE FIRMWARE V5.0A/B BOTH SEEM TO BE BUGGY TO SAY THE LEAST AND OBVIOUSLY NOT WORKING
    PROPERLY WITH NEW RIPS OF XBOX1 GAMES...EVEN OLD RIPS ARE NOT STABLE.
conclusions:

1. either the ripping tools need modification or the firmware needs updating to address these problems...LOGICALLY THE CONSLUSION IS BOTH..since this firmware is radically different.

2. choice of media used (ritek, verbatim, Yudin etc..) makes no difference..in fact that should not even be an issue of discussion...they all work fine for the most part on XBOX360 DL disk backups, so it not a media issue at all.

3.  using an external DVD (Samsung SH-D162C) flashed with KREON v.81 is not helping us make proper backups of the XBOX1 games to single layer DVD -R's that work with v5.0a/b firmware...regardless of what tool you want to use..and those isolated reports of BLACK working are not strong enough to draw that conclusion...until  can get 10 different games to work as backups then its not a fact!
MY OBERVATIONS FROM MY VERY FIRST POST IN THIS MASSIVE THREAD HAVE NOW BEEN PROVEN..MY CONCLUSIONS WERE 100% CORRECT..THIS FIRMWARE IS BUGGY AND THE RIPPING/patching TOOLS ARE BEHIND AND NEED TO PLAY CATCHUP TO ADDRESS THE PROPER WAY TO RIP AN XBOX1 GAME FOR XBOX360 USAGE.

UNTIL THEN IT MAKES NO SENSE TO USE V5.0A/ OR V5.0B...IN FACT THERE ARE SEVERAL DISADVANTAGES TO IT..CONSIDERING THE MANY REPORTS OF TRAY EXTRACTION ERRORS AND ITS COMPATABILITY WITH CURRENT XBOX LIVE GAME UPDATE IS STILL very much UNCERTAIN.

please do NOT flash to this v5.0a/b firmware untill ALL (yes all of these problems have been addressed)..it is too buggy and too much still in beta testing...wait until v5.1 is released and/or new ripping/patching tools are signicifcatly updated and proven to work and many different XBOX1 games.

don't use it!

p.s.
pardon the upper case...typed too fast to notice it until the end.

1: Wrong. I have many many xb1 backups (along with many many others) working perfectly fine.

2: I have yet to hear a 2nd confirmation of this. Do you read one post and assume its true?

3: The solution has been present for 4+ years...obviously some people on this board just dont know what the hell they are doing.

4: Wrong once again. I have a 3 year old backup playing absolutly fine, and a scene rip from a month ago playing great aswell.

Second section of BS?

1: Tools are fine. Appears to be user error, since i have many confirmed reports of success, aswell as personal success.

2: media is ALWAYS ALWAYS ALWAYS a issue. What world do you live on? If you burn a fucked game, to crappy media or good media, its not gonna boot either way. Its not the media, its the user.

3: The D162 / kreon works fine. Unless you seem to sugess that it breaks the hash on the files while in read-only operation? lol.

"MY OBERVATIONS FROM MY VERY FIRST POST IN THIS MASSIVE THREAD HAVE NOW BEEN PROVEN..MY CONCLUSIONS WERE 100% CORRECT..THIS FIRMWARE IS BUGGY AND THE RIPPING/patching TOOLS ARE BEHIND AND NEED TO PLAY CATCHUP TO ADDRESS THE PROPER WAY TO RIP AN XBOX1 GAME FOR XBOX360 USAGE."

No, no no, no no, and no.

Your ENTIRE post was misinformation, based on user error, and isolated situations. Wow what a drama you've caused. You read through a thread where only people with problems post, and think that it is a valuable source of information? for every problem mentioned, i spoke to 20 people who didnt have that problem.

Are there bugs? Of course. There will always be bugs when thinking outside the box. They will get fixed. However, for you to ASSUME that because a specific person has a issue, that the firmware is to blame, is absurd. Please do not post such misleading garabage again.

And lastly...for YOU to tell people to not use it? Wow, the audacity Get a grip on yourself kid.

[Iriez]

QUOTE(wolfienuke @ Dec 20 2006, 09:45 PM)

That maybe true. I have noticed the ms28 drive is more particular about what media it likes. Sometimes a firmware update for your DVD burner may help, but it may not. This is a totally seperate issue then xbox1 backup problems though. I had to update my pioneer 111D firmware from 1.06 (which worked fine with my ms25) to 1.24 so that my SONY DVD-R DL discs can be read on a ms28. Is your burner up to date? what model is it?
You are thinking or DVD-R DL, he is talking single layer. Single layers do not have 2.4X

I have burnt disc's with the 1.19, 1.29 and crossflashed to 111L 8.26 ...all work, but the 1.29 and 8.26 work the best. I was able to fix some open tray issues going from 1.29 to the 111L 8.26 crossflash, as apparently it lengthen's lead-in's.


AND FOR THE LAST TIME, IF YOU HAVE A VIA SATA CARD AND WISH TO UPGRADE FROM ANY XTREME WITH 'FIRMGUARD' THE 10 SECOND ON/OFF TRICK DOES THE SAME EXACT THING AS THE ENABLE 0800 DISC. THEY ACCOMPLISH THE SAME PURPOSE. ONLY ONE IS NECCESARY.

NOTE- the above statement is in reference to FLASHING. The bad recovery method is not a replacement for enable 0800 in the purpose of ripping xbox games

[wolfienuke]

QUOTE(Iriez @ Dec 20 2006, 07:21 PM)

I have burnt disc's with the 1.19, 1.29 and crossflashed to 111L 8.26 ...all work, but the 1.29 and 8.26 work the best. I was able to fix some open tray issues going from 1.29 to the 111L 8.26 crossflash, as apparently it lengthen's lead-in's.
AND FOR THE LAST TIME, IF YOU HAVE A VIA SATA CARD AND WISH TO UPGRADE FROM ANY XTREME WITH 'FIRMGUARD' THE 10 SECOND ON/OFF TRICK DOES THE SAME EXACT THING AS THE ENABLE 0800 DISC. THEY ACCOMPLISH THE SAME PURPOSE. ONLY ONE IS NECCESARY.

OK GOT IT! you don't have to shout... I just haven't looked into that before. Thanks for the info... hehehe

QUOTE(qent4977 @ Dec 20 2006, 08:52 PM)

Hi Cpasjuste, sorry for asking a noob question but, with the method you posted does this mean that i dont have to open my xbox360 anymore? just plugin in the usb disk and do all the steps??
Thanks!

What??? I think you are confused... read some tutorials. The only 2 options to flash your drive without opening the case are:

- Blaster360 which is not publicly released yet, and...
- cutting a hole in your case to access the sata cable

You cannot upgrade the firmware via the xbox 360 usb port. Geez

[firestorm2yk]

I dont think it's a media issue, if that was the case then Halo would DDE in different places, but instead it DDE's in exactly the same place for everybody, which is the start of the "Truth and Reconcilliation" level.

Iv'e tried different media and the results are the same. Halo boots just fine, but so far i cant see anyone who can actully load the third stage of Halo. My original xbox loads the backup just fine.

Iriez, if you dont mind, could you try loading the third stage of Original Halo from a single layer backup and tell us what happens?

[wolfienuke]

QUOTE(firestorm2yk @ Dec 20 2006, 09:26 PM)

I dont think it's a media issue, if that was the case then Halo would DDE in different places, but instead it DDE's in exactly the same place for everybody, which is the start of the "Truth and Reconcilliation" level.

Iv'e tried different media and the results are the same. Halo boots just fine, but so far i cant see anyone who can actully load the third stage of Halo. My original xbox loads the backup just fine.

Iriez, if you dont mind, could you try loading the third stage of Original Halo from a single layer backup and tell us what happens?

Can you post an md5 hash of your halo1 iso? NTSC/U, right?

[wolfienuke]

One thing I found out. I have a folder with all the files from my backup. I use GDFimage.exe to make an iso. I then created another iso also with GDFimage.exe of that same exact folder with no modification. The md5 hashes to NOT match... is this a problem? I would think if it creates the iso with the same files in the same order, the hashes should be the same.

MD5 hashes.
Original ISO unmodified from XBOX via ftp: de7f95c38e8664837383b8ed9453079e
Iso made with GDFimage from extracted iso: 23892005731cbccf338fb23b3e65e7e3
2nd ISO made with GDFimage from same files: 16677e790bc673c030d7e6c906ab8b47

Could this be a reason for the dirty disk errors? I was just messing around with iso creators to see if I can find one that works the best with xtreme 5.0, when I noticed this difference.