Hey fellas I am and always been stock Rom I have rooted and changed a few things to my benefit then I noticed my build number was change. Can anyone tell me what effects this can have on my device. I been trying to use adb installer for mtk Droid tool but my device isn't recognized even though it is thru the adb server via adb devices.
Nothing changes enable dev options again and USB debugging also put phone in mtp mode
Related
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Hoping it's okay to bump my thread after a month.
Does anyone know what to do in this situation?
Thanks!
jorge_quintanilha said:
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Click to expand...
Click to collapse
Have you tried Motorola's drivers? It installs separate drivers for adb, fastboot, mtp. https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/97326/p/30,6720,9050
I updated to cm 12 by OTA a few days ago. Today I want to copy some files between my Oneplus and computer, only to find that I can't turn on MTP. I went to settings -> storage, top-left menu, and the only item in the menu is 'USB computer connection', but press it only seems to refresh the storage panel (all values of space gets re-calculated), but nothing else. Any suggestions?
mrmathematica said:
I updated to cm 12 by OTA a few days ago. Today I want to copy some files between my Oneplus and computer, only to find that I can't turn on MTP. I went to settings -> storage, top-left menu, and the only item in the menu is 'USB computer connection', but press it only seems to refresh the storage panel (all values of space gets re-calculated), but nothing else. Any suggestions?
Click to expand...
Click to collapse
similar to you, but my problem is i can't get adb device to recognize my OPO, also on CM12S
I know what you mean, as I seen it as well
But if you get out, make sure adb debugging is off, and go back to USB computer connection menu, you should see 3 items
MTP
PTP
Charge only
My issue is
MTP with no adb debugging will let me access full /sdcard on windows, but adb device command does not see OPO thru USB
PTP with no adb debugging will let me access only pictures on OPO, and adb device command does not see OPO thru USB
Charge only will block out adb debugging completely
MTP or PTP with adb debugging will not present OPO storage to windows, and at the same time adb device command does not see OPO thru USB
This same computer that have problem with my OPO CM12S was working fine with OPO CM11
Back in CM11, the only way for adb device to see my phone via USB is to NOT select MTP AND PTP
With CM12S, I must select one of the 3 options in USB computer connection menu: MTP, PTP, Charge only
In another word, CM11 the options are not required. In CM12S, one option must be active/selected
To make it more "interesting", fastboot work just fine. Only adb device doesn't work
I installed latest android SDK google USB driver already, both ADB interface and ADB composite interface
EDIT: and Koush's universal adb driver as well
I am really at my wits end now.
For those of you who has CM12S installed (stock kernel if matter), do you have adb device working (ie can see your CM12S OPO thru usb)? If yes, can you let me know which usb driver you installed?
Thanks!
Thanks for the reply. After turn ADB on and off, it seems I get MTP working too. Not sure about your case. Also I should mention previously on CM 11S, usb connection works fine with my Oneplus.
mrmathematica said:
Thanks for the reply. After turn ADB on and off, it seems I get MTP working too. Not sure about your case. Also I should mention previously on CM 11S, usb connection works fine with my Oneplus.
Click to expand...
Click to collapse
I have been meaning to come back and update this thread...
I went on to CM12.1 nightly after I got fed up with COS12S
CM12.1 nightly is very stable, despite the nightly naming, but this specific issue (no adb on PC) still exist
Eventually, I switched to Sultanxda's Omni ROM with his tuned CAF kernel http://forum.xda-developers.com/showpost.php?p=61801883&postcount=850
and I can now run adb on my PC, and connect to OPO
and I did not change anything on my PC
My opinion is that CM 12 made some changes that prevent adb from PC to connect to the phone.
Still, I am surprise that there are not a lot of people who report this issue on CM 12.x based ROM, so I have to make assumption that something is wrong on my end as well
Still, I am now sticking with this custom Omni build
Please be aware that Sultanxda is no longer maintaining is custom Omni build. You use it at whatever state it's on now
Compare to CM12.x based ROM, this custom Omni ROM is pretty bare.
Still, it suits my need
For those of you who is still having problem with adb on PC connecting to OPO, you should try a non CM based custom ROM and see how that might work for you
Hope this help
mrmathematica said:
I updated to cm 12 by OTA a few days ago. Today I want to copy some files between my Oneplus and computer, only to find that I can't turn on MTP. I went to settings -> storage, top-left menu, and the only item in the menu is 'USB computer connection', but press it only seems to refresh the storage panel (all values of space gets re-calculated), but nothing else. Any suggestions?
Click to expand...
Click to collapse
MTP only works when you enable ADB Debugging for 5.X ROMs.
Qrze said:
MTP only works when you enable ADB Debugging for 5.X ROMs.
Click to expand...
Click to collapse
Thats not true. I have adb debugging turned off and yet I can access my phone from my mac using MTP. Using BlissPop 5.1 on my bacon,1+
Do You Like To Flash Custom Stuffs On Your Android phone? Or Are You A Developer? But You Can't Able To Do It Because You're Facing Some Problems with Your Adb & fastboot. All Of This Problems Are Only Because Of One Thing And That is Drivers.
And If you agree With Anyone Of This Situations Then You're At The Right Place Because Today I Am Going To Tell You That How You Can Install The Adb Drivers For Your Specific Android Phone On Your Pc.
Adb drivers are necessary if you want to flash a android device through Fastboot mode or if you're a android developer. Usually Our PC installs the adb drivers automatically for the specific android device but sometimes it can't so you have to install it manually.
This will also help you to solve adb errors like Device is offline, USB debugging Authorize pop-up not showing in android And etc adb errors. Make sure that your USB debugging option in developer mode is enabled on your Android device Because without this you can't use adb.
Steps:-
*So first go http://adbdriver.com to and download the "adb driver installer (Universal)". Then extract it.
*Now connect your Android phone to your PC using USB cable. Then Open the application.
*Now you will see something like Adb interface drive and with a red Cross at left side. Make sure to refresh if driver option is not shown.
*Now Just Click On install To install your device adb drivers. Then it will Install the adb drivers for your specific android phone in just under 2 minutes.
*Then Allow The USB debugging On your Android phone. Then the adb drivers will get successfully installed.
*If still adb can't recognize your device then try to connect your phone in PTP Mode instead of MTP or Charging only modes.
*If still it doesn't work for you then Revoke USB debugging Authorizations in developer mode. So that's how you can install the adb drivers for your Android Phone.
Video Tutorial - https://goo.gl/a6QgtH
Greetings.
I have a Samsung Galaxy Note 4 with a completely broken screen (no display, no touch response).
Android version is 4.2.2.
The phone is working, as pressing the power button lights up the bottom bar.
The phone is rooted, however, USB debugging is disabled. The phone is also pattern locked.
I am aiming to gain remote access to the phone through my PC, ideally mirroring the screen so I can manually backup everything from my phone. In the worst case, backup through ADB is also acceptable.
Initially, I attempted to mirror the screen using:
https://forum.xda-developers.com/showthread.php?t=2786395
However, it requires ADB, which in turn requires USB debugging to be enabled.
To enable USB debugging, I attempted to modify the build.prop through ADB shell in recovery mode:
https://forum.xda-developers.com/showthread.php?t=2335799
However, it is done so using custom recovery (TWRP) which I assume cannot be done in stock recovery (not confirmed, please respond if untrue).
I attempted to edit the build.prop manually:
https://forum.xda-developers.com/sprint-g4/themes-apps/tool-edit-build-prop-pc-t3312517
But It requires USB debugging to be enabled as well, and I assume it to be true for most such tools.
I also attempted to install a custom recovery (TWRP):
https://www.xda-developers.com/how-to-install-twrp/
However, out of the 3 installation methods listed, 2 require USB debugging and 1 requires application installation on the phone.
Using a USB OTG mouse to enable USB debugging would be difficult, since display is broken.
Since 4.2+ also shows a prompt to allow access to USB debugging to PCs, I assume I could use this:
https://forum.xda-developers.com/galaxy-s2/help/bypass-secure-usb-debugging-prompt-t2965462
However, I would need ADB first, which also comes back to USB debugging.
I would prefer not repairing the phone or getting a new screen, the phone is old, i'm trying to change phones.
Data in the phone must be preserved, as much as possible. I am willing to compromise, somewhat.
ADB seems powerful enough that I could achieve my goals if only I could access my phone through it.
Is it possible to enable USB debugging remotely through some other method to allow me to use ADB?
Is it possible to flash a custom rom with an edited build.prop without screen input and while preserving phone data?
Please suggest options.
I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
In Android Studio SDK Tools I have installed Google USB Driver v12.
My ONePlus One has Carbonfibers ROM, has developer options turned on and Android Debugging turned on.
When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
Device Manager / Portable or Other devices does not have the phone beneathn it.
When I run adb devices in cmd there are no devices attached.
I cannot find a OnePlus One adb usb driver.
Any suggestions how to diagnose this problem and get my OnePlus One recognised by adb?
Unable to connect to usb
I installed Carbon-cr-5.1-moo-release-bacon-20180202-1444.
I am unable to get usb connection working and having tried many different things...
-I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
-In Android Studio SDK Tools I have installed Google USB Driver v12.
-I have developer options turned on and Android Debugging turned on.
-When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
- when I go into developer options and hit 'select usb configuration' my selection of mtp or whatever is always ignored and charging selectiomn remains
-Device Manager / Portable or Other devices does not have the phone beneathn it.
-When I run adb devices in cmd there are no devices attached.
-I cannot find a OnePlus One adb usb driver. I thought I found one but I have no way to verify and after installing it made no difference
I want to update to the latest rom in case this may be the cause, but after I download it to the phone and click flash
I just get the oneplus icon forever and the recover app twrp does not come up. It used to be there but then after I installed
the first rom after a couple of uses it disappeared for some reason or at least will not boot to it.
When I installed that first custom rom I folowed instructions for rooting and on completion it says to open up the installed
su app but when you open it it says there is a more up to date version but when you try to install that it fails.
Now all the apps that will not run if your app is rooted say it is rooted and all the apps that will not run unless it is rooted
say it is not rooted.
I think I need connection via usb in order to reinstall the twrp recovery app in order to install an up to date rom, hoping this may help
me solve the usb issue, but I cannot get the usb connection working as described above,
any hehlop would be appreciated.
Same Situation
hardya said:
I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
In Android Studio SDK Tools I have installed Google USB Driver v12.
My ONePlus One has Carbonfibers ROM, has developer options turned on and Android Debugging turned on.
When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
Device Manager / Portable or Other devices does not have the phone beneathn it.
When I run adb devices in cmd there are no devices attached.
I cannot find a OnePlus One adb usb driver.
Any suggestions how to diagnose this problem and get my OnePlus One recognised by adb?
Click to expand...
Click to collapse
but my phone connects in edl mode just for 10 seconds and then automatic