never tried. I might try when I've got more time, but I'm realllly busy right now and shouldn't even be writing this.

needone: Thanks for -*test*-('")ing! GUI coming soon. ---- Edit: 0.2006.09.23 Unlocks new camcorders Mostly rewritten logging system If you start the GUI from the command line (e.g. "./PureTool.app/Contents/MacOS/PureTool") you can see log output. This is much more useful now because you can change the log level under Preferences. === 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.26

figured i'd post it here too, for all you OS Xers, saturnchallenger for mac forumer.com/viewtopic.php?p=34348#34348" target="_blank">http://camerahacks.10.forumer.com/viewtopic.php?p=34348#34348

I'm sorry, I double posted. See below.

needone: Thanks for -*test*-('")ing! GUI coming soon. ---- Edit: 0.2006.08.26 Unlocks new camcorders Mostly rewritten logging system If you start the GUI from the command line (e.g. \\\\"./PureTool.app/Contents/MacOS/PureTool\\\\") you can see log output. This is much more useful now because you can change the log level under Preferences. Trying that on my computer, and it can't find my camcorder. However, System Profiler shows it. Edit: I got it connected through a hub, but now I'm just seeing this: ERROR : error = e00002ed on bRequest=01 ERROR : request.wLenDone 0 != length 4 ERROR : Error reading challenge (e00002ed) on i=56 And here it is with full debugging information: NOTICE: Debug message level 2 (NOTICE) NOTICE: Debug message level 4 (DEBUG) INFO : Found device 0x65bb DEBUG: Found 1 configurations DEBUG: Found interface: 0x6903 DEBUG: dealWithInterface: found 3 pipes INFO : Found: INFO : Pipe: 1 INFO : Direction: Out INFO : Number: 1 INFO : Transfer Type: Bulk INFO : Max Packet Size: 512 INFO : Interval: 0 INFO : Found: INFO : Pipe: 2 INFO : Direction: In (??) INFO : Number: 1 INFO : Transfer Type: Bulk INFO : Max Packet Size: 512 INFO : Interval: 0 INFO : Found: INFO : Pipe: 3 INFO : Direction: In (??) INFO : Number: 3 INFO : Transfer Type: Bulk INFO : Max Packet Size: 512 INFO : Interval: 0 INFO : dealWithPipes: grabbing BULK IN pipe index 4, number 3 DEBUG: dealWithPipes: pipe maxPacketSize 512 INFO : Input pipe=4, Output pipe=0 INFO : Unlocking WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: a0 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 00 00 00 00 DEBUG: Camera lock query returned 00000000 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 80 00 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 00 00 00 00 INFO : Looks like you have a newer camera, looking for the response in a different place. INFO : Hop to the left... WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 00 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 67 45 23 01 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 04 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: ef cd ab 89 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 08 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 33 22 11 00 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 0c 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 77 66 55 44 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 10 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: bb aa 99 88 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 14 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: ff ee dd cc WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 18 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 11 11 00 00 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 1c 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 33 33 22 22 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 20 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 55 55 44 44 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 24 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 77 77 66 66 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 28 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 99 99 88 88 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 2c 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: bb bb aa aa WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 30 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: dd dd cc cc WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 34 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: ff ff ee ee WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 38 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 00 00 00 00 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 3c 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 11 11 11 11 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 40 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 22 22 22 22 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 44 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 33 33 33 33 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 48 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 44 44 44 44 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 4c 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 55 55 55 55 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 50 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 66 66 66 66 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 54 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 77 77 77 77 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 58 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 88 88 88 88 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 5c 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 99 99 99 99 WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 60 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: aa aa aa aa WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 64 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: bb bb bb bb WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 68 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: cc cc cc cc WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 6c 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: dd dd dd dd WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 70 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: ee ee ee ee WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 74 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: ff ff ff ff WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 78 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 55 aa 55 aa WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: 7c 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: ef be ad de WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 00 01 00 00 67 45 23 01 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 04 01 00 00 ef cd ab 89 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 08 01 00 00 33 22 11 00 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 0c 01 00 00 77 66 55 44 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 10 01 00 00 bb aa 99 88 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 14 01 00 00 ff ee dd cc WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 18 01 00 00 11 11 00 00 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 1c 01 00 00 33 33 22 22 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 20 01 00 00 55 55 44 44 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 24 01 00 00 77 77 66 66 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 28 01 00 00 99 99 88 88 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 2c 01 00 00 bb bb aa aa WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 30 01 00 00 dd dd cc cc WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 34 01 00 00 ff ff ee ee WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 38 01 00 00 00 00 00 00 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 3c 01 00 00 11 11 11 11 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 40 01 00 00 22 22 22 22 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 44 01 00 00 33 33 33 33 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 48 01 00 00 44 44 44 44 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 4c 01 00 00 55 55 55 55 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 50 01 00 00 66 66 66 66 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 54 01 00 00 77 77 77 77 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 58 01 00 00 88 88 88 88 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 5c 01 00 00 99 99 99 99 WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 60 01 00 00 aa aa aa aa WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 64 01 00 00 bb bb bb bb WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 68 01 00 00 cc cc cc cc WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 6c 01 00 00 dd dd dd dd WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 70 01 00 00 ee ee ee ee WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 74 01 00 00 ff ff ff ff WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 78 01 00 00 55 aa 55 aa WRITE: bReq=01 val=fa01 idx=0101, 8 bytes -> err=0 data: 7c 01 00 00 ef be ad de WRITE: bReq=01 val=fe01 idx=0101, 4 bytes -> err=0 data: a0 01 00 00 READ: bReq=01 val=ff01 idx=ffff, 4 bytes -> err=0 data: 01 00 00 00 INFO : Camera lock query returned 00000001 NOTICE: Camcorder successfully unlocked! WRITE: bReq=01 val=bf00 idx=0000, 4 bytes -> err=e00002ed (0 actual bytes) data: 00 00 00 00 ERROR : Unable to change to partition 0 (e00002ed)

Bahro: Your error messages are not consistent, suggesting a hardware problem. The first error snippet is a failure during authentication, the second shows your camera unlocking but failing right after that. In both cases the error number is "kIOReturnNotResponding". Are you sure the cable is good? Have you been able to use your camcorder/cable with other computers/programs?

Hey! It works with a different USB Hub. That's strange. Thank you! EDIT: It doesn't work in a Belkin USB 2.0 hub, though it does in a USB 1.1 hub. It also isn't even recognized in my PowerBook's USB 2.0 port. Any ideas?

Bahro: I'd still suspect a flaky or marginal cable; my camcorder has worked in my iBook's USB 2.0 ports. As a wild guess, I'd say that the 1.1 hub is forcing the slow transfer speed, which (may be) more reliable due to longer data bursts and more noise immunity. When you try to use a 2.0 port the camcorder tries to send data faster but the signal quality isn't good enough, so the connection is lost.

>0.2006.08.26 >Unlocks new camcorders >Mostly rewritten logging system >If you start the GUI from the command line (e.g. >\\\\"./PureTool.app/Contents/MacOS/PureTool\\\\") you can see log >output. This is much more useful now because you can change the log >level under Preferences. Ok, I don't see how this is supposed to operate. There's nothing in the readme but a changelog. 230 53.12, camera is seen, get config gives" unexpected" bitrate, framterate, " etc etc. The locked/unlocked setting seems to change nothing. As the dialogs say to fix this by choosing settings for each of the things that are unexpected, and writing them, unplug/ power down/ replug, I've done that, to no effect. Somewhere it seems like a logfile is being generated but I don't know where, it's not readily apparent. I can't seem to run this from commandline even though I give the location it's in (as reported by ls -l). Do I have to use a Windows box first or only? How many people here are using this successfully with their OS X machines? I looked for more info in the archives related to puretool and walkthru but the search engine for the forums generates a lot of not-relevant hits, and I haven't found it yet, if it's present. Thanks for help; Brian

I've never tried to use a locked M220/M230 camcorder with a Mac. All my attempts were with ones that had been previously set to the "reset key" on a Windows XP system.

@toomanyhandles, first you need to be in the directory of saturnchallenger. then run the run-me-only.sh or compile sc7.0 for the output to be in the right area.

=\"GotAnMP3\">I've never tried to use a locked M220/M230 camcorder with a Mac. All my attempts were with ones that had been previously set to the \"reset key\" on a Windows XP system. Then what is the point of the locked/unlocked setting? Thanks for the app anyway, it's good to see Mac stuff. To summarize: I tried to unlock this 53.12 on 2 PCs, are we SURE PD has not fouled up the methods listed here for new cams? 2 PCs OPS doesn't work, whether from sourceforge manual install with the libUSB, or with the oneclicksetup app. Cable is now purchased, I figured my problems were due to the fact that although I can surface mount solder, something I was doing was killing the darn thing. Nope. The cam is now a pile of plastic shards, I just bought one on ebay unlocked, for less than I could buy it in the store, even considering shipping. Same goes for the cable, if I'd looked- a Palm m100 cable plus killing a USB cable = just buy one on ebay, you save $. This paragraph of info should be a sticky. The info on these forums is great but for you guys who have been here forever, there is NO sense of narrative, missing docs, and incomplete FAQs. Nothing is complete. Example, try and find what a \"model 34\" camera is. It's talked about all the time, it's not in a FAQ, I've smashed 2 cams now, and nowhere in the powerup, in the firmware display, or on the innards, was readily found \"model 34\". Dittoe for \"model 410\" still camera. Another: A link to saturntools (mac) is in the recent posts but when, looking around and around when the software doesn't work, oh it doesn't WORK on current cams- but there was no mention of that in its docs, and you would never have found that info unless looking in threads in other forums- and again, not in the post where the app is mentioned. Not do mean I don't appreciate the authors effort, far from it, but some useful readme would be nice. New users CAN'T TELL. I don't know where you guys are buying the old cams but 2 stores here only have 230 (53.05 or 53.12, together on the shelves). I don't mean this to dis the forum, or the contributors or authors, it's great and without it I'd never have got so mad at a piece of white plastic and got tools off my workbench so I could use my vise :) but needed info is just not findable, and the search feature is amazingly not helpful, pulling up post after post without the keywords being searched for present in the post. People were griping in a recent thread about newbies asking the same questions over and over- it's because the answers are just totally buried. And often you can't tell current info from outdated info. Even in the program documentation. I'd add to the FAQs if I could figure out how to get one of these darn things working from scratch. But I don't think I will be able to do that at this point. My contribution would be to suggust the above paragraph re: Just Buy It. Not mad, just frustrated :)

PureDigital's actions have put something of a damper on the progress towards writing a decent How-To. The gist of it is that if you have: The la-*test*-('") version of OPS for Saturns (camcorders) and the la-*test*-('") version of PV2Tool for PV2s (still cameras) AND A challenge to response generator Then ALL models and firmwares are unlockable, except for the new M510 still cameras. To be honest, progress on the Mac side of things has been very sluggish, and if you're not accustomed to doing battle with drivers on Windows XP, things can get very frustrating.

=\"enigma-\">@toomanyhandles, first you need to be in the directory of saturnchallenger. then run the run-me-only.sh or compile sc7.0 for the output to be in the right area. Thanks, but I thought I saw a thread linked to from the thread in this Mac-related thread, that said the Saturnchallenger didn't work on 230's? Is that outdated?