Wondering if this is isolated to my phone or if its systemic. I have never modified my phone, its stock from Google directly. Twice now, the phone starts running slow/acting strange, then will reboot and say that the system is corrupted and will not load. I tried to sideload the latest OTA to recover, but doesnt take. I literally have to do a full hard reset to get the phone back. The phone has done this to me twice now randomly. I have never had a phone, especially not modified at all, just randomly corrupt itself let alone do it twice. Has this happened to anyone else?
Wondering if I should have Google send me another phone.
iceman4357 said:
Wondering if this is isolated to my phone or if its systemic. I have never modified my phone, its stock from Google directly. Twice now, the phone starts running slow/acting strange, then will reboot and say that the system is corrupted and will not load. I tried to sideload the latest OTA to recover, but doesnt take. I literally have to do a full hard reset to get the phone back. The phone has done this to me twice now randomly. I have never had a phone, especially not modified at all, just randomly corrupt itself let alone do it twice. Has this happened to anyone else?
Wondering if I should have Google send me another phone.
Click to expand...
Click to collapse
For me this sounds like a hardware failure and I'd try to get the phone replaced.
Probably the NEW in house TITAN chip.
There must be something on your device. Factory reset it. Should be yohr best bet.
dirtyreturn said:
Probably the NEW in house TITAN chip.
There must be something on your device. Factory reset it. Should be yohr best bet.
Click to expand...
Click to collapse
I agree and think it could be hardware. I have Factory reset the phone twice already.
The firmware flash may have become corrupted therefore factory resets are useless.
Flash data has a limited lifespan usually this doesn't become an issue but it can.
Reflash and see if it holds. Otherwise it's likely a memory chipset or mobo failure.
This happened to me. Was running one of the developer previews and chalked it off to that. lost everything I didn't back up the night before (out of habit from messing with my phones I do daily backups of the important folders and phone data). The only thing that worked for me was re-flashing factory image and start fresh. Hasn't happened again for me.,
I had a similar experience about a month or two ago. Same situation, stock firmware on an unlocked device direct from Google. I had thankfully backed up about a week prior.
EvilRubberDuck said:
I had a similar experience about a month or two ago. Same situation, stock firmware on an unlocked device direct from Google. I had thankfully backed up about a week prior.
Click to expand...
Click to collapse
For the system to go corrupt by itself is rare unless there's a hardware fault.
More than likely it was 3rd party software that caused it. Launchers, power management apps are prime suspects.
Androids are typically a very stable platform.
Related
I have a rooted stock 11s ROM with TWRP recovery. I can't stand the random reboots anymore. I've seen the plausible explanation that the problem is driver-related, probably wifi. There are claims that the factory sent out ROMs with a defective system partition. I've seen purported solutions for that theory including total wiping (including system) and reflashing stock. I've seen claims that flashing a kernel is the answer. Most of this seems to be speculation. And a lot of it takes place outside XDA. I know this is the best place to come for smart answers.
Please propose any solution that might have worked for you. And-- if you reach me by 18:30 Pacific time (US) with a rational message, I have something to convey that a non-owner would love to have.
Thanks folks!
Are you on the latest CM11s? Never had a random reboot, maybe try factory resetting it and installing apps fromplaystore all over again? Restoring apps from Titanium Backup can cause weird issues sometimes. Esp if its a new device.
goattee said:
I have a rooted stock 11s ROM with TWRP recovery. I can't stand the random reboots anymore. I've seen the plausible explanation that the problem is driver-related, probably wifi. There are claims that the factory sent out ROMs with a defective system partition. I've seen purported solutions for that theory including total wiping (including system) and reflashing stock. I've seen claims that flashing a kernel is the answer. Most of this seems to be speculation. And a lot of it takes place outside XDA. I know this is the best place to come for smart answers.
Please propose any solution that might have worked for you. And-- if you reach me by 18:30 Pacific time (US) with a rational message, I have something to convey that a non-owner would love to have.
Thanks folks!
Click to expand...
Click to collapse
The problem with this situation is that there can be way too many causes for random reboots, we're talking dozens and dozens and dozens. So pinpointing exactly what's causing your particular device to reboot is virtually impossible. Your best solution? Go to this thread and use that automated tool to perform a wipe and bring your phone back to an entirely stock state.
Transmitted via Bacon
---------- Post added at 09:29 AM ---------- Previous post was at 09:27 AM ----------
SilentRazor said:
Are you on the latest CM11s? Never had a random reboot, maybe try factory resetting it and installing apps fromplaystore all over again? Restoring apps from Titanium Backup can cause weird issues sometimes. Esp if its a new device.
Click to expand...
Click to collapse
Not really. I've flashed thousands of times and I restore my apps with Titanium every single time, I never, ever have problems. As long as you don't do something stupid like restoring system data then TiBu is perfectly safe to use.
Transmitted via Bacon
I'm having the same issue.
44S, rooted, TWRP. No Xposed, no themes, no icon packs and each day the reboots are getting worse. I've read the same thing about a faulty partition being a culprit and am going to try the tool linked above to see if that has any impact.
If you are still inside the 45 day window of purchase, I would suggest opening a ticket with Oneplus. It would be worth getting the issues documented as early as possible so you can have a valid claim for a warranty repair if it comes to that.
Psichi said:
I'm having the same issue.
If you are still inside the 45 day window of purchase, I would suggest opening a ticket with Oneplus. It would be worth getting the issues documented as early as possible so you can have a valid claim for a warranty repair if it comes to that.
Click to expand...
Click to collapse
Thanks for your wise suggestion! I just followed your advice. At least it gives me one possible option. I love the phone when it's not rebooting. But it's already rebooted a couple times just as a call was coming in!!!
Don't attribute the problem to Titanium Backup
Psichi said:
I've flashed thousands of times and I restore my apps with Titanium every single time, I never, ever have problems. As long as you don't do something stupid like restoring system data then TiBu is perfectly safe to use.
Click to expand...
Click to collapse
I agree.
I have used Titanium Backup on numerous Android devices from a variety of manufacturers-- including CyanogenMod 7 on my Nexus One. It's never been the cause of problems. And I also agree that the only reason Titanium restores would cause a problem is if you're restoring "foreign" system apps.
I don't have any confidence that using the official tool would solve the problem-- especially if the theory about the defective system partition image is the correct one-- I might just be reinstalling the same problem.
I'm more inclined to try the solution by echew010 in this thread:
https://forums.oneplus.net/threads/random-reboot.232446/
But I am not sure how bold I want to be. I'm not afraid of the concept of totally wiping the system partion. And it wouldn't be the first time I've had to rebuild a device all the way up to restoring apps from Titanium Backup. But it's such a pain. Maybe this weekend if nothing else turns up.
Two hours until my invitation expires. Anyone interested? Private me.
goattee said:
I don't have any confidence that using the official tool would solve the problem-- especially if the theory about the defective system partition image is the correct one-- I might just be reinstalling the same problem.
I'm more inclined to try the solution by echew010 in this thread:
https://forums.oneplus.net/threads/random-reboot.232446/
But I am not sure how bold I want to be. I'm not afraid of the concept of totally wiping the system partion. And it wouldn't be the first time I've had to rebuild a device all the way up to restoring apps from Titanium Backup. But it's such a pain. Maybe this weekend if nothing else turns up.
Two hours until my invitation expires. Anyone interested? Private me.
Click to expand...
Click to collapse
I'm not sure who's saying it's a corrupt system partition, I really don't think that's the case, if it were corrupt your phone wouldn't boot at all. Plus, the tool I linked to is perfectly fine, if there were something wrong with it then all of the people who have used it would be suffering all kinds of problems. You won't be reinstalling the same problem. That is your best option.
Transmitted via Bacon
---------- Post added at 12:46 PM ---------- Previous post was at 12:43 PM ----------
Plus, that fix you linked to one the OnePlus forum is almost doing the same thing, but it is missing some steps, and it would take longer. If you don't have confidence in the official tool then by the same logic you shouldn't have confidence in this other fix either, they both install official builds of CM11S onto your device. The official tool is more thorough, it is quicker, it is what you should be doing.
Transmitted via Bacon
I haves the same Problem with 44s. I try to revert back to 33r so I don't have random reboots
timmaaa said:
I'm not sure who's saying it's a corrupt system partition, I really don't think that's the case, if it were corrupt your phone wouldn't boot at all. Plus, the tool I linked to is perfectly fine, if there were something wrong with it then all of the people who have used it would be suffering all kinds of problems. You won't be reinstalling the same problem. That is your best option.
Transmitted via Bacon
---------- Post added at 12:46 PM ---------- Previous post was at 12:43 PM ----------
Plus, that fix you linked to one the OnePlus forum is almost doing the same thing, but it is missing some steps, and it would take longer. If you don't have confidence in the official tool then by the same logic you shouldn't have confidence in this other fix either, they both install official builds of CM11S onto your device. The official tool is more thorough, it is quicker, it is what you should be doing.
Transmitted via Bacon
Click to expand...
Click to collapse
You've convinced me with your logic that the official tool is the preferable approach of the two. I probably will try it in the next few days.
By the way, I followed advice to open a support ticket with OnePlus. Someone got back to me within 24 hours. I was asked to send them a video showing a random reboot. Am I supposed to keep a camera pointed on my phone 24 hours while waiting for a reboot?
Chikamru said:
I haves the same Problem with 44s. I try to revert back to 33r so I don't have random reboots
Click to expand...
Click to collapse
How long ago did you revert? Did the random reboots stop completely? Or do they just happen less frequently?
I'm on the same boat. Support is totally useless. For the past month or so they keep asking me to send them a video showing that my phone is rebooting randomly and all kinds of similar stupid requests.
I saw people talking about racing conditions when the device's storage is encrypted. For me this is a must or I won't get corp email. But I went through the various tools that would make me 100% "factory clean" and yet, the phone reboots just by sitting on my desk.
When I had encryption enabled, I'd come back home from work and find it beeping at the enter your password to decrypt screen. Now I keep it super clean, and don't encrypt it, don't do anything but enter my google ID/passwd to setup the device as new. When I check it, uptime is rarely more than an hour or two, so it reboots again, but comes back to a working state. I wonder if people, generally not encrypting, don't even notice when their device reboots.
I've finally got forwarded to some RMA person who said he'd send me the papers to get a new phone. Unfortunately, that has also taken days of silence now.
Very frustrating I can't use the OPO with its original ROM, after many years of flashing all kinds of ROMs to anything from Nexus One to my the N5 I went back to until the OPO gets fixed, to several Samsungs, LGs and HTCs and having FCs, some reboots, very stable builds, but never anything like this.
timmaaa said:
The problem with this situation is that there can be way too many causes for random reboots, we're talking dozens and dozens and dozens. So pinpointing exactly what's causing your particular device to reboot is virtually impossible.
Click to expand...
Click to collapse
Of course you are correct that there are many variables that can be the immediate cause of the reboots. But what cannot be denied is that so many users are experiencing the problem across various CyanogenMod versions. Because there are so many users, it's hard to believe that it's a few buggy user-installed apps causing the problem.
My favorite theory is that OnePlus has defective drivers. It reminds me of the effort to create custom ROMs for the Samsung Galaxy Tab 7.7 (GT-P6800). Samsung would not or could not release the wifi driver into the developer community. Same story with the ASUS Transformer TF101. ROM developers created pretty good ROMs but their degree of success depended heavily on whether they could scavenge drivers from cousin products. The Transformer efforts succeeded. The Galaxy Tab 7.7 custom ROMs still have some anomalies.
marvinandro said:
I'm on the same boat. Support is totally useless. For the past month or so they keep asking me to send them a video showing that my phone is rebooting randomly and all kinds of similar stupid requests.
Click to expand...
Click to collapse
I created two videos.
One shows a UI freezing issue that I experience periodically. I'm guessing it's a defect in interfaces to the Android System UI module.
The other demonstrates how the phone has rebooted on a few occasions when it receives an incoming call.
I saw people talking about racing conditions when the device's storage is encrypted. For me this is a must or I won't get corp email. But I went through the various tools that would make me 100% "factory clean" and yet, the phone reboots just by sitting on my desk.
Click to expand...
Click to collapse
I am betting that it's not the encryption itself that's the underlying cause. My guess is that the encryption/decription software layer is just more intensively interacting with an underlying bug or defect. Could it be a defect in physical memory? A poorly formed system partition? (One of the contributors here made a credible dismissal of that theory.)
I've finally got forwarded to some RMA person who said he'd send me the papers to get a new phone. Unfortunately, that has also taken days of silence now.
Click to expand...
Click to collapse
Please keep us updated when/if OnePlus does follow up on this.
Very frustrating I can't use the OPO with its original ROM, after many years of flashing all kinds of ROMs to anything from Nexus One to my the N5 I went back to until the OPO gets fixed, to several Samsungs, LGs and HTCs and having FCs, some reboots, very stable builds, but never anything like this.
Click to expand...
Click to collapse
We agree. I have had quite a stable of Android devices. But nothing like this coming direct from the manufacturer. I really like the phone when it's running properly. The display could be better in daylight but I could live with that. I suspect that the next OnePlus handset will benefit from lessons in their first release. I just don't want to suffer because I voted for a promising startup.
OnePlus would be wise to humbly acknowledge that there are two widely experienced problems: random reboots and periodic UI freezes. And then if they want to stick around they have to release a ROM that completely eliminates those two showstopper defects.
goattee said:
How long ago did you revert? Did the random reboots stop completely? Or do they just happen less frequently?
Click to expand...
Click to collapse
Last week Wednesday. Until now I have no reboots.
About 12 hours ago I did a clean flash to the official SlimROM 4.44. I followed the instructions on the official website. (I've linked to the site in the previous sentence.)
Immediately the phone seemed to be running smoother. No UI freezing and no random reboots so far. I can't be sure whether simply wiping the partitions solved the problem or whether it was something about 11s. But I like the features of SlimROM well enough that I don't feel the need to test other ROMs yet.
I'll come back here if the problems come back.
goattee said:
About 12 hours ago I did a clean flash to the official SlimROM 4.44. I followed the instructions on the official website. (I've linked to the site in the previous sentence.)
Immediately the phone seemed to be running smoother. No UI freezing and no random reboots so far. I can't be sure whether simply wiping the partitions solved the problem or whether it was something about 11s. But I like the features of SlimROM well enough that I don't feel the need to test other ROMs yet.
I'll come back here if the problems come back.
Click to expand...
Click to collapse
It's the end of the business day. The phone has not caused any problems or surprises. If this phone came out of the box in this new state, I would have been a much happier person for the past three weeks!
Well i've also tried echew010's solution and so far it seems promising! To anyone suffering from random reboots this is what i did: http://forum.xda-developers.com/one...us-one-stock-cm11-t2839870/page5#post59362462
Hello all,
I am new here as I have stayed faaaaar away from androids for many years (flips and windows). I tried to do a search on the boards but, unfortunately, my phone keeps freezing up and this is my only out to the web ATM. Anyways ever since my device prompted for me to download the newest update I wearily decided to go ahead. Ever since then my phone gets stuck on the lock screen, lags ridiculously, and refuses to send a message via text...not to mention random freezes. Is there anyone else having this problem. I know its new, but is this a yet known issue with this phone? I hate to factory reset it again if it is not going to fix anything?
Thank you,
Norseman
JPNorseman said:
Hello all,
I am new here as I have stayed faaaaar away from androids for many years (flips and windows). I tried to do a search on the boards but, unfortunately, my phone keeps freezing up and this is my only out to the web ATM. Anyways ever since my device prompted for me to download the newest update I wearily decided to go ahead. Ever since then my phone gets stuck on the lock screen, lags ridiculously, and refuses to send a message via text...not to mention random freezes. Is there anyone else having this problem. I know its new, but is this a yet known issue with this phone? I hate to factory reset it again if it is not going to fix anything?
Thank you,
Norseman
Click to expand...
Click to collapse
Have you tried a factory reset?
fubugang said:
Have you tried a factory reset?
Click to expand...
Click to collapse
Not yet what little I have been able to read around the web, before it locks up again, was it wasn't helping. So I wanted to ask before I wasted my time and it has to wait for my 12 hour shift. Just lack of communication from my site really stinks and may put some things behind.
Only problem I had with the update was serious battery drain from Android OS and System way higher than normal.
Thank you for backing up my reasons for never updating phones, computers, tablets, electronics in general, until I actually need to!
Tha Watcher said:
Thank you for backing up my reasons for never updating phones, computers, tablets, electronics in general, until I actually need to!
Click to expand...
Click to collapse
Generally you 'need to' update things when a new version is released because there are usually security enhancements that can be exploited with older firmware.
Hello everyone! I'm in need of advice and I'm not sure where I can find it.
A couple of days ago, I've been tricked into buying a Nexus 5 from a shady guy. I know, shame on me, I was simply stupid and I can't say what was in my mind.
Long story short, after buying the phone, I noticed that the charger doesn't work so I tried contacting the guy, but he vanished - his profile, with all his adds, was deleted 2 hours after selling me the phone.
I searched the phone's IMEI and it doesn't appear to be stolen, which makes me believe there is something rotten in Denmark with this phone. So far so good, it appears to work (although, it has some problems connecting to wi-fi and freezes from time to time), but I keep asking myself - what in the hell is wrong with it?! What should and what can I do to verify this phone and calm my worried mind? In case the hardware is ok, doing a hard reset would fix all potential threats that arise with a phone in this situation - it has been rooted and I'm not sure what might be on it, malware and stuff like that?
Try to install a custom ROM on it & If it's a fake one, it won't flash it... Then you can be sure that you have been tricked into buying a shady N5
I recommend flashing the latest MM release from Google using fastboot commands. After flashing all partitions, flash the userdata.img file, immediately boot into recovery, wipe data, wipe cache, reboot.
The intermittent wifi could be be to a hardware or software issue but you won't be able to know for certain until you eliminate the software possibility by flashing back to stock.
audit13 said:
I recommend flashing the latest MM release from Google using fastboot commands. After flashing all partitions, flash the userdata.img file, immediately boot into recovery, wipe data, wipe cache, reboot.
The intermittent wifi could be be to a hardware or software issue but you won't be able to know for certain until you eliminate the software possibility by flashing back to stock.
Click to expand...
Click to collapse
Thank you for your prompt reply. I'm not really familiar with android or IT, in general. Is this tutorial adequate for flashing the latest MM release?
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Yes, that tutorial should be fine.
audit13 said:
Yes, that tutorial should be fine.
Click to expand...
Click to collapse
Ok, I followed the steps listed here droid-life.com/2013/11/05/how-to-flash-nexus-5-factory-images and I believe I've installed the latest MM. I wiped the data/factory reset and it appears to work.... But the wi-fi still has issues, although it's significantly better now.... What does this mean? Also, can I now connect to my google account and others without the fear of malware or spyware or anything like that?
I would start by installing Avast Antivirus - Play Store.
It is possible that there is a problem with the wifi chip in the phone. I have two motherboards where wifi cannot be enabled anymore.
Still having wifi issues. I think you are right. Someone said that 5.0.1 and 5.1.1 burn some chip on the motherboard... Anyways, thank you for your kind support!
Who knows what happened to the phone before? Maybe the guy used it to make calls in the rain and the components have been exposed to water? Just to make sure that this is not the case, you could open the device and check if you see some water marks. If this is the case, use rubbing alcohol to clean the PCB, let it dry and assemble the device again.
That´s always a problem with devices you get from shady guys. You never know what happened to them before.
In the last three months or so my phone has been struggling. I don't know if it is a memory leak or bad memory flash as every so often the phone will be busy doing something and completely lock up. I'm having to restart my phone once of twice a day. I use Android Auto and need to restart the phone and clear all recent apps in order to get it to work.
I have tried factory resetting the phone, clearing the caches and installing CM13 but still get these slow downs and crashes. Is there anything else I can do or do I admit defeat and get a new phone?
nimdy said:
In the last three months or so my phone has been struggling. I don't know if it is a memory leak or bad memory flash as every so often the phone will be busy doing something and completely lock up. I'm having to restart my phone once of twice a day. I use Android Auto and need to restart the phone and clear all recent apps in order to get it to work.
I have tried factory resetting the phone, clearing the caches and installing CM13 but still get these slow downs and crashes. Is there anything else I can do or do I admit defeat and get a new phone?
Click to expand...
Click to collapse
Have u tried factory flashing? I've also heard of lol downgrading letting run to c if there's any difference than upgrading back to the latest. Another question is do u root your phone and if so do u use or tweak your phone? And my personal unfavored, what kind of apps do u use? Do they take all your memory? Try some of these and also think about these and reply back, I'd like to help you the best I can (I'm no super expert tho, the most I've done is replaced my nexus screen and camera parts)
edit: also be careful of those custom kernels, tweaking around those frequencies can lead to your phone spazzing , hint, hint, over clocking.
Aurey24 said:
Have u tried factory flashing? I've also heard of lol downgrading letting run to c if there's any difference than upgrading back to the latest. Another question is do u root your phone and if so do u use or tweak your phone? And my personal unfavored, what kind of apps do u use? Do they take all your memory? Try some of these and also think about these and reply back, I'd like to help you the best I can (I'm no super expert tho, the most I've done is replaced my nexus screen and camera parts)
edit: also be careful of those custom kernels, tweaking around those frequencies can lead to your phone spazzing , hint, hint, over clocking.
Click to expand...
Click to collapse
I have upgraded and downgraded the software but that doesn't seem to help. Apps are the normal social networking and utility apps. No fast paced games or other battery sucking apps. I haven't messed with custom kernels and OCing on this device.
Hmm that is weird, u even tried clearing the cache too hunh? Let's see, have u ever taken a look inside then? Maybe cleaning it out? I've had to clean my phone before because it wouldn't turn on due to dust and whatnot inside it. That's really strange that you've even factory flashed and that didn't help, usually that'll clear up the problem, the reason I could think of is its reaching that eol point because it's just that time or u didn't take care of it (this obviously isn't the case I assume), or maybe it got damaged somehow, or maybe a good clean. Idk I'm just throwing out ideas. But really tho factory flashing should've solved that problem, flash it 2 times in a row lol
**Solved posting update in thread.
Purchased S21+ from Samsung online for Verizon Network, every OTA update since purchase results in it failing to the downloading screen with "
partition super Reason SUPER: Build-id does not match with the reference" I have been able to resurrect it successfully by entering the recovery mode and performing a factory reset. But each OTA update push results in the same issue.
Samsung wants me to either send them the phone or take to a repair location for a software refresh as they called it. Problem is nearest repair center is 3+ hours away from me or 5-7 day turn around on the mailed device with no backup phone.
Has anyone else encountered this and does anyone here have a solution to fix this myself? I am comfortable using Odin and flashing roms but not sure if this will fix it.
have you talked to verizon?
Post Nine said:
have you talked to verizon?
Click to expand...
Click to collapse
Yes, Spoke with their Tier 2 support. Tier 2 discussed the issue and implied a change of information for the phone would fix it. They transferred me to Samsung due to the phone being purchased direct from Samsung.
Ok so the problem seems to have been resolved. Here's what I did to fix it.
Downloaded the current firmware I had before the update from Sammobile.com. Using Odin I installed the firmware I was currently on. I had done this before on the last update that failed. But this time I gave it the user data info and did use the Home CSC in an effort to reset everything.
Phone came back online functioning normally with everything wiped. I connected to WiFi and let the first of 2 updates download then run. Success . First OTA that's been successful on the phone. Then went for update #2. Failed, but rebooted this time and gave me an Error 402. Tried again a little later, same WiFi. It redownloaded the update and success again.
So it seems it needs a very very stable internet connection and the full wipe fixed the build id mismatch.
Also before attempting updates highly recommend having all your 2FA accounts either backed up, a second authenticator on another device or turned off. Its a real PITA to get back into all your accounts when your authenticator app gets wiped unexpectedly.
Hope this helps someone else!
CBH60 said:
Hope this helps someone else
Click to expand...
Click to collapse
Thank you!!! I was stuck on this screen all day!
I had restored my S22 Ultra, as a last resort to troubleshoot the shut down/reboot issue I, like many others, have been experiencing. When my phone then updated itself afterward, the install failed and I was stuck. I just happened to find this post of yours, while I was researching some info someone at the Geek Squad gave me, and told me to try it when I got home. The print out he gave me was a word for word copy of your solution! It totally worked, and I am back in. Now to see if the shut down/reboot issue recurs..... I suspect it will, I'm thinking it has something to do with my battery, which I can't remove.
Ardera_Sempre said:
Thank you!!! I was stuck on this screen all day!
I had restored my S22 Ultra, as a last resort to troubleshoot the shut down/reboot issue I, like many others, have been experiencing. When my phone then updated itself afterward, the install failed and I was stuck. I just happened to find this post of yours, while I was researching some info someone at the Geek Squad gave me, and told me to try it when I got home. The print out he gave me was a word for word copy of your solution! It totally worked, and I am back in. Now to see if the shut down/reboot issue recurs..... I suspect it will, I'm thinking it has something to do with my battery, which I can't remove.
Click to expand...
Click to collapse
Hey did you ever get this screen again? And were OTA updates normal after you flashed?
OTA updates keep failing for me on my S22+, either at 25% causing it to go back to the old firmware with an error message, or getting bricked showing that screen. I've tried to reflash and then update and so far only solution is flashing the update through Odin every time. I have had only 2 successful OTA updates since I got this phone in April
AliRAS said:
Hey did you ever get this screen again? And were OTA updates normal after you flashed?
OTA updates keep failing for me on my S22+, either at 25% causing it to go back to the old firmware with an error message, or getting bricked showing that screen. I've tried to reflash and then update and so far only solution is flashing the update through Odin every time. I have had only 2 successful OTA updates since I got this phone in April
Click to expand...
Click to collapse
I did not have any further issues with updates failing, and getting this screen again. I DID have to send my phone back to Samsung twice though for repair, because of the constant rebooting issue. They could NOT repair that issue, so I ended up getting a refund for the phone. Due to their p**s poor customer service (more than a month later I'm still trying to get them to return the charger for the phone, that they said I HAD to send back with the phone for testing), I will (very unhappy) be purchasing an iPhone. Never buying Samsung again.
Ardera_Sempre said:
I did not have any further issues with updates failing, and getting this screen again. I DID have to send my phone back to Samsung twice though for repair, because of the constant rebooting issue. They could NOT repair that issue, so I ended up getting a refund for the phone. Due to their p**s poor customer service (more than a month later I'm still trying to get them to return the charger for the phone, that they said I HAD to send back with the phone for testing), I will (very unhappy) be purchasing an iPhone. Never buying Samsung again.
Click to expand...
Click to collapse
Damn that sucks never heard of them needing the charger as well for tests, that is a bit odd. The reflash seems to have fixed the rebooting issue I had when I first got my S22+ not sure if I should gamble with trying to update again after the last one failed. Might just wait for One UI 5 and do a dirty flash through Odin and if it doesn't give any problems I'll just flash the security updates every so often I guess. Saves me the stress haha.