I need some help. I woke up this morning and my phone will not stay powered on. It will boot but after about 3 minutes it will notify me that it's shutting down and then start up again and repeat the process. I'm rooted on 4.4. I'm thinking maybe my phone tried to automatically update me with the 4.4.2 update, but it doesn't seem like it. I can't seem to find the thread where it goes through deleting the update file. But other than that, I don't know what else it could be.
kashtrey said:
I need some help. I woke up this morning and my phone will not stay powered on. It will boot but after about 3 minutes it will notify me that it's shutting down and then start up again and repeat the process. I'm rooted on 4.4. I'm thinking maybe my phone tried to automatically update me with the 4.4.2 update, but it doesn't seem like it. I can't seem to find the thread where it goes through deleting the update file. But other than that, I don't know what else it could be.
Click to expand...
Click to collapse
When I tried to update to 4.4 rooted I had this issue. I went from stock 4.2.2(shipped) to 4.4. I had to downgrade to 4.2.2(camera update). Then when I rooted up to 4.4 I had the problem you had. I had to use RSD lite to reflash(i guess is the correct term) 4.2.2 then update to 4.4 as it didn't download 4.4 correctly the first time.
So it may have tried to update, but if it didn't download the update fully could be the problem.
Boot into recovery and clear cache, that should clear any pending ota until it downloads again.
you can freeze the moto-ota apk to prevent it from downloading.
Related
I'm running decrap 1.1...My phone automatically attempts to install the vzw update every day, usually around 5 AM. With CWM installed, it seems that when the phone reboots after the install, it prevents the upgrade from actually being put in place. In theory this is a good thing and prevents unwanted downloads. The problem is that it is preventing my alarm from working and I wake up every day with my phone in CWM recovery mode. Plus I was late to work today. So, I would actually like to try the vzw update and replace it with the revolt rom if I don't like it. Does anyone know where the VZW update gets stored so that I can flash it out of cwm? Any thoughts on this would be appreciated.
You will need to flash back to stock and remove root to have the update install, and then if you change your mind, you will need to downgrade to the old software before being able to root again.
Nooben said:
I'm running decrap 1.1...My phone automatically attempts to install the vzw update every day, usually around 5 AM. With CWM installed, it seems that when the phone reboots after the install, it prevents the upgrade from actually being put in place. In theory this is a good thing and prevents unwanted downloads. The problem is that it is preventing my alarm from working and I wake up every day with my phone in CWM recovery mode. Plus I was late to work today. So, I would actually like to try the vzw update and replace it with the revolt rom if I don't like it. Does anyone know where the VZW update gets stored so that I can flash it out of cwm? Any thoughts on this would be appreciated.
Click to expand...
Click to collapse
Do NOT install the update if you want root and Revolt. Just flash Revolt or Home-Less as instructed in their threads, and you will be good to go!!!
Hi there,
My N3 was never rooted and it received the forced OTA update. The update began while I was holding the phone. It rebooted but I was able to interrupt the process by pulling the battery out to turn off the device during the status screen when it was showing updating apps.
I never turned on my phone after that.
Does this mean my baseband has already been updated to N900AUCUBMJ5?
I ask because now want root using RDLV (N900AUCUBMI9_OneClickBin) but I don't know if it is safe since another user tried to downgrade to M19 after receiving the MJ5 and softbricked the N3.
Thanks.
testrak said:
Hi there,
My N3 was never rooted and it received the forced OTA update. The update began while I was holding the phone. It rebooted but I was able to interrupt the process by pulling the battery out to turn off the device during the status screen when it was showing updating apps.
I never turned on my phone after that.
Does this mean my baseband has already been updated to N900AUCUBMJ5?
I ask because now want root using RDLV (N900AUCUBMI9_OneClickBin) but I don't know if it is safe since another user tried to downgrade to M19 after receiving the MJ5 and softbricked the N3.
Thanks.
Click to expand...
Click to collapse
Turn the phone on and check. You can put it in airplane mode I guess in case it tries to download the update again.
testrak said:
Hi there,
My N3 was never rooted and it received the forced OTA update. The update began while I was holding the phone. It rebooted but I was able to interrupt the process by pulling the battery out to turn off the device during the status screen when it was showing updating apps.
I never turned on my phone after that.
Does this mean my baseband has already been updated to N900AUCUBMJ5?
I ask because now want root using RDLV (N900AUCUBMI9_OneClickBin) but I don't know if it is safe since another user tried to downgrade to M19 after receiving the MJ5 and softbricked the N3.
Thanks.
Click to expand...
Click to collapse
Check the about section of your phone and tell us the last 3 digits of the baseband. Take the SIM out of it if it bothers you that it will update by itself.
No need for all that just turn off your wifi. It will only download the update over wifi. At least mine will.
Verizon 6 here...got prompted to update. Downloaded and was ready for the install and reboot. Phone rebooted. Still 5.0? And device up to date. How can i redownload? Please help
StrangeTimes said:
Verizon 6 here...got prompted to update. Downloaded and was ready for the install and reboot. Phone rebooted. Still 5.0? And device up to date. How can i redownload? Please help
Click to expand...
Click to collapse
Do you have a custom recovery and/or rooted? If so, the OTA fails. The reminder will probably come back in a day or so.
Same thing happened to me. I received the notice literally seconds after rooting and flashing custom recovery. I tried it anyway for ****s and grins, and it failed of course. After rebooting post failure, mine also stated it was up to date.
I did it the hard way, flashed system and radio using fastboot. All up to date now. :good:
Bone stock no root or anything. Would hard reset work? Or will it reprompt soon?
It's hard to say exactly, but given the image was just posted by Google today, and OTAs are already pushing out, you may see it again tomorrow.
I cleared the framework. Still nothing.
Connect to a charger, it reappear and I was able to update. BTW make sure you on WiFi
So wifi connect to charger and clear framework. Will try. Anyone else have solutions?
Yet to repop update. Still getting the up to date...
StrangeTimes said:
Verizon 6 here...got prompted to update. Downloaded and was ready for the install and reboot. Phone rebooted. Still 5.0? And device up to date. How can i redownload? Please help
Click to expand...
Click to collapse
Same thing is happening on my Nexus 7 2013. I've tried it 5 different times.
Sent from my SM-N900V
Same here... fully stock and unrooted Nexus 6 with VZW sim. Got an update notification. Tried to update and the notification just went away and now says I'm up-to-date even thought the update never installed... still on 5.0.
Any solutionsnyet? Hard reset phone does nothing btw
Man... Was really hoping to wake up to the update popping up again. No dice.
att nexus 6 failed 5.0.1
Got notification on att nexus 6 completely stock, for the update to 5.0.1, after accepting the install and agreeing for the restart, it never restarted or updated anything. Still on 5.0. Checking for updates shows that i'm "up to date" and attempting to side load the update via ADB fails.
Got the ota update just now. Install was successful.
I searched and found nothing exactly like what I was experiencing and nothing I hadn't already tried. Hopefully someone has seen this before. I HAD a nice rooted stock SM-G900A 4.4.4 and now I have a flashy gold brick (soft). I rooted by downgrading the kernel to use towelroot then flashed stock kernel back. Everything worked fine for about a week or so. I'm not sure at what point I started having issues exactly so I'm not sure if an app or mild mod could have caused my issues. The only thing I had done was use SuperSU to block Knox and change the terrible TW stock sounds to standard ogg clicks and what not. The trouble started with the camera. I opened my camera and the screen would flash green then I would have red ghost images in a pattern on the screen. The pictures I took had the same effect when viewed in the gallery. If I switched modes the problem would go away with the camera until I closed then opened the camera app again so I assumed it was a software rather than hardware problem. I couldn't find any info on a fix so I did a factory reset. The problem persisted. I decided finally to flash back to stock. That's when it really got bad. After flashing to stock the phone will boot to the Samsung animation with the swoosh, freeze there for a few seconds without completing the boot animation then the screen shuts off and the phone becomes unresponsive. The only signs of life is the blue LED is constant lit. I have to do a battery pull to start over. I have flashed just the PDA and I have flashed the whole shootin match (except for BL) and I get the same results. I have tried stock tar files from a couple different sources. It will go into download mode as well as stock recovery where I tried a factory reset after flashing. PLEASE HELP!
So I flashed OA1 stock kernel and got it to boot. Of course now I get the Update interrupted message when I try for the OTA to anything newer than the 4.4.2 it's running. And after 8 hours of messing with this gem the camera issue persists.
Acer904 said:
So I flashed OA1 stock kernel and got it to boot. Of course now I get the Update interrupted message when I try for the OTA to anything newer than the 4.4.2 it's running. And after 8 hours of messing with this gem the camera issue persists.
Click to expand...
Click to collapse
Go here and flash back to NCE. Then take the OTAs.
http://forum.xda-developers.com/showthread.php?p=60012961
Sent from my SAMSUNG-SM-G900A
That is what I ended up doing just an hour before your reply and all is well again. I suppose my first attempt to go back to NCE didn't work because I didn't use the downgrade flash, just a regular 4.4.2 stock. There must be a difference between the two. The OTAs still wouldn't work so I ended up installing the updates from external sd. The lollipop OTA is downloading fine though. Thanks for confirming I FINALLY went the right route. This root screw up wasn't as bad as my last (efs S3 debacle) but it still took too many hours to fix.
Acer904 said:
That is what I ended up doing just an hour before your reply and all is well again. I suppose my first attempt to go back to NCE didn't work because I didn't use the downgrade flash, just a regular 4.4.2 stock. There must be a difference between the two. The OTAs still wouldn't work so I ended up installing the updates from external sd. The lollipop OTA is downloading fine though. Thanks for confirming I FINALLY went the right route. This root screw up wasn't as bad as my last (efs S3 debacle) but it still took too many hours to fix.
Click to expand...
Click to collapse
If you take the 5.0 ota you won't be able to root. Just FYI. There is no root for it yet. There is a pay however in the general section on how to upgrade to 5.0 and keep root.
Hi
I've run into a problem while trying to update my Moto X (gen 1) XT1053 from 4.4.4. to 5.1. through standard OTA update. Here is the scenario:
- My phone is not unlocked or rooted, nor does it have modified firmware of any type. It is a fully stock XT1053 purchased directly from Motorola in the US that I have not tinkered with in anyway
- My phone downloaded and applied the update on Saturday morning and after the first section of the install rebooted. It sat at the screen with the M and "powered by android" at the bottom and vibrated once, then the screen went off, the same screen came back on and the phone vibrated again. Then an Android on it's back with a red exclamation and "Command" was shown.
- I figured out how to get into the recovery menu and wiped the cache, rebooted and no change. I then attempted to factory reset the phone, it did this but again no change.
- I spoke with a Motorola chat representative who was unable to help but I managed to follow some instructions on this forum to enter the fast boot menu, download and re-flash android stock 4.4.4 using RSDlite and get the phone working again.
- The phone attempted to apply the 5.1 update again yesterday and encountered the same issue again.
Would anyone have any ideas about what could be going wrong with the update process? Or ways that I can go about getting this to install correctly. The motorola rep seemed to think it was to do with my carrier, but as it was downloaded over wifi can this be the case?
If not, would anyone know how to stop android from continously prompting me to update to 5.1? I'm happy to remain on 4.4.4. if it means the phone will still remain functional.
Thanks in advance for your help.
Did you try going to settings and about phone, update
Sent from my Nexus 4 using Tapatalk
Correct, the update was applied through settings > about phone > system update
Delta117nz said:
Would anyone have any ideas about what could be going wrong with the update process? Or ways that I can go about getting this to install correctly. The motorola rep seemed to think it was to do with my carrier, but as it was downloaded over wifi can this be the case?
If not, would anyone know how to stop android from continously prompting me to update to 5.1? I'm happy to remain on 4.4.4. if it means the phone will still remain functional.
Thanks in advance for your help.
Click to expand...
Click to collapse
If you prefer to stay with a working 4.4.4 then you can try disabling some apps related to the OTA, like I think Motorola OTA used to be there although I don't see it now in 5.1, or Motorola Update Services, which now looks like you can't disable but anything you can't disable you can try unchecking "Show Notifications", and so on. if you check around the forum you'll find something that works.
On the other hand if you want to try to get 5.1 working you could try applying the OTA from recovery. while on 4.4.4 you download the OTA (see this post http://forum.xda-developers.com/showpost.php?p=61304089&postcount=864 ) and then boot into stock recovery and choose to apply update from sd. hopefully it will work that way. ***Be aware however that by going from your failed 5.1 update back down to 4.4.4 as you said you did, you have put your phone at risk of bricking when you try to go back up to 5.1. since you've already tried it once, you might be willing to try it again, but just know that there is that risk and its on you if it bricks and you lose your working 4.4.4
Oh and you do have another option, you can stay on 4.4.4 until Motorola releases the whole 5.1 firmware or someone managed to get it, then you can flash 5.1 firmware with rsdlite like you did with 4.4.4
dtg7 said:
If you prefer to stay with a working 4.4.4 then you can try disabling some apps related to the OTA, like I think Motorola OTA used to be there although I don't see it now in 5.1, or Motorola Update Services, which now looks like you can't disable but anything you can't disable you can try unchecking "Show Notifications", and so on. if you check around the forum you'll find something that works.
On the other hand if you want to try to get 5.1 working you could try applying the OTA from recovery. while on 4.4.4 you download the OTA (see this post http://forum.xda-developers.com/showpost.php?p=61304089&postcount=864 ) and then boot into stock recovery and choose to apply update from sd. hopefully it will work that way. ***Be aware however that by going from your failed 5.1 update back down to 4.4.4 as you said you did, you have put your phone at risk of bricking when you try to go back up to 5.1. since you've already tried it once, you might be willing to try it again, but just know that there is that risk and its on you if it bricks and you lose your working 4.4.4
Oh and you do have another option, you can stay on 4.4.4 until Motorola releases the whole 5.1 firmware or someone managed to get it, then you can flash 5.1 firmware with rsdlite like you did with 4.4.4
Click to expand...
Click to collapse
Thanks dtg7, I'll give that a try in the next day or so (updating via the recovery menu) otherwise will hold out for the 5.1 firmware and try RSDlite again.
dtg7 said:
If you prefer to stay with a working 4.4.4 then you can try disabling some apps related to the OTA, like I think Motorola OTA used to be there although I don't see it now in 5.1, or Motorola Update Services, which now looks like you can't disable but anything you can't disable you can try unchecking "Show Notifications", and so on. if you check around the forum you'll find something that works.
On the other hand if you want to try to get 5.1 working you could try applying the OTA from recovery. while on 4.4.4 you download the OTA (see this post http://forum.xda-developers.com/showpost.php?p=61304089&postcount=864 ) and then boot into stock recovery and choose to apply update from sd. hopefully it will work that way. ***Be aware however that by going from your failed 5.1 update back down to 4.4.4 as you said you did, you have put your phone at risk of bricking when you try to go back up to 5.1. since you've already tried it once, you might be willing to try it again, but just know that there is that risk and its on you if it bricks and you lose your working 4.4.4
Oh and you do have another option, you can stay on 4.4.4 until Motorola releases the whole 5.1 firmware or someone managed to get it, then you can flash 5.1 firmware with rsdlite like you did with 4.4.4
Click to expand...
Click to collapse
Worked perfectly downloading the OTA update and applying through the recovery screen. Thanks for your help