Abgx not recognizing iso

Thank you eisherz, that is probably the reason for Batman not read by abgx.
Still doesn't explain why Darkness (correctly read by abgx and burned at 4x with iHas 124) cannot be read by the console. In the dashboard it says "Reading...", I hear the console trying to read the disc, but after a while it only says "Open tray". Originals and older backups are read correctly. As soon as possible I'll check the disc with Probe as soon as possible, but imgburn verified it correctly.
Thanks again, anyway, I really appreciate all the help.

 

@Eisherz, you're right, I've been out of the scene for too long to even recognize what people are burning their games at now! Even when I have Imgburn set to 2.4x, my burner shows that it's going faster then 4x. So I apologize for my false info!

 

It's the write strategy for the particular type of media you're using that dictates the burn speeds you're offered.

That's why you end up with loads of people reading out of date guides that say "burn as slow as you can!" or "burn at 2.4X and no faster!", but when they set ImgBurn to 2.4X it will push the burn speed up to 4X as that's the slowest speed that particular media can be burned at with that particular burner and firmware combination.

A couple of years ago there was a guy on here trolling loads of threads telling people they were idiots for burning faster than 2.4X. He wouldn't listen to anything anyone said, so I contacted Verbatim and their quality manager got back to me with this response: -

It still didn't shut the troll up though, cos he said that even the guy from Verbatim was wrong, lol, but he got banned shortly afterwards anyway.

 

I finally did KProbe test. Has huge max (PI MAX 199 and PI MAX 6), but the average look fine(PI 3,76 and PIF 0.18).
Here is the result: . Hope it means something to you

 

Did you do the topology patch (spelling might be wrong, sorry if it is). You said you use ABGX, so I think you have, but it's still worth asking.
Other than that the only other problem I could think of is your laser going bad.

 

Sorry, I'm not English and I may be losing something. Feel free to correct or ask if something is unclear
Anyway, yes, I've used abgx. Is that the topology patch you mean? Or is there something specific I need to activate?

 

Use this guide created by funksoulb to make sure your settings are correct

abgx360 1.0.6 setup and user guide

 

Yes, thank you, but I've used it and it was set correctly. Running abgx again gives all greens, so it is probably alright. Does my Kprobe2 look fine to people who understand it?

 

That KProbe result is great apart from the spike at the layerbreak, but I highly doubt that the spike is enough to cause the console not to even recognise the game and the spike isn't even that bad.

If it was the topology data that's missing/incorrect, then the game would be recognised by the console - it just wouldn't boot - and you've already said that you get all green in abgx360, so it can't be that.

I think that only leaves us with 2 things: -

1. The drive isn't flashed with LT+ 3.0 after all, and is flashed with an earlier version.
2. It's a drive/laser issue of some kind.

EDIT - Just how many XGD3 backups have you tried? Ones that check out all green in abgx360 I mean? Have you got a friend with a flashed 360 so you can try some of their backups, and maybe they can try yours?

 

For the moment I have just 1 xgd3 original game with me (Darkness II) and the flash of Batman that I got before coming to UK.
Darkness II is giving this problem and with batman I made the mistake to patch the wave. I'll give next week darkness II to my brother and he'll let me know.
Happy to know that the disc is fine; I'll reflash the console and if there is still this problem, I'll change the laser or the reader (my brother is sending me his old Samsung, so I'll try to mount it on my console).
Thank you to everybody, really, i appreciate a lot all the help. Please let me know if anything else comes up to your mind in this situation.

 

I would definitely do some more testing before swapping out hardware. Also, if you flashed the console yourself with LT+ 3.0 and are sure you used the correct firmware, I wouldn't bother reflashing it without doing more testing either.

What you need to do is try some more XGD3 backups - preferably ones that definitely work on a friend's console. If you always get the same result, then I would try a reflash (making sure you get the LT+ 3.0 firmware files from a trusted source), and if you still have no luck then I would then either recalibrate the laser or swap out the drive/laser.

 

Problem is I wouldn't know who to ask (not many people with a 360 where I live and work ). I'll buy new XGD3 on ebay and ask somebody reliable to make the copy in order to do more testing. I'll also wait for my brother to let me know about the Darkness disc (he's in italy, so will take a while before my parents give him everything after coming here this weekend), if it works on his console, so this should also say if it is a problem of the reader or of the disc.