Database Users

Remote Debugging?

So I can't get my phone to remote debug in chrome. Every time I issue the adb forward tcp:9222 localabstract:chrome_devtools_remote my device is not found...
I tapped on the build number in about phone to enable the dev options. I selected USB debugging in developer tools as well as chrome but its still not working.
Has anyone been able to get this to work? I have searched around and can't find anything about the nexus 4 and remote debugging.

What does adb devices say?

Just says list of devices attached and doesn't show anything.
When I plug in my phone I know it is detected, it shows up as Nexus 4 in windows explorer.
I don't get it...

Your drivers aren't installed properly.
1. Ensure USB debugging is enabled (as you said it is... but double check anyways)
2. http://forum.xda-developers.com/showthread.php?t=1514942 use those drivers instead. follow the steps there.

zephiK said:
Your drivers aren't installed properly.
1. Ensure USB debugging is enabled (as you said it is... but double check anyways)
2. http://forum.xda-developers.com/showthread.php?t=1514942 use those drivers instead. follow the steps there.
Click to expand...
Click to collapse
Thanks, it was the driver.

bowenac said:
Thanks, it was the driver.
Click to expand...
Click to collapse
Hit the thanks button if I helped thanks very much

[Q] mtp vs ptp

Please help if you can
My first 32gb Nexus 7 had no problems showing up as an mtp device on windows 7.
Am running a rooted 4.1.2 and all is well with mtp as well as adb, toolkits, etc.
I purchased one more as a gift, and that one can only be set to ptp in the internal storage settings.
If I try to set it to mtp, it takes, but does not show up in windows or in adb.
The only way to see it or use adb or a toolkit on it, is to set it to ptp which shows up as a camera with read only permissions.
Both tablets are using the same rom etc.
Have tried this on 2 PC's (win 7 as well as xp)
Any Ideas?
Thanks

On my (rooted) Stock 4.2.1 tablet, MTP mode only seems to show up if ADB Debugging is enabled.
Sort of odd; PTP will work whether or not ADB Debugging is turned on, but MTP only shows up when ADB debugging is also enabled.
If you have not enabled "Developer Options" on the tablet, go to
Settings->About tablet
and tap on the last entry ("Build number") 6 or 7 times in succession. This will allow the following menu item to appear under settings:
Settings-> {} Developer options
You can enable ADB debugging from there.
The PTP/MTP toggle control is at
Settings -> Storage -> Menu (top RH corner) -> USB Computer connection
good luck

MTP vs PTP
bftb0 said:
On my (rooted) Stock 4.2.1 tablet, MTP mode only seems to show up if ADB Debugging is enabled.
Sort of odd; PTP will work whether or not ADB Debugging is turned on, but MTP only shows up when ADB debugging is also enabled.
If you have not enabled "Developer Options" on the tablet, go to
Settings->About tablet
and tap on the last entry ("Build number") 6 or 7 times in succession. This will allow the following menu item to appear under settings:
Settings-> {} Developer options
You can enable ADB debugging from there.
The PTP/MTP toggle control is at
Settings -> Storage -> Menu (top RH corner) -> USB Computer connection
good luck
Click to expand...
Click to collapse
Thanks, but I guess I was not very clear.
ADB Debugging is turned on but only works in PTP mode.
MTP does not work at all, even though it's checked.

ganovim said:
Thanks, but I guess I was not very clear.
ADB Debugging is turned on but only works in PTP mode.
MTP does not work at all, even though it's checked.
Click to expand...
Click to collapse
Even after reading this and your 1st post, I am still a little uncertain.
I *think* you are saying that you want to get MTP working on the second unit. And I *think* you are also saying that (additionally) ADB only seems to work when you have PTP mode selected.
Reading between the lines - are you testing things with the same computer for both tablets? (Or, another way to put that, if the answer to this previous question is no, do you see any "Unknown Device" messages in the Device Manager when you toggle things around?)
I fooled around with mine not more than 30 minutes ago. Leaving it plugged into the PC the entire time (Win 7 Pro x64), I could toggle USB Debugging on/off and back and forth between PTP/MTP. Although I didn't actually try a live ADB session in both MTP/PTP modes, the file browser thing would pop up for PTP mode no matter what I had ADB debugging set to, and for MTP mode that would only happen if I had ADB debugging enabled. At no time did I see any unrecognized devices in the Device Manager.
And I think that what I just said above doesn't help you.... arghh.

MTP vs PTP
bftb0 said:
Even after reading this and your 1st post, I am still a little uncertain.
I *think* you are saying that you want to get MTP working on the second unit. And I *think* you are also saying that (additionally) ADB only seems to work when you have PTP mode selected.
Reading between the lines - are you testing things with the same computer for both tablets? (Or, another way to put that, if the answer to this previous question is no, do you see any "Unknown Device" messages in the Device Manager when you toggle things around?)
And I think that what I just said above doesn't help you.... arghh.
Click to expand...
Click to collapse
First of all thanks for the interest.
Bottom line is as follows.
MTP mode does not work period.
However....
when I boot into recovery, (TWRP) the pc sees the usb connection, and I can use adb commands.
So it leads me to conclude that there is something off in the System files. But (and it's driving me nuts)
they are a clone of the first (MTP functioning) Nexus 7.
Thanks again

@OP
You can uninstall the drivers(all of the n7 drivers), then unplug, then replug it in, then let it install its drivers again. This solved the mtp issues other users had.

Nexus 4 cannot be recognized as MTP after root

I'm running Windows 7 64bit and followed the Ultimate guide to unlock and root my Nexus 4.
Everything went well but now it looks like that Windows won't recognize my phone as a device. When I plug in the phone, the auto-play window will pop out and recognize it as Nexus 4, but there is no other options. (Normally the auto-play will ask if open folder to view files or transfer photos). I can't see my phone in device manager either.
If I turn on the USB debugging mode, I can see it in device manager but still cannot see it in My Computer. Looks like Windows can't access the SD card at all.
I tried switching to the camera mode but the problem remained. Please help.

desperate bump. can anyone help?

Maybe it's a stupid advice, but have you tried change the USB port in PC?

glancer2315 said:
desperate bump. can anyone help?
Click to expand...
Click to collapse
Plug in the phone, uninstall the drivers from Device manager, then unplug, and replug.

Colourkey said:
Maybe it's a stupid advice, but have you tried change the USB port in PC?
Click to expand...
Click to collapse
yes, i did.

abaaaabbbb63 said:
Plug in the phone, uninstall the drivers from Device manager, then unplug, and replug.
Click to expand...
Click to collapse
thanks for your advice. the problem is that, without USB debugging mode on, I can't see Nexus 4 in Device manager, even though the Windows Auto-play will say Nexus 4 connected. (Nothing in My Computer either)
With USB debugging mode on, I uninstalled the driver and Windows would try installing the driver. Now it shows up as MTP device with an exclamation mark. I tried manually update the driver (direct it to the Google SDK folder and pick the android_windowsusb.inf) but it says it does not support x64. I don't think the 64 bit driver is digitally signed.

I think I had a similar problem as yours. If you deleted the drivers while on debugging mode and reconnected after and it's showing the exclamation mark of a unknown device, try restarting your computer and plugging your phone back in.

SovereigN7 said:
I think I had a similar problem as yours. If you deleted the drivers while on debugging mode and reconnected after and it's showing the exclamation mark of a unknown device, try restarting your computer and plugging your phone back in.
Click to expand...
Click to collapse
i did and it remains the same.
Is there anyway I can know all the files names of the drivers so that I can manually delete them from system folder? When I uninstalled it from the device manager, I don't see the option "Delete the driver software for this device".
I can still see it under "adb devices" list.

I think there are some conflicts in the drivers.
Now when I connect Nexus 4 (without USB debugging mode on), it will show up in device manager under Android Device.
With USB debugging, it will then show up under Portable Devices.
However, it's supposed to work the other way around. that is (no USB debugging --> portable device; with USB debugging --> Android Device).
How can i solve this?

Have you tried manually installing the drivers before plugging in the phone, vs letting windows choose the drivers it wants to install? One option you could try is installing PDA Net on your pc. It will install reliable drivers on your pc.

i also had this same problem after flashing my first custom rom on the n4, and i also run windows 7 Ultimate x64
here is the process i use for full clean installation of device
on phone
goto SETTINGS > STORAGE > (menu) USB Computer Connection
make sure Media Device (MTP) is checked
With USB Debugging On
On your PC go to device manager
there should be 2 devices (Android Phone > Android Composite ADB Interface & Portable Devices > Nexus 4) - this is on a fully working n4 so you might only have 1 of them
Right click on each of them and click uninstall
The popup box should have another check box to delete the driver also, if this is available check it then confirm (note mine only has the box for Android Phone > Android Composite ADB Interface, but if yours has it on both then check it on both)
your computer will now ask you to restart, dont do it yet
repeat previous step for the other device if you have 2 then reboot
upon rebooting it will automatically start reinstalling drivers
by expanding the selection you should see 2 devices
Nexus 4 - Successful - Ready To Use (this is your MTP connection)
Nexus 4 - Unsuccessful - No Driver Found (this is your ADB Connection)
at this point you should be able to access internal storage however ADB will not work
go back into device manager
you should now have
Portable Devices > Nexus 4
and Other Devices > Nexus 4 (with yellow exclamation mark)
right click on the Other Devices > Nexus 4 (with yellow exclamation mark)
hit Update Driver Software
click Browse my computer for driver software
click Let Me Pick Drom a List of Device Drivers On My Computer
double click Show All Devices
click Have Disk...
click Browse
navigate to the download directory for the google usb drivers (for me this was "C:\Program Files (x86)\Android\Android-SDK\Extras\Google\Usb_Driver")
double click on the android_winusb.inf file
click OK
double click "Android Composite ADB Interface"
it will then install the driver for ADB
you should now have full access to internal storage and ADB

Alex240188 said:
i also had this same problem after flashing my first custom rom on the n4, and i also run windows 7 Ultimate x64
here is the process i use for full clean installation of device
on phone
goto SETTINGS > STORAGE > (menu) USB Computer Connection
make sure Media Device (MTP) is checked
With USB Debugging On
On your PC go to device manager
there should be 2 devices (Android Phone > Android Composite ADB Interface & Portable Devices > Nexus 4) - this is on a fully working n4 so you might only have 1 of them
Right click on each of them and click uninstall
The popup box should have another check box to delete the driver also, if this is available check it then confirm (note mine only has the box for Android Phone > Android Composite ADB Interface, but if yours has it on both then check it on both)
your computer will now ask you to restart, dont do it yet
repeat previous step for the other device if you have 2 then reboot
upon rebooting it will automatically start reinstalling drivers
by expanding the selection you should see 2 devices
Nexus 4 - Successful - Ready To Use (this is your MTP connection)
Nexus 4 - Unsuccessful - No Driver Found (this is your ADB Connection)
at this point you should be able to access internal storage however ADB will not work
go back into device manager
you should now have
Portable Devices > Nexus 4
and Other Devices > Nexus 4 (with yellow exclamation mark)
right click on the Other Devices > Nexus 4 (with yellow exclamation mark)
hit Update Driver Software
click Browse my computer for driver software
click Let Me Pick Drom a List of Device Drivers On My Computer
double click Show All Devices
click Have Disk...
click Browse
navigate to the download directory for the google usb drivers (for me this was "C:\Program Files (x86)\Android\Android-SDK\Extras\Google\Usb_Driver")
double click on the android_winusb.inf file
click OK
double click "Android Composite ADB Interface"
it will then install the driver for ADB
you should now have full access to internal storage and ADB
Click to expand...
Click to collapse
thank you for your long and detailed reply.
this is what i wanted to do, but the problem is that when I uninstall them, I don't get to see the option "delete the driver software for this device". What should I? cuz every time I plug in Windosws just tries to automatically install the driver for me.

Have you tried toggling to ptp mode then back to mtp on your phone. It's odd indeed.
The fact that you can't remove the driver is because that is the mtp one which is built in to media player. Let me give this some more thought
EDIT: You said that with USB debugging disabled your device is listed under device manager as an android device
can you check and verify exactly what it is listed as? as it should be portable device
Sent from my Nexus 4 using xda app-developers app

Alex240188 said:
Have you tried toggling to ptp mode then back to mtp on your phone. It's odd indeed.
The fact that you can't remove the driver is because that is the mtp one which is built in to media player. Let me give this some more thought
EDIT: You said that with USB debugging disabled your device is listed under device manager as an android device
can you check and verify exactly what it is listed as? as it should be portable device
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
hi under android device it shows up as Android adb device
under portable device i can it now showing up as MTP USB device with exclamation mark.

glancer2315 said:
hi under android device it shows up as Android adb device
under portable device i can it now showing up as MTP USB device with exclamation mark.
Click to expand...
Click to collapse
does adb work?
i.e. adb devices
or is USB debugging turned off at this point
Also. The one with the exclamation mark. Right click and go to properties. What does it say in device status

Alex240188 said:
does adb work?
i.e. adb devices
or is USB debugging turned off at this point
Also. The one with the exclamation mark. Right click and go to properties. What does it say in device status
Click to expand...
Click to collapse
hi, adb devices works. (will list my device when usb debugging is on)
with usb debugging off, under portable device, the device status says "This device cannot start. (Code 10)". thanks.

still looking for solutions. maybe i should try uninstalling the ADB driver, but the problem is that when i uninstall the device from the device manager I don't see the option "delete the driver software for this device", any help?

glancer2315 said:
still looking for solutions. maybe i should try uninstalling the ADB driver, but the problem is that when i uninstall the device from the device manager I don't see the option "delete the driver software for this device", any help?
Click to expand...
Click to collapse
I have this same issue I'm trying to find a fix, that's how I found your thread. Alex gave very good info make sure you go back to his posts and hit his "Thanks" button, I did it on everyone one of his posts in this thread. I'm starting to think it's a hardware issue and not a software issue, I've never had this issue on any device. When I got it new running stock 4.2.2 MTP didn't work. ADB works and PTP works, just not MTP no matter what I try. I recommend you learn to use, ADB push and pull to move your files if you don't already know how to use it (To use ADB I need to check PTP for it to work and not MTP) you might need to do the same. I will keep you posted if I find a fix.
Sent from my Nexus 10 Pimpin AOKP 4Life

I'm just getting more and more confused with this.
If Adb works then you must have an Adb driver installed for the phone. However your also stating that you get no box for uninstall driver.
With USB debugging disabled you said that it appears as an android phone rather than a portable device. This should not be.
With debugging disabled what happens if you Try to uninstall in device manager
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 01:54 PM ---------- Previous post was at 01:51 PM ----------
My theory still stands that you have updated the mtp driver with adb drivers. Hence why mtp doesn't work but ptp does.
The problem is getting to a position where you can uninstall the adb drivers from the mtp device and let it reinstall the proper drivers
Sent from my Nexus 4 using xda app-developers app

I plugged another Nexus 4 in, and all the drivers loaded perfectly. I then tried my Nexus 4 phone, and nothing happens. No mtp, no adb, no boot loader drivers. Its my phone. My next step is to find a zip file that I can flash via custom recovery, which will bring all the binaries and ROM back to stock. Anybody know where I can find this? I'll probably lose the custom recovery, but hopefully it will be fixed and I can flash the custom recovery again.
LG-E960

[Q] N4 & Lollipop & MTP

Hello,
Since the update of my Nexus4 to lollipop , it is no longer recognized by my PC running Windows 7.
ADB can view the phone when USB debugging is switched on.
When it is off, nothing.
Device manager displays : Android Device/Android Composite ADB Interface in USB debugging.
When it is off, nothing.
Any help ?
Thanks
edited for more information...

yauyau said:
Hello,
Since the update of my Nexus4 to lollipop , it is no longer recognized by my PC running Windows 7.
ADB can view the phone when USB debugging is switched on.
When it is off, nothing.
Device manager displays : Android Device/Android Composite ADB Interface in USB debugging.
When it is off, nothing.
Any help ?
Thanks
edited for more information...
Click to expand...
Click to collapse
Thats normal. ADB requires usb debugging to be turned on.

venu123 said:
Thats normal. ADB requires usb debugging to be turned on.
Click to expand...
Click to collapse
Seems not quite normal to me. Because besides a ADB connection, there should be an MTP connection and Game connection.
---------- Post added at 02:57 PM ---------- Previous post was at 02:48 PM ----------
venu123 said:
Thats normal. ADB requires usb debugging to be turned on.
Click to expand...
Click to collapse
Assuming you have the android drivers on you PC. and USB debugging ON
Go to settings -> Storage -> Hit the three dots in to top right -> USB Computer Connection -> and check MTP box.
So MTP is hidden and disabled by default. Why is unclear. Seems a small bug to me.

ADB does not prompt to accept any USB debugging authorization after root

Hi,
I recently rooted my Samsung Galaxy Tab A thanks to the wonderful folks of this forum. However, now that it's rooted I can't seem to connect to it via adb. For example, I see the device listed when I run "adb devices", but it is listed as "unauthorized". I no longer received the prompt to allow USB debugging. More precisely, I can still access the developer options and see that "USB debugging" is enabled, I just don't receive the pop-up prompt to "Allow USB debugging?" that list my local computer's RSA fingerprint/etc after I plug in the usb... the device just remains unauthorized and never asks me to click ok to allow usb debugging.
As suggested elsewhere, I tried removing the adbkey and adbkey.pub in the .android directory on my local computer and the killing/starting the adb server to generate new keys on the local machine, but that also doesn't seem to help...
Additionally, I noted that there is also no longer a button under developer option to "Revoke USB authorizaiton" (maybe because there are now no longer any keys in /data/misc/adb/adb_keys ?)
Any idea how to get adb shell to work again? Or maybe it not possible after rooting?
Thanks!

__adam_ said:
Hi,
I recently rooted my Samsung Galaxy Tab A thanks to the wonderful folks of this forum. However, now that it's rooted I can't seem to connect to it via adb. For example, I see the device listed when I run "adb devices", but it is listed as "unauthorized". I no longer received the prompt to allow USB debugging. More precisely, I can still access the developer options and see that "USB debugging" is enabled, I just don't receive the pop-up prompt to "Allow USB debugging?" that list my local computer's RSA fingerprint/etc after I plug in the usb... the device just remains unauthorized and never asks me to click ok to allow usb debugging.
As suggested elsewhere, I tried removing the adbkey and adbkey.pub in the .android directory on my local computer and the killing/starting the adb server to generate new keys on the local machine, but that also doesn't seem to help...
Additionally, I noted that there is also no longer a button under developer option to "Revoke USB authorizaiton" (maybe because there are now no longer any keys in /data/misc/adb/adb_keys ?)
Any idea how to get adb shell to work again? Or maybe it not possible after rooting?
Thanks!
Click to expand...
Click to collapse
I finally solved this problem.... I don't think it was particular to the Galaxy Tab A.
In order to get adb working again I had to put the device into recovery mode (power down, then power up while holding power, up-volume, home button). I then went to the terminal application of the Team Win Recovery. In terminal I issues "stop adbd" then "start adbd". At this point the device now shows up on the local host PC when I run "adb devices" (it shows up as "recovery" rather than unauthorized). I can adb root/shell to the device now. This is really all I need to do. I expect this will solve my problem in non-recovery mode as well. Or, at this point I can push my PC pub key to the device and it should be fine.