Database Users

4.3 ota prompt popping up after already updated

Hey all,
I installed the 4.3 ota update back when it was first released in August, and it was rooted, lost root and rerooted. Nothing else I have changed.
Today is the 3rd time since updating back then has my phone recieved the ota prompt. First time I just went through and it restarted. 2nd time it gave a boot error and this time it just restarted the os. Like I said it doesnt come often but I just wanted to know if anyone has had this issue and Im going to assume I need to wipe the phone and a stock image?

Anyone else get a system update 10 Aug 2015?

Received notification of a system update today, 10 August 2015. I'm a little leery of installing this. I'm at 5.1.1 and after installing 5.1.1, I have the dreaded unannounced deaths where the phone will turn itself at random. Sometimes it will reboot if you hold the power button down for about 15 seconds. Sometimes the charger needs to be plugged in before it will reboot. Sometimes it cycles through all apps before completing the reboot. Sometimes not. If the new update will fix this, I'm all for it. But, I don't want to get fooled again with these updates. So, anyone else get an update? What does it do? Any problems after the update? Thanks.

dmkozak said:
Received notification of a system update today, 10 August 2015. I'm a little leery of installing this. I'm at 5.1.1 and after installing 5.1.1, I have the dreaded unannounced deaths where the phone will turn itself at random. Sometimes it will reboot if you hold the power button down for about 15 seconds. Sometimes the charger needs to be plugged in before it will reboot. Sometimes it cycles through all apps before completing the reboot. Sometimes not. If the new update will fix this, I'm all for it. But, I don't want to get fooled again with these updates. So, anyone else get an update? What does it do? Any problems after the update? Thanks.
Click to expand...
Click to collapse
It's the first update of Google's announced security patch program. Expect frequent OS updates now to address security issues. This one patches the well publicized Stagefright MMS exploit.

That was my guess. I rarely text, or other, message, so I'm not too worried about Stagefright. My gut tells me to wait until others have installed. I have enough memory leak auto turn-off issues, that I'm afraid of making my phone worse than it is.
If Google would be so kind as to include a memory leak resolution in these updates, I'd jump all over it.

Well I had been postponing updating to Lollipop for months... (was still on 4.4.4 cuz I didn't quite like the new UI) and decided to update Sunday morning.
Big mistake.
The OTA 5.1.1 5.0.1 update made my phone become unstable, lag, and crash at random. Constantly get "X ins't responding", where X can be anything from Launcher to System UI to Chrome!
I currently can't even use my N4, and I'm trying to find a way to revert the upgrade, My 4.4.4 was rooted, and now it's not and I can't even enter Recovery mode.
Not sure if it's 100% related to your troubles, but I've been having similar random reboots lately and just general instability.
Edit: my bad, I just realized it was 5.0.1 I upgraded to.

update aug 10, 2015
I saw the update and thought it would be a good idea but I now have a tablet stuck in reboot loop. Have tried everything (clearing data, factory reset, etc) and still not able to get past looping. Might want to wait before you update.

robpoth said:
I saw the update and thought it would be a good idea but I now have a tablet stuck in reboot loop. Have tried everything (clearing data, factory reset, etc) and still not able to get past looping. Might want to wait before you update.
Click to expand...
Click to collapse
You have to lock your bootloader for Ota to work.
Sent from my Nexus 4 using XDA Free mobile app

Stevica Smederevac said:
You have to lock your bootloader for Ota to work.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I don't think your bootloader has to be locked, but since 5.+ you do have to be unrooted with no changes to your /system partition. I know I have sideloaded the OTA after flashing stock images. Just did not want the poster to lock their bootloader and brick themselves thinking they will be able to boot the OTA if they have modified /system at all.

ariesgodofwar said:
I don't think your bootloader has to be locked, but since 5.+ you do have to be unrooted with no changes to your /system partition. I know I have sideloaded the OTA after flashing stock images. Just did not want the poster to lock their bootloader and brick themselves thinking they will be able to boot the OTA if they have modified /system at all.
Click to expand...
Click to collapse
Yeah,you're right. Everything stock +locked bootloader for ota to work. I assumed he knew thhat part about everything stock.
Sent from my Nexus 4 using XDA Free mobile app

I have unlocked bootloader and still I updated successfully thru OTA. No problems at all.
Sent from my Nexus 4 using Tapatalk

OTA update failed on Moto X Play

So, I stepped over to the Nexus 6p and sold my Moto X Play to my friend.
I unrooted it, flashed stock firmware(exactly like I did about 2 times before) but he can't install OTA updates, he says it reboots several times and reports the update as failed.
BUT, I went through the exact same proces before, 2 times even, I flashed the stock firmware and I COULD update but I am not sure how anymore, I think it had something to do with restarting the phone yourself? I am basically looking for a specific action here that I performed before, but I don't remember what it was.

Nvm, got solved. Turns out he was pressing Start in the bootloader and not Recovery.

G4 Play OTA update from 6.0.1 to 7.1.1 fails

Hello,
My father has a Moto G Play (XT1602, reteu). It is currently running Android 6.0.1 with september 2017 patches. Build number is MPIS24.241-15.3-26.
The device is completely stock. No unlocked bootloaded, no custom recovery, kernel or ROM. Just a few small apps were installed.
There is a OTA system update to Android 7.1.1, build number NPI26.48-36. After downloading, it prepares for installation, reboots, and starts installing.
When the blue progress bar reaches about 40%, it stops and just says "Error". After some time the device reboots and says the upgrade failed, and no changes were made.
How can I find the cause of the failing update? How can I get the update to install successfully?

gewe said:
Hello,
My father has a Moto G Play (XT1602, reteu). It is currently running Android 6.0.1 with september 2017 patches. Build number is MPIS24.241-15.3-26.
The device is completely stock. No unlocked bootloaded, no custom recovery, kernel or ROM. Just a few small apps were installed.
There is a OTA system update to Android 7.1.1, build number NPI26.48-36. After downloading, it prepares for installation, reboots, and starts installing.
When the blue progress bar reaches about 40%, it stops and just says "Error". After some time the device reboots and says the upgrade failed, and no changes were made.
How can I find the cause of the failing update? How can I get the update to install successfully?
Click to expand...
Click to collapse
If the device is pure stock (never rooted) the problem lies with Lenovo/Moto. There is little you can do to self-address short of performing a 'factory reset' which may not (probably won't) help. Be aware all personal data will be lost.
A few tips:
- insure there is adequate free space for the update
- remove the SD card if installed
- try clearing the cache partition from stock recovery
Your best best may be to seek assistance from whatever carrier your father uses. Failures if this nature are not uncommon - especially installing a new Android version via OTA update.

I updated my phone today on 7.1.1 but my network is not working. Can't access calls/msgs. Can anyone help me?
Sent from my XT1609 using Tapatalk

zohaibkhan143 said:
I updated my phone today on 7.1.1 but my network is not working. Can't access calls/msgs. Can anyone help me?
Click to expand...
Click to collapse
Posting the SAME question in a half dozen threads does not endear you to the community or yield a faster/better response. I don't know the answer nor does anyone else here based on the lack of replies. Restore the backup you created before updating.

Davey126 said:
Posting the SAME question in a half dozen threads does not endear you to the community or yield a faster/better response. I don't know the answer nor does anyone else here based on the lack of replies. Restore the backup you created before updating.
Click to expand...
Click to collapse
The phone's bootloader is locked so I didn't make a backup now I wondering can I flash the previous rom again which is android 6.0 (241-2.35.1.17) or downgrading cause some issues?

zohaibkhan143 said:
The phone's bootloader is locked so I didn't make a backup now I wondering can I flash the previous rom again which is android 6.0 (241-2.35.1.17) or downgrading cause some issues?
Click to expand...
Click to collapse
Have no idea. Limited feedback suggest downgrading is not a smooth ride as bootloader/kernel was likely updated with the ROM. Hard brick is a possibility.

Davey126 said:
Have no idea. Limited feedback suggest downgrading is not a smooth ride as bootloader/kernel was likely updated with the ROM. Hard brick is a possibility.
Click to expand...
Click to collapse
Thanks I am expecting the same thing.

Davey126 said:
If the device is pure stock (never rooted) the problem lies with Lenovo/Moto. There is little you can do to self-address short of performing a 'factory reset' which may not (probably won't) help. Be aware all personal data will be lost.
A few tips:
- insure there is adequate free space for the update
- remove the SD card if installed
- try clearing the cache partition from stock recovery
Your best best may be to seek assistance from whatever carrier your father uses. Failures if this nature are not uncommon - especially installing a new Android version via OTA update.
Click to expand...
Click to collapse
The phone was not bought via a carrier. So the carrier will be of little help.
I collected some information from the phone:
Of the 16 GB ROM, Android uses 5,04 GB. Of the remaining 10,96 GB only 3,78 GB is used. So 7,18 GB is free. There is no SD card installed.
Of the 1,9 GB RAM on average 52% is in use. 0,9 GB is free.
Current build number is MPIS24.241-15.3-26, Android 6.0.1 with patches up to 1 September 2017.
The update has build number NPI26.48-36, Android 7.1.1.
When I was at my parents today, I forgot your last tip, about clearing the cache partition from stock recovery.. I will try to explain the instructions to my father.

I finally had a chance to clear the cache partition. Unfortunately this does not solve the problem. Installing the update still fails.

Optimizing Apps on every boot.

I noticed a week or so ago that every time I reboot my Nexus 4, I have to sit through the optimizing apps every time. I have been going crazy searching for info on this and cant seem to find anything that helps. Phone is running 5.1.1, nothing custom, OTA update. I tried rolling back to 4.2 and everything seemed ok up until I got back to 5.1.1, then optimizing apps every boot again. I prefer Lollipop, but this constant half hour + delay before I can use the phone is unacceptable.
Any help would be appreciated, I really can't afford to buy another phone right now but this is driving me crazy trying to figure it out.

orangej said:
I noticed a week or so ago that every time I reboot my Nexus 4, I have to sit through the optimizing apps every time. I have been going crazy searching for info on this and cant seem to find anything that helps. Phone is running 5.1.1, nothing custom, OTA update. I tried rolling back to 4.2 and everything seemed ok up until I got back to 5.1.1, then optimizing apps every boot again. I prefer Lollipop, but this constant half hour + delay before I can use the phone is unacceptable.
Any help would be appreciated, I really can't afford to buy another phone right now but this is driving me crazy trying to figure it out.
Click to expand...
Click to collapse
I'm not an expert but I have some experience with my Nexus 4..
any root? SuperSu maybe?
You receive the 'Android is starting optimising app xx of xx'?
if you have SuperSu, install the last version...
Another cause may be some file in your internal storage, make a backup, delete all and restart 2 times to see if there is a change...
Last resort, flash the rom stock with nexus root toolkit with all wipe

I did use NRT to flash 4.2 back on and wiped it, then let it work its way through the upgrades again. Once it got back to 5.0+ the optimizing problem started. Phone was not rooted, just bootloader unlocked.
I flashed a custom rom based on Oreo on it and the problem stopped, so I am assuming this is a Lollipop problem, but I would really rather be able to run stock Lollipop on my phone.