help please

[m9g]

yeah re-started a few times since but good thinking - i will re-burn black ops and try it.

[m9g]

just noticed imgburn i had was 2.5.5 which was released last january and 2.5.6 was released this month, wonder if that has anything to do with it even tho' all settings for 2.5.6 were in 2.5.5

[martiboy]

Got to be worth a try. With blackops and the new ingburn.

[m9g]

Got to be worth a try. With blackops and the new ingburn.

hmm just tried black ops with imgburn 2.5.6 and it wouldnt work, wouldnt even work on my old hitachi - do you think it would matter that the settings for imgburn were still set as in tut above for xgd3? or wouldnt it matter?

[martiboy]

This is starting to sound like a bad flash in your burner. I'm not really sure what to suggest as I don't want you to have any more coaster. Do you still have the imgburn log if so could you post it


Sent from my iPhone using Tapatalk

[m9g]

found it, just noticed in this log it says the disc is mkm003 which would suggest i need opc on, could this be the prob? I know on this one the write speed was set to max which was 8x speed which was the black ops but the previous GOW3 i was trying i set to 2.4x speed as I couldnt see anywhere that the disc was mkm003 so thought best to leave opc blank and set to low writing speed. As Black ops isnt an XDG3 game then thought the opc setting wouldnt matter would it? should I have turned of the settings i.e overburn etc etc that is required for the XDG3 games?

; //****************************************\\
; ImgBurn Version 2.5.6.0 - Log
; Tuesday, 25 October 2011, 22:30:42
; \\****************************************//
;
;
I 21:47:35 ImgBurn Version 2.5.6.0 started!
I 21:47:35 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)
I 21:47:35 Total Physical Memory: 4,176,544 KB - Available: 2,720,036 KB
I 21:47:35 Initialising SPTI...
I 21:47:35 Searching for SCSI / ATAPI devices...
I 21:47:35 -> Drive 1 - Info: ATAPI iHAS124 B AL0S (E (ATA)
I 21:47:35 Found 1 DVD?RW/RAM!
I 21:56:42 Operation Started!
I 21:56:42 Source File: C:\Users\Matthew\Desktop\XB360CBO.dvd
I 21:56:42 Source File Sectors: 3,827,488 (MODE1/2048)
I 21:56:42 Source File Size: 7,838,695,424 bytes
I 21:56:42 Source File Volume Identifier: DVD_ROM
I 21:56:42 Source File Volume Set Identifier: ec67c000MS UDFBridge
I 21:56:42 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM)
I 21:56:42 Source File Implementation Identifier: Microsoft CDIMAGE UDF
I 21:56:42 Source File File System(s): ISO9660, UDF (1.50)
I 21:56:42 Destination Device: [3:0:0] ATAPI iHAS124 B AL0S (E (ATA)
I 21:56:42 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00)
I 21:56:42 Destination Media Supported Write Speeds: 2.4x, 4x, 6x, 8x
I 21:56:42 Destination Media Sectors: 4,267,040
I 21:56:42 Write Mode: DVD
I 21:56:42 Write Type: DAO
I 21:56:42 Write Speed: MAX
I 21:56:42 Link Size: Auto
I 21:56:42 Lock Volume: Yes
I 21:56:42 Test Mode: No
I 21:56:42 OPC: No
I 21:56:42 BURN-Proof: Enabled
I 21:56:42 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x)
I 21:56:42 Book Type Setting: DVD-ROM
I 21:56:42 Advanced Settings - Force HT: No, Online HT: Yes, OverSpeed: No, SmartBurn: Yes
I 21:56:42 Optimal L0 Data Zone Capacity: 1,913,760
I 21:56:42 Optimal L0 Data Zone Method: Copied From Original Disc
I 21:57:50 Set L0 Data Zone Capacity Succeeded!
I 21:57:51 Filling Buffer... (40 MB)
I 21:57:51 Writing LeadIn...
I 21:57:53 Writing Session 1 of 1... (1 Track, LBA: 0 - 3827487)
I 21:57:53 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3827487)
I 21:57:53 Writing Layer 0... (LBA: 0 - 1913759)
I 22:11:55 Writing Layer 1... (LBA: 1913760 - 3827487)
I 22:25:58 Synchronising Cache...
I 22:26:02 Closing Track...
I 22:26:03 Finalising Disc...
I 22:26:36 Exporting Graph Data...
I 22:26:36 Graph Data File: C:\Users\Matthew\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_iHAS124_B_AL0S_25-OCTOBER-2011_21-56_MKM-003-00_MAX.ibg
I 22:26:36 Export Successfully Completed!
I 22:26:36 Operation Successfully Completed! - Duration: 00:29:54
I 22:26:36 Average Write Rate: 4,545 KB/s (3.3x) - Maximum Write Rate: 11,192 KB/s (8.1x)
I 22:30:42 Close Request Acknowledged
I 22:30:42 Closing Down...
I 22:30:42 Shutting down SPTI...
I 22:30:42 ImgBurn closed!

[martiboy]

Ok that log looks ok. The only point I would say is burn at a slower speed than 8x.
Just so that we can work out if its the burner or Xbox that is causing the prob.
1 when you reburned BO did you run the ISO through abgx first to fully patch it.
2 have you tried other games including originals in the box.
3 did you retry flashing the burner.
4 can you post the jf log from when
you flashed lt2.0
5 when you load a blank disk into imgburn what free space does it say you have
It's going to be somthing simple that's causing the prob but finding it could be harder.


Sent from my iPhone using Tapatalk

[m9g]

Ok that log looks ok. The only point I would say is burn at a slower speed than 8x.
Just so that we can work out if its the burner or Xbox that is causing the prob.
1 when you reburned BO did you run the ISO through abgx first to fully patch it.
2 have you tried other games including originals in the box.
3 did you retry flashing the burner.
4 can you post the jf log from when
you flashed lt2.0
5 when you load a blank disk into imgburn what free space does it say you have
It's going to be somthing simple that's causing the prob but finding it could be harder.


Sent from my iPhone using Tapatalk

Yeah ran BO back through ABGX
I tried an old backup of MW2 and that did the same as the old BO picture came up and play game but screen went black and returned to dash
Will try an original when i get home from work this eve
Haven't reflashed burner, will do later, when i flashed it it did do everything as the tut said it would.

Will keep you posted

Appreciate your time

[m9g]

Just a thought, when i created CFW the source I used was the dummy.bin I created over a year ago before I put LT1 on, jf chose the target file itself, just wondering if my dummy.bin shold have been newer after the last ms update?

I ask this because I'm not sure exactly what the dummy.bin is and if JF loads a totally complete cfw on or if the cfw is generated by patching the dummy.bin and re-loading it back onto the drive if its the latter then is it possible the dummy.bin needs to be newer than the one I have.

[martiboy]

Try to reflash your Xbox again but this time do what I said in post 32 and use your old bin file not the new 1 you just made


Sent from my iPhone using Tapatalk

[m9g]

Try to reflash your Xbox again but this time do what I said in post 32 and use your old bin file not the new 1 you just made


Sent from my iPhone using Tapatalk

Hi if you read previous post thats what i did, i used the very first dummy.bin that i created over a year ago when i put lt+1 on. JF then auto loaded LTPLUS-025 and created cfw and thats what i wrote. Thats what i was asking was it ok to use my old dummy coz thats what i did and wondered if i needed to update stock fw then create dummy and use that.

What I thought i'd try when i get home is stick my old burner back in, re-set imgburn back to standard and burn BO again, if it works then that way i'll know if its the burner flash
Regards

[m9g]

Thinking about it when flashing the xbox drive, followed the jf tut and there was only one little bit thats mine didnt do, once the cfw is written to the drive and it verified as good it says click outro/ata

and right at the bottom it says something about key found, lists the key and says verified by c4eva - mine didnt do this bit it just said drive is lite-on

[m9g]

Right I burnt BO on my old drive with all settings put back to normal on imgburn and put in box and piccy comes up in box with play game under it and then black screen

Put an original in the xbox and it plays fine

What does this tell me - not sure :-/

[martiboy]

Well I would rule out any prob with the burner now. Do you have any none ap25 backups to try


Sent from my iPhone using Tapatalk

[martiboy]

Also could you post your jungle flasher log


Sent from my iPhone using Tapatalk