-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Help ADB Question
- Thread starter Lana30
- Start date
In what context are you seeing the "The system cannot find the file specified"?
That sounds like an MS/Windows error message...knowing where you saw this would help a lot.
In order to use adb on a device, it (the Android device) would have had USB debugging previously enabled--which is near impossible to do on a device with a dead touch screen.
That sounds like an MS/Windows error message...knowing where you saw this would help a lot.
In order to use adb on a device, it (the Android device) would have had USB debugging previously enabled--which is near impossible to do on a device with a dead touch screen.
Lana30,
I've merged your two threads together...it's a good practice to keep/continue with one related thread if you can and this one certainly seems to fit that bill
.
To clarify your most recent question (and please note my other questions to you above in the original post), "adb devices" will only show and connect to an Android device if:
- you have USB debugging already enabled
- your Android device is connected via a good, working USB cable to your PC
- you have the proper adb USB drivers on your PC (Linux being much more tolerant about this; Windows more strict)
- edit: also, you also might have to "grant" / allow your device to have "USB debugging authorization" (you should get a pop-up asking if you want to allow your PC (it'sMAC address RSA fingerprint will be listed) to have adb access)
So, disabling USB debugging will ensure that adb devices will not recognize your device, and not the other way around.
I've merged your two threads together...it's a good practice to keep/continue with one related thread if you can and this one certainly seems to fit that bill
.To clarify your most recent question (and please note my other questions to you above in the original post), "adb devices" will only show and connect to an Android device if:
- you have USB debugging already enabled
- your Android device is connected via a good, working USB cable to your PC
- you have the proper adb USB drivers on your PC (Linux being much more tolerant about this; Windows more strict)
- edit: also, you also might have to "grant" / allow your device to have "USB debugging authorization" (you should get a pop-up asking if you want to allow your PC (it's
So, disabling USB debugging will ensure that adb devices will not recognize your device, and not the other way around.
Last edited:
Lana30
Android Enthusiast
Ohhhhh, so if he wants his phone to be recognized that last thing he wants to do is to disable USB debugging, right? So why was I told before that disabling would fix the issue?Lana30,
I've merged your two threads together...it's a good practice to keep/continue with one related thread if you can and this one certainly seems to fit that bill
To clarify your most recent question (and please note my other questions to you above in the original post), "adb devices" will only show and connect to an Android device if:
- you have USB debugging already enabled
- your Android device is connected via a good, working USB cable to your PC
- you have the proper adb USB drivers on your PC (Linux being much more tolerant about this; Windows more strict)
So, disabling USB debugging will ensure that adb devices will not recognize your device, and not the other way around.
LOL, yes, that would indeed be the last thing you'd want to do if you wanted to use adb
.Not sure about who/why might have told you to disable it (hope it wasn't me
).
Lana30
Android Enthusiast
ha ha, No, I know it wasn´t you. This is going to be my friends face when I tell him I was wrong....
...nah, but he might think twice before taking my advice, ha ha. . So then the only solutions that are left are:
- your Android device is connected via a good, working USB cable to your PC
- you have the proper adb USB drivers on your PC (Linux being much more tolerant about this; Windows more strict)
Right?
...nah, but he might think twice before taking my advice, ha ha. . So then the only solutions that are left are:- your Android device is connected via a good, working USB cable to your PC
- you have the proper adb USB drivers on your PC (Linux being much more tolerant about this; Windows more strict)
Right?
This is often overlooked and i'd bet dollars to donuts that this is why your friend can't adb to recognize the phone. It's actively blocking the connection.
Lana30
Android Enthusiast
What is blocking it and how to make it stop doing that?
What is blocking it and how to make it stop doing that?
You should get a pop-up similar to this when you've properly connected your device (i.e., connected, good USB drivers, enabled USB debugging):
Press "OK" to allow this particular computer to have adb / USB debugging access to your Android device.
Lana30
Android Enthusiast
You should get a pop-up similar to this when you've properly connected your device (i.e., connected, good USB drivers, enabled USB debugging):
Press "OK" to allow this particular computer to have adb / USB debugging access to your Android device.
Oh, OK, but do you know what lunatic59 meant by something is actively blocking it?
Lana30
Android Enthusiast
Oh I see, he wasn´t too generous on the details, but he probably saw this notice dismissed it or canceled it and that is why he is going through all this drama, and now what he need to do is disable it so he can enable it again, but that is what he can´t do, disable it. So, is there anything that can be done from here?I was going to say that
Be careful though, if you cancel or dismiss the notification, the phone remembers it and you won't see it again unless you disable debugging and then re-enable it. Perhaps that's what your friend meant?
Hmmm. I'm not sure how you would be able to authorize access with a dead screen. In this scenario, the person would have had to have debugging enabled and access authorized prior to the screen going all kerflooey (sorry for the technical jargon ).
Now when you say "dead screen" do you mean all dead (as in completely off ... no image etc?) or mostly dead (as in not responding to touches.) With the latter you might be able to get debugging disabled/re-enabled by connecting an OGT mouse if the phone supports it. With all dead, all you can do is go through his pockets and look for loose change.
). Now when you say "dead screen" do you mean all dead (as in completely off ... no image etc?) or mostly dead (as in not responding to touches.) With the latter you might be able to get debugging disabled/re-enabled by connecting an OGT mouse if the phone supports it. With all dead, all you can do is go through his pockets and look for loose change.
Lana30
Android Enthusiast
I´ll ask to see how dead the screen is, but I don´t think that he is going to be too happy to hear that without USB debugging on in the first place, there is nothing that can be done with a no image dead screen, but oh well, we can´t always get what we want. I actually like all he technical jargon, I love learning about his stuff, that is why I try to be my friends ¨Android Expert¨, but with help from the real experts, ha ha. I´m a fake!! ha ha.Hmmm. I'm not sure how you would be able to authorize access with a dead screen. In this scenario, the person would have had to have debugging enabled and access authorized prior to the screen going all kerflooey (sorry for the technical jargon
Now when you say "dead screen" do you mean all dead (as in completely off ... no image etc?) or mostly dead (as in not responding to touches.) With the latter you might be able to get debugging disabled/re-enabled by connecting an OGT mouse if the phone supports it. With all dead, all you can do is go through his pockets and look for loose change.
I try to ask related questions to threads I have already posted and I try to look for threads in my history, but it only goes so far. Is there a way to see all the threads that I have started since signing up?
Yep!
Go to your "profile page" (http://androidforums.com/members/lana30.1878079/) (i.e., click on your username, find the "Profile Page" link (same one as I just provided) and then look in the Postings or Recent Activity tabs.
At the bottom of those pages/tabs, you'll also see a "Find all content by Lana30" and "Find all threads by Lana30" links that you can see all of our posts/threads.
Lana30
Android Enthusiast
Great, thank you. I sometimes want to ask something new, but on something that Ia already started and I don´t want to clutter things up by asking the same thing twice and give you guys more work.Yep!
Go to your "profile page" (http://androidforums.com/members/lana30.1878079/) (i.e., click on your username, find the "Profile Page" link (same one as I just provided) and then look in the Postings or Recent Activity tabs.
At the bottom of those pages/tabs, you'll also see a "Find all content by Lana30" and "Find all threads by Lana30" links that you can see all of our posts/threads.
Lana30
Android Enthusiast
Did I understand correctly, if the screen is 100% no image dead and the USB debugging was not turned on, there is nothing that can be donde?Yep!
Go to your "profile page" (http://androidforums.com/members/lana30.1878079/) (i.e., click on your username, find the "Profile Page" link (same one as I just provided) and then look in the Postings or Recent Activity tabs.
At the bottom of those pages/tabs, you'll also see a "Find all content by Lana30" and "Find all threads by Lana30" links that you can see all of our posts/threads.
Pretty much...however, as @lunatic59 mentioned above, if the device supports an on-the-go cable and mouse (see this page http://joyofandroid.com/unlock-android-device-with-cracked-or-broken-screen/ under "Method 2: USB On the Go Mouse", you might be able enable it that way.
Also, if the device has an unlockable bootloader and a custom recovery can be installed (or softbooted) via fastboot, then you have might have a few other options--not as simple or as straightforward as the above, though.
Lana30
Android Enthusiast
The screen is entirely black but still has tactile feedback whenever the screen is touched and you can still say turn off an alarm that goes off (that was on before the phone broke).Hmmm. I'm not sure how you would be able to authorize access with a dead screen. In this scenario, the person would have had to have debugging enabled and access authorized prior to the screen going all kerflooey (sorry for the technical jargon
Now when you say "dead screen" do you mean all dead (as in completely off ... no image etc?) or mostly dead (as in not responding to touches.) With the latter you might be able to get debugging disabled/re-enabled by connecting an OGT mouse if the phone supports it. With all dead, all you can do is go through his pockets and look for loose change.
Lana30
Android Enthusiast
Hi, It´s Galaxy S4.What kind of phone is it? Sometimes new screens are surprisingly cheap and easy to replace yourself.
Of course, other times they require 56 special tools, 12 days of work and the flexibility of an octopus.
Lana30
Android Enthusiast
That´s my friend issue, ha ha. So the best choice would be to replace the screen then?Looks like the kits are about $80 on Amazon/eBay. You have to make very sure about the models because Samsung has about 57 flavors of the S4.