i have android one Mito Compact, and my PC win 7 pro.
my PC cannot detect my android. and in android display don't show a notice anything just charging.
what must i do??
Thakz all
Easy : Bcoz of Debugging not turned on.
botaxxs said:
i have android one Mito Compact, and my PC win 7 pro.
my PC cannot detect my android. and in android display don't show a notice anything just charging.
what must i do??
Thakz all
Click to expand...
Click to collapse
1.Go to About Device
2.Tap on Build Number
3.Then Dev option will appear above about device
4. In it Check USB debugging/ Android debugging
5.Remove usb and connect again
6.Phone will be detected.
ThunderSky7 said:
1.Go to About Device
2.Tap on Build Number
3.Then Dev option will appear above about device
4. In it Check USB debugging/ Android debugging
5.Remove usb and connect again
6.Phone will be detected.
Click to expand...
Click to collapse
wow, thakz ya
it works:fingers-crossed:
ThunderSky7 said:
1.Go to About Device
2.Tap on Build Number
3.Then Dev option will appear above about device
4. In it Check USB debugging/ Android debugging
5.Remove usb and connect again
6.Phone will be detected.
Click to expand...
Click to collapse
I didn't even do such a thing, just connect the phone to USB and it works but after I installed the Micromax driver provided by the Micromax it didn't work the native driver works fine on Windows 7 x64bit.
Related
Can't seem to connect to Windows 8 through USB. It chimes and the Touchpad says connected as a media device. But I don't see it in Windows. Tried checking and unchecking MTP in storage settings and nothing.
BigB42078 said:
Can't seem to connect to Windows 8 through USB. It chimes and the Touchpad says connected as a media device. But I don't see it in Windows. Tried checking and unchecking MTP in storage settings and nothing.
Click to expand...
Click to collapse
Try this
1. Go into Device manager. You will see "MTP USB Device" under portable devices.
2. Right Click it and select update driver software
3. Select Browse my computer for driver software.
4. Select Let me pick from a list of device drivers on my computer
5. Select USB Mass Storage Device then click next.
and/or
6.To transfer files to PC, turn on USB mass Storage from the USB connection notification on the Android device.
The above is.courtesy of RolandDeschain79 install guide.
I've followed this and it worked for me.
Good luck and have fun.
hmmmmmm. Not showing up in portable devices?
OK it detected fine upstairs on a Win 7 machine must be WIn 8 problem, Anybody know how to make it work on Windows 8?
I have been facing a strange problem since I updated my Nexus 6 to Android Marshmallow. When ever I am plugging the phone to my computer (Running Windows 7) using the usb cable, I am not being able to tranfer any files. Its showing a message which says that "The device has either stopped responding or has been disconnected". Any help on this will be really appreciated
adb driver already installed?
h20ray said:
adb driver already installed?
Click to expand...
Click to collapse
Yes. It shows that all drivers are installed correctly....In fact, the device also shows under device manager. Its just that no tranfer is possible between the phone and the computer
did you bring down notifications and change connection type to MTP?
In Marshmallow your connection to PC is in Charging Mode by default, you should bring down notifications select connection mode and change connection type to MTP(Media Transfer Protocol).
aliesz said:
In Marshmallow your connection to PC is in Charging Mode by default, you should bring down notifications select connection mode and change connection type to MTP(Media Transfer Protocol).
Click to expand...
Click to collapse
Thanks ......That helped
My both devices are connecting to PC-np. I can browse files - np. Download mode works fine with com & port number - np. LG Mobile tool identify my phones-np. I can see and select options for charging, mtp, and all - np. usb debugging is works good too. BUT BUT when I connect my device manager shows only G4, LG Air drive under portable devices and NO comport number or LGE Mobile USB serial Port COM - Nothing worked. I did installed almost all the drivers and uninstalled and tired as much I could. Nothing worked and no shows the port com in device manager. I have t mobile and shows just like that.. Any help, advice and guide will be appreciated. Thanks
jayalaba said:
My both devices are connecting to PC-np. I can browse files - np. Download mode works fine with com & port number - np. LG Mobile tool identify my phones-np. I can see and select options for charging, mtp, and all - np. usb debugging is works good too. BUT BUT when I connect my device manager shows only G4, LG Air drive under portable devices and NO comport number or LGE Mobile USB serial Port COM - Nothing worked. I did installed almost all the drivers and uninstalled and tired as much I could. Nothing worked and no shows the port com in device manager. I have t mobile and shows just like that.. Any help, advice and guide will be appreciated. Thanks
Click to expand...
Click to collapse
You have to set in the hidden usb menu rndis modem. I cant remember how to get to it.
hi folks!
I recently bought a sm-t713 and i can't get my pc to recognize it in linux or windows.. i want to root and unlock the bootloader but odin cant even see it.. and its not an issue with not having debugging on. thats all turned on. Please advise. thanks!
Nobody knows why? I have oem unlock "on"
debugging "on"
But I cant get my comp to see the device..Have Samsung drivers installed. Still no luck.
How can I fix this? all it does is charge when I hook it to pc but can't transfer files.
sorry double post
Same issue here. I've had no luck sorting it out.
Gutterball said:
hi folks!
I recently bought a sm-t713 and i can't get my pc to recognize it in linux or windows.. i want to root and unlock the bootloader but odin cant even see it.. and its not an issue with not having debugging on. thats all turned on. Please advise. thanks!
Click to expand...
Click to collapse
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
ashyx said:
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
Click to expand...
Click to collapse
What the USB configuration is set to is actually moot. When the device is plugged in to a PC the tablet will bring up a notification stating what mode the USB port is in and also provide the option to change that to MTP mode (Transfer files), provided the drivers are correctly installed and all is in working order. By changing USB configuration to MTP the tablet shows up immediately on the PC but you still have to switch to "Transfer file" mode before you can move files between devices. Either way the results are the same and it takes the same number of steps. I always leave my USB configuration in "System Default" and I have never had any issues.
ashyx said:
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
Click to expand...
Click to collapse
Thanks for helping! under device manager the tablet is showing as a mass storage controller not an mtp device. Even though in the tablet itself I have it set to mtp under developer options.
When I do the command "adb devices" I get this message
C:\Users\Brian\Downloads\platform-tools_r28.0.0-windows\platform-tools>adb devices
List of devices attached
nothings there
Also I was reading this is happening because of the newest stock update from Samsung.. is that true?
Gutterball said:
Thanks for helping! under device manager the tablet is showing as a mass storage controller not an mtp device. Even though in the tablet itself I have it set to mtp under developer options.
When I do the command "adb devices" I get this message
C:\Users\Brian\Downloads\platform-tools_r28.0.0-windows\platform-tools>adb devices
List of devices attached
nothings there
Also I was reading this is happening because of the newest stock update from Samsung.. is that true?
Click to expand...
Click to collapse
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
ashyx said:
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
Click to expand...
Click to collapse
Still having trouble here, too.
After flashing a ROM and attempting to install what was probably the wrong Gapps version, I'm now getting a boot loop into TWRP, and the device is still not recognized. I can boot into 'Download Mode', but the device is still not being seen by my PC. I have tried multiple times to install the USB drivers, but Odin 3.12.3 is still not seeing the tablet.
Much as I hate installing hokey, bloated software, would KIES be helpful here?
So, all is not lost (yet) - I can still access TWRP, but I'm not sure where to go from here.
Thanks in advance for any ideas you have.
I
BillTheCat said:
Still having trouble here, too.
After flashing a ROM and attempting to install what was probably the wrong Gapps version, I'm now getting a boot loop into TWRP, and the device is still not recognized. I can boot into 'Download Mode', but the device is still not being seen by my PC. I have tried multiple times to install the USB drivers, but Odin 3.12.3 is still not seeing the tablet.
Much as I hate installing hokey, bloated software, would KIES be helpful here?
So, all is not lost (yet) - I can still access TWRP, but I'm not sure where to go from here.
Thanks in advance for any ideas you have.
Click to expand...
Click to collapse
Considering download mode is totally OS independent and neither uses adb nor mtp drivers it seems the issue is either incorrectly installed usb drivers or faulty cable, device or port issues.
Boot to Download mode, open device manager then plug in the usb cable.
Windows should detect the device as a USB composite device.
If there is no detection then there is a communication issue between device and PC which could be any one of the afore mentioned reasons.
No matter what windows should show some sort of detection as soon as the device is plugged in.
No detection means no matter what drivers are installed its not going to work.
It's probably worth uninstalling the usb ports then rebooting.
Then trying again.
ashyx said:
I
Considering download mode is totally OS independent and neither uses adb nor mtp drivers it seems the issue is either incorrectly installed usb drivers or faulty cable, device or port issues.
Boot to Download mode, open device manager then plug in the usb cable.
Windows should detect the device as a USB composite device.
If there is no detection then there is a communication issue between device and PC which could be any one of the afore mentioned reasons.
No matter what windows should show some sort of detection as soon as the device is plugged in.
No detection means no matter what drivers are installed its not going to work.
It's probably worth uninstalling the usb ports then rebooting.
Then trying again.
Click to expand...
Click to collapse
Well, I'll be dipped in $hit.
What's the probability that one guy could have three dodgy USB cables? Used one, wiggled it around and the PC recognized the device. Looks like I'm in for a quick trip to WallyWorld. Thanks!
ashyx said:
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
Click to expand...
Click to collapse
yeah, windows device manager detects it as a mass storage controller. I installed the driver from samsung site. Cant be the cord cause it works with the phone. Even linux mint wont pick it up either. Any ideas? Thanks again for helping this is driving me nuts!
Gutterball said:
yeah, windows device manager detects it as a mass storage controller. I installed the driver from samsung site. Cant be the cord cause it works with the phone. Even linux mint wont pick it up either. Any ideas? Thanks again for helping this is driving me nuts!
Click to expand...
Click to collapse
Are you able to connect to the device in TWRP, either ADB or MTP?
ashyx said:
Are you able to connect to the device in TWRP, either ADB or MTP?
Click to expand...
Click to collapse
nope don't have twrp installed. and adb or mtp wont detect it. how can I install twrp? don't I need to bootloader unlock this first? And I cant do it if its not recognized by the comp right?
Gutterball said:
nope don't have twrp installed. and adb or mtp wont detect it. how can I install twrp? don't I need to bootloader unlock this first? And I cant do it if its not recognized by the comp right?
Click to expand...
Click to collapse
Are you certain this is a genuine Samsung and not a copy?
Can you post the build details from the app Phone Info.
ashyx said:
Are you certain this is a genuine Samsung and not a copy?
Can you post the build details from the app Phone Info.
Click to expand...
Click to collapse
screenshot is in the attachment.
So I've got a 3T which currently has no OS installed, just the TWRP3.2.3-0. The problem is that every time I connect the phone to the PC, the PC will only recognise the phone as Unknown USB device (Device Descriptor Request Failed). Due to this I cannot use adb to transfer files to the phone or transfer files directly to the internal storage.
I have tried using Minimal adb but device isn't found, tried different USB ports and cables too. For some reason the recovery does not read devices attached to OTG as I have also tried to transfer files using this method.
Any suggestions as to what I can do to make my PC recognise this device? Thanks
first of all check your usb cable then use this op3/t tool
it will install all drivers, unlock, decrypt, install twrp and dm-verity issue solution
https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/toolkit-root-recovery-drivers-t3651138
Hayatzada said:
first of all check your usb cable then use this op3/t tool
Click to expand...
Click to collapse
device isn't found, tried different USB ports and cables too
Click to expand...
Click to collapse
So yeah.
@op USB port in the phone is damaged
Hayatzada said:
first of all check your usb cable then use this op3/t tool
it will install all drivers, unlock, decrypt, install twrp and dm-verity issue solution
https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/toolkit-root-recovery-drivers-t3651138
Click to expand...
Click to collapse
But I cannot enable USB debugging since there is no OS installed, however I have not yet tested this program.
The USB port was working normally before the OS was removed. This problem started once there was no OS and just recovery. Is there truly no other way I can transfer the ROM to the phone? Thanks for your help
J-_-M-_-C said:
But I cannot enable USB debugging since there is no OS installed, however I have not yet tested this program.
The USB port was working normally before the OS was removed. This problem started once there was no OS and just recovery. Is there truly no other way I can transfer the ROM to the phone? Thanks for your help
Click to expand...
Click to collapse
while having TWRP installed pc should recognize your phone, if encrypted phone shows Oneplus 3 in my computer Location without showing internal storage,
Check your USB cable, then boot into fastboot(Boot loader By pressing Power & volume up button together while phone is in off state) connect your cable to pc and phone and run the tool, to install op3 driver select number from your pc
install driver (1)
unlock bootloader (3)
decrypt(10)
install twrp (5)
boot into TWRP from fastboot screen select recovery and reboot
Push superSU (7) (it'll copy superSU into internal memory) install supersu otherwise phone lose root and go back to encrypted state and you cant see internal storage in pc
reboot into recovery and copy your rom, gapps and Magisk 17.1, install them
You are done now
Hayatzada said:
while having TWRP installed pc should recognize your phone, if encrypted phone shows Oneplus 3 in my computer Location without showing internal storage,
Check your USB cable, then boot into fastboot(Boot loader By pressing Power & volume up button together while phone is in off state) connect your cable to pc and phone and run the tool, to install op3 driver select number from your pc
install driver (1)
unlock bootloader (3)
decrypt(10)
install twrp (5)
boot into TWRP from fastboot screen select recovery and reboot
Push superSU (7) (it'll copy superSU into internal memory) install supersu otherwise phone lose root and go back to encrypted state and you cant see internal storage in pc
reboot into recovery and copy your rom, gapps and Magisk 17.1, install them
You are done now
Click to expand...
Click to collapse
Thank you for this information, however I get as far as installing the drivers but the PC still shows phone as Unknown USB Device (Device Descriptor Request Failed) and therefore the program does not find the phone. Tried this on two different PC's.
Go to advance in TWRP then click on sideload and flash the os using sideload command i. e. adb sideload filename. zip
J-_-M-_-C said:
Thank you for this information, however I get as far as installing the drivers but the PC still shows phone as Unknown USB Device (Device Descriptor Request Failed) and therefore the program does not find the phone. Tried this on two different PC's.
Click to expand...
Click to collapse
please please please check your cable
johnybravo.1981 said:
Go to advance in TWRP then click on sideload and flash the os using sideload command i. e. adb sideload filename. zip
Click to expand...
Click to collapse
Since the phone is only recognised as Unknown USB Device (Device Descriptor Request Failed) in the the win10 Device Manager, fastboot devices does not find any attached devices and I cannot transfer files through ADB.
I have tested the cable I am using with another phone and I was able to transfer files to the other phone using the same USB cable.
J-_-M-_-C said:
Since the phone is only recognised as Unknown USB Device (Device Descriptor Request Failed) in the the win10 Device Manager, fastboot devices does not find any attached devices and I cannot transfer files through ADB.
I have tested the cable I am using with another phone and I was able to transfer files to the other phone using the same USB cable.
Click to expand...
Click to collapse
i have the exact same problem as u my friend i had that problem so i just sideloaded my stock rom and searching for a method to fix this if u find a way to make the device recognised in twrp pls let me know
J-_-M-_-C said:
Since the phone is only recognised as Unknown USB Device (Device Descriptor Request Failed) in the the win10 Device Manager, fastboot devices does not find any attached devices and I cannot transfer files through ADB.
I have tested the cable I am using with another phone and I was able to transfer files to the other phone using the same USB cable.
Click to expand...
Click to collapse
Just sideload dude. I came across the same issue 2 days ago.
Or flash using usb otg.
johnybravo.1981 said:
Just sideload dude. I came across the same issue 2 days ago.
Or flash using usb otg.
Click to expand...
Click to collapse
I have tried using USB OTG but the recovery does not detect my connected usb drive. Regarding sideload, when I boot to recovery and select adb sideload, and connect the phone to my PC I get a USB device not recognised message. The commands adb devices and fastboot devices do not list my phone.
J-_-M-_-C said:
I have tried using USB OTG but the recovery does not detect my connected usb drive. Regarding sideload, when I boot to recovery and select adb sideload, and connect the phone to my PC I get a USB device not recognised message. The commands adb devices and fastboot devices do not list my phone.
Click to expand...
Click to collapse
Try this guide if your phone detects as Qualcomm in device manager then proceed otherwise check your charging port (type c port) as you mention usb otg didn't detected and usb cable worked with other phones.
don't forget to clean your type c port if dirty or rusted. :good:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Hayatzada said:
Try this guide if your phone detects as Qualcomm in device manager then proceed otherwise check your charging port (type c port) as you mention usb otg didn't detected and usb cable worked with other phones.
don't forget to clean your type c port if dirty or rusted. :good:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
I have tried to install the qualcomm driver but when I go to Device Manager -> Update Driver -> Have Disk and select the qcser.inf file I get the following message: "The folder you have specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems." I have disabled driver signature verification. No idea why nothing seems to be working.
J-_-M-_-C said:
I have tried to install the qualcomm driver but when I go to Device Manager -> Update Driver -> Have Disk and select the qcser.inf file I get the following message: "The folder you have specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems." I have disabled driver signature verification. No idea why nothing seems to be working.
Click to expand...
Click to collapse
which method do you try? i suggest full method, first one didn't worked for me .
Hayatzada said:
which method do you try? i suggest full method, first one didn't worked for me .
Click to expand...
Click to collapse
I have tried Method 1 and arrived till step 6. Then when I try to select the file I get the error I mentioned in my previous post.
J-_-M-_-C said:
I have tried Method 1 and arrived till step 6. Then when I try to select the file I get the error I mentioned in my previous post.
Click to expand...
Click to collapse
try to connect otg keyboard and type in TWRP advance section selecting terminal
if keyboard works, your type c port is ok otherwise change or repair the port
Hayatzada said:
try to connect otg keyboard and type in TWRP advance section selecting terminal
if keyboard works, your type c port is ok otherwise change or repair the port
Click to expand...
Click to collapse
Tried to connect a keyboard with otg and it did not work with this phone. It worked fine using the same otg cable on another phone.
J-_-M-_-C said:
Tried to connect a keyboard with otg and it did not work with this phone. It worked fine using the same otg cable on another phone.
Click to expand...
Click to collapse
now you should go for a hardware repair of Type C port
Hayatzada said:
now you should go for a hardware repair of Type C port
Click to expand...
Click to collapse
I already said that at the beginning.