M230-compatible Mac application?

needone: If you see the "Camcorder still locked, WTF?" message, you don't need to wait - there's no chance it'll work. Actually, if it succeeds you shouldn't need to wait either. No need to post the entire transcript, I just need about 10 lines after "Camera lock query returned 00000000". The log you just posted looks weird, I expected to see some info about the first response - it doesn't look like my changes got through. Trying again... http://koiproductions.net/PureTool%20alpha%200.2006.09.23.zip brite_eye: I was only a student and I just graduated, so I think it's a bit of a stretch to say that you have the support of MIT :) Besides, I've been here a while... === Edit (2006.09.24): My school account is expiring soon, so I'm updating the URL, and pointing at a newer version. The original post references version 0.2006.08.02-2

Even more amazing - we have the support of a recent MIT graduate!

needone: If you see the "Camcorder still locked, WTF?" message, you don't need to wait - there's no chance it'll work. Actually, if it succeeds you shouldn't need to wait either. No need to post the entire transcript, I just need about 10 lines after "Camera lock query returned 00000000". The log you just posted looks weird, I expected to see some info about the first response - it doesn't look like my changes got through. Trying again... An all zero challenge is the same exact thing that happens when you try to unlock an M220 or newer camcorder on any version of OPS that doesn't support it. Maybe you can compare the differences in the unlocking routines between OPS 0.14 and OPS 0.15 (the first version with support for the M220).

GotAnMP3: As I recall, the slowness is caused by MacOS X actually respecting the maximum request size reported by the camera, or something like that. The same is said to be true of Linux - predictably, only Windows lets you mess with something like that (not necessarily a good thing in general). Well in this case, a bug in Windows turns out to truly be a feature. No one likes waiting extra long for his videos to download... :roll:

Frozen in same place:

Camera lock query returned 00000000
Camcorder still locked, WTF?
Getting info: changing to partition 3
WRITE: bReq=01 val=bf03 idx=0000, 4 bytes ->  err=e0004051 (0 actual bytes)  data: 00 00 00 00 
Getting info: changing to "/"
Changing to '/'
WRITE: bReq=01 val=b800 idx=0101, 2 bytes ->  err=e0004051 (0 actual bytes)  data: 2f 00 
Getting info: downloading usp.bin (max 4096 bytes)
WRITE: bReq=01 val=b101 idx=0101, 8 bytes ->  err=e0004051 (0 actual bytes)  data: 55 53 50 2e 42 49 4e 00 
WRITE: bReq=01 val=b901 idx=0101, 0 bytes ->  err=0  data:

brite_eye: Awww, you're flattering me :) GotAnMP3: Already did that. It's actually an all zero response that's the problem, the challenge was not used at all in earlier cameras. Now it appears that you want to return the "challenge" instead of the "response". The 0.2006.08.02 builds implemented this. Even if I misread the algorithm, there's still something else going on - see comments to needone needone: If the build had worked correctly, you should have seen an additional message: "0 - response of " followed by a number, possibly followed by another new message about trying the new scheme. The lack of all the WRITE and READ entries from before is very puzzling - they should still be there. This makes me think my build settings are wrong or your environment is messed up. What kind of computer do you have? New build with prebinding disabled in case that was the problem: http://koiproductions.net/PureTool%20alpha%200.2006.09.23.zip - if it doesn't work, please PM me the entire transcript. === Edit (2006.09.24): My school account is expiring soon, so I'm updating the URL, and pointing at a newer version. The original post references version 0.2006.08.03

I'll try that tomorrow, I was just going to go to sleep. I'm on an iMac G5 17" Rev. B 1.8GHz/10.4.7/Combo/Airport and Bluetooth installed but not on (I use the built-in wired Ethernet to ensure my downloads are what they were intended to be.) Would it help if I reinstalled OSX? I've been meaning to do it for a while. I could try it on my mac mini before you go through all the trouble of a reinstall. Honestly though, I remember the M220 was giving BillW some fits back when he was updating OPS. I'd be willing to donate a M230 to the cause of getting a working OS X camcorder app - but considering how slow it downloads on a M200 3.40 when mass storage mode isn't enabled, I wouldn't really consider it a complete solution until someone manages to tackle the USB speed issue as well. I have a few family members who are exclusive Mac users, so they'd greatly appreciate being able to upgrade to a higher quality M220/M230 camcorder. As for myself, I use both but I actually prefer Windows. Evil, yes, I know. :twisted:

It's actually an all zero response that's the problem, Only the early 3.40 camcorders allowed reading response. After that you needed to either force a reset key from FSP.BIN by shorting flash, read directly from flash, or obtain key through other unsupported methods. As of about 7 months ago PD replaced known reset key in FSP.BIN with the same key as is in USP.BIN. On model 220 and above both the challenge and response have been offset by an additional 256 bytes.

Small addition to brite's note: when you add 256 to the challenge and response locations the unlock code still works fine with 3.40 cams, because the extra 256 eventually gets masked off in the firmware.

brite_eye's and BillW's explanations pretty much match what I saw, so once the new code's actually getting executed we should be good to go. Thanks for clearing the new scheme up. GotAnMP3: No, not evil - people have different preferences, and since you've tried both, you're ahead of many others in my book. Best tool for the job and all that. Now, dubious taste, maybe... :D

... stuck in same location. I'll let it sit for a few more minutes then I'll fire off a PM to you, koikoi.

Ah, but this time the new code's being executed and there's actually data being returned. I missed the part about the response needing an offset (I should really code when I'm more awake and diff against the correct version), hopefully this will do the trick: http://koiproductions.net/PureTool%20alpha%200.2006.09.23.zip === Edit (2006.09.24): My school account is expiring soon, so I'm updating the URL, and pointing at a newer version. The original post references version 0.2006.08.03-2

View Full Version: M230-compatible Mac application?