Related
So, I've been fiddling with the USB drivers and I still can't get it working properly.
ADB and windows (through explorer) will constantly drop out randomly and reconnect automatically.
Most of the times I connect my device, it's detected but is not shown in 'my computer' screen (cannot access its storage).
Thus, I can't actually copy files to it (unless through wifi).
What files should I delete to start the driver installation again? I have forcefully disabled windows update and I just want the ADB terminal to work.
Possibly relevant details:
- Using temasek's CM10.2
- USB debugging is enabled
- I sometimes use UMS mode.
- Tried using several cables.
- You can assume it's a fresh windows installation.
Hey guys.
I have Samsung galaxy ace 5839i (stock for 5830i) and I am using it for a few years, but this problem came for the first time.
Always, when I try to connect my mobile to pc using cable, it just won't connect, it won't even show me the notification of connecting.
Before this problem, I connected it to fedora linux and it was succesful, but now? It won't show me that USB sign even in windows.
Any help?
Thanks in advance
@LiQuDiAk, basically s5839i and s5830 i are identical in many areas ,, few questions though,, did you root your device or you are on android 2.3.6 stock version / kernel 2.6.35.7 ?
when you are in your windows device manager ( while you are connected , do you see any exclamation / question marks in front of the corresponding driver), you can always uninstall your old driver, reboot , then try compiled driver in attachment , and reboot to take proper effect in your registry (tested on win xp/7 -32bit) . Also check your device settings>Application>Development > USB Debugging and make sure the option is checked. now lets check your debugging mode through ADB command and see if your device is being recognized. download platform zip attachment, unzip it and put the folder someplace like your desktop. Now open your command prompt (cmd) through whatever means you are comfortable and change directory (cd) to the unzip folder or simply open your folder and drag/drop adb.exe into your CMD to be in the right place very fast. Then type "adb devices" without quotation marks and report for more troubleshooting .Assuming your Samsung cable is not faulty of course.
@ehsanotaku Yes i did root my phone on pheonix fire rom. No i do not see any. And debugging is checked, that was my first guess why it was causing this. I was checking, whether my device is recognized in linux (only available OS in present) and it was NOT, but the cable is not faulty, because it was charging my phone... but i will do recognize process on windows, hope it will get better. But thanks so far!
so, the driver didnt help, but the adb devices got me something long which i do not completely understand (i am a girl and not IT) so...
LiQuDiAk said:
so, the driver didnt help, but the adb devices got me something long which i do not completely understand (i am a girl and not IT) so...
Click to expand...
Click to collapse
off topic though, gender discrimination is prejudice,, sorry if you are offended . Learning from each other despite your gender,does not undermine your knowledge EVER mate You might find it hard to believe, but I am quite novice in android stuff myself ( learning a great deal from some female members though ).
Back to topic at hand now,,,So let Perfectly Clear take away the time-consuming tasks and fix some stuff ..1. so you can not access your sdcard's content from either systems,, even if you try some live bootable Ubuntu disk/flash into your system and boot it up,, you can't access the mount drive content , right?
2. screenshot of your device manger while you are connected always help mate
3. those long streams of numbers and words is supposed to be your device name , it means your device is communicating with your pc ( /sdcard/ should not be corrupted). You can push (copy ) some vital files to your device with following command :
again same path >> put some file into your desktop (drag/drop to cmd)
i.e: "adb push C:\Users\ehsanotaku\Desktop\test.txt /sdcard/"
back to your device and check root of your files with whatever file explorer you got to approve the theory
4. forgot to ask , just to be on the safe side your device is not in boot loop process, stuck on samsung splash screen or something like that, right?
okay, thanks!
1. I cannot access it trough USB to mobile way, but from SD card adapter, yeah I can (it is just the weird feeling, when you always have to put out your sd and do it that way, i would like to sort this out)
2. http://s1.postimg.org/nkta50u3x/Untitleddas.png I suppose the unknown device is my phone.
3. Just a question, my phone is not connected, i cannot access it and this doesn't help
4. Nope, it is working, i can access everything, just this connecting problem i have. anything else is running smoothly.
Let's say any of this will work, do you think flashing a stock rom will help? I am not sure, if this is problem of rom or not, so...
And maybe i wasn't clear (my bad if not) but when i plug the cable in my device and pc, pc will make this sound of new device found, but it wont show me anything, so my phone. It will charge, but it wont connect, it is behaving like it is on a charger and not connected to the phone.
@LiQuDiAk, Hasty actions are done in a hurry, sometimes without the necessary care or thought. Now let's not leap to any conclusion about your Android custom Rom and flashing back to stock. lets focus on your first most obvious problems,which is driver related.
You didn't declare your flavor of windows: i.e: Windows x86 based-PC;professional 7
Not so sure of your OS Name/Version and System Type, search "system information" in your search box.
Your task manger depicted ACPI x64 ( 64-bit system, no wonder previous 32-bit compatible didn't work out for you ).
Symptoms observed so far:
1. USB cable only charges ( remember your USB cable data line might be the culprit. Just in case of only charging,checking with another set recommended. Your USB port might be problem, some dirt or faulty data line, checking with another USP port doesn't heart though.
2. Windows recognizes something more (like in your case, struggling to find proper corresponding driver), but cannot see it as a Samsung android device (cannot allocate the installed USB drivers to the device).
-If you got Kies (Samsung proprietary software) installed on your PC, delete it with a descent uninstaller program such as CCleaner free version .Kies might cause driver conflict , use it as only last resort , if all drivers failed to communicate with s5830i device.
-Also Uninstall your previous given driver same way, now restart , back to system and grab set of universal Samsung Drivers from attachment .
3.Can't see your "USB connected" in Android notification bar, so you cant click on it and mount your storage data part while you are connected to your PC.
-Normally, when you plug in your Android device, Windows will recognize it as an MTP (Media Transfer Protocol) device and quietly mount it.
However, if you’ve ever attempted to unlock your device such as to install a new ROM or root it, then such miss behaviors might be expected occasionally .
Before i go for more troubleshooting , please provide a full screenshot from your "About Phone" page in your settings . I am quite curious about this phoenix Rom you have mentioned though . I am quite familiar with at least dozen of discontinued/ported projects, but never heard of such ported Rom from other models into s5830i .
Couple of solutions :
Navigate to your settings,Storage and touch the upper-right corner for the “USB computer connection” options, if you have this part available.
make sure “Media device (MTP)” is selected. ( if you have USB Utilities section or whatever added section in your custom settings go there . Selecting that will do the trick. If it does not, then you likely have a driver problem.
Open your device manager, Right click on your unrecognized device in question,choose update driver software, choose Browse my computer,find it through given x64 drivers in your package ,Restart. ( After a successful installation, restart your PC, you must have something like the picture in attachment ) .
Problem was not resolved, Uncheck your debugging option,power off your phone. Now hold Volume(+) + Home + Power for a couple of seconds simultaneously to get to your Samsung Recovery or your Clockwork Recovery, choose Reboot( might be some process/service in your background, which interfere with your Auto USB connected feature of your device. See if the problem is being resolved .
Problems have been persisting, we might need to format your SD card, but before that, insert it into your card reader, in your file explorer window choose Tools>Folder options>select view tab> tick your select hidden file.folders. Now copy all of your SD card's contents into some folder, safe inside your PC.
We can format your card through your clockwork mod recovery console, or some partition tools such as free mini partition wizard,,
problem still persist? let me know
Hey
After some rest with this, my mobile got it solved (dunno why, just once tried to do it and it works.)
So, thank you very much with your answers!!!!
And about that screenshots, I will PM you
But, really, thanks a lot, mate!!!!
Hi, I'm new to the N9, have had the tablet about a week. I have tried connecting it to my windows 7 Pc and the N9 isn't recognized. I have tried all the basics, all drivers are current, set tablet to mtp, and not found. I have connected to a friend's Windows 10 PC and the N9 is found immediately. My N9 is a wifi only device, non rooted. I have 2 other Android devices that my W7 PC finds with no issue. Anyone else experience this, and or have any suggestions on how to fix this issue ? Not looking to root at this point. Any help and guidance would be greatly appreciated
I think there are many threads about this problem. Nexus Root Toolkit has a driver installation feature.
If you were starting from scratch I'd delete any unknown "tablet/usb" devices in Device Manager - look for the also delete drivers option.
Google's W7 installation instructions are here http://developer.android.com/tools/extras/oem-usb.html#Win7
On this page http://developer.android.com/sdk/win-usb.html is a link to download a zip file of the drivers (not the full SDK package) Click here to download the latest Google USB Driver ZIP file.
This software http://www.nirsoft.net/utils/usb_devices_view.html is possibly better than device manager in deleting drivers
In some cases, you need to enable ADB on your N9 before plugging it into your PC (Settings -> Developer Options -> Android Debugging).
peterk-1 said:
I think there are many threads about this problem. Nexus Root Toolkit has a driver installation feature.
If you were starting from scratch I'd delete any unknown "tablet/usb" devices in Device Manager - look for the also delete drivers option.
Google's W7 installation instructions are here http://developer.android.com/tools/extras/oem-usb.html#Win7
On this page http://developer.android.com/sdk/win-usb.html is a link to download a zip file of the drivers (not the full SDK package) Click here to download the latest Google USB Driver ZIP file.
This software http://www.nirsoft.net/utils/usb_devices_view.html is possibly better than device manager in deleting drivers
Click to expand...
Click to collapse
Thank you for your help, I had already tried all of this, but tried once more in case a step was missed. Every other Android device I have, or had never gave me an issue like this. The 2 android phones I have connect to pc without a problem, I am at a loss, lol.
When deleting drivers, should I have deleted all drivers for all devices, or just the ones installed from N9 ? Thanks again for your help
eckharttim said:
Thank you for your help, I had already tried all of this, but tried once more in case a step was missed. Every other Android device I have, or had never gave me an issue like this. The 2 android phones I have connect to pc without a problem, I am at a loss, lol.
When deleting drivers, should I have deleted all drivers for all devices, or just the ones installed from N9 ? Thanks again for your help
Click to expand...
Click to collapse
I've not got access to a Windows 7 PC. Does this page help http://www.topnotchtablets.com/FixUSBproblems
A basic one. I don't think it's relevant until you have a connection. Do you know that the N9 USB connection defaults to "charging only" and you need to pull down the notification menu to enable MTP to see the device contents
In USBDeview
Expand the window there are a lot more columns
There is a "connected" y/n column. I'm not certain that this works as expected, I can connect a tablet and despite an F5 refresh or a restart of the program it will stay a "No"
Look at the VendorId column AFAIK everything Google Nexus related has an ID of "18D1"
Have tried to establish what, if anything pops up in Device Manager when you plug in the N9 so you can disable it? Nirsoft have a program http://www.nirsoft.net/utils/device_manager_view.html that gives a table view of all devices - no clicking to expand trees
peterk-1 said:
I've not got access to a Windows 7 PC. Does this page help http://www.topnotchtablets.com/FixUSBproblems
A basic one. I don't think it's relevant until you have a connection. Do you know that the N9 USB connection defaults to "charging only" and you need to pull down the notification menu to enable MTP to see the device contents
In USBDeview
Expand the window there are a lot more columns
There is a "connected" y/n column. I'm not certain that this works as expected, I can connect a tablet and despite an F5 refresh or a restart of the program it will stay a "No"
Look at the VendorId column AFAIK everything Google Nexus related has an ID of "18D1"
Have tried to establish what, if anything pops up in Device Manager when you plug in the N9 so you can disable it? Nirsoft have a program http://www.nirsoft.net/utils/device_manager_view.html that gives a table view of all devices - no clicking to expand trees
Click to expand...
Click to collapse
Thank you for your help I greatly appreciated it. After trying pretty much everything, I decided to see if the ruu's for my two phones would run on W10. They did, so I then proceeded to update my W7 to W10. N9 communicates perfectly now with my PC. Thank you
Hello all
I got a new Samsung S6 from work. for security reason, I cannot root the device (entrust and other software will not install)
since I got it, I am very annoyed by the fact that every time I connect the phone to my Linux, I have the following message when I want to access the files by MTP
allow access to device media
a MTP connection will be established to access the Data on the connected device : DENY ALLOW
Click to expand...
Click to collapse
is there a way to remember which connection was allowed or to remove once and for all this annoying message ?
thx
Dereut
Hello and welcome to XDA Q&A section of the Forum.
When you connect your phone to your pc, do you get any message in the status bar like "USB used for charging"? If not, go into setting (while connected) and click storage and USB and select MTP.
Hope that helped and hit "thanks" if it did .
thank you for your reply
my problem is not that I cannot connect. I have all the settings correctly done (or so it seems) and I have selected MTP. the issue is that the question to authorize the connection will pop up every time.
the device does not remember the previous authorisations.
example, if i connect to my Linux, then run a virtualbox windows, I have to redirect the USB to the virtualbox, but because it does not remember the authorization, it will disconnect and ask again if I agree, then I will have to redirect to virtualbox as it is seen as a new connection everytime. this in circle
also, I connect and disconnect the device from the USb all the time, everytime, I have to re-authorize the connection, it is getting old
Hi, without root, there is currently no way to automatically authorize a device (kinda stupid really) however with root there are a few ways to do it.
Kyronater said:
Hi, without root, there is currently no way to automatically authorize a device (kinda stupid really) however with root there are a few ways to do it.
Click to expand...
Click to collapse
Tell me more, every time I connect my phone I have to switch from charging to file transfer in cm13.
Hi all,
First of all, many apologies because I imagine that my situation below has been discussed here many times. TL;DR section at the bottom.
I have been trying to use adb to set an option on my Redmi Note 5 phone, to no avail. For the background of why I need that: I have arrived yesterday at my travel destination and I've realized that the app named "Google" has used over 2.24 GB of Wi-Fi data as reported by data usage in the Security app. In less than 24 hours! I've also installed and used the app Network Connections. All of this was in an effort to control the high bandwidth speed I was seeing in the notification bar (over 100 KB/s for minutes, without interruption). I have restricted network usage for all applications on Wi-Fi as well as on mobile data, disabled Sync (all forms of sync, believe me), and done everything I could think of to prevent the huge Wi-Fi usage, including rebooting the phone each time I changed a setting. The "Test Network" tile in Security still shows that about 100% of the bandwidth usage is by "Google" app. 90% of that usage is downloads and I can't figure out what Google is downloading to my device, which I've been using for a year without ever connecting it to a Wi-Fi network, until yesterday. Somehow, on my Redmi Note 5 running MIUI 11, "Wi-Fi" is equated to "unlimited network, with no cap, and no reason to be reasonable".
The root problem is that the Wi-Fi I'm connecting to is metered, and apparently, MIUI has removed the underlying Android option to set a Wi-Fi connection as metered. The solution, as I've discovered online is to issue an adb command (cmd netpolicy set metered-network <name of network> true).
Therefore, I head to using adb. Many pages online deal with enabling Developer Options and US debugging, and I had already done just that in the past.
However, in the instructions on using adb, each such page speaks at a certain point in the list of instructions of a dialog box that is supposed to show up on the phone ("Allow USB debugging?" with something about a computer fingerprint), but it never showed up on my device. The command adb devices does not list anything, not even in a command line opened as an administrator. The adb executable that I'm using is from the Android Platform Tools (platform-tools_r29.0.5-windows.zip).
Many forum pages hint to a missing driver. But I can easily plug the phone via USB and download files and photos from the phone to the computer. If it was a driver issue, shouldn't I have problems doing file transfers?
Moreover, each time I plug the phone via USB, I see a notification from "Android system" stating "USB debugging connected" followed by "Tap to turn off USB debugging", which tells me that USB debugging is working.
TL;DR
adb devices lists nothing when my Redmi Note 5 is connected via USB. I guess it's a driver issue. How can I get the appropriate driver? I would like to avoid downloading sketchy driver packs from random websites such as the ones from xiaomi advices (e.g. the "driver" for Redmi Note 5 was uploaded on October 5, 2014!!!).
Thank you.
do you already set enable usb debugging on developer setting?
You can try to install Xiaomi Mi PC Suite on your PC, after the installation, open the program and connect your phone with the USB cable, that will install the correct drivers, I hope. Then you can close the program and activate USB debugging in Developer Options in your phone, and try again to write the command in the terminal.
EriecTan said:
do you already set enable usb debugging on developer setting?
Click to expand...
Click to collapse
Yes. Both the plain "USB debugging" and the "USB debugging (Security settings)".
openCode168 said:
You can try to install Xiaomi Mi PC Suite on your PC, after the installation, open the program and connect your phone with the USB cable, that will install the correct drivers, I hope. Then you can close the program and activate USB debugging in Developer Options in your phone, and try again to write the command in the terminal.
Click to expand...
Click to collapse
Well, I have installed PC Suite 2.2.0.7032 to no avail: when I connect the phone via USB, a PC suite window shows up and says "Looks like you're missing some drivers... Make sure you're this system's administrator", which I am. I can't believe that in this day and age it is so difficult to find official drivers for a device that's been sold by the thousands.
Thanks for your help.
OMFG, I did it!
Before I say anything more: I have uninstalled Mi PC Suite.
The solution is in the mode that is active in the notification shade once the phone is connected via USB to the computer. In the notification shade, there was a notification from Android system that read "Charging this device via USB, tap for more options". Once I tapped and chose "File transfer", things changed!
At the same time, the Device Manger had been opened on the computer an I was seeing a yellow overlay icon over "SDM636-MTP _SN:xxxxx" in category "Other devices". As soon as I chose "File transfer", the device "SDM636-MTP" disappeared and a new category "Android Phone" showed up, along with a subcategory that read "Android Composite ADB interface". The "ADB" in the title prompted me to try using adb. That's when it all worked! Here is a transcript of the command line session, during which at some point I got (on the phone) a dialog box about authorizing the computer, also showing an RSA fingerprint. I obviously authorized the computer :
Code:
Microsoft Windows [version 6.3.9600]
(c) 2013 Microsoft Corporation. Tous droits réservés.
D:\Programs\adb>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
fce3c2e3 unauthorized
D:\Programs\adb>adb devices
List of devices attached
fce3c2e3 device
D:\Programs\adb>adb shell
whyred:/ $ cmd netpolicy list wifi-networks
waav19781502;none
WI-FI HOME;none
whyred:/ $ cmd netpolicy set metered-network "WI-FI HOME" true
255|whyred:/ $ cmd netpolicy list wifi-networks
waav19781502;none
WI-FI HOME;true
whyred:/ $
So the problem was not about drivers like I thought and complained about, it was about choosing the appropriate mode once the phone is connected to a computer via USB.
I'll see now whether setting the Wi-Fi networks as metered will be enough to stop Google from using up the data allowance.
EDIT: Setting the network as metered did the trick: what was previously hovering well above 100 to 200 KB/s is now around 0.05 - 3.00 KB/s, due this time not to "Google" but to "Google Services Framework" and "Google Play Store"