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?
Related
Hi all,
someone bought me a damaged (screen cracked and not usable) phone, and they want to get their photos off the device. But in order for me to even interact with the phone via terminal, or use any recovery app on computer, the adb option must be enabled! now this is where the problem is, cuase how can i enable the adb option when i am flying blind with no screen?!
SO my question is this. Is there a way to connect the phone via the cable and push a command to the phone to enable adb option?
The other problem when connecting the phone is that all that comes up when you connects to the computer is the drive to install the drivers, and not the other drives for the system. SO maybe even a way to send a commnad to the phone to enable data connection so can get access to phone internal memory?
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.
Hi everyone,
Yesterday I broke my Galaxy S7 screen in the building's stairs while leaving home.
I want to save all the stuff I have on it, but recently I installed a new stock rom and forgot to tick in the developer menu "usb debug".
I tried an adb connection but the phone is unauthorized...
I read on some french board that I could flash a special kernel (with debug usb ON) to be able to get an adb connection. but that I will be blocked because I never accept any adb connection while having my screen working....
Is there any solution ?
I need help to hopefully resolve my issue.
Have a nice end of day.
You can connect an USB keyboard/mouse. Maybe an USB-hub works too so you can connect a PC and keyboard at the same time.
I was able to unlock my screen but I can’t access to my storage because I have to enable the sharing storage...
It seems there is no solution.
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?
I believe this topic should be mostly device agnostic but for details I'm working with a Fire Tablet 10, a year or two old or so, not sure exact revision but OS and recovery are stock and it is not rooted.
In the past I have connected to this tablet over ADB from my PC (device/connection authorized). The screen and digitizer recently broke. I was still able to connect via ADB and I could even use scrcpy to remote in from my PC. I was having trouble inputting the screen unlock because the digitizer was constantly registering inputs all over the screen nonstop. I was able to unlock the screen with adb input text but as soon as I did, the tablet started opening apps, swiping the top panel, etc. I disconnected a few seconds later but in that short time something happened and now I can't get back in with ADB. My PC does recognize the tablet as being connected but can not even access typical files and folders (no files or folders show up at all). I suspect that one of the registered inputs was in the top panel like changing the usb mode to charge-only or even worse; disabled usb debugging. I have since opened it up and disconnected the screen and digitizer to prevent this from happening again.
I know the topic is asked a million times 'can I get back in if I never enabled usb debugging' but I can't find any answers for my situation where my computer should still be in the authorized devices list on the tablet, just lacking the debug interface being enabled (or something similar). I am not against buying some hardware/adapter to connect to an external display but I haven't found anything yet that will be plug-and-play out-of-the-box (all I've found so far need ADB or an app installed).
My question is: Can I do anything to re-enable standard ADB/USB debugging (or maybe ADB over IP) to get back in if I have a computer that should still be authorized?
Thank you all in advance for any advice or suggestions.
you could try to inject init.rc service
Code:
settings put global adb_enabled 1
or edit default.prop in boot (if not symlink to /system)
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
you can modify boot with AIK and flash with mtkclient or SP Flash Tool.
In any case, do a full ROM dump first. Do not try to unlock bootloader, encryption keys are bonded to bootloader lock state (some people claim it's possible to unlock bootloader without data loss, I don't believe).