Print

[Martinchris23]

QUOTE(rehab @ Nov 13 2007, 10:00 PM)

Well, I basically flashed it out of the box so 1.2c was the first flash. Having problems with backups since the beginning (2-3 months or so).

Run your disks through either Xbox Backup Creator or XDVDMulleter and make sure they are stealth patched. As a thought, if you have any which work fine, then do the same for these and compare the results.

[linnx88]

QUOTE(caster420 @ Nov 13 2007, 11:17 PM)

Yup - just put ix13.bin in the folder with mtkflash and all is good.  Just make sure not to proceed with flashing if there is an issue with the 'Make iXtreme Firmware' command.

Caster.

No no probs with the batch after I moved it to my C:\ drive....doesn't work from desktop or my documents, path too long.

[dvandriesen]

commodore4eva you are the best your work is greatly appreciated here.  FLashing these drives is getting so much easier for me did my ms28 and it took a few minutes great up 5x works great for me

[TorchMach1]

QUOTE(caster420 @ Nov 13 2007, 05:17 PM)

Yup - just put ix13.bin in the folder with mtkflash and all is good.  Just make sure not to proceed with flashing if there is an issue with the 'Make iXtreme Firmware' command.

Caster.

For some reason using the Make Ixtreme batch file doesn't copy over my drive key.  When i open the newly created ix13.bin file with FWToolbox, the key comes up as all F's.  I manually inserted the key with FWToolbox into the ix13.bin fiile, flashed, and it works.  Just seemed odd to me.  Any insight?

[kdallas]

QUOTE(TorchMach1 @ Nov 14 2007, 09:06 AM)

For some reason using the Make Ixtreme batch file doesn't copy over my drive key.  When i open the newly created ix13.bin file with FWToolbox, the key comes up as all F's.  I manually inserted the key with FWToolbox into the ix13.bin fiile, flashed, and it works.  Just seemed odd to me.  Any insight?

If you see all FF's as the drive key then you are seeing the default plain filler key as stored in ix13.bin

That is OKAY if all you are doing is using iPrep to make the batch files and mtkflash up for your boot disc.

But if you simply flash the same unalterted ix13.bin to your drive, then you will erase your unique key.
Just make sure that you've run the iDump batch file before doing anything else so you have a backup.

In fact I'd suggest dumping out a backup anyway so you can compare the key within it to what you've already backed up.

I listed out which tools I use earlier on in this thread..  perhaps go back to the first couple of pages and read through to get up to speed.

[caster420]

QUOTE(TorchMach1 @ Nov 13 2007, 07:06 PM)

For some reason using the Make Ixtreme batch file doesn't copy over my drive key.  When i open the newly created ix13.bin file with FWToolbox, the key comes up as all F's.  I manually inserted the key with FWToolbox into the ix13.bin fiile, flashed, and it works.  Just seemed odd to me.  Any insight?

Did firmtool actually run?  If so, did it error out? Sounds to me like it didnt run to me.  Rerun the command again and see what it says.  If it can't execute the command, move the folder closer to the root of your filesystem.  This has been stated several times already.

Caster.

[TorchMach1]

QUOTE(caster420 @ Nov 13 2007, 07:50 PM)

Did firmtool actually run?  If so, did it error out? Sounds to me like it didnt run to me.  Rerun the command again and see what it says.  If it can't execute the command, move the folder closer to the root of your filesystem.  This has been stated several times already.

Caster.

Yep, you were absolutely right!  Sorry, I feel foolish now!  I dropped the folder on my C drive and it ran successfully.  Curious though, is there any difference between the firmware generated (correctly with the batch file) and just grabbing the fw file and inserting the key?  The method I used seemed to work.  It ran both originals and backups.

[kdallas]

QUOTE(TorchMach1 @ Nov 14 2007, 10:08 AM)

Curious though, is there any difference between the firmware generated (correctly with the batch file) and just grabbing the fw file and inserting the key?  The method I used seemed to work.  It ran both originals and backups.

Caster's probably already on top of answering this already... but just thought I'd say both "methods" are fundamentally the same.  The batch files simplify the process, like a "wizard" and achieve exactly the same result as doing it manually with samtool or x360sam.  So if you did it manually, nice job

[kdallas]

QUOTE(bmcclint @ Nov 14 2007, 10:32 AM)

Quick question...I've been out of this for a while...My 360 has an older 5.3d version of the bios on it.  Any advantages of upgrading to the new iXtreme series or does the old adage...if it ain't broke don't fix it apply?

Some may disagree with me...  however I feel that you should definitely update it.  The thing is if you always use properly stealthed "backups" then you should in theory be able to stay with the old firmware indefinitely.  But the new firmware does have the smarts to prevent bannings and more importantly it won't boot improperly burned non-stealth discs.  It costs nothing but a little of your time - so why not do it anyway?

[caster420]

QUOTE(TorchMach1 @ Nov 13 2007, 08:08 PM)

Curious though, is there any difference between the firmware generated (correctly with the batch file) and just grabbing the fw file and inserting the key?  

For samsung firmware, there is no difference - either should work.

Caster.

[SwivZero]

Anyone done a thorough speed comparison between 2X/5X/8X/12X?  

I flashed the 5X firmware tonight.  Afterwards Mass Effect seemed a bit choppy, and occasionally paused for a second and said "loading".  I can't be sure whether I'm just forgetting what it was like before (with the standard 12X firmware) or if it really is significantly worse.

The only info so far is this:

QUOTE(kimnkk @ Nov 13 2007, 12:24 AM)

I did a test and in Mass Effect, the 8x loaded my level in 17 seconds whereas the 5x took 26s.

I wonder how the 8X compares to the 12X.

[kdallas]

QUOTE(SwivZero @ Nov 14 2007, 03:39 PM)

Anyone done a thorough speed comparison between 2X/5X/8X/12X?  
I wonder how the 8X compares to the 12X.

I have done some theoretical comparisons if that helps...

It might seem obvious but the loading times should correspond exactly to the data transfer rate.
For example a previous post said:
"8x loaded my level in 17 seconds whereas the 5x took 26s."

Well that would be consistent, so we should expect 12x or 2x to take roughly the same time per the transfer rate that is averaged at those speeds (in RPM's).

For example... 5x = 6750KB/s... X 26 secs and / 1024 = 171.4MB

Similarly...  8x = 8100KB/s... X 17 secs and / 1024 = 179.3MB

Therefore...  (171+179)/2= average 175MB X 1024 and / 12x (16200) = 11 seconds.


So we can see the same amount of data being transferred in 11, 17, 26 secs with a direct correlation with the multiplier.  Be interesting if you could test the same level load time at 12x and prove me right or wrong  

[kdallas]

QUOTE(kdallas @ Nov 14 2007, 08:21 PM)

Similarly...  8x = 8100KB/s... X 17 secs and / 1024 = 179.3MB

aaargh.. I'm tired..

should read:
Similarly...  8x = 10800KB/s... X 17 secs and / 1024 = 179.3MB


anyway... here's a simplified table:

multiplier / tx rate / time (sec) / data (MB)
2 ..   2700   ..      66  ..   175.3
4 ..   5400    ..    33  ..   175.3
5 ..   6750        ..    26  ..   171.4
6 ..   8100     ..    22   ..   175.3
8 ..   10800    ..    17    ..   179.3
12 ..   16200   ..    11    ..   175.3

[linnx88]

QUOTE(kdallas @ Nov 14 2007, 01:09 PM)

aaargh.. I'm tired..

should read:
Similarly...  8x = 10800KB/s... X 17 secs and / 1024 = 179.3MB
anyway... here's a simplified table:

multiplier / tx rate / time (sec) / data (MB)
2 ..   2700   ..      66  ..   175.3
4 ..   5400    ..    33  ..   175.3
5 ..   6750        ..    26  ..   171.4
6 ..   8100     ..    22   ..   175.3
8 ..   10800    ..    17    ..   179.3
12 ..   16200   ..    11    ..   175.3

I'll be going with 8x definitely...seems like the best compromise.

[cardboardbox]

I flashed the 8x 1.3 but when I test Bioshock it seems to be skipping (perhaps it cant read the disc or cant read it fast enough) during the opening cutscene.  I didnt have this problem with 1.2 (not the quiet one).  Should this be happening or should I try 12x?  Or should I go back to 1.2.