LITEON DG-16D4S - SLIM Status Code error

demon2011

Senior Member
Apr 8, 2011
147
0
Staffordshire, Uk
Seems all hit n miss, i updated my 0225 with my tx pcb and the latest update and no error but i was told its because a 0225 was locked from the start where the 9504 is unlocked and need to update the dash with stock pcb installed. So once updated to the latest dash and the 9504 is locked, won't it be like the 0225.
 
Last edited:

x360ccm

BANNED
Jan 18, 2011
3,616
0
south coast UK
well since the 13599 dash we all no the spi gets locked.this is why we follow the 0225 guide.so if they check for spi lock status then it passes,hence no probs with the 0225 drives with the tx pcb.so in furture updates the 9504 aka 0272 will be the same as the 0225 drives.

all we need to do is return the tx pcb back to stock spi lock it flick the switch.update then reflash.or just wait for new fw if needed.

it's that simple.:rolleyes2:
 

demon2011

Senior Member
Apr 8, 2011
147
0
Staffordshire, Uk
Just another quick question, I followed the Liteon DG-16D4S 0225 (Slim) Unlocked PCB / Pro Kit - Step-By-Step Guide on this forum to get my key and flash tx-pcb with LT+1.92 but when LT+2.0 comes out do i have to click erase in mtkflash 32 before i write or do i just write over. Like i said i'm new to all this.
 

tingedace

VIP Member
Feb 23, 2011
387
0
Scotland
I got caught out with this one today as well, attempting to use a TX PCB to update a slim from 12625 to 13604 (so as to avoid locking the original drive).

So it appears the TX PCB is no use for this job, which is surprising and a bit disappointing even though I don't expect to see many more unlocked 9504 drives whose owners don't play on live.

The solution was to use another drive (kamikaze'd 0225), flashed with stock 9504 firmware. This allowed the stopped update to continue and I was then able to put the original 9504 drive back in flashed with 0272 LT+2.0, still unlocked.

I just thought this was worth documenting in case anyone else is caught out and needs a solution.

Wonder why it doesn't work though!?? Did someone say the SPI locking command is different?