Related
If your G1/HTC dream's home button stops working, here is a fix (kinda). Whenever you turn your phone on it takes you to recovery (Home+Power=Recovery), here is a fix I found after an hour of Googling and ****.
Method number two got me back into my phone, but if it turns off I need to be at a computer using fastboot to turn it on.
It's better than nothing, Rogers is pissing me off. A week after the 1 year warranty and this breaks on me. Anyone know any permanent fixes or is it a hardware issue.
RichieDaze said:
I have the same problem with the home key being stuck after humidity entered my phone. Which boots me straight to recovery mode. I have managed to recover my phone with the following steps:
YOU MUST HAVE ADB AND FASTBOOT INSTALLED IN YOUR PC!!!
1) If your phone has the home button stuck, you can't update or confirm anything with the Cyanogen Recovery! Because you need the Home button to confirm. So you must revert your Recovery back to JF's Recovery to use the recovery properly in this case.
2) I have tried for weeks to make the system bypass the recovery and have succeeded. YOU MUST REBOOT YOUR PHONE FROM RECOVERY TO BOOTLOADER. So use ADB to reboot in to Bootloader mode ( adb shell reboot bootloader ). Now that your in Bootloader mode, use the FASTBOOT commands ( fastboot reboot ) and voila, it bypasses the recovery.Make a script on your Winbows or Linux to make it as easy as one click!
If I have helped, please say Hi to my Android or give me a link to a replacement Daughter board...
Click to expand...
Click to collapse
I seem to have a similar problem.
But some how, it boots up properly once in a while. But even after it boots up, I cannot go anywhere except the home screen.
If the home button is stuck, this is expected right?
Dont you have this problem?
I suggest you take the phone apart and replace the broken button.
Another thing that might be a little EASIER (without actually *fixing* anything) is to write your boot.img into your RECOVERY partition. If you need recovery, you can always "fastboot boot recovery.img". Having the regular boot image in the recovery partition *should* make it boot normal with a stuck home button. This way you don't need fastboot to normal boot the thing.
I tried opening it.
I opened the screws on the back side. But I could not figure out how to get to the home button from inside.
For some reason, I can boot in properly. (It goes into recovery sometimes. But if I switch off and wait for sometime, I can boot normally.)
My main problem is that once I boot, I cant get anywhere from the main home screen.
smileey said:
I tried opening it.
I opened the screws on the back side. But I could not figure out how to get to the home button from inside.
For some reason, I can boot in properly. (It goes into recovery sometimes. But if I switch off and wait for sometime, I can boot normally.)
My main problem is that once I boot, I cant get anywhere from the main home screen.
Click to expand...
Click to collapse
That makes sense, since as soon as you launch anything, the stuck home button will return you to home.
You may want to try harder to take it apart. You need to remove the circuit board in the "chin".
Do you know how to get access to the chin?
I could not figure that part.
When I opened the screws on the backside, I could not see anything that would lead me to the chin.
smileey said:
Do you know how to get access to the chin?
I could not figure that part.
When I opened the screws on the backside, I could not see anything that would lead me to the chin.
Click to expand...
Click to collapse
Here's the service manual:
http://mikechannon.net/PDF Manuals/HTC Dream SM (A04).pdf
It will walk you through a complete disassembly and reassembly.
Thanks a ton!!
I will try and see if I can do something about the button
Is there a better way than opening up the phone? The home button on my G1 stopped working, so, I unrooted the phone, but now it's stuck on the Triangle/Exclamation point screen. I've been able to do Alt S, (Alt+w doesn't work, I think the w is also broken), but I can't reboot because it asks for home and back button to reboot. Any other suggestions?
Ok guys, this is not a pretty solution but what you can do is re-map your phone so the camera button acts as a home key and home key does nothing. It's a hack but it's a simple one and sure beats the hell out of replacing the whole phone.
Here's a thread with directions.
I tried remapping my home button to the camera button and once in the os it works, but still boots into recovery everytime and doesn't let me wipe, flash,etc with the camera button. It aborts....
Also, a quick tip I learned......If u keep booting into recovery just go to console and type reboot android. It'll boot normally.
Sent from my HTC Dream using XDA App
with the remapping the keys make sure you push all the .kl files and if you want to remove the home button from working at all remove the home button line from the .kl file.
You should also make sure that you re-map your home button to do nothing, otherwise it will not work.
Thank u jj972 for that quick tip atleast I can get out of recovery mode....
Hello all:
I'm having a strange issue here. I have a Nexus 7 that won't boot past the X screen. I've managed to get it into recovery mode following the steps laid out everywhere on the internet, but the next step; using the volume rocker to select factory restore is not working. The screen has the word Start enclosed in an arrow, it has a little up arrow and a little down arrow, and information about bootloader version, fastboot, and its locked locked state. There are no other visible options, and nothing changes when the volume control is pressed or held.
Is there an easy solution here I'm not seeing? The only thing that works is holding the power button down to shut it off.
Have you tried "adb reboot recovery"?
Fixed
bobbytomorow said:
Have you tried "adb reboot recovery"?
Click to expand...
Click to collapse
Thanks for the reply. Adb was not an option, sadly as usb debugging was not enabled when the problems started. I did get it working however, based off that, and to explain for those who'll stumble on this with the same issue:
1. Boot into the fastboot screen (the place where you'd normally choose recovery mode)
2. Plug the Nexus 7 into your computer.
3. Enter device manager and see if you have an unknown android device.
4. Right click it and install the Google usb driver that you can find through the sdk manager part of the android sdk.
5. Try the volume keys again. Here's where it started working for me.
I hadn't realized that your computer treats fastboot mode as a separate device. It needed the same process you'd use to install the adb driver, but to be done from fastboot.
My N7 (grouper) tablet sometimes exhibits an inexplicable delay in the responsiveness of the volume rocker keys immediately after re-starting the tablet into fastboot mode. (That is, the fastboot screen is displayed exactly as you describe, but the volume rocker buttons are non-responsive).
If I wait 5 or 10 seconds, the volume rocker keys (up or down) seem to come alive after that little wait and I can use them as expected to select a recovery boot, followed by pressing the power button.
I don't have any idea what causes this delay to happen - it is odd as sometimes the delay is there, and other times the volume rocker keys are responsive immediately after the fastboot screen appears.
Maybe you have this going on, or the delay on your tablet is a little longer? Just a thought, anyway.
Glad you got it sorted out.
bftb0 said:
My N7 (grouper) tablet sometimes exhibits an inexplicable delay in the responsiveness of the volume rocker keys immediately after re-starting the tablet into fastboot mode. (That is, the fastboot screen is displayed exactly as you describe, but the volume rocker buttons are non-responsive).
If I wait 5 or 10 seconds, the volume rocker keys (up or down) seem to come alive after that little wait and I can use them as expected to select a recovery boot, followed by pressing the power button.
I don't have any idea what causes this delay to happen - it is odd as sometimes the delay is there, and other times the volume rocker keys are responsive immediately after the fastboot screen appears.
Maybe you have this going on, or the delay on your tablet is a little longer? Just a thought, anyway.
Glad you got it sorted out.
Click to expand...
Click to collapse
Interesting you should mention that @bftb0... when in the bootoader, if my Nexus 7 is USB connected to my laptop, the volume keys can (but not always) be completely non-responsive.
I've just attempted to replicate the problem... but with no success...
It last occurred after fastboot flashing TWRP with the intention of flashing Chainfire, as was recently required to re-root after the 4.4.2 OTA. With Chainfire's .zip already stored on my Nexus 7, and having successfully flashed TWRP... my next move was to use the vol keys to access recovery. The vol keys didn't work... UNTIL I DISCONECTED FROM MY LAPTOP... when they worked again. I was then able to flash Chainfire, and reacquire root without problems.
As I say, I've noticed this problem before... both with bootloader v4.23 and it's predecessor, v4.18. And you just sort of ignore it...
"oh, the volume keys are dead again - damn, forgotten to disconnect from the laptop!".
It just becomes one of those bizarre minor irritants that seem to bedevil all technology... you know how to fix it (pull the USB cable out), but you don't know what the cause is.
I suspect some bug in the bootloader itself... that is so innocuous and harmless and only occurs when the "stars-are-in-the-right-alignment", that digging it out and fixing it would just be more trouble than it's worth. Still a damned nuisance though.
I guess I'll just have to get into the habit of remembering to disconnect from my laptop after I've fastboot flashed something... if I want to access recovery afterwards.
Rgrds,
Ged.
Hi
The Volume Down button is jammed (the phone fell and landed on its edge slightly crushing the frame where the volume down is). Curiously the Volume Up button still increased the volume.
After turning the phone off the problem came when turning on the phone as it now only boots into the bootloader as a result of the jammed Volume Down button.
Once in bootloader mode, the volume up/down buttons do not change the reboot options - it appears the stuck Volume Down button is causing this.
The way to fix this is to take the phone apart (as per the Youtube clips) and physically straighten the frame.
This is no easy task, so the question: is there a way around this so that the phone can boot?
It's rooted and fastboot commands work. (I installed TWRP but can only boot to recovery with adb).
Any help will be appreciated. Thank you.
fastboot reboot system?
fury683 said:
fastboot reboot system?
Click to expand...
Click to collapse
No, the device is reading the hardware correctly and booting to bootloader. The only way to fix this is to fix your device.
akellar said:
No, the device is reading the hardware correctly and booting to bootloader. The only way to fix this is to fix your device.
Click to expand...
Click to collapse
He said he could still issue fastboot commands. If the device is OFF and he has to press the POWER button to turn it on, it is reading the VOL DOWN as being pressed as well. If he issues the reboot command in Fastboot, it should boot into system because he won't need to press the POWER button and VOL DOWN (being pressed by the bent frame) at the same time, right?
OP also said he could get to recovery from ADB, but I think he meant Fastboot because ADB is only available when you are booted to Android.
Clarification
"I installed TWRP but can only boot to recovery with adb" is unclear.
I was meaning that one can only boot directly to recovery using adb. In fastboot, one can't get to recovery.
At the moment adb can't be used - only fastboot.
When I issue the fastboot reboot command, it just returns to the bootloader. I was hoping it would bypass the Volume Down state, but sadly no.
Thanks for your input though - I knew it was a longshot.
By the way, the phone wasn't dropped, but came out of my pocket going up some stairs - the bigger size makes it not as stable!
A bit late to reply, but for the sake of the next guy that comes looking, the command you were looking for is:
Code:
fastboot continue
This should tell the bootloader to boot into system.
You are still right about not being able to boot into recovery from bootloader (that's the headache I am currently having)
Any way of disabling the volume key altogether without doing anything physical to the phone?
I tried editing Generic.kl from /system/usr/keylayout/, but that only makes a difference when the phone is booted, not before that. Any way to disable the key before the phone has booted?
Cuz this is my mum's phone and she will have no idea what "fastboot" is
Good evening everyone, i'm having a serious issue with my samsung A5. It was rooted, with custom recovery and custorm rom (Android 6.1 i think).
2 Days ago, a chewingum got stuck on my screen. I tried to remove it with nail paint remover, it did the trick but then my home button stopped working: the button itself can be pressed normally, but it won't work. I also experienced randomly long home button press actions, so i decided to turn them off. I thought that few drops of liquid may actually have gone beneath the home button. Few hours later, i experienced more issues: volume going up without anyone pressing the button (and the buttons are not stuck at all, and that side never got close to liquids), power button not doing his job etc. I tried to do a soft reset by recovery (cleaning cache and dalvik) but i ended up aslo factory resetting it for a distraction. Reconfigured the device, everything was back to normal (except the home button) but then i also experienced a couple of random volume up and crashes upon making phonecalls. SO i decided to reflash the entire rom, downloaded it + gapps, put into the decide, rebooted in recovery. Wipe cache, dalvik and also system i think, then i tried to intall the zip files but they were not there (probably i should have avoided wiping system, i get confused sometimes). I turned the device off and on, and now i'm stuck on bootloop (regular mode), can reboot it but it seems i can't go in either recovery or donwload mode (so no odin flash). Device is not recognized by the Pc. I keep rebooting it with power + home + volume down and as soon as i see the screen turn black, i try to press again volume up + home to enter recovery, but it goes straight to bootloop.
Any idea on how getting out of this situation? Thank you in advance
Dharmost said:
Good evening everyone, i'm having a serious issue with my samsung A5. It was rooted, with custom recovery and custorm rom (Android 6.1 i think).
2 Days ago, a chewingum got stuck on my screen. I tried to remove it with nail paint remover, it did the trick but then my home button stopped working: the button itself can be pressed normally, but it won't work. I also experienced randomly long home button press actions, so i decided to turn them off. I thought that few drops of liquid may actually have gone beneath the home button. Few hours later, i experienced more issues: volume going up without anyone pressing the button (and the buttons are not stuck at all, and that side never got close to liquids), power button not doing his job etc. I tried to do a soft reset by recovery (cleaning cache and dalvik) but i ended up aslo factory resetting it for a distraction. Reconfigured the device, everything was back to normal (except the home button) but then i also experienced a couple of random volume up and crashes upon making phonecalls. SO i decided to reflash the entire rom, downloaded it + gapps, put into the decide, rebooted in recovery. Wipe cache, dalvik and also system i think, then i tried to intall the zip files but they were not there (probably i should have avoided wiping system, i get confused sometimes). I turned the device off and on, and now i'm stuck on bootloop (regular mode), can reboot it but it seems i can't go in either recovery or donwload mode (so no odin flash). Device is not recognized by the Pc. I keep rebooting it with power + home + volume down and as soon as i see the screen turn black, i try to press again volume up + home to enter recovery, but it goes straight to bootloop.
Any idea on how getting out of this situation? Thank you in advance
Click to expand...
Click to collapse
Sadly, no software can fix broken hardware, it's probably best, as you'll now know, not to pour chemical liquids onto electrical devices, and just what kind of chewing gum exists that requires such extreme cleaning measures from a flat, non-porous surface I'll never know.
That said, as for rebooting, a force-restart on your device *doesn't* require you to hold Home+Volume down+Power, that should only reboot you to bootloader/download mode.
Try again only holding Power+Volume Down. THEN, when your screen goes fully black, immediately switch to Power+Volume up+Home.
You should then boot into recovery mode without any loop.
Good luck!
D4ND310 said:
Sadly, no software can fix broken hardware, it's probably best, as you'll now know, not to pour chemical liquids onto electrical devices, and just what kind of chewing gum exists that requires such extreme cleaning measures from a flat, non-porous surface I'll never know.
That said, as for rebooting, a force-restart on your device *doesn't* require you to hold Home+Volume down+Power, that should only reboot you to bootloader/download mode.
Try again only holding Power+Volume Down. THEN, when your screen goes fully black, immediately switch to Power+Volume up+Home.
You should then boot into recovery mode without any loop.
Good luck!
Click to expand...
Click to collapse
I didn't dip the smartphone into a cup of liquid, i just took a piece of cotton, poured a bit of nail pain remover (don't know the exact name in english, sorry) on it and then scratched the part where the chewing gum was on (on the soft touch back key, which works 100% fine).
I am trying using the method you described, but it seems i can't go into recovery. Maybe i'm not quick enough! will keep trying. If you have any other suggestions i will be glad to hear that!
You could try to make a USB jig, or buy one off of eBay. They're really cheap. Its basicly just a resistens that force the phone to download mode. It have worked fine for all my Sammy's including A310 so it probably works for A (15) series as well.
Just put it in USB connector and press power for a few secs and you should be in download mode.
Just an idea if everything else fails
Sent from my Honor 5X using Tapatalk
go to samsung
A hardware problem could NEVER be fixed by software ways... Unfortunatelly...
It seems that liquid made some changes on your PCB (maybe dissolved some isolators inside??)...
Anyway, go to service or replace it!
Hello everyone, i've updates about my problem and i would be glad if you could kindly point me in the right direction.
I purchased an USB Jig as suggested by one of you guys, i forced the device into dowload mode and installed a fresh stock firmware + custom recovery. When i try to boot i get a bootloop on samsung logo, and can't go into recovery probably because of the broken home button. I would like to enter recovery by using ADB command, i used to do it in the early days of Android but i'm a bit rusty and all the guides tell the procedure from an already functioning device. Since i can start it properly, is there a way to reboot it in recovery via ADB?
Thank you in advance
Dharmost said:
Hello everyone, i've updates about my problem and i would be glad if you could kindly point me in the right direction.
I purchased an USB Jig as suggested by one of you guys, i forced the device into dowload mode and installed a fresh stock firmware + custom recovery. When i try to boot i get a bootloop on samsung logo, and can't go into recovery probably because of the broken home button. I would like to enter recovery by using ADB command, i used to do it in the early days of Android but i'm a bit rusty and all the guides tell the procedure from an already functioning device. Since i can start it properly, is there a way to reboot it in recovery via ADB?
Thank you in advance
Click to expand...
Click to collapse
if you can access Download mode try this. hold volume down+home+power button. once the screen is black simply turn your finger to volume up while still holding the power and home button then release when SAMSUNG appears.
Sent from my SM-A500F using xda premium
babyyeobo14 said:
if you can access Download mode try this. hold volume down+home+power button. once the screen is black simply turn your finger to volume up while still holding the power and home button then release when SAMSUNG appears.
Sent from my SM-A500F using xda premium
Click to expand...
Click to collapse
Thanks for the suggestion, but still couldn't get into recovery. I think the home button is really broken, therefore i need to access recovery in another way.
Cause i flashed the stock samsung firmware twice with odin and i can't still start the phone properly, every guide says that a wipe of cache and dalvik solves the situation. But i need to get into recovery for that.
I can't go into recovery with normal procedure probably because the home button is not working, and all the guides about adb commands say that you need to plug in your phone when it has fully started. So i either need a way to force the device into recovery with my computer, or a firmware that once flashed doesn't give me bootloop
Got a broken power button and need to turn on your OnePlus X?
As long as one of your volume buttons and your microUSB port still work, you're lucky.
If the volume down button is working:
1. Press and hold the volume down button.
2. Connect to a USB power source.
3. The phone should vibrate and boot into the recovery. You can release the volume button at that point.
4. If you have the stock OnePlus recovery installed just tap "English", "Exit" (if present), then "Reboot".
5. Your phone should now boot up!
If only the volume up button is working, things get a bit tricky.
Before you start, read through all of the steps and the paragraph below to make sure this goes as smooth as possible.
1. Connect your device to a USB power source without pressing any button.
2. Wait for about half a second, then press and hold the volume up button.
3. If you've hit the right moment, your device will boot to fastboot mode.
4. Connect to a PC and run the command "fastboot reboot".
(If you don't know what fastboot is or you haven't set it up yet you should be able to find plenty of guides online.)
A word of caution on finding the right moment to hit the volume button:
Start with longer delays and work from there. If you hit the volume up button too early the phone will enter EDL mode, which can be hard or annoying to get out of. EDL is Qualcomm's low-level Emergency Download Mode which allows flashing the device.
When entering EDL mode the phone won't vibrate and the screen will stay off. The phone remains in EDL mode after disconnecting the USB plug.
Normally you could press and hold the power button until a hard reset to get out of there, but in this case you have the following options:
- Unplug the battery to power down the device completely if your device happens to be open.
- Wait? For as long as it takes for your device to reset from this mode on its own or for the battery to run out. idk, good luck.
- Use an EDL mode flashing tool on a PC to send the power reset command to your device. This could be viable if you have already used such a tool before, e.g. by following the "Mega UnBrick Guide" by Naman Bhalla. Alternatively you could dive into this cross platform command-line tool, which works on WIndows, Linux and macOS. Using this approach is a bit overkill and quite the tangent from what you're actually trying to do, but being able to make use of EDL can come in handy in other situations as well when you're tinkering with your Android device so taking that detour might just be worth the time.
Awesome, it worked for me.
-Incase you have entered into EDL mode, then continue charging your mobile, it will be back to old state after sometime (12 hours maybe).
- To get fastboot mode, first insert power cable then wait for vibration/ screen light illumination after that press volume up button. if you press volume up button before inserting power cable, then it will go to EDL mode, so be careful about it.