No, makbomb is on a Mac and I don't have a Mac so I don't use or have a compatible binary. From the looks of it, the ADB binary in that handy package linked earlier may be too far old (2012) to work with our 4.4.2 phones. That would certainly match up with the error message you're getting, makbomb, but it's not unusual for development tools to have misleading error messages, so we'll see. As for the PATH variable, that is mainly a Windows issue; I doubt that is the problem you're having.
I'm sorry this has been so much trouble for you, makbomb. I get the feeling when we sort it out, it will have been something embarrassingly simple (embarrassing for me, for not realizing it sooner).
If you'd like to try this first (and haven't already), you can try running the commands directly as shown in my previous post, just to see if that has any effect, but after all the time you've put into trying to get this to work, installing the full Android SDK seems like a lot less of an inconvenience than it once did. When you're ready, let's remove your existing, outdated adb and fastboot files, since they aren't doing you any good anyway:
Code:
adb kill-server # ok for this to fail
sudo rm /usr/bin/adb
sudo rm /usr/bin/fastboot
Code:
chmod +x INSTALL.sh scripts/*Please try that link and see if it works for you. Once installed, relaunch a Terminal window and see if you can list your device with 'adb devices'; also see if you can get a shell with 'adb shell' (if you can, type 'exit' to leave it). Those things being true, you should definitely be ready to root, so anything standing in your way is likely a script issue, which means you should try the advice in my previous post again, now that you've got a working adb installed.
