Good burns suddenly unreadable in XBL

PMac10000

Junior Member
Dec 16, 2013
20
0
So suddenly my xgd3 mk003 backups result in the "unreadable disc" error. All these backups were formerly fine, and all installed to my hard disk without problems. Retail discs and Xbox Live titles on HDD are still OK, however.

The backups were burned with Sony Optiarc 5280S-CB-PLUSand Imgburn, with very good results (92+ score on Nero Discspeed), and are all 100% green in abgx360. My Xbox slim has a Demon, and when I boot to the Demon NAND, the backups will run just fine from either 16537 NXE or FSD3... so I would think this would rule out a laser or HW problem.

So what's going on here? Any advice is welcome.
 

PMac10000

Junior Member
Dec 16, 2013
20
0
I will do that if it's required. I was hoping that the description of my symptoms would lead to some helpful suggestions without going to those lengths. My searches for a similar problem + solution haven't turned up anything yet.
 

PMac10000

Junior Member
Dec 16, 2013
20
0
Feels like there's an assumption of "guilty until proven innocent" around here... I don't have the same computer as when I ripped the backups. So I will need to start over. I have the green abxg results, but I don't think it makes a difference.
 

PMac10000

Junior Member
Dec 16, 2013
20
0
OK. Would it be sufficient to create a new backup rip of my retail disc with Imgburn and my Sony Opti-arc AD-5280S (and supply the Imgburn logs?) Otherwise I need to take my Xbox Slim apart to get at the flashed drive and hook it to my PC. Or alternatively, is it acceptable to rip to iso on the Demon side of my Xbox using some utility, and burn that iso in Imgburn?
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
I have the green abxg results, but I don't think it makes a difference.
Post your abgx log then please. It'll be something at least.

Don't be so dramatic. You pay for goods before you receive them all the time. Why don't people just TRUST you'll pay once you get them?
 

PMac10000

Junior Member
Dec 16, 2013
20
0
OK. Sorry. I suppose I was hoping this was a relatively common problem, with a known fix... but apparently not. In the meantime, here is an example abgx log from one of my burned xgd3 backups.
Code:
Checking for updates to abgx360.dat...
     Server file abgx360.dat no newer than local file - not retrieving


Checking Game
     ISO: "Optiarc DVD RW AD-5280S 1.Z8 < Oct24,2012> [ATA] (D:)"
     Layerbreak: 2133520
     Size: 8738865152 bytes
     Files in ISO: 159, Folders in ISO: 8
     Total bytes used: 7567242664 (87.36%)
Game appears to have random padding


Checking default.xex
     Original PE Filename:  madden.exe
     Original PE Timestamp: 2013/07/14 01:59:26
     Min Kernel Required:   v2.0.16202.0
     Game Name:             Madden NFL 25
     No Avatar Awards
     Achievements:          41 Achievements totaling 1000 Gamerscore
     XEX CRC = B0D77B28
     XEX Media ID: CBF9B6B38C51038057FB4847-26607375


Region Code: 0xFFFFFFFF
     Region Free!


Checking topology data
Querying the online database to find the appropriate verified data to use...
     Topology information was downloaded successfully


     Looking for TOP_XGD3-DID-F87A804E_v1.sha1 in the online verified database
     Server file TOP_XGD3-DID-F87A804E_v1.sha1 no newer than local file - not retrieving
Topology data is currently verified


Checking SS
     Timestamp of Authoring: 2013/07/15 00:00:00
     Timestamp of Mastering: 2013/07/24 10:04:27
     SS Version: 2 (trusted)
     SS CRC = B290AE09 (RawSS = 909187F8)
     SS Media ID: CBF9B6B38C51038057FB4847-26607375 (matches game)
SS looks valid


Checking DMI
     Timestamp of Authoring: 2013/07/15 00:00:00 (matches SS)
     DMI CRC = B311CCF8
     DMI Media ID: CBF9B6B38C51038057FB4847-26607375 (matches game)
DMI looks valid


Checking PFI
     PFI CRC = 26AF4C58
PFI matches known data (XGD3)


Video partition found
     Video CRC = 25438526 (V0 = 3E0BE00D, V1 = D1722B69)


Basic Stealth check passed!


Starting Verification
     Looking for B290AE09B0D77B28.ini in the online verified database
     Server file B290AE09B0D77B28.ini no newer than local file - not retrieving


     Using B290AE09B0D77B28.ini (328 bytes)
     Video CRC matches
     V0    CRC matches
     V1    CRC matches
     PFI   CRC matches
     DMI   CRC matches
     SS    CRC matches
     Xex   CRC matches


Checking Game CRC... (press Q to cancel)
 Percent  Elapsed  Estimated   Time     Average     Current     Errors    Total
    Done     Time       Time   Left       Speed       Speed  Recovered  Retries
    100%    18:28      18:28   0:00    7.5 MB/s    4.5 MB/s


     AnyDVD style corruption was not detected
     Game CRC = 5F09ACD4 (matches)


All CRCs match
Verification was successful!


Press any key to exit . . .
 

PMac10000

Junior Member
Dec 16, 2013
20
0
All backups abruptly reported "unreadable" last week, seemingly without any updates or other events (I can't be totally sure, because kids use this console). In any case, I remember this happening once before, after the last dashboard update. At the time, I solved the problem by building a retail NAND from my clean 16203 dump, and that solved it... until now.

Since then I've tried the same approach to fix it, to no avail. The backups run just fine in offline mode after booting to the fresh retail 16537 NAND, but after I install the system updates required by XBL, the "unreadable" error occurs on all backups.
 

PMac10000

Junior Member
Dec 16, 2013
20
0
They work as long as I haven't connected to XBL to download the required 16537 updates (avatars etc). After the update, backups give the dirty disc error, but retail discs and XBL content on HDD work fine.

On the Demon side of the console, backups work fine at all times.
 

PMac10000

Junior Member
Dec 16, 2013
20
0
I am updating from a retail 16537 NAND built using JRunner with Xebuild, with my CPU Key, and matched the CF LDV to the value from Xell's fuseset. Also had selected "Get Latest System Update" in the Advanced menu. Xbox boots fine on the retail side and "System Info" reports it is version 16537.0 ... but it still wants to download a system update before it can connect to XBL. Once it does so, all backups don't work, as I've described.
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Surely the latest update is 16547 now? This is why it's asking for an update.

Is this how you update your console every time? (building retail image etc)?
 

PMac10000

Junior Member
Dec 16, 2013
20
0
Actually, I did not know about the most recent system update. Thanks for letting me know! From what I've read, it appears to be safe for flashed drives however, so I'm still unclear as to why I'm getting the disc errors.

Is there anything I can do to fix my retail NAND after taking the system update to 16547 to fix the problem? Alternatively, is it possible to build a clean retail 16547 NAND?

To answer your question, I usually update the console through XBL, but only after I've determined that it's safe to do so. But this "unreadable" behavior has now occured on the last two system updates... which were done by kids using the console, not me.
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Go through the same process again, but this time extract the files from your existing dump and use with LDV from xell to build a 16537 retail image (build NAND without nanddump). You'll need kv.bin, smc.bin, smc-config.bin and fcrt.bin from the existing image. Let me know what happens.
 

PMac10000

Junior Member
Dec 16, 2013
20
0
OK will do. When you say extract those files from the existing image, do you mean the clean retail 16537, or the updated 16547 (or some other one)? Or does it matter?