Im trying install TWRP on my phone but its telling my i need ABD enabled, can anyone help please? thanks!
@danny2661 is your phone rooted? And if you want to enable adb then you have to go to settings->developer options->enable usb debugging. I also suggest to read tutorials and guides about this stuff if this is your first time.
wulsic said:
@danny2661 is your phone rooted? And if you want to enable adb then you have to go to settings->developer options->enable usb debugging. I also suggest to read tutorials and guides about this stuff if this is your first time.
Click to expand...
Click to collapse
I bought this phone amazon and the phone is rooted (checked with Rootchecker)
And i do have USb debugging enabled in my phone
@danny2661 Sorry for late reaction I was on school. Could you tell the exact program you are using and what it says exactly?
Related
Hi,
I kind of "bricked" my nexus. Kind of, because recovery is working, and I can even start the device in android. Problem is error windows pops up and I can't control a thing.
No big deal you say, but I deleted by accident the .zip of the rom I had on the device. AND USB DEBUGGING WAS OFF...
I can't transfer any file to the device, I can't start usb debugging, and every tutorial on the internet says to put the device in usb debugging -> it's bricked, that's the whole point, so WTF!
sorry, I didn't respect the unwritten rule stating you should'nt ask for help on a forum while angry furious
Hope any of you can help me...
I should add I'm really not a poweruser. I've been flashing roms for a long time following carefully the rules, but really I have no idea what I'm doing <insert meme>, so adb and stuff like that I've never used (directly).
Thanks!
Use fastboot, see the sticky that says flashing a factory image using fastboot/return to stock.
Sent from my Nexus 7(2012) that has zero issues.
Thanks for you answer.
Still, I have to turn on USB debugging
Enable usb debugging on your device (found under Settings > Developer Options)
Click to expand...
Click to collapse
I can't do that because I can't use my nexus in android.
Bipo said:
Still, I have to turn on USB debugging
I can't do that because I can't use my nexus in android.
Click to expand...
Click to collapse
USB debugging is system feature. If you cannot load system you don't need to bother about it. You can only use fastboot as writen before.
Bipo said:
Thanks for you answer.
Still, I have to turn on USB debugging
I can't do that because I can't use my nexus in android.
Click to expand...
Click to collapse
Incorrect.
Fastboot works even when there is nothing on the device save the bootloader. Follow the instructions in the flash factory thread linked above and don't apply and personal prejudices-- it does work, and is the "right" way to do things. If you use a Windows computer, then you may also need the naked fastboot drivers (which can also be found by searching).
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.
After following info on XDA and everything I could find elsewhere on the web to no avail, ADB still showed "error; device offline" . I believe I must install new rom in order to start over with computer/device recognition. After "Revoke USB Authorizations" in Settings>Developer Options>USB Debugging, believe that is a permanent revocation until computer is presented with a new system.img, (rom). But I am just noob, please correct me if I'm wrong. So if I'm correct I guess I'll Have to do Factory Reset, lose root, and go through the whole process again
diver47591 said:
After following info on XDA and everything I could find elsewhere on the web to no avail, ADB still showed "error; device offline" . I believe I must install new rom in order to start over with computer/device recognition. After "Revoke USB Authorizations" in Settings>Developer Options>USB Debugging, believe that is a permanent revocation until computer is presented with a new system.img, (rom). But I am just noob, please correct me if I'm wrong. So if I'm correct I guess I'll Have to do Factory Reset, lose root, and go through the whole process again
Click to expand...
Click to collapse
If you do a manual factory reset , never gonna lose the root.
diver47591 said:
After following info on XDA and everything I could find elsewhere on the web to no avail, ADB still showed "error; device offline" . I believe I must install new rom in order to start over with computer/device recognition. After "Revoke USB Authorizations" in Settings>Developer Options>USB Debugging, believe that is a permanent revocation until computer is presented with a new system.img, (rom). But I am just noob, please correct me if I'm wrong. So if I'm correct I guess I'll Have to do Factory Reset, lose root, and go through the whole process again
Click to expand...
Click to collapse
When you "Revoke USB Authorizations" it just clears the current saved devices. Try this, unplug device, use a USB port on back of the computer (sometimes it matters), make sure Developer Options is enabled, USB Debugging enabled, Verify apps via USB unchecked, revoke USB authorizations, then start ADB, plug phone in and wait for it to be recognized by windows, then enter the command "adb devices". The phone should ask if you want to authorize this PC.
If that fails, try a different cable.
alaneddy said:
When you "Revoke USB Authorizations" it just clears the current saved devices. Try this, unplug device, use a USB port on back of the computer (sometimes it matters), make sure Developer Options is enabled, USB Debugging enabled, Verify apps via USB unchecked, revoke USB authorizations, then start ADB, plug phone in and wait for it to be recognized by windows, then enter the command "adb devices". The phone should ask if you want to authorize this PC.
If that fails, try a different cable.
Click to expand...
Click to collapse
I was way off! I found a suggestion on another site that recommended updating sdk. Determined my sdk was version 1.0.29, updated to 1.0.30, and voila returned "device name device" good to go. Thanks so much for the help.
Hi all,
I am trying to root my phone, following this guide: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
However, I am stuck at entering 'fastboot devices' into the command prompt. It will not return my device's serial number. I know this is supposed to be becuase I don't have the correct drivers installed - but I'm pretty sure I do! I've spent hours scouring the internet for solutions and I can't find anything to help. So now I turn to you, please help me
I'm running windows 10.
I've double checked the google usb driver is installed.
I've manually installed the android bootloader interface driver.
The bootloader screen says on my phone says 'Connect USB data cable'. It is already connected and I have tried connecting it to all the ports on my laptop. I'm using the original cable that came with the phone.
Well did you enable USB debugging? I'm assuming you did but you didn't list that in the process you said you did.
Eric214 said:
Well did you enable USB debugging? I'm assuming you did but you didn't list that in the process you said you did.
Click to expand...
Click to collapse
I did indeed. And I also fixed it! I just needed to do some more tinkering. I set the fastboot.exe to recommended defaults. Not sure why it was not already but there you go. You can lock or delete this thread now, thanks!
Screen in my J5 2017 broke and I cannot unlock it anymore so I tried to make a backup via PC. I blindly rooted my phone and installed TWRP, which went OK. Then I tried to use ADB with no avail – the device isn’t listed. I got all the drivers and everything and all what shows up in the device manager is "MTP device" so I assume that my phone is stuck in MTP mode and that’s why it is not recognised by ADB. Can anybody confirm it? Does MTP mode prevents from using ADB? Also, I don’t have USB debug mode enabled but after doing some research I found out that it won’t be necessary – I’d just need to boot into TWRP and use ADB. So the only thing keeping me from making a backup of my phone is that the device isn’t listed in ADB.
Infinitiv said:
Screen in my J5 2017 broke and I cannot unlock it anymore so I tried to make a backup via PC. I blindly rooted my phone and installed TWRP, which went OK. Then I tried to use ADB with no avail – the device isn’t listed. I got all the drivers and everything and all what shows up in the device manager is "MTP device" so I assume that my phone is stuck in MTP mode and that’s why it is not recognised by ADB. Can anybody confirm it? Does MTP mode prevents from using ADB? Also, I don’t have USB debug mode enabled but after doing some research I found out that it won’t be necessary – I’d just need to boot into TWRP and use ADB. So the only thing keeping me from making a backup of my phone is that the device isn’t listed in ADB.
Click to expand...
Click to collapse
You need to have USB debug unlocked to use ADB even in recovery
Haxomen said:
You need to have USB debug unlocked to use ADB even in recovery
Click to expand...
Click to collapse
This blog entry states otherwise (around paragraph 3). Is it model‐specific or is the blog author simply wrong?
Infinitiv said:
This blog entry states otherwise (around paragraph 3). Is it model‐specific or is the blog author simply wrong?
Click to expand...
Click to collapse
He does not say that your USB debug can be turned off. He does not even mention it
Haxomen said:
He does not say that your USB debug can be turned off. He does not even mention it
Click to expand...
Click to collapse
Yes he is. The whole point of this blog entry is that he didn’t have USB debug enabled and he worked around it to make his backup. He describes how he felt hopeless when he found out that USG debugging is disabled (see the third picture in the blog entry) and that he had to manually turn the phone:
We can't use the screen, (or an adb reboot recovery command - USB debugging is not enabled) so we'll have to pop the battery out to turn the device off.
Click to expand...
Click to collapse
So, yeah… It seems that he did everything without USB debbuging enabled. So my question still stand – is he wrong or is it model‐specific? Or maybe I’ve done something wrong?
Infinitiv said:
Yes he is. The whole point of this blog entry is that he didn’t have USB debug enabled and he worked around it to make his backup. He describes how he felt hopeless when he found out that USG debugging is disabled (see the third picture in the blog entry) and that he had to manually turn the phone:
So, yeah… It seems that he did everything without USB debbuging enabled. So my question still stand – is he wrong or is it model‐specific? Or maybe I’ve done something wrong?
Click to expand...
Click to collapse
If he managed to do it, try it yourself, maybe you will be able.
Haxomen said:
If he managed to do it, try it yourself, maybe you will be able.
Click to expand...
Click to collapse
As I stated in the first post of this thread I tried it with no avail and now I’m looking for some help from people with serious knowledge on the topic.
Infinitiv said:
As I stated in the first post of this thread I tried it with no avail and now I’m looking for some help from people with serious knowledge on the topic.
Click to expand...
Click to collapse
I tried to use adb on my J5 2016 within TWRP 3.1.1 recovery, while USB debug was off, and it worked. But it did not work on a previous, unstable TWRP version. So it is probably due to your recovery, not your phone. What TWRP are you using?
I’ve used TWRP 3.1.1 from this thread: https://forum.xda-developers.com/ga...pment/twrp-twrp-recovery-j5-pro-2017-t3668266
The thing is that my device don’t get listed in ADB no matter whichever mode it’s in – download, recovery nor "normal". And I’ve checked on several PCs.
Windows recognises my phone as unknown MTP device, so I assume that my phone has MTP mode enabled and I’m stuck with it. That shouldn’t be the case since I tried to plug it in while it’s in recovery mode, but maybe you’ll find this information useful.
Haxomen said:
What TWRP are you using?
Click to expand...
Click to collapse
I assume that since I didn’t quote you in my previous post you didn’t get any notification – fixed it now. I’ve answered your question in the post above. Any thoughts?