Database Develop

[Q] phone will not power off or on properly. Shut down menu pops up constantly

I have searched this exact title and came up with 10 pages and I never saw anyone else with this problem. Surely I cannot be the only one.
After the Gingerbread upgrade I was getting the tethering message/force close, during that time my phone started to randomly shut off ( settle down Beavis, this isn't the same question thats been asked a thousand times ) and reboot. I lived with the tethering message problem for as long as I could but my phone became more ignorant day by day. I finally found a fix for the tethering issue and haven't had a return problem with that but now my phone either stays in standby mode ( dark screen ) and refuses to respond to the hard button to wake it up OR once on it refuses to go into standby mode and stays on until I pop the battery or I go into settings and time the screen out in 15 seconds ( often times this doesn't shut it down either ). Sometimes I can get it to come on by multiple pressing the power button ( this can't be healthy ) and the lock screen will flash momentarily just long enough for me to unlock the screen. Other times it will go to the lock screen while I'm in the middle of something.
Every day at some point while it's on and I'm using it, the power button option screen pops up ( silent mode, flight mode, power off ). When I'm done with a call I try to go into standby and it just sets there...ON.
The thought has crossed my mind that the button doesn't work or has a short but I really think it's something else ( I hope ). Can somebody help me? I am not very techie although I have updated the phone three times myself. It is unrooted and 2.3.5
Thank you in advance

I would go with the power button. It's a known issue on captivate.

mrhaley30705 said:
I would go with the power button. It's a known issue on captivate.
Click to expand...
Click to collapse
I stopped by the AT&T store the other day to check on insurance (ends up I didn't have it) and told them about my button not working properly and how the Captivate was notorious for this problem and they all said "We've never heard that". So the gadget gal is in there so she offers to take it apart and check it. She claims there isn't anything wrong with it and that it has the same amount of spring as the volume buttons. She then noticed that when she put the battery back in the phone came on automatically, I said it's not supposed to do that and she agreed but fortunate for me since I cannot turn it on. She then says I'm eligible for an upgrade and try's to sell me a new phone. I don't want a new contract.
So should I try and buy a new button and change it or could it be something else? Thank you in advance.

Are you using a case for your phone by any chance? If yes, is it too tight? Maybe the power button gets stuck because of that sometimes? Just a long shot! You stated that power menu pops up once in awhile when you're using it, is it possible that the way you grip the phone causes that? (Just trying to help and not trying to offend you btw.)
You might want to try flashing UCKK4 with bootloader(use it from the one click master collection of stock rom's) just to make sure that there is no issue with the firmware. It is not likely to fix your problem but it's good to have a clean start. At least that's what I would do to begin with.
Since you're willing to change the power button, why not do an experiment? Remove the power button and see if there is any change? If it works fine then it's the power button that's faulty else it's a hardware problem.

[Q] Samsung Galaxy S GT-I9000 won't work if not plugged on external power source

Hi guys,
The following problem has taken me litterally DAYS of reading XDA, trying everything I could, but still no solution. Googling and searching this forum didn't help either, and it's totally weird.
It's a Samsung Galaxy S GT-I9000, on which were installed, almost two years ago, the ClockWorkMod recovery, Darky's ROM, Froyo, and everything was fine for months. Then, one day, out of nowhere, it switched off, without notice. Impossible to switch it on again! I remembered having seen some strange battery behavior few days before, like falling from 80% to 30% with no reason, so I thought of a battery issue. I plugged it for a full night. In the morning, I was able to boot it, but not easily, and all apps were crashing: during boot, or when launched manually. Yes, all I tried were crashing! Then, the phone became fully not bootable: press the power button, the screen shows "Samsung GT-I9000", then switches off...
I ordered a new battery: same result.
A guy from a phone repair store told me to plug the phone, and keep the power button down for 2 minutes: after this, I could reboot the phone, and thus, wipe data (factory reset). But it didn't help.
After "playing" a bit with it, I realized that the problem is:
the phone won't boot if an external source of power is not connected (as said above, white text shows, then the phone "dies")
if started with power cord/usb, the phone will work fine, all the time
if started with power cord/usb, and the external power source removed once the phone is booted, the phone will work fine, UNTIL the screen goes black for power saving mode or by pressing pwoer button, after which, within seconds, you can't open the phone anymore. I mean: if you press the start/power button immediately after the screen goes black, the screen goes on again, and the phone is ok. If you wait for few seconds, it's over, you can't do anything, and have to reboot the phone. This said, the phone doesn't vibrate, so I suppose it's not really off. But then... what is this state??
I really tried my best: updated to GB2.3.6, bricked my phone trying to re-install the CWM and having a bootloop, installed and used Odin and Heimdall, reverted to stock kernel, etc, etc, etc.
I feel sorry to bother you guys, I was really convinced that with the incredibly huge amount of data, how-tos, explanations, etc. I would manage to get rid of this, but this problem, though I don't really think it's hardware (but maybe it is?) stayed across so many kernels, roms, etc. that it's killing me!
For the record:
Model number: GT-I9000
Micro-software (?): 2.3.6
Baseband: I9000XXJW4
Kernel: 2.6.35.7-I9000XWJW7-CL1125830 [email protected] #2 (problem was the same with [email protected] #2)
Version number: GINGERBREAD.XXJW4
Any help would be greatly appreciated, considering that a wireless phone that needs to be wired is a little bit of an issue... :laugh:
Thanks in advance !

Marc_B_ said:
Hi guys,
The following problem has taken me litterally DAYS of reading XDA, trying everything I could, but still no solution. Googling and searching this forum didn't help either, and it's totally weird.
It's a Samsung Galaxy S GT-I9000, on which were installed, almost two years ago, the ClockWorkMod recovery, Darky's ROM, Froyo, and everything was fine for months. Then, one day, out of nowhere, it switched off, without notice. Impossible to switch it on again! I remembered having seen some strange battery behavior few days before, like falling from 80% to 30% with no reason, so I thought of a battery issue. I plugged it for a full night. In the morning, I was able to boot it, but not easily, and all apps were crashing: during boot, or when launched manually. Yes, all I tried were crashing! Then, the phone became fully not bootable: press the power button, the screen shows "Samsung GT-I9000", then switches off...
I ordered a new battery: same result.
A guy from a phone repair store told me to plug the phone, and keep the power button down for 2 minutes: after this, I could reboot the phone, and thus, wipe data (factory reset). But it didn't help.
After "playing" a bit with it, I realized that the problem is:
the phone won't boot if an external source of power is not connected (as said above, white text shows, then the phone "dies")
if started with power cord/usb, the phone will work fine, all the time
if started with power cord/usb, and the external power source removed once the phone is booted, the phone will work fine, UNTIL the screen goes black for power saving mode or by pressing pwoer button, after which, within seconds, you can't open the phone anymore. I mean: if you press the start/power button immediately after the screen goes black, the screen goes on again, and the phone is ok. If you wait for few seconds, it's over, you can't do anything, and have to reboot the phone. This said, the phone doesn't vibrate, so I suppose it's not really off. But then... what is this state??
I really tried my best: updated to GB2.3.6, bricked my phone trying to re-install the CWM and having a bootloop, installed and used Odin and Heimdall, reverted to stock kernel, etc, etc, etc.
I feel sorry to bother you guys, I was really convinced that with the incredibly huge amount of data, how-tos, explanations, etc. I would manage to get rid of this, but this problem, though I don't really think it's hardware (but maybe it is?) stayed across so many kernels, roms, etc. that it's killing me!
For the record:
Model number: GT-I9000
Micro-software (?): 2.3.6
Baseband: I9000XXJW4
Kernel: 2.6.35.7-I9000XWJW7-CL1125830 [email protected] #2 (problem was the same with [email protected] #2)
Version number: GINGERBREAD.XXJW4
Any help would be greatly appreciated, considering that a wireless phone that needs to be wired is a little bit of an issue... :laugh:
Thanks in advance !
Click to expand...
Click to collapse
That's a very strange problem... let's try something, remove the battery, sim card and sd card and hold the power button for 1-2 minutes, btw when the screen is off, is really the phone off or just the screen? did you try to make a call to your phone when the screen is off?

timberman4444 said:
That's a very strange problem... let's try something, remove the battery, sim card and sd card and hold the power button for 1-2 minutes, btw when the screen is off, is really the phone off or just the screen? did you try to make a call to your phone when the screen is off?
Click to expand...
Click to collapse
Hi timberman thanks for the answer!
You're very right: I totally forgot to say that what initially allowed me to restart my phone "regularly" was this procedure of pressing the power button for 2 minutes (hint given by a man from a repair shop). Before this, I couldn't (kind of a bootloop).
It's a very good question! I don't think the phone is really off in fact, because there isn't this vibration saying the phone turned off... Let me try to call it!
F..k! I was redirected right away to the voicemail... so... phone was off
I'm starting to think it's an harware issue... I reinstalled lots of ROMs, kernel, etc. Same ****...
Any idea?

Marc_B_ said:
Hi timberman thanks for the answer!
You're very right: I totally forgot to say that what initially allowed me to restart my phone "regularly" was this procedure of pressing the power button for 2 minutes (hint given by a man from a repair shop). Before this, I couldn't (kind of a bootloop).
It's a very good question! I don't think the phone is really off in fact, because there isn't this vibration saying the phone turned off... Let me try to call it!
F..k! I was redirected right away to the voicemail... so... phone was off
I'm starting to think it's an harware issue... I reinstalled lots of ROMs, kernel, etc. Same ****...
Any idea?
Click to expand...
Click to collapse
Hi mark, i'm totally out of ideas for your problem... anyway, maybe you read mi answer wrong, in your post you say that the guy in the repair shop tell yo to press the power button with THE PHONE PLUGGED IN, but what i say is press the power button 2 minutes WITHOUT BATTERY, btw i keep thinking about this.. if any idea comes to my mind i tell you.

Hi again, try to play a song and turn the screen off to see what happens.
Sent from my GT-I9000 using xda app-developers app

timberman4444 said:
Hi mark, i'm totally out of ideas for your problem... anyway, maybe you read mi answer wrong, in your post you say that the guy in the repair shop tell yo to press the power button with THE PHONE PLUGGED IN, but what i say is press the power button 2 minutes WITHOUT BATTERY, btw i keep thinking about this.. if any idea comes to my mind i tell you.
Click to expand...
Click to collapse
Hi! Answering is already nice
I tried the button pressed for 2 minutes without battery: didn't change anything.
I tried playing a sound: MAN, YOU'RE A GENIUS!!! Launching the music, then forcing the screen off with power button lets the music play, and OF COURSE, I can reactivate the screen by pressing the home button. The screen goes off normally again after few seconds, but the music is still playing, etc. So, as long as the music goes, the bug doesn't happen!
Other hints:
For some time already, when I was removing the phone from my ear after a call, quite often, the screen was staying off, and I had to press a lot of buttons to have it on again, and be able to close the call
The moment where it crashes when booting without power is the very INSTANT where the initial white text (Samsung Galaxy S) goes brighter. So, if you unplug the power cord just after this, the boot ends normally. In summary, something happens at boot just after screen brightness changes which is the same thing happening when the screen goes off for power saving. All this, only when no external power is plugged.
Hehe, we (you) are making progress

Marc_B_ said:
Hi! Answering is already nice
I tried the button pressed for 2 minutes without battery: didn't change anything.
I tried playing a sound: MAN, YOU'RE A GENIUS!!! Launching the music, then forcing the screen off with power button lets the music play, and OF COURSE, I can reactivate the screen by pressing the home button. The screen goes off normally again after few seconds, but the music is still playing, etc. So, as long as the music goes, the bug doesn't happen!
Other hints:
For some time already, when I was removing the phone from my ear after a call, quite often, the screen was staying off, and I had to press a lot of buttons to have it on again, and be able to close the call
The moment where it crashes when booting without power is the very INSTANT where the initial white text (Samsung Galaxy S) goes brighter. So, if you unplug the power cord just after this, the boot ends normally. In summary, something happens at boot just after screen brightness changes which is the same thing happening when the screen goes off for power saving. All this, only when no external power is plugged.
Hehe, we (you) are making progress
Click to expand...
Click to collapse
Hi again, it seems like your phone is unable to exit the deep sleep mode or something like that so, let`s try another thing, in ICS or JB there´s an option in the developer option settings that unfortunately is not present in gingerbread roms, so, you can try to switch to a ICS/JB rom and go to settings-developer options and disable the "PM sleep mode" let`s see what happens then

timberman4444 said:
Hi again, it seems like your phone is unable to exit the deep sleep mode or something like that so, let`s try another thing, in ICS or JB there´s an option in the developer option settings that unfortunately is not present in gingerbread roms, so, you can try to switch to a ICS/JB rom and go to settings-developer options and disable the "PM sleep mode" let`s see what happens then
Click to expand...
Click to collapse
I tried to install ICS, with a GREAT tutorial found here: http://forum.xda-developers.com/showthread.php?t=1494493 Sadly, the phone reboots after installing the ICS kernel, and then doesn't work anymore, I had to reinstall the Gingerbread (I tried twice).
Last news: I let the phone play music (sound muted!!) for about 12 or 18h: all was fine! So I decided to pause the music, and see what happens. Boom ((c) Steve Jobs)!! The screen went black, and phone was "dead". I was expecting this, so no panick, I put back my SIM card, my SD card, and tried to reboot, with power cord plugged: it boots until the screen shows the small loader animation, then the empty battery image, but then goes black again, instead of showing the charging battery!! Download mode is still available, so I'll try to reflash the kernel, say.
It's like if each time screen was put black, phone was dying.
I can't stress enough how I appreciate your help: even if we can't save my phone, it's very pleasant to be able to TRY things. Thanks man!! :good:
Update: I reinstalled all... and it's not, even with power cord in, going further than the "Samsung Galaxy S" white text. The moment this picture disappears from screen, phone is dead. For good this time ?

Marc_B_ said:
I tried to install ICS, with a GREAT tutorial found here: http://forum.xda-developers.com/showthread.php?t=1494493 Sadly, the phone reboots after installing the ICS kernel, and then doesn't work anymore, I had to reinstall the Gingerbread (I tried twice).
Last news: I let the phone play music (sound muted!!) for about 12 or 18h: all was fine! So I decided to pause the music, and see what happens. Boom ((c) Steve Jobs)!! The screen went black, and phone was "dead". I was expecting this, so no panick, I put back my SIM card, my SD card, and tried to reboot, with power cord plugged: it boots until the screen shows the small loader animation, then the empty battery image, but then goes black again, instead of showing the charging battery!! Download mode is still available, so I'll try to reflash the kernel, say.
It's like if each time screen was put black, phone was dying.
I can't stress enough how I appreciate your help: even if we can't save my phone, it's very pleasant to be able to TRY things. Thanks man!! :good:
Update: I reinstalled all... and it's not, even with power cord in, going further than the "Samsung Galaxy S" white text. The moment this picture disappears from screen, phone is dead. For good this time ?
Click to expand...
Click to collapse
you tried to install the rom on the recovery instead of odin?

timberman4444 said:
you tried to install the rom on the recovery instead of odin?
Click to expand...
Click to collapse
Hi! No, I didn't, I used Odin. But now, I can't try anything anymore The only "results" I can get from this phone are:
- enter download mode and update from Odin (maybe from Heimdall, too, but I didn't check)
- reboot until the first moment the screen goes black, after which, the phone becomes fully unresponsive

Marc_B_ said:
Hi! No, I didn't, I used Odin. But now, I can't try anything anymore The only "results" I can get from this phone are:
- enter download mode and update from Odin (maybe from Heimdall, too, but I didn't check)
- reboot until the first moment the screen goes black, after which, the phone becomes fully unresponsive
Click to expand...
Click to collapse
so, you can`t install any rom at the moment?

timberman4444 said:
so, you can`t install any rom at the moment?
Click to expand...
Click to collapse
I can! I can install any kernel, or ROM, trhough Odin, but I can't boot at all... Except if someone has a magical trick, I would say it smells like coffin...

Marc_B_ said:
I can! I can install any kernel, or ROM, trhough Odin, but I can't boot at all... Except if someone has a magical trick, I would say it smells like coffin...
Click to expand...
Click to collapse
Pretty bad signals there.. i think you should go to a repair shop or buy another device

timberman4444 said:
Pretty bad signals there.. i think you should go to a repair shop or buy another device
Click to expand...
Click to collapse
Sadly, yes... thanks for helping however !

[Q] [HELP] Something is SERIOUSLY wrong with my Moto G(boot loop)

So. My Moto G is completely un modded, not rooted, and is exactly stock how I bought it and haven't changed any of the software. My Moto G has been getting slower in the past couple of months with everything going slower than usual. I bought my phone in February 2014.
Yesterday while I was at school, in my pocket I had my phone. I felt random vibrations in timed cycles. So I pulled out my phone and had a lol at it randomly rebooted but came back to the home screen. As I started to use it just to send a couple of messages it rebooted again but this time after the reboot animations they just went on and on, what I've found out to be called a boot loop.
So I went home did some research and figured I would have to factory reset. I couldn't get into the phone therefore I had to do it externally. I got the the menu thing ( I think it's called fast boot menu ) and I wanted to select newer bootup or power up just to see if that would possibly stop the boot loop. I selected it and got into my phone, into setting and factory erased my phone.
Well I factory erased my phone and re installed the apps I on,y essentially use or NEED such a social media, within this time there was no unusual activity. Shortly after my phone randomly rebooted ( after downloading the apps ) and turned off, and then went in to the former boot loop! I was furious!
Well here I am, left it overnight for charge and it's been looping for 10 hours. I tried going back into the fast boot menu, the first time I got into it this morning I selected recovery in hope to reset it, however the screen said no command with the android and the exclamation point. The second time I got into the menu I tried 'Factory' and it just rebooted and back into the cycle.
At one point I did get into my phone however shortly after that guess what happened, it turned off and rebooted. And back into the vicious cycle.
I am led to believe it's the power button that's causing the problem ( correct me if I am wrong ) as when I did manage to get I to the phone I did try pressing the power button to investigate this and on some occasions in did lock the phone but in several others it displayed the power off popup and then turned off shortly after indicating that I was holding the button down which I definitely wasn't doing.
So where would I go from this? Do I call Motorola, try flashing a stock ROM ( it's completely stock ATM , I don't know how to do this so if I have to do this can you please explain briefly ) or try going back into the fast boot and go into recovery and try and get rid of no command ( if I can, and how ? ).
Please any help would be very appreciated!
Thanks in advance.
PS you don't think it's the back cover that's doing it because it took that off last night '

kevlarpatel said:
Do I call Motorola, try flashing a stock ROM
Click to expand...
Click to collapse
Since your phone is completely stock, don't start tempering with it now. Just return the phone. But you have to act quick, warranty is about to expire.

doppelhelix said:
Since your phone is completely stock, don't start tempering with it now. Just return the phone. But you have to act quick, warranty is about to expire.
Click to expand...
Click to collapse
Hi, I had a look online and came across a forum post saying it was a jammed or sticky power button and the poster stated to hit the power button side of the phone on a desk a couple times and it will go back to normal. I'm glad to say it did work after I hit it a couple times, as fast as ever now due to the reset!
I was wondering if I call Motorola would they give me a free new moto g out of it, as I see it as an opportunity to do so, or will they just prompt me to send it so they can repair it under warranty? Is it worth calling ?

[Q] Random freezes with Lollipop, I can only reboot the phone

Good evening.
I just can't take it anymore. After updating to Lollipop 1 month ago, at least once a day my phone freezes completely and I can only reboot it.
Most of the time, it happens when I unlock the phone to answer a whatsapp message. When the chat appears, the phone stop responding. It also happen in random cases, but usually just after I have unlocked the phone.
If I press the lock button, the screen goes black and never turn on. If I longpress the button, the screen to reboot or shut down the phone shows up, but not the background or any other app.
After upgrading from Kitkat, I did a factory reset from the menu. With KitKat this Z3C was the best phone I ever had, but now I hate it.
Is there a way to solve this problem?
Thanks in advance.

Nobody? Maybe have I to install again Lollipop?

Alan Slade said:
Nobody? Maybe have I to install again Lollipop?
Click to expand...
Click to collapse
I have exactly the same issue. It happened 3 times in 2 weeks, not so often but still annoying. I bought the phone two weeks ago and it was already with lollipop...
https://www.dropbox.com/s/j2ww4vqusxgnijw/Screenshot_2015-06-25-22-34-06.png?dl=0
https://www.dropbox.com/s/34syos0lyua5rz7/Screenshot_2015-06-25-22-42-40.png?dl=0
I've discovered that going in full screen mode with power toggles widget I can enter the settings and do whatever I want, but as soon as I exit (even if I just pull down the notification drawer only) it goes back with black screen and only the back key, which is not responding.
Is a Lollipop bug or should I send back the phone to the seller? Factory reset could help, even if it was new?

Alan Slade said:
Good evening.
I just can't take it anymore. After updating to Lollipop 1 month ago, at least once a day my phone freezes completely and I can only reboot it.
Most of the time, it happens when I unlock the phone to answer a whatsapp message. When the chat appears, the phone stop responding. It also happen in random cases, but usually just after I have unlocked the phone.
If I press the lock button, the screen goes black and never turn on. If I longpress the button, the screen to reboot or shut down the phone shows up, but not the background or any other app.
After upgrading from Kitkat, I did a factory reset from the menu. With KitKat this Z3C was the best phone I ever had, but now I hate it.
Is there a way to solve this problem?
Thanks in advance.
Click to expand...
Click to collapse
I'm trying to see if a factory reset may help, I'll let you know...

luxpast said:
I'm trying to see if a factory reset may help, I'll let you know...
Click to expand...
Click to collapse
Thanks a lot

Alan Slade said:
Good evening.
I just can't take it anymore. After updating to Lollipop 1 month ago, at least once a day my phone freezes completely and I can only reboot it.
Most of the time, it happens when I unlock the phone to answer a whatsapp message. When the chat appears, the phone stop responding. It also happen in random cases, but usually just after I have unlocked the phone.
If I press the lock button, the screen goes black and never turn on. If I longpress the button, the screen to reboot or shut down the phone shows up, but not the background or any other app.
After upgrading from Kitkat, I did a factory reset from the menu. With KitKat this Z3C was the best phone I ever had, but now I hate it.
Is there a way to solve this problem?
Thanks in advance.
Click to expand...
Click to collapse
Like you i didnt like lollipop, if you want to revert back to Kitkat like i have done read HERE
Hope this helps you out.

note 8 sxreen crash after reboot - possible issue with 9.0 beta

Hi guys
Just a quick one. Got a strange issue with the screen on my note 8 and just seeing if anyone has had the same issue or any idea on a fix.
Last week updated to the 9.0 beta and all seemed to be going well with no notable issues just a bit of lag here and there. However last night I turned my phone off and when I came to turn it back on this morning it started to boot as normal I entered my password successfully and it started to boot. As soon as the password registered and the unlocking pad lock appears it quickly shifts to the bottom right hand corner instead of the centre as normal. The phone continues to boot and from then on the screen just goes black and is unresponsive. The handset is on cause people can still ring, notifications still get received and all the hardware buttons make noise as if they are working. The screen will just not turn on. If I try doing a soft reboot with the power and volume down I can start the phone and the Samsung logo comes up as normal and the pin screen as normal but as soon as I enter my pin the same issue happens. If I hold the power button on its own to turn off the phone the multi menu (reboot, power off, emergency) all briefly appear but are enlarged and sitting on the right of the screen.
Any ideas guys, cheers.

Try reinstalling Oreo back onto it. It could be an issue with the Beta Version of Pie that you installed on your device.

The beta software is intended for this very purpose, you found a problem, then you report it to the releaser to be fixed, the creators of the software are the ones that will evaluate and improve the software, you see, it did not work for you, just try to reinstall it, if the issue persists, provide feedback to samsung, and flash a stable firmware

Possibly this bug Pie Beta + Secure Startup + WQHD = Black Screen?

It happened to me too. I installed over my existing UAE firmware with Indian one then the one ui update. After reboot got the same blank screen issue. I then did a factory reset and everything is back to normal for the last couple of days with improved battery life probably due to the reason that many region specific Samsung app like Samsung pay doesn't work.

So had a bit more of a play when I got chance and I managed to resolve the issue. Still being hit with the same problems for some reason I tried unlocking the phone again but sideways (don't ask not sure why) and the screen unlocked. From then on phone worked completely normal until next reboot. Same thing every time until I hold phone on its side and unlock with the fingerprint reader.
I've since reverted back to 8.0 and sent feedback over. I'm gonna try testing again weekend see if I have same luck.
Cheers for the replies guys, hope anyone else has this issue the comes across this.

you must disable secure start up

I had the same issue after updating to beta 1 with secure boot enabled. I wiped the phone and it started as it should, since I couldn't unlock the phone even with fingerprint. I noticed that the screen was only showing for few seconds the 1/4 of the image (unlock sim with PIN).