not sure, but here's mine: purchased around June 10th 2005 6550 06 2b 2b db2051301825 20

2.13 release of the tool is out... -Added "SDRAM Keyscan" button. This should be used with Brite_eye's unlock method, found in the PV2 HOWTO section of camerahacking.com -Added "Zeroed" key. The zeroed key is only useful if you're resurrecting using a locked FIRMWARE.BIN file with an unreadable filesystem. -Added user donated keys: mpho01-6520-2B-02, RayM-6550-2b, mpho01-6550-2B-03, Mpho01-6550-2B-02, WebcoW-6550-2B, Mattwhitt-6550-2B, Stupid, and Stupid2. -Changed message "External key file, pv2keys.txt was found and will be loaded" to just appear in the debug window, instead of a pop-up window. -Added "please report this key worked" code to the "unlock" button. This message is only triggered for keys that haven't been seen in other cams yet. -Fixed bug that required newline at end of pv2keys.txt external key file. -Changed icon to look more like a CVS Red. Anybody want to write docs for pv2tool? PM me if you understand most pv2tool usage, have the writing skills, and want to contribute to the docs - your chance to get your name/handle linked forever with pv2tool! ;)

PV2Tool release 2.14 is out in the usual place ( https://sourceforge.net/project/showfiles.php?group_id=134210&package_id=151762 ) The Tool and Ops have cross-bred somewhat. Changelog excerpt follows. Enjoy! Changes from 2.13 to 2.14 -Added "Change PID" button. Minimally -*test*-('")ed changing a blue from PID 28 to 24 and back. -Added "Disable Warning Messages" checkbox. -Ported the MakeDistribution batch file from Ops. -Ported back the directory browerser from Ops. Now directory dialog remembers last used directory. -Added checks to make sure user hits "Open" first, and warning message the first time a button is pressed without a previous unlock operation. -Made pv2keys.txt always stored and opened from the initial directory that pv2tool was run from.

Great job! However, I seem to get even more crashese when downloading files with this version. This is odd as I thought the file-reading was handled by the camera. Anyway, anyone wanting to use their camera with the FF2 drivers can change the PID to the FF camera PID! No more INF editing.

Ok, thanks. I'll add that one to the TODO's.

PID problem?
I just used the new PV2Tool to change my PV2 Blue over to the FF2 PID (29) and unlock the firmware - all seems well - I was able to unload my photos with iPhoto on my mac :) . But now PV2Tool doesnt seem to recognize my camera! I made sure to edit the libusb.inf to include the correct PID and installed them properly. Windows recognizes it just as before - but PV2Tool wont see it anymore so i cant change the PID back. a bug? am i missing something? thanks

Since BillW is Sleeping ... SSSHhhhhh ... speak softly not to wake him... :wink: :P :mrgreen: I'll post a quote from him to ME regarding this very same thing, BillW said... If you're using pv2tool 2.14, you can just hit the "change PID" button and choose the "flatfoto 2" entry, assuming you have that driver. The camera will be a new USB device after that. If you unplug/replug, Windows should ask for drivers. Just point it at the ff2 ones and you're set. If you need to connect with pv2tool in the future, you'll need to make sure libusb recognizes the new PID, and you'll need to swap the drivers from ff2 to the libusb ones from the Windows Device Manager. :D you may also be able to install one driver to one of your other USB ports and just swap the camera to the other USB port with the LIBUSB driver to use the TOOL and back to the USB port you had the camera in at when you installed the FF2 driver to use it as FlatFoto2 This way you have the best of both worlds without having to re-install the other driver into the device manager each time. This is what I'm doing, but I also left the camera as a 0027. I had changed it to a 0029 also ... and had to use the runpv2 option in the TOOL to reload the firmware (first renaming the original FIRMWARE.BIN to FIRMWARE.PV2) so the TOOL will load the file... and this reset my camera back to the 0027 either way.. you can have your cake and eat it too. 8)

thanks for the reply
Since the computer that i used to change the PID doesnt have any camera software other than PV2Tool, I dont even have the FF2 drivers loaded on it at all. The only driver for the camera on there is libusb, which i modified to include the FF2 PID of 0029. The device manager recognizes it properly and indicates that its using the libusb driver, yet PV2Tool still cannot open the camera. I do have a firmware backup so all is not lost - i just wanted to use the camera easily with both computers. ** EDIT ** It turns out that I cant get PV2Tool to restore my backed-up firmware at all now since it wont open the camera :/ . Does anyone know of another way to change the PID of my camera back? - that seems to be the problem since i can still use PV2Tool with my other identical PV2 blue. ShootME - you mentioned above that you were able to use the tool to upload your backed-up firmware and change the PID back to 0027 - did you have to do anything special besides assigning the libusb driver to PID 0029? I cant get it to open at all now that its a 0029 even though it works fine with iPhoto on my mac using the same cable.

bump!
No one else is having this problem? I just re-produced it with another PV2 blue 6510 ... As soon as I change it to PID 0029, PV2Tool doesnt want to play with it anymore even though I'm sure its using the usblib drivers... I can use the tool with all my other cameras, but not the 29's ... is there a problem with the tool? is anyone else able to use Pv2Tool with a 0029 camera?

I have had no problem using 29. Are you sure you added it to libusb.inf?

Got vr.14 and the comp recognizes the camera and everything. Problem... The prgm opens the camera... but will not unlock it... heres the message... ------------------------------------------------ PV2Tool 2.14 Use this software at your own risk. The author takes no responsibility if you damage your camera. Found the camera: SMaL Digital Camera, VID:0DCA PID:0027 Found camera. Connected to camera. warning: unlock hasn't been pressed yet. Requesting challenge from camera Recieved challenge from camera Comparing Reset key to challenge Comparing Morcheeba's key to challenge Comparing Zeroed key to challenge Comparing BillW's key to challenge Comparing Codeknowbi's key to challenge Comparing Mpho01's key to challenge Comparing Mpho01-6520-2B-02 key to challenge Comparing RayM-6550-2b key to challenge Comparing Mpho01-6550-2B-03 key to challenge Comparing Mpho01-6550-2B-02 key to challenge Comparing WebcoW-6550-2B key to challenge Comparing Mattwhitt-6550-2B key to challenge Comparing Stupid key to challenge Comparing Stupid2 key to challenge Challenge not recognized 02 A8 6C B8 BE E0 0B 48 07 53 04 A1 6C 14 33 02 BE 01 0B E3 26 EA 2A 35 5E F5 30 EB 20 40 D2 B9 DF C9 2A 1C B6 8B 51 9A 9E EA 30 4B E3 51 93 98 D9 1A 7F 43 CB AE C6 A8 34 ED D8 42 31 D0 DC 70 37 4C 00 79 01 7A 0D CE CD F6 3E 90 C8 85 52 52 C7 FA E0 20 37 5A EB C0 57 3E B6 37 A5 79 D9 90 95 FB 95 D8 89 F5 65 6D FE 3E D5 79 03 F6 97 B9 F0 69 D4 83 54 35 C0 07 2F B0 71 D5 62 84 F1 9F Could not unlock the camera with any of the known keys. --------------------------------------------------- My cam info: Its a red... firmwear:6520 hardwear:06 cmb typeid:27 cmb typeid:27 ID: daa042062146realm id: 16 i can tell you ive hack the orig dakota blue but the lcd red will not unlock for me please help! Thanx: Dan

in recent HOW-TO's Brite_eye & BillW agreed on the following ... The batteries should remain IN when you connect / disconnect from the USB... also wait to hear the Windows connect / disconnect tone also you should have at least two pictures taken, and delete ONE, this creates a special file that may (will) make a special new key file to unlock the firmware. most importantly though ... you should have the flash pins in question shorted BEFORE you connect the USB to the camera, then after you hear the bootloader beeps, disconnect the USB, then disconnect the short to the pins of the flash... tell the PV2Tool to connect to the camera, click the RAM-SCAN button in the TOOL, then, the UNLOCK button ... if it finds a new key, or can unlock the firmware, you should also click the UNLOCK-FIRMWARE button so you don't have to go through this again each time you turn the camera on. you may have to try this several times though, ... it may not happen right away ... but it will work... eventually ... ! From what you wrote in this post ... I don't think you shorted the two pins of the flash chip to get into bootloader mode, so this could also be why it's not showing it's unlocked.

how do you flash te pins?