Database Info

[Q] ADB while phone is turned off

Hi,
I just flashed a 5.0.1 custom build (I used the "eng" variant), and I was surprised to see that if I plug a USB cable connected to my PC into the phone while it is turned off I see enumeration and I can connect to the phone (presumably OFF) via adb.
it is important to mention that while in adb the screen is off and I can only see the charging icon.
the task list is somewhat limited compared to an active phone but still it is alive.
attached is the output of "ps" and "getprop"
does anyone know why the phone is alive while it need to be turned off?
can it transmit information? record information?
Thanks

PC won't recognize lg x venture for MTP or ADB?

Hello, I just purchased an LG X Venture, model number H700. It is running android 7.0. When I first got it a few days ago, I installed the drivers for it on my windows 7 computer, and plugged it in. I got a pop up on the phone where I set the default USB mode to MTP (media transfer protocol). It worked great, and I was able to tranfer files between my PC and my phone.
Then I tried to get adb debugging to work with my phone, and screwed everything up. I enabled developer options, and then checked USB debugging. I also accidentally hit the "revoke USB debugging authorization button." I installed what I think are the correct ADB drivers on my PC. Then I plugged my phone back into my PC. This time, nothing comes up. I've checked in the device manager, etc., and I can't find a trace of the phone anywhere.
I looked back at developer options under USB configuration, and it's still set to MTP. But somehow I screwed something up, because my phone and computer no longer recognize each other (except for charging).
I even tried my phone with two other computers (one also windows 7, the other mac), and got the same behavior.
Any idea how to fix this? Ideally I'd like to get ADB to work, but I would settle for just getting MTP back haha.

Actually, solved it! Turns out the cable I was using was damaged. I used another one and MTP works fine on all computers.

Change USB connection settings via ADB? (to use Vysor with broken screen Moto G5)

I am trying to use Vysor to control my Moto G5 which has a broken screen (completely black). It appears to be working otherwise (rings when called etc).
However, I cannot connect to my PC using USB cable when the phone is on, because I cannot change from "Charging only" to MTP or PTP because I cannot see it on the screen. I can connect to ADB via recovery (stock and un-rooted) but all "adb shell" commands fail (error:closed) which I assume is due to not being rooted.
I am trying to change the default USB connection mode to PTP rather than "Charging only" so I can use Vysor when the phone is booted normally, not in recovery. Has anyone got any ideas?
I either need a way to made "adb shell" commands work (to use "setprop" etc), or another way to change the USB default?

Access recovery with a broken screen?

So I accidentally dropped my Pixel and now the screen is black. The device still functions normally, only the screen doesn't work. I wanted to access my phone through Vysor but that requires I have USB debugging on. Unfortunately I restarted the phone and cannot use the fingerprint sensor to unlock it, and the only way to unlock it after a restart is to enter the passcode. I saw a tutorial on how to remove the passcode using adb which supposedly works from recovery. However, I've been struggling to reach recovery mode without being able to see what I'm doing on the screen.
I can get into fastboot just fine ("fastboot devices" shows the device is in fastboot mode) but when I press volume down twice, nothing happens for a few seconds, then the phone is "disconnected" from the computer and eventually just restarts into the normal ROM (I know this because using the fingerprint sensor makes the device vibrate). How should I get into recovery to remove my passcode? Is there an easier way to achieve what I want to do? (access the phone from my PC)
Thanks!

Vysor might work. You can remotely install it from the play store website, then access it using the chrome browser extension. I was able to do this when my pixel c display died.

skawtnyc said:
Vysor might work. You can remotely install it from the play store website, then access it using the chrome browser extension. I was able to do this when my pixel c display died.
Click to expand...
Click to collapse
I just did a remote install from the play store but when I plug it in it says the device is unauthorized, meaning USB debugging is disabled. I can't enable it because the device remains locked after a reboot until I put the pin in, which I can't do because the screen doesn't work.

efrtt said:
I just did a remote install from the play store but when I plug it in it says the device is unauthorized, meaning USB debugging is disabled. I can't enable it because the device remains locked after a reboot until I put the pin in, which I can't do because the screen doesn't work.
Click to expand...
Click to collapse
That's unfortunate. I don't know of a method for turning on USB debugging without logging into the device. It's one of the reasons why I always enable developer mode and USB debugging immediately when setting up a new device.

ADB settings

I have two Mi Mix 3 phones, one without a screen.
Few days ago I moved my screen to enable ADB support, than move it back to first phone.
So I was able to connect via the USB cable and see screen via adb, its work after rebooting the phone etc.
Today I power the phone and I can't connect via USB, adb devices shows device is "unautorized". So I guess I have to activate them by touching the screen.
Why did this happen? Why can't I connect either via USB or ADB WiFi as I set up week ago?