LITEON DG-16D4S - SLIM Status Code error
- Thread starter demon2011
- Start date
Right so now i've updated to 13599 dash and its updated my drive to 0272, so even though i flashed the tx pcb before the update to lt+ 1.92 it should be ok. Am i right.
Well if thats the case i'm going to have to reflash as when i flashed the tx pcb it was still a 9504.
they didn't do a 9504 1.92 fw tho??
just be on the safe side - flash the TX PCB with the LTPlus-0272-v1.92.bin
just be on the safe side - flash the TX PCB with the LTPlus-0272-v1.92.bin
Last edited:
Oh i'm lost here, i'll start again.
This morning my brothers 9504 slim was on stock firmware, i connected it and fired up jungleflasher and got the dummy.bin then toook the orig pcb out and connected the tx pcb and i writed the lt+ 1.92 to it. I then went to update to latest dash but got error so i reconnected the orig pcb updated to latest dash and now have the tx pcb connected to the slim.
So do i or do i not need to reflash the tx pcb.
Very new at this and just trying to get my thick head around it all.
This morning my brothers 9504 slim was on stock firmware, i connected it and fired up jungleflasher and got the dummy.bin then toook the orig pcb out and connected the tx pcb and i writed the lt+ 1.92 to it. I then went to update to latest dash but got error so i reconnected the orig pcb updated to latest dash and now have the tx pcb connected to the slim.
So do i or do i not need to reflash the tx pcb.
Very new at this and just trying to get my thick head around it all.
Last edited:
that's ok.......
so u did a full dump and read the key..........put all the LT firmware in jungleflashers firmware folder, and then wrote all that to the TX PCB?
If so, JF will have picked up the right firmware and you're good to go
so u did a full dump and read the key..........put all the LT firmware in jungleflashers firmware folder, and then wrote all that to the TX PCB?
If so, JF will have picked up the right firmware and you're good to go
is this 100% true as people performing a system update for 9504/0272 drives with a tx pcb with stock firmware on get an error code and untill the original stock pcb is in cannot update. then they put the tx pcb in after updating. so the spi lock on tx pcbs are not the same as MS stock pcb spi lock.you don't need to hot swap after this....unlock TX PCB....flash stock fw......lock PCB.....update dash......unlock PCB....flash CFW......lock PCB
remember - m$ wont change the SPI again....only check it
but the lock only happened on 13599 which is the latest update which is where the errors come from...lol
so on the next update it'll be fine....
so on the next update it'll be fine....
but new updates will have to check that 9504's are spi locked so no updating with a tx pcb on stock fw?
oh dear i can't get my point across today lol thanks for the replys though.
even if they updated there stock 0272 drive and it's spi locked at some point a new system update will hit and if they update with a tx pcb with stock fw the update will fail hence what i have been saying for last few posts about the annoyance of hot swapping. each new system update after 13599 will check spi status on 9504/0272 pcbs.
even if they updated there stock 0272 drive and it's spi locked at some point a new system update will hit and if they update with a tx pcb with stock fw the update will fail hence what i have been saying for last few posts about the annoyance of hot swapping. each new system update after 13599 will check spi status on 9504/0272 pcbs.