The last few mornings I've turned on my tv and found my Nexus Player sitting at the recovery screen; finally clued in there must be an update.
So what is the best way to install this small 15mb update? Tried doing it in TWRP, but it failed.
Do I need to re-flash stock recovery and just let it do the work?
Will I lose ROOT access?
I'm pretty keen to get the update, fingers crossed it fixes the Netflix problem.
So I've done more reading and realised I'm going to have to;
- download the factory image,
- install,
- re-root,
- re-flash TWRP
- reinstall Xposed and the modules
- Re-setup if any data is lost
This could become a painful process if Google stick with their promise of monthly patching. Is there a better way?
Are you sure that your Nexus Player's random reboots are being caused by an attempted system update? If your Android device is rooted with a custom recovery, you shouldn't even be prompted for system updates. A couple of months ago, I noticed my Nexus Player randomly going in to recovery mode but this only started happening after I installed the initial x86 version of Xposed for Android 5.1 by romracer. After I updated the device to a newer version of Xposed, I no longer had this random rebooting problem.
http://forum.xda-developers.com/showpost.php?p=61690282&postcount=4
The monthly patches from Google will probably be security-oriented so I don't think it's necessary to update that often on a device like the Nexus Player. I wouldn't bother to go through all those steps just to move from Android 5.1 to 5.1.1 but I don't mind doing whatever's necessary for a major operating system update such as Android 6.0 (Marshmallow).
I did the upgrade yesterday. All sorted.
I only ended up flashing the system.img from the factory image, re-rooted and reinstalling Xposed.
Wasn't as much work as I thought and I didn't lose any data/setting.
This particular minor upgrade seems to have fixed the issue with Netflix deactivating itself; so well worth it in my book. But will only flash minor patches in the future if there is an issue I'm trying to fix like Netflix.
Interesting point about Xposed causing the reboots, I will keep an eye on it. It's only been one night, but it was fine this morning.
They weren't random reboots as such, only happened over night and never while in use. I thought that was normal behaviour for the NP; auto check for update, auto download update, auto install update during night/idle. The issue did seem to line up perfectly with the release of the update.
Thanks for your input!
Found the NP at the recovery screen this morning, booted up and there was an Android update pending.
So I can say for certain that Xposed wasn't causing the reboots. Hasn't reboots itself since I started this thread a month again.
Looks like Google are going to make good on their monthly patching; so I either need to find a smooth way to update, re-root and re-install Xposed or disable the auto-update feature in Android. It could get painful.
Yeah, I too realized that it was not Xposed but rather the Android system updates which were causing my Nexus Player to reboot in to recovery mode. I'm good for now after flashing the Android 5.1.1 LMY48N factory image but I'm not looking forward to doing clean installs every month to handle security updates. You mentioned your quicker update method in post #4 and perhaps that's as quick as it can be under these circumstances. I wonder if a user can disable automatic update attempts on the Nexus Player by sideloading the Disable Service app which is available at https://play.google.com/store/apps/details?id=cn.wq.disableservice&hl=en.
Disable Service >> System >> Search >> Google Play Services >> Uncheck SystemUpdateService.
Disable Service >> System >> Search >> Google Services Framework >> Uncheck SystemUpdateService.
GabbyWC said:
You mentioned your quicker update method in post #4 and perhaps that's as quick as it can be under these circumstances. I wonder if a user can disable automatic update attempts on the Nexus Player by sideloading the Disable Service app which is available at https://play.google.com/store/apps/details?id=cn.wq.disableservice&hl=en.
Click to expand...
Click to collapse
Twice now I have only flashed "system.img" from the stock ROM without any issue.
- flash system.img in fastboot
- re-root with SkipSolt
- remove Japanese and Korean language with Titanium Backup (to create enough space for Xposed)
- reinstall Xposed in recovery
I haven't lost any settings/config this way and only takes about 20mins.
I'm actually not super keen on disabling auto updates for security and bug-fix reasons, so it's looks like I'm going to have to live with the monthly flash-reroot-reXposed method for now. I might script it if I get the time.
GabbyWC said:
Yeah, I too realized that it was not Xposed but rather the Android system updates which were causing my Nexus Player to reboot in to recovery mode. I'm good for now after flashing the Android 5.1.1 LMY48N factory image but I'm not looking forward to doing clean installs every month to handle security updates. You mentioned your quicker update method in post #4 and perhaps that's as quick as it can be under these circumstances. I wonder if a user can disable automatic update attempts on the Nexus Player by sideloading the Disable Service app which is available at https://play.google.com/store/apps/details?id=cn.wq.disableservice&hl=en.
Disable Service >> System >> Search >> Google Play Services >> Uncheck SystemUpdateService.
Disable Service >> System >> Search >> Google Services Framework >> Uncheck SystemUpdateService.
Click to expand...
Click to collapse
Nexus 6 OS version 6.0.1: This method does not work!
Related
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
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?
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.
Keep getting the update pops up and I dont want to update. Is there a way to disable the update itself?
I tried App Settings > System Apps > Moto Update Services, Force stopped but there isnt Freeze or disable Options like my S8. Any ideas?
Thanks!
I froze it in Titanium Backup. That is if you're rooted of course.
Why don't you just update what's the point in not updating when there is an update.
This is under the developer options. It bugged me too.
I'd have a street party if mine said there was an update, i think it is a myth and no updates actually exist.
lucanoid said:
This is under the developer options. It bugged me too.
Click to expand...
Click to collapse
What option stops the notification? Disabling automatic system updates will still prompt you occasionally to update if there is an update pending.
Using Titanium Backup, I assume freezing Motorola Update Services should be the only app required, correct?
If I wanted an opinion on whether or not I should perform the update, I would have referred to the "should I perform the update" thread - not the "How to disable the G5 plus update notification".
Seems like a very simple thing to understand, no?
Here is the real answer:
adb shell
pm uninstall -k --user 0 com.motorola.ccc.ota
Ok, but more clarification please.
lucanoid said:
This is under the developer options. It bugged me too.
Click to expand...
Click to collapse
Got a new Moto G5 plus (unlocked) with 7.0. Spouse accidentally downloaded update BUT caught the error before installing the update, and did not install. The file is apparently on the phone and now badgers us constantly to install. I want to halt the automatic update process and remove the downloaded update file. I have disabled automatic updates under the 'Developer Options' as you say, but the notice continues, even after reboot. I suspect it is because the update is now resident on the phone and triggers the process, even though it has been switched off under developer options. This phone has not been rooted. I guess the fix will require rooting, but I'm apprehensive about what method is the most current and reliable, specifically for this phone. Any help on how to proceed would be greatly appreciated. Til then, a billion annoyances.
Same issue here - and the update notification is extremely aggressive. It will interrupt anything I'm doing, including videos/music on YouTube.
I vaguely recall reading somewhere that we need to flash a stock recovery and boot.img temporarily, but I don't know if that's accurate. I'm wondering if I should just wipe it and install Unofficial LineageOS.
For clarity, at least in my case:
Phone is rooted
TWRP Recovery
Custom boot.img
Stock ROM
EDIT: I'm trying NeoGeo's advice and freezing Motorola Update Services using Titanium Backup.
This will help you to enjoy clean stock smooth experience on Mi A2 without the OTA being shoved down your throat. I know you can always flash custom ROM, but in my experience there were always a few micro-stutters in the UI and some bugs here and there so I decided to stick to stock with Magisk as the ROM is almost the same as a CAF compiled ROM with no bloat except the Feedback app which I manually disabled.
WHY? Because the monthly OTA updates don't fix anything. So it was annoying to keep updating every month.
- There are some comments here and there which asks to disable just the "Apply update on reboot" in developer options.
But again, it still kept popping up in my notification bar.
- There are ppl saying just disable the notification. But it still goes ahead and downloads the 1.3 GB update zip while phone is idle.
So the final solution which seems to be working for me so far is -
1. Disable "automatic apply update on reboot" from Developer Options.
2. Remove the package named "Dynamic System Updates" using root explorer or ADB, whatever you're comfortable with.
2. Download "Servicely" app from play store (or any service blocker app, really).
3. Disable the following services -
com.google.android.gms.update.SystemUpdateService
com.google.android.gms.update.SystemUpdateGcmTaskService​4. ????
5. Profit.
How to disable updates on Android 9? I downgraded from Android 10 to Pie due to random reboot issues