firmware update

[pkphilip]

i have the liteon 16dg2
it has firmware ixtreme 1.6 on it and i need to update this
the tutorials assume you are doing this from scratch
i have the dvdkey and just need to update
when i try to follow tutorial i get bad serial data when trying to get dvdkey
is this because it is not original firmware
i have the ck3 lite serial com with probe
the drive is recognised in jungle flash
help
philip

 

[tonyjandc]

please post a copy of jungle flasher log then we can take it from there

 

[jsinger47]

If you have 1.6 on the drive, just use "dummy from ixtreme"

 

[pkphilip]

have tried to load dummy from ixtreme
error message tray is not half open
is this connected with the bad serial data when you try to extract the key
should you be able to extract key with firmware 1`.6
many thanks for your interest and help
philip

 

[jsinger47]

If dummy from ixtreme doesn't work its not 1.6 fw. Buy a probe 3 or make a pmt and use phatkey

 

[pkphilip]

hello again
its def firmware 1.6 i put it there
and i am using the probe 3
regards
philip

 

[Goldensavage]

What point are you probing???????

Because if you put 1.6, the old probe point was R707.

Now with the probe 3, it is MPX01.

Can you post a pic of your probe?

 

[pkphilip]

i have tried probing both points
the probe is the original that came with the ck3 lite serial
its2-3 years old
as i flashed this myself and have not done any since i cannot remember the exact procedure
i have tried connecting to the original motherboard i used and at the time jungle flasher was v1.66
jungle flasher recognises the lite on drive but returns bad serial data when you try to extract the key same as current setup
how critical is the tray half open
i am ejecting with button on ck3 tray fully open turn off ck3 press eject switch again re power then push try half way in
i still have the original lite on files for key enquiry can i import these
regards philip

 

[FlashDrive360]

i have tried probing both points
the probe is the original that came with the ck3 lite serial
its2-3 years old
as i flashed this myself and have not done any since i cannot remember the exact procedure
i have tried connecting to the original motherboard i used and at the time jungle flasher was v1.66
jungle flasher recognises the lite on drive but returns bad serial data when you try to extract the key same as current setup
how critical is the tray half open
i am ejecting with button on ck3 tray fully open turn off ck3 press eject switch again re power then push try half way in
i still have the original lite on files for key enquiry can i import these
regards philip

i the original that cam with the ck3 then the chances are its not a probe 3

 

[axee44]

I don't get what is the hassle here??
If OP already has the key why insisting on extracting it again??
If it is dummy.bin just use that as source file - or if you have written down as set of numbers just use manual spoof in jf. Or am i missing something here??

Edit: i suggest using "Possibly flashed this drive before on this pc? Click HERE" on page 85 in jf tutorial.

 

[RepairBucks]

As long as you know the key you already have is correct, which it sounds like it is, then erase the firmware and write 3.0 to the drive.

Probe isn't necessary in this situation.

 

[pkphilip]

followed instructions managed to load dvdkey and source destination firmware
tried to erase got intro read failure
now ck3 will not recognise the drive and the eject no longer works
thanks for previous help where to now
many thanks philip

 

[axee44]

Have you plugged dvd power cable upside down?
Can you post jf log?

 

[hilly360]

do what u been doing, load target and source. click spoof source to target (just to make sure keys match).

then follow this step by step from step 10. - http://www.team-xecuter.com/forums/showthread.php?t=66257



once you get to step 10 click yes and turn ck3 off and on straight away within a second.

you may have erased fw thats maybe why drive cant be seen in jf.

 

[pkphilip]

many thanks for all the advise given
the drive has now been successfully updated
and the xbox360 is now working fine again