adb가 내 장치 / 전화를 찾지 못했습니다 (MacOS X)

adb가 내 장치 / 전화를 찾지 못했습니다 (MacOS X)

---

Mac에서 Android 개발을 수행하고이 새로운 전화는 adb 의 장치 목록에 표시되지 않습니다 . 다른 전화 및 장치가 많이 작동하므로 설정이 좋습니다.

휴대 전화에서 디버깅을 사용하도록 설정 (설정-> 응용 프로그램-> 개발-> USB 디버깅)했지만 실행시 표시되지 않습니다. adb devices

---

추가 업데이트 : USB 케이블의 가치를 과소 평가하지 마십시오. 때로는 케이블 교체만으로도 도움이됩니다.

최신 버전의 adb에 대한 업데이트 는 ~/.android/adb_usb.ini제거해야합니다.

요약 : 공급 업체 ID를 추가하고 ~/.android/adb_usb.iniadb를 다시 시작하십시오.

상세 정보 : 대부분의 경우 Mac이 전화 / 장치를 인식하도록하려면 아무 것도 수행하지 않아도됩니다. 진지하게, 99 %의 시간은 "그냥 효과가 있습니다."

즉, adb 를 재설정하는 가장 빠른 방법 은 다음 명령을 순서대로 다시 시작하는 것입니다.

  adb kill-server
  adb devices

그러나 때때로 adb devices명령은 장치를 찾지 못합니다. 실험 또는 프로토 타입 또는 일반 장치로 작업하는 경우 알 수없고 표시되지 않을 수 있습니다.

장치의 "공급 업체 ID"에 대해 기본적으로 힌트를 제공하여 adb가 장치를 찾도록 도와 줄 수 있습니다. 16 진 공급 업체 ID를 파일에 넣어서 수행 할 수 있습니다.~/.android/adb_usb.ini

그러나 먼저 공급 업체 ID 값을 찾아야합니다. 다행히도 Mac에서는이 작업이 매우 쉽습니다. 시스템 정보 응용 프로그램을 시작하십시오 . 그것은에 위치한 /Applications/Utilities/폴더 또는 상단이 화면의 상단 왼쪽에 당신은 "추가 정보 ..."버튼을 클릭, "이 매킨토시에 관하여"를 선택, Apple 메뉴를 통해 얻을 수 있습니다. 스크린 잡아요 :

"하드웨어"트리를 확장하고 "USB"를 선택한 다음 대상 장치를 찾으십시오. 위의 예에서 내 장치의 이름은 "SomeDevice"입니다 (실제 장치 제조업체를 숨기기 위해 Photoshop에서 수행했습니다). 또 다른 예는 "SAMSUNG_Android"로 표시되는 Samsung 태블릿입니다 (btw, Samsung 태블릿을 작동시키기 위해 특별한 작업을 수행 할 필요는 없습니다.) 어쨌든 장치를 클릭하면 세부 정보가 아래 창에 표시됩니다. 공급 업체 ID가 표시됩니다. 스크린 샷의 예제에서 값은 0x9d17다음 명령에서이 값을 사용합니다.

echo 0x9d17 >> ~/.android/adb_usb.ini

adb_usb.ini이전에 해당 파일을 가지고 있지 않은 경우 괜찮습니다 . 대부분의 경우 장치를 찾는 데 필요하지 않으므로 파일이 존재하지 않는 것은 드문 일이 아닙니다. 위의 명령은 명령을 작성하거나 이미 존재하는 경우 맨 아래에 추가합니다. 이제 위에 나열된 명령을 실행하여 adb를 다시 시작하십시오.

adb kill-server ; adb devices

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached 
123ABC456DEF001 device

---

EasyTether 응용 프로그램을 설치 한 경우 ADB를 방해 할 수 있습니다.

이 페이지 에서 다음 명령을 실행할 수 있습니다.

sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext 

EasyTether 확장이 언로드됩니다.

테 더링을 위해 EasyTether를 다시 활성화해야하는 경우 다음을 사용할 수 있다고 생각합니다.

sudo kextload /System/Library/Extensions/EasyTetherUSBEthernet.kext 

이것은 내 Samsung Galaxy S2에서 작동했습니다. 필자의 경우 재부팅 할 때마다 kextunload 명령을 실행해야했습니다.

---

OS X 용 Nexus 4 및 Nexus 5 전용 솔루션

Got no device listed in the "List of devices attached" when I ran: adb devices

Fix:

1. Get the SDK (Latest Version) from developer.android.com
2. Put developer mode on nexus 4 ( About Phone > Build Number > tap 7 times to enter Dev Mode)
3. A new menu option will come up in the 'Settings' : { } Developer Options
4. Make sure you check the following under { } Developer options:
   • USB Debugging : Debug mode when USB is connected (Accept the RSA fingerprint popup)
   • Verify apps over USB : Check apps installed via ADB/ADT for Harmful behavior

Try listing your device from ./adb devices and it should work.

Answer taken from: Any idea why adb does not recognize my nexus 4 on mac

---

If you are using following devices:
Samsung S3 GT-I9305 (Android 4.1.2)
Mac OS 10.6.8

Do following:

# echo "0x04e8" >> ~/.android/adb_usb.ini
# adb kill-server
# adb devices

(if you are not using Samsung device, change the Vendor ID "0x04e8" to the correct value of your Vendor)

If still not working, you may want to try following:

(1) On your Samsung device, disable "USB Debugging" and re-enable it again
(and try the adb commands again)

(2) Disconnect the USB cable, and re-connect it again

(3) Uninstall Samsung Kies

(4) Install Android File Transfer

(5) Reboot your Mac and the Samsung device

(6) Use hardware device to test your Android app

After getting the devices connected but you suddenly unplug the USB cable, and suppose now "adb devices" cannot see your device any more, even after "adb kill-server", in this case, you may want to try the following:

(1) power off your Mac
(2) disable "USB debuggine" on your Samsung device
(3) power off your Samsung device
(4) power on your Mac
(5) power on your Samsung device
(6) enable "USB debuggine" on your Samsung device
(7) connect the USB cable
(8) Run "adb devices"
(9) You should see the attached device now

---

Believe it or not, swapping USB cables solved this for me. I'd been using a random one (which wasn't working), and as soon as I switched over to one that came with an actual Android device, it worked.

Another sign that the good cable was working, was that the Android File Transfer app immediately launched, which wasn't happening with the crappy cable.

---

I had a similar issue. I've discovered that MTP is not supported in OSX. I changed it to PTP, I was promoted to approve my laptop and then my device was finally listed (LG G3).

---

Also make sure you are not using an USB cable designated for charging only. This just got me. And it actually was labelled "for charging only"

---

This only worked for me after I've enabled developer usb debugging on the phone:

On your android phone, go to Settings > About, then tap repeatedly on Build Number until Developer Options is enabled.

---

In my case, it was because the USB cable.

I discovered there are two types of USB cables:

• Those that only supply power
• Those that supply power and can transfer data

And it's hard to know what type is a USB cable. Now I make a notch on my cables with data transfer.

---

NOTE TO FOLKS WHO CANT GET ANY OF THIS ADVICE TO WORK

Try launching Console.app and watching for errors when you plug in your device. I was getting

# The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying.

It persisted after reboots, so I eventually reset my PRAM and that got it working again.

HOW TO PERFORM A PRAM RESET

1. Shut your machine down completely.
2. Briefly hit the power button
3. Hold down Command + Option + P + R
4. Wait until you hear the boot chime for a 3rd time
5. Release all keys and let the machine continue to boot completely

---

Here is another thing to try, if like me you have tried all of the other answers and have had no luck.

In my case (Android 4.3) I went into the USB settings under the notifications and changed from MTP mode (Media device) to PTP (camera) and as soon as it switched, the device showed up in the ADT device list.

---

I was experiencing the same issue and the following fixed it.

• Make sure your phone has USB Debugging enabled.
• Install Android File Transfer
• You will receive two notifications on your phone to allow the connected computer to have access and another to allow access to the media on your device. Enable both.
• Your phone will now be recognized if you type 'adb devices' in the terminal.

---

With the newer adb version, you have to remove ~/.android/adb_usb.ini

---

Simply changing the cable and Authorizing the Mac worked for me!

---

Just in case it helps somebody in the future, I had accidentally turned off "USB debugging" in my settings when I was enabling/disabling "Show layout boundaries". So, first check this setting in your "Developer options".

---

I switched to a different USB port and that got it to show up in the adb devices list.

That was the only thing that worked for me of all the solutions proposed here. It was proposed by @user908643 in this comment.

---

Also make sure you check the vendors website for their "USB" drivers. I had this problem with my AT&T Galaxy Note (Running Android 2.3.6) and it wasn't being recognized by the adb without a driver install that I got from the samsung website.

---

if you are trying to detect a samsung galaxy s3, then on the phone go to settings -> developer options -> make sure usb debugging is checked

---

Its damn strange but just plugging to the USB port located next to Thunderbolt port on my mid-2014 MBP with Retina worked!

The other USB port would simply not recognise the device.

---

On the LG G3 I was able to get it working by installing ADB via homebrew (Installing ADB on MAC OS X) and then disabling/enabling USB debugging.

---

Try rebooting (if it was ever detected before and stopped showing up) - the mother of all solutions!

---

Tried all the above, the last piece missing was to enable USB Debugging within Developer Options which was hidden on my 4.4 Galaxy Note 10.1.

See item 5.2 from this link.

---

None of the tips above worked for me on my Mac OS X Lion set up. I have Motorola phones running 2.3.6. It turns out that I needed to install drivers for Motorola phones. I found them here.

---

Another tricky thing with modern Android is you set the device behavior by selecting "Use for" of the device.

If it is set as "Use for" charging for example the device won't be detected by ADB. switching to PTP/MTP other behavior which is more 'active' will auto-magically make your device detectable.

---

I had a devil of a time with this.

I attempted this method but it did not work. I ended up turning OFF USB debugging and the device then requested that install motocast.

It attempted to use the build in installer but it kept crashing past the download. After I downloaded it manually and installed it, I was able to do it.

I am running 10.6.8 and the device is a Xoom 2 running 3.2.2

After that installation, it worked fine.

---

In case, like me, none of the above worked for you, I figured out a very stupid solution.

I'm using a HTC One X on a 2011 Macbook Pro. I just disabled NFC in Settings > Wireless & Networks > More > NFC and viola! Working normally.

---

I have seen this problem and tried every solution on stackoverflow and other sites, but nothing help me.

I have restarted adb, switching on developer mode and activating usb debugging, uninstalling samsung kies and even exchanging the usb cables to different ports.

But then I read somewhere that different usb cable use different pins for connecting to the laptop or computer.
So I used different usb cable to connect my samsung phone to mac .. and vowwww it works... for me......

---

In my case, USB debugging wasn't enabled on my device yet connecting the device to my macbook didn't cause the familiar "Allow USB Debugging" dialog to pop up on the screen.

---

I was trying to connect an old phone that I use to test apps on older API versions. Today adb was not finding it.

After trying pretty much everything here, I figured out that the phone was not even showing the system notification about the USB connection going on.

So I looked around for that issue, and found the solution here (credits to the original source):

1. Remove phone from PC and remove battery to shut off phone.
2. Plug USB cable into PC.
3. Plug USB cable (other end) into phone.
4. The PC install new hardware appropriate drivers for a few minutes (phone without battery)
5. Unplug USB cable from phone
6. Put battery back in and turn on phone
7. 전화가 부팅 될 때 볼륨을 올리거나 내립니다. 전화가 안전 모드로 부팅됩니다.
8. 휴대 전화에 USB 케이블을 연결합니다.
9. 전화기에서 USB MTP 연결에 대한 알림을 받았습니다. PC가 내 전화를 찾았습니다!
10. 정상 모드에서 재부팅 후 문제가 수정되었습니다

macOS에서 4 단계를 사용하고 있는지 확실하지 않지만 모든 단계를 수행했으며 제대로 작동했습니다.

---

나는 가능했다 USB debugging (Security settings)외에도 개발자 옵션 USB debugging에서 Redmi 주 4 .

참고 URL : https://stackoverflow.com/questions/7135999/adb-not-finding-my-device-phone-macos-x