Nearly every phone today is sold with a USB C port.
"But this phone is older than..."
My Moto Z Play was released in 2016. That phone is now 5 years old. It came with Nougat... and I can mirror the screen with a USB C hub with Built in HDMI. Plug in a mouse and you're done.
No need to leave adb enabled, which is a security hole that can be exploited by unsafe USB ports and bad actors. (Also, police.)
Pixel 5 does. I tried with one recently and noted it only does mirroring, unlike Samsung and Huawei which launch some pseudo desktop OS when plugged in.
Got out my old Moto Z Play which was retired. Restarted the phone so I couldn't use fingerprint to unlock.
Plugged in a mouse, clicked pin. Unlocked.
Moto Z Play runs Nougat, stock but rooted. You don't need root to be able to do this nor do you need ADB to be enabled.
Also confirmed to be working on Razer Phone (stock, 9/Pie) and Essential Phone (stock, 10). Also works with Keyboard instead of mouse. Just type in the pin and hit enter.
Pattern unlock will have to be done with the mouse for obvious reasons.
So if your digitizer is completely busted, you can still use a mouse and keyboard. If your display is completely busted, you likely will be able to get video alt mode with USB C out.
I tried it on a few other devices that I had in my pile. Chances are, if it's Micro USB, you won't get video on boot, even with a proper MHL adapter.
* Sony Xperia J (Jelly Bean): Nothing, Micro USB
* Sony Xperia Play (Gingerbread): Nothing, Micro USB
* Marshall London (Lollipop): Mouse and Keyboard Works, Micro USB
* Asus Zenphone 3 Zoom (Nougat): Mouse and keyboard works, USB C
IIRC, Displaylink and OTG support was officially added in Lollipop, so that kind of jives with my experience here. As always, YMMV.
On my android I can enter pin/password per keyboard, or the swipe pattern per mouse. Some early android phones had slide-out keyboards (like a Blackberry), so good support for physical keyboards isn't that surprising. I wasn't expecting the mouse support tough.
MHL largely was for MicroUSB. Chances are what you need is a USB to DP or USB to HDMI adapter. Some work in one but not the other and vise versa. In the end however, Moto Es ARE designed to be the most cut down, least featured phone in the Moto line.
You would still be able to use a mouse or keyboard to input a pin or passphrase if the screen was still semi readable.
My friends Moto Z Play 2 screen was cracked and stopped working after a hard fall. Phone still powers on and accepts touch input but no display. 2 different hubs do not push video at all, so we’re probably looking at replacing the screen to recover her pics.
With a USB C port, there's a near absolute certainty that you can simply plug in a USB hub with HDMI built in to hook your phone up to a mouse and monitor to get around the cracked screen issue.
The recent versions of Android seem to have gotten way better on ADB security. It seems to generate a keypair on every computer with ADB and require a user with the unlocked phone to authorize the keypair for each device manually. It also auto-revokes authorization if you haven't connected that device with ADB in 7 days by default.
I had a double whammy of a corroded display connection and a loose usb-c port, meaning recovering data from the phone was a very sensitive and frustrating affair.
See I did that, but got the one-two punch of death.
Cracked screen AND USB-C port failure. No charging or data transfer possible.
Apparently at one time google opted me in for Google Photos, so I have a backup of those, but recent contacts were totally lost.
Still have the board lying around and am tempted to continue tinkering with it... Or would be if I had any clue where to get insight on how to do advanced debugging on why a mobile phone wouldn't even register as connected over USB-C. Assuming some sort of handshake failure.
At the level of running apps, yes. But unless I'm way behind on my rooting tech, all of the usual methods leave the phone in a state where anyone who connects it to a computer via USB can access everything on it. AFAIK, Android has gotten way better at having phones with the stock OS locked down hard, with signed bootloaders, OS level encryption keys stored in secure media, etc, and rooting blows that all away.
Not sure what you mean there. I'm saying that one is a necessary consequence of the other. If you want to have your phone really locked down tight such that it won't give up everything to anyone who connects a USB cable to it and has a few clever tools, it's inevitably going to be tough to do things like load third-party ROMs and root the phone. And it's going to be really tough to do any of those things and also maintain that security against hostile physical access.
Did you install a custom bootloader to load your ROM and root apps? Cool, but as a consequence of that, anyone who connects a USB cable to your phone can get into anything in it. Does it supposedly have security? Wanna bet the quality of any security in a homemade app vs Google's best efforts?
You might need it if the screen cracks and you want to save data off it.
Sometimes there are ways around it by dirty booting a recovery image, but it's not as simple as it sounds, and you'd need an unlocked bootloader to do so: https://petermolnar.net/article/save-files-from-a-dead-scree...