PV2Tool

Ok, I'll bend, so long as not finding the .ini in the current directory isn't an error condition. (just a condition for "camera info" to work)

That's fair - I like things to be "bulletproof" if possible... handling errors gracefully. BTW, that's part of the next pv2raw code release - detection and graceful handling of errors, where I can.

Had some slack time today, so I released pv2tool 2.09 Changes from PV2Tool from 2.0.8 to 2.09 ---------------------------------------- -Now only one "Unlock" button. Unlock now gets the challenge from the camera and replies with the correct response if it's known. -Added key from my stubborn 6520-T2B -Added "Patch FIRMWARE" button, and ported a simple version of the pv2patch engine. -Added "Upload File to /" button. Useful when "Get/Refresh File listing" doesn't work. -Increase timeout for "Take a pic". -Fixed logging so logs from CCamera methods were actually displayed. -Fixed the versioning of pv2tool back to 2 parts. What was I thinking?!? ;)

That was fast. Now how about a 2.09.1? I can wait for 2.10, but would like to hex edit firmware with many minor changes and depend on upload to produce correct checksums. Sorry for late notice. No pressure free FF2 will be in your hands shortly no matter what you release. All 4 of my $11 dead FF2s are now taking pictures. Is this another opportunity for you to use my time machine (am I asking for something that already exists)?

I can wait for 2.10, but would like to hex edit firmware with many minor changes and depend on upload to produce correct checksums. Now he tells me! :) The feature doesn't yet exist, but it makes sense to add it in. I'll write a function that checks FIRMWARE.BIN uploads from both the "upload file" and the "upload to /" buttons, and offers to adjust if checksum is bad. All 4 of my $11 dead FF2s are now taking pictures. I really need to take a break. I read that as "All 4 of my 17 dead..." :P

Released another pv2tool to the sourceforge site... Sorry for back to back releases, but I didn't want to sit on the new response/challenge key donated by codeknowbi. Here's the changelog for 2.10 Changes from PV2Tool from 2.09 to 2.10 ---------------------------------------- -Added optional checksum fixing to uploaded FIRMWARE.BIN files. Works on both file upload buttons. -Added "Preview TFT on computer" button. Incorporated part of Forkboy's TFT Utility as engine. -Added codeknowbi's 6550 challenge and response keys. -Added twill.pv2 and nvramparser to new utilities subdirectory. twill.pv2 can be used to -*test*-('") "Run PV2 Code". nvramparser can be used to extract keys from NVRAM.DAT. On a personal note, I'm starting to burn out on pv2tool, so I'll be taking a break from it for at least a few weeks. (except to lend a hand with your "info" screen sailpix). Feel free to still submit ideas here though, I'll get to them after the break. Ditto if someone wants to submit patches to the source. Also, please report here if codeknowbi's encryption key works to unlock your 6550.

Wow... do you ever sleep? :lol:

2.10 works for the 6550 camera the key was extracted from. but not the other 6550 that I bought at the same time. I pulled them from different pegs at the store. I will dissassemble/short ... to get its keys, eventually. If others verify that the new key unlocks any other 6550. I'll do it sooner.

My 6520/28 Blue doesn't seem to behave under PV2Tool 1.10. If I plug in a Red and hit "Patch Firmware" I get the download/success/upload/success string of messages. But with the Blue I only get as far as "Downloading" The program doesn't freeze up, but it doesn't say that it didn't succeed either. And it doesn't get permanently unlocked. BillW, when you have a chance, could you elaborate on what's happening at that point? This little $8 is certainly giving me a run for the money...

You may want to just download firmware, then hex edit and change 01 to 02 at location 6991 as long as it is preceded by E0 and followed by C8. Then upload firmware - pv2tool will take care of checksum.

... said suggesstion working perfectly fine, of course! :oops: Thanks!

It seems that the blue camera may have significantly different code surrounding the patch location. I have a new blue, so I'll see if I can get pv2patch/pv2tool to work reliably with it. If anybody else has the same problems, suggest you follow brite's directions or if your firmware is different check out the patches at forkboy's site.

2.10 doesn't work for my 6550s
i wasn't able to unlock my 6550 camera with 2.10, my cameras information: 6550 06 2b 2b db1051602641 20 -mha

Yeah, this is the second report of a 6550 not unlocking with 2.10, despite the harvested 6550 key. The other report was codeknowbi, who bought 2 6550 cameras at the same time. He cracked the key out of one, and it's key (incorporated into pv2tool) didn't unlock the other. It looks like Pure Digital has tightened things up a bit. It's unknown if the keys are now unique to each camera, batch, month, or whatever. It's starting to look like the hardware method for unlocking cameras is going to be the only way to get at 6550 cameras, at least for the short term. Check out the HOWTO section for more details. If anybody else unlocks a 6550 using the hardware method, I'll accept and incorporate donated keys in pv2tool.

I have 4 6550's that won't unlock with codeknowbi's 6550 key.Maybe the key is specific to something in the ID #'s ?Here's mine, db 605 160 2978 , db 605 160 1213 , db 605 130 4640 , db 205 160 2992 I got them from 4 different stores in about a forty mile radius.

View Full Version: PV2Tool