Related
Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following Buster's guide I was able to successfully reflash stock firmware and the device runs fine when booted up now.
However, now ADB is not detecting my device. At all. I have tried running the kill-server and start-server commands to see if that would do the trick to no avail. I'm not even receiving an error saying "device not found." Rather, the device listing is left blank whenever I enter the devices command into the command prompt. I can still send commands via fastboot, but I'm concerned that there's something here that I'm missing, or that I have somehow managed to completely bork the motherboard. I have already tried uninstalling and reinstalling the Asus usb drivers, in addition to the ADB drivers/software to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.
Does usb debugging is on?
Graiden05 said:
Does usb debugging is on?
Click to expand...
Click to collapse
Yes, USB debugging is enabled; yes that was the first thing I checked.
Any other ideas?
If You use asus drivers it worth to try universal naked driver.
Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I'll give that a shot this evening.
Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I just installed the naked drivers and tried again, but that didn't work either. Fastboot still works just fine, but I'm still at a complete loss as to how to get adb working again.
Thanks for your help thus far.
Hmm... How windows show tablet when You connect it to PC?
Graiden05 said:
Hmm... How windows show tablet when You connect it to PC?
Click to expand...
Click to collapse
Yeah everything *looks* normal, and appears to be acting normally whenever I have the tablet plugged in. When my tablet is booted up and connected to my pc, I can transfer files to and from with no issue. Also when it's plugged in, there are two different entries under the device manager (one for adb and the other for the tablet itself). It's only when I have my tablet running in bootloader mode that things don't seem to want to work correctly.
I even ran netstat last night to see if there were any programs/services using the same port as adb, and even that turned up nothing. Is it possible that I somehow inadvertently altered the settings on my tablet's motherboard when I installed a bad version of CWM, per my original post?
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Graiden05 said:
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Click to expand...
Click to collapse
It wasn't a problem until I flashed the wrong version of CWM, got stuck in a boot-loop and fixed the problem using fastboot to completely wipe my tablet and start over from scratch.
Edit: I suppose I could try a fresh install of Windows.
Try first remove all drivers and software for tablet. Then install universal naked driver.
Graiden05 said:
Try first remove all drivers and software for tablet. Then install universal naked driver.
Click to expand...
Click to collapse
Update: finally got adb to detect my device. Ended up removing everything Android-related from my desktop and re-downloaded/installed everything, including usb drivers. That did the trick.
Thanks again for the help.
Hey guys, i have the following problem.
So I want to unlock the bootloader of my Moto G but to do that I must use USB debugging. But if I use the command "adb devices" it gets always shown as offline. So I did a little research and found out, that since 4.4.2 a Pop-Up should show up to allow USB debugging with the connected PC.
Problem is this Pop-Up won't show up...
Could you please help me. I couldn't find a solution. Really frustating
Have you enabled USB debugging in Developer Options in settings?
Sent from my XT1032 using Tapatalk
Of course I did ^^
battlemaxi said:
Hey guys, i have the following problem.
So I want to unlock the bootloader of my Moto G but to do that I must use USB debugging. But if I use the command "adb devices" it gets always shown as offline. So I did a little research and found out, that since 4.4.2 a Pop-Up should show up to allow USB debugging with the connected PC.
Problem is this Pop-Up won't show up...
Could you please help me. I couldn't find a solution. Really frustating
Click to expand...
Click to collapse
For my XT1031, I had to use the Motorola USB drivers for ADB to work, and Kush's Universal ADB drivers for Fastboot to work.
And if you are using Windows 8/8.1, then you have to disable to forced signature verification in order to install the Universal ADB drivers.
Also, for ADB to work in Windows, I had to set the phone's USB computer connection to Camera (PTP), instead of Media Device.
I'm using Motorolas Drivers. I downloaded them from the official website.
My ADB is also on the latest version (1.0.3.1). Also tried to factory reset my phone. Nothing works, the pop-up wont show up...
battlemaxi said:
I'm using Motorolas Drivers. I downloaded them from the official website.
My ADB is also on the latest version (1.0.3.1). Also tried to factory reset my phone. Nothing works, the pop-up wont show up...
Click to expand...
Click to collapse
Dude, you need to follow the instructions step by step and provide more info about what's going on.
1. Is your "Enable ADB debugging" enabled? You said yes.. does your phone show "Android debugging enabled" icon when you plug it into your computer? If not, you don't have it enabled !
2. If you see the notification, go to Device Manager (hope you are using Windows, or I can't really help you), then can you find your device there? If the USB drivers are installed correctly, then you should see "Android Device" then a "Motorola ADB Interface" inside it. If not, you will see a yellow exclamation with something like "Motorola device"..
3. Did you change your phone's USB computer connection to Camera (PTP)??
If adb says that the device is "offline" but you see its ID, then you didnt authorize (on the phone) the pc to access USB Debugging, its a new feature of 4.4.When you connect your phone, a prompt should appear (check the status bar if it doesnt), saying a computers with RSA Key XX:XX:XX:XX:XX:XX:XX requested access to USB Debugging.
good luck
First of thanks for your help, much appreciated
1. Yes I have USB debugging enabled. If I plug in my Moto G a icon appears in the Notification-Center which says "USB debugging activated"
2. Yes if I go into the Device Manager I can see Android Device
3. Yes I ded change my USB-Setting to PTP
Any other ideas ?
battlemaxi said:
First of thanks for your help, much appreciated
1. Yes I have USB debugging enabled. If I plug in my Moto G a icon appears in the Notification-Center which says "USB debugging activated"
2. Yes if I go into the Device Manager I can see Android Device
3. Yes I ded change my USB-Setting to PTP
Any other ideas ?
Click to expand...
Click to collapse
Actually you do not need adb to unlock the bootloader only mfastboot which does not need adb to work all you do is boot into the bootloader then follow this
http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6
liveroy said:
If adb says that the device is "offline" but you see its ID, then you didnt authorize (on the phone) the pc to access USB Debugging, its a new feature of 4.4.When you connect your phone, a prompt should appear (check the status bar if it doesnt), saying a computers with RSA Key XX:XX:XX:XX:XX:XX:XX requested access to USB Debugging.
good luck
Click to expand...
Click to collapse
As mentioned above (first post of the thread) I know that I gotta allow my PC to connect properly to the phone. But the problem is that pop-up thingy wont show up. So I'm not able to allow USB debugging for my PC...
robin0800 said:
Actually you do not need adb to unlock the bootloader only mfastboot which does not need adb to work all you do is boot into the bootloader then follow this
http://forum.xda-developers.com/showpost.php?p=47705438&postcount=6
Click to expand...
Click to collapse
Everytime I try to do this i get the errormessage, that those commands or not known even if I'm at the right folder with the fastboot.exe within it. Because of that I thought I would need the connection to be online (I'm kinda new to all of this ).
battlemaxi said:
As mentioned above (first post of the thread) I know that I gotta allow my PC to connect properly to the phone. But the problem is that pop-up thingy wont show up. So I'm not able to allow USB debugging for my PC...
Everytime I try to do this i get the errormessage, that those commands or not known even if I'm at the right folder with the fastboot.exe within it. Because of that I thought I would need the connection to be online (I'm kinda new to all of this ).
Click to expand...
Click to collapse
Just follow those instructions to the letter and any thing you don't understand or get an error message report back here
battlemaxi said:
First of thanks for your help, much appreciated
1. Yes I have USB debugging enabled. If I plug in my Moto G a icon appears in the Notification-Center which says "USB debugging activated"
2. Yes if I go into the Device Manager I can see Android Device
3. Yes I ded change my USB-Setting to PTP
Any other ideas ?
Click to expand...
Click to collapse
Hmmm... so.. what do you see when you type "adb devices" ?
Also, in your Device Manager, is the Motorola ADB interface properly installed? (no issues)?
And yes, to unlock the bootloader you just need Fastboot... when you boot to Fastboot and type "fastboot devices" do you see anything?
Okay, I will Unlock my Bootloader tomorrow but I would like to fix this issue, because I might encounter it in the future :/
battlemaxi said:
Okay, I will Unlock my Bootloader tomorrow but I would like to fix this issue, because I might encounter it in the future :/
Click to expand...
Click to collapse
Well, are you sure you fastboot works?
If so, it's very weird why adb won't...
And yeah, ADB is very useful... if not lifesaving...
Okay I'm sure fastboot works, cause I just unlocked my phone. So got anyone any ideas how I could Allow USB debugging ? :/
battlemaxi said:
Okay I'm sure fastboot works, cause I just unlocked my phone. So got anyone any ideas how I could Allow USB debugging ? :/
Click to expand...
Click to collapse
Can you see adb in the computer device manager program
battlemaxi said:
Okay I'm sure fastboot works, cause I just unlocked my phone. So got anyone any ideas how I could Allow USB debugging ? :/
Click to expand...
Click to collapse
Couldn't wait till tomorrow to unlock the bootloader huh?
Hmm... Did you use the Motorola USB drivers from the Motorola Device Manager 2.4.5?
And everything is properly installed in Device Manager? No devices with yellow exclamation?
And ADB devices shows no list of devices attached?
So weird...
battlemaxi said:
As mentioned above (first post of the thread) I know that I gotta allow my PC to connect properly to the phone. But the problem is that pop-up thingy wont show up. So I'm not able to allow USB debugging for my PC...
Everytime I try to do this i get the errormessage, that those commands or not known even if I'm at the right folder with the fastboot.exe within it. Because of that I thought I would need the connection to be online (I'm kinda new to all of this ).
Click to expand...
Click to collapse
You can revoke all authorized devices for adb access.The option is right below the USB Debugging switch in Developer Options.
Then reboot your moto g and try again.
liveroy said:
You can revoke all authorized devices for adb access.The option is right below the USB Debugging switch in Developer Options.
Then reboot your moto g and try again.
Click to expand...
Click to collapse
Even if you revoke, you should see the device listed if you run "adb devices"...
neozen21 said:
Couldn't wait till tomorrow to unlock the bootloader huh?
Hmm... Did you use the Motorola USB drivers from the Motorola Device Manager 2.4.5?
And everything is properly installed in Device Manager? No devices with yellow exclamation?
And ADB devices shows no list of devices attached?
So weird...
Click to expand...
Click to collapse
Nope
I guess I have the newest Version, cause I downloaded it from Motorola.com
Yes everything is working no yellow thingys what so eher..
If I use the 'ADB devices' command the ID of my device shows up but as already mentioned it's offline.
Gesendet von meinem XT1032 mit Tapatalk
Well, it happened
I was sitting on a bench and somehow my phone found a way to slide between my fingers and crash. (I must note that it dropped on the bench, which was like 10 cm max fall).
Anyway, I came home, plugged it into my computer and miraculously the phone works even though the screen is all crashed/pixelated/non-responsive.
Is there a way to control my phone with my computer? Like viewing everything on the computer itself?
There are some programs that I need to backup my files there in order to use them on my other phone.
Thanks!
Hi
Thanks for writing to us at XDA Assist. Here is a thread which will be very helpful to you:
[Tool][Windows] Control a device with a broken screen
Good luck!
timmaaa said:
Hi
Thanks for writing to us at XDA Assist. Here is a thread which will be very helpful to you:
[Tool][Windows] Control a device with a broken screen
Good luck!
Click to expand...
Click to collapse
Already tried it.
I can't see if I got into the recovery mode and cmd does not recognize what "adb shell" is.
Even if I somehow reach it (and I'm not sure if I really did) then on windows it gives me an error qhsusb_bulk (driver not found).
Airbender123 said:
Already tried it.
I can't see if I got into the recovery mode and cmd does not recognize what "adb shell" is.
Even if I somehow reach it (and I'm not sure if I really did) then on windows it gives me an error qhsusb_bulk (driver not found).
Click to expand...
Click to collapse
If you're seeing qhsusb_bulk in Windows there's more wrong with the phone than just the screen unfortunately. I think we're going to have to move your thread into the Nexus section so the Nexus experts can lend a hand. Please standby while we have your thread moved.
Good luck!
Transmitted via Bacon
I finally managed to get into recovery mode. It seems like the "qhsusb_bulk" error is gone.
I tried using the adb shell but it doesn't recognize my phone even though device manager sees it perfectly fine.
Any help?
Maybe there is a chance that USB debugging is enabled so I just waste my time, how can I check?
Airbender123 said:
I finally managed to get into recovery mode. It seems like the "qhsusb_bulk" error is gone.
I tried using the adb shell but it doesn't recognize my phone even though device manager sees it perfectly fine.
Any help?
Maybe there is a chance that USB debugging is enabled so I just waste my time, how can I check?
Click to expand...
Click to collapse
Does the "adb devices" command return your serial number?
Transmitted via Bacon
timmaaa said:
Does the "adb devices" command return your serial number?
Transmitted via Bacon
Click to expand...
Click to collapse
Nope, that's the problem I'm facing currently.
It just gives me an error "device not found".
There could be many reasons for that. Unfortunately I'm not terribly experienced with this phone so we'll need to wait for one of the Nexus experts to come and lend a hand.
Airbender123 said:
Nope, that's the problem I'm facing currently.
It just gives me an error "device not found".
Click to expand...
Click to collapse
Please Google "15 second adb installer". Use that to install adb drivers. Then open a command prompt. Make sure you navigate to where adb gets installed (usually in program files) then adb device
Edit: To check Developer Settings go to Settings then About phone. Tap your build number 7 times. This will enable developer options in settings. Turn on developer mode there.
Sandman-007 said:
Edit: To check Developer Settings go to Settings then About phone. Tap your build number 7 times. This will enable developer options in settings. Turn on developer mode there.
Click to expand...
Click to collapse
Ummm that's kind of hard to do with a shattered display.
OP Just follow sandmans advice to get the drivers right and you'll be able to follow the tools instructions you're trying to use to enable USB debugging. If you just want your data off you could also just use:
Code:
adb pull /sdcard
Is your Bootloader unlocked?
If USB debugging is not enabled in Android and you can not enable it in android due to unreadable screen,
Your only option is to ADB shell from custom recovery such as TWRP.
You can only boot into custom recovery if your bootloader is already UNLOCKED.
theesotericone said:
Ummm that's kind of hard to do with a shattered display.
Click to expand...
Click to collapse
Not really. There are some tools out there that let you view and control your screen on a PC.
Sandman-007 said:
Not really. There are some tools out there that let you view and control your screen on a PC.
Click to expand...
Click to collapse
Yes there are. The OP is trying to use one of them. He has a broken screen and is unable to use the screen on the device. He does not have USB Debug enabled. To use the program to mirror screen you need USB Debug enabled. See the catch-22 there? His only hope is to enable it via recovery and ADB. But as @joegestes points out if he's not already unlocked he needs to unlock for that. Unlocking wipes the phone. Another catch-22.
This thread is still alive?
Fastboot / TWRP installed, NO OS, NO USB access
I can boot in bootloader and recovery (TWRP 2.6.3.1), Win7 drivers+adb+fastboot are installed properly since I have 2 Nexus 5 and 1 is working fine (I can see the device with "fastboot devices").
There is NO OS installed, I can not connect via USB, and I can not mount the USB-OTG (tried with the working phone and it work fine).
In TRWP when try to reboot it tells me that "the device does not appear to be rooted" but the device has been rooted.
When it boot into the bootloaded, I have a window popping with the yellow triangle, than disapears, (USB device not recognized)
There is nothing in the device manager.
In bootloader I have: variant D820H, HW rev: rev_11, bootloader:HHZ12h, secure boot:enabled,Lock state:unlocked
How do I revive the phone to transfer a rom since I can not use USB-OTG or USB connection, is there a cmd I can run on the phone via terminal to enable the USB (/data is empty).
Thanks
adb sideload and update TWRP
Primokorn said:
adb sideload and update TWRP
Click to expand...
Click to collapse
I can not connect from my PC, "fastboot devices" does show any connected devices, so adb neither...
peterman3 said:
I can not connect from my PC, "fastboot devices" does show any connected devices, so adb neither...
Click to expand...
Click to collapse
Did you install fastboot on your PC?
FYI adb doesn't work when you are in the bootloader.
Primokorn said:
Did you install fastboot on your PC?
Yes fastboot is properly installed, I tried it to connect using my other working nexus 5 and it works fine, when I type "fastboot devices" I get the serial # of the phone.
With this Nexus 5 I get nothing.
NB: If I boot the phone, it get stuck with the google logo (since no OS is installed)
I just want to be able to transfer a rom file on the phone...
Click to expand...
Click to collapse
peterman3 said:
Primokorn said:
Did you install fastboot on your PC?
Yes fastboot is properly installed, I tried it to connect using my other working nexus 5 and it works fine, when I type "fastboot devices" I get the serial # of the phone.
With this Nexus 5 I get nothing.
NB: If I boot the phone, it get stuck with the google logo (since no OS is installed)
I just want to be able to transfer a rom file on the phone...
Click to expand...
Click to collapse
Weird... Boot into your recovery and adb push a rom.
Click to expand...
Click to collapse
Primokorn said:
peterman3 said:
Weird... Boot into your recovery and adb push a rom.
Click to expand...
Click to collapse
When I boot into recovery (TWRP), I can not connect, my computer does not recognize the USB port (tried differents cables including the LG original cable). like I said everything is installed properly since I have another Nexus 5 and I can perform all operation.
Is it possible that the USB is disabled / missing config file in TRWP or in bootloader ?
Click to expand...
Click to collapse
In TWRP don't you have to mount system in order to get MTP? Newer versions can do it not sure about the version you are using. If you cannot get the phone to mount over USB in either fastboot over recovery in not sure what you can do. Possibly a bad USB port on the phone?
galakanokis said:
In TWRP don't you have to mount system in order to get MTP? Newer versions can do it not sure about the version you are using. If you cannot get the phone to mount over USB in either fastboot over recovery in not sure what you can do. Possibly a bad USB port on the phone?
Click to expand...
Click to collapse
I have TWRP 2.6.3.1 installed, I can mount everything except USB-OTG (USB-OTG device is working fine on my other Nexus 5 and I can mount it within TWRP), the usb port was working fine since I was able to root, and flash other roms, phone is almost new, when the phone is connected to the PC and I turn it on (Start in System), the PC detects a USB connection and then fail.
I know for sure it is not the USB connector, it is just something in the phone USB config that is corrupted.
The only thing I can do is use File explorer within TWRP to play with (not even sure if I can edit a file).
If anyone can guide me into checking the USB config file on the phone I will really appreciate.
I wish there was an an external SD card slot...
peterman3 said:
I have TWRP 2.6.3.1 installed, I can mount everything except USB-OTG (USB-OTG device is working fine on my other Nexus 5 and I can mount it within TWRP), the usb port was working fine since I was able to root, and flash other roms, phone is almost new, when the phone is connected to the PC and I turn it on (Start in System), the PC detects a USB connection and then fail.
I know for sure it is not the USB connector, it is just something in the phone USB config that is corrupted.
The only thing I can do is use File explorer within TWRP to play with (not even sure if I can edit a file).
If anyone can guide me into checking the USB config file on the phone I will really appreciate.
I wish there was an an external SD card slot...
Click to expand...
Click to collapse
Can you get the phone to mount on a PC in TWRP or bootloader? Have you tried sideloading from recovery? Are the TWRP versions the same on both phones? There was mounting/OTG changes at some point but I'm not sure when. Don't think there are any USB config files you can access especially for the bootloader.
galakanokis said:
Can you get the phone to mount on a PC in TWRP or bootloader? Have you tried sideloading from recovery? Are the TWRP versions the same on both phones? There was mounting/OTG changes at some point but I'm not sure when. Don't think there are any USB config files you can access especially for the bootloader.
Click to expand...
Click to collapse
no I can not mount on a PC, the PC does not see the phone, if there is a cmd I can run in the terminal from TWRP to check/enable the USB, I'm not familiar with Android sdk.
So far, I typed "dmesg" in the terminal, and I can see that in :
usbhid: USB HID core driver
....
sps:BAM 0xf9304000 is registered
sps:BAM 0xf9a44000 is registered
usb_bam_ipa_create_resources: Failed to create USB_PROD resource
So the phone USB driver is not loaded...
Sorry mate, other than enabling MTP under mounts in twrp I have no idea. If the phone doesn't mount in fastboot I got nothing. I do everything in fastboot and other than setting up my PC there was nothing else to do.
Hope you figure something out.
galakanokis said:
Sorry mate, other than enabling MTP under mounts in twrp I have no idea. If the phone doesn't mount in fastboot I got nothing. I do everything in fastboot and other than setting up my PC there was nothing else to do.
Hope you figure something out.
Click to expand...
Click to collapse
Thanks, just to let you know that I tried to bind the USB port to a folder and I get "permission denied", so I thing I lost the root access, I tried to issue /su, got also "permission denied".
I probably need to find how to root the phone from within the terminal cmd.
If there's no os what are you going to root? What happened to the phone where the usb port doesn't work and there's no os?
peachpuff said:
If there's no os what are you going to root? What happened to the phone where the usb port doesn't work and there's no os?
Click to expand...
Click to collapse
Like I said I can get to the bootloader and TWRP, but the usb communication is gone (and it is NOT the usb connector).
If I put the phone into fastboot, it is not recognized by the PC, if I boot in recovery (TWRP) the PC detect a usb connection but fail to install the driver.
When I'm in TWRP, I go into Advanced > terminal cmd, I type "dmesg" in the terminal, and I can see that in :
========================
usbhid: USB HID core driver
....
sps:BAM 0xf9304000 is registered
sps:BAM 0xf9a44000 is registered
usb_bam_ipa_create_resources: Failed to create USB_PROD resource
========================
So I know that the USB driver inside the phone is not loading...if the phone does not load its own driver there is no way to use the USB cable nor the USB-OTG...
I know you have a second Nexus 5 and have used it to check against this one that you're having issues with so this may sound stupid, but how about trying a different PC/Mac other than the one you've been using?
I had the same problem, but with a working phone.
Everything was fine except the usb connection. So I ordered the USB PCB from eBay for about $8, replaced it, and everything is fine now.
Edit: This is the part, from a quick ebay search
http://pages.ebay.com/link/?nav=item.view&id=271795600723
resident0915 said:
I know you have a second Nexus 5 and have used it to check against this one that you're having issues with so this may sound stupid, but how about trying a different PC/Mac other than the one you've been using?
Click to expand...
Click to collapse
Tried with another PC (Win7 and Linux), same thing...no luck
kted said:
I had the same problem, but with a working phone.
Everything was fine except the usb connection. So I ordered the USB PCB from eBay for about $8, replaced it, and everything is fine now.
Edit: This is the part, from a quick ebay search
http://pages.ebay.com/link/?nav=item.view&id=271795600723
Click to expand...
Click to collapse
USB was working fine before the flash / wipe, so its not hardware related.
/persists partition was wiped.
peterman3 said:
USB was working fine before the flash / wipe, so its not hardware related.
/persists partition was wiped.
Click to expand...
Click to collapse
Don't bet on it.
Mine was working fine too, and it just stopped. A stray voltage or a spike while you insert or remove the usb plug, is enough.
Στάλθηκε από το Nexus 5 μου χρησιμοποιώντας Tapatalk
Hi,
I dropped my Pixel 1 too many times tonight, and the screen died. The phone is still functional, and I would like to be able to mirror it on my PC using Vysor, but for some reason, it seems to have lost the USB debugging rights, as adb devices shows "unauthorized".
Is there any way I can authorize USB debugging so that I can access my device via adb and mirror the screen?
Thanks.
goister said:
Hi,
I dropped my Pixel 1 too many times tonight, and the screen died. The phone is still functional, and I would like to be able to mirror it on my PC using Vysor, but for some reason, it seems to have lost the USB debugging rights, as adb devices shows "unauthorized".
Is there any way I can authorize USB debugging so that I can access my device via adb and mirror the screen?
Thanks.
Click to expand...
Click to collapse
Not sure, but doesn't the device automatically goes into Debugging Mode when entered into recovery mode? I think at least you can access the internal storage then. Not sure if it works, but you can give it a shot and report here.
BenjyTec said:
Not sure, but doesn't the device automatically goes into Debugging Mode when entered into recovery mode? I think at least you can access the internal storage then. Not sure if it works, but you can give it a shot and report here.
Click to expand...
Click to collapse
Thanks for the reply. That might be my last resort. However, while I'm still able to unlock my device with my fingerprint, I'd like to exhaust all my options to gain remote access to my phone via a connected PC, if possible.
Once I reboot, without a working touchscreen, my options would be much more limited since I won't be able to unlock my device.