Related
Some of us are having problems with our Captivate randomly shutting down. AT&T technical support thinks it could be apps that we've installed. Could they be right? My replacement device didn't start shutting down again after 3-4 days of owning it. By that time, I have already installed some favorite apps. Here's my list. Let's compare and figure this out. It's just a theory. Can't hurt.
<<<< OMG! While typing this new thread to turn on my phone so I can see the list of apps I have installed, MY PHONE TURNED OFF ON ME! WHAT THE...!!! >>> Anyway...
Apps installed:
-SMS Back Up and Restore
-Yahoo! Mail for Android
-Adobe Reader
-XDA-Developers
-Market History Manager
-Speedtest.net
-Google Maps
Mine never did it until I set advanced tag killer to harsh every half hour. I watered down the harshness a little bit and it hasn't shut off since
Sent from my SAMSUNG-SGH-I897 using XDA App
Theres a thread in the vibrant section that's about the same problem and it happens after 3 days could try there
Sent from my Nexus One using XDA App
Thanks. I just posted on an existing thread over there. I will do a hardware master reset later and observe again the next 3-4 days. Samsung gave me the directions. (Hold the volume up and down plus the power button, all 3 buttons for 15 seconds, etc.)
most are saying that its bad RAM/memory and exchanging the handset fixed all the problems
andy2na said:
most are saying that its bad RAM/memory and exchanging the handset fixed all the problems
Click to expand...
Click to collapse
Is there a memtest type application for android? Bad memory would make sense, but so would a number of other theories.
Ur welcome hope it helps and u get it figured out
Sent from my Nexus One using XDA App
RexEscape said:
Thanks. I just posted on an existing thread over there. I will do a hardware master reset later and observe again the next 3-4 days. Samsung gave me the directions. (Hold the volume up and down plus the power button, all 3 buttons for 15 seconds, etc.)
Click to expand...
Click to collapse
Yeah, that's their answer for all problems, big and small. I'm sure in some cases it's valid, but the reset is used more as a "what the hell' reply rather than a knowledge-based solution.
Jack45 said:
Yeah, that's their answer for all problems, big and small. I'm sure in some cases it's valid, but the reset is used more as a "what the hell' reply rather than a knowledge-based solution.
Click to expand...
Click to collapse
...which I agree to some point. Some users just end up loading crap on devices which screws things up (some of the apps mentioned above might be crap, or not, not sure, it's only a theory. Of course, a perfect device is a unit that can withstand ANY apps you feed to it. But we don't have THE perfect device (yet, or ever).
I will do the hardware master reset in a few minutes and not load anything for 3-4 days (but I will enter my Gmail account and let it sync with my Contacts, Calendar, and Email, but that's it...for now).
RexEscape said:
...which I agree to some point. Some users just end up loading crap on devices which screws things up (some of the apps mentioned above might be crap, or not, not sure, it's only a theory. Of course, a perfect device is a unit that can withstand ANY apps you feed to it. But we don't have THE perfect device (yet, or ever).
I will do the hardware master reset in a few minutes and not load anything for 3-4 days (but I will enter my Gmail account and let it sync with my Contacts, Calendar, and Email, but that's it...for now).
Click to expand...
Click to collapse
What steers me away from the app theory is that there have been several posts indicating that the random shutdowns have occurred with a stock device. No apps downloaded / installed.
I don't have an answer except to say that the master reset can't hurt. Realistically, though, if you go a few days without a shutdown don't sit back and smile like the Cheshire Cat. Sometimes the shutdowns occur weeks into ownership. I'm not being negative, just realistic.
I wish you well.
Jack45 said:
What steers me away from the app theory is that there have been several posts indicating that the random shutdowns have occurred with a stock device. No apps downloaded / installed.
I don't have an answer except to say that the master reset can't hurt. Realistically, though, if you go a few days without a shutdown don't sit back and smile like the Cheshire Cat. Sometimes the shutdowns occur weeks into ownership. I'm not being negative, just realistic.
I wish you well.
Click to expand...
Click to collapse
Agreed. Like I said, this is my second device and the shutdowns didn't start until 3-4 days after ownership on both devices. The reality (for me) is that the Captivate isn't so great after all after two devices already (sorry to say) but I'm not going to give up just yet. I have until the 31st to decide whether I will continue this 30-day early upgrade trial or take it back and continue to use my HTC Fuze and just let my contract expire (in October). If I take it back, come October, I will decide whether I will stay with AT&T and take on another (hopefully bug-free) Captivate, or move to Verizon and check out their Android phones -- HTC and Motorola devices!
I just did a hardware master reset. It isn't exactly a hardware master reset like the tech guy described it. He gave me the directions to "delete user data". It deleted the apps that I have downloaded from the Market, and other things. I don't know what else. However, when it booted up again, I noticed my settings and widgets are still there. My homescreen was still customized the way I had it. So, it's not a total master reset. The software Factory Reset isn't also a total (software) reset. I did that and found some folders left in my internal memory (not my external MicroSD) from the previous working session. Hmm..
my captivate started to shutdown about five days ago. it's been doing it once a day, always in the morning. i wonder if it has something to do with the power management. the phone is always charged overnight and the shutdowns always seem to happen about an hour or so after i unplug it from the charger.
the one day it didn't shut down, i noticed that the lock screen was unresponsive (ie i couldn't unlock the phone) and i ended up having to power down the phone anyway.
vksf01 said:
my captivate started to shutdown about five days ago. it's been doing it once a day, always in the morning. i wonder if it has something to do with the power management. the phone is always charged overnight and the shutdowns always seem to happen about an hour or so after i unplug it from the charger.
the one day it didn't shut down, i noticed that the lock screen was unresponsive (ie i couldn't unlock the phone) and i ended up having to power down the phone anyway.
Click to expand...
Click to collapse
exactly how it happens on mine.
i'll see what happens over the rest of the week and then try the master reset. if it still happens, i'm going to return this for another one. unfortunately, i've had it for over 30 days.
vksf01 said:
i'll see what happens over the rest of the week and then try the master reset. if it still happens, i'm going to return this for another one. unfortunately, i've had it for over 30 days.
Click to expand...
Click to collapse
Even after 30 days, you will still be able to return it (maybe to Samsung) for repair or a replacement. Good luck.
vksf01 said:
my captivate started to shutdown about five days ago. it's been doing it once a day, always in the morning. i wonder if it has something to do with the power management. the phone is always charged overnight and the shutdowns always seem to happen about an hour or so after i unplug it from the charger.
the one day it didn't shut down, i noticed that the lock screen was unresponsive (ie i couldn't unlock the phone) and i ended up having to power down the phone anyway.
Click to expand...
Click to collapse
Mine has shut down twice, and I've only had it for 12 days. As you described, it happened both times in the morning, following a recharge.
I had to remove and replace the battery to get it to turn back on, is that the same thing that happened to you? I mean to say, did you have to remove and replace the battery to get it to work again?
The two Captivates I've owned (and returned due to a combination of GPS and Random Shut Downs) have shut down on me even in the middle of the day (not only in the morning after recharging for the night). It shut down on me while getting my afternoon coffee. I was showing the phone to the Barista, set the phone down on the counter to pay, picked it up, walked back to my office and just when I'm about to wake it up, it does the bootup. It also shut down on me at night while walking in the dark. I noticed my pocket lit up. I pulled out my phone and I saw the Shut Down screen as if you had pressed and held the power button (but nothing else was in my pocket that could have pressed the button!).
Random, I tell ya. Random.
pmpntl said:
exactly how it happens on mine.
Click to expand...
Click to collapse
Larry202br said:
Mine has shut down twice, and I've only had it for 12 days. As you described, it happened both times in the morning, following a recharge.
I had to remove and replace the battery to get it to turn back on, is that the same thing that happened to you? I mean to say, did you have to remove and replace the battery to get it to work again?
Click to expand...
Click to collapse
no, i just turned it back on using the power button.
I just wanted to chime in to say that I am having the same problem. Random shutdowns, not necessarily related to charging. Often they are in the morning however. For me it has been happening a few times a day. Likewise, it seems to have not happened at first, but began a few days ago (I have owned the phone about 2 weeks.)
Are you guys rooted? I have tried unrooting to see if that matters. I don't know why it would, but perhaps...
My two months old Nexus S started to behave in a way that renders it pretty much useless - Freezing / Locked U
Freeze/Delay Between Menu and basically the phone is dead.
Very often when the screen is off, pressing power button powers up the screen with the screen lock, but the phone is not responsive so the screen just goes off again as it is impossible to slide to unlock it.
On top of that, leaving the phone with the screen off for a half an hour or so brings up some sort of warning sign and a small android (can see the screen shot here: http://yfrog.com/h3apmgqj) and the phone is effectively dead. The only thing to do in any of the two cases is remove and reinsert the battery, but that is no solution to anything. All this is while the battery is fully charged.
Did anyone experienced this before? resetting phone does not help.
Here is more info on this topic: http://www.google.com/support/forum/p/Google+Mobile/label?lid=4e31a500f89fe575&hl=en
Are you using a custom recovery/ROM? That icon you posted isn't the stock image
Hi, no I do not - the image is actually from different phone but it looks exactly as it did on my Nexus S (little green guy with an exclamation mark). I never rooted my phone or done any custom mods to its system.
I actually sent it to Samsung and they are claiming that they found no problem, so they re-flushed the phone and are sending it back. I am seriously angry at samsung. It is arriving on the 11th so I'll let you know if that helped but I doubt it.
I believe this might be a faulty memory because I often received notification that the internal storage was unavailable or something of that nature as well, right before the problem would occur. Are the any tests I could perform for memory / storage?
just try to flash it back to stock
then do wipe data and wipe cache
see if that gets it back on its feet
Hey,
thank you, I thank that means I would have to root it first ehhh
Samsung told me they've done just that (flashed phone) so I am seriously hoping that my phone will work when it arrives on the 11th.
thanks!
Samsung supposedly is looking into this problem, please see link below:
http://www.google.com/support/forum...ad?fid=44db6d8e31129d4c00049e3b2a6db4d1&hl=en
Update:
I just received my phone from Samsung repair and of course, the phone is NOT fixed. On the side note, they also sent back my note that explains the problem meaning it was ignored completely.
I will be contacting @SamsungServic and calling but at this point I am not sure that they can fix the phone other then replace it.
Also,
I've spoken to Samsung and chat online and - yes they nice and throw back lots of promises and niceness back but they are NOT doing anything about it, for now at least.
I copy and paste the best answer on the google support topic to here:
I've been keeping a notebook to document my debugging of this problem. No app in particular is responsible, in my opinion. I have observed the phone lock up after a Factory Data Reset + USB wipe, and with no accounts configured. In fact, I have had it freeze after following this procedure:
1. Factory Data Reset + USB erase from Settings menu
2. Phone reboots.
3. Go through initial setup screens, skip account setup.
4. Power down phone.
5. Remove battery.
6. Remove SIM card.
7. Replace battery.
8. Power up phone.
9. Let phone sit for 15 minutes or more.
10. Phone freezes.
This is about as close to bare bones as I can get with this device.
I have also documented at least four freeze modes:
1. Phone is completely dark (both display and buttons). No combination of power button or other buttons can bring phone back. Battery removal required.
2. Phone display is dark, but the four "hard key" buttons are illuminated. No combination of power button or other buttons can bring phone back. Battery removal required.
3. Phone displays only a green android by a warning exclamation sign. Holding power button down, then volume up, then release volume up, will bring up the Android system recovery screen, from which phone can be rebooted.
4. Phone is frozen at the unlock screen. Sometimes this freeze occurs while swiping the unlock icon. No combination of power button or other buttons can bring phone back. Battery removal required.
I have observed the phone going from normal standby state (display and buttons dark) to state 2, and at other times to state 3, while it was sitting on my desk by the keyboard.
I'm just about ready to send it to Samsung. I just wanted to verify that the problem would be reproducible after a factory reset and without the SIM card.
I think it may be a hardware problem. It's also possible that part of the Android kernel or some device driver on my device has become corrupt. Unfortunately I can't reset the OS.
Click to expand...
Click to collapse
I did a factory reset from the stock recovery, too. Doesn't help either.
My phone arrived on Friday Samsung mobile repair in Texas. And like they did to ohter Nexus S devices from other users they will do the following to mine:
Reflashing the phone -> doing some functional tests ...
... and this is the crazy thing about it. The error we have is just appearing when the phone is in standby and because of this the phone passes the functional tests Samsung is doing at the end of the service. Phone goes back to user. A defective phone.
Some guy managed to keep the phone alive by setting the display turning off after 30mins. He is charging it twice a day
I got a reply from @SamsungSupport on twitter:
Thank you Fabian for again reaching out to us. We are aware of this issue as some of us have your same phone.
An evaluation is already being conducted to determine the fix. We don't have a timeframe of the resolution.
But understand it will be pushed to phones. We will advise once we have a timeframe.
Click to expand...
Click to collapse
The support team is friendly and to me it feels like they try to do anything they could.
Funny: One guy got a replacement device. But then no one other. Just reflash...
I think they will do something but on the other hand I'm worried that they will do nothing. But time will tell....
Maybe it would help us if Google will be aware of the problem, too. Ok maybe they allready know it, but I don't know that.
So if some of you here do have some connections... please do us a favor and forward this topic or the link to the google support topic. Feel free to forward this topic to any website you think it would write a news about it. Maybe Google will throw a eye on it. My phone is 8 weeks old and yeah this so anoying. And of course all my friends who are iHippster are trolling me like hell.
It don't want to flame or blame Samsung\Google for this.But our phones are in warranty. The error hits only a few devices and so they should replace it. My 50cent about it... this is not a Google expierence they talked about...
I also had the same problem and sent my phone into Samsung. They only re flashed it, which didn't fix the problem. I immediately called Samsung to inform them that the issue was not fixed and they just told me to send it back for "double checking." Do you think it is better to send it back in or just wait for fix to emerge?
I will be sending it back and demand replacing the phone, also making sure they just don't re-flash again. I guess anything but re-flashing could work.
Remember that I've mailed my phone with one page letter explaining the problem. Their response was flashing the phone and sending it back - with my letter.
Here is note from the support team:
----------------------------------------
Original Problem:
Technical Inquiry
Phone Freezing / Locked U
Freeze/Delay Between Menu
Problem found:
NO TROUBLE FOUND
SW,PRL,OTSL RESET
Solution:
Passed All Functional Testing
--------------------------------------
@Samsungservice did not even acknowledge it officially that this is a problem.
Yeah i wrote a letter too explaining the issue and how to recreate it (the first time). They told me that it passed their quality assurance inspection after re-flashing it, which must be very poor because my phone shut off again 15 minutes after receiving it. Just dropped it back off at UPS today. Can they replace the phone because of this issue? I know one person had success, but it doesn't seem anyone else has.
Nexus S faulty
Samsung may not be able to reproduce it after reflashing; as this issue does not seem to occur when connected to a PC/computer via USB. Their automated testing could be over USB.
Looks like more and more people are facing this issue as the day goes by.
Search for "Nexus S fault state" on google and you'll find the google support forum thread discussing it
Guys,
Did anyone have tried to flash a custom rom to see if this will solve the problem ?
cheers !
No, but this problem is not ROM related.
discr said:
Samsung may not be able to reproduce it after reflashing; as this issue does not seem to occur when connected to a PC/computer via USB. Their automated testing could be over USB.
Looks like more and more people are facing this issue as the day goes by.
Search for "Nexus S fault state" on google and you'll find the google support forum thread discussing it
Click to expand...
Click to collapse
I figured that was why they couldn't recreate the shutdown. Made sure they knew that it has to be unplugged. Mine always shuts off within 10-15 minutes if untouched.
I have same problem.Only remove battery helps. I have been having nexus s for 2 and half months and this problem just came last week. I don't know how to solve it. I tried reflash firmware but didn't help.
welcome to the club. you have to send it to USA to get it serviced (make a extreme detailed problem description and make sure the support worker writes it down 1:1 into their ticket system). they provide a 2day ups shippment label, BUT only to locations in USA.
I can recommend FedEx. They helped me a lot with this duty stuff for shipping to USA. That's not so easy . I paid €50 to get it shipped to a friend of mine in USA.
You have to send only the foreparts of the device. No battery and back panel, no charger and so on. But they will give you all informations at the end of the service request.
or: wait for a hotfix. which maybe never will come.
Update:
I just mailed my phone again... they told me they do not replace phones (not sure what that means yet). The Rep was arguing that if I want the phone replaced then I need to talk to T-Mobile - it does not make any sense.
Anyway, I explained the problem as much as I could and did not mail any notes this time as they obviously do not care for it. But I made sure he included every detail in his notes.
I am very skeptical but still hoping....
Also,
About the part when the phone does not freeze when plugged in or charging. I had my Nexus S charging overnight and it was frozen in the morning.
Update:
Also, I've contacted @SamsungServic via Twitter and asked if their team recognized it as a problem, but I've got no response.
On the other hand if you report the problem to them, they will respond that they will look into it - which means nothing, but if enough people asks the same question them they will have to.
-thanks
I've got some sort of responce via Twitter from @SamsungService, here is what they wrote back:
@SamsungService
Thank you for reaching out to us. We are aware of this issue as some of us have your same phone. An evaluation is already being conducted to determine the fix. We don't have a time frame of the resolution, but understand it will be pushed to phones. We will advise once we have a time frame. Thank you. ^Mary
@Keinam
Does this mean we should stop sending our phones back for repair and just wait for your OTA update? If it happens?
@SamsungService
Many issues can be resolved with warranty service. Regarding the issue you've referred to,It is my understanding that a fix if being worked on which would be sent out OTA. ^Mary
My nexus 5 is three days old now. This morning when I was reading an article in Chrome my screen started to just freak out. It was clicking links, going back to my app drawer, opening programs, going to Google now, opening (and sending!) emails, hangouts, Google Voice SMS messages, etc.
Thinking it might just be a glitch I did the first troubleshooting step - I turned it off and then turned it back on again. After a few minutes it was glitching again.
When it stopped momentarily I went right ahead and did a hard reset - just in case there was a Virus or something insidious on my phone. Normally I'd hold off on that option, but for this time since I didn't really have anything on the device I figured it was the appropriate course of action. After doing the hard reset and starting up my phone again, within a few minutes it was freaking out again. Luckily, I had the presence of mind to grab my old Galaxy Nexus and take a video recording of what I was seeing:
www [dot] youtube [dot] com/watch?v=6J5ILs-MqjI
Here are the facts:
- The phone is three days old.
- This is the first time that I've noticed this issue, however on day 1 I left the phone on my desk when I went to get some lunch. When I left (and came back) the battery was approximately 70%. Yet, mysteriously, in that 30 minute time frame the unit had shut itself off.
- The phone has not yet been exposed to moisture, extreme heat, or extreme cold. It has not yet been dropped. There are no other indications of manufacturer's defect readily visible.
- The screen is clean
- While having the tantrum, the phone went in and out of airplane mode several times.
- The tantrum occurred both before and after the hard reset. Installed apps weren't even completely downloaded when recurrence happened.
- In another fit, it eventually restarted itself.
Is this a hardware issue? Software issue? User error? Should I initiate an RMA?
DutchessDucky said:
My nexus 5 is three days old now. This morning when I was reading an article in Chrome my screen started to just freak out. It was clicking links, going back to my app drawer, opening programs, going to Google now, opening (and sending!) emails, hangouts, Google Voice SMS messages, etc.
Thinking it might just be a glitch I did the first troubleshooting step - I turned it off and then turned it back on again. After a few minutes it was glitching again.
When it stopped momentarily I went right ahead and did a hard reset - just in case there was a Virus or something insidious on my phone. Normally I'd hold off on that option, but for this time since I didn't really have anything on the device I figured it was the appropriate course of action. After doing the hard reset and starting up my phone again, within a few minutes it was freaking out again. Luckily, I had the presence of mind to grab my old Galaxy Nexus and take a video recording of what I was seeing:
www [dot] youtube [dot] com/watch?v=6J5ILs-MqjI
Here are the facts:
- The phone is three days old.
- This is the first time that I've noticed this issue, however on day 1 I left the phone on my desk when I went to get some lunch. When I left (and came back) the battery was approximately 70%. Yet, mysteriously, in that 30 minute time frame the unit had shut itself off.
- The phone has not yet been exposed to moisture, extreme heat, or extreme cold. It has not yet been dropped. There are no other indications of manufacturer's defect readily visible.
- The screen is clean
- While having the tantrum, the phone went in and out of airplane mode several times.
- The tantrum occurred both before and after the hard reset. Installed apps weren't even completely downloaded when recurrence happened.
- In another fit, it eventually restarted itself.
Is this a hardware issue? Software issue? User error? Should I initiate an RMA?
Click to expand...
Click to collapse
It definitely doesn't look like a user error, seems to prove you're using it fine when you can. This tantrum could be both hardware and/or software. If it were me with such a new device having an issue like this, i'd get a new one. I'd initiate RMA sooner rather than later.
FourPointedFreak said:
It definitely doesn't look like a user error, seems to prove you're using it fine when you can. This tantrum could be both hardware and/or software. If it were me with such a new device having an issue like this, i'd get a new one. I'd initiate RMA sooner rather than later.
Click to expand...
Click to collapse
Thanks. I guess with no other defects I just want to make sure it isn't user error or an app I have installed or anything. Seems like a waste to wait another month to get another unit and increasing the chances of it being someone else's refurb.
DutchessDucky said:
Thanks. I guess with no other defects I just want to make sure it isn't user error or an app I have installed or anything. Seems like a waste to wait another month to get another unit and increasing the chances of it being someone else's refurb.
Click to expand...
Click to collapse
Well based on my experience with Google and Nexus devices, typically they'll try hard in your situation to get a you a new device and sooner. They'll probably resell yours as a refurb but issue you a new one.
Fingers crossed.
Not sure if it is a rogue app or what. Screenshot attached. I'm about to get some sleep but whatever information I need to provide let me know. Stock no root. I work 10 hour days sometimes more and it really doesn't make it through and my on screen time is nothing. Was great and this week it's crap. Not sure what I did install. Whatever I need to run or information I need to give let me know please.
I manually did an OTA update to my phone yesterday, in order to put it on the latest NOF26V build with the February security patch. I noticed today that my phone is no longer going into deep sleep. The most likely reason for the change in behavior on my phone would be the OTA update, which probably means resetting the phone. Since no one else has commented, I'll just throw out the idea that maybe an OTA system update could cause the phone to keep from going into deep sleep, considering that seems to be the most likely cause of what happened to my phone. The official troubleshooting for a problem app is to try Safe Mode before resetting the phone, which is how I've come up with my opinion that Google (Play) Services usage around 200 mAh or more per day is probably to be expected on this phone, but the app you're using to check deep sleep will not work in Safe Mode.
https://support.google.com/pixelphone/answer/2852139?hl=en
https://support.google.com/pixelphone/answer/6090599?hl=en&ref_topic=7084611
EDIT: I later found out that my phone being held awake was likely due to a setting change I had made, rather than the OTA update
That could be it. Going to give it a try and see how it is over a few days.
Hello all,
First post here and hoping someone can help me!!
I got a Samsung S22 ultra back during launch this year (Feb or March time?) and it's an awesome phone but unfortunately, over the last few months it's begun randomly restarting/rebooting itself on it's own accord (I remember checking and I have no settings ON to make it do this). It was mildly annoying and to be honest, I just persevered and didn't do a factory reset back then which I probably should have in hindsight...
Fast forward to this week. I am out walking the dog and my battery drops to 5% and the screen darkens in an attempt to conserve battery. I think in this time I have somehow maxed out my screen unlock attempts to the point that it now says 'Try again in 24 hours' which I thought would be fine if it wasn't for the fact that every time my phone randomly restarts itself, it also restarts the 24 hour lock period.
Essentially, I am indefinitely locked out of my phone and unfortunately remote unlock is off. Why oh why I do not know but I am kicking myself.
Basically, is there ANYWAY or METHOD that anyone can help me with that would enable my phone to stay powered on for the full 24 hours? the solution seems easy enough to me, allow the countdown to reach 0 and I will be able to unlock my phone again with fingerprint/pin. I have downloaded something called 'Droidkit' from Imobie and they have a feature called system fix. Could that be installed safely to my phone and perhaps correct or update any firmware/software isssues that is causing the reset? Or is the Samsung Knox security too secure?
I am absolutely desperate as I have got no back up arranged and stand to lose nearly 2/ 3 years of photos and videos of sentimental value (wedding, honeymoon, relatives, memories etc) and it's incredibly distressing to think my only option is factory reset when if my phone COULD JUST STAY POWERED ON FOR 24 HOURS AND ALLOW ME TO UNLOCK IT.
Please help, thank you in advance.
If you really need that data... use a data recovery specialist. That phone, if survives the data retrieval attempt, needs to go in for repair.
You can try keeping it on the charger to see if that prevents a reboot. Even with an SD card I redundantly backup its critical data, you should too.
blackhawk said:
If you really need that data... use a data recovery specialist. That phone, if survives the data retrieval attempt, needs to go in for repair.
You can try keeping it on the charger to see if that prevents a reboot. Even with an SD card I redundantly backup its critical data, you should too.
Click to expand...
Click to collapse
Sadly, keeping it plugged in to the charger doesn't keep it on power for 24 hours - it tends to restart randomly every so often still
Well I went to an official Samsung store today in the UK - I was told that for them to fix it would involve wiping/factory resetting the phone. Losing everything (which I am not yet prepared to do).
Would rebooting to bootloader be any good? I am not good with this stuff!
Thanks
Why you just don't switch phone off, and leave it like that for 24 hours?
Phone doesn't need to be turned on.
vinoboxer said:
Sadly, keeping it plugged in to the charger doesn't keep it on power for 24 hours - it tends to restart randomly every so often still
Well I went to an official Samsung store today in the UK - I was told that for them to fix it would involve wiping/factory resetting the phone. Losing everything (which I am not yet prepared to do).
Would rebooting to bootloader be any good? I am not good with this stuff!
Thanks
Click to expand...
Click to collapse
Try chilling it down to 50F, see if that helps.
Never attempt to charge an Li near or below freezing though. Bag it before you chill it.
The screen lock complicates everything. Files are encrypted so you need those encryption keys to access data. Way beyond the level I could troubleshoot. A data recovery specialist is your best shot. They may need to remove the chipset to access the files. Fees are around $800.
You can keep trying, get it into safe mode if possible. I never use a screen lock as you are the one most likely to be locked out, sometimes through no fault of your own. Having lost a 30yo database that's not recreatable myself, you have my empathy. Sometimes all you can do is learn from your mistakes... and not repeat them.
vinoboxer said:
Hello all,
First post here and hoping someone can help me!!
I got a Samsung S22 ultra back during launch this year (Feb or March time?) and it's an awesome phone but unfortunately, over the last few months it's begun randomly restarting/rebooting itself on it's own accord (I remember checking and I have no settings ON to make it do this). It was mildly annoying and to be honest, I just persevered and didn't do a factory reset back then which I probably should have in hindsight...
Fast forward to this week. I am out walking the dog and my battery drops to 5% and the screen darkens in an attempt to conserve battery. I think in this time I have somehow maxed out my screen unlock attempts to the point that it now says 'Try again in 24 hours' which I thought would be fine if it wasn't for the fact that every time my phone randomly restarts itself, it also restarts the 24 hour lock period.
Essentially, I am indefinitely locked out of my phone and unfortunately remote unlock is off. Why oh why I do not know but I am kicking myself.
Basically, is there ANYWAY or METHOD that anyone can help me with that would enable my phone to stay powered on for the full 24 hours? the solution seems easy enough to me, allow the countdown to reach 0 and I will be able to unlock my phone again with fingerprint/pin. I have downloaded something called 'Droidkit' from Imobie and they have a feature called system fix. Could that be installed safely to my phone and perhaps correct or update any firmware/software isssues that is causing the reset? Or is the Samsung Knox security too secure?
I am absolutely desperate as I have got no back up arranged and stand to lose nearly 2/ 3 years of photos and videos of sentimental value (wedding, honeymoon, relatives, memories etc) and it's incredibly distressing to think my only option is factory reset when if my phone COULD JUST STAY POWERED ON FOR 24 HOURS AND ALLOW ME TO UNLOCK IT.
Please help, thank you in advance.
Click to expand...
Click to collapse
you could send it to a unofficial repair store and let them check the phone, they might change the battery and check for any hardware issue or at least keep the phone on for you to be able open and backup everything from your phone.
you might lose the warranty by doing so.
i wish you the best.
All I see is you got too confident. If you have had fixed the randomly reboots when you started experiencing it this problem you have now would be easily fixed in 24 hours. Anyways, if I were in your shoes, I would try to flash the current complete firmware through Odin but flashing the HOME_CSC binary as CSC, since that one is supposed to don't wipe your data. That's what I would do (without high hopes) before doing a factory reset if that's my only option.
Try to unlock with Google's Find my phone app.
Hi, trying to boot into safe mode could potentially prevent the random reboots ONLY IF the culprit is an app.... It's worth trying anyway...
Why not factory reset in bootloader. It will trigger FRP lock but as long as you know your unlock code/password it will work fine. You'll lose your data but you'll be back in the phone
draskome said:
Why you just don't switch phone off, and leave it like that for 24 hours?
Phone doesn't need to be turned on.
Click to expand...
Click to collapse
I'm with draskome....
I don't have a S22 and my last Galaxy S was an S5 so I doubt I know anything...but where does it say it has to be on for 24 hours straight? All the other posts on this thread seem to take that condition as a given, so maybe it's just something a non-S22 user wouldn't know.... I would think that turning it off for at least 24 hours, and then turning on & loading up the phone, the phone's internal check would find 24 hours have passed and remove the "lock" on it; and that would only need a nanosecond to confirm...
If not, what a complete oversight by Samsung! That is completely stupid requirement that it must be on for 24 hours; I would see no intrinsic value in it needing to be on for that long before removing the lock.... maybe someone can explain....
simplepinoi177 said:
I'm with draskome....
I don't have a S22 and my last Galaxy S was an S5 so I doubt I know anything...but where does it say it has to be on for 24 hours straight? All the other posts on this thread seem to take that condition as a given, so maybe it's just something a non-S22 user wouldn't know.... I would think that turning it off for at least 24 hours, and then turning on & loading up the phone, the phone's internal check would find 24 hours have passed and remove the "lock" on it; and that would only need a nanosecond to confirm...
If not, what a complete oversight by Samsung! That is completely stupid requirement that it must be on for 24 hours; I would see no intrinsic value in it needing to be on for that long before removing the lock.... maybe someone can explain....
Click to expand...
Click to collapse
I think you're correct but maybe the OP's firmware or hardware is fubar and not following the protocol.
Got locked out of a bios like that, a hardware failure. Had I never set a password no lockout would have occured.
blackhawk said:
I think you're correct but maybe the OP's firmware or hardware is fubar and not following the protocol.
Got locked out of a bios like that, a hardware failure. Had I never set a password no lockout would have occured.
Click to expand...
Click to collapse
Hmmm...I wonder...
I find it unlikely that if OP is able to keep his phone turned on (but locked out) for some time -- just not for the 24 hours straight as the phone will randomly restart -- and the phone's hardware is that "fubar" so badly that it can keep on for at least minutes (if not hours) but not be able to track or release after finding out 24 hours has passed. I might believe the "fubar" failure is that severe if the phone would crash when loading up or immediately restart when starting up -- but then OP would say "bootloop" and not merely that it "randomly restarts" -- but it seems stable enough for at least a little while....
If what you say is true in the end, then the OP probably has no hope because even stopping the random restarts might not resolve the countdown properly because the "hardware [is]....not following the protocol" regardless....
simplepinoi177 said:
Hmmm...I wonder...
I find it unlikely that if OP is able to keep his phone turned on (but locked out) for some time -- just not for the 24 hours straight as the phone will randomly restart -- and the phone's hardware is that "fubar" so badly that it can keep on for at least minutes (if not hours) but not be able to track or release after finding out 24 hours has passed. I might believe the "fubar" failure is that severe if the phone would crash when loading up or immediately restart when starting up -- but then OP would say "bootloop" and not merely that it "randomly restarts" -- but it seems stable enough for at least a little while....
If what you say is true in the end, then the OP probably has no hope because even stopping the random restarts might not resolve the countdown properly because the "hardware [is]....not following the protocol" regardless....
Click to expand...
Click to collapse
Don't know. Maybe if they play with it a bit... but if the lock screen pass code has been corrupted... fubar.
Always redundantly backup critical data regularly, if you have a SD card slot use it. Having a data drive many times saves the data if the phone dies. Don't encrypt it...
reflash the firmware (use home csc), boot into safe mode