Print

[bshth]

I just flashed 8x 1.3
Thanks for answering my questions guys i really appreicate for helps  

[getRAWed]

Thanks guys, can always count on you.

I've flashed my MS25 with 1.3 (5x), using the Bad-flash method... it's so quiet, and loading times are good too ^^,

Just two more things though... when making the x13.bin file with the Batch tool, I used the ORIG.bin that I got when I first flashed my drive last night to iX 1.2... though this time, nothing was put into the Backups folder on my floppy when using mtkflash w /m /sata command in DOS prompt, so I assume this is all good?

Also, the batch creator said:


----------------------------------------------------------------------------
|      firmtool v1.0 by caster420                                     |
----------------------------------------------------------[360mods.net]-----

 Drive Key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx (I've removed that myself)

 Original Firmware Version: MS25
  iXtreme Firmware Version: MS28

*** SUCCESS ***
Drive key copied.
Drive version spoofed.

Your iXtreme firmware is now ready to be flashed!

***************************************
iXtreme v1.3 firmware created: ix13.bin
***************************************

That spoofed thing is confusing me, because even when I flashed the MS25 for the first time (using 1.2c [fast] from Xbins), it said the orig fw and iXtreme fw did not match, because the iXtreme fw was "MS28", so I pressed 'y' to spoof or something... have I done something I shouldn't have?

This post has been edited by getRAWed: Nov 13 2007, 10:14 AM

[kdallas]

QUOTE(getRAWed @ Nov 13 2007, 06:12 PM)

I've flashed my MS25 with 1.3 (5x), using the Bad-flash method... it's so quiet, and loading times are good too ^^,

That spoofed thing is confusing me, because even when I flashed the MS25 for the first time (using 1.2c [fast] from Xbins), it said the orig fw and iXtreme fw did not match, because the iXtreme fw was "MS28", so I pressed 'y' to spoof or something... have I done something I shouldn't have?

It should be fine... basically all you've done is set your firmware to report the drive as being an MS28 instead of an MS25.  If you'd said NO to spoofing it would report as an MS25 and would have copied that over from your orig.bin

It's not really relevant what version of firmware you're reporting, only that the keys in both your orig.bin and the hacked.bin are a match.

Oh and if you had used a key from a previous hacked firmware... this is fine too, although many of the tutorials say to use your original BIN.  But again its the same manufacturer for your drive and its the same key - so no harm done.

This post has been edited by kdallas: Nov 13 2007, 10:23 AM

[getRAWed]

Cool, thanks for the reply.

<3 to Xbox-Scene and everyone involved in the FW biz

[Martinchris23]

QUOTE(kdallas @ Nov 13 2007, 04:45 AM)

oh.. just a small edit to my post above.  The tutorials refer to the Hitachi's switching to "ModeB" (specifically so that Windows detects the drive and you can then use the firmware toolbox etc).  Just trying to preempt any confusion I might have created... my bad  (IMG:style_emoticons/default/tongue.gif)

But as for the bad flash method I stand by what I said that you CAN use it for all sammy's..  even if simpler methods might work on pre-MS28's.

This is what confused me - I've never had to use an 0800 disc, even before I got my 6421A PCI card. Any MS25s worked straight away through my Nforce3 chipset - the only snag was when I had an MS28 (IMG:style_emoticons/default/wink.gif)

Anyhoo - I use the 10 second method for all Sammys without the need of an 0800 disc.

QUOTE(xorcist00 @ Nov 13 2007, 03:56 AM)

just a quick question so i understand 100% clearly...1.2c quiet is 5x in 1.3?

From my understanding, the quiet mode in 1.2c is 2x in 1.3 - 5x in 1.3 is an excellent compromise.

[potvin]

QUOTE(Dazz @ Nov 12 2007, 03:48 PM)

Hmmm... this does not appear to be working on my MS28 drive... I was running 1.2C without any issues.  I flashed the 5x version and now none (even original games) will play.  The 360 thinks that all previously working games, burned or original, are all returning the following error:

To play this disk put it in an Xbox 360 console.

Thankfully I backed up my USB key and going to flash back to 1.2C

I'm having the exact same problem... but after Dazz posted that he also made another post saying he fixed it because he was using the wrong key... but in my case, im pretty sure im using the right key... heres my scenario:
my original dvdrom that came with 360 was samsung ms28 i flashed it and it eventually had to many problems reading anything so i ordered a ms25 and did a swap. flashed it with ixtreme1.2c and havent had any problems till now when i tried to flash to 1.3...

i flashed back my orig.bin then did the hacked.bin.. tried 2x, then 5x... same result.. "to play this disk put it in an xbox 360 console..." even retails give that error...

please help me

[potvin]

QUOTE(potvin @ Nov 13 2007, 07:23 AM)

I'm having the exact same problem... but after Dazz posted that he also made another post saying he fixed it because he was using the wrong key... but in my case, im pretty sure im using the right key... heres my scenario:
my original dvdrom that came with 360 was samsung ms28 i flashed it and it eventually had to many problems reading anything so i ordered a ms25 and did a swap. flashed it with ixtreme1.2c and havent had any problems till now when i tried to flash to 1.3...

i flashed back my orig.bin then did the hacked.bin.. tried 2x, then 5x... same result.. "to play this disk put it in an xbox 360 console..." even retails give that error...

please help me

nevermind.. i flashed my friends xbox month ago.. forgot his orig.bin was on my floppy LoL
my bad.. i flashed with the correct key this time and it works great!

DONT FORGET TO USE THE RIGHT KEY PPL!! DONT BE A NOOB LIKE ME

[caster420]

QUOTE(getRAWed @ Nov 13 2007, 04:12 AM)

Thanks guys, can always count on you.

I've flashed my MS25 with 1.3 (5x), using the Bad-flash method... it's so quiet, and loading times are good too ^^,

Just two more things though... when making the x13.bin file with the Batch tool, I used the ORIG.bin that I got when I first flashed my drive last night to iX 1.2... though this time, nothing was put into the Backups folder on my floppy when using mtkflash w /m /sata command in DOS prompt, so I assume this is all good?

Also, the batch creator said:


----------------------------------------------------------------------------
|      firmtool v1.0 by caster420                                     |
----------------------------------------------------------[360mods.net]-----

 Drive Key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx (I've removed that myself)

 Original Firmware Version: MS25
  iXtreme Firmware Version: MS28

*** SUCCESS ***
Drive key copied.
Drive version spoofed.

Your iXtreme firmware is now ready to be flashed!

***************************************
iXtreme v1.3 firmware created: ix13.bin
***************************************

Firmtool automatically copies your version strings if the original is different from the hacked.  So, it states that, 'Drive version spoofed', thus, it is reporting as a ms25.

Caster.

[kdallas]

QUOTE(Martinchris23 @ Nov 13 2007, 07:18 PM)

This is what confused me - I've never had to use an 0800 disc, even before I got my 6421A PCI card. Any MS25s worked straight away through my Nforce3 chipset - the only snag was when I had an MS28 (IMG:style_emoticons/default/wink.gif)

Yep, sorry 'bout that  (IMG:style_emoticons/default/biggrin.gif)   -- I was talking about the Hitachi and should have used the correct term "ModeB" instead of 0800 disc.  They both do the same thing though - and that is to allow you to mount the drive in Windows.

QUOTE(Martinchris23 @ Nov 13 2007, 07:18 PM)

From my understanding, the quiet mode in 1.2c is 2x in 1.3 - 5x in 1.3 is an excellent compromise.

According to the 1.2b readme it was 4x, but I couldn't find a specific mention in subsequent readme's - so I assumed the choice was still either 12x or 4x.

I'm surprised more people don't choose the 8x option as the noise level is apparently only a marginal increase over 5x.

[getRAWed]

QUOTE(caster420 @ Nov 13 2007, 12:03 PM)

Firmtool automatically copies your version strings if the original is different from the hacked.  So, it states that, 'Drive version spoofed', thus, it is reporting as a ms25.

Caster.

Cool, so it's reporting the model number that the drive actually is ^^,

Thanks for the help caster, and for firmtool.

[caster420]

QUOTE(getRAWed @ Nov 13 2007, 08:12 AM)

Cool, so it's reporting the model number that the drive actually is ^^,
 

 

Yes, its reporting the drive versions before any modification has been done.  iXtreme for sammys will always say MS28 and iXtreme for benq's will always say 64930.  Then your original should state what your drive actually is.

 

Caster.

[rehab]

Hey guys, just a quick question: Could someone clarify the "(v1.3) Improved media detection"?
Does this mean more cheap media supported or does it get rid of dirty-disc errors? I'm having a lot of dirty-disc errors in iXtreme 1.2 with a MS28 (3 months old) and i'm always using Verbatims (burnt @ 2x).

Thanks.

[Martinchris23]

QUOTE(rehab @ Nov 13 2007, 04:07 PM)

Hey guys, just a quick question: Could someone clarify the "(v1.3) Improved media detection"?
Does this mean more cheap media supported or does it get rid of dirty-disc errors? I'm having a lot of dirty-disc errors in iXtreme 1.2 with a MS28 (3 months old) and i'm always using Verbatims (burnt @ 2x).

Thanks.

Are you getting this same error with the originals?

[fabricioss]

I have some questions.

1. What is the Bad-flash method? Can anyone explain in details please?
2. What is the xbox 360 default speed?
3. Currently I have ixtreme 1.2c, do I need the enable 0800 disc?

[gnutellafan]

QUOTE(fabricioss @ Nov 13 2007, 07:23 PM)

I have some questions.
...
2. What is the xbox 360 default speed?
...

I would like to know this as well.