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.
Related
Hey,
i've got a huge problem with my Nexus 7 32 GB 3G. I've had root and i made an update many times without any problem, but once i was making some update of 4.2.2 the device didn't want to turn on and it freezed on Google logo. I tried to do plenty of ways to repair it; unroot, factory reset, wipe... Then i tried to do a flash via Nexus 7 Toolkit, but... there is the problem! How can i do the flash without enabled USB debugging? Is there any way to evade it? Or can I enable USB debugging from my PC for example? HOW??? PLEASE!
Is there anyone who can help me with solving this problem?
Any ideas, recommendations..?
Thank you for all of your responds.:good:
flash a factory image using fastboot...
USB debugging doesn't have anything to do with fast boot mode. Fast boot is the proper way to flash the images.
USB debugging only matters within the booted OS.
You should spend some time learning the right way to do things instead of relying on toolkits.
Sent from my Galaxy Nexus
BerryRide said:
Hey,
i've got a huge problem with my Nexus 7 32 GB 3G. I've had root and i made an update many times without any problem, but once i was making some update of 4.2.2 the device didn't want to turn on and it freezed on Google logo. I tried to do plenty of ways to repair it; unroot, factory reset, wipe... Then i tried to do a flash via Nexus 7 Toolkit, but... there is the problem! How can i do the flash without enabled USB debugging? Is there any way to evade it? Or can I enable USB debugging from my PC for example? HOW??? PLEASE!
Is there anyone who can help me with solving this problem?
Any ideas, recommendations..?
Thank you for all of your responds.:good:
Click to expand...
Click to collapse
Hi, BerryRide...
You don't need USB Debugging enabled (as far I'm aware, it's not possible anyway, in FASTBOOT/BOOTLOADER mode)...
Download the factory stock image for your device, from here...
https://developers.google.com/android/nexus/images.
Shutdown your tablet... and reboot into FASTBOOT/BOOTLOADER mode (Vol Down BUTTON + PowerOn BUTTON)...
Hook your tablet up to your computer, via a USB cable (preferably the USB cable that originally shipped with your tablet)...
And run...
Code:
fastboot devices
This should return a SERIAL NUMBER, indicating you have a FASTBOOT connection, and you can then run whatever FASTBOOT commands you like... including what is in the FLASH-ALL script in the FACTORY STOCK image for your specific device.
Rgrds,
Ged.
Bumping this thread because it just really helped me!!! Thanks @GedBlake!!!!
For the longest time I could never get fastboot or flash-all to work without first enabling USB debugging and much swearing and dealing with permissions. Wound up that my device wasn't getting recognized by Windows at the bootloader. It finally worked after a manual update Device Manager -> Update Drivers using the SDK Manager directory (I subsequently read about in this thread: http://forum.xda-developers.com/showthread.php?t=1583801).
Updating my three Nexii 7 to MRA58V was a breeze this time. Wow- thanks again for the direction.
Hello guys. im a new owner of a n4. its really nice and fells a lot better than my old sgs 2 First what ive done was updating it to android 4.3.
then i wanted to install drivers, unlock bootloader and root him. the problem is with those stupid drivers :/ when i put my n4 to the pc i have only in my device manager Google Nexus ADB interface without the yellow triangle. i have the debug mode on. im using the Nexus root toolkit from Wugs and after checking the drivers, it always fails with an error like check the debug mode, check if the device is connected etc....
What im doing wrong ?
roberto18 said:
Hello guys. im a new owner of a n4. its really nice and fells a lot better than my old sgs 2 First what ive done was updating it to android 4.3.
then i wanted to install drivers, unlock bootloader and root him. the problem is with those stupid drivers :/ when i put my n4 to the pc i have only in my device manager Google Nexus ADB interface without the yellow triangle. i have the debug mode on. im using the Nexus root toolkit from Wugs and after checking the drivers, it always fails with an error like check the debug mode, check if the device is connected etc....
What im doing wrong ?
Click to expand...
Click to collapse
When you're plugged into ADB, from your fastboot/adb folder:
ADB reboot-bootloader
Fastboot oem unlock ( select yes using power up/down - power to confirm )
It will wipe your data, but from here your bootloader will be unlocked, afterwards, you can download a customer recovery, put yourself back into fastboot, and type
Fastboot flash recovery NameOfRecoveryImage
I've always used the ADB/Fastboot as opposed to the one button click tools. After owning multiple other phones, this tends to be the easiest and most flexible way.
I think you didnt understood me ive asked what im doing wrong, that my pc cant swe my device. I CANT install drivers, and root my phone
The nexus root toolkit has detailed instructions and multiple ways to get drivers working. Which did you try? Where did each method fail?
Sent from my Nexus 4 using Tapatalk 4
I have searched high and low for a forum where the same problems are presented. I have had no luck at all. So, I hope that I'm not driving anyone nuts here, but here goes
I have a 2012 Nexus 7. I am using this tablet to learn all about how to work with android software, ROMS, kernals, etc. It is unlocked and rooted. I have TWRP. It is currently stuck in a bootloop (I tried to install a custom ROM) and I have no idea if USB debug is on or not. When I connect the tablet to my PC, it will charge and the computer acknowledges that SOMETHING is connected but will not find the tablet itself. (ie: I cannot find the tablet icon to click on). I have been to dev manager and I cannot find it there either.
I have no idea what anyone is talking about with this abd sideload. Most of what is said is greek to me. If someone would be willing to explain that to me (in english) I would love to learn.
Obviously, I am in above my head and I really could use some genuine help here.
I just want to flash this thing back to stock. Could someone please explain to me how to accomplish this?
deejinfla said:
I have searched high and low for a forum where the same problems are presented. I have had no luck at all. So, I hope that I'm not driving anyone nuts here, but here goes
I have a 2012 Nexus 7. I am using this tablet to learn all about how to work with android software, ROMS, kernals, etc. It is unlocked and rooted. I have TWRP. It is currently stuck in a bootloop (I tried to install a custom ROM) and I have no idea if USB debug is on or not. When I connect the tablet to my PC, it will charge and the computer acknowledges that SOMETHING is connected but will not find the tablet itself. (ie: I cannot find the tablet icon to click on). I have been to dev manager and I cannot find it there either.
I have no idea what anyone is talking about with this abd sideload. Most of what is said is greek to me. If someone would be willing to explain that to me (in english) I would love to learn.
Obviously, I am in above my head and I really could use some genuine help here.
I just want to flash this thing back to stock. Could someone please explain to me how to accomplish this?
Click to expand...
Click to collapse
You need to read first. Then flash. If you kill your device then you won't learn too much. Start with this thread --> http://forum.xda-developers.com/showthread.php?t=1907796.
You will probably need to install the naked Android fastboot drivers (search!) to proceed through the thread, since you can't put the device into USB debugging.
Anyway, to answer your questions:
adb (Android Debug Bridge) is a tool that allows a computer to control low-level features of an Android device. adb sideload allows you to send an app or ROM from your computer to your device (usually in a custom recovery) and install it, which helps if you've accidentally killed everything on your internal memory. However, you need a custom recovery (CWM/TWRP) to use adb sideloads.
You're better off learning how to use fastboot, which is a bootloader-based tool that helps a lot with disaster recovery.
Okay, I guess I need more help. I don't understand how I am supposed to be able to use fastboot to bypass the "enable USB Debugging". If I could get this to happen, I believe I can get my device back to stock. Can you explain this to me? NONE of the descriptions online are of any use at all.
Just reboot your device using power boutton and volume+ and volume- buttons to access to bootloader mode I suggest you to use nexus root toolkit it's very simple and usefull
Sent from my Nexus 7 using XDA Premium 4 mobile app
Nexus CANNOT ENABLE USB DEBUGGING
Can I ask for your help guys? My Nexus 7 v1 is stuck on boot loop (either stuck on google screen or sometimes would proceed up to the nexus animation screen) and I've been trying to fix it with the Nexus Root Toolkit (NRT). I just have problem proceeding with the steps since the toolkit advices me to enable my device's USB DEBUGGING (open device , go to settings, then developer options etc) which I CANNOT POSSIBLY DO COS AGAIN, NEXUS IS JUST STUCKED ON BOOT LOOP.
Can you suggest OTHER ways I can enable USB Debugging in Nexus 7? I would greatly appreciate your help.
You don't need to get into USB debugging mode, as your goal is to reflash a stable ROM onto your device. You can do that with Fastboot commands when your N7 is in the (unlocked) bootloader. You can follow the instructions in the second thread in this forum, or tell NRT you're soft bricked, to install a factory ROM.
So as the title suggest, my screen is working but not recognizing touch. Basically useless.
Device is rooted, Usb debugging is enabled but RSA Key is not authorised to this pc.
Stock Lollipop with custom kernel.
Problem 1 -
I am already with CWM recovery. From what I have read from cwm recovery I must be able to get access to adb recovery mode so I can backup my app data from system but the device stills shows "Unauthorized" in recovery mode. I dont know why this is happening?
Problem 2 -
I bought the OTG USB Y Cable thinking I might be able to install a differnet kernel that support otg through external power source but then I read that most kernel require to manually enable the option in settings/tweaker app for OTG SUPPORT. I cannot do this becasue as i said my screen is not working.
Please help me out.
Does your computer recognize the phone in bootloader? If so I would suggest you flash twrp and then try booting to recovery. Then you can check if your computer recognizes it now.
theminikiller said:
Does your computer recognize the phone in bootloader? If so I would suggest you flash twrp and then try booting to recovery. Then you can check if your computer recognizes it now.
Click to expand...
Click to collapse
Yes.
Already did that and it did work.
Was able to backup few imp. data.
I just have one more question -
Is there some kernel which support otg in Lollipop without me manually going into settings/tweaker app for kernel and enabling it?
Because I cannot do it manually coz the screen is broken.
Hi
I have a nexus4 that has a broken screen, it is, it doesnt react to the finger touch, and doesnt have usb debug enabled
What could i do to extract the files from there?
I have seen that connecting a mouse via usb is not an option as this device is not compatible with that, so i think the only option i have is to flash the device to have usb debugging enabled
Is there any other option i can explore?
Thanks
I am sure that you can enter your recovery assuming that your power + vol button is still functioning.
Try to connect your device using Wug Tool and use the tool to back up all the files.
Give it a try and let us know.
Sent from my Nexus 4 using XDA-Developers mobile app
Thanks
Yes, i can get in recovery, but, i assume i would need to unlock the bootloader first, isnt it? If i do it, i will erase all the documents inside
Hi
I have tried getting into recovery, but, as expected, as usb debugging is not enabled, i cant see the device from adb
So, the key question is... how can i enable usb debug in a device with the screen broken and with bootloader locked, without wiping the data?
Thanks
It is possible to turn on usb debugging?
I have clean phone - after factory reset.