Issues accessing usb diagnostic mode in Lollipop/cm12/pa - ONE Q&A, Help & Troubleshooting

Ok, after searching quite a bit, there doesn't seem to be any way of configuring usb diagnostic mode (sys.usb.config diag,adb) in CM12/PA 5.0.2. I've tried several times, and the closest I get is adb working and the diag port either constantly turns on and off, or doesn't read at all. I'm thinking it might be due to the fact that I can't seem to fully shut off mtp in storage. It only turns off (meaning the screen to switch doesn't open) after I issue the diag,adb command. I'm not sure, but I'm leaning towards this being some sort of new setting for Lollipop, which, if so, I guess I can try writing a script that might allow diag access. But, if anyone has any insight into this, please let me know. Thanks for reading.
-Mike

Shameless bump is shameless. For shame...

Hello, did you find something out?

I'm looking for a solution too. I think we are screwed until there is an OS update that fixes it

*delete*

hi guys...
any news from diag mode for CM12..?

Related

USB Connectivity Issue nuemassstorage Issue

Hi all, I have been running into a little bit of a problem and I wondered if somebody might have an idea or could point me in the right direction. I'm usually fairly adept at using google search and searching XDA and other forums and finding what I need but I have run into an issue I can't seem to find much info for.
Using the PPC Kitchen interface I assembled a rom for my sisters Titan. I have done this many times on my own Apache with great success. I went through added the things I thought she needed and everything went off with out a hitch. I used the 6.5 base and built on that. Everything works great. Except...
There were some other things on my phone that she has asked me to put on her phone. So no big deal I can just make up something new for her and flash her phone again. The problem is with connecting via USB. Both windows XP pro and Vista Ultimate say "the usb device has malfunctioned" or "the usb device is not recognized" No matter what settings I try on the nuemassstorage popup it does not seem to want to connect. Always the same error. I'm not sure how to get past this step though because I cannot seem to connect.
Any diagnostic ideas or info would be greatly appreciated. I can post whatever other info may be needed as well that would help.
Thanks

Bad ROM - various settings not responding and no PC connection

I just traded my X1 for an x7510, but find many of the settings not reacting at all. It's apparently running a version of 6.5
USB to PC does nothing when clicked, along with various other settings such as Device Information and Format Microdrive.
I can't connect to my PC, so I can't even begin to sync or think about updating the ROM to something that might work again.
Does anyone have any useful tips how I could get this thing working again?
Go into bootloader, its camera button and reset. And it will work. Thats the whole points of a hard-spl...Make sure you have the correct drivers in windows.
...
Well, that's such an obvious solution I rightfully feel like a n00b now.
Thanks.

Autostarts freezes even with USB Debugging Enabled

I am trying to use autostarts, which is an application that disables things from running automatically. I have seen people say that the app freezes when trying to disable something, and to enable USB debugging. I have it enabled and it still freezes when I try to disable something. Anyone else have this issue or know a way to get it to work? Thx
I had the same issue a couple days ago. I have a Samsung Epic but hopefully this will help you to.
I had the same problem when I didn't have USB Debugging checked in the settings menu. So I read the forums and found out that is what I had wrong but that didnt work either.
So I got it to work by making sure USB Debugging and Stay Awake was on. Rebooted the Device and had it on the charger while I did it and Autostarts started to work like normal.
Hopefully this was somewhat helpful and it works for you

How to Enable USB Debugging through ADB?

Right then. First things first, I apologize if I don't use the proper lingo associated with everything; I'm as super nooby as can be.
So, here's my problem: My rooted, Samsung Galaxy S3 has had it's screen shattered and its digitizer broken. The screen is completely black and the touchscreen does not respond. It didn't have a password (it was just swipe to open), which I suppose makes things easier, though. The phone itself still turns on, and I receive notifications and all that, but I am completely unable to do anything about. I understand that I am able to view and operate an Android phone through my computer, so I was hoping that'd work. Well, as the title of this topic hinted at, I didn't USB debugging enabled on my phone, which pretty much every program I found requires. So, I searched around, and learned that ADB can activate USB debugging through a usb cable and some tech magic. Unfortunately, I am not a tech magician and the articles I found were hieroglyphics. I spent some time reading, researching, reading researching, but it still doesn't make sense to me. I have ADB installed, but I don't know how to use it at all. I can launch "adb.exe" in administer mode but nothing occurs. I'm wondering if anyone would be able (or want to) explain to me, preferably step-by-step on how to enable USB debugging be it through ADB or some other, miraculous technique.
For anyone interested, these were the articles I looked at:
http://forum.xda-developers.com/showthread.php?t=1725858&page=2
http://android.stackexchange.com/qu...ndroid-if-forgotten-pattern-for-screen-unlock
http://android.stackexchange.com/questions/120394/can-i-enable-usb-debugging-using-adb
http://android.stackexchange.com/qu...bug-mode-was-disabled-how-can-i-re-enable-adb
http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
http://developer.android.com/tools/help/adb.html
http://forum.xda-developers.com/showthread.php?t=2786395
Hey dude, what you are talking that can enable USB Debugging from ADB is possible only on custom ROMs. But on stock ROM this is not possible.

Can usb debugging be enabled via adb/fastboot?

A friend has a stock S7 with a broken screen and USB debugging disabled.
I have read posts here about this situation and it looks like the prognosis is bleak, but it has been more than a year since the last one I found, and things do change with time as more is learned, especially on popular phones like the Galaxy line, so it seemed like a good idea to ask again. His wife has baby pictures on it that are worth a good bit to them. Why they weren't backed up to the cloud is anyone's guess - I get that some folks dislike sharing private lives with Google, but there are plenty of Boxcryptor type apps one can use - but the point is moot. They have their privacy and no baby pictures. It is what it is.
A quick Google search finds lots of proprietary software that claims that it doesn't need USB debugging to be enabled or that it can enable it, but the sparse details provided about this superhuman ability makes this seem unlikely.
Someone mentioned a way to sideload a custom kernel in order to somehow enable USB debugging via ADB. Is this possible? Can USB debugging be enabled from stock recovery on the S7, or any other route?
There are all sorts of Octopus / Miracle Box type gadgets and software packages that claim to make various phones dance and sing, but I can't find one that will recover files from the S7. It might be worth buying such a package, if it existed.
Some posts, articles and videos suggest using an OTG to connect a mouse or keyboard and navigate the broken screen, either from memory or by taking screenshots and retrieving them from phone storage. We have not tried this yet, and any tips specific to the S7 would be really appreciated.
Someone posted an application here, that is apparently intended to help with this situation, but mirroring a phone screen requires USB debugging to be enabled.
https://forum.xda-developers.com/showthread.php?t=2786395
Thanks to anyone who might be able to help, and I apologize for adding a redundant question. I am just hoping that there is something new in the Galaxy world that might have made this situation salvageable.
SmilingPerson said:
A friend has a stock S7 with a broken screen and USB debugging disabled.
I have read posts here about this situation and it looks like the prognosis is bleak, but it has been more than a year since the last one I found, and things do change with time as more is learned, especially on popular phones like the Galaxy line, so it seemed like a good idea to ask again. His wife has baby pictures on it that are worth a good bit to them. Why they weren't backed up to the cloud is anyone's guess - I get that some folks dislike sharing private lives with Google, but there are plenty of Boxcryptor type apps one can use - but the point is moot. They have their privacy and no baby pictures. It is what it is.
A quick Google search finds lots of proprietary software that claims that it doesn't need USB debugging to be enabled or that it can enable it, but the sparse details provided about this superhuman ability makes this seem unlikely.
Someone mentioned a way to sideload a custom kernel in order to somehow enable USB debugging via ADB. Is this possible? Can USB debugging be enabled from stock recovery on the S7, or any other route?
There are all sorts of Octopus / Miracle Box type gadgets and software packages that claim to make various phones dance and sing, but I can't find one that will recover files from the S7. It might be worth buying such a package, if it existed.
Some posts, articles and videos suggest using an OTG to connect a mouse or keyboard and navigate the broken screen, either from memory or by taking screenshots and retrieving them from phone storage. We have not tried this yet, and any tips specific to the S7 would be really appreciated.
Someone posted an application here, that is apparently intended to help with this situation, but mirroring a phone screen requires USB debugging to be enabled.
https://forum.xda-developers.com/showthread.php?t=2786395
Thanks to anyone who might be able to help, and I apologize for adding a redundant question. I am just hoping that there is something new in the Galaxy world that might have made this situation salvageable.
Click to expand...
Click to collapse
Try the solution in the link you've posted, i'm sure you no longer need debugging enabled.
Also the real issue is you need to unlock the phone, so if the screen is just black?? You can usualy guess where the patterns or numbers appear etc, easy if you have another s7 next to it.
Also other options here
cooltt said:
Try the solution in the link you've posted, i'm sure you no longer need debugging enabled.
Also the real issue is you need to unlock the phone, so if the screen is just black?? You can usualy guess where the patterns or numbers appear etc, easy if you have another s7 next to it.
"]here [/URL]
Click to expand...
Click to collapse
Thank you! This is very helpful.
I think debugging must be enabled for that solution, but I hadn't read far enough or close enough to find Msmtx's solution for enabling it from ADB.
https://forum.xda-developers.com/showpost.php?p=66731042&postcount=260
My blind spot now rectified, I am going to give this a try. I know nothing about stock recoveries - is the one in the S7 going to allow me to do this, or will I have to install or boot TWRP or Safestrap?
Thanks again mate, it will be great to get those pics back. I just hope they have learned from this the great value of backups...
Sent from my unknown using Tapatalk
Hi @SmilingPerson - Did you get this resolved? I'm facing the same issues, and on top of all the OTG ideas, the phone I need to access has a swipe lock, so I'm pretty sure connecting a mouse without seeing anything is useless. Would appreciate any tips.
I wish I could tell you something, but nothing worked, sadly, and I used the old phone for parts.
Good luck though, hope you fare better than I.

Categories

Resources