- Aug 15, 2011
Here's some extra detail:I'mma ask what version of windows? I did mine on 8.1.... did you run it as administrator?(usually anything firmware related everything should run as admin).... without the phone connected it should say waiting for device.... possibly do the command from inside the folder containing ADB; maybe you have another copy floating somewhere that has priority? ..... sidenote I believe I'm using what came with SkipSoft Unified Android Toolkit so might try installing that???
- Windows 10/Linux Mint 20
- Ran as admin
- It did say <waiting for device> when no device was connected
- All command lines were mapped to the root folder
- I'm not sure about another copy with priority, but after I rebooted both computers with nothing else running, I still got this issue
- For Windows i'm using the 15 second installer, which other people in this forum said worked to fix this problem, so I don't think that's the issue
I appreciate your help very much!