• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Turn on with broken power button?

EarlyMon said:
My pleasure.

I'm sure that the MTP device driver shouldn't be causing the problem. Adb is wanting to hook in below that sort of thing. In other words, MTP is good for managed access to your storage for pictures and movies, etc etc, adb is just a direct connection for debugging.

I think that your best bet might be to take it to a service center and see if they can start it from the bench.

Your other option is if you have a pal with a Mac or Linux where usb device drivers don't exist at all.

Either way, I'm wondering if it wouldn't be a good idea to see if we can verify the device some easier way.

I'd hate to have you banging your head on Windows if the problem is really the phone. :(
Click to expand...

Alright I see.

I don't think taking it to a service center is an option for me because where I live, the service centers are pretty bad. Employees there probably know less than I do and would just send the phone to some repair center which would cost me a fortune (I would probably be better off buying a new one).

I tried rebooting my phone via Command Prompt on my fathers pc (he has windows 7 32bit) and got the same error as I got on my laptop: "error: device not found".
So I went down to my basement to get my old pc and installed ubuntu 13.10 32bit on it. Then I tried rebooting my phone with it but I think I'm doing something wrong.
I copied the sdk-tools folder into documents, opened the sdk.sh file, opened the Command Prompt (Terminal) and issued the command "sudo ./adb reboot". I had to enter my password but then I just got the error: "command not found".

Sorry, this is the first time I really used linux so I don't know much about it.
 
EarlyMon said:
Check the folder path to where you put adb, and change directory to there first in your command window.

This may work -

cd Doc(tab key)/sdk-tools

Then do this, see if adb is listed -

ls -l

(those are small Ls)

And if it's there, do the sudo ./adb exactly as before.
Click to expand...

Alright I changed directory to where the sdk-tools folder is, checked with ls -l and the files were all there. I did the sudo ./adb reboot but still got the same error as before: "command not found".
I have the german version of ubuntu installed, but that shouldn't be the problem, right?
 
So far as I know, German should not be the problem. Sudo caused you to enter your password and adb is spelled the same in any language.

Please check as follows, I don't know if you ran my installer -

1. From the "ls -l" you have a file named just "adb"

2. From the "ls -l" you see a string that looks like "rwxr-xr-x" on the same line as your adb files.

Even without running the installer, I expect #2 is ok. If #1 is not, please try -

sudo ./adb-linux reboot
 
EarlyMon said:
So far as I know, German should not be the problem. Sudo caused you to enter your password and adb is spelled the same in any language.

Please check as follows, I don't know if you ran my installer -

1. From the "ls -l" you have a file named just "adb"

2. From the "ls -l" you see a string that looks like "rwxr-xr-x" on the same line as your adb files.

Even without running the installer, I expect #2 is ok. If #1 is not, please try -

sudo ./adb-linux reboot
Click to expand...

I don't really know how to run your installer. Do I just need to open the sdk.sh file or do I have to do something else?
From the "ls -l" I don't have a file just named "adb" but I see a string that looks like "rwxr-xr-x" on the same line as the adb files.
I tried "sudo ./adb-linux reboot" but still got the same error as before: "command not found".
 
The installer just tinkers around names, it's no big deal.

But you do have something else up. :(

Let's try to sort it out.

So - you have a file named adb-linux with rwxr-xr-x (meaning, any user can read and execute that file).

And you're running "sudo ./adb-linux reboot" (no quotes of course) from inside the sdk-tools folder?

Space between sudo and ./adb-linux?

What happens when you command -

which sudo

I believe that you installed 32bit Ubuntu, you can confirm it by commanding -

uname -a
 
EarlyMon said:
The installer just tinkers around names, it's no big deal.

But you do have something else up. :(

Let's try to sort it out.

So - you have a file named adb-linux with rwxr-xr-x (meaning, any user can read and execute that file).

And you're running "sudo ./adb-linux reboot" (no quotes of course) from inside the sdk-tools folder?

Space between sudo and ./adb-linux?

What happens when you command -

which sudo

I believe that you installed 32bit Ubuntu, you can confirm it by commanding -

uname -a
Click to expand...

No, I've got the "rwxr-xr-x" string only on the lines where the .exe files lie (adb.exe, fastboot.exe and md5sums.exe), on the line where adb-linux lies, I've got the string "rw-r--r--".
Maybe this helps too: I wanted to install VLC Media Player 2.1.3 on my Ubuntu but always got an error message saying "Operation not permitted" as I tried to extract the .tar.tar file.
 
Ok, that's the problem - the x means eXecute permission and that's why it can't be found.

Do this in the sdk-tools folder -

sudo chmod 755 adb*
sudo chmod 755 fastboot*
sudo ln -sf adb-linux adb
sudo ln -sf fastboot-linux fastboot

And then go for -

sudo ./adb reboot

And I'll bet that tar file wants to install to a folder where you don't have permission, that's my guess on that.
 
EarlyMon said:
Ok, that's the problem - the x means eXecute permission and that's why it can't be found.

Do this in the sdk-tools folder -

sudo chmod 755 adb*
sudo chmod 755 fastboot*
sudo ln -sf adb-linux adb
sudo ln -sf fastboot-linux fastboot

And then go for -

sudo ./adb reboot

And I'll bet that tar file wants to install to a folder where you don't have permission, that's my guess on that.
Click to expand...

Alright, I entered these four commands in the Terminal, then I tried "sudo ./adb reboot" but the command could still not be found. Then I tried "sudo ./adb-linux reboot" and the command could be found, but I got the same error message as I got under Windows: "error: device not found". So I guess it's my phone who's the problem.
I'll maybe get a power button for my phone on the internet and try to replace it myself.
So, thank you very much for your help, I appreciate it. :)
 
Dang! :(

Well, can't say that you didn't try everything you could.

Thanks for the correction on adb vs adb-linux on the sudo line - I was going from memory while posting from my phone. :o
 
I've had this same problem for the past week and there is a really simple fix. Obviously without a power button you have two problems: 1) you can't turn the screen on and off 2) you can't turn the phone on if the battery completely dies or is removed.

Solution to not being able to turn screen on and off
-Download one of the many apps that uses the accelerometer and/or proximity sensor to control the screen

Solution to not being able to power on the phone
-Use "recovery mode" to turn the phone on and then click to restart the phone. Google search for how to enter recovery mode for your specific device, but for the Galaxy S2 Skyrocket you turn the phone off, disconnect the charging cable, and while it's off you press and hold both volume buttons at once. While holding these buttons you connect the usb charging cable and a message pops up telling you to press "volume up" to enter recovery mode or press "volume down" to exit recovery mode and restart the phone. Do this second option. Your phone will reboot and you'll be back to your home screen.

Hope this helps someone!
 
Hi, I have the same problem as well. so i did everything that you said to do, and when i typed adb reboot, it said "daemon started successfully". Now what should i do next? thanks in advance for replying :)
 
Hi,

I'm having the same problem with my HTC One X and the ADB method isn't working in Ubuntu or Windows. Also, I'm quite confident USB debugging was enabled before this happened.

I didn't even get to have the phone listed by 'adb devices'. When I connected it to the PC, it would recognize it only while the screen was on (with the charging icon). When the screen turned off the device gets disconnected, meaning it isn't listed by lsusb or the Device Manager.

Apparently, since Android 4.2.2, ADB requires an on-screen confirmation using an RSA fingerprint in order to debug via USB with the phone. I haven't found a way to override this behavior, if anyone knows how to do it please let us know
 
I have an HTC One VX with a dead power button. After reading through this whole thread I installed mini-sdk on my windows laptop, double-checked that it has only USB 2.0 ports, and tried using adb reboot. The message I see in the command prompt is:

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found

I am 99% certain that I enabled USB debugging on the phone after the last reset. Any help is appreciated. I am not due for upgrade for another month and that will be a looong month phoneless! Thoughts?
 
EarlyMon said:
You need to install adb, you can grab our Mini-SDK if you don't already have it -

http://androidforums.com/faqs/443072-adb-guide-updated-2013-05-21-a.html#post5389081

1. Charge the phone (doesn't need to be at full power but can't be blinking either).

2. Plug in to non-USB 3.0 port - USB 2.0 port is fine.

3. Open command line window (DOS or Command window in Windows, Terminal in Linux or Mac).

4. Navigate to the sdk-tools folder (or wherever your adb is installed).

5. Issue command:

adb reboot

~~~~~~

For Linux, that's:

sudo ./adb reboot

And for Mac, that's:

./adb reboot

If you didn't use the installer script.

~~~~~~~~~

To open a command line window -

Linux: press control-alt-T

Mac: Applications -> Utilities -> Terminal Window

Windows: How Do I Open Command Prompt?

Use the cd command to navigate over to the folder where you adb installed.

Let me know if that gives you any trouble.

Welcome to the forums! :)
Click to expand...

Sorry for replying for a post this old, but how can you use adb when a device is off?
all I get is "error: device not found".
 
I'm on an HTC desire 331 and I've had it for awhile now and my power button is broken. It's still there but it doesn't work whenever i click on it I've tried talking to Verizon but i have an older version so they can't help me for some reason, I've been looking around for help and I'm hoping this thread will do the trick any help? Btw if i take my phone apart in the circuits have a high chance of being damaged...
 
HankHill76 said:
The top power button on my htc 4G LTE broke off and my phone is now powered off and I can't power it back on. Is there a way to power it back on without the power button???
Click to expand...

Ok I have an m one 8 with a broken power button and don't ask me how or why but if I hold down both volume keys simultaneously (which I thought it teeter tottered between up/down but whatever do what seems to be holding them down simultaneously) it boots on after about five seconds...I have also restarted it when it's already on like that. I don't know why it works but it does. I can only think it's a failsafe for just this scenario. Don't know if it will work with your phone or not but it's worth a try.

I didn't even notice how old this post was...oh well. Maybe it can still help someone out
 
Very simple way to do this. Plug it in when it registers and charge the screen pops on. Yeah it's annoying to have to do that but, it's easy and stress free while you wait to get a new phone. Also I just through mine on screen time out 1hr for the time being.
 
Hi I have followed your instructions but my HTC One Mini piece of S@£$ is still not starting up. It's charged 100% and has a green LED. Do I just have to click on adb-mac? I can't find anywhere I can actually type a command
 
You must log in or register to reply here.
Back
Top Bottom