Hey.
Short description: My Oneplus 3's LCD was destroyed to atoms. I'm trying to use Vysor to control the phone through my computer. I actually have USB debugging already enabled from developer options, but that is not enough, as the computer's MAC address needs to be "allowed" for debugging through a prompt that appears on my phone's notifications. Any idea how to do this?
A bit longer description of how I know that the MAC needs to be allowed through a prompt: The LCD broke during two days. First I saw partially what's on the screen, so I was able to enable USB debugging and install Vysor. It worked for these two days, but once a day I needed to allow my computer's MAC for USB debugging through the notifications of my Oneplus 3. Now I cannot do it anymore, as the screen has gone pitch black. Also, ADB says that the phone is offline / it cannot be debugged at the moment. I wish I knew the exact location of the prompt so I could just allow it, since the touch screen still works... There must be another way.
If the touchscreen still works you could just try to hit the button blindly, it's not like missing would be an issue, right?
I tried hitting the prompt blindly, but it's either not there or I already opened it and pressed "decline" which made it go away. :/
Related
Hey xda--
Here's the story: my friend's phone has a broken screen, as in, the screen works, but touch doesn't. So I can see everything fine, but I can't tap on anything.
The ultimate goal is to get a screenshot of a certain thread of SMS messages. It's the only thing she cares about at the moment. I was thinking ADB would be perfect since I can just simulate screen taps, but my PC isn't authorized on her phone for ADB. USB Debugging is enabled, and her phone is actually rooted. But it was rooted by her brother and he lives in a different country.
We can get into her recovery (clockworkmod), but obviously there's no way from there to view SMS messages. Is there any way to simulate screen presses aside from using ADB? Or, is there any way at all to authorize ADB without being able to tap the screen? I can see the prompt come up to authorize my PC, but I just can't tap "Accept".
So I've been searching Google all day and still can't find a way around all this...
Phone (Nexus 5) got the black screen of death, where a connector on the motherboard gives up due to heat/old age. It only then works by applying pressure to the connection. The digitizer would sometimes play up and I'd have to press on the spot to write emails and texts. My phone got the the point where it became unusable and the digitizer started spazzing out, in that, the flight mode button got pushed, now the screen doesn't work at all.
So heres my dilemma..
Since I flashed Android 7.1 the USB debugging mode has never stayed on through a reboot and is currently off. That ruins my Vysor option to control the phone via usb. Theres a post about a guy who turned on USB debugging via Cerberus which I have, but with flight mode on that rules that out. I've managed to find my way into recovery and ADB works but I have plenty of issues, maybe because I had to use SUhide atc after 7.1 decided to clamp down on rooted devices with banking apps, snapchat etc. My Slimport hdmi adapter isn't working well but I guess thats a cheap fix and will allow me to at least see the screen, (no digitizer though). Other option is to use usb otg to connect a mouse and try things blind.
So are there any other ideas out there? ADB still may work, I got Boot.img onto my computer, but had trouble unpacking it.
Hey Folks,
So I ran over my phone ;P...
Screen is cracked, blank, and doesn't respond to touch. Home button works.
I was able to use a blind keyboard to enable USB Debugging so I could mirror it to another device but I can't authorize my PC as the screen is broken. Any ways to get around this?
Thanks much!
sokratz said:
Hey Folks,
So I ran over my phone ;P...
Screen is cracked, blank, and doesn't respond to touch. Home button works.
I was able to use a blind keyboard to enable USB Debugging so I could mirror it to another device but I can't authorize my PC as the screen is broken. Any ways to get around this?
Thanks much!
Click to expand...
Click to collapse
If you can manage to get to recovery, hook it up to your computer and type this into the terminal:
Code:
cd ~/.android && adb push adbkey.pub /data/misc/adb/adb_keys
adb reboot
Hope it works
Well I used a combination of AirDroid and TeamViewer to get it working. Hardest part was getting the keyboard sequence to enabled usb debugging. AirDroid's Screenshot function worked really well to follow along with a keyboard but I need something that remote control the device via wifi to allow authorization and that's were TeamViewer came in. Now I guess i can do anything. As in go buy a new phone.
Hope this helps someone else!
I have my USB Config set to MTP and USB Debugging ON under Developer Options. However, whenever I connect a USB device, it always resets itself to Charge only and I have to switch it back to File or Photo transfer in order to connect to PC, AA, etc.
Any ideas on how to make the USB setting 'stick' with what I set in DO?
Is there an ADB command? Other setting I should be looking for? Any help is appreciated.
bilottag said:
I have my USB Config set to MTP and USB Debugging ON under Developer Options. However, whenever I connect a USB device, it always resets itself to Charge only and I have to switch it back to File or Photo transfer in order to connect to PC, AA, etc.
Any ideas on how to make the USB setting 'stick' with what I set in DO?
Is there an ADB command? Other setting I should be looking for? Any help is appreciated.
Click to expand...
Click to collapse
Strange, I *know* that mine 'used to' stay at whatever setting it was left at before. I just tried it now, and it still stays on whatever it was last set to, BUT... It automatically toggles the 'allow debugging over USB' to OFF every time I plug my phone into my computer. Now I know it didn't do this before, I wonder if it has something to do with 'always trust this connection' being set? Also, it really seems like this stuff is behaving just a wee bit different since I unlocked my bootloader. Hmm, could it be they have set a flag where USB debugging always turns off when the device is connected to something, IF the bootloader is unlocked?
bilottag said:
I have my USB Config set to MTP and USB Debugging ON under Developer Options. However, whenever I connect a USB device, it always resets itself to Charge only and I have to switch it back to File or Photo transfer in order to connect to PC, AA, etc.
Any ideas on how to make the USB setting 'stick' with what I set in DO?
Is there an ADB command? Other setting I should be looking for? Any help is appreciated.
Click to expand...
Click to collapse
I can confirm that this happens on mine too, really annoying, but I think this is not something a lot of people are facing, as there are literally NO other references to this that I can find. The reason why I think this is a very specific issue is that I recently got a Mate 20 X, which is essentially the same phone, and noticed that when I plug in the USB to a PC, I get a dialog pop up at the bottom of the screen asking if I want to transfer photos, files or to charge only. I NEVER saw this on the Mate 20 Pro, but that might be because I messed something up. I did do a lot of fiddling over ADB when the phone was new (mostly disabling apps) and giving permissions to apps like lightning launcher and System UI tuner and I'm wondering if this what has caused the issue.
Obviously even before I did this, I necessarily must have connected to the thing via USB, but strangely, I don't remember seeing this dialog... Having to go into developer mode to change this setting can't be how it's set up normally, as then basically no-one will be able to get connected via MTP (I suspect everyone on XDA knows about this setting, but suspect none of the average Joes even knows the option exists).
So the question is, what did we do wrong and how do we get this diaglog back because I have found that Developer mode is not accessible for other Users set up on the phone so I can't access the phone at all via USB now when the other user is using it...
I'm hoping we can work together to find out what we did wrong!
PS: I find like kaibosh99 that the USB debugging also toggles back to off. I am not rooted or bootloader unlocked
After a lot of faffing and looking into it some more, I don't get the pop-up dialog but have discovered that it is in the notification menu where it shows
USB icon . Charging via USB
Expanding that notification and tapping on it, gives the option to choose file transfer and a load of other stuff. It's a pity that a pop-up dialog doesn't open like on the Mate 20 X, you can see what I mean here
https://uk.community.huawei.com/mat...tried-usb-debugging-and-all-that-already-6786
Much easier than having to go into the notification menu!
Hi there XDA. Been a while and hope everyone's been fine. Need some expert help and hopefully some resolution can be found.
I have a Note 8 that was dropped. Belongs to a family member and was taken to me as the resident tech to get things off. I managed to get all FILES copied off the device, and they no longer need it however...being how I am, I'd like to try and recover EVERYTHING from the device. All notes and such - especially as some of these things were used for classes. However I'm stuck,
Screen is totally black and was responding to finger touches before - not doing so now. Unlocking the device isn't an issue as I can do that using the stylus or a USB keyboard through OTG. I'm able to navigate using the USB keyboard and get into certain settings, but without actually seeing what's going on I don't know what is stopping certain actions or why they don't work.
The current goal is to get talkback working so that it can read to me the various options. If I can get it on then I assume there will be smoother navigation - however....
I got my hands on a Note 9 and used two USB keyboards with OTG simultaneously to try and mirror the actions. Attempts to enable talkback failed. On the Note 9 the option comes up and you hear when it asks to be enabled, but on the damaged phone you never hear it. This is a tedious process which involves:
Attaching USB keyboard.
Using shortcut keys to get into the apps menu (ALT+A).
Navigating to SETTINGS.
Typing in the name of the area I need to get to.
Pressing the arrow keys the appropriate number of times.
etc. etc. etc.
Finally when it SHOULD be at the talkback option, nothing is read back to suggest it's enabled. Holding the VOL+/- keys for 3 seconds don't work. Inserting a SIM with data then using voice to "turn on talkback" results in a response: "I can't change talkback yet."
So now - I'm at a loss. Once I'm able to turn on USB debugging I should be able to connect to my PC/laptop and mirror the screen. From there all navigation should be easy - but following what is seen on the Note 9, it doesn't work. So I can't enable talkback and I can't enable USB debugging. I'm also not 100% sure where on the screen the prompt would appear - so unplugging and replugging then guestimate tapping have not been successful.
So far I can use it like an expensive USB drive, but I'd like to get all things off, test the functionality otherwise, and then factory reset before giving it away or selling it. Not ready to buy a screen as the cost is the same as buying a used device.
Well - that's everything. Hopefully someone can assist. I can post the exact steps after someone replies, but let me give a quick rundown below. If you have one you can try with a USB keyboard and see where it gets you.
Unlock device with PIN.
ALT+A
UP x2
Type SETTING
ENTER x3
UP x2
ENTER
Type TALKBACK
Enter x3
Down......can't recall. Think it was x2. To the voice option.
ENTER
DOWN
ENTER
DOWN
RIGHT
ENTER
The last bit should select the ALLOW option and ultimately enable talkback. But for some reason it doesn't. Nothing is heard. For the USB debugging it's the same thing except at step 8 it's "USB debugging" then down like 9 or 10 times to get to the option - then enter - then right and enter.
Nothing has worked so far to blindly enable either talkback or USB debugging. So any help is appreciated.
I'm hoping there's some file I can copy directly to the file system, or something I can manipulate on the file system to enable either of these features, but I won't hold my breath. No idea whether or not this will work, but hopeful all the same. Looking forward to replies and thanks in advance.