TL;DR Smashed phone, need to find a ROM with ADB enabled to use it
Long story short, I smashed my phone last Friday. The LCD screen works and the phone appears to be fully functional except for the digitiser. I had ADB disabled as I frequently plug my phone into computers at university and elsewhere and I don't want to run the risk of ADB commands being run maliciously. Since the Nexus 4 can't do USB OTG without a splitter cable (and, I believe, some configuration) I can't just plug in a mouse to control the phone. Annoyingly, this happened while moving house and I don't have internet at home until tomorrow; I was planning on using USB or WiFi tethering to get my PC online.
I found this page with a suggestion on what I might be able to do. Alternatively, my other plan is to connect an Ouya controller by bluetooth and use the touch pad on that to control the phone. Either way, the plan hinges on using ADB to control the phone to begin with to either configure an app or enable bluetooth.
I've noticed a lot of ROMs (since 4.3.1?) have ADB disabled until the user enables it. Also, whether or not ADB is enabled to begin with isn't something a developer is likely to list in their first post. Does anyone know any ROMs that have ADB enabled on first boot? Any other suggestions on what to do would also be great.
I've been reading various threads and tech posts for hours and feel like I'm going in circles and getting absolutely nowhere, so I'm really hopeful someone can help me out.
I broke the screen and digitizer on my AT&T SGH-I337 Galaxy S4 with stock Android 4.2.2 and ROM, though it is rooted. I was trying to control it via the computer with 'Ultimate Touchscreen Control for Android' or Screencast, but they require ADB which I'm pretty sure is not enabled. I did enable USB debugging before the screen broke, though I can't say with 100% certainty that I didn't later disable it, so I'm not entirely sure what the status of that is. I've been reading about sideloading a kernel with ADB enabled through recovery, or using CWM with Odin to enable it, but I have been absolutely unable to figure out how to do it with a broken screen. It doesn't help that it's been 3.5 years since I really messed with stuff like CWM and custom ROMs, and I've never used Odin, and my knowledge on this stuff is not great. Any help would be greatly appreciated.
I think you're pretty much sol. You say you're on 4.2.2, do you know what bootloader you're on. Mdb, mdl or mf3. If you're on mf3 you won't be able to flash a kennel. Do you have a custom recovery, and if so, which one?
When booted into recovery and adb installed on your pc in a Windows command window type
adb devices
If you're devices serial number shows up you have adb debugging enabled. If it just shows waiting for device, you don't.
Your best bet is to get the screen/digitizer replaced.
Sent from my Nexus 5 using XDA Free mobile app
Not sure what bootloader, but I got the device only a month or two after the S4 came out and immediately rooted it with Motochopper and it hasn't had any updates since, so it has to be an earlier one, probably the first.
After several attempts, 'adb devices' gave me:
"List of devices attached
da916528 unauthorized"
The first several times it would just say "List of devices attached" with nothing following.
'adb shell' resulted in "error: device unauthorized. Please check the confirmation dialog on your device."
Shortly after it does list the phone, the phone shows up in Windows, so I'm thinking it's not going into recovery. My timing must be off because I can't see the screen to know when to release the buttons.
vertigo_2_20 said:
Not sure what bootloader, but I got the device only a month or two after the S4 came out and immediately rooted it with Motochopper and it hasn't had any updates since, so it has to be an earlier one, probably the first.
After several attempts, 'adb devices' gave me:
"List of devices attached
da916528 unauthorized"
The first several times it would just say "List of devices attached" with nothing following.
'adb shell' resulted in "error: device unauthorized. Please check the confirmation dialog on your device."
Shortly after it does list the phone, the phone shows up in Windows, so I'm thinking it's not going into recovery. My timing must be off because I can't see the screen to know when to release the buttons.
Click to expand...
Click to collapse
You're close but unfortunately no cigar. You have usb debugging enabled but it's waiting for you to authorize the device by clicking accept on the touch screen. Which you obviously can't do. If you used motochopper you are on mdb or mdl bootloader which means you could flash a kernel but you'd have to do it in a custom recovery and use the touch screen. I don't have an i337 so I'm not going to be much more help. Sorry.
Sent from my Nexus 9 using XDA Free mobile app
Kinda figured it was something like that. Thanks anyways, at least I know exactly where I stand now. I'm going to try using an MHL and OTG adapter to see if I can click it that way. In the meantime, hopefully somebody with the same phone as me will come along and be able to provide further guidance.
So I was finally able to gain remote access with some crazy wiring and a lot of patience. I'm putting this here so others in my situation might have an easier time at doing it.
First I installed TeamViewer QuickSupport (TVQS) via the Play Store online, then connected a PS/2 mouse to the phone through a OTC cable and a USB to PS/2 adapter (only USB mouse I have is wireless, but good to know you can use such an adapter for this). I blindly swiped the screen to unlock the phone, then connected it to my TV with an MHL adapter and the 5 to 11 pin Samsung-specific adapter. I long-pressed the menu button to activate voice search and said "launch TeamViewer QuickSupport," then when the app opened it showed me the ID to connect to the phone which I entered into my desktop TeamViewer application. I then had to switch back to the mouse to do some more blind clicking to authorize the connection, then again to authorize the remote control, which took several frustrating minutes of switching back and forth between the mouse and the TV. One mistake I made was not installing the remote addon at first, so after I first authorized the connection, I didn't have that option, so I had to install it again through the Play Store online then close and relaunch TeamViewer on the phone and reauthorize the connection before I could start a remote session. Once I was FINALLY in I had full control and was able to get the Ultimate Touchscreen (UTCA) program authorized (which in retrospect would have required the same thing only it would have been significantly easier, since I would have only had to do one blind click) and Mobizen (which I'm currently using to control it as it's the best and fastest of the three, and oddly it's faster through the web interface than the desktop program).
In the end, what would have made this significantly easier (in fact, very easy), would have been to use a combination OTG/MHL adapter that would allow using the mouse and TV at the same time, or possibly a micro-USB OTG Y-cable so I could plug one connector into the phone and one into a power supply, then plugged the MHL Samsung adapter into that so it could get power that way, allowing me to plug the mouse in to it instead of a USB cable for power. Not sure if that would actually work, but it seems like it would. Hopefully somebody finds this info helpful. From now on, I'll be installing and authorizing TVQS, Mobizen, and UTCA on my phones when I get them.
I have the same problem. I cannot access ADB in anyway, even in in Clockworkmod recovery. USB Debugging is off. I am on the original firmware that came with the device, (Pre Knox) and the device is rooted.
My lock screen is just the simple lock, with no password required, but I have an app installed that switches the USB mode to Mass Storage for the external SD only so I cannot see internal storage.
MHL does work, but the touchscreen is not working, so all I can see is the lock screen.
When in recovery, ADB Devices shows the device as unauthorized. If i go to option # 3, (which apparently is Factory Reset) the status changes to "Sideload." But I still cannot do anything.
If no one has any suggestions. I think i'm going to have to purchase one of the Samsung Smart Docks.
I can't post links or pictures until I get 10 posts, but this works;
goo.gl/PR7TCK
Other than getting the dock, the only other way to do it that I know of is how I described above, switching back and forth between video and mouse, which sucks because you're flying blind. It requires a lot of patience.
I have had a Moto G4 Plus since it came out and i got into a fight over the summer and the screen broke and NOTHING is displayed, BUT fingerprint sensor vibrates when i touch and i can control the volume so the device is working...just been sitting in a drawer...
I wanted to use Vysor or a similar app (suggestions?) to view my device on my laptop. Currently stuck with an S9+ and NO ROOT for anytime soon and im bored.
When i run adb devices, cmd comes back with the serial number UNAUTHORIZED. Apparently from what i read, because USB Debugging is ALWAYS ON ALL MY DEVICES, i need to **** off USB Debugging and flip it back on.
So does anyone know the DETAILED commands for Windows 10 to turn USB Debugging off and on or on and off, but im positive its on, just having the UNAUTHORIZED problem. Vysor sees the device and the serial but it says i have to turn on USB Debugging.
Any help would be GREATLY appreciated...
Thanks in advance!
AFAIK there isn't a way on an unrooted, bootloader unlocked device.
Hey guys,
I recently bought this phone second hand and started having issues. First of all I was getting the infamous 'moisture in charger port' problem which I managed to solve by cleaning the port a bit, spraying a bit of WD40 in it and putting the charger cable in with the smooth side pointing upwards (still displays error with the joined side pointing upwards).
Ok so now I can at least use the phone right? Well now I want to bootloader unlock it to root it, the problem is now whenever I connect to my laptop (Windows 10 x64) it just charges the phone and I get a popup saying 'slowly charging device, unplug to save power' but no option to change to MTP mode on drop down menu.
Anyone know how to sort this problematic device out?
Things I have tried:
Two different USB C cables, both operate fine in terms of charging multiple devices but both only work with the smooth side of the connector facing upwards
Reinstalling LG Drivers (4.2.0) from their website, cleaned installation RevoUninstaller.
Restarting the phone (initially I had tried the force stop fix on the LG app).
Disabling the moisture detector through the *#546368#*870# command (didn't work at all).
Disabling USB selective power settings through Windows power settings.
Connecting with and without USB Debugging enabled.
The fix mentioned here, exactly as its written for issues involving device descriptor failed messages, followed by a PC restart.
Tried sfc /scannow
Uninstalled drivers through device manager, restart PC and let Windows install.
Forcefully tried to use LG Drivers through manually setting it in 'Have Disk', tried all options available.
Edit:
Just found the option for forcing MTP mode on USB connection through developer options, doesn't change anything, still device descriptor failed code 43.
Edit 2:
I just noticed my cables are not certified for USB 3.0, can anyone please confirm that 3.0 is required to connect to a laptop/PC? I have ordered another cable anyway to try it but clarification before hand would be nice.
I have a no-name Allwinner T3 head unit. I need to enable some Accessibility options for an app, but there is no Accessibility Settings menu on this head unit. From reading the forum, I see how to set these options using ADB. With help from various posts, I have enabled debugging and ADB over WiFi. (USB on this unit only accepts devices and can't connect to a PC)
I am able to connect ADB over WiFi to head unit from PC, and also from ADB Shell apps on my phone and even locally on the head unit. However, when I connect, no authorization box pops up, and all ADB shell commands return "unauthorized". The strange thing is that if I do a reboot after connecting ADB, the authorization box does appear briefly during the reboot, but pressing OK in the box doesn't seem to do anything.
Does anyone have any idea how I can get around this without root on the head unit?