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.
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
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!
Hello,
I am on stock 6.0.1 locked bootloader. Yesterday suddenly my software got partially corrupted. It boots fine but the status bar and on screen controls like menu button are not working. Also, clicking on build number isn't doing anything. An ota was available and I updated it but still its in the same state. Fast boot mode is accessible. I am using xt1562. Is there any way by which I can flash a full stock/custom firmware with/without rooting/unlocking my phone? I tried to download the stock recovery from github/filefactory but it keeps on getting canceled after 200mb or so. Can someone please guide me or provide me a resumeable link to 107.70 firmware? TIA
Regards
redlag said:
Hello,
I am on stock 6.0.1 locked bootloader. Yesterday suddenly my software got partially corrupted. It boots fine but the status bar and on screen controls like menu button are not working. Also, clicking on build number isn't doing anything. An ota was available and I updated it but still its in the same state. Fast boot mode is accessible. I am using xt1562. Is there any way by which I can flash a full stock/custom firmware with/without rooting/unlocking my phone? I tried to download the stock recovery from github/filefactory but it keeps on getting canceled after 200mb or so. Can someone please guide me or provide me a resumeable link to 107.70 firmware? TIA
Regards
Click to expand...
Click to collapse
You should be albe to flash original firmware with locked bootloader, the best option is to flash exactly the same one you've currently got on your phone.
However, I'd start from installing Activity Launcher (download from playstore) and launching com.google.android.setupwizard.SetupWizardTestActivity. It looks like yor phone is in setup mode for some reason, just like it is when you boot it for the very first time. This activity will take you through the Setup Wizard, hopefully something "clicks" in your system when you finish it and your home button functions, etc. will be restored. If this doesn't work I'd try factory reset before flashing firmware.
minimale_ldz said:
You should be albe to flash original firmware with locked bootloader, the best option is to flash exactly the same one you've currently got on your phone.
However, I'd start from installing Activity Launcher (download from playstore) and launching com.google.android.setupwizard.SetupWizardTestActivity. It looks like yor phone is in setup mode for some reason, just like it is when you boot it for the very first time. This activity will take you through the Setup Wizard, hopefully something "clicks" in your system when you finish it and your home button functions, etc. will be restored. If this doesn't work I'd try factory reset before flashing firmware.
Click to expand...
Click to collapse
I have 107-70-1 but cant seem to be able to find it? The other one is not a resumeable link and downloads break in between. I will try the activity launcher and let you know. I already tried factory reset from setting and facroty mode from fastbook but it did not work.
Edit: The activity Launcher thing worked! Thanks!
redlag said:
Hello,
I am on stock 6.0.1 locked bootloader. Yesterday suddenly my software got partially corrupted. It boots fine but the status bar and on screen controls like menu button are not working. Also, clicking on build number isn't doing anything. An ota was available and I updated it but still its in the same state. Fast boot mode is accessible. I am using xt1562. Is there any way by which I can flash a full stock/custom firmware with/without rooting/unlocking my phone? I tried to download the stock recovery from github/filefactory but it keeps on getting canceled after 200mb or so. Can someone please guide me or provide me a resumeable link to 107.70 firmware? TIA
Regards
Click to expand...
Click to collapse
First of all when you have the opportunity quickly go to the developer mode and check OEM unlock. Then you use fastboot to flash stuff and get things correct
there is also usb debbuging app on playstore to access from there..
kos25k said:
there is also usb debbuging app on playstore to access from there..
Click to expand...
Click to collapse
It won't work if the phone is in setup mode and Developer's options aren't unlocked
i remember lately i had formated my phone and for some unknow reason my dev. mode wasn't showing atall.then i tryied this app and solved it.it doesn't have dev. options inside,it just opens stock devs. settings.
kos25k said:
i remember lately i had formated my phone and for some unknow reason my dev. mode wasn't showing atall.then i tryied this app and solved it.it doesn't have dev. options inside,it just opens stock devs. settings.
Click to expand...
Click to collapse
AFAIK you can't do it in setup mode, even with an app, because ADB access is blocked on system settings level.
ooooh yes sorry.mine was booting normally..
minimale_ldz said:
You should be albe to flash original firmware with locked bootloader, the best option is to flash exactly the same one you've currently got on your phone.
However, I'd start from installing Activity Launcher (download from playstore) and launching com.google.android.setupwizard.SetupWizardTestActivity. It looks like yor phone is in setup mode for some reason, just like it is when you boot it for the very first time. This activity will take you through the Setup Wizard, hopefully something "clicks" in your system when you finish it and your home button functions, etc. will be restored. If this doesn't work I'd try factory reset before flashing firmware.
Click to expand...
Click to collapse
You were right, it was in setup mode. I was unable to install apps over the Google Play Store so I downloaded the apk of Activity Launcher, enabled "unknown sources" and installed it. I opened the activity you wrote but I got an error, so I opened the com.google.android.setupwizard.SetupExit (not sure if it was the exact name) and it was all normal again.
Polyparadox said:
You were right, it was in setup mode. I was unable to install apps over the Google Play Store so I downloaded the apk of Activity Launcher, enabled "unknown sources" and installed it. I opened the activity you wrote but I got an error, so I opened the com.google.android.setupwizard.SetupExit (not sure if it was the exact name) and it was all normal again.
Click to expand...
Click to collapse
Nice, seems like it's even easier way. Thanks for the feedback and a good tip.
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.
I have rooted my phone and installed Titanium Backup. What processes do I need to freeze to prevent OTA updates from automatically downloading and installing? I tried the usually keywords, but it seems like the only process that might be an updater is ConfigUpdater. Is that all I need to freeze? Thanks.
awdrifter said:
I have rooted my phone and installed Titanium Backup. What processes do I need to freeze to prevent OTA updates from automatically downloading and installing? I tried the usually keywords, but it seems like the only process that might be an updater is ConfigUpdater. Is that all I need to freeze? Thanks.
Click to expand...
Click to collapse
If you're rooted, OTAs won't install anyway.
spotmark said:
If you're rooted, OTAs won't install anyway.
Click to expand...
Click to collapse
Can I stop it from downloading at all? Thanks.
awdrifter said:
Can I stop it from downloading at all? Thanks.
Click to expand...
Click to collapse
I don't think it will automatically download, but you're always going to have the notification telling you an update is available.
So far I've found an option called "Automatic System Updates" in Developer Options, I have turned that off. I guess there's no way to block it from checking for new updates?
I think I've figured out what to block to prevent the update from downloading. I use AdAware to log the DNS requests when the phone is trying to download an update. There where a few URLs, but the one needs to be blocked seems to be redirector.gvt1.com. After blocking this url the OTA update download will pause itself (probably because it can't reach the server). I don't know what other Google services it'll affect, but I've tried downloading an app from Play Store and searching for an address in Google Map, they still work. So I'm going to block that URL for now. I can always temporarily unblock it for certain app updates if they need that redirector url.
Same Problem here
I have a Rooted Lenovo Yoga Tab YT3-850M running Android version 6.0.1, and I am struggling with this same issue. I used TWRP and Magisk.
Even if I enable Developer Options, there is no option to turn off Automatic Updates.
And it keeps downloading and installing the OTA System Updates. It fails to install, but keeps on doing it again and again.
I don't know how to stop it. The only thing is I disabled it from doing the Update over Mobile Data, and I switched off the Wifi to get some relief.
And am now hunting online for some method to either install the OTA, and go back to Root (or) to Disable OTA Updates permanently...
Saro43 said:
I have a Rooted Lenovo Yoga Tab YT3-850M running Android version 6.0.1, and I am struggling with this same issue. I used TWRP and Magisk.
Even if I enable Developer Options, there is no option to turn off Automatic Updates.
And it keeps downloading and installing the OTA System Updates. It fails to install, but keeps on doing it again and again.
I don't know how to stop it. The only thing is I disabled it from doing the Update over Mobile Data, and I switched off the Wifi to get some relief.
And am now hunting online for some method to either install the OTA, and go back to Root (or) to Disable OTA Updates permanently...
Click to expand...
Click to collapse
If you guys are talking about ROM OTA system monthly update, then the solution is very simple.....use FOTAkill
chanh2018 said:
If you guys are talking about ROM OTA system monthly update, then the solution is very simple.....use FOTAkill
Click to expand...
Click to collapse
The solution is even simpler:
There won't be any more monthly QTA updates for this phone anyway, as the company behind the phone went bankrupt and stopped doing updates since February 2020...
Pa9an said:
The solution is even simpler:
There won't be any more monthly QTA updates for this phone anyway, as the company behind the phone went bankrupt and stopped doing updates since February 2020...
Click to expand...
Click to collapse
Yeah, we knew that, but many people don't use Feb because TWRP doesn't work well with it, so they rolled back to Jan, and that's why the OTA kicks in.
chanh2018 said:
Yeah, we knew that, but many people don't use Feb because TWRP doesn't work well with it, so they rolled back to Jan, and that's why the OTA kicks in.
Click to expand...
Click to collapse
All right...sorry, this happens if one is only readying through half the story...
...was already surprised to be the first one to have that mentioned - now this explains it :silly:
Nevermind... :angel:
did anyone find a working solution? I tried FOTAkill but it did not work. I also tried editing the build.prop, but i am still seeing the update icon appear after a few hours.
Thanks,
JD
JudasD said:
did anyone find a working solution? I tried FOTAkill but it did not work. I also tried editing the build.prop, but i am still seeing the update icon appear after a few hours.
Thanks,
JD
Click to expand...
Click to collapse
Where did you put Fotakill? Try to put it in /system/priv-app folder
chanh2018 said:
Where did you put Fotakill? Try to put it in /system/priv-app folder
Click to expand...
Click to collapse
I did try that folder as well, but it's not removing the update. The app also deletes itself upon reboot from /system/app and /system/priv-app
Thanks,
JD
JudasD said:
I did try that folder as well, but it's not removing the update. The app also deletes itself upon reboot from /system/app and /system/priv-app
Thanks,
JD
Click to expand...
Click to collapse
Hmm...that's strange....and you said it's gone after reboot which never happened to me.
Making sure you're using the right version from xda ( and your device is rooted, I assumed)
https://forum.xda-developers.com/showthread.php?t=2249350
chanh2018 said:
Hmm...that's strange....and you said it's gone after reboot which never happened to me.
Making sure you're using the right version from xda ( and your device is rooted, I assumed)
https://forum.xda-developers.com/showthread.php?t=2249350
Click to expand...
Click to collapse
I did the same exact thing 4 times in a row and it is now persistent through reboots. Try number 2 caused magisk to claim no root after reboot. Very weird.
My wife has the same phone and the exact same setup, it took 3 tries to make hers work. Her phone never lost root.
Neither phone is prompting for updates. Very cool! This is a step in the right direction.
Both phones do show the update available notification icon on the right side of the notch. Should this go away as well? I tried multiple cache/dalvik wipes to no avail.
Thanks,
JD