Print

[zidanej]

So I tried using dosflash without the hacked.bin file since I don't think I needed it yet anyway.  I got an invalid dvdkey error on both of my computers so I'm guessing that the serial port is not the problem.  What's weird is that probe started acting up again.  It continually flashes green without touching anything.  I have a feeling that I got a faulty probe and I'm gonna look around the forums on how to make my own but any help/input about making a probe or my dosflash errors would be greatly appreciated.

My inquiry and identify bins go through without a hitch so according to the guide I believe my sata stuff is fine.  Once it hits the key.bin part I'm guessing it errors out but I just bought this new serial cable and I don't think both of my computers would have a faulty serial port so I'm thinking that it's the probe.

Another weird thing is that the dosflash error pops up around 1-3 seconds after I hit enter to read the key.  I know that with dvdkey32 and cktools or whatever the key read would take quite a long time before it would give me an error.  Is it supposed to read it that fast and realize that there's an error?

[JamieThompson]

hacked.bin is the iXtreme firmware for your drive. Looks like I chopped that line out! Ill get that edited soon. Thankyou! you then patch hacked.bin using dummy.bin in firmtool which updates the hacked.bin and then you flash with hacked.bin. So you will need it later on. But for the keys:

If your doing it in windows porti/o drivers wont work on 64bit xp. But if your running 32bit on a 64 processor that should be fine!

& try following the guide again for reading your key. Ive wrote a paragraph about why you might get those errors and how you might fix them its at the end of the key read information. (use dvdkey in dos -but dont use the files created by dvdkey. If that works you know its just software problems. dvdkey is that fastest way as you simply type dvdkey portnum . If that works, without remving probe run dosflash liteon k . Fully explained in the guide)

[zidanej]

So I just gave DOS a try with both my 32 bit processor computer and 64 bit processor computer and this is how it turned out:

32 bit:
Dosflash returns: Germia's DVD Key method failed
DVDkey returns: Error in sending CDB

64 bit:
Dosflash returns: DVDkey is invalid
DVDkey returns:
It didn't work, sorry           sega: 54
Nothing received from COM port

So basically, I was wondering what CDB and sega: 54 means.  Looks like the COM port in my 64 bit computer might be busted but I'm still not sure.  Also my ck3 probe is still continuously green even when it is touching nothing, is something wrong with it?

[JamieThompson]

Boot into dos with CK3 turned OFF.
Turn CK3 on and eject drive using onboard switch.
Turn CK3 off (without closing drive)
Push drive tray half way closed
Turn CK3 on
Type dosflash
drive number
liteon k -name id/iq/key/dummy files.
If you get bad dvdkey - straight away type
dvdkey sataport( sata port is listed in dosflash when selecting deivce should be 4 characters e.g. ff00)

if this works go back into dosflash without removing probe! and run liteon k.

Its important to have your drive tray correct. & you must have txd connected. So check r707. Make sure your spear is plugged in correctly.

Keep running dvdkey and you should get a response.

And keep probe connected during key read.

[matt_cooper_1987]

try using a screwdriver to bridge the r707, its always worked fine for me, had trouble with the probe working, bad connection save you using the probe!

[naiku]

QUOTE(zidanej @ Jan 14 2009, 09:42 AM)

Thanks for the input but I've tried that and another way.

1. Turn on ck3, eject, turn off ck3, push halfway in, turn on ck3, read key

I was having issues for the past 3 hours with dumping a zero key.  I tried the quoted method. First attempt it came up w/ a good key.

I am using CK3 Pro w/ JungleFlasher 0.0.26 Beta windows xp. Thank you so much for that alternative to the Official tutorial which kept failing me.

edit: sorry for bumping a month old topic but it worked like a beauty.

[joliverio]

QUOTE(naiku @ Mar 3 2009, 12:26 PM)

I was having issues for the past 3 hours with dumping a zero key.  I tried the quoted method. First attempt it came up w/ a good key.

I am using CK3 Pro w/ JungleFlasher 0.0.26 Beta windows xp. Thank you so much for that alternative to the Official tutorial which kept failing me.

edit: sorry for bumping a month old topic but it worked like a beauty.

Another important detail is that ALWAYS keep your probe connected before powering on CK3, I only could get my (perfect) key after realize that you must keep the probe connected into R707 before powering on CK3, keep it in this position and get the keys using any extractor software. If you can get the key using one method should work with any other methods, try to get your keys using as much applications you have and later compare the results under DOS
Also a "mandatory" suggestion is to check the files "dummy.bin", "identify.bin", "key.bin" and "inquiry.bin" that you got using ALL methods available (Windows and DOS) and compare the results to make sure that your key is (at least) the same using all methods. I used the suggestions from "Im-rick-james-b1tch Method" [ http://forums.xbox-s...howtopic=673927 ] that, besides the full extract and flash method, explains how to compare Under DOS the results you got with Win and DOS methods, using the command (under DOS) “fc.exe /b FILE_GET_FROM_METHOD_A.bin FILE_GET_FROM_METHOD_B.bin” for example “fc.exe /b inquiry_FROM_METHOD_A.bin  inquiry_METHOD_B.bin”, If you get the result "FC: no differences encountered" means the extract files from different applications are exactly the same and the chance to make a mistake is reduced a lot... If you don't have this result, surely you have some problem and do not flash your drive until get this message... Don't be desperate to flash your Liteon drive, the most important is to make sure your key is the right one, flashing is not a big deal, big problem is to have a wrong or incomplete key... good luck for everyone