Print

[scooge]

thanks for the mac help.

I had used iburn360 and abgx but wondered if that would work anymore. Sounds like even if I could get the truncate setting right, my burner might flake anyway.

[josh256]

QUOTE

c4eva] The following drives have been tested for ixtreme burner max firmware:
[c4eva] Liteon iHAS124B = baseline model
[c4eva] Liteon iHAS224B = 124 + LightScribe
[c4eva] Liteon iHAS324B = 124 + SmartErase
[c4eva] Liteon iHAS424B = 124 + LightScribe + SmartErase (or = 224 + SmartErase)
[c4eva] Liteon iHAS524B = 124 + LabelTag + SmartErase
[c4eva] Liteon iHAS624B = 124 + LabelTag + LightScribe + SmartErase (or = 524 + LightScribe)

[josh256]

Update:
If you have a Liteon iHASx24B drive flashed with Burner Max the new layer break is 2133520. You must use this layer break in order to burn un-truncated backups. Also note that at this time only Verbatim media seems to pass verification checks in ImgBurn.

Instructions - Flashing iXtreme Burner Max firmware onto a Liteon iHASx24 on a Mac:

At this time, Windows is required and this can easily be performed from within a VM. I have 1x iHAS124B installed within a NextStar DX USB 2.0 5 1/4" external enclosure and 1x iHAS324B installed internally within my Mac Pro using a Jmicron-based SATA to USB 2.0 adaptor wired into a rear USB port and have flashed both drives without issue. The process takes all of 3 minutes (not including installing VMware Fusion and Windows XP).

Using a SATA to USB bridge pass your Liteon IHASx24 drive to a Windows VM within Fusion 4 (I used Windows XP Pro, 32-bit). Within the VM follow the max burner packaged instructions on updating the drive to the latest Liteon firmware *before* updating the drive to Burner Max. You will also need to reboot the VM and cycle the power on the Liteon between the two firmware updates.


Instructions - Burning with LT+ 2.0 Burner Max on a Liteon iHASx24 on a Mac:

Using the virtualization method described above to run ImgBurn on Windows is the arguably the best method at this time since ImgBurn verifies the disc after burning. This is very important with Burner Max since you are writing beyond the originally intended outer perimeter! Be sure to use ImgBurn 4.0.1 (474597) or later (aka "SetupImgBurn_2.5.6.0.exe" which is included in the Burner Max package).

Other options - Assuming you have an iHASx24B flashed to burner max and don't want to use a VM:

OSx360 supports the layer-break field but forces the -dvd-compat flag which conflicts with the new layer break. Respectively command-line use of growisofs will be necessary. I will post the correct command later tonight after I confirm a couple backups to be 1:1 verified against the original iso (using ImgBurn within Fusion to verify!). It is also possible a new version of IsoBurn will be released to support the new layer break in place of truncate.

[josh256]

Burning an un-truncated XGD3 backup in OSX using Burner Max:

The following command will burn an LT+2.0 XGD3 backup to a burner max flashed iHASx24 (un-truncated):

CODE

growisofs -use-the-force-luke=break:2133520 -speed=2 -Z /dev/rdisk5=/Backups/backupFilename.iso

Note:
- Change drive and filename accordingly
- speed 2 is the same as 2.4
- I have not tested burns @ 4X
- Have verified 2 backups in ImgBurn using this method

See first post for more on growisofs

[lelik11a]

Tried to burn on traxdata dvd (media id RITEK/S04), burned fine, but verified only to 47%.
Tried same to burn same dvd in imgburn in windows (bootcamp), burned fine and verified 100%.

[josh256]

One test in each environment with media known to fail verification proves nothing beyond your media doesn't support over burning reliably (as was already known).  Multiple tests in a single environment with media known to pass verification would a good use of time.

Before anyone else posts their results:

1) If you don't believe my posts re: Verbatim please read c4eva's numerous posts on the subject. Verbatim is the *only* media that verifies at 100% consistently.

2) Read the label on your media --> if it doesn't say "Verbatim" please don't post your results here - start another thread for "flaky alternatives to verbatim" or something

[Pandoriaantje]

QUOTE(josh256 @ Oct 24 2011, 05:31 AM)

Burning an un-truncated XGD3 backup in OSX using Burner Max:

The following command will burn an LT+2.0 XGD3 backup to a burner max flashed iHASx24 (un-truncated):

CODE

growisofs -use-the-force-luke=break:2133520 -speed=2 -Z /dev/rdisk5=/Backups/backupFilename.iso

Note:
- Change drive and filename accordingly
- speed 2 is the same as 2.4
- I have not tested burns @ 4X
- Have verified 2 backups in ImgBurn using this method

See first post for more on growisofs

No need for ImgBurn to verify.

CODE

$ md5sum xxx.iso
$ echo count=$(( $(ls -l xxx.iso | awk '{ print $5 }') / 2048 ))  //to output sector range
$ dd if=/dev/sr0 bs=2048 count=yyy | md5sum           //to rip sector range from disc, and verify (yyy is sector count output for above command)

md5sums should match.

[josh256]

The verification offered by ImgBurn's .ibg exports and DVDInfoPro goes a lot further to prove which discs/brands have safe angles.. meaning: Using crappy media that has passed an MD5 check could still be detectable by M$..

If you stick to Verbatim the MD5 is perfect though, thanks -

J

[barfly126]

I'm burning with OSx360 using your settings the DVDs seems to be ok but when I putt them ino my xbox. they crash. Any idea of what's going on ?

[josh256]

I'm guessing you haven't read all the posts in this thread but in short:

OSx360 no longer works w/ the new layer break, which is needed for untruncated backups, which is forced by the latest dash update (which I'm assuming you've applied otherwise most truncated ISOs should work).

W/ regards to the original post on OSx360:
I'd update the original post but for some reason xbox-scene has chosen to completely prohibit edits after ~1 day.

This post has been edited by josh256: Oct 31 2011, 09:54 PM

[josh256]

barfly126:

One other thing this could be is spoofed xbox 360 replacement drives which will not support AP2.5 backups (all XGD3 backups are AP2.5 so far)

Symptom:
When attempting to launch any AP2.5 backup (incl. but not limited to an XGD3 backup) you will get something similar to a blinking RRoD and you will have to restart your console.

Cause:
You do not have your original DVD-ROM installed, have had it replaced by a different drive model and have the replacement drive spoofing your original drive/firmware. EG: Samsung MS28 spoofing a Hitach 78, etc..

Workaround:
If so you will need to revert your current drive's firmware to non-spoofed (EG: reflash to LT+ 2.01 Samsung MS28, not spoofing the Hitachi) and manual import your original drive's key (which can be acquired via a dump of the current "bad" firmware if you have misplaced the original dummy or key bins).

[DQB]

There's a new isoburn out that seems to support the layer break and stuff fine.



I'm using a flashed ihas324b with the mkm0003 discs (or whatever it is exactly) and they say to burn at 4x with those you need OPC on.  I tested burning a game with isoburn at 4x and it worked on my Xbox but some of the video intro/cutscene things were a bit jerky.  Haven't tried the same game with imgburn but other games I've used imgburn for haven't had any problems.


What I'm wondering is if it's ok to use isoburn when it doesn't have that OPC setting that's recommended on imgburn?  Could not using OPC cause problems loading the disc?

[akula169]

I created a shell script (bash) that automates all of this on the command line.

It's beta - so use at your own risk!  I cannot commit to supporting the code.

But I coded it to be safe, it creates a working copy for all changes - leaving the original ISO untouched.

Requires abgx360-1.0.6 OSX package to be installed, as well as the Binaries package at the top of this thread.

Save the script as whatever filename you'd like, in the same directory as the the binaries you just downloaded. The only argument it needs is the original iso's filename. The script will automatically detect your burner (but only if there is blank media in it)

process.sh:

CODE

#!/bin/sh
TSIZE="8547991552"
LAYERBREAK="2086912"
BURNSPEED="2" # or 4

TEMPISO="working.iso"

SCRIPT="$0"
PWD=$(pwd)
EXEDIR=${0%/*}

if [ ! $1 ]; then
   echo "usage: $SCRIPT "
   exit 0
fi

ISO="$1"
if [ ! -f $ISO ]; then
   echo "error: $ISO does not exist"
   exit 0
fi

#check file copy
if [ -f $TEMPISO ]; then
   ZI=$(stat -f "%z" "$ISO")
   ZT=$(stat -f "%z" "$TEMPISO")
   if [ "$ZI" -eq "$ZT" ];  then
      SKIP=1
   fi
   if [ "$ZT" -eq "$TSIZE" ];  then
      echo "! working copy exists and is truncated - most likely abgx has already repaired the topology info."
      echo "?force new working copy and abgx check? [Y/n]"
      read a
      if [[ $a != "Y" ]]; then
         SKIPABGX=1
         SKIP=1
      fi
   fi
fi

if [ ! $SKIP ]; then
   echo "> making duplicate working copy ($TEMPISO)"
   EXE=$(which rsync)
   if [ ! -x $EXE ]; then
      echo "! could not find rsync"
      exit 0
   else
      $EXE -v --progress $ISO $TEMPISO
   fi
else
   echo 'working copy exists, skipping duplication'
fi

if [ ! $SKIPABGX ]; then
   #abx check (repair)
   EXE=$(which abgx360)
   if [ ! -x "$EXE" ]; then
      echo "! could not find executable (abgx360)"
      exit 0
   else
      $EXE - -- $TEMPISO
   fi
else
    echo 'skipping abgx verify/patch'
fi


#truncate
EXE="$EXEDIR/truncate"
if [  ! -x $EXE ]; then
   echo "! could not find executable ($EXE)"
   exit 0
fi
ZT=$(stat -f "%z" "$TEMPISO")
if [ "$ZT" -eq "$TSIZE" ]; then
   echo '>skipping truncate, already done'
else
   echo "#original size: $ZT"
#   echo "truncate size: $TSIZE"
#   echo "truncate? [Y/n]"
#   read a
#   if [[ $a == "Y" ]]; then
      $EXE $TEMPISO $TSIZE
      echo '>truncating...'
      ZT=$(stat -f "%z" "$TEMPISO")
      echo "#new size: $ZT"
#   else
#      echo 'user break'
#      exit 0
#   fi
fi

#check media
EXE="$EXEDIR/dvd+rw-mediainfo"
if [  ! -x $EXE ]; then
   echo "! could not find executable ($EXE)"
   exit 0
fi

#check for burner and blank disc
for i in `seq 1 10`;
do
   DVD="/dev/disk"$i
   DVDSTAT=$($EXE $DVD 2>/dev/null)
   if [[ $DVDSTAT =~ "INQUIRY" ]]; then
      BURNER="/dev/rdisk"$i
      echo "found burner at $BURNER"

      if [[ ! $DVDSTAT =~ "Double Layer" ]]; then
         echo 'media is not DVD-DL'
         exit 0
      fi
      if [[ ! $DVDSTAT =~ "blank" ]]; then
         echo 'media is not blank'
         exit 0
      fi
   fi
done

if [ ! $BURNER ]; then
   echo 'error: no DVD burner or no blank media in drive'
   exit 0
fi

#burn it!
EXE="$EXEDIR/growisofs"
if [  ! -x $EXE ]; then
   echo "! could not find executable ($EXE)"
   exit 0
fi

echo "burn? [Y/n]"
read a
if [[ $a == "Y" ]]; then
   echo ' burning'
   CMD="$EXE -use-the-force-luke=dao -use-the-force-luke=break:$LAYERBREAK -dvd-compat -speed=$BURNSPEED -Z $BURNER=$TEMPISO"
   echo $CMD
   $CMD
   echo 'Done Burning!'
else
   echo 'user break'
   exit 0
fi

echo "remove temporary working ISO? [Y/n]"
read a
if [[ $a == "Y" ]]; then
   rm $TEMPISO
   echo 'working copy iso removed!'
else
   exit 0
fi

echo 'Done!'

[josh256]

I would advise against truncating. Unless you are aware of the risks/constraints and/or don't have a Liteon iHASXXX burner w/ Burner Max the process should be as follows (As of LT+ 3.0):

1) Run ABGX 1.0.6 to verify the backup (and patch topological data if needed)

2) Burn w/ growisofs using a Liteon iHAS DVD writer flashed w/ Burner Max firmware


Detailed LT+ 3.0 Mac Tutorial