Morning all.
I got an OTA update available notification on my wife's phone and started the update. Its been well over 1.5 hours and it seems to keep repeating the "installing update" step in a loop.
I thought I check here for suggestions before I rebooted the phone. Anyone faced similar situation? Note the phone is unrooted.
A Google search didn't find anything similar.
You upgrade from lollipop? Anyway, try to backup all the data from the device. After that try to do a factory reset, maybe it's will help. Maybe WiFi problem?
Related
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
m_hawkmoon said:
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
Click to expand...
Click to collapse
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Theonew said:
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Click to expand...
Click to collapse
The phone rebooted automatically. Did not give me the chance to do anything beforehand.
As you said the phone was soft bricked so when i got home that day i just fixed it. No problem. However I am really really into getting to find out how a 1 day old back up can get corrupted.
Does anyone know why the Samsung update button when it pops up to check if there is any updates available. takes so damn long?
I clicked it one today, and it showed and prompted me to install the new update, yet when i tried to click it"Because want to save root i had to stop it to have it enabled" I came back to installing it, and it just hangs there swirling :/. Tried also FC - Google Services, and Clearing Data, then tried software updating, yet nothing.
It's been like this for the last 5 minutes
Any other way for me to reset and speed up this thing? is just stuck at "checking for software update"
Thank you guys!
Kikoshi said:
Does anyone know why the Samsung update button when it pops up to check if there is any updates available. takes so damn long?
I clicked it one today, and it showed and prompted me to install the new update, yet when i tried to click it"Because want to save root i had to stop it to have it enabled" I came back to installing it, and it just hangs there swirling :/. Tried also FC - Google Services, and Clearing Data, then tried software updating, yet nothing.
It's been like this for the last 5 minutes
Any other way for me to reset and speed up this thing? is just stuck at "checking for software update"
Thank you guys!
Click to expand...
Click to collapse
simply because you tablet are rooted.
You can't receive OTA's. If you did, root would be removed as soon as you ran it.
Go to Sammobile and download the latest stock rom for your area... Flash with Mobile ODIN to keep root...
Last night I decided to switch to ART from Dalvick runtime. Ever since, when android finishes loading, I get the error message "Unfortunately, Android System has Stopped." I've tried returning to stock (I'm rooted) and neither of my windows computers can see my phone which is weird because I unrooted my LG G3 recently with no problems. I've performed a hard (factory) reset numerous times. Sometimes the android system loads up OK but as soon as I reboot or power down I have the error message again. I'm at my wit's end. I can't return the phone because it's still rooted and I can't get it to work. When it boots, the LG screen appears normally. The At&t screen appears normally. Please help! I'm desperate.
If you're okay with losing info, give this a shot. I'm not sure exactly why it's doing this unless you had xposed framework before. Anyway, follow the steps and it should fix it. I'm not sure if you've tried going into the boot loader yet and doing a factory reset through there. So you can try whatever you like
http://forum.xda-developers.com/showthread.php?t=2785089
I can't get a computer to recognize the phone. I have tried a hard reset and I still get the error message. Any other ideas?
I had the same issue after I tinkered with something I shouldn't have tinkered with. I think I installed GravityBox, didn't like what it did, tried to factory reset, and started getting the Android System error consistently.
That link mcnick posted will serve you well. I would however use this thread since it's tailor made for the AT&T variant.
http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827
Hello fellow xda-ers,
I have a OnePlus One, but i cannot seem to update the phone.
What is the exact problem?
- there is a system update ready, so i download the update and it asks me to install and then it tries to reboot
- the phone shuts down and doesn't reboot, i have to manually turn the phone off which makes the update sequence stop.
- the phone tells me again theres a update, but it doesnt reboot after it shuts down.
- even just giving the phone the command to reboot, just shuts the phone off and the phone doesn't reboot.
What did i try?
- via oneplus toolkit (mac) i flashed it to stock default, but still the problem persists.
- i flashed a 5.1.1. firmware straight from cyanogen mod, but still the problem persists.
- i flashed a custom recovery (while unchecking the update cm recovery), but the problem still persists.
I don't know what to do... Anybody have advice? It would be much appreciated.
I am pretty aware of what to do and not to do, i have been flashing phones since the iPhone 3gs. But this is just odd.
I was having similar problem. Except mine was booting into the bootloader. From there I tried to manually install the update. It kept failing so I gave up. Then about a week later (today) I let it try to install and it seemed to be working, except when it finally booted back up, it had completely wiped my phone!!! Now I'm midway though reinstalling all my apps and it gives me the "There's an update available for you phone". So apparently it didn't even update in that process.
I've got the exact same problem here.
I rooted my device using king root, in that state i got the notification for an official update. I went to settings, about phone, and updated. after it rebooted, it started installing the update. halfway through the the status bar was a little less half full, it stopped and booted normally. It said the the update installation was unsuccessful. I remembered that i had the stupid kingroot, so i uninstalled it, it rebooted, everything so far so good. i went just to double check the OS version currently installed, still on 5.0.2 Lollipop. This time i went ahead and started installing the update. I noticed that this time it looked fine because the status bar didn't stop halfway through like last time. It kept going until it was more than half full. So I was like "ok, lets just leave it for now to do its job and ill look at it later" Later, I looked and it had a black screen with the android model with an exclamation mark. It said: "No Command" I decided not to **** with it, so i jut left it. I went to Motorola's website, and chatted with one of their technicians. She told me to factory reset it. She gave me instructions on how to do that, Which those instructions did not work. I went on YouTube and figured out a way on how to get into recovery mode and factory reset it, and that was what i did of course. Now all it does is boot, show me android model, power off. Then it keeps doing the same thing over and over until the battery dies, or i force to shut down from recovery mode. BTW i still can access recovery mode, and everything is useless and leads to boot-loop thing i just mentioned. Please help i feel like i really ****ed it up.
XDA Visitor said:
I rooted my device using king root, in that state i got the notification for an official update. I went to settings, about phone, and updated. after it rebooted, it started installing the update. halfway through the the status bar was a little less half full, it stopped and booted normally. It said the the update installation was unsuccessful. I remembered that i had the stupid kingroot, so i uninstalled it, it rebooted, everything so far so good. i went just to double check the OS version currently installed, still on 5.0.2 Lollipop. This time i went ahead and started installing the update. I noticed that this time it looked fine because the status bar didn't stop halfway through like last time. It kept going until it was more than half full. So I was like "ok, lets just leave it for now to do its job and ill look at it later" Later, I looked and it had a black screen with the android model with an exclamation mark. It said: "No Command" I decided not to **** with it, so i jut left it. I went to Motorola's website, and chatted with one of their technicians. She told me to factory reset it. She gave me instructions on how to do that, Which those instructions did not work. I went on YouTube and figured out a way on how to get into recovery mode and factory reset it, and that was what i did of course. Now all it does is boot, show me android model, power off. Then it keeps doing the same thing over and over until the battery dies, or i force to shut down from recovery mode. BTW i still can access recovery mode, and everything is useless and leads to boot-loop thing i just mentioned. Please help i feel like i really ****ed it up.
Click to expand...
Click to collapse
Hello,
I'd recommend you to restore your device back to stock firmware Restore to Stock][XT1068][All Dual Sim Model][4.4.4] with fastboot.
Also, I would advice you not to flash bootloader again. (Since if yours is updated with marshmallow one, flashing the older one (downgrading) might end in a brick).
-Vatsal
last step fail
Vatsal said:
Hello,
I'd recommend you to restore your device back to stock firmware Restore to Stock][XT1068][All Dual Sim Model][4.4.4] with fastboot.
Also, I would advice you not to flash bootloader again. (Since if yours is updated with marshmallow one, flashing the older one (downgrading) might end in a brick).
-Vatsal
Click to expand...
Click to collapse
at the last step, it fails to verify the package and aborts package installation. what now?
waseem98 said:
at the last step, it fails to verify the package and aborts package installation. what now?
Click to expand...
Click to collapse
Hello,
You may try posting your query in the thread I linked above with all relevant logs, the experts there maybe able to assist you.
-Vatsal