Hello Everyone,
I' ve looked through the forum, and have had issues finding an answer to my question. Is there any way to get USB debugging working for ADB? I have tried everything i can think of, and am only able to get it to work in host mode.
My head unit is already rooted, and i am willing to make changes to accomplish this.
Thank You
Hammer
hammer_gaidin said:
Hello Everyone,
I' ve looked through the forum, and have had issues finding an answer to my question. Is there any way to get USB debugging working for ADB? I have tried everything i can think of, and am only able to get it to work in host mode.
My head unit is already rooted, and i am willing to make changes to accomplish this.
Click to expand...
Click to collapse
Go into the Settings->About tablet -> buildnumber
Tap the build number 7 times and you are in developer mode. Restart the Settings and you can enable the usb debugging.
I wish it was this easy. I've tried all of the normal methods without luck.
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).
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.
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?
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?