Database Users

OTA Update Failed

Hello,
I just noticed 1 hour ago I have 4.3 OTA update for my Nexus 10. However the update has been failed, due to vfxsound mod as far as I understand. I deactivated this app but I cant see OTA update again if I check the system updates manually it states that your system is current(4.2.2). What can I do to have this system update notification again?
My configuration:
rooted (supersu)
CWM recovery
Thank you.

Same here!
mbt28 said:
Hello,
I just noticed 1 hour ago I have 4.3 OTA update for my Nexus 10. However the update has been failed, due to vfxsound mod as far as I understand. I deactivated this app but I cant see OTA update again if I check the system updates manually it states that your system is current(4.2.2). What can I do to have this system update notification again?
My configuration:
rooted (supersu)
CWM recovery
Thank you.
Click to expand...
Click to collapse
I can't update to 4.3 because of the same reason.
In my case, I installed both vfx and vhifi.
I deactivated and turned both of them into safe mode and tried to flash the update with stock recovery.
However, I still got "assert failed: apply_patch_check system/vendor/etc/audio_effects.conf"
There is a way to get the OTA update back, but I repeatedly failed, and ended up with error.
Someone please help us!

This happens because those files have been modified and are no longer the originals. Extract the files it is having issues with from the 4.2.2 factory image, replace them and try again, or just flash system.img from the factory 4.2.2 image and run the OTA again.
Edit: Also, to get the OTA notification again, go to Settings>Apps>All and force stop "Google Services Framework" then "Clear Data". Immediately return to the "About" screen and check for a system update. If any popups come up regarding allowing location services, choose "No" or otherwise don't allow it.
While the system update downloads, remove your google account, and re-add it to avoid any issues with sync, etc. on your google account. Keep in mind if you use 2-factor authentication via google, you'll need to add a new application password for your tablet.

I succesfully upgraded the system. As you said I replaced these file with the original ones. Now It works fine. The only problem is mx player doesnt work. I think they will update it soon.

plastikowl said:
This happens because those files have been modified and are no longer the originals. Extract the files it is having issues with from the 4.2.2 factory image, replace them and try again, or just flash system.img from the factory 4.2.2 image and run the OTA again.
Edit: Also, to get the OTA notification again, go to Settings>Apps>All and force stop "Google Services Framework" then "Clear Data". Immediately return to the "About" screen and check for a system update. If any popups come up regarding allowing location services, choose "No" or otherwise don't allow it.
While the system update downloads, remove your google account, and re-add it to avoid any issues with sync, etc. on your google account. Keep in mind if you use w-factor authentication via google, you'll need to add a new application password for your tablet.
Click to expand...
Click to collapse
Thanks for your guide , my problem is same as above problem with little difference , when I click on OTA update my phone restart and go to CWM recovery and say "it is not safe package , do you want to install ?" I click yes but nothing happened . I also try to get OTA notification back as same as your instruction but nothing happened . please help me . thanks

sabx13 said:
Thanks for your guide , my problem is same as above problem with little difference , when I click on OTA update my phone restart and go to CWM recovery and say "it is not safe package , do you want to install ?" I click yes but nothing happened . I also try to get OTA notification back as same as your instruction but nothing happened . please help me . thanks
Click to expand...
Click to collapse
Did you mean, "phone"? I can only speak for how this behaves on the Nexus 10. Also, if you enable location services (sometimes it tries when the google services framework starts back up) and you allow it, the OTA doesn't seem to show up (at least not for me, perhaps it's region-based?).
I had to redo mine several times while I replaced system files that had been modified, so I know it works if it's done the way I described. 60% of the time, it worked every time.
Also, try removing your custom recovery. I don't know how this affects things for the OTA but it's a factor I didn't have to contend with.

I'm pretty sure he meant tablet. I'm having the exact same problem on my N10.
plastikowl said:
Did you mean, "phone"? I can only speak for how this behaves on the Nexus 10. Also, if you enable location services (sometimes it tries when the google services framework starts back up) and you allow it, the OTA doesn't seem to show up (at least not for me, perhaps it's region-based?).
I had to redo mine several times while I replaced system files that had been modified, so I know it works if it's done the way I described. 60% of the time, it worked every time.
Also, try removing your custom recovery. I don't know how this affects things for the OTA but it's a factor I didn't have to contend with.
Click to expand...
Click to collapse

The difference between "Official" and "Custom" device status was S-Health.

The difference between "Official" and "Custom" device status was S-Health.
I was freaking out over being unable to get my S5 to show as "Official" in its device status (wanted to update, but was told I couldn't) .Out of paranoia, I copied over all my Downloads to my SD card and removed it, deleted any root apps and even cleaned it up using SuperSU. And I rebooted a lot. After I finished, I still saw
Device Status: Custom
Then, I remembered the S-Health bug. Since i like S-Health, I had switched it over recently from being a System app to being a User one (because S-Health on a rooted device was, well, broken). So I re-rooted with SuperSU, then re-opened Android Tuner Free and moved S-Health back from being a User app to being a System one again.
Device Status: Official
I didn't even have to unroot, remove the SU app, or reboot it; I just checked back in Settings and it was "fixed."

Really and it have you official from what I know custom comes out because the phone is rooted anybody correct if im wrong
Sent from my SM-G900P

verse187 said:
Really and it have you official from what I know custom comes out because the phone is rooted anybody correct if im wrong
Sent from my SM-G900P
Click to expand...
Click to collapse
Well, it looks like I spoke too soon. During my OTA update attempts, I had root and it showed as "Official" for a while. Then when I removed SuperSU fully (including the su binaries, making it unrooted), my next attempt to install the update proved futile.
Somehow, when I removed the su binaries with SuperSU, it re-registered my device as Custom. I don't know how, because SuperSU had been specifically told to not attempt to retain itself during OTA updates...

primetechv2 said:
Well, it looks like I spoke too soon. During my OTA update attempts, I had root and it showed as "Official" for a while. Then when I removed SuperSU fully (including the su binaries, making it unrooted), my next attempt to install the update proved futile.
Somehow, when I removed the su binaries with SuperSU, it re-registered my device as Custom. I don't know how, because SuperSU had been specifically told to not attempt to retain itself during OTA updates...
Click to expand...
Click to collapse
You did not reinstall stock recovery. You cannot get OTAs if you have a custom recovery still.

KennyG123 said:
You did not reinstall stock recovery. You cannot get OTAs if you have a custom recovery still.
Click to expand...
Click to collapse
I never actually installed a custom recovery, though. I did eventually reinstall the fully stock firmware with Kies and then performed the upgrade, something I'm going to guess wouldn't be possible otherwise... But to be specific, I never had anything installed except got XPosed mods and a moved S Health to get it functioning again.
But I'm really sad that, for whatever reason, my device status kept flickering between Official and Custom, especially when it chose Custom after I disabled root.

I just flashed the stock nd5 firmware through odin in mine and it still show's as ''custom''. Any ideas on how to get it to show ''official''?

BlackJou said:
I just flashed the stock nd5 firmware through odin in mine and it still show's as ''custom''. Any ideas on how to get it to show ''official''?
Click to expand...
Click to collapse
I ran into the same issue when trying to update OTA for WiFi calling. I wound up (before I had a chance to reset), changing the runtime back to Dalvik from ART, wound up working.

frcollier said:
I ran into the same issue when trying to update OTA for WiFi calling. I wound up (before I had a chance to reset), changing the runtime back to Dalvik from ART, wound up working.
Click to expand...
Click to collapse
It is on Dalvik though :/

well, I did it again.
rooted: Official status
Installed XPosed: Official
Removed S-Health: Official
Reinstalled old S-Health as a user app: Official
Shifted S-Health to System app: Official
Removed XPosed: Custom
Anybody know what permissions SHealth and HealthService (.apk, .odex) should be reinstated with, and in which folder they go, I'd be really happy. Especially if someone got back to me before I downloaded this 1.5GB system file to figure out if it says.

New Update for Verizon SGP561 Android 4.4.2

I have the Verizon SGP561 running Android 4.4.2 rooted with PhilZ Touch & CWM & TWRP installed. I just received notice of an OS update. Has anyone else receive this and know what it is? I hesitate to take any updates and don't want to lose root.
OK--- Just found this to answer one of the questions --
OTA update 23.0.1.E.0.208 also includes "optimized touch sensitivity," better performance for users who encrypt their tablet, improved support for TalkBack (Google's accessibility service for the visually impaired), and minor UI tweaks to fonts, icons, and layouts. None of it is particularly crucial, and no , it doesn't include an update to Android: Verizon's version of the Tablet Z2 is running the same build of Android 4.4 that is was back in July. But it's hard to be too miffed about that, since the Wi-Fi version of the Tablet Z2 hasn't been upgraded to Lollipop, either.
Now the question is will I lose root if I apply it...

I would also like to know if we would lose root with this update.

Varekai said:
I would also like to know if we would lose root with this update.
Click to expand...
Click to collapse
i took the plunge and tried it...
i used the supersu and used survival mode and installed as a system app
I am STILL ROOTED

Thanks! Except I've tried 4 times to update and keep getting failed. Using stock recovery so not sure what's going on.

Varekai said:
Thanks! Except I've tried 4 times to update and keep getting failed. Using stock recovery so not sure what's going on.
Click to expand...
Click to collapse
I didn't change my recovery, I only rooted it yesterday and then 20min later enabled su as system app and then survival mode and applied update. No issues here
So far running good, however when I go into settings and tick on airplane mode it actually doesn't goto airplane mode. The only way I can get air plane mode is by holding the power button and selecting air plane mode.
Not sure if this is a error with root or glitch with the new update.
We now have a reboot option tho (not like I have ever needed it on this awesome tab)

On mine the update fails. Says "There was a problem with the update..." As I said, I am on 4.4.2 using NUTs dual recovery and root. I install SuperSu as a system app .

It makes me disappointed I spent money on the sixaxis controller on play store to not figure out how it works for the Z2 tablet a month prior to this update.
Maybe I could use it on other non-Sony devices?

Since my system update thing doesn't work, is there another way of acquiring and applying this update?

TheGrayson said:
Since my system update thing doesn't work, is there another way of acquiring and applying this update?
Click to expand...
Click to collapse
You can use this software to download the ftf file and flash it manually using flashtool http://forum.xda-developers.com/cro...perifirm-xperia-firmware-downloader-t2834142/ (will lose data and root)
Update: I've found a way to update the latest version without losing root and posted here http://forum.xda-developers.com/xpe...et-verizon-t3054700/post59440416#post59440416

Any idea on a lollipop update compatible with the sgp561?

Nexus 4 OTA 5.1 Update error

I'm getting the OTA update to Android 5.1, it downloads, asks me to restart, then fails with an error screen and the robot lying on its back. The phone then reboots itself into the 5.0.1 firmware.
The phone is rooted, is anyone else getting the same issue. Are there any logs I can look at to find out why?
Thansk

i have troubles as well. i unrooted, installed stock recovery (via n4 toolkit) and tryed to install. it takes longer then before but i stell get an error. SuperSU is gone in my app drawer.. any other help?
PS: i am on stock rom 5.0.1
i tryed to use sideload ADB update. it says: "/system/bin/app_process32" has unexpected contents. Error in sideload/package.zip. Status 7
any tipps?

I used the excellent Wug Nexus Toolkit http://www.wugfresh.com/nrt/
Through there I unrooted. Then applied the new update.

rowdybeans said:
I'm getting the OTA update to Android 5.1, it downloads, asks me to restart, then fails with an error screen and the robot lying on its back. The phone then reboots itself into the 5.0.1 firmware.
The phone is rooted, is anyone else getting the same issue. Are there any logs I can look at to find out why?
Thansk[/Q
I tray everything but don't work, it tell me , cache file fail.
Click to expand...
Click to collapse

In my case, this did the trick: aaronhastings.me/updating-to-android-5-1-0-on-rooted-nexus-5
I hope it will help you, too.
Regards.

Nexus player is in recovery mode in the morning

Hi I was wondering if anyone could tell me why my Nexus player ends up in recovery mode in the mornings im stocked rooted and unlocked with twrp I have to reboot my Nexus player each morning unless it's trying to update.

The same thing use to happen to me. The stock rom tries to do an update, then reboots, but you are rooted/unlocked, so it fails and just sits there in recovery. Most custom roms take the update feature out, but on stock it still exists, and I think there is a way to turn off checking for updates or something similar so it will not happen again.

Rawb0Ss said:
The same thing use to happen to me. The stock rom tries to do an update, then reboots, but you are rooted/unlocked, so it fails and just sits there in recovery. Most custom roms take the update feature out, but on stock it still exists, and I think there is a way to turn off checking for updates or something similar so it will not happen again.
Click to expand...
Click to collapse
Think had happen to me as well on my n7 2nd when on stock but do you know what I can do or do I need disable a the service or something or do bak

nikkifm said:
but do you know what I can do or do I need disable a the service or something or do bak
Click to expand...
Click to collapse
Try http://forum.xda-developers.com/showpost.php?p=62865084&postcount=6

You can disable system updates if your device is rooted. In order to do this, download My Android Tools (https://play.google.com/store/apps/details?id=cn.wq.myandroidtools) and sideload the APK on to your Nexus Player. After it's installed on your device, load the app, access its menu and go to System >> Search >> Google Play Services >> Uncheck SystemUpdateService. This will disable system updates but still allow your apps to update.