Haha, okay. Hmm, well if it's getting as far as that there's no question that ADB is connecting. For some reason, it's just not writing out the files. You're on 4.0.2, I'm sure? (not that it should make a difference), and are you GSM or LTE? I really don't think it should matter; I'm just grasping at straws...
I just tried the same exact command you mentioned; I'm also on Win7 x64; LTE Nexus with 4.0.2; backed up directly to C:/c/backup.ab.
I am running the same setup as you. Would the version of SDK tools and Platform tools matter? I am running Rev 16 and 10 repectively. When I run the comands I am in the C:/ prompt, but that doesnt seem to matter from what I can tell. I am using the USB computer connection of MTP rather than PTP if that matters.
I am still pretty green to this, as the last phone I really messed with was the Eris, and with that it has still been awhile. Things have really come a long way since then.
The versions might matter, but you're on the same revisions I'm on. Now, I will say that I am running from C:/Program Files(x86)/Android/android-sdk/platform-tools/ rather than just the straight C:/ prompt, just because I've been too lazy to add ADB to my system variables. I'm also using MTP, which shouldn't affect it.
Yeah, things have changed quite a bit; going from the Droid line to the Fascinate was my last jump.
The only thing I can think of to try is to make sure that you are running your Command Prompt as Administrator. The fact that it's creating a file at all seems to disprove that this would have an effect, but it's worth a try.
|adb, android, backup, ice-cream-sandwich, restore|
|Thread Tools||Search this Thread|