Teslafreak's Method - if camera won't unlock in pv2tool
Teslafreaks Repeatable Reset Method Background Information The PV2 camera comes in a locked state, to keep people like us from downloading pictures from it. To unlock, the camera uses a challenge-response system. Currently there are only 2 known keys: one which is widely used by Ritz and CVS (but not universally), and a reset-camera-key. If it turns out your camera comes with an unknown key, you won't be able to unlock it right away in pv2tool. The Fix You need to reset your camera so it uses the known reset-camera-key. The Method - Quick Overview 1.Install foxz2 2. Modify foxz2's smalunhj.inf to accept PID 27 3. Plug the camera in, and when Windows asks, point it to the foxz2 install location 4. Uninstall the drivers from the Windows Device Manager 5. Camera should now be reset. The Method - Detailed Explanation First download the foxz2 drivers from http://www.che-ez.com/download/ and install the drivers to the default location. Using notepad, go to C:\Program Files\Che-ez! Foxz\driver and edit the smalunhj.inf file. Look for 2 lines, both in different locations, that contain the text "PID_0024". Make a new copy each line, underneath the old one, and change PID_0024 to PID_0027. Now plug your camera in. Windows should indicate that you have new hardware and ask you where the drivers are. Point it to the C:\Program Files\Che-ez! Foxz\driver location. When Windows is finished, you should hear a healthy beep from your camera. Enter the Windows Device Manager (on W2K, right click on My Computer+Properties+HardwareTab+DeviceManagerButton) and you should see your camera somewhere in the list (under digital imagers IIRC). Right click on the camera and choose "uninstall" Once Windows has finished uninstalling the device driver, unplug the cable from your camera, and check the nerve pinch (DisplayButton+ShutterButton, then OnButton). If everything worked, your ID should read "LAMSSMAL0000"... when you change back to using the libusb driver the camera should now unlock fine in pv2tool using the "Reset Key" Variations on a Theme Some cameras appear stubborn. Try the method a few times. If the camera still doesn't unlock, try repeating the method using PID 27 adapted flatfoto2 drivers or libusb drivers instead of the foxz2 drivers. Extra stubborn cameras... Libusb variation in detail... -Plug the camera in, and make sure it shows up as a libusb device in the Windows Device Manager. -Go into pv2tool, hit "find camera", then "connect". -Minimize pv2tool, go to the Windows Device Manager, right-click on the camera and choose Uninstall. -Unplug and check to see if it's reset. bubba007's Libusb variation... -Plug camera in, and make sure it shows up as a libusb device in the Windows Device Manager. -Run pv2mod from a command prompt with the "pv2mod disable-80" script. -Unplug and replug the camera. -Open pv2tool, "find camera", "connect", and "unlock reset"

bubba007's Libusb variation... Worked!!! Thanks. I'm now working on a CVS PV2 Blue (0x0028) and Red (0x0027). Little beast was stubborn.

It Worked!!!
It worked :D Thanks a lot. thank you very very very much. u r a genius. thanks for making my day. i was struggling with my camera for 7 hours. but with your method it took just 7 minutes. Thanks :D

Not having luck with these methods yet. What's the syntax for bubba's method? pv2mod disable-80 gives the message "cannot open file 'disable-80'. Is there a script that I'm missing? Signed, My camera doesn't love me anymore.

variation on the above methods
I rebooted while having the camera plugged in while using the above two methods. ones my computer got to bios screen I removed the camera and viola reset. and unlockable.

Syntax
You're typing correctly, but you must download and put the 'disable-80' mod in the same directory as the pv2mod executable. I hope this helps. Now to play with these blasted 6550's. :?

worked like a champ, even on a camera that was already processed at cvs and was "ready to be recycled". i just had to format the camera after resetting it. now that i think about it, i wish i would've seen what was still on the camera before unlocking it, i'd imagine that it was the pictures that the people who bought the camera took.

didn't work
I tried bubba's method... but it didn't work for me. the pv2mod disable-80 ran and seemed to do something, but still said it couldn't unlock. I'm curious what version of libusb, and pv2tool you propose using for this... please let me know... oh yeah mine's a 6550... maybe that's it.... please help, i'd love to crack this thing

I suggest following my most current method at top of How To forum using la-*test*-('") releases of software (I used 1.10.1 of Libusb). You may want to wait a week for a new release of 2.13 which will simplify that procedure (thanks to BillW's skillful coding). :D

camera
Is there any information on the CVS red 6550? I have tried the new PV2Tool 2.13 and libusb-win32-device-bin-0.1.10.1 The camera is detected but am unable to unlock the camera, it says "no keys could be found". I also have a CVS Blue says : jun-24-04 on main cba. Same response "no keys could be found". I also attempted to short pins 6 & 7 of the memory IC on the red, and it did not change any values. These were purchased at a CVS in Tennessee back in June. Any advice would be appreciated, thanks.

I dont know which camera version this works for, but I would recomend you use the method at the top and just try your best at following the tutorial. The PV2tool 2.13.. short.. sdram keyscan.. that thing

can someone upload the changed INI file to yousendit.com or something i have no idea what to change....