Hi, folks. Few days ago, I updated my MXP via ota, from 6.0.1 to 7.1.1. As this is my first experience with Nougat, I turned off a particular notification without caution, i forgot what it's about, by long pressing the notification and selected silence.
When I look at Settings > Notifications, it turns out that "System UI" was silenced. (attached screenshot 1)
I don't know how to un-silent it as there is no longer said notification for me to long press, and no option to select (in screenshot 2).
If I use a new user, there is an overwrite dnd option (screenshot 3), so I think this might just be affecting some user preference setting.
I would like to restore this if there is some way besides restoring a complete twrp backup. Clearing its cache didn't help, nor did restoring "System UI 7.1.1" via Titanium-nandroid of the twrp backup. Is it possible to do it through adb, or another method?
Related
Hi,
I have a Nexus 4 on 4.2.2 (stock, locked bootloader, no custom recovery, etc). I don't want to upgrade yet in light of all the issues people seem to be having with 4.3 -- I've even come across people that have had 4.3 hard brick their device. Unfortunately, my phone seems to have already downloaded the update and now its sitting ready to install, one missed click away in the notifications menu. So I have a few questions;
* Why did the update automatically download? Is this default behavior and if so, how do I opt out of downloading future updates automatically? As a side note, I'm particularly pissed because the download could have eaten into my data usage and because I wasn't asked to download it first. Google seems to increasingly love opt-out behavior on its services these days.
* Is there any way I can get rid of the update? I don't want someone else that uses the phone to accidentally click the notification. I also don't want to update until 4.3.x issues are resolved -- maybe 4.3.1, etc. Can I manually delete the upgrade files for 4.3 Google pushed onto my device?
Turn off the device, press and hold volume down and power until the bootloader shows up, using the volume keys scroll to recovery and then press power to select, the recovery should say "No command." so you have to press and hold volume up and power until it unlocks and shows the options, scroll to wipe cache partition and select it.
This will delete the OTA zip.
If you want to prevent it from happening every boot then you will need to get Autostart or an other startup application manager to stop the OTA updater from starting every boot but you need root.
Since you don't have root there is an option but it may cause a problem.
The option is to restrict background data by going to the settings, data usage, menu and enable "Restrict background data".
The problem is that you will not receive emails from gmail, other email clients and such unless you manually refresh that email client to look for new emails.
Sent from my Nexus 4 using Tapatalk 4 Beta
I love 4.3. It seems smoother, has better battery life and has built in permissions settings.
How did someone hard brick their device doing an update? I find that hard to believe. Did they manage to run it over with a truck while it was installing?
Not sure if this is related, but I rooted my phone yesterday, went through and formatted data, etc (twice since it needed to be done after a bootloader unlock and again when I installed supersu), set up my phone and restored data with the LG backup I made, and everything is working great. Only problem (that I've noticed so far) is that my second screen doesn't give quick toggles as an option. It was there before rooting so, again, not sure if it's related. Any way to get it back?
Never mind, figured it out. Occurred to me that I froze something called "Quick Tools" via Titanium Backup because I didn't recognize it and I didn't have a "run app" option. But tada, it's back now.
I have the Verizon variant V20 and rooted with Dirty Santa last night. I have gone into developer options and turned off automatic system updates, but it still downloaded an update today and asked to apply it. I hit the later option and delayed it until tomorrow. How do I delete that update file and prevent it from trying again in the future? I have TiBu installed, so hoping there is something I can freeze to prevent it.
Search for "system update" in titanium backup and freeze the two apps you see.
I don't know about deleting the downloaded update though... Browse through and find it?
I just froze the two system updates and also FOTA Update 7.0. Thanks for the help!
Anyone know the file names for the tmobile variant?
If anyone had an issue freezing these apps with TB just open up your dialer interface and type in 277634#*#
This will bring up a hidden menu and then select Wi-Fi test and then select OTA then select disable. After that you will have to kill the hidden menu and you shouldn't be seeing the annoying OTA icon in your status bar anymore.
Had this problem on AT&T H910 it's an easy fixer.
1. boot into TWRP go to wipe and clear cache and Dalvic and reboot
This rids you of the annoying wanna update msg and gives you time to fix it
2. Go to playstore and install DisableService
3. Open and find Software Update open it and disable everything reboot and your good 2 go....
4. Just in case... Go to Developer options and see if you have a checkbox for Automatic System Updates and turn it off ( after using step 3 it most likely is but turn it off anyway)
Just curious, can't u just go to Developer Settings and turn off "Automatic System Updates" ?
TBPro pulls "FOTA Update 7.0" and "System updates 1_16_02_0"
I've frozen both of them and assume that will do the trick for the popups. But would wiping their data remove the updates that they already downloaded (not installed)? Also, would deleting these apps cause any issue with the device? Just curious...
https://forum.xda-developers.com/showpost.php?p=72463487&postcount=4237
On Tmo H918. The above link has a pic that shows the screen mentioned below.
Here's how I got rid of a previous update:
Rename otacerts.zip in /system/etc/security to otacerts.bak.
The full update is found in the cache partition called update.zip. Move the update.zip file from /cache directory (I put it on the sd card).
The next time you get the notification, selected to install it. See the attached. It said rebooting. It won't reboot because the necessary file is gone. Wait 10 seconds and touch the recents key and close the window. Done!
I rebooted the phone and no nag.
Would just like to point out if you click on system updates it will still download, but it won't install you'll have to delete the update zip again, but you shouldn't get any notifications.
crazyc78 said:
If anyone had an issue freezing these apps with TB just open up your dialer interface and type in 277634#*#
This will bring up a hidden menu and then select Wi-Fi test and then select OTA then select disable. After that you will have to kill the hidden menu and you shouldn't be seeing the annoying OTA icon in your status bar anymore.
Click to expand...
Click to collapse
I tried this on my H910 and it says "Connection problem or invalid MMI code."
This is what I did on H918.
https://forum.xda-developers.com/showpost.php?p=72463487&postcount=4237
androiddiego said:
This is what I did on H918.
https://forum.xda-developers.com/showpost.php?p=72463487&postcount=4237
Click to expand...
Click to collapse
Mine's already named .bak. Still getting the notification.
ArmOfAtlas said:
TBPro pulls "FOTA Update 7.0" and "System updates 1_16_02_0"
I've frozen both of them and assume that will do the trick for the popups. But would wiping their data remove the updates that they already downloaded (not installed)? Also, would deleting these apps cause any issue with the device? Just curious...
Click to expand...
Click to collapse
Does anyone else find a different wording of this "System updates 1_16_02_0" ? Am I the only person who's TiB shows it to be called "Software updates 1.16.02? I figure that this "Software updates" is what everyone is talking about because it has the same version build numbers with the exception of not having the trailing 0 at the end. It seems highly unlikely that there would be a coincidence where two different programs would have the same version build numbers.
I have had to restore my rooted factory ROM several times after I have tried to remove some factory installed things which apparently were too deeply tied into android to be safely removed. My nandroid backup which I often restore to is pretty much untouched with the exception of SU and TiB being installed. So I've had the luxury of dealing with this multiple times now. I just want to know if people are seeing a different program called "System updates" than I am seeing it as being called "Software Update."
wargear said:
Had this problem on AT&T H910 it's an easy fixer.
1. boot into TWRP go to wipe and clear cache and Dalvic and reboot
This rids you of the annoying wanna update msg and gives you time to fix it
2. Go to playstore and install DisableService
3. Open and find Software Update open it and disable everything reboot and your good 2 go....
4. Just in case... Go to Developer options and see if you have a checkbox for Automatic System Updates and turn it off ( after using step 3 it most likely is but turn it off anyway)
Click to expand...
Click to collapse
Ok so i got this OTA I was going to update to SuperV 4.0 to try to fix this which told me to update my TWRP...So I went to the app to update and now somehow I have no TWRP and I cannot get my phone to show properly in LGUP because it come up unknown device I cant push that way either now...I am stuck on about 1 minute or so of a loop of the OTA update...obviously my phone wont work for much...I did freeze FOTA in TiBu but there are no system update or software update to freeze...PLEASE HELP ME I have been trying to figure this out for 2 days now...
---------- Post added at 01:52 PM ---------- Previous post was at 01:42 PM ----------
Dgsaxhitman84 said:
Ok so i got this OTA I was going to update to SuperV 4.0 to try to fix this which told me to update my TWRP...So I went to the app to update and now somehow I have no TWRP and I cannot get my phone to show properly in LGUP because it come up unknown device I cant push that way either now...I am stuck on about 1 minute or so of a loop of the OTA update...obviously my phone wont work for much...I did freeze FOTA in TiBu but there are no system update or software update to freeze...PLEASE HELP ME I have been trying to figure this out for 2 days now...
Click to expand...
Click to collapse
Ok so i got into Download mode and LGUP recognized the phone...The issue you ask??? It was the usb port i had it plugged into...Here's more...
I didn't had the same issue as you, but had a similiar one (phone didn't get discovered neither by LGUP nor LG Flash Tool). Yesterday I fixed it by following this guide:
http://forum.xda-developers.com/show....php?t=2785089
I upgraded my device (it is actually a Huawei GT3 NMO-L31C432, but basically identical to the P9 lite) to Nougat couple of days ago. There were some issues regarding automatically upgrading, so I upgraded using fastboot etc. My model number and build number got messed up (NDR test keys) but apart from that all functionality seemed to be there (Wifi, mobile data, camera, sound etc) so I just fixed that in build.prop. However, I noticed a serious issue with push notifications (e.g. WhatsApp) and figured that this is pretty common for EMUI (this is my first Huawei device), so I went through all the settings to see if I could fix the issue (don't close WhatsApp automatically, ignore battery optimizations for WhatsApp, grant unrestricted data access, priority notifications). Yet, the issue couldn't be solved.
So I decided to wipe the phone through TWRP and reflash the firmware (basically following the steps outlined here: xxx/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532 Replace "xxx" with "https://forum.xda-developers.com/"). IMPORTANT REMARK: Before wiping and reflashing, I could change the ringtone etc - no issues.
Now, after configuration of the fresh system (root, restore most important apps using TitaniumBackup) it seems that the push notifications work fine. However, I can no longer change ringtone/notification sound in the system settings: Settings -> Sound (I apologize if these are not the usual expressions used in the English UI, I am using the German one). From there, I have options to open up other menus, such as ringtones for SIM1 and SIM2, or notification sound. If I press on those, it looks like they get "activated" but nothing happens. Settings in the same menu (Settings -> Sound) that just require to be activated/deactivated such as vibration on/off or a "sound when screen is locked" work fine. It is just that I can not open the list to choose between the preinstalled sounds. As a workaround I downloaded an app from the PlayStore and changed the ringtone via this app - no issue.
What I already tried/checked:
- Wipe Cache/Dalvik/ART through TWRP
- check /system/media/ringtones and /system/media/notifications -> all exist and all default sound .ogg files are there
- reflash just the system.img and wipe cache afterwards
Nothing of this helped. What could be wrong? What else could I try? In case someone suspects I messed up some files/settings using root: shouldn't be the case. All I did was flash the TWRP through fastboot, flash the recent SuperSU.zip and then used root access to setup AfWall+, AdAway and TitaniumBackup. TitaniumBackup was used to restore most important apps (mail, some office apps and such - NO system tweaks whatsoever). It also seems (only sometimes) like the settings in general are a bit laggy - very rarely they "freeze" for a second or so or if I want to get back to the previous page a black screen appears for a fraction of a second (as if settings crashed - but I end up where I want to).
_theluk_ said:
I upgraded my device (it is actually a Huawei GT3 NMO-L31C432, but basically identical to the P9 lite) to Nougat couple of days ago. There were some issues regarding automatically upgrading, so I upgraded using fastboot etc. My model number and build number got messed up (NDR test keys) but apart from that all functionality seemed to be there (Wifi, mobile data, camera, sound etc) so I just fixed that in build.prop. However, I noticed a serious issue with push notifications (e.g. WhatsApp) and figured that this is pretty common for EMUI (this is my first Huawei device), so I went through all the settings to see if I could fix the issue (don't close WhatsApp automatically, ignore battery optimizations for WhatsApp, grant unrestricted data access, priority notifications). Yet, the issue couldn't be solved.
So I decided to wipe the phone through TWRP and reflash the firmware (basically following the steps outlined here: xxx/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532 Replace "xxx" with "https://forum.xda-developers.com/"). IMPORTANT REMARK: Before wiping and reflashing, I could change the ringtone etc - no issues.
Now, after configuration of the fresh system (root, restore most important apps using TitaniumBackup) it seems that the push notifications work fine. However, I can no longer change ringtone/notification sound in the system settings: Settings -> Sound (I apologize if these are not the usual expressions used in the English UI, I am using the German one). From there, I have options to open up other menus, such as ringtones for SIM1 and SIM2, or notification sound. If I press on those, it looks like they get "activated" but nothing happens. Settings in the same menu (Settings -> Sound) that just require to be activated/deactivated such as vibration on/off or a "sound when screen is locked" work fine. It is just that I can not open the list to choose between the preinstalled sounds. As a workaround I downloaded an app from the PlayStore and changed the ringtone via this app - no issue.
What I already tried/checked:
- Wipe Cache/Dalvik/ART through TWRP
- check /system/media/ringtones and /system/media/notifications -> all exist and all default sound .ogg files are there
- reflash just the system.img and wipe cache afterwards
Nothing of this helped. What could be wrong? What else could I try? In case someone suspects I messed up some files/settings using root: shouldn't be the case. All I did was flash the TWRP through fastboot, flash the recent SuperSU.zip and then used root access to setup AfWall+, AdAway and TitaniumBackup. TitaniumBackup was used to restore most important apps (mail, some office apps and such - NO system tweaks whatsoever). It also seems (only sometimes) like the settings in general are a bit laggy - very rarely they "freeze" for a second or so or if I want to get back to the previous page a black screen appears for a fraction of a second (as if settings crashed - but I end up where I want to).
Click to expand...
Click to collapse
Reflash firmware using dload method.
Thanks for the suggestion. Sorry that I forgot to mention that I tried this already but it always fails after verification if the software package. At 5% when installation should starts it stops "software verification failed. Incompatible software..." although I just want to reflash the one I installed successfully via fastboot.
Would it be dangerous to flash other imgs in the update.app, such as all the modem related ones. Might that even help at all? For many of them I am unsure what they really are, e.g. Trustfirmware.img... I guess xloader is the bootloader?
Try doing a rollback, search for Unified help thread for p9 lite. I've written in detail how to do it.
Thank you very much. Will give it a try later on. Hopefully the dload method for rollback will work
you have to revert back to your original fw and do the upgrade to nougat through hicare.... I had the same problem
This device is driving me insane. The dload method just never tends to work...
What I did:
put the UPDATE.app into dload folder (ROOT of external SD)
Start "dload" method using VOL+ & VOL- & POWER.
Fails after verification: "Software install failed! Incompatibility with current version. Please download the correct update package."
I suspected (after reading the Huawei pdf accompanying the rollback package) that maybe the root access and unlocked bootloader might be an issue. So I reverted the phone back to stock recovery, reflashed system.img to remove root and relocked the bootloader. Yet, dload fails with the same message as before. I think I will go ahead and try the rollback method for the GR5 mini (even though it's for south asia region, but hey... I just want a working phone. Can change CUST later on).
If that also fails I am really tempted to fully wipe the phone using TWRP and flash every single *.img that can be extracted from the UPDATE.app files. If I use a Marshmallow ROM as source for the img files, this should work as well as a rollback, right? Or do I have to expect major issues?
EDIT: The GR5 mini rollback also fails.
Deleting everything won't work... You will just face major issues.
Do you (or anyone else) have any other suggestion what I could try? Currently, as said, I would flash all *.img files that can be extracted from a Nougat UPDATE.app and can be flashed via fastboot (except for xloader.img and fastboot.img, which I believe to be the bootloader and the fastboot stuff, respectively?). Those that can't be flashed via fastboot would be converted to ext4.img files using imgtool and put into the proper partitions using "dd" command via adb. I hope that if I do this for both the ~1.3GB update.zip and the ~0.7GB update_data_full_NMO-L31_hw_eu.zip, the phone (unrooted, locked bootloader) will be in a state that eventually allows the dload method to work... Does this make sense? Are there any partitions that I should never ever flash manually?
So what I now did is probably not the best solution but for now it appears to be an "okay-ish" workaround. Using the C432 oeminfo of a P9-lite I converted my NMO-L31 to a VNS-L31 and then down/upgraded the smartphone to the recent software for the P9-lite. Seems to work now
Hello people,
my M1 is running latest Android 9 ROM, with February 5 update.
I've flashed it and I've noticed that the "Backup now" button is disabled.
I did a factory restore, too, and I have same issue.
I've noticed that Contacts and Photos are fully synced.
I've played a bit with adb and fastboot to force a backup via shell.
It worked, but the button stay disabled as you can see in attached screenshot.
****UPDATE****
I've noticed that "Backup now" button is enabled if NO LOCKSCREEN IS enabled.
If I choose, for example, PIN as lockscreen, "Backup now" is disabled.
Any hint, please?
Regards,
ghale
My guess would be that you have backup ongoing already ("waiting to backup" messages). I have the button enabled, when I click on it, backup starts and button is disabled until task finished (takes a couple of minutes).
There was similar discussion a while ago with some solutions/workarounds:
https://forum.xda-developers.com/mi-a1/help/mi-a1-pie-update-t3893338
BTW : My backup is working fine since I did the steps I wrote in thread above...
Thanks.
I've tried those steps without success.
I'm going to downgrade and try to see if Backup button works.
Then, I'll upgrade again.
And it's a pain because I have to reinstall everything....
So, to recap: I've downgraded to tissot_images_V10.0.4.0.PDHMIXM_9.0 ROM, then I've done OTA and installed February 5 update.
Now "Backup Now" button is active and works.
What a mess.
I've updated first post with additional info.
Disabling Lockscreen re-enables Backup.
Weird.