So last night I tried unlocking my bootloader so I could root my HTC One, but I've had one issue. Whenever I get to the part where you make the back up of my apps I get the following message "adb: unable to connect for backup". My phone is conncected, and I have USB debugging enabled. I also checked the device status and it keeps reporting it as offline. I don't quite know what to do, if anyone can help it'll be appreciated.
First off, I barely know anything with regards to phones as I still learning. However, last night had a similar issue and ended up having to use cmd prompt to navigate to adb and then used it to see the device.
MrTechie890 said:
So last night I tried unlocking my bootloader so I could root my HTC One, but I've had one issue. Whenever I get to the part where you make the back up of my apps I get the following message "adb: unable to connect for backup". My phone is conncected, and I have USB debugging enabled. I also checked the device status and it keeps reporting it as offline. I don't quite know what to do, if anyone can help it'll be appreciated.
Click to expand...
Click to collapse
New security enhancements in android 4.2.2 builds (and above) require the end user to explicitly grant adb access to any connecting computers before that connecting machine can successfully issue any adb commands to your device. When you connect a 4.2.2 (and above) android device to your machine (with USB debugging enabled) for the first time, you should be prompted with a confirmation message to allow or disallow USB debugging. This message will display your computers unique RSA key fingerprint and provide you a checkbox to “Always allow from this computer”. Check this box and select ‘OK’. Your device should no longer be listed as ‘offline’
If you don’t see this prompt then you should try the following:
With your device connected via usb and the toolkit running, toggle USB debugging off/on in Settings > ‘Developer Options’ and see if the prompt comes up
Also try unplugging and re-plugging the usb connection.
BD619 said:
New security enhancements in android 4.2.2 builds (and above) require the end user to explicitly grant adb access to any connecting computers before that connecting machine can successfully issue any adb commands to your device. When you connect a 4.2.2 (and above) android device to your machine (with USB debugging enabled) for the first time, you should be prompted with a confirmation message to allow or disallow USB debugging. This message will display your computers unique RSA key fingerprint and provide you a checkbox to “Always allow from this computer”. Check this box and select ‘OK’. Your device should no longer be listed as ‘offline’
If you don’t see this prompt then you should try the following:
With your device connected via usb and the toolkit running, toggle USB debugging off/on in Settings > ‘Developer Options’ and see if the prompt comes up
Also try unplugging and re-plugging the usb connection.
Click to expand...
Click to collapse
I've already done this. I had usb debugging enable since I started this. I even tried unplugging and replugging multiple times while trying to do this. Are there any other settings I need to enable?
MrTechie890 said:
I've already done this. I had usb debugging enable since I started this. I even tried unplugging and replugging multiple times while trying to do this. Are there any other settings I need to enable?
Click to expand...
Click to collapse
You have to help us with a little more info -- ADB and Fastboot just *have* to work or you'll get nowhere:
1) What OS are you using? Version included;
2) Plug in your phone, open a command window in the appropriate place and type: adb devices
Tell us the output.
If you don't get a device listed, either your drivers are bogus on your machine and need to reload, or you're not getting USB debugging setup correctly (not sure how you miss that, so I'd think the former).
tdhite said:
You have to help us with a little more info -- ADB and Fastboot just *have* to work or you'll get nowhere:
1) What OS are you using? Version included;
2) Plug in your phone, open a command window in the appropriate place and type: adb devices
Tell us the output.
If you don't get a device listed, either your drivers are bogus on your machine and need to reload, or you're not getting USB debugging setup correctly (not sure how you miss that, so I'd think the former).
Click to expand...
Click to collapse
The version of android I'm using is 4.3, for my computer I'm using OSX 10.9, and the code that is listed when I search for my device through adb is FA3A8S902431.
MrTechie890 said:
The version of android I'm using is 4.3, for my computer I'm using OSX 10.9, and the code that is listed when I search for my device through adb is FA3A8S902431.
Click to expand...
Click to collapse
Then try this:
adb backup
That should create a backup file called: backup.ab
tdhite said:
Then try this:
adb backup
That should create a backup file called: backup.ab
Click to expand...
Click to collapse
Still get the same issue I've been getting. I typed that command in, it just tells me all the options for adb, and I then retried the other command I was using and squat.
MrTechie890 said:
Still get the same issue I've been getting. I typed that command in, it just tells me all the options for adb, and I then retried the other command I was using and squat.
Click to expand...
Click to collapse
I know you don't want to read this, but you'll need to read all about Macs and this issue. A quick Google on "adb unable to connect for backup mac" brings up all sorts of folks fighting exactly what you are. I don't have a Mac -- use Linux almost exclusively, but it all appears related to either usb debugging, or a connection timeout setting.
tdhite said:
I know you don't want to read this, but you'll need to read all about Macs and this issue. A quick Google on "adb unable to connect for backup mac" brings up all sorts of folks fighting exactly what you are. I don't have a Mac -- use Linux almost exclusively, but it all appears related to either usb debugging, or a connection timeout setting.
Click to expand...
Click to collapse
For me, doing it on Linux wouldn't be a huge issue but since I have a mac as my primary machine I'm trying to make due with it.
I think I just firgured it out actually. I just had to install the android sdk, I was using the abd files provided from a tutorial. anyhow, thanks for trying to help tdhite.
So, I went and skipped through the setup process without inserting my SIM, enabled developer options and turned on ADB access, and enabled OEM unlock while I was at it. I use eclipse frequently for other devices, so I ran an update in SDK manager. My device is not showign up as an external drive, or in ADB. However when I reboot into fastboot, I get a connection just fine. I am suspecting this is a software issue on the device itself. Any ideas?
Edit: switching from MTP to PTP was the only thing that worked
Cheetohz said:
So, I went and skipped through the setup process without inserting my SIM, enabled developer options and turned on ADB access, and enabled OEM unlock while I was at it. I use eclipse frequently for other devices, so I ran an update in SDK manager. My device is not showign up as an external drive, or in ADB. However when I reboot into fastboot, I get a connection just fine. I am suspecting this is a software issue on the device itself. Any ideas?
Edit: switching from MTP to PTP was the only thing that worked
Click to expand...
Click to collapse
What showed up in Device Manager when connected as MTP? Did it perhaps say ACER Android Device or something similar to that?
PaisanNYC said:
What showed up in Device Manager when connected as MTP? Did it perhaps say ACER Android Device or something similar to that?
Click to expand...
Click to collapse
I actually did nto check device manager. but I had the safely eject Nexus 6 show up in my task bar, so it was recognizing it as a nexus.
I just bought this device (D5803 to be precise) and I'm trying to root it. I'm following This instructions and I'm stuck at the "Rooting with exploit" step as I can't authorize the connection.
I've already tried:
Restarting the ADB server
Rebooting the device
Rebooting my PC
Changing from MTP to MSC and back
Disabling and then enabling USB debugging
Disabling and then enabling 'Developer options'
Using various ADB drivers
Using different ADB binaries
Deleting my ".Android" folder
Deleting ADB copies in other tools' folders
Plugging the device in another port
Any combination of the above
I can't find any other solution to my problem on the Internet (nor here in XDA for that matter). I'm hoping you guys will be able to enlighten me and finnaly be able to solve this.
PS: I'm pretty sure that my PC is the problem as I was never able to do this with my old SGS3 either, but I ran out of ideas about what could be causing it anyway.
EDIT: I managed to do this step on a borrowed PC, it was a breeze; further proving that my PC is the problem here. I still would like to solve this issue as I know I'll be needing ADB in the future.
Also, a little more info: I looked into the newly generated .Android folder and the "adbkey" files are missing, I tried creating blank files manually to no avail. I also tried setting write permissions to that folder as well as the SDK one manually, didin't work either. Could it be that my system cannot generate those keys for some reason?
Hello, looking for a bit of help with a problem. I broke the screen on my Nexus 6 a few days ago, and I'm trying to get access to the phone again. The screen is completely black, no image whatsoever, but the phone is still working fine (apparently, even the digitizer--the phone started ringing, so on a whim I swiped to answer the call and it worked fine). It was completely stock without root and with USB debugging disabled (I'm kicking myself for that, it was turned on until a week or so ago). It is locked with a PIN. I managed to use Wug's Nexus Root Toolkit to boot into TWRP, then used ADB to back up all the files on the device. Unfortunately, I'm waiting on a Nexus 5x to be delivered and won't get it for another few days, so I'm looking to access the text messages on the device. I've been trying to use this tool to access my phone from my computer, but the problem is that USB debugging is disabled. I tried following these instructions to enable USB debugging from recovery using ADB, but it doesn't seem to be working. First I received errors saying that the files were read-only when attempting to write to build.prop, but using this StackOverflow question and answer I remounted it and the commands seemed to work. However, after rebooting the phone it doesn't show up in ADB Devices. It does appear to have rebooted fully--I'm hearing notifications periodically again--but I'm guessing the method to enable USB debugging failed. Does anybody have any other suggestions for how I can get USB debugging enabled?
I just used adb pull to get the build.prop and default.prop, it looks like the build.prop had the changes I made in there, but the default.prop didn't. I made the changes manually and pushed my edited default.prop over, but it's still not showing in adb.
Does anyone know why PTP mode would not be retained across a reboot? It seems to revert to MTP when rebooting into either the bootloader menu or into regular user mode.
I am trying to unlock the bootloader on my Nexus 6 running the latest build N6F27C of 7.1.1 that was sideloaded over 7.0 using ADB from my Mac. Now I'd like to start again and perform a clean flash of the 7.1.1 using ADB.
In normal user mode I can enable USB debugging in Developer Options and when PTP USB mode is selected then ADB will list my device just fine, I can trigger a reboot, etc.
However, after rebooting into the bootloader menu ADB shows that it has lost connection with my device, even though the screen shows that USB is connected. The ADB device list is empty.
On subsequent reboot into user mode I can see that USB debugging mode is still on but PTP connection mode has reverted to MTP, which (at least on a Mac) can account for ADB's lost USB connection to the device.
ADB debugging in PTP mode has worked fine for me in the past, but the phone now has been through several factory resets and restores from Google's backups, plus it is on 7.1.1.