Hi,
I tried to install the latest software update which was available in Software Updates on my SM-A107F phone.
It downloaded with no issues first time and I was prompted to restart and install the update, which I did.
The update process starts and appears to run to completion (gets to 99% of "Installing System Updates...") and then the screen goes blank / phone turns off.
I've restarted the phone multiple times with consistent outcomes. I have not rooted this phone, installed TRWP or anything similar. I think I may have enable developer mode options but nothing else.
Is anyone else experiencing this issue? And have you been able to get around it?
Regards
K
I have exactly the same issue , 99% installing update and shuts down!
data on the phone are really important to me so I was afraid to flash the phone , please if anyone knows how to fix this issue without losing data let us know...
skysheykh said:
I have exactly the same issue , 99% installing update and shuts down!
data on the phone are really important to me so I was afraid to flash the phone , please if anyone knows how to fix this issue without losing data let us know...
Click to expand...
Click to collapse
Related
Anyone had a problem updating to 651.167.26.en.EU??
I've tried to update (many times), the phone shuts down starts the install, gets about half way then reboots. When it does reboot I get a message saying the update failed. I've even done a factory reset (which I hated) but now joy. Grrrrr
Has anyone had this issue and have you manage to solve it??
Also does anyone know what location the phone saves the update to?
Perhaps you're lucky it failed because I am having the following problem after the update:
After updating wireless is stuck and won't either turn on or off.. in settingsmenu on the wlan activate button it just says "error" in the second line. on push it says "activating" for some time the drops back to error. So my question: Does anyone else have this an what can I do to correct this?
PS: Moto Support just says Factory reset but there is upfront no way I am doing this without having tried anything else..
You could always just root it and install a custom rom. My app will will root it in 1 click.
BreakDroid
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
Hi all,
I've started to have an issue with my HTC One X+ where it won't automatically connect to (any) Wi-Fi.
If I then go to settings, Wi-Fi appears as 'Disconnected' but the slider button says 'On'.
If I try and turn it off, it wont turn off. Then 'settings' ends up hanging.
The only way around it is a reboot, but this happens every day now, seems to normally happen when I return home and expect it to drop 3G and connect up to my homes Wifi (as it always has done?).
I really don't want to do a factory reset... I can't say that I've changed anything to cause this...
Does anyone else have the same issue and have you been able to resolve it?
Thanks
I'm having the same problem, but for me I know it didn't start happening until after I did the update. Not sure how to fix either.
Are you both on stock ROM?
I had similar problem after OTA update from AT&T. It was worse than yours since I wasn't able to enable WIFI at all, it just stuck on the "turning on" state. I was able to fix the problem by re-flashing the boot.img following this post:
http://forum.xda-developers.com/showthread.php?t=2235248
Btw my phone is rooted but running the stock rom.
Hope this helps.
KH_Lionheart said:
I'm having the same problem, but for me I know it didn't start happening until after I did the update. Not sure how to fix either.
Click to expand...
Click to collapse
Yes I'm stock and locked right now because I have some problems I need to return the phone under warranty for, and I have the problem where it is just stuck trying to turn on. Thanks for the link, but until I switch this one under warranty I don't want to do any modifications to void the warranty. As soon as I get the new one I will be unlocking and rooting it immediately, not doing so is killing me right now.
Well just reboot in bootloader mode and flash the correspondent RUU. You know how to find the good version?
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Have you performed a factory reset? (It will delete all your data and apps)
rp-x1 said:
Have you performed a factory reset? (It will delete all your data and apps)
Click to expand...
Click to collapse
Yes, when the phone was new and the restarts were annoying. It fixed it for 1 day. The next day it was restarting again.
This would point to an app you've installed causing the issue. Factory reset again and install each app one by one until the restarts happen to find out which.
SteveTM said:
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Click to expand...
Click to collapse
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
cmstew said:
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
Click to expand...
Click to collapse
Will try it when I'll have time for it, thanks for the help!
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.