Gear s not showing up in adb devices on windows 10 - Samsung Gear S

hi everyone
i have been trying to fix an issue for days with my gear s1 sm-r750a (software r750aucu2apc1) not show up in the cmd adb devices so this is what ive try that has not worked:
reinstalled my samsung and google drivers multiple times
factory reset
my gear s is unlocked as i have a virgin mobile sim inserted and i have made a call that worked
unpaired and paired with a samsung phone
turned on usb debuging on my gear
updating my gear s firmware
updating drivers manually in device manager
15 seconds adb installer
googling it and youtube videos
adb kill-server
adb start-server
adb devices
recovery mode
android sdk software
eclipse software
disable digitally signed driver
updated to the lastest java
restarted my pc multiple times
tried mobilego by wondershare
impactor
odin
vroot
samsung kies
smartswitch pc
naked adb drivers 0.73
universal adb drivers
simple adb installer
tried different usb cables and ports on my laptop
it only shows up if i use cmd sdb which i have installed opera mini using this method
my LG G3 works fine and it shows up in the cmd adb and in android devices and portable devices in device manager where as my gear s only shows up in portable devices. my lg g3 is rooted with Xposed Installer on it. with my gear s im trying to root it but having no success with it. i like the tizen ui but its a real pain in the butt so i can change to android if need be.
if anyone one knows any over way to root or make it show up in cmd adb please help me
thanks for any help

Related

[Q] ADB Driver Problem

I tried to root my Samsung Vibrant using the One-Click Root method but when I get to the part where the phone is supposed to reboot into Recovery Mode, nothing happens. Then, I checked Device Manger to see if there were any problems with the drivers and it said that Windows failed to initialize the Samsung Android Composite ADB Interface driver. How do I fix this?
I have Windows XP 32-bit.
I googled fixes for this for a while but nothing I found worked. Any help would be appreciated.
Does Kies is running without any problems and you can connect your phone?
If No, pls install Kies and be sure that you have an access to your phone.
If it is working: pls close Kies - also in the Systray. Not that the 2 different application makes trouble
I can connect my phone to Kies without any problems but it still won't work even after I uninstalled Kies

Can't connect with ADB.

I can't connect to my phone with ADB. I've tried with SE's adb drivers and the ones from Android SDK, but none of them work, it starts the daemon but it's unable to recognise any device.
I'm on Android 2.1 with "USB dbg" enabled. My system is a XP64 SP2 with the correct drivers. Any ideas?
_SpAiK_ said:
I can't connect to my phone with ADB. I've tried with SE's adb drivers and the ones from Android SDK, but none of them work, it starts the daemon but it's unable to recognise any device.
I'm on Android 2.1 with "USB dbg" enabled. My system is a XP64 SP2 with the correct drivers. Any ideas?
Click to expand...
Click to collapse
Does it not recognise it at all or will just not mount?
I can mount it, but if I type "adb devices" in cmd it returns a blank list. I've switched of my firewall and antivirus, but it does not resolve anything. I've seen that when running adb, it loads two instances of adb.exe and then kills one, also when trying to root with SuperOneClick it loads and maintains two instances.
I've had trouble with it most of the day but seem to have sorted it now, but it does show with adb devices for me so not sure.
Once you update to 2.1, you need to update the drivers.
The easiest way is to install Sony Ericsson's PC Companion (and update): http://www.sonyericsson.com/cws/support/softwaredownloads/detailed/pccompanion/xperiax10
I was wondering about this too. Sony Ericsson Update Service would detect the phone in flash mode, but not ADB or SuperOneClick. Once I installed PC Companion, it was fine.
Check your Device Manager. I'd bet you have a yellow exclamation mark.

[Q] 4.2.2, devices showing offline in adb

I updated SDK Tools to 21.1 and Platform-tools to 16.0.1. Verified with 'adb version' that I am running v1.0.31. Windows 7, x64.
I have four 4.2.2 devices to test with, a Galaxy Nexus with unlocked bootloader but not rooted, and Nexuses One, 4, 7 & 10, all stock.
The Nexus One, being <4.2.2, works just fine with adb, but all the 4.2.2 devices show as 'offline' in adb, and I have NEVER seen the RSA security dialog pop up on the devices, even after several restarts of ADB (using kill-server), the PC and the devices themselves.
Have tried using different USB ports and cables. I'm using the standard 'Android ADB Interface' drivers from the SDK, but have also tried the 'Android Composite ADB Interface' and 'Samsung Composite ADB Interface' drivers too. I even completely re-installed the SDK from the ADT bundle.
Weird thing is, my colleague can get the popup to show on those same devices without any trouble. I even copied his adb.exe and dll's and tried that and it still wouldn't work on mine. He didn't install from the bundle; he installed ADT into Eclipse, the old-fashioned way, but I doubt that would make a difference. What gives?!
Just downloaded the recently released update to Android SDK Platform-tools rev.16.0.2, but this hasn't updated ADB or helped the problem.
Still no RSA security popup on any of my 4.2.2 devices using ADB v1.0.31, yet the same devices will show the expected dialog on my colleague's machine, using the same version of ADB.
Can anybody confirm that the ADT bundle as downloaded from developer.android.com is working with 4.2.2 devices? That's the only difference I can see between mine and my colleague's machines.

[Q] [LG VS930] Unable to get ADB commands to work

Alright, I've tried installing the drivers from Verizion and also using the drivers from the Android SDK and either way I have the same problem. ADB devices shows my phone, however whenever I try to push, pull, or reboot (the only commands I have any use for atm) the command prompt hangs like it's trying to access the device but no matter how long I leave it the device will not reboot, nor will any files appear in the correct folders on either the device or my computer.
I'm trying to root my phone and this is a pretty major roadblock.
Note:
USB Debugging enabled
ADB drivers installed
Phone shows up on "adb devices"
There is no error or any other output in the console. The best way to describe this problem is that ADB hangs.
I'm running Windows 8.1 and my phone is running Android 4.1.2
Also, I don't know if this is normal but, In order to get the notification that "USB debugging connecting" I have to use the internet connection option on the phone. When using MTP, Charge only and PTP that message doesn't appear and I don't see an ADB device show up in device man.
Things I've Tried
Uninstalling all Android drivers and redownloading/installing them after restart
Restarting my phone multiple times
Running adb kill-server / adb start-server
Changing USB ports7
Thanks!
Try installing drivers from LG. This seems the right one but double check:
http://www.lg.com/us/support-mobile/lg-LGVS930

ADB not working on Recovery/Fastboot mode.

I am trying to root my old phone Samsung Galaxy core prime G360h so that I can gain some confidence to change the stock rom of my main device. When the phone is on, adb works perfectly and recognise the device. I can even reboot device when the phone is unlocked. But once I go into Fastboot/Recovery mode then ADB fails to find the device and no commands work(.To the best of my knowledge, I have all the necessary drivers. I have tried multiple USB slots, multiple computers (Windows 7 sp1 and Windows 10 latest update), and have searched all around the internet and various forums on XDA for an answer. I've tried manually updating the USB drivers through device manager, installed universal usb driver, but that did nothing. What I don't understand is that how ADB works when the device is on but don't work when it's in Recovery/Fastboot mode. I would have post images to clear things but the site is not letti g me to post imaves
tldr: adb recognize phone when it's on but Adb don't work in fastboot/recovery mode
Thanks in advance for any help, I've tried everything I can think of.
On MediaTek devices you need Preloader VCom Driver so your PC would detect your phone on fastboot but on Qualcomm ( which is your phone chipset ) i don't know what driver is required ...

Categories

Resources