Related
Hello,
Two days ago I upgraded to Gingerbread from 2.2.1, both times using Kies. I did the factory reset, CF root and put all my apps back with Titanium. No system backup was restored.
Suddenly the phone started to shut down if the screen shut down, regardless if I did a quick press on the powerbutton or let the screen time out. No lit buttons and the computer doesn't recognise the phone. The only way to start the phone was to press the powerbutton for 10 seconds. If the phone is correctly shut down you only need to press the button for approx two seconds for it to start.
I did another factory reset and the phone worked ok for a day but the problem showed up again today. EVERY single time the screen goes black the phone shuts down.
Edit:
I don't think the phone is shut down. When I call it I get a beep in the other phone as if nobody is answering. If I shut down my phone correctly and call it I get a voice that says "the number you dialed cannot be reached".
Any ideas?
I have the same problem with my phone at the moment, I have tried numerous software versions and all are the same, I think it is either a battery issue or a complete phone fault.
If it's still under warranty see if they will replace it.
You updated twice from what rom stock custom /original
Twice why ???
What network was the Kies firmware for re phones product code .
A flash through Odin to stock Froyo with pit 512 and repartition checked could well fix any faulty rom problem .
jje
ulsa said:
Hello,
Two days ago I upgraded to Gingerbread from 2.2.1, both times using Kies. I did the factory reset, CF root and put all my apps back with Titanium. No system backup was restored.
Suddenly the phone started to shut down if the screen shut down, regardless if I did a quick press on the powerbutton or let the screen time out. No lit buttons and the computer doesn't recognise the phone. The only way to start the phone was to press the powerbutton for 10 seconds. If the phone is correctly shut down you only need to press the button for approx two seconds for it to start.
I did another factory reset and the phone worked ok for a day but the problem showed up again today. EVERY single time the screen goes black the phone shuts down.
Edit:
I don't think the phone is shut down. When I call it I get a beep in the other phone as if nobody is answering. If I shut down my phone correctly and call it I get a voice that says "the number you dialed cannot be reached".
Any ideas?
Click to expand...
Click to collapse
It seems like when the device goes to sleep it cannot wake up any more. I'm getting the same problem by the way. The only way to come out of it as you mentioned already is to hold the power button for 10 seconds or pull the battery out.
My steps for upgrading from Darky's 9.5 were:
1) Odin stock JVB with bootloader (repartitioned with pit512)
2) Odin deodexed JVB without bootloader
3) Odin CF-Root
4) Applied lagfix through ext4
5) Flashed Gingerbread theme (v3 and after it v4)
6) Odin Voodoo
(with a reboot between each of the steps)
And that's about it. Have you applied any modifications or hacks?
JJEgan said:
You updated twice from what rom stock custom /original
Twice why ???
Click to expand...
Click to collapse
I did not write that very clear. I meant that both the upgrade to 2.2.1 a couple of weeks ago and the upgrade to 2.3.3 was done with Kies, not Odin.
What network was the Kies firmware for re phones product code .
Click to expand...
Click to collapse
NEE
I did another factory reset... Odin flash is next.
I updated the phone to Gingerbread with Kies.
I then rooted it with Odin (CF)
I have not done any modifications other than that.
I'm starting to think it maybe be some root app's fault. When I reinstalled using Odin to stock all was fine, then installed CF-Root, but as soon as I restored my apps it started happening again. I froze SetCPU, NoLED, and WidgetLocker, and so far nothing bad has happened. Weird. Fingers crossed that it stays this way...
martino2k6 said:
I'm starting to think it maybe be some root app's fault. When I reinstalled using Odin to stock all was fine, then installed CF-Root, but as soon as I restored my apps it started happening again. I froze SetCPU, NoLED, and WidgetLocker, and so far nothing bad has happened. Weird. Fingers crossed that it stays this way...
Click to expand...
Click to collapse
I only have SetCPU of the ones you listed.
Did you do a factory reset before you frooze those apps? If not, I guess you have found the problem.
Maybe you should try to unfreeze them one by one?
Edit: One of my settings for SetCPU was to set the CPU to 100 MHz when the screen turned off. Could be something...
I found this in another forum:
"i figured out why SetCPU makes my phone never wake up, the settings i was using was ondemand 100 min 1000 max. SetCPU is set to 100 in standby and this is just too slow and puts the phone completely to sleep.
ive since moved up the phone to 400 min and ive gone a day without any sleeping.
"
http://samsunggalaxysforums.com/showthread.php/313-i-figured-out-why-SetCPU-makes-my-phone-never-wake-up
ulsa said:
I only have SetCPU of the ones you listed.
Did you do a factory reset before you frooze those apps? If not, I guess you have found the problem.
Maybe you should try to unfreeze them one by one?
Edit: One of my settings for SetCPU was to set the CPU to 100 MHz when the screen turned off. Could be something...
Click to expand...
Click to collapse
Yes, I factory reset. But it does look like SetCPU. I unfroze WidgetLocker overnight and no problem.
I also had a 100MHz setting when the screen turned off. So I think we have found the problem I guess I'll ask Chainfire why 100MHz no longer seems to work, but it did on 2.2. I'm a bit worried about the battery now...
My phone randomly rebooted around 4 am this morning (mountain time) The only way I noticed it was I was looking at battery stats and there was a white gap or is there some other explanation for that? I have not seen this before... stock no root no unlocked bootloader.... kind of weird no?
how are we supposed to know why your phone rebooted? you provided no info besides that it rebooted around 4am. no logs, nothing. my guess is that a spaceman came and made your phone reboot, just to watch the google logo as its booting up :silly:
simms22 said:
how are we supposed to know why your phone rebooted? you provided no info besides that it rebooted around 4am. no logs, nothing. my guess is that a spaceman came and made your phone reboot, just to watch the google logo as its booting up :silly:
Click to expand...
Click to collapse
No, definitely not a spaceman... Not in mountain time
If I knew how to provide logs I would have, guess I'll check with the spacemen and see if they have them. Thanks for the help, you can close the thread......
My phone used to reboot 2-3 per day. I removed the Amazon app and it hasn't rebooted since. If you have that app installed, uninstall it.
My phone had random reboots before, but it went away.
Today i had a freeze again, before a reboot happens i cant wake my phone up . So i tired the power button like 10 times. It came back on, stayed on lock screen for 2 second and everything went black. Had to turn it back on.
Its like a deep sleep of death. I don't get notifications or anything when this happens, but my Moto 360 somehow stay connected but cant do any voice search.
This i how i usually discover the problem. When i want to do some OK Goggle with my watch and it does nothing... Checking my phone and its always dead.
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
terragady said:
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
Click to expand...
Click to collapse
Honestly, there's not enough information to understand exactly why it's happening. You need to get a logcat in the time before the reboot; unfortunately, logcats get erased during a reboot so it might be a little tricky getting it if the reboot is seemingly random. Someone had posted this as a possible way of getting the log:
"Retrieving the logs is tricky, since the log cache gets erased on reboot. If the phone reboots even while sitting on a charger, try running adb logcat continuously (you will need Android SDK and USB drivers installed and configured on your PC.) When the phone reboots, look at the last several pages in the command prompt window for any errors or abnormalities."
Click to expand...
Click to collapse
Otherwise, it's hard for anyone to help. I'm not much help in actually figuring out the issue, but I know if you can get the log, someone else probably can help.
For more information on logcats: Logcat Tutorial
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
terragady said:
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
Click to expand...
Click to collapse
Check in advanced to see if schedule off is on
Nope it's off
Happened to me to on 4.0.2. Rebooted twice a day.
Solution to me was Qualcomm flash back to stock 3.5.1 and uodate from internal to 3.5.4. OTA 4.0.2.
The theard "how to unbrick".
Not one reboot until now in days.
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
terragady said:
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
Click to expand...
Click to collapse
It's possible. Not necessarily the reason, but it might be. Either uninstall the app or freeze it using Titanium. Greenify might also work, but that allows the app to start itself up and potentially continue the issue. See if that stops the crashes for a couple of days.
The problem is that it doesn't happen often and only when I quit the game and lock the phone immediately after that. I am not sure if that's a reason though, just guessing because it happens after this last time. I will uninstall this game anyway, it's just time eater
I'm just putting this here to hopefully help someone else not lose their mind after a bad December update. I just got my OTA for my 4XL on VZW about 40 minutes ago. MY PHONE JUST BOOTED.
After applying the update and the phone restarting, per usual, I noticed the lock screen was super sluggish and intermittently not responsive. More concerning still, it said my PIN was invalid, which I KNOW it wasn't. So.... I rebooted. Just held power for a second, and clicked Restart in the menu. That may have been where I went wrong. For the next 25 or so minutes, I had nothing but a black screen. No sounds, no vibrations, nothing registered when plugging into my PC. Even holding the power key for 30+ seconds or attempting safe mode or bootloader did not work.
In retrospect, I am now considering that even though the phone initially rebooted and was at the lock screen, Android may still have been in the process of updating which could cause the slow down and maybe even the invalid pin. Mostly, I think that may be what happened when I rebooted the phone, I basically did it in the middle of it finalizing the update which very well could have caused all sorts of issues.
TLDR: I don't think I did anything to fix it, I gave up after 1000 times of trying and set it down, then about 5 minutes later (off the charger) it just started booting up. So don't throw your phone at the wall if it doesn't turn on right away after the update.
lessthanzach said:
I'm just putting this here to hopefully help someone else not lose their mind after a bad December update. I just got my OTA for my 4XL on VZW about 40 minutes ago. MY PHONE JUST BOOTED.
After applying the update and the phone restarting, per usual, I noticed the lock screen was super sluggish and intermittently not responsive. More concerning still, it said my PIN was invalid, which I KNOW it wasn't. So.... I rebooted. Just held power for a second, and clicked Restart in the menu. That may have been where I went wrong. For the next 25 or so minutes, I had nothing but a black screen. No sounds, no vibrations, nothing registered when plugging into my PC. Even holding the power key for 30+ seconds or attempting safe mode or bootloader did not work.
In retrospect, I am now considering that even though the phone initially rebooted and was at the lock screen, Android may still have been in the process of updating which could cause the slow down and maybe even the invalid pin. Mostly, I think that may be what happened when I rebooted the phone, I basically did it in the middle of it finalizing the update which very well could have caused all sorts of issues.
TLDR: I don't think I did anything to fix it, I gave up after 1000 times of trying and set it down, then about 5 minutes later (off the charger) it just started booting up. So don't throw your phone at the wall if it doesn't turn on right away after the update.
Click to expand...
Click to collapse
Were you rooted ?
reboot took longer than normal, should have left it
factory reset will clear up everything lol
prgopala said:
Were you rooted ?
Click to expand...
Click to collapse
I am not rooted. Gave up my rooting back when it made Google pay and Pokemon Go a complete ***** to use, even with magisk. So I've left this stock out of the box.
lessthanzach said:
I'm just putting this here to hopefully help someone else not lose their mind after a bad December update. I just got my OTA for my 4XL on VZW about 40 minutes ago. MY PHONE JUST BOOTED.
After applying the update and the phone restarting, per usual, I noticed the lock screen was super sluggish and intermittently not responsive. More concerning still, it said my PIN was invalid, which I KNOW it wasn't. So.... I rebooted. Just held power for a second, and clicked Restart in the menu. That may have been where I went wrong. For the next 25 or so minutes, I had nothing but a black screen. No sounds, no vibrations, nothing registered when plugging into my PC. Even holding the power key for 30+ seconds or attempting safe mode or bootloader did not work.
In retrospect, I am now considering that even though the phone initially rebooted and was at the lock screen, Android may still have been in the process of updating which could cause the slow down and maybe even the invalid pin. Mostly, I think that may be what happened when I rebooted the phone, I basically did it in the middle of it finalizing the update which very well could have caused all sorts of issues.
TLDR: I don't think I did anything to fix it, I gave up after 1000 times of trying and set it down, then about 5 minutes later (off the charger) it just started booting up. So don't throw your phone at the wall if it doesn't turn on right away after the update.
Click to expand...
Click to collapse
Hey got the same issue as you. Either it's stuck on a black screen (adb works), either it hangs on Applying update when starting the phone. Can't seem to get past this crap... I'm trying with a patched magisk image btw, not sure if it's the issue, I already applied the magisk adb commande in order to remove the magisk modules but to no avail.
Ok, so here is to explain what happened, so you can have a clue what am I talking about.
I bought Galaxy A71 a month ago (give or take), so out of the box it had Android 10. The phone was working flawlessly. Battery life awesome, pictures from camera great, etc. So, few days ago on March 26, 2021, an update to Android 11 came in. I am a tech nerd, I know about phones, rooting, flashing, etc.
So, I saw that I have around 78-80% of the battery so it was enough to download and install Android 11.
Downloading and installing and optimizing apps after went smooth as silk. I usually soft restarting my device after any software update, so I did that after the installation of Android 11 was entirely finished.
But, this is what happen when I restart my phone the normal way. I press and hold the power button, the dialog of Power off, Reset and Airplane mode came out, tapped twice the reset button and phone went restarting and just.... died. I remember that when I soft restarted my phone, the battery was on 72%. So I tried any trick in the books to turn on my phone again like combinations of pressing buttons, then with USB cable, charger, etc, but nothing was responsive. It's like the phone was clinically dead.
My phone is still under warranty and I will probably end up taking it to the T-mobile store, but the point of this thread is to inform others of the situation like mine and see if someone else had the same problem?
Maybe someone will post a solution what to do in situations like this?
If I find any solution, I will update this post with all the details.
You probably done it.But have you plugged it into A computer to see if the computer can detected it?
Essex_Hal said:
You probably done it.But have you plugged it into A computer to see if the computer can detected it?
Click to expand...
Click to collapse
Yes i did, nothing shows in Device Manager. As I said, I tried every possible trick to wake the phone up, but it was unsuccessful.
I end up taking it to the carrier store cuz it is still under warranty. They told me if they can't fix it, they'll probably give me a new one or to wait for Galaxy A72 To arrive in 2 weeks. We'll see what happens.
BorisMKD said:
Yes i did, nothing shows in Device Manager. As I said, I tried every possible trick to wake the phone up, but it was unsuccessful.
I end up taking it to the carrier store cuz it is still under warranty. They told me if they can't fix it, they'll probably give me a new one or to wait for Galaxy A72 To arrive in 2 weeks. We'll see what happens.
Click to expand...
Click to collapse
Least you still have A warranty to help you.
Good luck with it.Hope you don't lose your data if it's still on the phone.
Essex_Hal said:
Least you still have A warranty to help you.
Good luck with it.Hope you don't lose your data if it's still on the phone.
Click to expand...
Click to collapse
They fix it, it said it was software problem, got stuck on rebooting. I get it today (2 weeks later) and it worked. They managed to turn it on but without a factory reset, every app was there, every picture, video, contacts, call history, etc. I don't know how they did it, but they did. So when I got my phone back I tried to restart it normal way, long press of the power button, then tap Restart and again restart. The phone restart it without a problem. I was happy. Then later that day (2 hours ago when I'm writing this, I notice that always on display when i touch the phone screen will show up but doesn't switch off after 10 seconds (I set it up like that), instead it started to blink in intervals like i was touching the screen continuously. Then I did a deep soft reset. You know, when you press Volume down and Power button at the same time and.... got the same problem again. Phone is non functional, none combination of pressing buttons worked, just like i describe it in the OP. Just for information, I did the same on my previous phone Galaxy A7 2018 and never had this problem. I did it on this phone too, never had a problem. Then I remember it that on both phones when i do that and not having problems were running on Android 10. this phone now update it to Android 11 and that buttons combination is probably bricking the phone. It's just a thing I notice. So I am planning to call the official service that fixed the phone how did they do it, so maybe I can do it myself too. I don't want to wait for another 2 and a half weeks.
I am facing the same issue. And I think my warranty is out. Did you get to ask them how can you turn it on yourself!!
I would really appreciate some help here!
BorisMKD said:
Ok, so here is to explain what happened, so you can have a clue what am I talking about.
I bought Galaxy A71 a month ago (give or take), so out of the box it had Android 10. The phone was working flawlessly. Battery life awesome, pictures from camera great, etc. So, few days ago on March 26, 2021, an update to Android 11 came in. I am a tech nerd, I know about phones, rooting, flashing, etc.
So, I saw that I have around 78-80% of the battery so it was enough to download and install Android 11.
Downloading and installing and optimizing apps after went smooth as silk. I usually soft restarting my device after any software update, so I did that after the installation of Android 11 was entirely finished.
But, this is what happen when I restart my phone the normal way. I press and hold the power button, the dialog of Power off, Reset and Airplane mode came out, tapped twice the reset button and phone went restarting and just.... died. I remember that when I soft restarted my phone, the battery was on 72%. So I tried any trick in the books to turn on my phone again like combinations of pressing buttons, then with USB cable, charger, etc, but nothing was responsive. It's like the phone was clinically dead.
My phone is still under warranty and I will probably end up taking it to the T-mobile store, but the point of this thread is to inform others of the situation like mine and see if someone else had the same problem?
Maybe someone will post a solution what to do in situations like this?
If I find any solution, I will update this post with all the details.
Click to expand...
Click to collapse
have same issue too anyways to fix it?