Hi, I'm really hoping someone can please help.
I accidentally dropped my 2012 Nexus 7 and now the touchscreen won't work. I am trying to backup the data. The tablet turns on and my PC recognizes it when I plug it in via USB. However because I have a passcode on the lockscreen Windows won't show the files on the tablet until I unlock the screen. This is no doubt a security feature. Is there any way possible to either bypass the lockscreen or access my data another way?
I tried using SkipSoft Android Toolkit but for every option I select it says "Waiting for USB debugging to be enabled".
2012 Nexus 7
Android 4.4.x (Can't remember if it was running 4.4.1 or 4.4.2).
Everything is stock, no root.
Bootloader version: 4.23
The problem is that USB debugging is not enabled on the device, so I cannot use adb. Is there any way around this?
Any help is greatly appreciated.
Thanks
For anyone who might be caught in a similar situation, I was able to enter the pin code via mouse and OTG cable.
Hi all,
I greatly need your help or some advice. I searched for more than 6h yesterday and Im surprised I couldnt find a solution to my problem.
Typical stuff : I broke the screen of my Nexus 4, that is completely stock 5.0.1. The phone is unrooted, bootloader is locked and obviously USB Debugging is disabled.
I need to backup some data from my phone : pictures, notes and if possible my contacts.
When I connect my phone via USB to my PC, I cant browse my files since my screen is locked. My screen is not responding at all, so no way I can unlock it. Only thing I can do is install new applications on my phone, but no way to launch them since I'd need to unlock my screen again.
I have installed adb and fastboot in order to try and use Android Screen Control, but I dont have USB Debugging enabled.
So I read that I could sideload a kernel that has USB Debugging enabled by default.
I got into Recovery Mode, and tried sideloading a zip file containing a Kernel found on the forum, but I always get an error saying the footer is wrong and the signature of the file didnt pass verification. I guess I can only sideload OTA updates ?
I tried fastbooting CWM recovery, that also didnt work.
adb devices command lists my 'recovery' device.
At this stage, all I need is to either be able to unlock my phone so I can access my files via USB (i tried few apps without success), or to enable USB debugging so I can connection using sideload, use Android Screen Control, reset the pattern lock, and backup my phone.
Also, USB OTG isnt enabled by default on Nexus 4, so that's another dead-end
So what are my options ? Where could I find a kernel that has USB Debug enabled, and how can I sideload it considering phone is not rooted, and bootloader is locked (unlocking it and whipping data defies the purpose).
THANK YOU for any advice!
There is nothing you can do with a locked bootloader and no custom recovery. Sorry man, but you're not going to be able to access your data.
Sent from my Nexus 9 using XDA Free mobile app
I've exactly the same problem, but my bootloader is unlocked and I'm rooted.
I'm also on a Nexus 4 with 5.0.1 and I'm trying to get control over my device from my Windows PC. But I don't know which kernel to use and how (yet) to enable USB debugging.
Help is appreciated.
Joakim_Lind said:
I've exactly the same problem, but my bootloader is unlocked and I'm rooted.
I'm also on a Nexus 4 with 5.0.1 and I'm trying to get control over my device from my Windows PC. But I don't know which kernel to use and how (yet) to enable USB debugging.
Help is appreciated.
Click to expand...
Click to collapse
All you need is a custom recovery to boot into to access your files. If you don't have one, download the latest version of twrp from here. http://techerrata.com/browse/twrp2/mako
Then flash that using fastboot. If you need help let us know.
Sent from my Nexus 5 using XDA Free mobile app
Hmm, "error: cannot load 'open recovery-twrp-2.3.2.3-mako'.
Sure usb-debugging doesn't have to be enabled?
Joakim_Lind said:
Hmm, "error: cannot load 'open recovery-twrp-2.3.2.3-mako'.
Sure usb-debugging doesn't have to be enabled?
Click to expand...
Click to collapse
You have an ancient version of twrp. Install the latest. I'm positive you don't need usb debugging enabled.
Sent from my Nexus 5 using XDA Free mobile app
Yes, you're so right! I also missed .img in the command
But what kernel would you recommend me to use so I have usb-debugging I can have usb-debugging enabled?
I am in almost completely the same situation! My N4 fell yesterday and shattered at the bottom right hand corner. No the touch screen doesn't work and there are sections of the screen that are black. However, I have...
root
cwm recovery
stock 5.0.1 kernel
windows 7
adb not working
fastboot working
usb debugging disabled
a need for usb debugging to become enabled.
I would like a kernel with usb debugging enabled and instructions on how to install it. Or if you have another fix, instructions on that.
Hi all,
My Samsung Galaxy S7 Edge (SM-G935FD) has broken screen after a drop. The screen is black or flickering with green, but I think that it still reacts to touch. The firmware was upgraded to Oreo stock very recently, and the phone is not password or pattern protected. USB debugging is disabled (it has never been enabled) and the phone is OEM protected, so flashing a custom recovery with ODIN doesn't work (I tried). I'd like to backup the data, and I need to find a way to enable USB debugging for that. I see two options:
- Boot into maintenance mode to activate USB debugging in spite of the black screen, using physical keys. The thing is that I can't seem to boot into maintenance mode with that version of the phone following instructions found online (maybe this maintenance mode is specific to some versions or carriers, or am I missing something here?).
- Blindly activate USB debugging using an external keyboard. To do that, I would greatly appreciate help from one of you to know the exact sequence of keys.
Hope I can get this working!
Thanks
No one with a keyboard and OTG adapter to help me on that?
Thanks!
Hello old friends,
I would love some help. My beloved Nexus 6p has a broken screen. I think it's still accepting touch input, but I cannot see anything.
Everything else works. I'm trying to connect via ADB so I can get some control, but it says the device is unauthorized. I've been googling trying to solve the issue for a few hours, but even following guides and a otg-usb keyboard I cannot enable usb-debugging as the menus seem to be different.
The phone is running a stock android 8.0 (or 8.1 maybe) but is rooted.
Could someone either a) tell me exactly what to press on the usb keyboard once I've unlocked the phone via fingerprint or
b) suggest a better idea
Thanks very much!
Unfortunately I broke the screen of my beloved 6P today and have spent the last 8 hours trying to figure out how to recover everything from it. It's still working as I can hear notifications and phone calls but the screen is blank.
After searching everywhere (xda, stackoverflow etc.), I'm a bit stuck and was wondering if anyone can help. Here's my plan/what I know:
1) I want to emulate the phone screen on my PC via USB using Android Control
2) I need USB debugging mode to access the phone via ADB
3) I need the correct (Google) USB drivers installed on my PC to access ADB
I have downloaded several tools/drivers and this is how far I got:
1) Windows sees/recognizes the phone under Devices and in Device Manager (as It does normally) - I am unable to access the phone because it's not in file transfer mode
2) When I run adb devices, the list is empty
3) I tried to update the driver to the latest Google USB driver but Windows 10 won't let me (windows has determined the best drivers etc. etc.)
I can't be sure what is blocking access via ADB. I'm sure I enabled USB debugging when I first got the phone but it was a long time ago. I read that I might need to disable Windows Driver Signing to install the latest Google driver but I haven't tried it yet.
My question is, how can I tell if it's USB debugging or the Driver? Any help would be greatly appreciated!
If you have your bootloader open, then this should be easy. You can install (if not already installed) TWRP recovery with "fastboot flash recovery file.img". When you then boot blindly into the recovery (its always the same amount of button presses in bootloader) then you can access the storage of your phone.
Other cheap solution: Get a phone with bootloop issue and use that screen from it. Then you have again a fully working phone.