LITEON DG-16D4S - SLIM Liteon 2072 unlocked PCB Fast eject and wont read

Chris_S

Full Member
Jan 12, 2012
41
0
Well I've had this PCB for a very long time now and had troubles with it before, originally I thought it was a problem with the other drive so I replaced the laser and drive motor. Neither of those worked so I decided to get a new drive, turns out the drive wasn't the problem and it was the PCB, i've tried directly soldering to the PCB and using the solder less solution and neither changed the results.

So basically it ejects very fast and wont spin up




I'm not new to flashing and have reflashed the PCB several times now.
 

Chris_S

Full Member
Jan 12, 2012
41
0
Have you made sure the ribbon cables are seccured and the clamps are down
Yep both are in good, when I flashed back to stock 9504 fw the disc at least spun which it isn't doing right now but it still wouldn't read. I'm going to pot tweak it here in a little and see if that changes anything. My stock 9504 PCB wont even read any more.
 

doe1200

VIP Member
Feb 21, 2011
460
48
northern ireland
which dash are you on,dash 2.0.13146.0 and up, your drive frimware is changed from 9504 to 0272,cause i see in your post you said you flashed the pcb to stock 9504 frimware
 

Chris_S

Full Member
Jan 12, 2012
41
0
if you are on dash 13146 or higher, you have to flash with 0272 not 9504.Good luck
They both work, I know because I had 9504 on the original and it is on 14719 or what ever the newest one is. I ordered a new PCB so we will see if the PCB is just faulty or something else. But yes I did try 2072 stock
 
Last edited:

djxxx

VIP Member
Mar 20, 2006
331
33
Planet Earth
You cant inject 9504 if ya xbox360 is at 14719...I`m Sure it has to be 0272

This was from Ubers docs...
NOTE: If you have updated to the dashboard 2.0.13146.0 then your fw version will now be 0272. If you have updated to dashboard version 2.0.13599.0 then your drive is now locked and you need to follow the same procedures as the 0225 and 0401 drives.
 
Last edited:

Chris_S

Full Member
Jan 12, 2012
41
0
You cant inject 9504 if ya xbox360 is at 14719...I`m Sure it has to be 0272

This was from Ubers docs...
NOTE: If you have updated to the dashboard 2.0.13146.0 then your fw version will now be 0272. If you have updated to dashboard version 2.0.13599.0 then your drive is now locked and you need to follow the same procedures as the 0225 and 0401 drives.
I can guarantee you it 100% does work. Either way doesn't matter, this PCB has never worked so ill assume it is faulty.
 

Argentum

VIP Member
Dec 13, 2011
388
0
Khobar, Saudi Arabia
The firmware should be 0272 now.

and mention which version of LT+ did you flash

and what type of backups are you using?

for the new LT 3.0 XGD3 games have to be patched with the topology data
 

Chris_S

Full Member
Jan 12, 2012
41
0
The firmware should be 0272 now.

and mention which version of LT+ did you flash

and what type of backups are you using?

for the new LT 3.0 XGD3 games have to be patched with the topology data
I tried 9504 stock, 2072 stock and 2072 LT+ 3.0

Patched game using the newest abgx and burned with an IHAS on mkm-001
 

djxxx

VIP Member
Mar 20, 2006
331
33
Planet Earth
You need to get hold of Verbatim mkm-003 if you can then verify your burn and check again with kprobe 2
 

Argentum

VIP Member
Dec 13, 2011
388
0
Khobar, Saudi Arabia
I tried 9504 stock, 2072 stock and 2072 LT+ 3.0

Patched game using the newest abgx and burned with an IHAS on mkm-001
Its 0272 not 2072.

You know you should patch the topology data with XBC

Then run it on abgx.

Verbatim 003 is the best. I am also using TDK with no problems
 

Chris_S

Full Member
Jan 12, 2012
41
0
You need to get hold of Verbatim mkm-003 if you can then verify your burn and check again with kprobe 2
Its 0272 not 2072.

You know you should patch the topology data with XBC

Then run it on abgx.

Verbatim 003 is the best. I am also using TDK with no problems
I've always used mkm 001 for my xgd3 games. So it isn't the disc and I'm not sure why I would screw with XBC when i'm pretty sure ABGX patches it now. Also this is on a RGH not retail so I'm not to worried about flags.

I'm 99.9% sure it is the PCB, ill update on Monday or Tuesday when I get my new PCB.

Thanks for correcting me on the FW, I don't pay much attention
 
Last edited: