I can't connect adb on any 4.2.2 ROMS, i understand theres a new security feature in 4.2.2 that should prompt you to confirm your PCs RSA key, but i never get this prompt. Also, ktoonsez kernel seems to bypass the security, as it allows me to connect without ever seeing the prompt. But any other kernel, no prompt, and all adb commands show device offline.
I do have the latest version of adb (1.0.31) and the latest sdk etc.., i also can't connect to adb using the USB cable either. I've tried reinstalling drivers, rebooting... nothing seems to be working.
any suggestions?
Edit: got it working. Can't say i know exactly what i did to fix it, but i'll try to reiterate what i just did. Clean flashed a new ROM, in developer options > root access set to Apps and ADB, make sure Android debugging is enabled, make sure USB debugging notify is enabled, then turn on adb wireless. Then on my pc connect to adb using "adb connect 192.168.1.x", adb devices shows device still offline. Then connected my phone to my pc through usb and i got the prompt. FINALLY lol
I'm sure you already did this, but you didn't mention it.
In a lot of 4.2.2 ROM's, you have to go into Developer Options and change from "Root access for Apps Only" to "Root Access for Apps and ADB".
Not all 4.2.2 ROM's do this, but some of them do.
I could not ADB from my computer to my 4.2.2 until I changed that selection.
Also, some new ROM's have the built-in Superuser which includes an ADB option in its settings.
CZ Eddie said:
I'm sure you already did this, but you didn't mention it.
In a lot of 4.2.2 ROM's, you have to go into Developer Options and change from "Root access for Apps Only" to "Root Access for Apps and ADB".
Not all 4.2.2 ROM's do this, but some of them do.
I could not ADB from my computer to my 4.2.2 until I changed that selection.
Also, some new ROM's have the built-in Superuser which includes an ADB option in its settings.
Click to expand...
Click to collapse
Tried it, no luck.
Maybe try this?
https://plus.google.com/+CyanogenMod/posts/M2pVM7Y6MTq
CZ Eddie said:
Maybe try this?
https://plus.google.com/+CyanogenMod/posts/M2pVM7Y6MTq
Click to expand...
Click to collapse
I appreciate the input but all that post says is that you must be on the latest SDK version which I mentioned I already was
i cant seem to connect thru adb or fastboot usb. adb doesnt show anything under "adb devices" and fastboot doesnt give me "USB" icon if i plug it in to a usb. i've tried multiple wires. i tried on my macbook and on a windows 7 machine. played around with htc drivers. cant seem to make it work. tried unmounting and remounting the sdcard and rebooting all devices.
i was going to try adb over wifi but you need to root for that. without adb or fastboot, i cant even htcdev unlock.
any other ideas? i plug it in and it shows a charging icon in the batter bar but no mounting options show up in the notification bar. usb debug is enabled. i tried the different "mount as" options in the settings menu. i've read countless web pages to try to get this to mount to any computer so i can mod it a little but nothing seems to work.
Revoke the USB debugging authorizations and then connect to the computer?
Sent from my Nexus 7 using xda app-developers app
Also make sure Fastboot is unchecked under power settings.
havikx said:
i cant seem to connect thru adb or fastboot usb. adb doesnt show anything under "adb devices" and fastboot doesnt give me "USB" icon if i plug it in to a usb. i've tried multiple wires. i tried on my macbook and on a windows 7 machine. played around with htc drivers. cant seem to make it work. tried unmounting and remounting the sdcard and rebooting all devices.
i was going to try adb over wifi but you need to root for that. without adb or fastboot, i cant even htcdev unlock.
any other ideas? i plug it in and it shows a charging icon in the batter bar but no mounting options show up in the notification bar. usb debug is enabled. i tried the different "mount as" options in the settings menu. i've read countless web pages to try to get this to mount to any computer so i can mod it a little but nothing seems to work.
Click to expand...
Click to collapse
have you downloaded sdk manager and put the path of platforms tools folder in path on the environment variables?
atticustcx said:
have you downloaded sdk manager and put the path of platforms tools folder in path on the environment variables?
Click to expand...
Click to collapse
I have the same problem with my HTC One.
nasvi said:
I have the same problem with my HTC One.
Click to expand...
Click to collapse
i think is same here, i dont have any system in my htc one, only recovery, and cannot push file from anyway
bump
been having same problem, no menus or anything when plugged into usb just charging
try reinstalling your device drivers and make sure you have android sdk installed. ive had this issue before and all i had to do was reinstall the drivers. and make sure you have fastboot for the htc bec using other fastboot can cause issures with recognition of your phone.
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
http://www.mylgphones.com/tag/usb-drivers try these drivers
That's the ones that didn't work.
Same problem here... Any luck?
Change the USB mode to PTP and you should get the RSA prompt.
anod said:
Same problem here... Any luck?
Click to expand...
Click to collapse
Yes I have install Google universal usb drivers worked for me search on Google for them
PTP worked for me, no LG driver installed.
Just got my G3 on Verizon, cannot see the device over ADB either on Mac OSX
I tried MTP, PTP, and Charge only both with and without LG drivers installed. Since it's OSX, there are no Google Universal USB drivers.
Android File Transfer opens up fine, but ADB doesn't show the device. Quite fishy indeed.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
May I ask how you managed to connect your phone to your mac via MTP? I am unable to get any kind of connection to my mac.
On windows it works finde, I can open the internal and external sd card and copy files from and to the device, I would be more than happy to achive the same on my mac.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
Hi there, you will first need to enable USB Debugging. Head over to Settings > General > About Phone > Software Information. Tap Build Number 5 times, and you'll unlock the Developer options.
Go to Settings > Developer options, and check USB Debugging. From there, ADB should work. Good luck!
OK, so I installed the new drivers, rebooted, and got ADB to recognize my LG, and was able to debug successfully. Now Android File Transfer doesn't see it, nor does Finder show the device. What am I missing?
It's broken, I saw a tweet from jcase regarding the issue. I have the same problem. I just adb push/pull when necessary for now.
Sent from my LGLS990 using XDA Free mobile app
EDIT - It wasn't jcase, it was @utoprime
Mine works fine on my Mac
faded03cobra said:
Mine works fine on my Mac
Click to expand...
Click to collapse
You have adb and MTP works? What OSX version?
Sent from my LGLS990 using XDA Free mobile app
Solution
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
I know this is a seriously old thread, but for future reference - if your device is NEVER recognised by adb from the start, no matter how much you add the vendor etc, open up Terminal.app and type this in:
cd ~/.android/
rm adbkey adbkey.pub
This will navigate to android's folder and remove the RSA keys your computer uses to identify with the phone. If the address of the folder is wrong you can alter the first line to whatever is appropriate.
KAR0SH1 said:
I know this is a seriously old thread, but for future reference - if your device is NEVER recognised by adb from the start, no matter how much you add the vendor etc, open up Terminal.app and type this in:
cd ~/.android/
rm adbkey adbkey.pub
This will navigate to android's folder and remove the RSA keys your computer uses to identify with the phone. If the address of the folder is wrong you can alter the first line to whatever is appropriate.
Click to expand...
Click to collapse
Seriously old, and seriously unresolved (for me and a few people on reddit, at least). Still have not succeeded at getting ADB to detect G3 on USB, tried running the -usb flag on the cli and everything. Is there a working process yet? Verizon seems to be the outlier here as well...
Just worked for me on OSX Yosemite with a D855 on V10l:
- Update ADB (android platform tools)
- Install LG Driver (link is in this thread)
- Reboot
- run "rm ~/.android/adbkey" and "rm ~/.android/adbkey.pub"
- run "adb devices" (you should now see your G3)
- run "adb kill-server" (just to make sure there is no interference)
- quit all applications on your phone and go to home screen
- run "purpledrake_osx.command" which should now work
Inbetween (guess it was directly after running "purpledrake_osx.command") you should get a permission request on your phone which you should allow
Thanks
_ranch said:
Change the USB mode to PTP and you should get the RSA prompt.
Click to expand...
Click to collapse
Thanks, this works for me on El Captain
Also on El Capitan:
After enabling developer settings + USB debugging on phone (see earlier in thread),
Removing the adbkey + pub from the users .android folder (see earlier in thread),
and connecting with PTP,
It finally works
Like it says my display is completely broken :'(
The phone starts up and I hear the Samsung tune start and then it connects to computer.
However it connects as a fresh install. I'm almost certain USB Debugging is on, but I don't believe I had hooked it up to a pc on the Rom yet so I have not selected Mtp mode yet. Its modified Touchwiz kk not cm.
Is there an easy method to command it to connect through mtp before or with simple adb commands?
Or do I have to download Android sdk and go full adb everything?
Sent from my SPH-D700 using XDA Free mobile app
I'm trying to get my G7 connected back to my laptop with ADB after upgrading to Android 10, and every time I go to click on Allow to allow USB Debugging, I get an error message on my phone saying "Because an app is obscuring a permission request, Settings can't verify your response" and I can't get ADB to work. I'm trying to enter a shell command to allow System UI Tuner app to work again.