This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
I'm looking in the utils directory right now. adb is not in there. The only things in there are 7za.exe, CDTParser, exe, fciv.exe, and sa-md5sum. I just re-ran the 7.0 installer and adb is still not in there.
And as Dave said, it makes no sense that adb is not running because it is actually installed. I can run adb at the command line from the root, from /users/xxx, etc. I don't understand why adb is not being installed in the utils directory.
LMAO - I use HoB quite a bit, but only look at the code from time to time. I should know better though, if there's any way to avoid an ID-10-T error, it's probably coded into the HoB by now.
I'm looking in the utils directory right now. adb is not in there. The only things in there are 7za.exe, CDTParser, exe, fciv.exe, and sa-md5sum. I just re-ran the 7.0 installer and adb is still not in there.
And as Dave said, it makes no sense that adb is not running because it is actually installed. I can run adb at the command line from the root, from /users/xxx, etc. I don't understand why adb is not being installed in the utils directory.
LMAO - I use HoB quite a bit, but only look at the code from time to time. I should know better though, if there's any way to avoid an ID-10-T error, it's probably coded into the HoB by now.
I'm looking in the utils directory right now. adb is not in there. The only things in there are 7za.exe, CDTParser, exe, fciv.exe, and sa-md5sum. I just re-ran the 7.0 installer and adb is still not in there.
And as Dave said, it makes no sense that adb is not running because it is actually installed. I can run adb at the command line from the root, from /users/xxx, etc. I don't understand why adb is not being installed in the utils directory.
Actually, it does make sense if you look at the batch file. It sets up a variable called %UTILS% and the ADB command is explicitly referenced to run from that exact location. So in this case, it doesn't care that you have the SDK installed and adb is in your path statement.
Sort of like if I am trying to run "C:\files\runme.bat" it's not going to run "C:\otherfiles\runme.bat" - even if I have "C:\otherfiles\runme.bat" in my path, it's still going to give an error if I try running "C:\files\runme.bat" and that particular "runme.bat" file doesn't exist. A direct path reference always overrides the PATH environment variable.
Actually, it does make sense if you look at the batch file. It sets up a variable called %UTILS% and the ADB command is explicitly referenced to run from that exact location. So in this case, it doesn't care that you have the SDK installed and adb is in your path statement.
Sort of like if I am trying to run "C:\files\runme.bat" it's not going to run "C:\otherfiles\runme.bat" - even if I have "C:\otherfiles\runme.bat" in my path, it's still going to give an error if I try running "C:\files\runme.bat" and that particular "runme.bat" file doesn't exist. A direct path reference always overrides the PATH environment variable.