I was thinking about using the RAv1.6.2 ROM, but I see he has "removed debugging" via "Recompiled kernel RAv1.6.2".
Does this really affect ADB usage? The only research I came across was info about what debugging mode was, but I don't see why it would get taken out of a ROM if it affects ADB usage. I'm assuming I'm missing something
Related
When the Nexus 7 is plugged in there is a persistent notification that indicates "CONNECT AS / Media Device (MTP)". In this state adb devices will not show the Nexus. Not exactly obvious why, but I you select the second option "Camera (PTP)" the device is available for debugging. This choice is persistent, and I'm guessing that with a band new device it will connect as MTP until told otherwise
Click to expand...
Click to collapse
Basically, This is my problem. I need to change my Nexus usb configuration from MTP to PTP so that it'll show up on adb devices, but unfortunately I'm softbricked; I cannot get my Nexus to do anything because I can't get it pass the googlescreen.
So my question is; is there anyway to change it from MTP to PTP without having the option to enable it via the tablet?
Bump, can I configure usb through the nexus toolkit? Please help.
What do you mean?
EDIT: Saw the OP now. If you can get into bootloader mode, try flashing a factory image. If that's not the answer you were looking for, please specify your requirements and why you need them.
I don't know what you mean, and I don't understand why you recommended flashing a factory image but I'll try to elaborate.
At the moment, my Tablet doesn't allow for USB Debugging.
It is Soft Bricked, so I can't get into system to enable USB Debugging, as I have accidentally deleted my OS.
I cannot disable MTP either because I cannot access my tablet setting.
WHAT I NEED:
An alternative to accessing these such settings.
To activate usb debug you have to go in "developer options".
To repair "softbrick" you have to flash factory image in "adb sideload" or adb in linux or windows pc.
Yeah since you dleted the OS itself, your only optioons are to either flash a ROM from recovery or flash the factory image.
ivn888 said:
To activate usb debug you have to go in "developer options".
To repair "softbrick" you have to flash factory image in "adb sideload" or adb in linux or windows pc.
Click to expand...
Click to collapse
Not necessarily correct, since it depends on having a working custom recovery that can start an ADB instance. Fastboot flashing is much more reliable.
You DO NOT need USB debugging in recovery or fastboot modes.
USB debugging ONLY applies to a booted OS.
Sent from my Galaxy Nexus
Stop trying to use ADB, use FASTBOOT. There is a sticky at the top of the forum How to flash a factory image using fastboot/return to stock. It has all the information you need to return to a working device. ADB is only useful if you have a working OS, which currently you do not.
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 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.
so i'm trying to adb to my phone. rooted, unlocked, all that done. just trying to adb in. i have debugging on, phone will charge only. not notifications telling me anything. go to developer options, try to change connecting to mtp, or ptp, select it...and...charging only. i turn off debugging and then plug in usb and all options are there and work flawlessly. i am on ubuntu 16.04...all adb is up date, etc...searched and searched...and nothing for my exact problem. thank for any help. not a noob...just a lost tinkerer.
also with debugging on, lsusb doesn't show nexus. but does with debugging off.
So no one has a clue? I've done lots of searching...Everything from updating SDK, Android.rules, deleting keys (there were none), .Android folder keys, everything possible. ADB works in TWRP. Fastboot works. But still same problem...
Sent from my Pixel XL using Tapatalk
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?