Database Develop

Need help trying to unlock bootloader on HTC One

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.

Device Offline Error on HTC One

Okay, I am trying to run the firewater script in order to get S-OFF. But I have run into the "device offline" error when I try to connect my Mac to my HTC One. I understand from reading why I am getting the error, and that it is due to a new "feature" of Android 4.2.2+ which gives us secure usb debugging.
Here is the rub, though: 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’.
But that is not what is happening! Whatever manages the authorization questions thought that this computer was still trusted and did not ask for a new authorization. The trick, according to this thread [http://forum.xda-developers.com/member.php?u=4159439] would seem to be to remove the
adb key from the device, so as to trigger the confirmation window to allow USB debugging. But I can not find the location of this file on my HTC One, so I have no way to remove it.
Please tell me where this file is located if you know it. I have ES File Explorer installed on my rooted HTC One, Dev. Edition, running Android 4.4.2. but that path nets me an empty folder.
Thank you for any and all assistance that you provide.
SOLUTION FOUND! - See my reply below.

Okay, typed into terminal:
cd Android/HTCOneRoot
./adb-mac version (This command gives the version of ADB that the Mac is using.)
Android Debug Bridge version 1.0.29 (Terminal returns this answer; ADB needs to be at least version 10.3.1 to properly work and fix the "device offline" error.)
Here are the steps I then followed to fix problem:
1. I unplugged my HTC One from the computer.
2. Downloaded and installed Android Studio from the Android Developers’ site into my Applications folder
3 Updated my Platform Tools, as follows:
Control-clicked on the Android Studio Application and selected “Show Package Contents” from the pulldown menu.
Followed this path to the platform tools: Android Studio/sdk folder/platform-tools folder/adb & fastboot
Option copied both adb and fastboot from platform tools to my user directory ~/Android/HTCOneRoot.
Closed Android Studio
4. Restarted the computer.
5. Launched Terminal and typed cd Android/HTCOneRoot( my user directory where my adb and fastboot are stored)
6. Typed into my terminal the command, “./adb version”
Following this command prompt, Terminal responded with “Android Debug Bridge version 1.0..3.1. (Yes!!)
7. Typed into Terminal, ./adb devices
My device did not show up right away!
8. So, I unplugged my device. Shut down my Mac and restarted it.
9. Relaunched Terminal and typed cd Android/HTCOneRoot
10. Typed ./adb kill-server
11. Then typed, .adb start-server
Terminal responded with: daemon not running. starting it now on port 5037 *
daemon started successfully *
12. Plugged in device again, and the device dialog about RSA appeared. (Whew!)
13. Clicked “OK” on the dialogue box.
14. Now typed ./adb devices and my device's serial number shows up, followed by the word "device" (not "device offline")
14 All done! No more device offline errors.

Hey all,
Has anyone a guide on how to update ADB version for Windows?
I am using unrooted HTC One (UK) on v 4.3

RickCov said:
Hey all,
Has anyone a guide on how to update ADB version for Windows?
I am using unrooted HTC One (UK) on v 4.3
Click to expand...
Click to collapse
mini-sdk-1.0.31-windows.rar
download and extract to a folder of your choice, that's all.

let me also add that post the described method - ./adb devices command came up with the device and serial, but unauthorized.
With the phone connected via usb I went to Dev. Options, unchecked USB Debugging then rechecked it, instantly the confirmation dialog box came up regarding the RSA Key for my laptop. Check the box so it remembers your computer and hit save.

I was having the exact issue described by OP and simply by getting the newest version of ADB and unchecking and rechecking debugging I got the authorization. Thanks all who offered suggested and posted links to files.

and this helped as well
metropical said:
let me also add that post the described method - ./adb devices command came up with the device and serial, but unauthorized.
With the phone connected via usb I went to Dev. Options, unchecked USB Debugging then rechecked it, instantly the confirmation dialog box came up regarding the RSA Key for my laptop. Check the box so it remembers your computer and hit save.
Click to expand...
Click to collapse
http://goo.gl/WyyzhX

adb device not found

the device is not found however I installed the drivers and I am using windows 7 I tried it with another computer and it didn't work
and it works with the recovery I want it to work to gain s-off

RedBlackPellet said:
the device is not found however I installed the drivers and I am using windows 7 I tried it with another computer and it didn't work
and it works with the recovery I want it to work to gain s-off
Click to expand...
Click to collapse
check FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

nkk71 said:
check FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
I tried with different devices laptops and mobiles and I always get device not found and different adb sdks

RedBlackPellet said:
I tried with different devices laptops and mobiles and I always get device not found and different adb sdks
Click to expand...
Click to collapse
if your booted into a rom, do you have usb debugging enabled ?
its in system, developer options, if you cant see developer options then goto about - software information - more - and tap build number 7 times, it will count down and eventually say you are now a developer, you should now see developer options in your system menu.
when you enable usb debugging and plug your phone into the computer.....eventually.....and sometimes it takes a while, you will get a pop up on your phone saying your computer wants to connect to this device, allow or deny, I suggest you allow.
if you don't get the message, then with the phone still plugged into the computer, open developer options again and disable usb debugging, then enable it again.

Seanie280672 said:
if your booted into a rom, do you have usb debugging enabled ?
its in system, developer options, if you cant see developer options then goto about - software information - more - and tap build number 7 times, it will count down and eventually say you are now a developer, you should now see developer options in your system menu.
when you enable usb debugging and plug your phone into the computer.....eventually.....and sometimes it takes a while, you will get a pop up on your phone saying your computer wants to connect to this device, allow or deny, I suggest you allow.
if you don't get the message, then with the phone still plugged into the computer, open developer options again and disable usb debugging, then enable it again.
Click to expand...
Click to collapse
Ofcourse i even tried different devices and cables and I always get device not found and simetimes device offline

RedBlackPellet said:
Ofcourse i even tried different devices and cables and I always get device not found and simetimes device offline
Click to expand...
Click to collapse
im at a loss, sorry I couldn't help any further, but if its doing it with different devices, it has to be a software issue, especially as you say its working in recovery and bootloader, the only thingf I picked out from your picture is it states your adb is out of date, but you say you've tried that too, all I can suggest is you try this one.
http://forum.xda-developers.com/showthread.php?t=2588979
also where did you get the drivers from

RedBlackPellet said:
and sometimes device offline
Click to expand...
Click to collapse
reboot PC and phone, use a USB2 port

RedBlackPellet said:
Ofcourse i even tried different devices and cables and I always get device not found and simetimes device offline
Click to expand...
Click to collapse
why are you using an adb shell to push the file? push the file using adb and then enter the shell to chmod the "ff" file (I suppose you are pushing firewater but your renamed the file to "ff" ?) And btw "adb devices" will not output your device ID from an adb shell.
Code:
adb devices
adb push ff /data/local/tmp
then
Code:
adb shell
su ---> [COLOR="blue"]to get a # prompt[/COLOR]
chmod 775 /data/local/tmp/ff [COLOR="Blue"]--> to give read/write/execute permission[/COLOR]
/data/local/tmp/ff

can't install drivers on win7 or win10

i've tried all suggestions to install the drivers and when i connect my fire to my computer, it shows up as portable device > fire. if i try to update drivers, it says that i am already using the best one, the MTP usb device.
i've followed this:
http://forum.xda-developers.com/showpost.php?p=63072252&postcount=2
and also tried the drivers from amazon and neither allow me to select the adb driver.

You have turned adb on on the Fire?

Pond-life said:
You have turned adb on on the Fire?
Click to expand...
Click to collapse
thanks for the reply.
yes, i put it in dev mode by tapping the serial numbers and it is adb enabled.

ultraman69 said:
and also tried the drivers from amazon and neither allow me to select the adb driver.
Click to expand...
Click to collapse
What error message from windows are you getting when you select the ADB driver in device manager?
For Windows 10 in case it's an unsigned driver issue.
Post #84 linux VM solution if your absolutely hitting a wall.

i cannot select the adb drivers, when i try to manually select it, by going the the folder and clicking install, windows says i already have the best drivers installed. if i try to right click and install the inf, it says it is invalid for my computer.
i also have a macbook that i can try this on, are there instruction for a mac?
i'll take a look at the vm thing, but i have no idea about vm's.
thanks.
thekrakah said:
What error message from windows are you getting when you select the ADB driver in device manager?
For Windows 10 in case it's an unsigned driver issue.
Post #84 linux VM solution if your absolutely hitting a wall.
Click to expand...
Click to collapse

ultraman69 said:
i cannot select the adb drivers, when i try to manually select it, by going the the folder and clicking install, windows says i already have the best drivers installed. if i try to right click and install the inf, it says it is invalid for my computer.
i also have a macbook that i can try this on, are there instruction for a mac?
i'll take a look at the vm thing, but i have no idea about vm's.
thanks.
Click to expand...
Click to collapse
From the images you posted it looks like you should be able to at least poll your device using the windows version of adb, and start rooting. I'll presume you already have adb installed somewhere on your system, "c:\adb", or something like that.
You should be able to poll your Fire device serial number.
Open a command prompt as administrator, goto your adb directory. On the command line type the following.
adb start-server
adb devices
adb kill-server
On your fire device you should see a popup asking you to approve the USB connecting from xxxxxxx hardware id when you try to poll it.
If you get this far you can proceed with the root process for whichever version of Fire OS 5.x.x you have.

i tried that and polling comes up with nothing. after running adb devices, there is no popup on the fire and it lists nothing.
thekrakah said:
From the images you posted it looks like you should be able to at least poll your device using the windows version of adb, and start rooting. I'll presume you already have adb installed somewhere on your system, "c:\adb", or something like that.
You should be able to poll your Fire device serial number.
Open a command prompt as administrator, goto your adb directory. On the command line type the following.
adb start-server
adb devices
adb kill-server
On your fire device you should see a popup asking you to approve the USB connecting from xxxxxxx hardware id when you try to poll it.
If you get this far you can proceed with the root process for whichever version of Fire OS 5.x.x you have.
Click to expand...
Click to collapse

for some reason, on only one out 4 of my win 10 rigs, i had to turn off driver signature enforcement. to do this go to settings, update and security, recovery, advanced startup, restart now. then in the restart menu push, troubleshoot, advanced options, startup settings, then restart. when booted choose "Disable driver signature enforcement" (which is option 7 on current build). now try to install the drivers. after successful just do a normal restart to enable the signature enforcement again

ultraman69 said:
i tried that and polling comes up with nothing. after running adb devices, there is no popup on the fire and it lists nothing.
Click to expand...
Click to collapse
Can you verify that, "android debug" mode is turned on in the Fire devices developer settings? At least that was the only way I could reproduce the same message output from "adb devices".

I faut with my win 7 laptop for about an hour with one of my fires. Has the yellow icon on unknown device. Ended up "update driver" "browse for file" "let me choose from a list" picked Android/adb composite device. Adb and fast boot now work. I originally had to install Android studio and some extras to get my first fire to link up. Pm if you need help.
Sent from my Nexus 6P using Tapatalk

I recommend RootJunky tool, does everything and gives you instructions what to dohttp://www.rootjunky.com/amazon-fire-5th-gen-supertool/ Also recommend watching all his videos https://www.youtube.com/watch?v=sVv1D_LNLTg&feature=youtu.be

ADB commands not working

Has anyone gotten the ADB commands to work? I'm trying to see if I can get by without root, so I want to enable the enhanced battery stats in GSam battery. It doesn't work for me. I'm using the latest platform tools, and I have the USB file transfer checked.
Does anyone have any suggestions that I can try?
Thanks.

Have you enabled "USB debugging" in developer options? Cause ADB definitely works here, and i haven't done anything special to get it working. Steps i'd personally take if it wouldn't work are:
Make sure USB debugging is enabled and USB is physically plugged in.
Make sure everything is ok with the ADB drivers, double-check the device manager.
Check if the device appears in "adb devices", make sure its authorized on the device.
Try actual adb shell and other relevant adb stuff.
BTW, if you seem to have troubles with ADB drivers, you can try wireless ADB instead. It is only available without root on Android 11 and does require the absolute latest SDK platform tools, but hey, i've tested it, it works, and it doesn't require any special USB drivers. Follow the "Connect to a device over Wi-Fi" steps from https://developer.android.com/studio/command-line/adb to try that.

InfX said:
Have you enabled "USB debugging" in developer options? Cause ADB definitely works here, and i haven't done anything special to get it working. Steps i'd personally take if it wouldn't work are:
Make sure USB debugging is enabled and USB is physically plugged in.
Make sure everything is ok with the ADB drivers, double-check the device manager.
Check if the device appears in "adb devices", make sure its authorized on the device.
Try actual adb shell and other relevant adb stuff.
BTW, if you seem to have troubles with ADB drivers, you can try wireless ADB instead. It is only available without root on Android 11 and does require the absolute latest SDK platform tools, but hey, i've tested it, it works, and it doesn't require any special USB drivers. Follow the "Connect to a device over Wi-Fi" steps from https://developer.android.com/studio/command-line/adb to try that.
Click to expand...
Click to collapse
Thanks!
I had already done everything you suggested, but can't get the battery stats to work. I even tried it using wireless ADB, but had the same results. I get no indication that my command was accepted . I've never enabled permissions like this before, just used root, so I don't know if anything is even supposed to come up.

What command are you trying to use exactly?

InfX said:
What command are you trying to use exactly?
Click to expand...
Click to collapse
I used :
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
and
adb shell settings put global hidden_api_policy 1
According to GSam labs website, I need to enable both of these.
I am going to try to contact the developer and see if I can get an answer as to why it's not working.

EMcTx said:
I used :
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
and
adb shell settings put global hidden_api_policy 1
According to GSam labs website, I need to enable both of these.
I am going to try to contact the developer and see if I can get an answer as to why it's not working.
Click to expand...
Click to collapse
These work for me.
Sent from my Pixel 5 using XDA Labs

EMcTx said:
I used :
adb shell pm grant com.gsamlabs.bbm android.permission.BATTERY_STATS
and
adb shell settings put global hidden_api_policy 1
According to GSam labs website, I need to enable both of these.
I am going to try to contact the developer and see if I can get an answer as to why it's not working.
Click to expand...
Click to collapse
The first command supposed to grant a specific permission (BATTERY_STATS) to a specific app, i am unfamiliar with the second one (it turns a system setting named 'hidden_api_policy' on, but i have no idea what this setting is). I have no idea if those work as expected on Android 11, and Google loves changing stuff like that.
In any case, first, make sure you don't just run those commands from start->run or equivalent, but from a command line window, so if there are any errors you have a chance to read them. And finally, don't forget to force close and restart the app in question.
---------- Post added at 01:44 AM ---------- Previous post was at 01:40 AM ----------
ridobe said:
These work for me.
Click to expand...
Click to collapse
Then the OP just doing something trivial wrong, which is a good thing, since it can be fixed

ridobe said:
These work for me.
Sent from my Pixel 5 using XDA Labs
Click to expand...
Click to collapse
Did you get any text after you entered the commands that indicated you were successful? I've tried it multiple times without success. I may try to clear the data on the app and try again.

InfX said:
The first command supposed to grant a specific permission (BATTERY_STATS) to a specific app, i am unfamiliar with the second one (it turns a system setting named 'hidden_api_policy' on, but i have no idea what this setting is). I have no idea if those work as expected on Android 11, and Google loves changing stuff like that.
In any case, first, make sure you don't just run those commands from start->run or equivalent, but from a command line window, so if there are any errors you have a chance to read them. And finally, don't forget to force close and restart the app in question.
---------- Post added at 01:44 AM ---------- Previous post was at 01:40 AM ----------
Then the OP just doing something trivial wrong, which is a good thing, since it can be fixed
Click to expand...
Click to collapse
I am using the ADB shell in the platform tools folder. Yes, I'm sure I am making some stupid mistake . I had no problem rooting my Pixel 2Xl, so I'm hoping I can figure this out. I'll just keep trying.

EMcTx said:
I am using the ADB shell in the platform tools folder. Yes, I'm sure I am making some stupid mistake . I had no problem rooting my Pixel 2Xl, so I'm hoping I can figure this out. I'll just keep trying.
Click to expand...
Click to collapse
When you do a "adb devices" do you see your phone and are you getting any prompts on your phone?

Tel864 said:
When you do a "adb devices" do you see your phone and are you getting any prompts on your phone?
Click to expand...
Click to collapse
Yes, I do see my device, and I got a prompt on my phone the first time I connected.
I have managed to adjust my AOD brightness with ADB, so it must be something I'm doing wrong with the battery stats. I'm still waiting to see if the developer can give me any pointers. If I can't figure it out, I'll find another battery app.

I finally got it to work. The developer emailed me and told me that since I had the pro version, I needed to add pro after bbm.
Thanks for all the input!

I clearly remember you mentioning getting the package name wrong... the forum migration didn't exactly go smooth for xda, i guess :-/
Edit: WTF, now i see that last post, AFTER posting this one.

I'm having a similar problem.
Typing "adb reboot bootloader" using Windows Powershell, put my USB connected tablet into bootloader mode.
However when then typing "fastboot flash twrp.img" the command line returns "waiting for device" and appears to hang.
I definitely have Debugging ON, and "twrp.img" is in the adb folder.

AussieNordo said:
I'm having a similar problem.
Typing "adb reboot bootloader" using Windows Powershell, put my USB connected tablet into bootloader mode.
However when then typing "fastboot flash twrp.img" the command line returns "waiting for device" and appears to hang.
I definitely have Debugging ON, and "twrp.img" is in the adb folder.
Click to expand...
Click to collapse
fastboot flash boot twrp.img to install twrp, fastboot boot twrp.img to boot twrp

Got it eventually.