I have connected Nokia 1 TA-1066 phone to windows PC via USB cable after enabling USB debugging in setting->System->Developer Options.
on the command prompt, I am unable to get the device after executing #adb devices. Do I need any specific driver ?
I am able to see access phone storage via windows PC.
Please let me know if someone tried adb connection on Nokia 1 TA-1066 model.
Thank You!
-Mayur
JainMayurD said:
I have connected Nokia 1 TA-1066 phone to windows PC via USB cable after enabling USB debugging in setting->System->Developer Options.
on the command prompt, I am unable to get the device after executing #adb devices. Do I need any specific driver ?
I am able to see access phone storage via windows PC.
Please let me know if someone tried adb connection on Nokia 1 TA-1066 model.
Thank You!
-Mayur
Click to expand...
Click to collapse
Solution
1. Developer option -> enable USB debugging
2. Developer Options-> Select USB Configuration-> Audio Source
Adb started working
Solution 2.
Use below adb platform tools for windows
platform-tools Windows: http://www.devfiles.co/download/KtLs...st-windows.zip
Thank You!
-Mayur
JainMayurD said:
Solution
1. Developer option -> enable USB debugging
2. Developer Options-> Select USB Configuration-> Audio Source
Adb started working
Solution 2.
Use below adb platform tools for windows
platform-tools Windows: http://www.devfiles.co/download/KtLs...st-windows.zip
Thank You!
-Mayur
Click to expand...
Click to collapse
you are the man !
thanks a lot
JainMayurD said:
Solution
1. Developer option -> enable USB debugging
2. Developer Options-> Select USB Configuration-> Audio Source
Adb started working
Solution 2.
Use below adb platform tools for windows
platform-tools Windows: http://www.devfiles.co/download/KtLs...st-windows.zip
Thank You!
-Mayur
Click to expand...
Click to collapse
it works! must be a bug inside nokias firmware cause when i change the USB configuration back to charging it breaks the ADB and when i switch it back i get ADB back... weird!
Hello,
Many thanks, it helped me for my nokia 7.1.
Cheers
JainMayurD said:
Solution
1. Developer option -> enable USB debugging
2. Developer Options-> Select USB Configuration-> Audio Source
Adb started working
Solution 2.
Use below adb platform tools for windows
platform-tools Windows: http://www.devfiles.co/download/KtLs...st-windows.zip
Thank You!
-Mayur
Click to expand...
Click to collapse
I have connected Nokia 6.2 phone to windows PC via USB cable after enabling USB debugging in setting->System->Developer Options.
on the command prompt, I am unable to get the device after executing #adb devices. Do I need any specific driver ?
I am able to see access phone storage via windows PC. There is no in usb configuration audio source
Please let me know if you kmow how connect adb to nokia 6.2.
Thank You!
JainMayurD said:
Solution
1. Developer option -> enable USB debugging
2. Developer Options-> Select USB Configuration-> Audio Source
Adb started working
Solution 2.
Use below adb platform tools for windows
platform-tools Windows: http://www.devfiles.co/download/KtLs...st-windows.zip
Thank You!
-Mayur
Click to expand...
Click to collapse
Related
I'm new to CyanogenMod & It needs new driver for ADB connection!!???
I already have HTC_Driver_4.1.0.001 installed on my windows7 & works good with other previous ROMs.
I've checked ADB via usb on developer setting. How can I find or have a driver for "ADB connection" Windows couldn't find it automatically.
Thanks
kam5iz said:
I'm new to CyanogenMod & It needs new driver for ADB connection!!???
I already have HTC_Driver_4.1.0.001 installed on my windows7 & works good with other previous ROMs.
I've checked ADB via usb on developer setting. How can I find or have a driver for "ADB connection" Windows couldn't find it automatically.
Thanks
Click to expand...
Click to collapse
For me. Go into Device Manager and find the unconfigured device and manually assign the driver to it.
EDIT: Which you may need to get the android sdk and download the usb driver and manually assign it with those.
hello,
I previously was using HTC explorer and had many great experience of rooting and changing custom ROMs setting up of adb was easy with it but currently I own a dell venue 7 3740 LTE tablet which is having KitKat 4.4.4 I have a HP laptop with windows 7 ultimate I want to start using adb in command prompt so that I can do lagcat and capture ota updates link also I want to use adb so that some apps which needs root but can be used via some tweaks done in adb eg.helium,screen shot ultimate etc.
please help me how to setup adb in my laptop.
Have you tried installing the Intel Android USB Drivers?
xBIGREDDx said:
Have you tried installing the Intel Android USB Drivers?
Click to expand...
Click to collapse
That one works amazingly well fixed my fastboot driver on windows 10
social-design-concepts said:
That one works amazingly well fixed my fastboot driver on windows 10
Click to expand...
Click to collapse
But Its not working for me.
http://forum.xda-developers.com/general/xda-assist/dell-venue-7-3740-mtp-usb-debug-problem-t3173463
xBIGREDDx said:
Have you tried installing the Intel Android USB Drivers?
Click to expand...
Click to collapse
yes I have installed the v1.9.0 setup in device manager in laptop when I connect my tab with debugging enabled it shows in portable device my tab name,and other device mtp is shown with yellow exclamation.
mtp drivers for tab are not getting installed.
in cmd when I hit adb devices I don't get my tab details
Does it show like the pictures in my link ????
Dipyaman said:
Does it show like the pictures in my link ????
Click to expand...
Click to collapse
yes its shows yellow error in mtp but I am able to transfer files from laptop and tablet only thing is I can't use cmd and adb but after going thru your link I come to know that my adb was too old which is of my HTC explorer so I downloaded adb (platform.zip) from the thread given in your post and then for mtp I manually selected driver installed in my laptop I.e adb interface >Samsung adb and then I tried cmd in new platform.zip which had updated adb files for jellybean+ version and now its working fine.
Dunno how you did that. I'm a newbie.
Could you plz help me out ?
I don't have any sort of "Adb" connection in device manager (which you can see in my image), which was supposed to be there.
Can you give me a detailed explanation of what you did ????
Dipyaman said:
Dunno how you did that. I'm a newbie.
Could you plz help me out ?
I don't have any sort of "Adb" connection in device manager (which you can see in my image), which was supposed to be there.
Can you give me a detailed explanation of what you did ????
Click to expand...
Click to collapse
so you too also want adb to work for you right?
I can't say exactly what made it work for me cause I have s duos 2 also n so its drivers are also installed in my lappy.
but you do one thing
1.install Intel android driver from above post v1.9.0
2.enable debugging in tablet and connect and then goto device manager where you have mtp error,right click on mtp,update drivers select from folder will appear below that must be some option select from installed drivers goto that see Intel android driver after that you will be getting multiple option android adb interface, adb composite interface select any one preferably android adb interface and install.after that uncheck debugging and again check it and see if mtp error is gone from device manager.
3.download platform.zip from your given thread link unzip it and in that folder open cmd by holding shift and right click do open cmd here and check if all is OK by typing adb devices,if its OK it will list your device.
I'll give it a try, then i'll inform you. Till then, please stick to the post ! Thank you for the info BTW.
Dipyaman said:
I'll give it a try, then i'll inform you. Till then, please stick to the post ! Thank you for the info BTW.
Click to expand...
Click to collapse
today I tried changing from samsung adb driver with Intel adb driver and it worked
djmacpro said:
today I tried changing from samsung adb driver with Intel adb driver and it worked
Click to expand...
Click to collapse
The problem is, Installing Intel USB drivers does not do anything. Its does not show up in my device manager.
Dipyaman said:
The problem is, Installing Intel USB drivers does not do anything. Its does not show up in my device manager.
Click to expand...
Click to collapse
if still yellow error is shown on device manager right click on it update driver,then browse from folder or look for installed driver some where is must be there search something related to Intel or adb and select that else forget it cause what's the use of adb for us as there is no custom ROM or other things to do.
other way is download helium app on PC and tablet and in ptp mode you can get adb working
I have not managed to connect to my Redmi Note 4 (Android 6.0 MRA58K, MIUI Global 8.1 | Stable) via adb from my Windows 7 computer.
With my old SGN4 this was never a problem but I am a noob on the RN4.
I have Android Studio (with adb) installed, then
I connect my mobile via USB cable
I select on the mobile "Use USB for: Transfer files (MTP)", USB debugging is enabled and I can see the phone in the Windows explorer
then I open a command prompt and run adb but "nothing happens":
c:\Progs\Android\sdk\platform-tools>
c:\Progs\Android\sdk\platform-tools>adb.exe logcat
- waiting for device -
^C
c:\Progs\Android\sdk\platform-tools>adb devices
List of devices attached
c:\Progs\Android\sdk\platform-tools>
What am I missing???
Check drivers on control panel, it is correct?
dromaczek said:
Check drivers on control panel, it is correct?
Click to expand...
Click to collapse
Not sure I can post an image: i.imgur.com/UFAi5ez.png
In the Windows Device Manager there are two interesting entries:
Other devices
--- MTP [has an exclamation mark]
Portable devices
-- Redmi Note 4 [looks fine]
Is the "Transfer files (MTP) mode correct"?
Does the phone need to be rooted?
Gollob said:
Not sure I can post an image: i.imgur.com/UFAi5ez.png
In the Windows Device Manager there are two interesting entries:
Other devices
--- MTP [has an exclamation mark]
Portable devices
-- Redmi Note 4 [looks fine]
Is the "Transfer files (MTP) mode correct"?
Does the phone need to be rooted?
Click to expand...
Click to collapse
You have wrong adb driver (choose manually other from control panel)
dromaczek said:
You have wrong adb driver (choose manually other from control panel)
Click to expand...
Click to collapse
The driver was indeed the issue, thanks for that.
This is what I did:
[1] xiaomifirmware.com/downloads/download-xiaomi-redmi-note-4-drivers-utilites
[2] Download: latest_usb_driver_windows.zip
[3] also downloaded ADB Installer v1.4.3: adb-setup-1.4.3.zip from the same page (not sure if this was necessary)
[4] Control Panel, Device Manager: installed the driver (Android ADB Interface)
Now I have this Android ADB Interface under the heading SAMSUNG Android Phone, not sure if this is a problem
at some point later on as it is obviously a Xiaomi Android Phone that I have. [see: i.imgur.com/yvIyIjt.png]
When running adb devices I got the device ID and unauthorized at first and after approving USB access on the
handset it showed the device ID and authorized and I can issue commands like abd logcat.
Gollob said:
The driver was indeed the issue, thanks for that.
This is what I did:
[1] xiaomifirmware.com/downloads/download-xiaomi-redmi-note-4-drivers-utilites
[2] Download: latest_usb_driver_windows.zip
[3] also downloaded ADB Installer v1.4.3: adb-setup-1.4.3.zip from the same page (not sure if this was necessary)
[4] Control Panel, Device Manager: installed the driver (Android ADB Interface)
Now I have this Android ADB Interface under the heading SAMSUNG Android Phone, not sure if this is a problem
at some point later on as it is obviously a Xiaomi Android Phone that I have. [see: i.imgur.com/yvIyIjt.png]
When running adb devices I got the device ID and unauthorized at first and after approving USB access on the
handset it showed the device ID and authorized and I can issue commands like abd logcat.
Click to expand...
Click to collapse
You must authorized access and check all ADB options on xiaomi rom to use for example adb density command etc (and log on mi acount)
[Solved] Xiaomi Redmi Note 4 : Connection with ADB
Hi,
As we all know Xiaomi works on its own MIUI, So when you want to connect to adb that is developer mode you need to connect as MIDI,
Enable MIDI
Step 1: Goto settings > Additional Settings > Developer options
Step 2:In developer option, Enable developer options,
Step 3: In same menu go down in side Networking and from the SELECT USB CONFIGURATION, select MIDI
Now check adb devices on your command prompt you can see your Xiaomi is connected.
Happy Coding
Does your phone show up on the terminal with adb devices command when in recovery? Can be stock recovery too.
Also, in fastboot, use fastboot commands
i.e. fastboot devices instead of adb devices
One more thing, go to device manager and manually install a legacy driver and browse to adb and choose Android Bootloader Interface (ABI) look into it, it's possible.
That should do it. Tell me if it helps.
Sorry I don't know how to quote stuff and format commands.
dromaczek said:
Check drivers on control panel, it is correct?
Click to expand...
Click to collapse
hello brother, I'm facing the same issue while unlocking the bootloader.
I think these is prob with the drivers.. pps help me out
Hello People,
i have a display broken Samsung Galaxy SAM-A510. If i connect it per USB to my Windows 10 Laptop the Name of the Handy appears as Device in my Windows Explorer, but no Folders for this Handy appear. I cannot switch to MTP per Handy so i have the question if i can switch from my Laptop over ADB to USB-MTP?
If you know a way to select MTP from Laptop with Handy per USB connected please write a step by step solution for this problem!
We only want to save the Data from the Handy to the Laptop!
Thanx a lot
dan813
@dan813
Should work:
Code:
adb devices
adb shell "svc usb setFunction mtp true"
jwoegerbauer said:
@dan813
Should work:
Code:
adb devices
adb shell "svc usb setFunction mtp true"
Click to expand...
Click to collapse
Thank you so much, it worked for me!
SOLVED: Issue fixed by using an USB 2.0 Port, don't use USB 3.0, it has some issues.
I've searched everywhere for a fix and still have not been able to make this work, this are the steps I have taken:
> I've created an MI Account with "Sync" and "Find Device" options enabled
> Enabled "OEM unlocking", "USB debugging", "USB debugging (Security settings)" on Developer options
> I've added my account and device on "MI Unlock status"
> Downloaded & installed ADB Driver, Mi PC Suite and Qualcomm Driver following the steps on this website:
Flashxiaomi website pokcophone f1 usb driver (can't type link here)
(After Android ADB Interface is installed it says that it might not work correctly and the device can not be started (Code 10) as shown on one of the pictures of the guide above)
> Downloaded MIUI Unlock software via the official website zip file named "miflash_unlock-en-4.5.514.47"
> Moved MIUI Unlock file to C:
> Ran as admin "MiUsbDriver" from the previous downloaded folder in order to install drivers
> Turn off my device and set it into fastboot mode
> Devices Manager > Android Phone > Android Bootloader Interface > driver tab proprieties show driver provider is "Xiaomi Technology, Inc.", driver date is "11/3/2016", and driver version is "16.0.0.0".
> Installed android_winusb.inf on MIUI Unlock | driver | win10 folder
> Ran as admin "miflash_unlock" and at this point my phone disconnects from my PC, phone shows "Press key to shutdown" on screen and by clicking the settings option on the MIUI application it tells me to click the button to install the drive
Other informations:
My pc is using intel, not AMD
What can I do?
Try unlock with windows 7 and usb port 2.0
tiennhu89 said:
Try unlock with windows 7 and usb port 2.0
Click to expand...
Click to collapse
That might be the issue, I'm on windows 10 and usb port 3.0, ill give it a try
Edit: It worked with usb 2.0 port!
Thanks, issue solved.
eldesaro123 said:
That might be the issue, I'm on windows 10 and usb port 3.0, ill give it a try
Edit: It worked with usb 2.0 port!
Thanks, issue solved.
Click to expand...
Click to collapse
Congratulations. :highfive: