Hello XDA, i've heard (and know) that you guys are quite good with phones, and was hoping someone would be able to help me out, i can't find anybody with the same problem.
So here it is:
Since i've been skiing, often when i lock my phone the screens keeps on coming on and staying on the lock screen, and just won't turn off, so it's an obvious baterry drainer and pontentially dangerous for the screen, so i've resosrted to putting a black background image.
Also when the battery gets "critically low" my phone comes up with the message and also vibrates, but keeps on repeating in, just doesn't stop !
I've also noticed that when this problem occurs when i go into battery saver in options the second box constantly flashes as does the estimate remaining time and time since last charge.
My battery is now really bad when this happens, but supprisingly is ok when this doesnt happen.
Has anybody else had this problem, or something similar? and could someone give me some advice (factory reset? which i don't really want to have to do :/ )
Thank You
and my phone is generaly a bit buggy when this happens, like suddenly turning off etc.
Since this happened after skiing, I'm guessing your phone got a bit wet, probably around either the power button or the battery (or both). You can try drying it out by putting it in some warm dry rice (an excellent dessicant) but that's something you do within minutes of it getting wet, not days, if you want to avoid permanent damage.
You could also try taking the battery out and carefully inspecting it, comparing it with the battery from another phone, etc. If it appears damaged in any way (swollen, discolored, corrosion on the contacts, etc.) you could try replacing the battery and seeing if that helps. You could also replace the phone, of course, but you'll probably have to buy it at retail price unless you've got insurance that covers liquid damage.
You could try a factory reset before replacing the phone, since you'll lose all your data anyhow, but this doesn't sounds nearly as much like a software problem as it does like a hardware problem. However, getting your data off is actually possible, using a tool like WP7 Root Tools (which is really awkward to use for backup, but it can be done). If you wait the next however-long for Heathcliff74 to release a version of Root Tools that supports elevating other apps, you'll be able to use a data backup tool that I wrote last year and am modifying to work via any full-permissions access.
Thank you for the reply.
The same problem actually happened in November also, but quickly went back to normal, but it's been a week now so it's getting a bit annoying.
I just rang samsung and she obviously said do a reset, so i think i'll do this but this will erase everything, i would just like to keep my contacts and messages tbh.
Havn't got time do research that yet but i'll look after, unless someone points me to something first, and i'll post back.
Thanks
You can make a backup of the phone before hard-reset. That way, if the reset doesnt' fix anything, at least you can restore the backup and be back where you were before deciding on your next step.
I can't get the Backup program to work, http://forum.xda-developers.com/showthread.php?t=1103011
Keep getting "Le format de la chaîne d'entrée est incorrect."
And if i try the in the command prompt i just get a an error saying "updatewp.exe stopped working"
is there any other way of backing it up?
Thanks
Related
Hello all, i am having a couple of problems with my sensation,firstly its a refurb supplied by an insurance company and they only gave it a 30 day returns policy which expire over a month ago,i had already sent one back where the microphone didn't work.
The first problem is that i have a green flickering that appears on just over half of the screen (see attached video) it comes and goes but is there most of the time now,if it gets really bad in the area where the screen flickers the graphics within that area goes corrupt almost as if someone has brushed the graphics down the screen with a paint brush.
It is worse than the video shows but only have an old phone to take the video with.
Could this be hardware malfunction? It was there before i upgraded to 4.0.4 and there afterwards.
The second problem is since upgrading to 4.0.4 i have terrible battery life 8-9hrs max the phone keeps turning it self off, on nearly every re-boot "upgrading applications 0-32" comes up runs through the upgrading and then turns off again. these re-boots also suck the life out of the battery.
I haven't yet tried flashing a new custom rom to it as it has not been rooted etc yet.
Any ideas/suggestions?
Thanks in advance.
I am 99% sure the screen flickering is hardware related. For battery life, firstly check for battery draining apps running in the background. The android is upgrading message happens when android is building the dalvik cache and seems to happen only when dalvik cache and cache are wiped on deodexed systems, however it seems to happen on every boot on odexed systems but either way, its normal and nothing to worry about
oh well time to phone the insurance company AGAIN then,just as you get all your progs/games on your phone you want on there, somethings screws it up.
was gonna flash a custom rom to see if that worked out the screen probs but, i shall wait until i know what the insurance people say.
Thanks for the response
Now what to do for the best????
Ok so i contacted my insurance company and they agreed to take the phone and fix it for free,they have dispatched a special delivery envelope to me.
I have wiped my phone and got a little annoyed because i have got 29gb worth of programs installed and its such a pain in the arse to reinstall everything!
So the phone is now reset to factory settings and guess what......Thats right the fault has gone!
What to do still send it off with no visible fault?
Or keep it?
I cant see it being a program thats did it as i hadnt s-offed the phone or rooted it so there shouldnt be any software that can interfer with the phones screen can there?
I have had a few "huh humm" trial versions of games and apps on it,could there be mal or spyware that has done it or possibly where something may or may not have been [email protected]?
What to do.....
back a little bit...Damn phone
Well after the factory reset the battery life is a lot better.
The screen flicker has come back but very very intermittently so hoping that the tech guys at either the insurance company or more likely HTC as the insurance people quoted this "you should within 17 days you will get your phone back" will be able to see it.
All this trouble aside this is definitely one of the best phones i have ever owned and i love it,never did i think back in the days when i owned a titan II and a jade did i think i would ever see graphics like i do today,the game, application programmers/designers and the phone makers just keep on astounding me with what they produce.
So, there I was, eating dinner while my phone read me a book.* And suddenly, it stopped. Because my phone crashed. And the amount of a boot cycle it can get through before crashing has been decreasing ever since. A complicating factor: when I still thought it was possibly a software issue, I booted into recovery, and attempted to re-flash the OS (currently it's on 10.2.1). It crashed partway through the process.
On the off chance this was a humidity issue (and not having a lot of time to mess with it) I opened up the phone, removed battery, sim, sd and the small screws in the main body of the phone, and left it in a dry well ventillated place. Now it will get as far as the initial "samsung" splash screen the first time I've reinserted the battery, and won't boot at all beside that. (It's possible that the power button was behaving weirdly, but the phone's behavior was generally so erratic that I can't say that with confidence.) Also, sniffing at the keyboard there is ever so faint a smell of burnt electronics... maybe. Maybe just platicizers. (I've noticed a bit of
This is the same phone that had screen issues (assumed to be related to a small amount of water** though subsequent evidence suggested a loose connector as an alternative hypothesis) around the beginning of February. It's been fine ever since, discounting the occasional weird usb connectivity issues that seem to be common with this phone.
I'm pretty happy to take the phone apart, but other than a general decase everything and look for loose connectors or other obvious trouble, I'm not even sure where to begin. (Also, I have about twelve hours to put in an order if I want Amazon to send by a new phone by tomorrow. Which is kind of silly, but this is swiftly and impressively dead. And otherwise it'd be no phone until Tuesday, which wouldn't kill me, but which would annoy me mightily.)
Any thought regarding common problem areas for this phone? I'm hoping to be able to leave the lab early today, which should give me some hours of working time. Well set up for tools, always happy to have things to take apart.
* Text to speech is awesome, once you get used to the robo-voice.
** Really, not a lot - none of the moisure stickers showed anything, and I don't think it got into the main body of the phone.
The de-casing was fun, and yet there isn't an obviously damaged component. It was pronounced dead at 6:20 yesterday evening.
R.I.p.
Sent from my SGH-T699 using XDA Premium 4 mobile app
tylik said:
So, there I was, eating dinner while my phone read me a book.* And suddenly, it stopped. Because my phone crashed. And the amount of a boot cycle it can get through before crashing has been decreasing ever since. A complicating factor: when I still thought it was possibly a software issue, I booted into recovery, and attempted to re-flash the OS (currently it's on 10.2.1). It crashed partway through the process.
On the off chance this was a humidity issue (and not having a lot of time to mess with it) I opened up the phone, removed battery, sim, sd and the small screws in the main body of the phone, and left it in a dry well ventillated place. Now it will get as far as the initial "samsung" splash screen the first time I've reinserted the battery, and won't boot at all beside that. (It's possible that the power button was behaving weirdly, but the phone's behavior was generally so erratic that I can't say that with confidence.) Also, sniffing at the keyboard there is ever so faint a smell of burnt electronics... maybe. Maybe just platicizers. (I've noticed a bit of
This is the same phone that had screen issues (assumed to be related to a small amount of water** though subsequent evidence suggested a loose connector as an alternative hypothesis) around the beginning of February. It's been fine ever since, discounting the occasional weird usb connectivity issues that seem to be common with this phone.
I'm pretty happy to take the phone apart, but other than a general decase everything and look for loose connectors or other obvious trouble, I'm not even sure where to begin. (Also, I have about twelve hours to put in an order if I want Amazon to send by a new phone by tomorrow. Which is kind of silly, but this is swiftly and impressively dead. And otherwise it'd be no phone until Tuesday, which wouldn't kill me, but which would annoy me mightily.)
Any thought regarding common problem areas for this phone? I'm hoping to be able to leave the lab early today, which should give me some hours of working time. Well set up for tools, always happy to have things to take apart.
* Text to speech is awesome, once you get used to the robo-voice.
** Really, not a lot - none of the moisure stickers showed anything, and I don't think it got into the main body of the phone.
Click to expand...
Click to collapse
Get a new battery for it....had this issue before and placing new battery in it fixed my bootlooping and not being able to flash or get past samsung screen...the samsung batteries have an overcharge feature which has been known for causing errors such as this...
Hello,
I have searched and searched this forum to find any threads or posts that describe this problem. I have found lots of similar ones, but none like this, so that is why I have started a new thread. If I missed this topic somewhere, I apologize for not having found it.
My wife and I both have Skyrockets (GSII - I727). Stock AT&T ROM (not rooted), but both unlocked. Mine got partially wet last week (toilet incident, would rather not elaborate, but I will answer the first question everyone asks - yes it was a "clean" toilet ) Anyway, I immediately liberally rinsed all ports with alcohol and warmed gently with a hair dryer. After drying I powered up, and everything worked, except the battery percentage display (with a variety of completely fresh and fully charged batteries), would only show in the 50 - 68% charge range, and the phone seemed to die at about the rate one would expect commensurate with those numbers. Put it in a bag of rice for 2 days. No better.
So, after reading here and watching several YouTube videos, I completely disassembled the phone. cleaned all ports, ribbon connectors, mother board, etc. with CRC electrical contact cleaner spray using the spray tube and a very gentle toothbrush. I paid special attention to the micro USB charging port, and all other contacts and circuits that seemed to be related to charging, though I am by no means an electrical engineer or technician, so a lot of it was guesswork. I made sure all was dry and new looking. All contacts intact, no visible corrosion or bridging, and reassembled the phone perfectly (pretty proud of myself for not breaking anything in the process!)
The phone still works great, except for the battery percentage display issue. I have tried everything I've read on this forum about recalibrating the battery meter - discharging fully and then charging up. With the phone on, with the phone off, every permutation I can think of. I tried clearing the cache and rebooting. Still, the maximum the display will read is 68% and that's it, and the phone behaves and dies like it has a battery that is only 68% full, even though I know I am putting 100% charged batteries into it. I have verified this by putting the same batteries into my wife's identical phone and it displays 100%.
If my phone we're lasting as long as it normally would with a fully charged battery, I wouldn't be so bothered by the display being inaccurate, but that is not the case. I've downloaded CPU SPY and some other apps to see if my phone is using an unusual amount of battery resources, but it is not. So, that's the story.
I am not afraid of rooting the phone, and I have no warranties left so I don't care, it's just that from what I've read here on the forum, people with somewhat similar issues have not benefitted from rooting and then running apps or programs that are only available to rooted phones, so I would prefer not to go down that time consuming route, if all I'm going to do is hit another dead end.
So, any suggestions or comments would be greatly appreciated! Thanks in advance.
Best regards,
Ron M.
This may sound dumb, but did you try a factory reset?
sireniankyle said:
This may sound dumb, but did you try a factory reset?
Click to expand...
Click to collapse
Thank you for your post sireniankyle. Not a dumb question at all, and actually the answer is no. I have certainly considered it, but I haven't done it yet for 2 reasons.
The first is that from all the research I've done, trying to find others who had similar experiences (I have yet to find anyone with the IDENTICAL problem), they have all without exception reported that factory reset did not solve their problem.
Second, because of my previous experiences with doing a factory reset, it seems that no matter how well I am backed up, that it turns into a very time consuming process in getting the phone tweaked and with all the applications and setting back to where I had them. So, I've been holding out and saving factory reset as one of the last resorts.
The other last resort is to root the phone, because apparently there are some apps that might be able to reset the battery counter that will only work on a rooted phone. However, again in my research thus far, I haven't identified anyone with a rooted phone with a similar problem who has had succeeded in solving the problem.
Perhaps this weekend if/when I have the time and patience I will attempt one or both of the above. It's just that I have such low expectations of success that am reluctant to start down those paths.
If you, or anyone else on this forum can point to any experiences where these methods actually worked for someone in this same or similar situation, I would very much appreciate if you could direct me to the appropriate thread.
Thanks again very much for your input, and your further assistance and suggestions would be most appreciated.
Best regards,
Ron
No problem. I just try to help out where I can.
I can't say that I have had any of these issues. I understand the issues with backing up, but if you install twrp, you can create an entire backup of your phone. I've done it many times before without issue, and if resetting it doesn't work, you can still go back to your original set up.
It seems like you may be a pioneer in this particular issue. I hope you figure it out. Both for yourself, and for others who have this problem in the future.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
sireniankyle said:
No problem. I just try to help out where I can.
I can't say that I have had any of these issues. I understand the issues with backing up, but if you install twrp, you can create an entire backup of your phone. I've done it many times before without issue, and if resetting it doesn't work, you can still go back to your original set up.
It seems like you may be a pioneer in this particular issue. I hope you figure it out. Both for yourself, and for others who have this problem in the future.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
Thanks again sireniankyle!
I used to like being a "pioneer", but as I get older now I just want my stuff to work, and don't have the time or the patience to go where no man has gone before Nevertheless, I absolutely hate to admit defeat, and now that you've turned me onto twrp (do I have to root first to use it?), then perhaps that will make the experiment less time consuming, so I may try this weekend if time allows.
In the meantime, the phone continues to function normally in every other way. I simply carry a couple fully charged batteries in my pocket throughout the day, which are of course 100% charged via my wall charger, but show as 58% as soon as I put them in the phone, and then die at approximately the rate one would expect from a 58% charged battery! Weird huh?
Best regards,
Ron
Was given a Skyrocket the other day which suffers from the same kind of problem (had massive water damage), but the battery percentage is stuck at 0%. So of course it will not even boot up. (Fully charged the battery in a wall charger.) Only thing the power button will do is vibrate the haptic feedback given at first power on, no screen activity. Funny thing is it'll go into Download mode perfectly normally and sit on the Odin mode screen till I assume the battery dies. However it will not go into Recovery mode. Plug in a USB charging cord to charge block or a port on a PC and the phone powers on and works perfectly fine, though forever stuck at 0% battery.
So the only thing I can think of to quickly get around this is without solving the problem, if in fact it can be, is to get a charging case. Like such, for example. http://http://www.ebay.com/itm/XPAL-Galaxy-S2-Skyrocket-PowerSkin-Case-i727-Extended-Battery-Gel-Cover-OEM-New-/310903753323 Had one similar before for another model and when installed it shows as if the phone is charging. So in theory will work for me, though powered strictly by the cases battery. Should work for you even better as you'll get the cases battery life then your own 58% worth of battery life. Edit, just realized when the last post was made, you probably have a new phone and moved on by now.
**I'm going to try to craft myself a homemade powered case yet, have tons a batteries kicking about.
Never dropped it or got water in it. Never tried to change the OS or anything like that either.
It started freezing and a soft reset would get it back up. Started happening more often and eventually none of the suggested resets would work and even when charging with the phone off it would freeze. I eventually managed to get it into the recovery boot (just the once) and it said E:/ failed to mount over and over. When i pressed a button it froze again and since then i haven't been able to get any response. Not even the little battery symbol or red light when it's on charge. It seems completely messed up and essentially a brick right now.
Any ideas? I can get it repaired via my UK network provider (O2) which would take a couple of weeks but would really like to back up and factory reset my stuff if possible as i have lots of personal data on my phone including passwords to peoples websites (i'm a web developer). As well as the ordinary things your girlfriend wouldn't want ending up on the net. My online banking and everything is on there. There's pictures with some famous people at Glastonbury and also some brilliant sporting events i was at that i'd never be able to get the vids/pics back.
With the failed to mount error, would that mean they'd have to factory reset it regardless of what happens and i'd have no chance to back it up either? I'd really rather not lose my files but i also don't want some random guy snooping through my stuff.
Thanks in advance for any replies guys!
Have you tried a different charging method?
From PC with a different USB lead for example
Leave it connected overnight and see how it is the next day
Thanks for the reply.
My girlfriend uses my charger to charge her blackberry as she lost hers and it works fine. I also tried leaving it for a few hours connected to the laptop using the USB connection from the original charger with no response whatsoever. My mother has as Samsung too... given the points i just told you, is it worth trying to borrow another charger still?
I'd reluctantly be happy even if i have to factory reset to save me having to wait for ages to get it back.
No, sounds like you can rule out the charger being the problem
Sounds like something inside the phone has fried, possibly the charging port if you can't even get an LED on, but considering the errors leading up to the fault it sounds more like the motherboard has died, which, unless you saved anything to external SD (MicroSD), contains the Internal storage where all your files are
More than likely, Samsung will just replace the board rather than fiddling around trying to repair that one, so unless it is something else at fault you can probably relax about them snooping, it'll end up in the recycling bin to be melted down for it's gold contacts never to be powered up again
I can't think of anything else you can try to get life out of it tbh other than opening it and charging the battery another way / replacing the battery with a charged one, but warranty is gone after that and not even sure how you would go about switching batteries tbh, if you can
If it is already out of warranty, you could find where the battery terminals connect to the motherboard, and put an alternate power source to them matching the battery voltage etc (Removing the battery first), might give you time to remove / erase / copy
Thanks again for the reply.
So you think the motherboard just progressively died? I hadn't mentioned this but a while ago i accidently left the phone on the radiator for a short while whilst working. It worked fine afterwards and when i asked on another forum they said if any damage was going on it would have restarted or gave an overheat message (which it didn't).
I guess i'll be sending it off to my network provider (O2 UK) then, it's still in warranty (just) so they should fix it or send me a new one. I've seen so much stuff on amateur porn sites of videos or pictures that probably weren't meant to be "released", leads me to having a fear about my girlfriend ending up on them. And like i said, passwords are stored on there to some websites i create for people so its not just my personal data but theirs. I don't really know how these businesses are run, i'd imagine they'd want to get as many phones done as possible... but knowing me if i was doing that job i'd probably have a snoop where i could lol.
powlesy6 said:
Thanks again for the reply.
So you think the motherboard just progressively died? I hadn't mentioned this but a while ago i accidently left the phone on the radiator for a short while whilst working. It worked fine afterwards and when i asked on another forum they said if any damage was going on it would have restarted or gave an overheat message (which it didn't).
I guess i'll be sending it off to my network provider (O2 UK) then, it's still in warranty (just) so they should fix it or send me a new one. I've seen so much stuff on amateur porn sites of videos or pictures that probably weren't meant to be "released", leads me to having a fear about my girlfriend ending up on them. And like i said, passwords are stored on there to some websites i create for people so its not just my personal data but theirs. I don't really know how these businesses are run, i'd imagine they'd want to get as many phones done as possible... but knowing me if i was doing that job i'd probably have a snoop where i could lol.
Click to expand...
Click to collapse
If the phone powered on when you sent it in then no doubt somene would have a snoop, but if it is DOA they won't waste their time, they'll be getting thousands of phones a day to go through, yours will just be another number: Press power > Nothing > test with some USB device > Nothing > open > replace motherboard > test > working > job done
Something like that I would imagine
For future reference, get a MicroSD card for your replacement and save all media to that, then you don't have this problem if it dies
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