I've encountered an odd error, and I'd prefer not to factory reset. Ever since I upgraded to Oxygen OS2.1 (and subsequently installed AK Kernel), nothing happens when I plug my phone into any computer. However as soon as I disable USB Debugging in Dev Settings, the phone is immediately recognized. Has anyone else encountered this, and if so, how did you fix it?
The drivers that are on the phone didn't work for me with debugging on , assuming that's what you used? I grabbed the drivers from the android sdk and that seems to work fine.
dcontrol said:
The drivers that are on the phone didn't work for me with debugging on , assuming that's what you used? I grabbed the drivers from the android sdk and that seems to work fine.
Click to expand...
Click to collapse
I'll give that a try. Thanks!
Related
Hi guys,
after unocking bootloader and so on, i cannot connect the n4 as a media device. camera (ptp) and debugging works, but not mtp.
already wiped everything
someone can help me?
I had the same problem. Had to remove the Google drivers I installed to get fastboot (do this via device manager, make sure to tick the box to delete the driver files as well else it will just reinstall them)
1.Delete the Device from device manager.
2. Grab the naked drivers in teh dev forum and install them.
3.???
4.Profit
i don't think it's a driver problem, i have the same issue on both w8 and ubuntu
someone else wanna try?
If you turn off USB debugging, media device mode works.
Nexus4, Tapatalk
tyea said:
If you turn off USB debugging, media device mode works.
Nexus4, Tapatalk
Click to expand...
Click to collapse
already tryed, but still doesn't work.
also tryed to relock bootloader, unroot, but nothing.
now i'm switching back to windows7, i'll see if it will work
solved getting rid of windows8 and going back to windows7
I've googled and searched everywhere for this, but no luck. I got the S4 yesterday (AT&T) and i went through the steps to turn on developer options for the new 4.2.2 jellybean to get access to the USB debugging option. I turn USB debugging on and hook it up to my computer and it will not install the ADB interface driver (needed for PDAnet). The phone connects as if USB debugging is not turned on saying "connected as a media device" and keeps giving me the option on the computer to access storage. Anyone or everyone else having this problem?
urn357 said:
I've googled and searched everywhere for this, but no luck. I got the S4 yesterday (AT&T) and i went through the steps to turn on developer options for the new 4.2.2 jellybean to get access to the USB debugging option. I turn USB debugging on and hook it up to my computer and it will not install the ADB interface driver (needed for PDAnet). The phone connects as if USB debugging is not turned on saying "connected as a media device" and keeps giving me the option on the computer to access storage. Anyone or everyone else having this problem?
Click to expand...
Click to collapse
Did you install the drivers? Did you have the phone connected when you enabled it? If so disconnect and reconnect.
urn357 said:
I've googled and searched everywhere for this, but no luck. I got the S4 yesterday (AT&T) and i went through the steps to turn on developer options for the new 4.2.2 jellybean to get access to the USB debugging option. I turn USB debugging on and hook it up to my computer and it will not install the ADB interface driver (needed for PDAnet). The phone connects as if USB debugging is not turned on saying "connected as a media device" and keeps giving me the option on the computer to access storage. Anyone or everyone else having this problem?
Click to expand...
Click to collapse
I did the same thing and it worked for me tho..
Also, you may want to check your phone's screen after you connect it to the computer. I had to "accept" my computer's RSA key before adb could detect the device.
crawrj said:
Did you install the drivers? Did you have the phone connected when you enabled it? If so disconnect and reconnect.
Click to expand...
Click to collapse
I've done everything and tried everything I know to. I have restarted the computer, the phone, enabled and disabled usb debugging while it's connected to the pc and no conncected. I've installed the drivers PDAnet says to, but still my phone connects as if usb debugging is not on (says connected as media and pc doesn't recognize and install the adb driver). Is there anything I'm missing?
Dare{D}evil said:
I did the same thing and it worked for me tho..
Click to expand...
Click to collapse
Did you do anything different besides just turn on usb debugging?
urn357 said:
I've done everything and tried everything I know to. I have restarted the computer, the phone, enabled and disabled usb debugging while it's connected to the pc and no conncected. I've installed the drivers PDAnet says to, but still my phone connects as if usb debugging is not on (says connected as media and pc doesn't recognize and install the adb driver). Is there anything I'm missing?
Did you do anything different besides just turn on usb debugging?
Click to expand...
Click to collapse
All I did was install install the S4 drivers from Samsung. Enabled USB Debugging. Plugged it into the computer. Waited for the drivers to finish setting up. Disconnected and reconnected again just to make sure drivers were loaded. And launched ADB. Nothing else.
Edit: Oh almost forgot. I got a message on the phone saying something about a computer trying to connect do you allow it. I hit always allow or something. Sorry don't remember exactly was too long ago. That is probably it because if you weren't watching the screen you wouldn't see it.
Edit2: LOL just saw captawsm's post. Yes what he said.
captawsm said:
Also, you may want to check your phone's screen after you connect it to the computer. I had to "accept" my computer's RSA key before adb could detect the device.
Click to expand...
Click to collapse
crawrj said:
All I did was install install the S4 drivers from Samsung. Enabled USB Debugging. Plugged it into the computer. Waited for the drivers to finish setting up. Disconnected and reconnected again just to make sure drivers were loaded. And launched ADB. Nothing else.
Edit: Oh almost forgot. I got a message on the phone saying something about a computer trying to connect do you allow it. I hit always allow or something. Sorry don't remember exactly was too long ago. That is probably it because if you weren't watching the screen you wouldn't see it.
Edit2: LOL just saw captawsm's post. Yes what he said.
Click to expand...
Click to collapse
You guys on AT&T? I never got that message. I know nothing ever popped up like that. Did you get the actual driver from Samsung website for your phone? I just tried installed the one pdanet offered.
urn357 said:
You guys on AT&T? I never got that message. I know nothing ever popped up like that. Did you get the actual driver from Samsung website for your phone? I just tried installed the one pdanet offered.
Click to expand...
Click to collapse
I did not install any other drivers tho..it was all default but it did ask me to confirm the computer's RSA key
Hallelujah! I finally got it working! It must of been a driver install quirk on my pc. For anyone else with this prob who used a previous phone with pdanet on the same pc like I did ( I used a samsung infuse prior). I went and uninstalled the samsung drivers that were already on my pc and then went to the samsung site and installed the newest ones they had. Hooked the phone back up and after about 6 or 7 seconds (have no idea why it took so long) the drivers on the pc started installing again and cha ching usb debugging was working correctly. The RSA thing popped up after that.
Thanks guys for assuring me it was only my problem and not a mass-wide problem to make me troubleshoot further.
I've been having the same problem but can't seem to find the drivers on the Samsung website. Could you please post the link?
Drivers
http://www.sammobile.com/kies/
http://www.samsung.com/us/support/owners/product/SGH-I337ZKAATT
If your computer recognized (and installs drivers) when your S4 is connected via usb (not in developer mode) but does NOT recognize your S4 when connected with USB debugging this is what you might need to do. It took me 2.5 hours to find this.
Remember to have your phone set to MTP + ADB mode.
to do this:
in phone mode type *#0808#
Choose : AP on upper part and
for USB Setting, choose : MTP.
http://forums.androidcentral.com/samsung-galaxy-s4/282817-pc-cant-detect-galaxy-s4.html
Hello everyone.
I don't know since when or how, since it has been always working for me on my win7 desktop, but when I tried to connect my phone to a new Latptop (with win8) during the holidays at home, it wouldn't detect it as an MTP device.
Well, it doesn't recognise it at all, unless I put it in debug mode, then it's under unknown devices as "Nexus 4" with a failed driver installation.
But I need to get MTP working to back some things up.
I'm running AOKP's Milestone for 4.3 and franco's kernel 193.
I checked if fastcharge was enabled: No
Switched it on and back off: Nothing
Reflashed the Kernel: Nothing
Reflashed AOKP (including the stock Kernel): Still not recognised
Of course several reboots included. Tried all slots and different cables. The cables tested all work for my N7 on Kitkat.
I had issues before with franco's kernel not really disabling fastcharge when I clicked it but I managed to fix that by rebooting or switching it back on and off again. Also this doesn't really give me any clues as I reflashed AOKP which comes with a different kernel that doesn't even support fast charge..
I'm kind of clueless now, I urgently need to back up things from my phone which I now did via Airdroid, but I also need to get MTP back working for bigger files.
Thank you very much for your help!
It would be nice if someone had a suggestion before I try going back to stock.
turn off driver signature verification(ask google how to do)
install universal naked drivers.
there you go
Will it then only be recognised in debug mode? Or normal as well? Since it doesn't even appear in device manager right now when in regular USB mode
Gesendet von meinem Nexus 4 mit Tapatalk
Try the way @opssemnik said, maybe your driver isnt work
andredn8 said:
Try the way @opssemnik said, maybe your driver isnt work
Click to expand...
Click to collapse
I had this problem. Try deleting all android drivers and MTP drivers from your PC using USBDeview (google it). Also try connecting to a different PC to see if the phone can connect at all. Finally, you may need to unlock the lock screen before attaching. After that it connects no problems!
jimbo34 said:
I had this problem. Try deleting all android drivers and MTP drivers from your PC using USBDeview (google it). Also try connecting to a different PC to see if the phone can connect at all. Finally, you may need to unlock the lock screen before attaching. After that it connects no problems!
Click to expand...
Click to collapse
USBDeview did the trick. Thanks a lot.
I have a 6P running on android 8.1 SuperXE rom. And when i tried to run Substratum and it asked me to download the Andromeda app to make it work so I did. Then i went on my Desktop downloaded the script for that followed all the instructions. Now after running the script a couple times my phone no longer works with adb. It is not a computer problem because I have tried to plug it in on multiple computers that have the right drivers installed and none of them work. It seems to be a problem with my phone.
I have tried factory resetting my phone uninstalling and reinstalling drivers. Nothing seems to work.
Has anyone ever run into a similar situation?
Also the error that shows up is USB device not recognized, "the last USB device you connected to this computer malfunctioned and Windows does not recognize it." It says this on both my windows computers, and my Linux laptop. So I know it has nothing to do with the phone cord or the computer.
Snowlandghost said:
I have a 6P running on android 8.1 SuperXE rom. And when i tried to run Substratum and it asked me to download the Andromeda app to make it computer.
Click to expand...
Click to collapse
It's probably the chord try another one. And if you root your phone with magisk you won't need Andromeda and Android pay still works. I'm on SuperXe also and don't have any issues. It's pure stock with some add-ons and customization.
Check with another cable or clean flash a stock rom via fastboot to see if the issue still persists, mm,n or o, it doesn't matter.
Edit: first go to Dev options and reenable USB debbuging and set USB configuration to mtp, may a phone reboot is required.
Edit: to reset the USB debugging authorization is worth a try too.
Exodusche said:
It's probably the chord try another one. And if you root your phone with magisk you won't need Andromeda and Android pay still works. I'm on SuperXe also and don't have any issues. It's pure stock with some add-ons and customization.
Click to expand...
Click to collapse
The first time I installed 8.1 it said it required Andromeda to run, but after I wiped my phone and re installed 8.1 it worked without it. Which was weird.
coremania said:
Check with another cable or clean flash a stock rom via fastboot to see if the issue still persists, mm,n or o, it doesn't matter.
Edit: first go to Dev options and reenable USB debbuging and set USB configuration to mtp, may a phone reboot is required.
Edit: to reset the USB debugging authorization is worth a try too.
Click to expand...
Click to collapse
I went out and got a new cord and now it is working thanks for the advice. It's weird though because nothing was wrong with the cord before this incident.
But thanks for the advice it was the cord I have a new one and no problems thus far.
Not to hijack this thread but I am having a similar issue. My nexus 6p and an old Nexus 6 will not connect to any computer. I have used different cables and still no dice. I have a Nexus 9 that connects fine. Both Nexus 6 and 6p charge on the cables but will not connect to computer. Any thoughts or suggestions. Again have tried different usb ports in same computer 3 different computers and multiple cables.
McAwesome said:
Not to hijack this thread but I am having a similar issue. My nexus 6p and an old Nexus 6 will not connect to any computer. I have used different cables and still no dice. I have a Nexus 9 that connects fine. Both Nexus 6 and 6p charge on the cables but will not connect to computer. Any thoughts or suggestions. Again have tried different usb ports in same computer 3 different computers and multiple cables.
Click to expand...
Click to collapse
???
May start from scratch with the drivers, download usbdeview (simple Google search) and get rid of all nexus and or android installed drivers. Reset USB debugging and authorization on the phones, set to mtp, do a reboot and do a fresh connect.
???
coremania said:
???
May start from scratch with the drivers, download usbdeview (simple Google search) and get rid of all nexus and or android installed drivers. Reset USB debugging and authorization on the phones, set to mtp, do a reboot and do a fresh connect.
???
Click to expand...
Click to collapse
Neither my Nexus 6p nor the 6 show up in usbdeview. Only the Nexus 9. Tried revoking. Have done factory reset set to mtp turned debugging off then on restarted phone different cables still doesn't show up in usbdeview.
Also the point of all this was to try to get this to work with my Mavic Pro drone. Which also does not recognize my 6p and thinking about this now my car also does not auto launch Android auto like it used to and in fact does not work at all. Phone charges from usb but does not seem to communicate.
Faulty phone maybe?
Is there a way to get off Oreo without having usb access? Not currently rooted and the apk's I have tried seem not to work.
McAwesome said:
Neither my Nexus 6p nor the 6 show up in usbdeview. Only the Nexus 9. Tried revoking. Have done factory reset set to mtp turned debugging off then on restarted phone different cables still doesn't show up in usbdeview.
Also the point of all this was to try to get this to work with my Mavic Pro drone. Which also does not recognize my 6p and thinking about this now my car also does not auto launch Android auto like it used to and in fact does not work at all. Phone charges from usb but does not seem to communicate.
Faulty phone maybe?
Is there a way to get off Oreo without having usb access? Not currently rooted and the apk's I have tried seem not to work.
Click to expand...
Click to collapse
It's strange that your n6 and n6p both don't communicate.
If you got TWRP installed you can root and flash what ever you want with flashfire. Or with TWRP itself. But never ever flash bootloader and radio with flashfire, it isn't necessary all the time anyway.
Or is your n6p completely stock ???
Uhh, I do miss my Nexus 6
A little history. I have rooted several other brands of tablets, so I am not new at this. Even thogh I am not a programmer by any stretch of the word. My Pixel C drivers work fine in normal mode, I can see the storage as a drive, no problem. I can transfer files back and forth. But, when I boot it into fastboot mode, it will not see it. It is listed as an unknown device in the device manager of Windows 10. I have tried to install the drivers, but they say not found. And this is the driver from the Android website. I'm at my wit's end. I'm not a newbie at windows, either. But, I need suggestions to get this to work. BTW this is the latest version of Windows 10 1903. And I have tried every solution I have found on google and on this website. TIA
Ok, fixed that by selecting a driver from a list of drivers so now I have ADB drivers. I have another issue which I will do some research on if not.....I'LL BE BACK.
What is your goal?
Do you want to use adb or fastboot?
Is the bootloader unlocked, have you enabled usb debugging in the developers menu (hidden) etc
Ok, as I said before, I figured it out. And yes, the bootloader was unlocked and yes USB debugging was enabled. I got everything
working and I am now running Android 9. Thanks for the reply, though.
Toolcrazy said:
Ok, as I said before, I figured it out. And yes, the bootloader was unlocked and yes USB debugging was enabled. I got everything
working and I am now running Android 9. Thanks for the reply, though.
Click to expand...
Click to collapse
Missed that! (you mentioned another issue)
Well done etc