Database Info

[Q] OTA update error, rooted using CF-Autoroot

Hi, have seen some posts for this issue but none really help me understand what went wrong (tried this update 3 times with same result)
I have nexus 5 with android 4.4.2, rooted with CF-Auto root.
Recently i received OTA update notification to 4.4.3, but when i'm trying to install it i get error without any info.
Before trying to update i completely uninstall xposed and all of its modules.
To my understanding using CF-Autoroot should not interfere with OTA updates.
Any ideas?

oshera said:
Hi, have seen some posts for this issue but none really help me understand what went wrong (tried this update 3 times with same result)
I have nexus 5 with android 4.4.2, rooted with CF-Auto root.
Recently i received OTA update notification to 4.4.3, but when i'm trying to install it i get error without any info.
Before trying to update i completely uninstall xposed and all of its modules.
To my understanding using CF-Autoroot should not interfere with OTA updates.
Any ideas?
Click to expand...
Click to collapse
did you do any other system modifications? change kernels?

I'd just dirty flash 4.4.3 and call it a day.

Zepius said:
did you do any other system modifications? change kernels?
Click to expand...
Click to collapse
Nop, unless apps like titanium backup or file manager (only other apps that require root) change something. :/

Lokke9191 said:
I'd just dirty flash 4.4.3 and call it a day.
Click to expand...
Click to collapse
Im no android expert(far from it), and prefer to stick to the most simple methods as long as i can run xposed framework.
this is why OTA without flashing or interfering with OS is best for me.
Keep this as last resort if no progress will happen regarding OTA updates.
Thanks!

oshera said:
Im no android expert(far from it), and prefer to stick to the most simple methods as long as i can run xposed framework.
this is why OTA without flashing or interfering with OS is best for me.
Keep this as last resort if no progress will happen regarding OTA updates.
Thanks!
Click to expand...
Click to collapse
OTA is more complex if you're rooted.. There's more flashing involved if you have / want a custom recovery (which all rooted users should aim to have)
Just download the full rooted stock ROM in android development and flash it without wipe from recovery.
It's actually fewer steps anyway.
OTA = revert system changes, boot recovery, flash, re-flash recovery, re-root
Rooted stock = boot recovery, flash
No brainer really. Flashing an OTA if rooted is a fool's errand
Sent from my Nexus 5 using Tapatalk

oshera said:
Im no android expert(far from it), and prefer to stick to the most simple methods as long as i can run xposed framework.
this is why OTA without flashing or interfering with OS is best for me.
Keep this as last resort if no progress will happen regarding OTA updates.
Thanks!
Click to expand...
Click to collapse
lmao, its FAR from the most simple method. most simple method would be to dirty flash a 443 stock/rooted rom and call it a day, without over complicating anything.

oshera said:
Hi, have seen some posts for this issue but none really help me understand what went wrong (tried this update 3 times with same result)
I have nexus 5 with android 4.4.2, rooted with CF-Auto root.
Recently i received OTA update notification to 4.4.3, but when i'm trying to install it i get error without any info.
Before trying to update i completely uninstall xposed and all of its modules.
To my understanding using CF-Autoroot should not interfere with OTA updates.
Any ideas?
Click to expand...
Click to collapse
Did you uninstall Xposed from within the app? If you simply uninstalled it the same way you install regular aps (by dragging to uninstall from the app drawer) then it doesn't completely uninstall.

marleyfan61 said:
Did you uninstall Xposed from within the app? If you simply uninstalled it the same way you install regular aps (by dragging to uninstall from the app drawer) then it doesn't completely uninstall.
Click to expand...
Click to collapse
Thank you!
That fixed my problem, after uninstall from within the app i could use OTA updates without flahing anything!
And thanks for everyone else for advises

oshera said:
Thank you!
That fixed my problem, after uninstall from within the app i could use OTA updates without flahing anything!
And thanks for everyone else for advises
Click to expand...
Click to collapse
Glad it worked for you. For future reference, do read this sticky - http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
(along with the other stickies in that forum)

App Updates?

Hey,
So I have flashed my Nexus 5 back to pure stock in preparation for Lollipop.
The problem I'm having is; although many of the stock apps require updates and show this on an individual basis on the store - the usual long list of apps requiring an update in the 'my apps' section is missing. I like being able to click update all, and I don't want to trawl through and update every app individually. I have tried clearing the cache in settings, restarting, logging out and back into my Google account, but none of these have worked.
My Nexus 5 is only a few weeks old, and the stock I installed was from the Google Developer page, so it should be working in theory. It's also set to update automatically over Wi-Fi. Any advice?

Could be because those apps have permissions changes if they didn't auto update. I've noticed that I have to click apps individually when the permissions change from the update.
Sent from my Nexus 5 using XDA Free mobile app

Or_Ca said:
Hey,
So I have flashed my Nexus 5 back to pure stock in preparation for Lollipop
Click to expand...
Click to collapse
Sorry for the off topic, but why did you do this?

I was worried in case the OTA update would not push through with my device being on CM11.

And I'd much rather be on Lollipop than CM11

Or_Ca said:
I was worried in case the OTA update would not push through with my device being on CM11.
Click to expand...
Click to collapse
Or_Ca said:
And I'd much rather be on Lollipop than CM11
Click to expand...
Click to collapse
Yeah but there will be rooted flashable zips available before the OTA anyway, and OTA is about the crappiest way to update too. Just seems a lot of effort for nothing.

True, I was getting tired of CM11 anyways. I look forward to the zip!

Remove notification after CPE1 update using Flashfire.

Hello. I'm rooted on Marshmallow 6.0.1, using Xposed Framework. I downloaded the CPE1 OTA update, and installed it successfully, using Flashfire so that i could maintain my root and recovery. I can't get the notification for the update to go away though.
I don't want to select "install" on the notification, without using Flashfire, because i think it will remove root and recovery, or cause some other problems. Besides, it's already successfully installed, i read the new build number in "About Phone" setting!
I've read methods, like disabling the system update app, but as far as i understand that'd prevent me from being notified of future updates, which i don't want.
Is there a file i can delete, using Total Commander, or a one-time, simple fix to remove the update notification?
Thank you kindly!
Sent from my SM-G900P using XDA-Developers mobile app

Out of curiosity, what release were you on before? I'm on the rooted PA1 release from the dev forum here and don't want to lose root (or twrp). If flashfire will do it for me, that's awesome.

Well I tried installing it but it rebooted to twrp recovery and twrp failed to install it since you need the stock recovery to install updates.
Thereforw doing OTA won't do anything it will most likely solve your problem of the notification not going away
Sent from my SM-G900P using XDA-Developers mobile app

dmolavi, I'm not sure what my previous build was, i just know my current build matches the build number in the info of the OTA. Flashfire installed it no problem; just make sure to check the "maintain recovery" option. Flashfire works by temporarily reverting to stock, installing the update, then restoring your root... I'm not sure of the specifics.
svz235, i ended up doing the same as you, but then it re-downloads the update, and keeps notifying me, in a cycle of failing, downloading, and notifying :-/
Sent from my SM-G900P using XDA-Developers mobile app

Disable the system update app then re-enable it again
Sent from my SM-G900P using XDA-Developers mobile app

dieseldeeznutz said:
dmolavi, I'm not sure what my previous build was, i just know my current build matches the build number in the info of the OTA. Flashfire installed it no problem; just make sure to check the "maintain recovery" option. Flashfire works by temporarily reverting to stock, installing the update, then restoring your root... I'm not sure of the specifics.
svz235, i ended up doing the same as you, but then it re-downloads the update, and keeps notifying me, in a cycle of failing, downloading, and notifying :-/
Sent from my SM-G900P using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you download the OTA but just not choose to install, or did you sideload it somehow?

svz235 said:
Disable the system update app then re-enable it again
Sent from my SM-G900P using XDA-Developers mobile app
Click to expand...
Click to collapse
Disable was grayed out, so I used the "Disable Service" app... So, I disabled it but then, it displayed a notification that said "checking system" indefinitely, and the update notification came back!

dmolavi said:
Did you download the OTA but just not choose to install, or did you sideload it somehow?
Click to expand...
Click to collapse
Yes, I downloaded it, but ticked "later" in the install options, then opened Flashfire and it automatically recognized it, and allowed me to install it.

I am curious to use flash fire myself to install the latest update. I tried using flash fire to flash the CPE2 update but it didn't work I am still stuck in CPE1. What settings did you use to flash it successfully?
Sent from my SM-G900P using XDA-Developers mobile app

svz235, CPE1 is the latest isn't it ? It's listed in the description of the OTA, and so is CPE2. I think it the version you get just depends on your phone model and carrier.
Flashfire recognized that i had an OTA, and automatically set the settings. I just made sure to select "maintain recovery" as well.
Sent from my SM-G900P using XDA-Developers mobile app

And i STILL have the notification!
Sent from my SM-G900P using XDA-Developers mobile app

Can you post the OTA file for download? My phone won't download it, says it's been modified. I don't know if that's due to TWRP, or the fact that I think i tripped knox a while back...

dieseldeeznutz said:
svz235, CPE1 is the latest isn't it ? It's listed in the description of the OTA, and so is CPE2. I think it the version you get just depends on your phone model and carrier.
Flashfire recognized that i had an OTA, and automatically set the settings. I just made sure to select "maintain recovery" as well.
Sent from my SM-G900P using XDA-Developers mobile app
Click to expand...
Click to collapse
Well I have the SM-g900p from sprint flashed over to boost. I had CPE1 already installed. Then I got notification of CPE2 coming out. I did try flashfire but it keeps failing on me for some reason I go to build number and it is still on CPE1.

Alright, so it turns out I was mistaken... did I mention I'm somewhat of a noob? Anyway, CPE1 was the original mm6.0.1 build from Sprint, CPE2 is the update. They list it like this in the OTA info: CPE1>CPE2, I guess just to show it's going from cpe1 to cpe2... confused me because I thought they were just different builds for different models and carriers. :silly: So, FlashFire didn't work for the update. I ended up uninstalling Xposed Framework, and unrooting with SuperSU, then tried the OTA, but it gave me the message "Your phone has been altered in an unauthorized way" and wouldn't install the OTA. So I went to sammobil.com , downloaded the latest CPE2 build, flashed it with Odin, then rooted it again, and installed Xposed. Everything went smoothly, I'm on the newest build, rooted again, and no more notification... Yayy!! :laugh:

dieseldeeznutz said:
Alright, so it turns out I was mistaken... did I mention I'm somewhat of a noob? Anyway, CPE1 was the original mm6.0.1 build from Sprint, CPE2 is the update. They list it like this in the OTA info: CPE1>CPE2, I guess just to show it's going from cpe1 to cpe2... confused me because I thought they were just different builds for different models and carriers. :silly: So, FlashFire didn't work for the update. I ended up uninstalling Xposed Framework, and unrooting with SuperSU, then tried the OTA, but it gave me the message "Your phone has been altered in an unauthorized way" and wouldn't install the OTA. So I went to sammobil.com , downloaded the latest CPE2 build, flashed it with Odin, then rooted it again, and installed Xposed. Everything went smoothly, I'm on the newest build, rooted again, and no more notification... Yayy!! :laugh:
Click to expand...
Click to collapse
Sweet glad it worked for you mind showing how you flashed the cp2 build from Odin and where you got it from? I also want the notification to go away I am stuck on cp1
Sent from my SM-G900P using XDA-Developers mobile app

Security Update XT1572

Finally the September Security Patch is available for the Style. Hope Nougat is on the way soon.

How many threads about a September security patch that is now 4 months old do we need? Not very impressive to get the September patch in January in my opinion. If anything, the release of a security patch for Marshmallow now doesn't give me much hope that we will see Nougat in the near future. I hope I'm wrong, but I feel like we are getting screwed.

Moto does security patches in 1/4 by 1/4 updates so roughly every three months. Also they are usually a 1/4 behind the most recent.

autosurgeon said:
Moto does security patches in 1/4 by 1/4 updates so roughly every three months. Also they are usually a 1/4 behind the most recent.
Click to expand...
Click to collapse
Motorola/Lenovo never committed to a release schedule.

If u have the captured ota pls share it here
Xt 1572 Retasia Ds

False expectations that it was Nougat update, turns out to be just a security update for September month.
Moto updates slowly turning out to be a just a regular name any oem. No reliability for the software updates.
Day by day getting disappointed by Moto series ??

quakeaz said:
Motorola/Lenovo never committed to a release schedule.
Click to expand...
Click to collapse
I am aware of that however past performance while not indicative or proof of future performance says they have been sticking to an every 3 to 4 month schedule on Moto X line for security updates.

Uninstalled supersu, flashed stock recovery, downloaded security update. But while install getting the dead andi symbol with 'error'. upon reboot says the update install was unsuccessful. phone functions normally.
where did it go wrong? any suggestions.?
thanks

kcnanand said:
Uninstalled supersu, flashed stock recovery, downloaded security update. But while install getting the dead andi symbol with 'error'. upon reboot says the update install was unsuccessful. phone functions normally.
where did it go wrong? any suggestions.?
thanks
Click to expand...
Click to collapse
Uninstalling SU doesn't disable root. Did you unroot?

boxman99 said:
Uninstalling SU doesn't disable root. Did you unroot?
Click to expand...
Click to collapse
I did full unroot from within the su app before remove twrp. Don't want to restore full stock image. May be I will wait till N is released. Now if there is a way to disable the nagging update notification
Sent from my XT1572 using XDA-Developers Legacy app

kcnanand said:
I did full unroot from within the su app before remove twrp. Don't want to restore full stock image. May be I will wait till N is released. Now if there is a way to disable the nagging update notification
Sent from my XT1572 using XDA-Developers Legacy app
Click to expand...
Click to collapse
If you used root to make any change to the system partition (like Xposed, or even some simple things like the GSAM root battery_stats monitor), you cannot take an OTA successfully. The script checks to see if the system partition has been modified, or possibly just ever mounted R/W, and will refuse to continue and will result in an error in recovery like you see.
If the condition occurs like you are seeing, the only recourse is to restore to pure stock by flashing the factory images or restoring a pre-root TWRP backup.

acejavelin said:
If you used root to make any change to the system partition (like Xposed, or even some simple things like the GSAM root battery_stats monitor), you cannot take an OTA successfully. The script checks to see if the system partition has been modified, or possibly just ever mounted R/W, and will refuse to continue and will result in an error in recovery like you see.
If the condition occurs like you are seeing, the only recourse is to restore to pure stock by flashing the factory images or restoring a pre-root TWRP backup.
Click to expand...
Click to collapse
The only way to do is flash stock.. else wipe cache partition and disable notification for Moto Update app. It wont bother you anymore.

rahul14322 said:
The only way to do is flash stock.. else wipe cache partition and disable notification for Moto Update app. It wont bother you anymore.
Click to expand...
Click to collapse
True, I meant the only way to take the OTA update was to go back to stock... I neglected to mention that you can restore functionality to the device by just wiping caches.

I got the Security Update today too @ XT1572

ATT here got it today as well.

Anyone having problems with calls after this update!?
Since I updated yestarday people complaining they dont hear me well when they call me!

andromobilogy said:
Anyone having problems with calls after this update!?
Since I updated yestarday people complaining they dont hear me well when they call me!
Click to expand...
Click to collapse
No problems here... Spent a good 2 hours on the phone last night after getting the update and no one said anything.

kcnanand said:
Uninstalled supersu, flashed stock recovery, downloaded security update. But while install getting the dead andi symbol with 'error'. upon reboot says the update install was unsuccessful. phone functions normally.
where did it go wrong? any suggestions.?
thanks
Click to expand...
Click to collapse
You can do a minimal factory restore to satisfy the checks for the OTA. Just reflash the partitions most likely modified (recovery, system, boot) and the OTA should succeed. This assumes you're not running an alternate modem or haven't tinkered with any other partitions (besides the logo, that's fine to leave altered).
See ace's nice post @ https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110, and just execute the lines from boot.img to system.img_sparsechunk.8 with the appropriate 6.0 (May) files.

Has anyone from India received this update? I download RETASIA DS verison of this ROM and flashed it, however I'm getting no wifi and can't find an alternate download link. And obviously now I can't flash an older verison and then update using OTA

rahul14322 said:
The only way to do is flash stock.. else wipe cache partition and disable notification for Moto Update app. It wont bother you anymore.
Click to expand...
Click to collapse
What Moto Update app??? I don't see such a thing listed under Apps in settings.

System update notification. How to get rid of it ?

I run stock rom Emui 4.1 .
Rooted
TWRP 3.0.2-0
Every time it changes from wifi to 4g or any data changes the phone wants to do a system update.
The problem with this is I am pretty happy with 4.1 and not going to 5.
A pop up shows up asking me to update.
Pretty sure that its impossible and would not work even if I wanted to.
May end up going to a custom rom in time, but not right now.
Attached is the notificaiton that pops up.
Any advice on what I can do to get rid of this ?
Thank you,

If you have root, freeze the system update app.
Sent from my FRD-L04 using Tapatalk

Or just turn off notifications for the system update app.

PuffDaddy_d said:
Or just turn off notifications for the system update app.
Click to expand...
Click to collapse
All of the notifications are off for emui updater,
All permissions and data were cleared , it still comes back.
Interesting enough , freezing the app did kill the notification .
Thank you for seeing something I overlooked