My C1905 has been acting very strange lately. I have noticed the volume up key failed without warning. This was confirmed with CWM key test. Today, my phone was locked, on a table with nothing that could have pressed any buttons. It randomly rebooted and went into recovery mode. I rebooted it, and then to adjusted volume. The phone crashed and rebooted. When it loaded back up, it crashed when I tried to unlock (insecure lockscreen) first time after boot. I noticed some processor heat, so I removed the back to allow for cooling. The crash lead to yet another reboot. This time, the phone crashed again about 4 seconds into the boot animation. Every one of these crashes involves 2 seconds or so of screen frozen and then automatic processor reset. After this crash, the phone decided to boot to CWM recovery. I went to key test again, and noticed that it said key 766. I can't find any key that causes this code, and Googling this code makes me no wiser. I did a backup of the phone just to be sure against data loss. I left the phone powered off for 5 mins, then turned back on. After about a 3 mins boot, phone seems to be "back to normal."
The phone is "usable" now, but for how long? I'm running latest CM11 build with mounts2SD.
Can anyone shed any light on possible causes? Or even key code 766, or why volume up key failed? I use volume down more than volume up.
I've had the phone for 1yr10mnth now.
The only cause I can think of is the 68C processor temp on 30/06/15, due to warm temperature outside, roughly 34C. Possible PCB warping causing bad processor connection?
theperson333 said:
Hi,
My C1905 has been acting very strange lately. I have noticed the volume up key failed without warning. This was confirmed with CWM key test. Today, my phone was locked, on a table with nothing that could have pressed any buttons. It randomly rebooted and went into recovery mode. I rebooted it, and then to adjusted volume. The phone crashed and rebooted. When it loaded back up, it crashed when I tried to unlock (insecure lockscreen) first time after boot. I noticed some processor heat, so I removed the back to allow for cooling. The crash lead to yet another reboot. This time, the phone crashed again about 4 seconds into the boot animation. Every one of these crashes involves 2 seconds or so of screen frozen and then automatic processor reset. After this crash, the phone decided to boot to CWM recovery. I went to key test again, and noticed that it said key 766. I can't find any key that causes this code, and Googling this code makes me no wiser. I did a backup of the phone just to be sure against data loss. I left the phone powered off for 5 mins, then turned back on. After about a 3 mins boot, phone seems to be "back to normal."
The phone is "usable" now, but for how long? I'm running latest CM11 build with mounts2SD.
Can anyone shed any light on possible causes? Or even key code 766, or why volume up key failed? I use volume down more than volume up.
I've had the phone for 1yr10mnth now.
The only cause I can think of is the 68C processor temp on 30/06/15, due to warm temperature outside, roughly 34C. Possible PCB warping causing bad processor connection?
Click to expand...
Click to collapse
The problem occurred yesterday, so I tried to flash back to stock when the phone "seems to fix itself" again. I got flashtool ready, pulled the battery, inserted again, held the vol_down and connected the USB cable. The phone entered the qualcomm USB HS download mode. I remembered seeing that VOL_UP and VOL_DOWN would cause this mode to be entered aswell as missing kernel. I knew the kernel asn't missing since the phone sometimes boots fine. To further confirm this, I took the battery out, put it back in and connected the usb cable. As expected, the phone entered fastboot, as if the VOL_UP key was being held.
I tried drying the phone out, using silica desiccant, in a moisture shield bag, in case water was shorting the VOL_UP traces. No success. To my knowledge, the phone should be dry anyway. The volume switch feels fine, when pressing it, suggesting the problem is after the switch.
Could the VOL_UP button cause the crashing at the various stages outlined in the OP? I've made them bold in the quote. I also noticed that phone entered CWM whilst in my pocket and enabled, disabled and enabled again rainbow mode. I didn't even know that existed. When the phone boots normally, the VOL_UP key acts like it doesn't exist. When the phone crashes during boot, the main board seems to heat up.
Related
Hello, i bought an older desire, installed cyanogenmod 7 on it and all was running ok for ~4 days.
2 hours ago i left the phone on the table, battery was around 70%, when i came back screen was blank and i was unable to turn it on or restart it. I pulled out the battery and then inserted it back, after turning on the screen is blank and the phone permanently vibrates.
i have tried common key combinations mentioned on forums (vol - + power, back + power, vol - + power + home) with no change, the screen remains blank and the phone constantly vibrates.
i have tried to connect it to pc and to boot into recovery blindly, adb / fastboot doesnt list it after any of the key combinations, lsusb also doesnt list it, it only drains some power from usb.
I would like to know what happened, i would have understood if something like that had happened while i was flashing it / rebooting it after flashing, but it ran just fine for over 4 days. Now i have a nice usb powered vibrator :]
Would anyone care to help me with my issue? It doesnt seem to be covered anywhere on the forums. I am an android newbie but i can test probably any idea you may give me. Many thanks.
Very strange...
Try to remove the SD and the SIM to discard them as the problem.
Good luck
i have already tried that. and i have tried all combinations of sim / no sim, sd / no sd.
no effect.
i have got the same problem!!!
i've tried to root my desire following the instructions from internet, maybe i did something wrong. after i running bootloader from hdbootscreen it run in cmd window from pc the moment later it automatic shutdown the screen to black but the phone system was seem still work. ive tried to remove battery SIM SD card and reboot by combined button like instructions but nothing above screen, just stayed black screen, but my phone vibrated when i try to push power on
i hope anyone can helps us, ive just bought it 2day ago.
thank in advancej
Hey mate
I gave my old desire phone to my dad to use and I got that problem. According to him, he turned the phone off to charge and when he turned it on it just constantly vibrated.
Kinda puzzled me at first, I pulled the battery, sim and SD out but didn't fix it. Found my other genuine spare battery for it and put it in, I let it charged for a bit and turned it on.
Phone's now working with the other battery, I think I eliminated the problem but I'll have to hear back from my dad to see if he encounters the problem again.
Hope that helps you mate
[Q] Please help! Stuck in Bootloop, power button "stuck", no download mode!!
I believe this has to do with the phone thinking the power button is constantly being pressed...
I'm looking for any advice. My s3 suddenly went into a boot loop this morning. It powers on for a few seconds and turns itself back off. I took my case off and noticed the power button is loose. Doing a little research, came across similar issues online caused by the main board going faulty and the phone thinking the power button is constantly being held down.
I know this because I can remove my battery, put it back in, and without even touching any buttons, the phone will attempt to power up.
I'm currently rooted and can't get into download mode for more than 3-5 seconds before it turns itself off. I was only once able to apply the perfect pressure by squeezing the side of the phone which allowed it to boot normally, but about 30 seconds later, the power menu appeared by itself and it turned off a few seconds later.
Has this happened to anyone else?? Anybody know how to go about fixing it??
My phone is still under warranty, but I can't flash back to stock.
Things I've tried:
Download mode
Recovery mode
Different battery
I haven't tried taking the phone apart yet. I want to get a replacement if possible. But just in case, has anybody repaired this themselves??
I'm really at a loss here. Any help is much appreciated!
Darkendes said:
I believe this has to do with the phone thinking the power button is constantly being pressed...
I'm looking for any advice. My s3 suddenly went into a boot loop this morning. It powers on for a few seconds and turns itself back off. I took my case off and noticed the power button is loose. Doing a little research, came across similar issues online caused by the main board going faulty and the phone thinking the power button is constantly being held down.
I know this because I can remove my battery, put it back in, and without even touching any buttons, the phone will attempt to power up.
I'm currently rooted and can't get into download mode for more than 3-5 seconds before it turns itself off. I was only once able to apply the perfect pressure by squeezing the side of the phone which allowed it to boot normally, but about 30 seconds later, the power menu appeared by itself and it turned off a few seconds later.
Has this happened to anyone else?? Anybody know how to go about fixing it??
My phone is still under warranty, but I can't flash back to stock.
Things I've tried:
Download mode
Recovery mode
Different battery
I haven't tried taking the phone apart yet. I want to get a replacement if possible. But just in case, has anybody repaired this themselves??
I'm really at a loss here. Any help is much appreciated!
Click to expand...
Click to collapse
Wow, crazy. I'm experiencing the same issue starting yesterday! I haven't tried swapping my battery yet, but the stuck power button makes so much more sense. I'm having all the same issues with not being able to stay in recovery mode or download mode for very long.
[EDIT]
My phone also seems to be reacting to static electricity. Say I let sit on my desk... It does nothing (not cycling reboots), if I pick it up it'll just start rebooting again. This leads me to believe that maybe it's not my power button but a battery or internal component issue.
MooreHeat said:
Wow, crazy. I'm experiencing the same issue starting yesterday! I haven't tried swapping my battery yet, but the stuck power button makes so much more sense. I'm having all the same issues with not being able to stay in recovery mode or download mode for very long.
[EDIT]
My phone also seems to be reacting to static electricity. Say I let sit on my desk... It does nothing (not cycling reboots), if I pick it up it'll just start rebooting again. This leads me to believe that maybe it's not my power button but a battery or internal component issue.
Click to expand...
Click to collapse
Weird. I haven't noticed mine reacting to touch, but I did watch it try to start itself multiple times while sitting all by itself on my desk.
I'm going to take it to my carrier's in-store warranty center. They said with it rooted it can't be replaced, but they can try to repair the button if it's stuck.
We'll see what happens.
Has anybody had to replace their power button themselves before?
Darkendes said:
Weird. I haven't noticed mine reacting to touch, but I did watch it try to start itself multiple times while sitting all by itself on my desk.
I'm going to take it to my carrier's in-store warranty center. They said with it rooted it can't be replaced, but they can try to repair the button if it's stuck.
We'll see what happens.
Has anybody had to replace their power button themselves before?
Click to expand...
Click to collapse
Well I just disassembled my S3. The power button mechanism seems to be just fine. It clicks down with pressure and releases just as I would expect it to. I'm thinking my issue is something electrical or battery.
Were you doing anything when your phone went in to boot loop? I was just texting someone and then.. poof!
What ROM are you using?
So today my phone started to power it's self off. When I power on it shows the kernel screen for a few secs then powers off. I can boot into Recovery (CWM) and when I select reboot it does the same. If if I boot in to Download Mode, it only stays on a few secs.
Is it the power button? Any ideas?
I'm running the BMS Kernel and C-Rom 6.6. I have had this same rom and kernel for weeks with no issues.
djdoubt03 said:
So today my phone started to power it's self off. When I power on it shows the kernel screen for a few secs then powers off. I can boot into Recovery (CWM) and when I select reboot it does the same. If if I boot in to Download Mode, it only stays on a few secs.
Is it the power button? Any ideas?
I'm running the BMS Kernel and C-Rom 6.6. I have had this same rom and kernel for weeks with no issues.
Click to expand...
Click to collapse
Sounds like your battery is dying. Might wanna look into getting a new one.
BWolf56 said:
Sounds like your battery is dying. Might wanna look into getting a new one.
Click to expand...
Click to collapse
Interesting, I have not had any issue with the battery. I'll look into it. Any way to test without using another battery?
Anything else it could be?
Using CWM built in key test it seems it is the power button, when I touch the power key it reads as if it is being touched multiple times or heklod down. Any Fix without replacing the button?
Not that I know of I have only seen replacing it fixes it
Ive seen several people report that opening it up and jiggling the button can help, but when it does it is only temporary.
djdoubt03 said:
Using CWM built in key test it seems it is the power button, when I touch the power key it reads as if it is being touched multiple times or heklod down. Any Fix without replacing the button?
Click to expand...
Click to collapse
It's fairly easy to replace. You can buy a button off ebay for fairly cheap and look on YouTube to replace it.
Sent from my SGH-I747M using XDA Free mobile app
I agree it sounds like a stuck power button. My experience with this problem first showed in a captivate of my moms. It was very bizarre tho. On stock ROM it would constantly do the vibrate, cycle, vibrate etc. On a custom ROM however, it has had zero problems with the power button. Maybe try that? Not a sure fire fix, just telling what happened with the Cappy. ☺
If this is power button problem you can try (what i did and worked, but it is your choice and you can damage your phone) drop little of oil in power button and press couple time with out battery in phone.
norbarb said:
If this is power button problem you can try (what i did and worked, but it is your choice and you can damage your phone) drop little of oil in power button and press couple time with out battery in phone.
Click to expand...
Click to collapse
That's actually fairly dangerous for your device. I would suggest an air duster if you think it's dirty.
I'm actually having the same problem. It just started his morning.
The phone won't boot normally. I get the kernel boot screen, sometimes a Samsung screen, and then it turns off. 2-3 seconds max.
I can get it into download mode, but after 3-4 seconds, it spontaneously shuts off.
Recovery mode (CWM) is completely stable. I can get in, make back ups, perform a key test, etc. When I run a key test, it shows that the power button is a little sensitive, but not crazy. If I jiggle it some (mostly back a little) it registers a key press, even if I'm not fully pressing it. If I do press it fully, sometimes it doesn't register.
If this is really a button issue, why is recovery stable? Even if I put the phone on a flat surface with nothing that could touch the button, the phone still doesn't stay in download mode (it just shuts off.) When I put the phone in recovery, place it on a flat surface, and perform the key test, the phone isn't registering a key touch.
I've tried 3 different batteries, kept the phone plugged in, popped the battery and held the power button to discharge everything, wiped the cache, wiped dalvik cache, and used CWM touch to reboot (and avoid the power button all together.)
The only think I can think of that's maybe different is that gapps was FC'ing more than normal this morning (before the phone crapped out.)
I'm running StockMOD ROM 4.4.2 R2 with the Ktoonsez Kernel for TouchWiz 4.4.2.
EDIT: Also, when it's plugged in, the LED doesn't light up. I'm not sure that it's actually charging. I do have a wall charger, so I can verify that the batteries I'm using are charged.
Try flashing a different rom from recovery to see if it still happens. Also try a factory reset. If you get as close to stock as possible and it still happens it raises the probability thst its hardware.
If you put the battery in and wait a few moments does it turn on by itself?
Band-aid
@DocHoliday77 I messed with the phone a little later tonight and recovery became unstable. I'm convinced it's a power button problem now. I think the internal mechanism gets stuck and that's the issue.
When I put the battery in, the phone does try to boot by itself.
I used the advice in this post: http://forum.xda-developers.com/showthread.php?p=53915864 and I was able to get up and running again. I opened the phone up, blew some compressed air on the button, tapped the flat side of the button lightly a few times with the end of my screwdriver, and put everything back together. I was able to get back into recovery, and then reboot normally.
I ordered a new power button and I plan on replacing it next week when it gets here, just to be on the safe side.
You guys at xda are life savers!
The booting up on its own after inserting the battery is a classic symptom of the power button going bad. Glad to hear you got it working for now, and that you are ordering a replacement. Everyone ive heard about getting it to work using any number of methods have always found it to only be a temporary solution.
Just a thought, in case it starts up again, maybe remove the plastic piece until you replace the switch. Hopefully that would help prevent it from getting accidentally pressed in your pocket or by bumping it into something. (You could probably still access it with a toothpick or something like that if needed)
I agree it's the power button. I just posted about my little experience on Google+
I tried seriously whacking it on the floor and everything. I wouldn't recommend that but I had no warranty and no funds for repair. Others had said that beating the crap out of it worked so I thought why not lol...
https://plus.google.com/116004961340303353216/posts/ig2ogLeUWJ8
Long story short, my beating it up didn't work but it did wake it up. It falling on the floor however, jarred whatever was stuck and it now works like a charm...good luck
I have a Google Galaxy Nexus and was using it last night (8/11)--it was a bit slow, as it has been for a few weeks, so I shut it down and hope restarting may help. When I started it back up, it was stuck on the "Google" word for about an hour and then I suppose lost power. I was not near a computer to plug it in.
When I got home, I plugged it into my pc to charge, then read online to hold down Power + Up + Down, which I did. I got to the Recover console with the "start" and little Android guy and the white arrows. However, no matter what I press (power, up, down) nothing happens. I cannot get past this screen. Also, my pc was trying to find drivers for it and couldn't. What should I do? And is there a way to preserve anything on the phone? I have not modified the phone in any way (rooted or whatnot).
I think you cannot move between options because the bootloader is locked. Can't say 100% that's the cause of it though.
Thank you for replying. If that is the case, how do I fix that?
And after it ran out of power, I charged it again and tried starting it normally and it started. So I have no idea what is going on. However Im now afraid to restart it in fear it will be stuck on the logo again. It still runs a bit slow.
So I guess I have 2 questions:
1) If I have to load it into recovery again and no buttons work, how do I fix that?
2) Since it did start again, but runs slow, what could be going on? Any tests I can run?
Thanks!
I have a Nokia 6.1 TA-1043. I have not unlocked the bootloader, and it runs the default operating system (Android One, probably Nokia flavoured). It has gotten slower over the years, and it had a period where it crashed every now and then (sudden reboot). Anyway , some days ago I decided to reboot the phone because it was slow, and it instantly shut off. After waiting probably 20 seconds without response, I decided to hold the power button down to force it. I don't remember exactly what I did, but after trying to again hold the button down to turn it on again, it vibrated as usual but the screen remained black. I then most likely tried holding volume + and power to force another reboot, unsuccessfully. I then tried holding volume - and power to enter download mode. It might have vibrated, or I might have touched the cable making me think it vibrated, but nothing happened. I pressed some random buttons after I think.
Now, the phone does seem to charge. It gets warm when I plug in the charger. I've searched for hours on different forums, and some people say that their phone was magically resurrected after the battery went completely flat after few days. I have tried plugging the phone a bit and testing every button combination (including volume +, volume - and power at the same time) for a few days now. It's dead.
The phone is also seemingly not recognised at all on my windows 10 PC. Haven't tried on Linux.
I have a few theories:
1. The phone simply hard bricked itself due to some hardware failure.
2. I bricked the phone by (blindly due to screen being blank) entering recovery mode and unknowingly factory resetting the phone and shutting it off mid process.
3. The battery is messed up? Some suggest deconnecting the battery. It would require the use of a heat gun to even open the phone though.
I've seen some people suggest entering EDL-mode either by shorting some pins or using a modified USB-cable. However, that would either require opening a phone that isn't supposed to be opened easily, or plugging a modified USB-cable into my computer, nether of which seem safe. I've also seen people mention that whatever needs to be flashed in EDL-mode must be signed by Nokia, which I can't do obviously haha.
It's probably time to move on right? Has someone managed to get a phone in that state to work again?
Hi i can explain some of your theories:
The first one: It's impossible to make the phone hard bricked itself.
The second one: Factory reset is only wipe your data not the OS itself so if you Factory reset and force reboot it should get in to Download mode and you need to unlock bootloader to reflash the ROM. (I'm not in that situation so I'm not sure it's correct or not.)
The third one: No, I don't think so.
That's all so if you have any question ask me. Thanks!
alprtewwqfr said:
Hi i can explain some of your theories:
The first one: It's impossible to make the phone hard bricked itself.
The second one: Factory reset is only wipe your data not the OS itself so if you Factory reset and force reboot it should get in to Download mode and you need to unlock bootloader to reflash the ROM. (I'm not in that situation so I'm not sure it's correct or not.)
The third one: No, I don't think so.
That's all so if you have any question ask me. Thanks!
Click to expand...
Click to collapse
Thanks for replying My phone seems unresponsive, so I haven't managed to get in to download mode, at least not visually on the screen. Also, my phone is not recognised on PC, making me suspect it's not really turned on. I also tried holding volume up + power for 40+ minutes by stuffing it between a few books when making dinner haha, and it still didn't respond. Would you move on in this situation?
speedrocket2110 said:
Thanks for replying My phone seems unresponsive, so I haven't managed to get in to download mode, at least not visually on the screen. Also, my phone is not recognised on PC, making me suspect it's not really turned on. I also tried holding volume up + power for 40+ minutes by stuffing it between a few books when making dinner haha, and it still didn't respond. Would you move on in this situations
Click to expand...
Click to collapse
I don't know because I'm not in that situation, but I had a similar one but only boot to download mode.