Sorry, I meant to fill you in before I skitterred off for some holiday pleasantries. The ADP and SDK went on as a singular unit, however Google packages them for distribution. Since I was using either the last of the versions of the releases in the 6.xx series of Java SDKs, or else the very latest of version 7 Java SDK, the Android Debug Bridge (more hits for other n00bs wondering "WTF is ADB" right there), so it started off rather stickily as I had to click through an ominous-seeming "Yes, I do have JSK or JDK or whatever it's called that I need" "... Are you sure? People you love may die if you make the wrong decision. Is Java cool or isn't it? If you called the cops, the deal's off, the phone is dead. " / "No, I don't have Java SDK 6 or 7 yet. I'll be right here next time we do business, everything's cool, man! "- triad of buttons. Eventually I chose the "pretend you've got JSDK set up just like we said, or else don't blame us... " button & proceeded to compile stuff.
It took a while to compile... Whatever I compiled. I would have to look back through again. But the ADP/SDK kit seemed a functional whole, until I started trying to get the system to recognize my phone. At some point it started to get social. I came back to my workstation to find that the phone showed up as a generic ADP modem-y thing under Device Manager. Perhaps more interesting? Previous driver? A Motorola OEM one. I have the name elsewhere.
I never did get ADP to identify anything attached to the PC, although the computer itself has identified stuff for sure, & knows what it is. I also have a virginal Ubuntu 11.10 x64 system to go swimming around with if need be.
That's just the "A" menu of stuff! When I tried something from the "B" list of boot options, Windows installed 5 or 6 different interface protocols. It was groping around trying to communicate with something it didn't quite understand the subtleties of as a being. (Images, rather naughty, of Windows getting jabbed, kicked, spit upon, & otherwise treated like I usually do whenever members of the opposite sex come nearby. Or tourists fresh off busses from overseas. I feel like the second part of the menu might have the answer i'm looking for, after all, which is to get that "sd" data off intact[ish] of my DROID3. For those just tuning in, my phone went meta-brick, it wouldn't even accept a factory reset. This great new DROID3 is a suitable replacement; it's only that there's proprietary data & stuff that it's easier to try and learn how to vivisection your dying DROID than it is to hire a professional or end up in a state hospital/jail after VZW's conceptual-art installation about the contemptuousness with which modern late capitalism has inured the worker to accept as normal. I don't know what that last part meant, kudos to anyone who can explain it to me in the morning.
Point is, I want my /sd/ stuff relatively intact & i don't care how!
Sent from my DROID3 using DroidForums