So, I recently installed an ota patch from AT&T (apparently it was supposed to make the gps more accurate or something?). Since then I noticed that my battery started draining very quickly, so I entered 'top' in a terminal and found out there was a process called 'applypatch' taking up 50% of the cpu.I can't use 'killall applypatch' because it's a root process, and apparently the update also got rid of my root.
I've already tried a factory reset, but that didn't seem to help. Also, I doubt it's still installing the patch, because I left it on all of last night and it's still going at it. The bootloader is still locked, so If possible I'd like to avoid messing with that. This is my only GSM compatible phone, and I paid a lot for it.
Should I just try rooting it again and try killing the process, or do you guys have any other ideas?
Thanks!
kratanuva said:
So, I recently installed an ota patch from AT&T (apparently it was supposed to make the gps more accurate or something?). Since then I noticed that my battery started draining very quickly, so I entered 'top' in a terminal and found out there was a process called 'applypatch' taking up 50% of the cpu.I can't use 'killall applypatch' because it's a root process, and apparently the update also got rid of my root.
I've already tried a factory reset, but that didn't seem to help. Also, I doubt it's still installing the patch, because I left it on all of last night and it's still going at it. The bootloader is still locked, so If possible I'd like to avoid messing with that. This is my only GSM compatible phone, and I paid a lot for it.
Should I just try rooting it again and try killing the process, or do you guys have any other ideas?
Thanks!
Click to expand...
Click to collapse
You are not the only one with that problem. I have the exact same issue. Process chewing up the CPU and if you kill it the process comes right back. Hopefully someone has a good answer as to how to fix it. I actually have 2 of the phones and one is rooted, second one is not. The unrooted phone does not have the same issue as the rooted phone.
I'm having the same problem with my Atrix. Phone is stock and unrooted. Never had an issue until I installed the latest update.
Well I got a response back from Motorola about the issue. These were their recommendations.
1. Reboot phone. Duh....
2. Uninstall any apps that you installed when the problem started. Uh, it was the OTA update... Cannot be uninstalled I do not think.
3. Clear Cache partition from Fastboot menu. That did not do anything.
4. Factory reset the phone. I hate doing that. Doubt it fixes anything but I will do it anyway.
I asked them about option 5 if 1-4 did nothing and he said call and talk to support.
Just an update...
Maybe someone knows how to just kill the process. It is obviously doing nothing as the phone is already updated to 4.5.145 according to the phone info.
I've just had a quick look around about the 'apply patch' process. Not that it helps you but this problem has been ongoing since at least android 1.6!!! Unfortunately solutions to the problem were few and far between - the main one would be to roll back the update you received (if you can).
Rooting and then trying to find the process and freezing the 'apply patch' process is another (again, I didn't find much about how to do that) as is unlocking the bootloader and putting installing a custom rom is another option for you. I know you don't feel comfy unlocking your bootloader but it isn't as bad as it sounds.
If you do decide to go the unlocking way then there are guides on here which will help you.
Edit: just seen this over in the 'general' section http://forum.xda-developers.com/showthread.php?t=2145316 ... the very same problem you are having.
Ok, just to hopefully keep this going I have tried these additional steps.
Root phone.
Unroot phone
Re-root phone
Try multiple startup program apps to kill it, none show anything besides installed apps.
None work. applypatch still taking 49% cpu
Maybe there is a way to edit androids startup config file to make it stop? Not a Linux/android guy so hopefully someone smarter than me has the answer to that.
If you've rooted the phone, you might as well have deleted or renamed that program... That's what I would do.
Same problem with my Atrix........I've been following this thread and have found a temp fix that works for me. I say temp as the applypatch process will show up again on reboot
1.) Gain Root Access
2.) Download OS Monitor from PlayStore (this will show you all processes running on Android OS)
3.) Run OS Monitor ...."applypatch" should be at the top of the list with a high Load % (Note: Under Settings enable ROOT mode)
4.) Long press on applypatch process and select kill process and allow superuser/root access...should terminate
This has been working for me so far so I signed up to share with you all.....hope it helps.
And heres to hoping for a more permanent:good: solution to this issue
Related
Hope you can help me - I am desperate to halt the OTA update for my galaxy s4 -
based on everything I’ve read, Samsung did a really bad job on this update, 4.4.2, and they are currently rolling out 4.4.3 and 4.4.4, but of course, the s5 is getting it well before we are.
anyway,
I have been “happily” running 4.3 and just dealing with the bluetooth issues, found enough hacks/fixes for the wifi issue that i have been ok with it since getting 4.3 in November.
There are just too many unworkable issues of battery drain, overheating, losing apps, pics, etc etc etc for me to risk the update to 4.4.2.
HERE’S MY PROBLEM - Somehow, altho i'm fairly technical, the update finally got on my phone (after having kept it off for months) and for the past month or more, I've just been
dealing with the notification, putting it off for 24 hrs at a time.
I guess it finally decided not to allow me to do that any longer, and started the installation without permission. i stopped it by pulling the battery, but when i try to start in recovery mode just so i can clear cache and hopefully reboot without actually installing the new os, I cannot - it goes through (some of) the motions but when i let go of the power button as i should when it's running normally, and would get the options of factory reset, clear cache, et al, it just brings up the android bot and shows that it is continuing to install where it left off. I’ve done this numerous times.
Tried different methods of button-holding and other trouble-shooting based on massive searching, but always get the same result. and I can only pull the battery to stop it.
Am I stuck? Do I have to install now at this point?
I do not want to perform factory reset, guess I'd rather install the 4.4.2 s/w. (altho I can't even get to that option at this point)
Sincerely hope someone out there will respond – I've posted to multiple sites, and no one is responding - gonna have to turn my phone back on at some point soon...
Thanks in advance!!
Roxanne
rkohlin said:
Hope you can help me - I am desperate to halt the OTA update for my galaxy s4 -
based on everything I’ve read, Samsung did a really bad job on this update, 4.4.2, and they are currently rolling out 4.4.3 and 4.4.4, but of course, the s5 is getting it well before we are.
anyway,
I have been “happily” running 4.3 and just dealing with the bluetooth issues, found enough hacks/fixes for the wifi issue that i have been ok with it since getting 4.3 in November.
There are just too many unworkable issues of battery drain, overheating, losing apps, pics, etc etc etc for me to risk the update to 4.4.2.
HERE’S MY PROBLEM - Somehow, altho i'm fairly technical, the update finally got on my phone (after having kept it off for months) and for the past month or more, I've just been
dealing with the notification, putting it off for 24 hrs at a time.
I guess it finally decided not to allow me to do that any longer, and started the installation without permission. i stopped it by pulling the battery, but when i try to start in recovery mode just so i can clear cache and hopefully reboot without actually installing the new os, I cannot - it goes through (some of) the motions but when i let go of the power button as i should when it's running normally, and would get the options of factory reset, clear cache, et al, it just brings up the android bot and shows that it is continuing to install where it left off. I’ve done this numerous times.
Tried different methods of button-holding and other trouble-shooting based on massive searching, but always get the same result. and I can only pull the battery to stop it.
Am I stuck? Do I have to install now at this point?
I do not want to perform factory reset, guess I'd rather install the 4.4.2 s/w. (altho I can't even get to that option at this point)
Sincerely hope someone out there will respond – I've posted to multiple sites, and no one is responding - gonna have to turn my phone back on at some point soon...
Thanks in advance!!
Roxanne
Click to expand...
Click to collapse
Are you rooted?
SiVisPacemParaBellum
OderintDumMetuant
stvn2569 said:
Are you rooted?
SiVisPacemParaBellum
OderintDumMetuant
Click to expand...
Click to collapse
Thanks for responding stvn2569!
Nope, not rooted.
But based on all my searching I sure wish I was and likely will the next phone.
Stock Verizon Galaxy s4 - 32gb - model # SCH-I545
(Sorry, should have put this in orig message)
THis summarizes some of the reason I don't want to update the OS - -
ack - can't post links - will have to type it out if you are interested in all the bugs Samsung saddled us with -
(most egregious is the battery drain, but others are quite serious and hard to live with too)
www(dot)androidpit(dot)com(slash)samsung-galaxy-s4-update-to-android-4-4-2-littered-with-bugs
rkohlin said:
Thanks for responding stvn2569!
Nope, not rooted.
But based on all my searching I sure wish I was and likely will the next phone.
Stock Verizon Galaxy s4 - 32gb - model # SCH-I545
(Sorry, should have put this in orig message)
Click to expand...
Click to collapse
You'll need to root the phone to stop the OTA notifications, it's all very easy.
Go to settings > security > allow installations from unknown sources, check the box
Go to www.towelroot.com
Click on the lambda, download and install the towelroot.apk
Click on "make it ra1n", reboot
Download "SuperSU" from the play store
Upon opening the app, it will prompt you to "update binaries". Do this using the "normal" option
Then download "Root Explorer" from the play store
Navigate to the system and system-priv app folders
In one of those folders you'll find "FWupgrade,apk" and "SDM.apk"
Delete those apk's and no more OTA updates:good:
joshm.1219 said:
You'll need to root the phone to stop the OTA notifications, it's all very easy.
.......
:
Click to expand...
Click to collapse
Thanks, Josh, I appreciate your trying to help, but if you read the original post -
I CANNOT TURN ON THE PHONE, hence couldn't get to settings if I wanted to, BUT - -
It is not the notification that is the issue -
the phone has finally downloaded the OTA update and IS INSTALLING IT. (every time I turn it on)
I DO NOT WANT THIS UPDATE INSTALLED. (see prior post for the reason - it's terribly buggy update - worse than what I have)
I have to figure out how to halt it - when I try to start in "recovery mode", it doesn't give me the options
it normally would - I won't start in a normal recovery mode.
It continues the OS update.
I noted all this in the original post - I completely understand how to get rid of the update notifications.
One doesn't even have to root the phone to do this, you can just rename the SDM apk (like add .bak or something)
Do you have ideas how to stop the installation? How I can turn phone on in recovery mode?
(note the steps I've taken to do that are also in the original post)
I know there are many people out there smarter than me about this - hoping you guys can help...,
rkohlin said:
Thanks, Josh, I appreciate your trying to help, but if you read the original post -
I CANNOT TURN ON THE PHONE, hence couldn't get to settings if I wanted to, BUT - -
It is not the notification that is the issue -
the phone has finally downloaded the OTA update and IS INSTALLING IT. (every time I turn it on)
I DO NOT WANT THIS UPDATE INSTALLED. (see prior post for the reason - it's terribly buggy update - worse than what I have)
I have to figure out how to halt it - when I try to start in "recovery mode", it doesn't give me the options
it normally would - I won't start in a normal recovery mode.
It continues the OS update.
I noted all this in the original post - I completely understand how to get rid of the update notifications.
One doesn't even have to root the phone to do this, you can just rename the SDM apk (like add .bak or something)
Do you have ideas how to stop the installation? How I can turn phone on in recovery mode?
(note the steps I've taken to do that are also in the original post)
I know there are many people out there smarter than me about this - hoping you guys can help...,
Click to expand...
Click to collapse
My bad, I would suggest booting into download mode and flashing the mk2 tar file with odin (3.09 recommended).
I didn't suggest renaming the file because it doesn't always work. Told my brother to do that on his Note 3 (no root method at the time) and it start downloading an OTA upon reboot one day.
joshm.1219 said:
My bad, I would suggest booting into download mode and flashing the mk2 tar file with odin (3.09 recommended).
I didn't suggest renaming the file because it doesn't always work. Told my brother to do that on his Note 3 (no root method at the time) and it start downloading an OTA upon reboot one day.
Click to expand...
Click to collapse
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
rkohlin said:
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
Click to expand...
Click to collapse
It is Power button click and hold volume down....
rkohlin said:
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
Click to expand...
Click to collapse
Like he said, download mode is Power+VolumeDown, press and hold.
UPDATE:
Well, never could get into download mode, so had to accept the OS update to KK 4.4.2
Guess I'm one of the lucky ones, (I do have a fairly new model S4) and I didn't lose apps or contacts.
however,
The Battery Life is TERRIBLE after the 4.4.2 update! Some WiFi issues too.
Seem to have fixed WiFi (for now anyway)
Been searching around and recalibrated my battery, am trying a battery life extender app,
turned off a huge bunch of Samsung and Google apps that evid constantly "ping" and use battery.
It's been a little better, but not a lot.
Hope for 4.4.4 to be available soon (heard 4.4.3 is not a good variant either)
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
JayWulf said:
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
Click to expand...
Click to collapse
You need to start over from scratch
post your fastboot getvar all (minus you serial.no and IMEI)
Most likely your using AT&T so if you have s-off you can flash these two and get back two stock. take the OTA Update then re flash recovery and root.
flash this first
http://fs1.d-h.st/download/00101/a1w/4.18.502.7 Custom Firmware.zip
fastboot oem rebootRUU
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot reboot bootloader
now stay on the bootloader
and run this RUU from your PC > http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Take the Over the air update and your all set to start rooting again.
clsA said:
post your fastboot getvar all (minus you serial.no and IMEI)
Click to expand...
Click to collapse
What is this, and how do I do it?
JayWulf said:
What is this, and how do I do it?
Click to expand...
Click to collapse
go to the folder where fastboot and adb are
open a command window (right click / command prompt here)
with the phone plugged into the PC
Type fastboot getvar all
it will output all the specs for your phone
remove the serial no and IMEI when posting it
what if your s-on
I'm having all the exact same problems except I'm 4.3 and s-on. Help please!
Gonna kinda bump this thread a bit because I've got another question - what about the "full unroot" option within SuperSU? Will this help the situation at all, or make it worse?
I ordered my Kyocera Hydro Icon from Freedompop and got it yesterday. I tried Root Genius, which seemed to work (by which I mean it asks me if I want to give root access to apps that need it, but does not allow user of the "su" command in Terminal Emulator). I then used a root app uninstaller and uninstalled a couple very harmless seeming things that the app said was safe to remove. Various forums said safe to remove. However, after doing that I'm now on a boot loop.
I did a factory reset from the boot menu (hold buttons, go to wipe data, etc.). However, my system still has the same issue and reboots unless I'm in Airplane mode (for the record, many people have reported this, and it's pretty obvious that some company triggers a reboot remotely when they don't like what they see on your phone, and that's why disconnecting prevents reboot). There were some Freedompop apps I uninstalled before, and they are still uninstalled after factory reset. I probably can't even return the phone because the KingoRoot app is installed and I can't remove it. I installed SuperSU, not sure exactly how it works, but it keeps telling me it wants to update and I can't go out of airplane mode to use the Internet.
So, after spending over 24 hours straight on this problem, frustrated the entire time, I found my way here. Though I was skeptical (having had much bad luck so far), I thought maybe a stock ROM would work. However, all links to any kind of ROM for this device on these forums were dead.
My understanding is the source was released for this device here:
tiny url .c om / ppbnlwo (used tinyurl to make it shorter so I could post it; goes to Kyocera Developer Support Downloads)
I'd like to know the following:
1) Will a ROM fix my device, removing Kinguser and all root-related changes I made?
2) Is there a ROM that someone can provide me with (along with instructions hopefully) to help me with this?
Thank you.
Hey all,
My phone updated today and ever since I cannot move past the initial lock screen. When unlocked, the UI appears to crash and send me back to the lock screen. My pin code works for turning the phone off, restarting the phone and putting it into emergency mode, which indicates some sort of UI crash.
Because this is a new account I can't post a link to a video of the issue directly, but the YouTube video code is: 8ZhlH-Tt-NU
I have tried the standard fixes like wiping the cache partition and booting into safe mode, but these don't seem to make any difference. Unfortunately I never logged into my Samsung account on this device, so their 'Find My Mobile' service is not an option. I am however signed into my Google account on the device and it does have wifi/network enabled.
The phone is running PPR1.180610.011/G965FXXU2CSA8
On the phones internal memory is a bunch of photos from a recent trip to Japan, I'm a fool for not backing these up sooner but I would hate to lose them.
Has anybody experienced anything like this before, and is there any way for me to get back into the phone, or atleast recover the photos that I took?
Thanks!
Edit:
One potential route out of this I can see is sideloading the same or a subsequent OTA update using ADB to hopefully fix the issue. Unfortunately despite some digging I can't find any updates that will allow installation from: PPR1.180610.011/G965FXXU2CSA8
If anybody has any information on this specific firmware version (Is it beta 3? beta 4? ect.), its installation path and where files relating to it may be listed/hosted it would be appreciated. Also how disasterous would it be to take a mismatched OTA upgrade and modify the metadata to allow it to be sideloaded onto the phone? I assume this would almost certainly break the OS completely but I'm not too sure.
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
profi_fahrer said:
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
Click to expand...
Click to collapse
Thanks for the reply Profi I had no idea using HOME_CSC would retain user data. I have tried flashing a few different versions of Pie (wish HOME_CSC) using Odin but with no luck, every time the phone boots I have the same problem. Do you know if there is a sure way to downgrade to Oreo while retaining user data? I have seen a few posts of people attemping this and getting stuck in bootloops, eventually requrining them to factory reset.
To give a final update on this. I attempted the Oreo downgrade, upon reboot the phone was stuck in a bootloop so I updated to Pie again. When the phone booted I tried the pin code as quickly as I could, and after some glitchy graphics on the screen it unlocked. From here I turn on the stay awake while plugged in feature in the developer options and managed to transfer all my data over to PC.
I don't believe it was the firmware changes that actually made any difference, because any further attempts to put my pin in, to remove the pin code for example, failed and cause the same crashing behaviour.
All data is recovered, I have factory reset the phone and all appears to be behaving as normal again. If anybody stumbles upon this with the same issue, all hope is not lost, but unfortunately I was unable to determine a realiable way to overcome it. It seems in this case it was just dumb luck.
Thanks for the assistance.
Hi all,
Last night my phone started to randomly reboot itself, even in Safe Mode! It's now to the point where I can't even login -- I enter my pin, the 'Phone is starting' overlay shows for a while, and then it suddenly reboots. I haven't installed a new app for at least 2 weeks at this point, and the reboot was happening before I updated my apps. After updating, things seemed to get worse maybe?
Is there any way I can salvage my phone or do I have to hard factory reset via hardware buttons?
Its called bootloop. you need to flash your phone to fix this problem and flashing can fix all the software issues of your device.
I was afraid of that... Just a bit worrying that it happened randomly when running stock.
Ok, thanks!
I had same issue when ran android 9 in 2019, however, I fix this issue by doing a clean flash. Yes, you will lose everything, so make sure you do a backup via google.
Tom_usborne said:
Its called bootloop. you need to flash your phone to fix this problem and flashing can fix all the software issues of your device.
Click to expand...
Click to collapse
If you didn't add an app or update that caused it either the boot load got corrupted or it's a hardware issue. The flash memory should not spontaneously get corrupted unless it's defective ie a hardware issue. However anything is possible... quantum physics.
More than likely it was a poorly written app or update that caused it. 3rd party launchers and power management apps are prime suspects. It may take a week or more to manifest its self as a boot loop. Any signs of system lagging or instability should be taken seriously as they are the only warnings you may get before a boot loop*.
A virus or rootkit** is another prime candidate.
Do a factory reset now. Be wary of which apps you load and avoid any updates until the system is know to be stable. Then add apps and updates one at a time. Updates many times aren't really needed.
Over a year ago I had 2 back to back boot loops on my Note 10+... yes, and 2 factory resets and full reloads.
The prime suspects were as I mentioned above. Neither one was reloaded after the 3red factory reset. A year latter that 3rd reload is still running fast and stable. Fun times
**if your Android version is 9 or above a factory reset will purge any virus or rootkit as long as you don't inadvertently reintroduce it. Be careful what apps you load and what you download.
If the Android version is 8 or below, they are suspectable to a nasty rootkit that requires a firmware reflash to purge. Pie and above are not.
1. For me, it was also itself rebooting, only while phone were in pocket / case. So do not use any of them (searched on reddit forum, was exactly same topic)
2. Maybe sim ejection tool is not correct be inside, don't often open and close it