I-Appliance BBS
The Official Source for Internet Appliance Upgrades and Mods
Amazon Honor System Click Here to Pay Learn More
BBS Main List | Sign In | Sign Up | Search | Help | Linux-Hacker.netReply to Thread | Printer |

Home / MISC Areas / Cameras
Success - 1 2 many 4 all
Success - 1 2 many 4 all

New MessageSuccess - 1 2 many 4 all (modified 0 times) brite_eye
Profile
I can't believe my own eye. But all your eyes will brite-n when I post latest shots downloaded from flash on my CVS Blue. Please do not respond to this thread - we will have discussions on other 1 2 many 4 all threads about next steps. My method did require use of copyrighted software running under XP. More work is needed to generate a method 4 all.

morcheeba, please call number ending in 26 that I sent you a few days ago.
Drmn4ea, Can you host a chat, or find someone who can? Please respond with an answer on Questions 1 2 many 4 all.

All others including daBass, bartoni, icedragon, boodles, scribble, ... many more; my eye was wide open all night with no sleep: Please be patient, watch all 1 2 many 4 all threads for updates and continue to respond in other threads.

12-16-2004 12:01:15

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
Who can explain why Red Stop Sign and Yellow Fire Hydrant looks better now?

Ritz Red http://www.photo.net/photodb/folder?folder_id=453271

CVS Blue http://www.photo.net/photodb/folder?folder_id=456813

Please do not answer on this thread - it is intended strictly for follow up detail and discussions on methods used to obtain above pictures, which may be delayed until we iron out some issues. Feel free to fray on Questions thread. Oh, a hint for the question, at one point in download process a size of 3.14 M appeared - I think about 2M of uncompressed photo at $120000 may be hidden in unreachable storage.

12-16-2004 14:32:46

New MessageRE:Success - 1 2 many 4 all (modified 1 times) morcheeba
Profile
(message removed)
12-17-2004 01:06:37

New MessageRE:Success - 1 2 many 4 all (modified 1 times) Synlor
Profile
I'm just going to copy my message in the Suggestions thread in here:

WAHOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!!! I got my pictures finally! I bought one of the first versions in D.C. 7 months ago and have been waiting, finally it is here! Great job everyone.... Drmn4ae, boodle, scribble, morcheeba, and anyone else I haven't mentioned, congratulations! The quality is pretty damn good.

Here is how I did it, though I have been playing around with various thigns before so it may be slightly differant.. I've installed several versions of drivers and such.
I started with the libusb drivers, used the poker program to unlock it, after I read the 13 bytes confirming that I unlocked it I changed the driver over to the foxz2. I opened Photobase, did the get picture routine, and tried the WIA foxz2 driver, nothing came up but I think it might be necessary to try it first... not sure. Then I tried the driver called just Foxz (this may ahve been left over from previous driver installs and such), and whamo all there. Just had to hit download and I had all my pictures :)

Here is a sample one taken at Mount Vernon (Washington's home): http://devcast.dcemulation.com/animals.png

Thank you everyone who has contributed, this is truely incredible, my weekend has been made :)
----------

I am working on a post for the dummies thread, but I want to use a clean environment (no previous drivers installed and such) so that I can make it work for hopefully everyone. This'll take some time because a) I'm lazy ;) and 2) I'm not gonna have access to another computer till tomorrow most likely. :)

12-18-2004 17:14:00

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
For png format of above you'll need to cut a paste the link.

For a jpg version:
http://www.photo.net/photodb/folder?folder_id=457304

12-18-2004 18:04:13

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
I got what I wanted, what I needed, and more (see Annoying thread). She has refreshed my body, mind and soul. The brains are back in charge again – dakotamod can’t keep a job – not this one, not the one at Ford (poor guy losing everything just before years end).

Major success on two fronts: 1. Good pictures without Blue FlatFoto software. 2. Lens mod works great! A simply ASTOUNDING EYE with tal of Digital seemingly reflecting off retina and camera lens hole perfectly centered inside pupil. It looks like I have a CVS camera inside my head!

I used the radioshack 1.3 download from their site and a trial of Arcsoft Photobase 4.5 (4.0 came with blue flatfoot). I started Photobase, updated driver to libusb, unplugged replugged camera, unlocked, switched driver to 1.3 red Radioshack, then get camera, select digital (middle of 3 options, no more wia on list). Works the best of any driver / software combinations I have tried.

The photos from my Red CVS many time use camera: http://www.photo.net/photodb/folder?folder_id=458360

12-23-2004 07:23:04

New MessageRE:Success - 1 2 many 4 all (modified 0 times) mike
Profile | Email
Brite_eye
What were version level of drivers used.....????? very inportant!!!
What was RS link/filename etc
Was this using Linux or Windoz????
did you use poker to unlock and did you close poker????
Have you/anybody tried this on CVS blue ????
12-23-2004 08:16:24

New MessageRE:Success - 1 2 many 4 all (modified 0 times) mike
Profile | Email
Brite_eye
What were version level of drivers used.....????? very inportant!!!
What was RS link/filename etc
Was this using Linux or Windoz????
did you use poker to unlock and did you close poker????
Have you/anybody tried this on CVS blue ????
12-23-2004 08:17:37

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
mike, please search back for latest links try those and post your success. I do not think the Radioshack site is changing (download 1.3 large package but only install driver not MP album). The only trial at ArcSoft for Photobase is release 4.5 (more current than the 4.0 that came with my blue flatfoto). I think I used Drmn4ea's latest release (but you can try both and report back). I have posted good shots from all my cameras, but do not remember what combination worked for the CVS blue (feel free to gather my Vulcan never pinches and group everything together). The photos in my most recent $14.99 Red CVS folder were done using 2 red cameras - the macros with a reset LaMSSMaL and outdoor shots with a nonfree unique IDd trackable one with untouched lens. Setup libusb driver, unplug, reboot, replug (verify driver), click on USBPoker, open it, unlock verify final 13, minimize, driver update (no search, have disk ...), get camera button on Photobase, select digital camera (in middle - if WIA you have wrong driver), and wait, 25 pictures can take more than 10 mintues.

Lens mod - do not try to unscrew 2 very tiny philips on shutter, after pressing to hard it became clear the whole assembly is just glued on top of lens (glue much easier to remove than before on original blue). Slide shutter between lens and black blob, free lens, cut off 1/8 inch flange on inside of cover, close it up and you can now focus as you please. See morcheeba's post to find 3 case screws, I peeled back stickon, but should have just gently poked for screws.

12-23-2004 09:44:03

New MessageRE:Success - 1 2 many 4 all (modified 0 times) Drmn4ea
Profile
I found on my machine anyway (Windows 2000), all the driver-shuffling is not necessary. I have the Foxz2 drivers installed and libusb 0.1.80. On plugging in the camera, the Foxz2 driver immediately claims the camera's USB interface (beep and ready light); but USBpoker can claim it too (!). So I can just open it again there, write the key (it seems reading the old key first isn't strictly necessary, unless you don't know it of course), read the status (may fail; perhaps the Foxz driver beats you to it?) and close it, then I can access the camera via anything with a TWAIN interface (I use Paint Shop Pro).

Haven't seen the image quality of this for myself yet; haven't used any camera with actual pictures on it yet. It seems it only works with the LAMSSMAL0000'd cam, the other returns "Operation not permitted in bootloader mode" (guessing the reset cam returns something different in response to the numerous $5E requests the Foxz2 driver sends).

12-23-2004 11:49:41

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
This is the libusb driver I am forced to use since others do not work. Am I the only one using the 11/18/2004 driver? I am running XP SP1. http://prdownloads.sourceforge.net/libusb-win32/libusb-win32-device-bin-20041118.tar.gz?download Sometimes these show up as tar.tar instead of tar.gz and I have to select another download site.
12-23-2004 12:41:03

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
mike, please respond either with a success here or answer one of my emails, or let me know if you haven't received my emails.

2 all 4 all, Ignore my driver post above this one. I have had success downloading and installing both device and filter from sourceforge .1.8.0 version. The steps are now in CVS 1 use thread. Please try to confirm in your environment.

12-27-2004 10:51:43

New MessageRE:Success - 1 2 many 4 all (modified 0 times) mike
Profile | Email
I download 2 images tonite...photobas grabbed them.....note these were better than
the photos I took with the flatfoto blue.....now history,,,,,returned it,,,,,
12-27-2004 19:47:24

New MessageRE:Success - 1 2 many 4 all (modified 0 times) binaryweaver
Profile
I'm using a CVS Blue (PID 28) and have successfully pulled all 24 photos out of the camera after playing around with the INF files. Basically, I just modified the Che-Ez FoxZ 2 driver to add libusb0.dll so the camera has all the following files loaded at once for the same driver: libusbfl.sys, usbscan.sys, libusb0.dll, smalcnhj.dll, smalenhj.dll, smalwnhj.dll. I used Photoshop 7.0 to extract the photos via the Che-Ez TWAIN interface and then resaved them to disk. I would like to post the INF file (I know very little about drivers and haven't really played with them until I found this site, so it's a mess I'm sure, but it worked) but I'm afraid of the Copyright statement in the INF file and don't want to post it if it's illegal. I did make a screenshot of my Device Manager showing the driver details, though which should help. Here are the files:

http://www.demanufacturing.com/pv2/screenshot.jpg
This is the screenshot of the device manager with driver details

http://www.demanufacturing.com/pv2/photo.jpg
One of the photos I was able to pull off the CVS Blue (Not a good shot, my wife took it.) :)

I hope this helps. Oh, I should mention that after I loaded this modified driver for my camera, I also rebooted, unplugged and replugged the camera in and ran Forkboy's PV2Tool to unlock the camera. It wouldn't unlock until the second attempt (strange), but once it did, I was able to extract the photos. Now if I can only find a utility that helps delete the images off this Blue (a good front end - Forkboy??), I'm ready to shoot again!

12-30-2004 22:33:45

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
binaryweaver, great work another success and a new picture - but where are the eyes - must have at least one eye!

Please consider helping with some hot plugged shots for decompression thread - we could use a binary weaver to help unravel mysterious patent methodologies.

12-30-2004 22:54:45

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
binaryweaver, forgot to mention that previous methods offers a default delete option during download, and also a media tab to reformat/delete all pictures. Please be more specific on how you modified/integrated drivers and if in that process you lost media tab and ability to delete pictures. I like your screen shots and hope others will provide examples stepping us through their success.
12-30-2004 23:01:36

New MessageRE:Success - 1 2 many 4 all (modified 0 times) binaryweaver
Profile
You're right. If you leave the box checkmarked for deleting the photos off the camera while downloading (In the Che-Ez Foxz Twain utility), they all go away. My camera which previously displayed "Return for Processing" on the LCD now says 25 pictures remaining and is ready for reuse.

I'm going to get all of the files and modified INF together and try it on a virgin machine and attempt to trace and document my steps. It's getting too late for that tonight. I have to work tomorrow, but maybe I can sneak in the time if the bosses aren't around and get paid for it. :)

12-30-2004 23:15:44

New MessageRE:Success - 1 2 many 4 all (modified 0 times) taytrr
Profile
I can consistently get images off with the driver switch but they are all blue with a blue halo. Using XP, libusb 0.1.8.0, Foxz2, PhotoImpression 3. I remember someone else having the blue issue too but couldn't find the solution -- could someon remind me? Also, after using the show .tft on camera function my system will suddenly reboot if I try a second time (no warning, just starts post and mem count) -- any ideas?
12-31-2004 01:33:08

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
taytrr, do not teeter toter, use a release of software that someone else has found works: Photoshop 7.0, current Irfan View download, 4.5 Photobase trial ... I had problems with ArcSoft photostudio and photobase, but did not try photoimpression and would recommend Irfan over all others. Also make sure you deinstall all previously installed interfering drivers - a very difficult task. If possible use as close to a pristine Windows install as you can (I almost resorted to a fresh installation - and would suggest such if all else fails).
12-31-2004 05:18:34

New MessageRE:Success - 1 2 many 4 all (modified 0 times) buster
Profile
Okay guys this seems to work for at least 3 of us. If I get confirmation from others we can post boil it down for a dummies thread.

1)remove all traces of previous attempts. Delete any driver files from anywhere on you computer (should be smal*.* and libusb*.*)
**Please be carefull with this if you have other files with similar names that are unrelated**

2)Install only libusb filter version 0.1.8.0 found here http://prdownloads.sourceforge.net/libusb-win32/libusb-win32-filter-bin-0.1.8.0.exe?download

3)Install Che-Ez Foxz2 driver found here
http://www.che-ez.com/jp/download/driver/foxz2/Foxz2.zip

4)Edit C:\program files\Che-ez! Foxz\driver\smalunhj.inf to add 4 lines (These are for CVS Red 6520):
[SMALUSB.models]
%USB\VID_0DCA&PID_0027.DeviceDesc%=SMALUSB.Dev, USB\VID_0DCA&PID_0027
[SourceDisksFiles]
libusb0.dll=222,,
[SMALUSB.CopyWIAFiles]
libusb0.dll
[Strings]
USB\VID_0DCA&PID_0027.DeviceDesc="CVS Red Foxz2"

5)make sure that you do not have more than one *.inf file with a reference to the new PID or you may mess up you might not install the driver properly.

6)Plug the camera in if not already. If the driver wizard does not start then choose update driver for the camera entry in device manager.

7)choose "Install from specific location"

8)choose "Don't search, I will choose the driver to install."

9)Do not select from the drivers that xp chooses to be compatible. Instead select "have disk".

10) Browse to your new updated driver in directory c:\program files\Che-ez! Foxz\driver\

11) If all is well windows will prompt you to locate libusb0.dll. browse to c:\windows\system32\ and select "retry"

12) Download and install new PV2Tool from here
http://forkboy.doesntexist.com

13) Choose your camera from the list of devices and run "unlock". Your camera is unlocked when the display reads "unlocked".

14) Install and run Irfanview found here:
http://www.tucows.com/preview/194967.html

15) Select twain source as "Ce-ez ????"

16) select batch scanning. Choose the directory and filename to download to. and select "Okay"

*** Here is where I got hung up the first time ***

17) If you don't get a bootloader error message select "start download" and you are done, congrats. otherwise continue

18) If you get an error message about not being able to download in boot loader mode then follow this procedure:
a.unlock with pv2tool
b.unplug usb cable
c.restart the computer
d.plug in usb cable after reboot finished
e.unlock with pv2tool
f.repeat steps 15 & 16 and hopefully you are successful now


That is how it worked for me to my best recollection. If you have success with this method please post for all to know that it works. If enough people have success I will try to simplify the process for a dummies post.

01-05-2005 12:40:41

New MessageRE:Success - 1 2 many 4 all (modified 0 times) insomniac40
Profile
Thanks to morcheeba, buster, brite_eye and all you geniuses even a dummy like me can down load images off of CVS Red! Here's my first image off the camera.
\https://home.comcast.net/~petermac/3401.jpg
01-09-2005 14:50:21

New MessageRE:Success - 1 2 many 4 all (modified 1 times) ygfperson
Profile
It works! I have a CVS blue and I used the method buster posted two posts up. I'm using windows SP2 on a Thinkpad T40 laptop. Unlocking was problematic but I got it to work eventually through trial-and-error (mostly unplugging and replugging, clicking on 'type 1' in pv2tool 'keys', clicking 'unlock' in the pv2tool program mentioned).

I kept getting a 'bootloader mode' error for IrfanView, until I reinstalled the che-ez driver as brite_eye posted in the 'cvs digital 1 use' thread (keeping irfan open, right after having a 'bootloader mode' error). After reinstalling things went fine. I haven't repeated it so maybe it only works sometimes and I got lucky.

Anyway, thanks to all of you for working on this. Pics (both are random pics of my room, ~120k each):
http://www.rpi.edu/~schneg/ScanImage01.jpg
http://www.rpi.edu/~schneg/ScanImage02.jpg

01-09-2005 17:35:06

New MessageRE:Success - 1 2 many 4 all (modified 0 times) binaryweaver
Profile
Ygfperson -

You go to RPI? Nice. We're neighbors. My friend Critter and I used to do a Tech radio show on RPI years ago called "Little Brother". He still has the shows archived at:

http://mercury.critternet.mine.nu/little_brother/

01-09-2005 22:02:10

New MessageRE:Success - 1 2 many 4 all (modified 0 times) insomniac40
Profile
Small world, I went to RIT years ago... I had a buddy who attended RPI.

So, for the blue I just need to put in 28's instead of 27's?

01-09-2005 22:09:26

New MessageRE:Success - 1 2 many 4 all (modified 0 times) ygfperson
Profile
>So, for the blue I just need to put in 28's instead of 27's?
pretty much, yeah.

>My friend Critter and I used to do a Tech radio show on RPI years ago called "Little Brother".
That's cool... a few of my friends are getting radio shows next semester, although they'll be doing more music than discussion

01-10-2005 00:22:29

New MessageRE:Success - 1 2 many 4 all (modified 0 times) morcheeba
Profile
Can I tangentlly join the lovein? I visited RPI when I toured potential colleges I wanted to go to.
01-10-2005 00:58:53

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
RPI, I almost went but feared leaving my Michigan and comfort of home - I commuted to Oakland University instead. But had I gone for higher technical ground I never would have met my lovely wife. Thanks binaryweaver for pointing out RPI.

Now RPI is not your normal stuffy U where wise men don't know how it feels to be thick as brick. I was quite pleased earlier this year to see: http://www.rpi.edu/web/News/press_releases/2004/lahey.htm

Wow cold now becomes just a low-key bubble, to avoid trouble. ygfperson - I am happy to enjoy your setting vicariously.

01-10-2005 01:18:46

New MessageRE:Success - 1 2 many 4 all (modified 0 times) insomniac40
Profile
Thanks to all you rocket scientists! Using brite_eye suggestions changing 27's with 28's and a lot of install/uninstall/plug/unplug/reboot and do it again, I have successfully accessed images off both Ritz and CVS Blue cameras as well as the CVS red previously using busters procedure on both XP Pro and Win 98. It can be done so keep on trying. Now I am hooking up the shutterbug servo switch to a blue so I can fly it in an RC plane without fear of crashing a $300-400 camera.
01-11-2005 18:13:52

New MessageRE:Success - 1 2 many 4 all (modified 0 times) drider
Profile
Uh, please forgive my ignorance because I must have missed something somewhere, but since I don't have any of these newer cameras (I have the original Dakota) I will ask my question: Does the same cable work with the newer cameras as does with the original?
01-11-2005 23:00:12

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
drider, YES SAME CABLE. But if you could not find that scanning all these threads, then ...

If you wish to try, you will have to read several entries in several threads several times! Please surprise us all with an early success!

01-11-2005 23:36:12

New MessageRE:Success - 1 2 many 4 all (modified 0 times) taytrr
Profile
I have been successful at converting my camera (one with preview) with ForkBoy's new tool and the mods described by morcheeba. Thanks guys!

Computer: WinXP Pro SP2, LibUSB 0.1.8.0, ForkBoy's PV2Tool2, Foxz2 Driver, Irfan

Using morcheeba's mods text I located the positions to change for firmware 6520 by inference using 'tiny-hexer'

in firmware 6410 morcheeba's instructions are (mod 2 and 4):
6913 change 01 to 02
6Af7 change 27 to 24 (these are 0x1e4 apart)

so in firmware 6520 I made the following three changes:
6910 change 01 to 02 (this one is exactly 0x1e4 back from the next one)
6AF4 change 27 to 24 (This can be located visually)
then I addressed the checksum by arbitrarily selecting this byte in one of the vast areas of 0x30's in the file
6b30 change 30 to 32 (added 1 and -3 = net -2, need +2)

I then uploaded the file using ForkBoy's new tool and also replaced all of the .TFT's with new ones (a skin). The camera works as an unlocked Foxz2 (24). I'll try and locate the locations to convert the non-preview camera tomorrow.

One problem though; my pictures are still all blue just as before the mod. Tried modded camera on clean '98 system with same blueness. Has anyone determined the cause of the blueness yet, or even have the problem?

01-13-2005 06:38:56

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
taytrr, excellent work. I hope to repeat your exact mod tonight; Of course without the blue hue. Just guessing but depending on angle there is a blue or red filter (ultraviolet or infrared or both) in the 4 element lens - you may have an extra filter, a missing filter, a damaged imager, driver glitch, or bad flash. When recovering lost images I had some incomplete cluster strings that showed up with a strong green tint.
01-13-2005 06:59:53

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
taytrr, Was your CVS Red a virgin with original serial or a reset LaMSSMaL?
01-13-2005 07:06:03

New MessageRE:Success - 1 2 many 4 all (modified 0 times) ForkBoy
Profile
You guys are working on exactly what I had hoped for! - Thanks (Post pictures of your skinned camera)

One possible clue to the "Blue" problem (Which I have also)

I have noticed that the following files are no longer present on my camera:
CAMCALIB.BIN
PDSCRTCH.BIN

These where in my original Flash extraction - Do you think these issues could be related???

01-13-2005 07:12:52

New MessageRE:Success - 1 2 many 4 all (modified 0 times) mike
Profile | Email
Are we talking about a dark blue screen with faint black images???
My old CVS blue gave me that with cheez-foxz2 and was identified as unknown camera
but using flatfoto driver it downloaded images ok & was identified as accord camera
I see if I can find dumps to see if the 2 files are missing....
01-13-2005 08:08:53

New MessageRE:Success - 1 2 many 4 all (modified 0 times) ForkBoy
Profile
morcheeba & taytrr, or anyone else

Could we make a list of all known successful patches so I an add a patch function to PV2Tool2?

I'd like to have a before and after FIRMWARE.BIN file checksum (32bit or MD5Sum) and a list of all
memory locations with the before and after values.

01-13-2005 12:16:23

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
I am under a bit of stress looking for a new assignment with Compuware and my continuous monitoring will not be as frequent. Anyone who thinks they understand some of this feel free to gather what ForkBoy is asking for and post with a note requesting verification from morcheeba and taytrr. Thanks. That post probably fits best in Applications thread.
01-13-2005 13:31:55

New MessageRE:Success - 1 2 many 4 all (modified 0 times) taytrr
Profile
I applied the following patch to my T28-6520 (model 400 with no preview):

6991 change 01 to 02
6B85 change 28 to 24
6BC0 change 30 to 33 (added 1 and -4 = net -3, need +3)

Suceeded with downloaded in Adobe Photoshop CS trial, Che-ez Foxz2 -- Had errors though -
Stopped downloading at 21/25 with twain error, 20 retrieved, 4 still on camera
Stopped downloading at 16/20 with twain error, 15 retrieved, 4 still on camera
Stopped downloading at 11/15 with twain error, 10 retrieved, 4 still on camera

It seems that it can't get the fifth to last one then loses it leaving the last 4. If the camera is then filled up again the 4 that remained are downloaded first. Perhaps with the correct checksum modification, rather than my third change, it wouldn't do this though I get all 25 from the T30-6520 (410 w/preview) with the same type of mod.

Also, this camera still has the two files (PDSCRTCH.BIN & CAMCALIB.BIN) and does download the files in normal colors (not blue). Since I haven't poked at it with USBPoker and only used the libusb and ForkBoy's tools it must have happened while I was initially assembling my cable and wired it wrong -- I think I shorted 2 and 9 then plugged it in a few times before I figured it out. It must have been after this that the camera was reset and the files missing. This may be some sort of security measure.

ForkBoy -- as soon as you can, add the entire flash contents upload/download to the new tool. (Thanks again!)

01-14-2005 01:04:39

New MessageRE:Success - 1 2 many 4 all (modified 0 times) mykel27
Profile
So I think I fried my one and only "Ritz Red PV2" 6410-06-27 (Live in Canada). I have been following this threads for months now and lately had lots of success extracting the pictures with "busters" method and the driverX. Today after seeing taytrr's success in patching the firmware bin and using ForkBoy's new tool I first downloaded the flash.img and firmware.bin (for backup purposes) then opened the firmware.bin with "XVI32" and located 6913 and changed 01 to 02, 6Af7 changed 27 to 24 and 6b30 changed 30 to 32 saved the file, loaded it to the camera and "bump" the camera kind of died. The pv2tool did not give me any errors, but after the whole thing the camera does not turn on (it gives a low one tone beep) of course no salute (also tested batteries just in case). The funny thing is that the camera is recognized by windows to install driver switch drivers and such, PV2tool finds it, connect to it (gives a normal beep) but will not unlock it; USBpoker will list it, open it and I have no clue as to how one uses this tool. So the question is, Am I out the game for good? Is there any way to write to the flash without unlocking (Irfan gives me the bootloader message when batch scanning) Is there any way to upload the flash.img or the firmware?....by the way my camera was reset to "lamssmal" before all of this, and that happened when sending the wrong authentication with previous Pv2Tool.
Please mike, moorcheeba, taytrr, forkboy, brite_eye and many others HELP! And thank you for an amazing experience playing with this little gadget.
01-14-2005 01:25:43

New MessageRE:Success - 1 2 many 4 all (modified 0 times) taytrr
Profile
mykel27 - sorry about the camera, that really sucks. All I can think of is that when I first tried it my hex editor was in insert and my file was expanded by the three bytes I changed and I discovered it right before I was about to uploaded it, and went back and re-did it in overwrite mode. If you saved the original and modded files, recheck that only the three changes were made, and that they were overwritten rather than inserted (check for different file size). As far as I know the camera's bootloader hasn't been figured out yet but when it is there will most likely be a recovery process. Unfornately, that camera is probably out of comission until then. Can you post the camera's firmware/cmp/etc info? Was it a 2b, 28, 30, or another hardware type? Does it still boot up at all? It it being recognized as a type 2F (I read that another one that became corrupted came back up as 2F and had similar symptoms.
01-14-2005 01:43:14

New MessageRE:Success - 1 2 many 4 all (modified 0 times) mike
Profile | Email
The CVS Blue cam back as 2F....I could use usbpoker and could read/write flash using
$52 and Lun 1 but screwed up somewhere....probably when playing with $26 and $28 cmds
I did not have to unlock while Type-2F but could do no hilevel stuff ie use foxz2
I had to set byte 17/18 = E0+block offset ie block 0 = E0+0=E0 00 block 34=E0+34=114= 14 01
block 35=E0+35=115= 15 01 block248=E0+F8=1D8= D8 01
xE0 * 256 = 1C000 -- is where code started in the raw firmware dump of CVS BLUE 400 Type-28
block 34/35 patching ,,block 248 Csum ... have decided when I try to write firmware again,,that
I will the D in D i g i t a l to compensate for Csum A,B,C,D,E,F,G,H etc and only have to write 2 blocks
@ 512 / write I may have trashed mine trying larger writes,,just don't know....

Has anyone investigated the remaing connector pins ...maybe I2C for incircuit programming of flash?????/

01-14-2005 04:09:28

New MessageRE:Success - 1 2 many 4 all (modified 0 times) taytrr
Profile
Mike - does it come up in ForkBoy's old tool? Can you do a download of entire flash?
01-14-2005 04:22:35

New MessageRE:Success - 1 2 many 4 all (modified 0 times) mike
Profile | Email
Forkboys old tool would not function since it relies on unloking the cam.....
and since its not locked ..pvtool fails..try using usbpoker
open-- select bulk out and use a file for the $52 cmd block to input data [see previous posts]
SEND [should write 31 bytes] then change to bulk in and set a byte count usually at least 13 byte more than
you requested you should rcv data...into angerrcv.txt
you can change byte 13 to lun 1 then set byte 17/18 to block offset to get firmware.....
if cam is not totally screwed....the max bytes I can read from lun0 is 0x2fffff I'm not sure about Lun 1
01-14-2005 05:34:42

New MessageRE:Success - 1 2 many 4 all (modified 0 times) mike
Profile | Email
CVS RED Type-27 FIRMWARE 6430 patched aok using pv2tool2
changed 68f9 = 01 to 02 +1 changed 6ADD = 27 to 24 -3 net=-2 Changed 6A93 = 44[D] +2 to 46
D i g i t a l = F i g i t a l
now find new hardware Figital Camera,,, I am undecided if I really want to change type or not
I have some pics taken at night and are grainy using flatfoto // and are blurred using cheez
for some reason I can't seem to get the same quality as others....
01-14-2005 09:19:07

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
mike, I only post my best (average about 1 of every 30). In low light at more than 8 feet all mine are grainy - get closer for flash shots. Blurry - try hands off using 10 second timer.
01-14-2005 10:59:34

New MessageRE:Success - 1 2 many 4 all (modified 1 times) morcheeba
Profile
taytrr - congratulations!! Funny about that last-4-pictures thing, though. I tried my camera a couple of times, but each time there were only 1-6 pictures on the camera.

mykel27 - the mods you made sound like they should pass the checksum correctly, but the error condition you described sounds like what happened to my camera when I messed up its checksum (is that low beep actually two beeps close together?. I'll bet you're in the bootloader mode -- whoowhee, something else to explore! (argh, ok, it sucks a little to be in that mode). Is there any chance you can get this on a linux system and get a dump of the USB info (endpoints, etc.)? When I connected the USB, I only got a single high tone instead of the normal two tones (medium then high).

The only difference in programming I'd suggest is changing the location of the compensating byte. 6b30, while it has a $30, looks like it is being used as a variable. The code at $11000 ($4000) that initializes the memory segment starts erasing at $03b33 ($6b33).
--
Side note: I got my PSP today... I just walked in the store and asked for it. I guess some stores have it earlier than others It cost me 310,000 smackaroos, though. It's a really nice system. The info screen says it uses code from RSA, so it might be a little more secure than the PV2.

01-14-2005 21:40:39

New MessageRE:Success - 1 2 many 4 all (modified 0 times) mike
Profile | Email
CVS BLUE 400 Just used Forkboy's PV2tool203
Downloaded flash modified location 22991 changed from 1 to 2
changed 22b2b D i g i t a l to C i g i t i a l Uploaded aok...camera functions AOK
Camera is permently unlocked........! yi pi ki yi aye!!!
thx ForkBoy
thx morcheeba

sidenote! my trashed Blue is trashed ... every read give me my 1st 512 of firmware....

01-14-2005 22:42:18

New MessageRE:Success - 1 2 many 4 all (modified 0 times) taytrr
Profile
I used ForkBoy's PV2Tool v.203 and was able to download the flash from my T2B-6520 (model 410). Since the built-in file tool wasn't working I used WinImage and extracted the firmware and modded the following:

6910 01 to 02
6AF4 27 to 24
6B30 30 to 32 (+1, -3, net -2, add +2)

I also used ForkBoy's old TFT tool to convert my custom .BMP's (the skin) and copied those and the firmware back in to the image. Finally I uploaded the whole image back to the camera. I can take the full 25 pictures (helped by my custom screens) and download them using the Cheez2 driver. The pictures are normal color (not the blue halo ones I'm having with the T30-6520).

Morcheeba - I picked a value in the area with '0x30's because I assumed that the area was either not used or wouldn't be used until after the camera booted and the checksum test completed. I've used that trick of filling work areas with '0's or another characters visible while browsing the hex code to help delineate my code areas and assumed that if it was used later by the firmware that my byte would be overwritten and harmless. You'd be best qualified to tell me if it's not accurate in this case though. Idealy I'd update the normal checksum bytes instead but had trouble making the calculations match up. As far as the modders changing the the 'digital', 'camera', and other strings, I wouldn't recommend doing that as those strings could be used in the interface with the computers device driver or twain driver.

Also, anyone considering duplicating one of these hoaky mods I've posted should only do it knowing that it has not worked for at least one person (sorry Mykel) and you could end up in boot-loader mode with an unusable camera. And, before you mod your camera download and save a working copy of the flash (and label it).

01-15-2005 01:55:36

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
Thanks 2 all above and beyond.
I now have a Many-Time-Use T28-6520 (CVS Blue model 400 with no preview) and a Many-Time-Use T27-6520 (CVS Red model 410 with preview).
T28-6520 Patch: 6991 1->2, 6B2B D->C
T27-6520 Patch: 6910 1->2, 6AAA D->C
Both working with one Che-ez driverx.inf containing entries for 27 and 28. Vulcan nerve pinch for 27 gives 2B - an ignorable annoyance. I can only get file list function of PV2Tool203 to work when cameras are full. ForkBoy do you have a hardcoded 1-25 loop?
01-15-2005 02:11:33

New MessageRE:Success - 1 2 many 4 all (modified 0 times) taytrr
Profile
brite_eye - your T28 is a T2B if info screen comes up as 2B -- T28 and T2B have different compatibilities that we're still discovering. Comgratulations on your successful mods!
01-15-2005 02:20:52

New MessageRE:Success - 1 2 many 4 all (modified 0 times) taytrr
Profile
Sorry, I meant T27 is T2B - NOT - T28 is a T2B.
01-15-2005 02:24:57

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
2B or not 2B, 27 not 2B works best for me in Che-ez driver. I wonder taytrr, if something other than 30 will cheez away your hues (try changing 30 to 28 in inf). Can you see beyond my offer in bits thread?
01-15-2005 02:48:15

New MessageRE:Success - 1 2 many 4 all (modified 0 times) taytrr
Profile
I've got my T30-6520 modded and can download photos but I've got the blues . . .

http://www.photo.net/photodb/user?user_id=1482493

Actually, they're quite interesting.

I can't get a complete upload or download of the flash so this may be part of my issue. ForkBoy's PV2Tool v.203 will upload about 2MB so I have been uploading my original and modded image (which are picture free so the camera's file system and first 800k of software are loaded). Since the image above 2mb should be empty anyway it shouldn't matter (right?).

01-15-2005 05:31:37

New MessageRE:Success - 1 2 many 4 all (modified 0 times) mattguyver
Profile
Much like mykel27 I too have a ritz red 6410 and seem to have entered the double low beep bootloader mode. How very frustrating! Just today i was able to finally get the ver 204 of pc2tool running and i go and fubar my camera. Hehe. Any suggestions are much obliged!
01-15-2005 23:51:10

New MessageRE:Success - 1 2 many 4 all (modified 0 times) taytrr
Profile
ForkBoy -- PV2Tool v.204 still errors out while reading/writing flash. The size of the dumps created are:
2,883,584 v.203
3,014,656 v.204
The original util will download the full image though.
I've been using it anyway since the camera's system software is less than 800k and will work when reloaded even when it crashes. The downloaded images don't load in wimimage though but tinyhexer show that they are full of the right data, just truncated where the error occurred.
Also, it won't read the entire directory from the camera -- when full, firmware.bin & pdscratch.bin aren't visible and only 20 of the 25 images show in the picture dir. (I'm cross referencing with WinIMage).
Thanks for your work on this!
01-16-2005 01:16:26

New MessageRE:Success - 1 2 many 4 all (modified 0 times) binaryweaver
Profile
One of my older reds died yesterday so I purchased a new one. I performed the firmware mods as described by Taytrr (changing the PID to 24) and the firmware works fine. I can connect the camera to my computer and download the images without having to unlock. Only one problem,... I'm getting the blue photos, too.

I've got to find those FlatFoto 2 drivers and see if that clears up my problem.

Has anyone tried taking firmware from an older red and flashing it to the new ones that are out there? Will it work
and/or clear up the blue photo issue?

01-19-2005 15:58:10

New MessageRE:Success - 1 2 many 4 all (modified 0 times) mike
Profile | Email
Are you showing FOX2 as camera type or Unknown.... I showed Fox2 with Type24 and the cheez camera selection...
I have NEVER gotten a good picture when display unknown camera
01-19-2005 16:41:08

New MessageRE:Success - 1 2 many 4 all (modified 0 times) binaryweaver
Profile
It originally showed up as "Digital Camera".

Here is an update: I went to Radio Shack and as luck would have it, they had a dead FlatFoto 2 that they were shipping back for credit. They let me have the original driver CD to play with. Nice.

I modified the .INI that came with the FlatFoto CD to match PID 24 (The PID # of my new RED after the firmware modification) and the drivers load fine, camera is automatically unlocked, etc.

I transferred the photos into Photoshop 7 via the WIA FlatFoto 2 twain device and they are no longer blue! If I download the same photos off the camera using the Che-ez! Foxz twain interface, they come back blue again. So some of the new cameras coming out are not compatible with the Che-ez! Foxz drivers anymore. Even though the FlatFoto drivers work, I don't like them as well. The images returned were more grainy than the Che-ez! Foxz drivers. It works and would be acceptable for web use, I suppose. I'm going to take some new photos to show as examples and post them later.

01-19-2005 21:11:37

New MessageRE:Success - 1 2 many 4 all (modified 0 times) mike
Profile | Email
Binaryweaver... You might try a different PID....my macro pics
are CVS BLUE set for pid 29 [shows 2.0 mp camera] and I select Digital Camera
in irfanview or photobase and using FlatFoto......I have never got WIA - Twain to work..
get missing driver ....
Also my type 24 shows up as FOXZ2 when using Cheez-FOX2..then again I did NOT select WIA
01-20-2005 04:51:36

New MessageRE:Success - 1 2 many 4 all (modified 0 times) binaryweaver
Profile
I really should just clean out my OEMXX.INFs from c:\windows\inf and just start over. I think I might have some residual drivers on here causing the WIA to work. I installed the FlatFoto drivers on my work PC today and got the "Digital Camera" option for TWAIN in Photoshop, but I don't seem to have it on this computer. Probably because I ran the "Setup" file at work and just used the drivers here at home without running "Setup".

If I'm going to write up a walk-through or document this, I really need to find a clean computer with a fresh installation of Windows. Maybe this weekend.

I don't really want to mod the firmware again to change the PID. If it's not broke, don't fix it. :) One bit off and it's toast.

01-20-2005 20:33:30

New MessageRE:Success - 1 2 many 4 all (modified 0 times) teslafreak
Profile | Email
starting to sniff out problem if you can call it that about
resetting the sereal number i bought a new red firm 6510
after resetting an older 6510 and not knowing how it happened
i downloaded the firmware of the untouched red and saved the file
i also uploaded the full reset red and saved the file
installed the full reset red img onto the new untouched red
and checked. RESULT "CAMERA FULL RETURN FOR PROCESSING" BUT SEREAL NO UNALTERED
LOADED NEW FIRMWARE ONTO RESET OLDER FIRMWARE RESULT "25 SHOTS REMAINING" SEREAL
NUMBER UNALTERED.
I WAS HAVING A PROBLEM WITH THE "BOOTLOADER" ERROR ON IFRANVIEW CHEEZFOXZ DRIVER
AND HAD LEFT THE CAMERA INSTALLED UN THE USB PORT WHEN I UNINSTALLED THE DRIVER
UNPLUGGED THE USB REPLUGGED THE USB "FOUND NEW HARDWARE" AND INSTALLED CHEEZ DRIVER
AFTER USING PV2TOOL V5 TO UNLOCK THE NEW KEY DID NOT WORK SO I CHECKED THE CAMERA AND SN
HAD CHANGED TO LAMSSMAL0000 IT HAD BEEN RESET
ILL TRY ANOTHER CAMERA TO SEE IF ITS REPEATABLE
TESLAFREAK
01-23-2005 15:24:23

New MessageRE:Success - 1 2 many 4 all (modified 0 times) teslafreak
Profile | Email
yes its repeatable and you dont evin unlock the camera
new camera (opps forgot to record the original sereal no firmware 6510)
hooked up to computer os win xp looked up hardware profile
removed camera from list imagang devices %USB\VID_0DCA$PID_0027.DeviceDisc%
unplugged camera from computer (batteries inside camera)
re plugged in camera found new device wizard pops up
selected che-ez foxz driver in program files and selected liusb0.dll ni windows system 32
finished installing driver and the sn was changed to lamssmal0000
never unlocked camera using forkboys tool at any time
hope this helps
teslafreak
01-24-2005 11:30:38

New MessageRE:Success - 1 2 many 4 all (modified 0 times) teslafreak
Profile | Email
success matched code and found unlock patch for 6510 model 410
use forkboys tool download firmware.bin
to convienent location on computer use hex editor program
change location 68F7 from 01 to 02
change location 6A91 from D to C (cigital)
do not alter any other locations
it will unlock
mabye there are'nt many 6510's out there but i have 3
teslafreak
01-27-2005 17:25:52

New MessageRE:Success - 1 2 many 4 all (modified 0 times) binaryweaver
Profile
Just for kicks, I thought I would try taking the firmware from my blue (the camera without the LCD) and flashing it to the red (my camera with LCD). Well, it worked. My camera with LCD still takes great photos (only the LCD stays black). My red now thinks its a blue. Uhm,.. I think I just downgraded.
02-07-2005 22:05:07

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
binaryweaver, downgrade? was that a new 2F blue firmware or old 28 firmware? Did you end up with a Red that requires upgraded flatfoto drivers? Which PV2Tool are you using? Did you use file upload or complete 16M flash upload?
02-07-2005 23:45:35

New MessageRE:Success - 1 2 many 4 all (modified 0 times) binaryweaver
Profile
I believe it was the firmware from my newer blue. I had it sitting in a directory (didn't pull it directly off the camera) and I didn't label the directory well. Sorry. When I flashed the red (camera with LCD) with the blue firmware, the red basically acted as a blue (no activity whatsoever on the LCD display, but still functioned and took photos just like a blue would). I have since put the original firmware back on the red so I would have LCD functionality again. I was REALLY bored last night and risked frying the camera just to see what would happen. I just uploaded firmware.bin (not the entire 16 meg image).
02-08-2005 21:52:56

New MessageRE:Success - 1 2 many 4 all (modified 0 times) unclebill
Profile
I have 2 red 6430s. One was successfully unlocked and is getting good pics using Che-ez and Irfanview.

The other is in the same condition now but it took some playing to get there. The camera had been accidently "reset" to the LAM****condition but acted different from any I've read about. It required being unlocked each time and would only download 1 picture no matter how many on camera. Forkboy's PV2 tool V2.05 was the only tool that would unlock it. I could not download the flash file though. I accidently left the 1.2 and 2.06 versions of the tool open together and when I hit unlock on v1.2 I was then able to download all pics in camera and was able to download flash file but found the 3xxx-7xxx portion filled with groups of numbers or keyboard characters. I opened up V205 at the same time and was able to download an apparently correct flash file, modify it , and upload it. The camera works like the other one now but neither one shows the change from 27 to 24 on the info screen. The camera had previously been unlockable with the V1.2 but this quit working after a while. I thought the camera was done for but I kept playing and found a combo that worked but I have no clue why. The V2.06 tool gave errors in the flash download on both cameras.

I'm off to get a couple more to play with.

02-09-2005 10:04:42

New MessageRE:Success - 1 2 many 4 all (modified 0 times) brite_eye
Profile
unclebill, Please post your 6430 firmware changes to "2 4 hex 8 Firmware" thread following previous examples. Thanks. Oh and please let me know if you are a Pharmacist.
02-09-2005 18:28:42

New MessageRE:Success - 1 2 many 4 all (modified 0 times) unclebill
Profile
I'm not a pharmacist - official or otherwise. Electrician by trade.
02-10-2005 17:31:48

New MessageRE:Success - 1 2 many 4 all (modified 0 times) Mehoff
Profile
Finally have a couple of working CVS Blues. #1: 65 10 28 28 20 #2: 65 20 28 28 20. Changes the same for both:
0x6991 from 01 to 02
0x6B85 from 28 to 24
0x6BC0 from 30 to 33
Both cameras working great with IrfanView-Che-ez!Fox2 combo. Here are some of the first pictures.

The ‘wall of fame’ in my lair. The GMC badge is all that was left after a close encounter with a very large deer last August.
http://mysite.verizon.net/vze6sg4z/Feb%2013-05_CVS-Blue-09.jpg

No giants doing cartwheels or statues wearing high heels (apologies to CCR) but this is looking out my back door.
http://mysite.verizon.net/vze6sg4z/Feb%2013-05_CVS-Blue-10.jpg
http://mysite.verizon.net/vze6sg4z/Feb%2013-05_CVS-Blue-11.jpg

Hope the links work!

02-15-2005 14:01:23

New MessageRE:Success - 1 2 many 4 all (modified 0 times) mykel27
Profile
Friday night Firmware modification - CVS Red FIRMWARE 6520 06 2B Adapted morcheeba's scripts for his pv2mod tool with the addresses from tango's modification (just unlock and PID) and it worked flawlessly with Drmn4ea's ported win version. Camera is unlocked and recognized as "Che-ez! Foxz2".
02-20-2005 17:16:49

New MessageRE:Success - 1 2 many 4 all (modified 0 times) Mehoff
Profile
I was able to get my hands on the FlatFoto2 driver and finally the blue hues are gone. I now have 3 working CVS Reds. All are 6520-06-T30. One appears to have been recycled and right out of the package had a reset serial#. Still able to unlock with PV2Tool206. Changes to firmware.bin were the same for all: 0x6910 from 01 to 02; 0x6AF4 from 27 to 24; 0x6B30 from 30 to 32. Pictures are a little grainy (as others have said) but are tolerable for snapshots etc. See Photo thread for pictures.
02-21-2005 09:06:17

New MessageRE:Success - 1 2 many 4 all (modified 0 times) tweak
Profile
Got a 6410, after trying to hack the firmware, I get three low beeps when trying to turn on the camera, or when connected to usb. Running the PV2Mod util when I connect I get one beep, but no light... I am unable to unlock... Any suggestions on how I can fix this? Also, what changes need to be made on the 6410 27 firmare.bin file?
03-03-2005 09:23:38

New MessageRE:Success - 1 2 many 4 all (modified 0 times) DanAdamKOF
Profile | Email
I guess y'all might appreciate seeing some new blood here that has a working camera :). Anyhow, it's a red Ritz, vulcan nerve pinch shows 6410, and I'm running it under 98SE. I used a USB cable from a Handspring Visor Deluxe cradle that was $2 at a thrift store and soldered it directly to my camera (it will be used mostly around the house anyway). I started following tango's instructions at first until I realized I was doing it on the wrong type of camera (whoops!). After uninstalling libusb and manually deleting http---libusb-win32.sourceforge.netlibusb.inf, I followed Morcheeba's instructions (except with the windows port of PV2mod) and my camera seems to work fine. I'm using the Foxz drivers, and I've downloaded 13 pictures so far with no problems. I'll post the photos I took in the Photos section now.
03-04-2005 22:56:40

New MessageRE:Success - 1 2 many 4 all (modified 0 times) bubba007
Profile
OK, this might be a repeat/re-collection of previous info, but at least it'll be from a different perspective:

RE: recycled-reissued CVS reds

Here's how I unlocked a couple of 'stubborn' ones:
[assuming CVS red camera 6520 with 3finger info: "Type ID"=30 and "cmp type ID"=30. (although USB id is still 27)]
[assuming windows XP ]

First: check Device Manager for correct driver usage:
If you have a 'Foxz' or 'CVS red' or whatever listed under 'imaging devices' you must un-install it.
The only reference in Device Manager should be to a 'Ritz PV2' under the 'U.S.B. controllers' category (re-install if necessary to ensure - if you have multiple drivers available (like me) pick the 'Ritz PV2')

Second: run PV2MOD in a 'cmd' window using "pv2mod disable-80"; unplug and re-attach usb.

Third: run PV2Tool2 and find/connect/UNLOCK RESET.

This has resulted in success in all 4 I've tried (30/30 models)

03-09-2005 12:19:40

New MessageRE:Success - 1 2 many 4 all (modified 0 times) MicronEye
Profile
Here's more confirmation:

CVS RED Firmware 6430, TypeID 27, HW 06
0x68F9 01->02
0x6ADD 27->24
0x6A93 44->46
using PV2tool2.05, Chee-ez, Ifranview on a pentium win98 2nd ed

CVS RED Firmware 6520, TypeID 30, HW 06
Reset using Teslafreak's procedure to ID LAMSSMAL0000
0x6910 01->02
0x6AF4 27->24
0x6AAA 44->46
using PV2tool2.06, Chee-ez, Ifranview on a pentium win98 2nd ed - unlocked but got the blues!

Granted it took some doing to layer in the libusb files just right (and erase failed attempts), once that is done the steps are pretty straight forward. Here's a few pointers that may help:
If you, like me, wish to keep the original Blue&Silver useable on the same machine, realize you must devote that usb port for reading the unlocked cameras with maushammers's sw or ifranview.
Be sure to utilize another port during the unlocking stages per the instructions.
Your B&S may appear to have been broken half way thru a red unlock process, but will work again with the final drivers (and port) you install for the CVS cameras.
Since I'm working with an old os, you may need to follow instructions carefully to re-try installing libusb by deleting all previous instances of the files - and to eliminate confusion I unplugged all other usb items (back to a serial mouse!) during the installation.
As always there is a learning curve with new sw, and I first didn't observe that pv2tools wrote the latest status out of view in the scroll down window.
Regarding the 6520, pictures were taken before attempting the unlock so the ID reset was necessary.

I posted a sampling of pictures on the photo thread but as ifranview erases the pictures as they are read, I didn't download or post any of the 6520 pics yet (infact, I heldoff posting confirmtion and photos in anticipation of resolving the blues first).

Thanks one and all (morcheeba, forkboy, brite-eye, forkboy, sailpix, mehoff, dakotamod, teslafreak.. and yes, fife, and smal).

03-10-2005 13:42:54

New MessageRE:Success - 1 2 many 4 all (modified 0 times) hmknight
Profile | Email
Successfully modded a Model 410 Firmware 6510, using teslafreak's process.

"use forkboys tool download firmware.bin
to convienent location on computer use hex editor program
change location 68F7 from 01 to 02
change location 6A91 from D to C (cigital)"
This unlocked the camera permanently.

After changing the firmware and uploading to the camera, I then used the 4-line driverx.inf and pasted those into the FlatFoto driver inf file, and can now use Irfanview to download the pictures.

Sample here. http://www.hhost.org/~hmknight/images/cvspv2/cvs01.jpg

Thanks for all your work guys.

03-27-2005 10:49:05

New MessageRE:Success - 1 2 many 4 all (modified 0 times) Paperboy4828
Profile
Successfully modded a defiantly used, abused and reset CVS Model 410 Firmware 6520, ID: 27 using teslafreak's reset to LAMMSSMAL0000 process. After that forkboy’s PV2tool was able to unlock using the "unlock reset" function, and uploaded FIRMWARE.BIN. Next, used billw’s pv2flag to discover likely points of edit, since the typical firmware edit locations did not conform to firmwares I have modded before. Next in the process was to use Tinyhex to edit the firmware at the following locations:

x68F7 01 --> 02 (check sum +1)
x6AD8 27 --> 24 (check sum -3)
=========================
net: -2
change required: +2
so, edit:
x6A91 44 --> 46

Camera works just fine, with Che-ez Foxz / IrfanView… no blues! Thanks to all you folks, the hard work you put in is really apreciated! :D

03-30-2005 22:03:21

New MessageRE:Success - 1 2 many 4 all (modified 0 times) Lincoln_man
Profile
Just purchased Dakota PV2 Red from Wolf Camera online (18.99).
Model 41
Firmware 6430
Hardware 06
Type ID 27
Changed
0x68F9 01>02
0x6ADD 27>24
0x6A93 44>46
Using Vickers CVS Red camera mods I was sucessful in building a cable from a centronics
connecter(parallel cable)and using all the tools called for I sucessfully modded the
camera on first go around.
I am using a modified Che-Ez Foxz2 driver and Irfanview the pictures come out great.
Also I used PV2Tool206 with no problems downloading and flashing the firmware.
Many thanks to all on this board for the info. This is a great place.
Lincoln_man
(Which means I have a 1953 Lincoln)
04-09-2005 12:48:35

New MessageRE:Success - 1 2 many 4 all (modified 0 times) Lincoln_man
Profile
Sorry Model 410
04-09-2005 12:49:51

New MessageNew CVS red Camera 6550 (modified 0 times) astalavista
Profile | Email
I have new cvs camera and firmware versions 6550 , i was try to use pv2tool but its fail, i need some help ?? i have 6520 too ,i have no problem with this model ,

Thank you

04-26-2005 20:13:57

New MessageRE:Success - 1 2 many 4 all (modified 0 times) teslafreak
Profile | Email
INSTERESTING DISCOVERY AFTER LOADING THE COMPLETE FLATFOTO2 DRIVER CD
I CAN NOW DOWNLOAD MY MODIFIED RED 6520 DIRECTLY FROM WINDOWS
ALTOUGH THE PICS COME OUT AS 3.14MB BITMAPS THEY DO APPEAR TO BE
VERY WELL CONVERRSONS OF THE RAWS ALTOUGH YOU HAVE TO USE THE TRAIN DRIVER
TO ERASE THE CAMERA THE DRIVER IS LISTED AS OEM 3.0.5.1
PROVIDER MICROSOFT CORP FILE VERSON 5.1.2600.2180
& LIBUSB 0.1.8.0
HOPE THIS HELPS
ALSO SP2 INSTALLED
TESLAFREAK
PS THE FLATFOTO2 WILL ONLY TRY TO DOWNLOAD PICS THIS WAY
I GET A 9MB FILE WITH 0 BYTES
05-04-2005 22:45:41

Reply to Thread | Printer |
All times are PSTPowered by UltraBoard v1.62



Copyright © 2000, Netmake Inc. All Rights Reserved.
See Terms and Conditions for more information.




i-opener opener laptop notebook computer help drivers dll free windows dos repair fix linux mac macintosh 2000 95 98 nt pc configure hardware software sound video netscape explorer network networking lan wan software cmos fat bios printer card mouse modem ide scsi cd rom controllers scanner tape hard drive cgi scripts source code mp3