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 managed to get into developer mode on my new NGP, there's no more "build number" as I've seen in several blog posts with the latest update you click on the Nook icon on the About page it takes you to Developer mode. I've been able to install a few apps, but here's what I'd like to do.
I'd like to plug in a USB keyboard and use it to SSH into another machine through my WiFi hotspot to do some HTML/JS/CSS text editing while I'm outdoors (at the pool, the park, etc) as my other laptops/tablets aren't visible at all outdoors with glare. This would be a nice portable solution if I could get it to work, even editing locally on the device through some editor and sending via SFTP would be just fine.
However, I can get my USB OTG cable and USB keyboard to work on my Samsung J3 phone just fine, but not on my NGP it does nothing when plugged in, keyboard caps lock doesn't activate. Is there a way to get it to work, and does it require rooting the NGP? I haven't rooted the device yet.
JohnnyFriendly said:
However, I can get my USB OTG cable and USB keyboard to work on my Samsung J3 phone just fine, but not on my NGP it does nothing when plugged in, keyboard caps lock doesn't activate. Is there a way to get it to work, and does it require rooting the NGP? I haven't rooted the device yet.
Click to expand...
Click to collapse
As a workaround I put a VNC client on it so I can access my other devices and do the typing from there, that way I can use my RPI3 as the system with a keyboard on battery power and do some Python (Django)/NodeJS/ReactJS from the NGP using it as a monitor outdoors, but if I issue the following commands via adb to rotate into landscape mode I lose input on the NGP and have to reboot:
adb shell settings put system accelerometer_rotation 0
adb shell settings put system user_rotation 1
Any ideas?
I believe I looked at this once.
At least one of the problems is that the ID pin on the micro USB connector is not connected through to the processor.
B&N has never shown any interest in putting Bluetooth in a Nook.
We'll have to see if the latest "Nook Glowlight 3" will have either OTG or BT.
I''m trying to get mirrorlink to connect, but it never seems to work. The radio isn't detecting it.
The radio unit I have is an aftermarket and it says it requires USB Debugging to be on, however this seems to be interfering with mirrorlink. I say this because whenever I have USB debugging turned on, and I try to enable mirrorlink from the settings, it resets the connection. And whenever I have USB debugging off, the radio unit does not detect the phone. I can only guess that this is happening because mirrorlink is trying to establish a "new" usb connection, and since usb debugging is connected, the usb is already in use and would have to kill the initial connection to have a new one. I don't know if it's the way Samsung has it set up, but that's my guess.
Does anyone have a fix or any information regarding this (mirrorlink on S10+)?
I'm trying to look into the source files, however I am not quite advanced in android dev and that will take a while. If anyone has any ideas or fixes, I'll gladly try them.
I have successfully connected this tablet, a Fire HD6 2020 device before and have been able to use ADB to switch launchers but it has been very infrequent. When I did get the prompt, I had thought I had set the authorization to always but likely not as I see the "no permissions" when I do adb devices. Does anyone know if there is a way to force authorization? I plug it in frequently hoping to get the prompt and it may happen once in a hundred tries. I have tried different cables so I have no idea where to go next
Hello everyone.
Recently bought android head unit for my mustang, unfortunately I found out that the vent cover is partially covering the top portion of the screen rendering the status bar unreadable.
I found an solution for that
Over ADB type wm overscan 0,15,0,0 (adjust the 15 to whatever you want)
That will shift the whole display area but it is the only solution I could find. Is it an persistent solution i don't know.
Also to enable ADB on 7862 cpu headunits:
1.Instal ADB drivers and console on your windows pc (also I had to manually assign drivers from the driver list to the unknown device in the device manager)
2.in the head unit in settings enable developer options(3368 is the password) and debugging then change usb function to second one (right top corner three dots)
3. Connect windows laptop with the third USB connector in the android car head unit (the one which is separate) (normal usbc cable works if laptop has usbc)
4. Open windows command line and enter "adb shell"
5. Enter "wm overscan 0,15,0,0"
6. Type exit
Please move to android head units general
zachwiej said:
Please move to android head units general
Click to expand...
Click to collapse
Try again using report button. Mods don't read treads here.