Hey Guys,
I have just installed a custom ROM and can't connect via ADB Shell. Under developer options, there is no option to revoke USB debugging. If I search for it, it finds it but I can't get to it.
Any ideas?
Cheers
jasonst165 said:
Hey Guys,
I have just installed a custom ROM and can't connect via ADB Shell. Under developer options, there is no option to revoke USB debugging. If I search for it, it finds it but I can't get to it.
Any ideas?
Cheers
Click to expand...
Click to collapse
There is here, just under USB debugging main switch. And I can connect just fine via adb usual operations and even adb shell.
What is it that you're trying to achieve exactly? What ROM are you running?
a hammerhead wrote this.
I have come across it on a couple of different ROMs from 5.1 to 6.0. I was the latest Veneno ROM but seeing as I couldn't revoke authorisation, I wiped it and installed the latest Xtrasmooth Rom.
I was just wondering if there was something in the build.prop that changed what was viewed under developer options.
Related
Hi,
I have a WellcoM A69 mobile phone I would like to connect to with Eclipse for debugging purposes. It is running Android 1.5 cupcake. I'm a n00b here so I can't post a link to the specs, but it's easy to find them on Google (you may need to use Google translate for Thai language translation as this phone is for the Thai market).
Even though I enable the Development USB Debugging option, Eclipse doesn't detect it. Is there something in the ROM created by WellcoM that would prevent USB debugging?
I saw this with a MID Android tablet I tried before as well. Can they disable the debugging option even though the menu option for this still exists? Or perhaps there is something else I have to do?
For lesser known devices, what can I do to get access like this? How can I find out how to reboot the device, perform recoveries, install custom ROMs, etc.?
Thanks,
gonzobrains
Hi, I am a beginner developer for Android, and was able to develop a sample app using eclipse and the Android Emulator. Now I am trying to deploy the app on my samsung galaxy skyrocket (unrooted). I have taken the following steps.
1. Enabled "unknown sources"
2. Enabled USB Debugging.
3. Downloaded kies which installed the required USB drivers.
4. Was able to confirm that my device driver is setup correctly by going to Window's device manager and not seeing any error for my device.
The Issue is here.
- I tried to run "adb devices" in command line, but it does not list my device.
- I also tried Device Chooser in Eclipse and still do not see my device.
Things I tried to do.
- I tried updating my Device Driver from device manager and still no success.
- I restarted my phone.
But still no success.
Is there any step that I am missing? Any help on this will be great, thank you.
amarmahtani said:
Hi, I am a beginner developer for Android, and was able to develop a sample app using eclipse and the Android Emulator. Now I am trying to deploy the app on my samsung galaxy skyrocket (unrooted). I have taken the following steps.
1. Enabled "unknown sources"
2. Enabled USB Debugging.
3. Downloaded kies which installed the required USB drivers.
4. Was able to confirm that my device driver is setup correctly by going to Window's device manager and not seeing any error for my device.
The Issue is here.
- I tried to run "adb devices" in command line, but it does not list my device.
- I also tried Device Chooser in Eclipse and still do not see my device.
Things I tried to do.
- I tried updating my Device Driver from device manager and still no success.
- I restarted my phone.
But still no success.
Is there any step that I am missing? Any help on this will be great, thank you.
Click to expand...
Click to collapse
perhaps it's your pc that doesn't see your phone.
I got the same problem when i wanted to root my phone.
It was because of the latest version of kies that didn't works for me.
Don't know why but many people as the same problem.
i found an older version that works well. the file version is Kies_2.0.3.11082_152_2
here's the link.
http://downloadcenter.samsung.com/conte.../Kies_2.0.3.11082_152_4.exe
I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.
aaa12585 said:
I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.
Click to expand...
Click to collapse
Is the device showing up under Device Manager (which would indicate that the driver is installed--see #2 here)? This is not a "root" issue. I've run rooted devices for over three years and have only had the problem in the early days with the Pandigital Novel. Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.
ritchea said:
Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.
Click to expand...
Click to collapse
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online
aaa12585 said:
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online
Click to expand...
Click to collapse
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Sent from my Nexus 7 using Tapatalk 4
Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go
ritchea said:
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Click to expand...
Click to collapse
I have tried that too, but I end up with the same outcome. Same drivers I would normally have installed and give me no recognition of the device for file transferring.
Fortunately, knowing how this goes down, as it has happened before with me and my S2, I'm not desperate enough to factory reset. As I would ultimately reach the same issue.
I've been interested in wireless file transferring, but I much more prefer not having to upload the file to something like dropbox or manually setup a server. I'm more into the press-and-go (similar to the plug-and-go method... haha, get it?... made a funny there cause it relates to a cord ordeal) routine.
I haven't actively searched that route yet because I'm in hopes that there is a fix for this problem. I'll get to it if there really is no other choice. So, if there is a program that will allow me that ease of access, I'm open to suggestions!
AkaGrey said:
Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go
Click to expand...
Click to collapse
Seeing this makes me question whether I'm confusing the purpose for each of these drivers or you haven't read what I wrote. However, our circumstances differ. I didn't root through conventional means of the toolkits, I just came across it through my search for driver issues. I have tried the method you are suggesting, as the toolkit driver installation steps take me through that step before I do anything else; but this doesn't work. I end up with the same outcome: Device is recognized and drivers are installed (if I allow windows to automatically search for them), but no PTP or MTP for any file transferring.
ok, silly question : Is it enabled on your android phone? under memory ->tap the 3 dots and you will see mtp/ptp try to uncheck and check.
Otherwise I don't really know anything u could do about it.
By using the NRT or toolkits to root, all of the pc's usb drivers were deleted and new/generic/universal ones installed to re-install custom recovery & achieve root. Go to Control Panel on the PC, do you see Portable Devices listing including the Nexus 5 ? Most likely, no - only Android Interface.
A simplistic approach that worked for me is to roll it back - if you are using PC running Windows OS, use System Restore to go back to a previous state to an earlier (earliest possible) time before - with the N5 disconnected. When the PC is restored, turn OFF USB debugging on the N5, connect via the OEM N5 cable - it should be recognized, then turn ON USB debugging if there are missing drivers - let Windows search & install.
At some point, N5 will be recognized as a Portable Device along wit Android Interface, and "Auto Play" would pop up, with full access to all the SD folders & files. Toggle MTP and PTP if necessary as it might install more drivers - you should be good to go.
Reboot the PC just to reconfirm that everything is back to normal, connect N5 and profit - enjoy.
If this work, please share & if it doesn't - please comment what didn't work.
The simplest and shortest way to connect google nexus5 with PC as MTP(Media device)
When I plugged it, there wasn't any yellow exclamation mark within Device Manager. So for me, the drivers were OK. But the device was not listed within my Eclipse DDMS. After a little bit of searching, it was just an option to change in the device settings. By default, the Nexus 5 USB computer connection is in MTP mode (Media Device).
What you have to do is:
Unplug the device from the computer
Go to Settings -> Storage.
In the ActionBar, click the option menu and choose "USB computer connection".
Then select Media device(MTP) or Camera(PTP) based on your requirement...
Plug the device and you should have a popup on the device allowing you to accept the computer's incoming connection..
I hope this will help!
Hello xda users!
I have bought a CAT s50 device and I am very used to feature that phone vibrates once when someone answers my call. Since it runs andorid 4.4.2 it does not support this feature by default. So I found app Vibrate Call (on Play store) (if someone knows better way around without rooting it would be cool)
So there is a main problem - when I try to access my phone via "adb devices" command it is not shown there (I enabled USB debugging and device can be seen in explorer). So I cannot run the shell to enable app. I tried it as well on Linux where no drivers are needed
Any solutions? Anyone faced the same problem?
pmDx22 said:
Hello xda users!
I have bought a CAT s50 device and I am very used to feature that phone vibrates once when someone answers my call. Since it runs andorid 4.4.2 it does not support this feature by default. So I found app Vibrate Call (on Play store) (if someone knows better way around without rooting it would be cool)
So there is a main problem - when I try to access my phone via "adb devices" command it is not shown there (I enabled USB debugging and device can be seen in explorer). So I cannot run the shell to enable app. I tried it as well on Linux where no drivers are needed
Any solutions? Anyone faced the same problem?
Click to expand...
Click to collapse
Try to unmount the storage / deactivate MTP when you are going to use ADB. Have you checked the devicer manager if your phone is listed?
Still no success. Looks like there is missing ANDROID (not USB) driver for s50 (under device manager). But it is strange that it did not work on Linux, but I am not sure that I tried PTP mode insted of MTP as you said.
pmDx22 said:
Still no success. Looks like there is missing ANDROID (not USB) driver for s50 (under device manager). But it is strange that it did not work on Linux, but I am not sure that I tried PTP mode insted of MTP as you said.
Click to expand...
Click to collapse
Try to disable the storage mount at all. Just adb connection.
LS.xD said:
Try to disable the storage mount at all. Just adb connection.
Click to expand...
Click to collapse
There is no right-click option to unmount it -> is there any other way to do it?
pmDx22 said:
There is no right-click option to unmount it -> is there any other way to do it?
Click to expand...
Click to collapse
Unmark all the checkboxes MPT/PTP/Mass storage (In the Android interface)
LS.xD said:
Unmark all the checkboxes MPT/PTP/Mass storage (In the Android interface)
Click to expand...
Click to collapse
There is the problem - I cannot uncheck, just switch between those 2. Any other ideas?
Thanks for answering!
LS.xD said:
Unmark all the checkboxes MPT/PTP/Mass storage (In the Android interface)
Click to expand...
Click to collapse
Any other ideas? Tried to contact developer from Bullit group, but still no answer.
I've been trying to root my OPO for two days now and I've continued to have this issue. After installing Android Studio + the SDK, as well as downloading the Google USB Driver, when I connect my phone to my computer it shows up as an MTP device under unknown devices. If I allow it to automatically download drivers, it becomes a portable device instead. But I need it as an ADB device. I've already started USB debugging on the phone, as well as switched between all the different USB options on the phone (charging, MPT, PTP, MIDI, etc.) and still no good
When I try to update the driver for the "MTP" device, the Google USB drivers don't show up, and if I try to browse manually, it comes up with the error message saying how "the folder you specified doesn't contain a compatible driver." What do I do?
Thanks!
tli said:
I've been trying to root my OPO for two days now and I've continued to have this issue. After installing Android Studio + the SDK, as well as downloading the Google USB Driver, when I connect my phone to my computer it shows up as an MTP device under unknown devices. If I allow it to automatically download drivers, it becomes a portable device instead. But I need it as an ADB device. I've already started USB debugging on the phone, as well as switched between all the different USB options on the phone (charging, MPT, PTP, MIDI, etc.) and still no good
When I try to update the driver for the "MTP" device, the Google USB drivers don't show up, and if I try to browse manually, it comes up with the error message saying how "the folder you specified doesn't contain a compatible driver." What do I do?
Thanks!
Click to expand...
Click to collapse
Just want root? No custom recovery or rom?
Then use kingoroot or kingroot app on phone and get root without pc
Make sure you've fast net connection.
Mr.Ak said:
Just want root? No custom recovery or rom?
Then use kingoroot or kingroot app on phone and get root without pc
Make sure you've fast net connection.
Click to expand...
Click to collapse
Don't exactly want to use them due to the risks / IMEI debacle.
I have exactly the same issue.
I managed to get root by flashing SuperSU (only on a system less basis)
This just got the rooting side sorted but I'd still want to be able to get ADB working again on the phone.
I tried with three different laptops and the issue is persistent. I am running Cyanogen 13.1 coated beautifully with a Boeffla kernel and a slimlined build.prop (have to boast because everyone can agree, the Oneplus One is a revolution on its own)
tli said:
Don't exactly want to use them due to the risks / IMEI debacle.
Click to expand...
Click to collapse
Trsut me,there are no risks involved.