Related
I recently forced the updates to get to Mango using the http://www.wpcentral.com/force-mango-update-early-through-zune-software method. I'm on step 8 of 10 on the Mango installation and it appears to have frozen. The small gray bar appears to be at 100 percent but it still depicts the do not disconnect from computer screen. I'm wondering if anyone else has encountered this problem and what I should do. Thanks.
It's possible it just froze and a restart would work.
EDIT: Well I waited for the little gray status bar to get as far as it will go. ie: let it sit there for an hour or two to make sure everything was set. The Zune software said something about a failed update or whatever so I disconnected it. Anyways took two restarts and bam I have Mango working perfectly fine on my phone. Sat a little while on the new Windows Phone logo page.
I have a HTC 7 Trophy and I managed to update succesfully, but I'm dissapointed that there's no difference from the leaked one. No IM integration from yahoo, no skype. Very little customisation
chioreanul said:
I have a HTC 7 Trophy and I managed to update succesfully, but I'm dissapointed that there's no difference from the leaked one. No IM integration from yahoo, no skype. Very little customisation
Click to expand...
Click to collapse
That was 100% unhlepful.
I have the same problem as you. I cancelled the update and disconnected my phone but now my phone will not boot properly. It vibrates 7 times and stays on the HTC start up screen.
Can anyone help us?
using an omni a 7 here, been stuck on step 6 of the process "rebooting your handset" for about an hour now. Handset rebooted a couple of times as I expected before this step but just hangs on this screen. Loading bar stick ticking on and the do nt disconnect screen on the handset but that's it.
hightower1 said:
using an omni a 7 here, been stuck on step 6 of the process "rebooting your handset" for about an hour now. Handset rebooted a couple of times as I expected before this step but just hangs on this screen. Loading bar stick ticking on and the do nt disconnect screen on the handset but that's it.
Click to expand...
Click to collapse
My Omnia did the same. Just unplug the USB cable from your phone, and then plug it back in again. Worked for me!!!
this is just from my experience.
I did have freeze the first time I updated to mango beta few weeks back on part where I had to restarted the phone. I disconnected the usb, and seemed everything was good.
but I connected the phone again, try to look for new update, and zune gave me error. the only way I fixed is by restoring to previous NODO build.
the 2 things I would make sure I have before doing any updates for wp7:
1. battery power is > 50%
2. I would make sure that screen time out is set to NEVER
since then, I never had issue with updates
I hope this helps
Edited because I found the 'fix' or work about. Everything is fine.
to stop Verizon from forcing update
Use Titanium to freeze com.smithmico
i lost root because vz forced the update so i reinstalled .5 oem then used revoluton to unlock boot in stall SU installed .9 radio seems to work well rebboted it pop saying .9 would start download in 26 secs i stoped it from installing
i remembered reading about smithmicro and OTA so i froze it so far n more pushed OTA ...
your mielage may vary
Or just delete it completely. Not needed and is in my top 10 list of things to remove via tb.
Could you tell me exactly how you reinstalled .5 after having .9 already on the phone?
http://www.multiupload.com/WES9PABEQF
rename it PG05IMG.zip copy to sd card reboot do power volume restart it should do it itself don't shutdown until it is completley finished.
I did that but it won't downgrade. It says I have the newest version installed so it won't flash the "older .5" version. Any suggestions?
Make you rename it pull battery two button restart and it will load .5 I had no issues
Sent from my ADR6400L using Tapatalk
davwman said:
Or just delete it completely. Not needed and is in my top 10 list of things to remove via tb.
Click to expand...
Click to collapse
Is that uninstall com.smithmicro.DM 1.0.0 ? Is this the right thing to uninstall for no OTA? Thanks
If so, I think I will uninstall this before I flash the new radio. What do ya think?
i don't see that file... on a side note, i updated the radio this morning and still no message to update so not sure if i'm in the clear or not
so what does com.smithmirco actually do? is it just an updater?
My phone seems to be stuck in the process. I can't locate a p50IMG on the SD card and before I can even open Titanium my phone starts to power down and tries to install the update, but fails. Any ideas?
---------- Post added at 01:51 AM ---------- Previous post was at 12:57 AM ----------
Finally think I figured it out for my situation. As soon as home screen loaded I opened up TasKiller, killed everything. Repeated that 4 times so that everything loading up with the phone was killed before it would reboot the phone. Went to app drawer and made a shortcut for Titanium right next to TasKiller. After this I went in and killed all apps again.
Now let's freeze some things via Titanium so it doesn't try to reboot to install an OTA. First I froze com.smithmicro, next I froze HTC DM. After these two I let the phone go while I messed around for a few minutes, after this I turned airplane back off. I checked TasKiller and noticed that an app MCC_OTA had opened, fearing this may be the cause I killed all apps again and went in to Titanium and froze this.
15 minutes later and I've had no issues with cell/data service. I can get into the market, update apps, receiving gmail/email, and Facebook working fine.
Pender1 said:
so what does com.smithmirco actually do? is it just an updater?
Click to expand...
Click to collapse
I am not trying to be an alarmist, but a description from Smithmicro's site sounds strangely similar to the description on the Carrier IQ site. I will let you be the judge.
"Device Management Suite™ (DM Suite) is a standards-based server solution for mobile device management, enabling mobile operators to remotely customize, provision, configure, and diagnose mobile device settings."
http://www.smithmicro.com/products/device-management-suite.aspx
Still running strong, no problems and no force OTA attempts.
Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery and phone rebooted, quickly showed OTA icon and rebooted.
It got to the android man screen and got stuck there. Again pulled the battery and rebooted in to recover. Wipe Davlik cache and regular cache, rebooted and phone appears to be back to normal.
Rooted running Team Gingerbreaton ROM. This is the second time in the last few months that the forced OTA has tried to run itself.
CenFlo said:
Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery and phone rebooted, quickly showed OTA icon and rebooted.
Click to expand...
Click to collapse
Happened to me this morning too. Good thing the phone sits next to my bed (use it as an alarm) and woke me up since I would have oversleep without it. Of course, I lost two hours of sleep because of it since I couldn't get it working in my half-sleep state and just stayed up because I didn't want to be late to work.
I need a real alarm clock.
CenFlo said:
Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery and phone rebooted, quickly showed OTA icon and rebooted.
.
Click to expand...
Click to collapse
Happened to me as well. Up at 4:30 roughly with nothing working. Cleared cache as suggested and phone is now powered up but no longer showing 3g or 4g, simply 1x so something is still wrong. Have to get ready for work at this point and will have to do some more digging.
CenFlo said:
Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery ... Wipe Davlik cache and regular cache, rebooted and phone appears to be back to normal.
Click to expand...
Click to collapse
Thanks for that. I was losing my mind this morning. Woke up, grabbed phone, and it had the sad Android screen with the Exclamation triangle. Felt like Anakin at the end of Ep. III for a bit. Did a search for "Block update" and came to this thread. Now to flash a non-Verizon ROM so I don't have to go through that again.
Just got another OTA notification this morning, was able to delay it... WTF? I'm rooted running a custom ROM and it's still trying to push this updated.
Just an FYI, if you get the update. Revolutionary root no longer works.
I woke up to my phone stuck on the black screen with the little Android man also. I pulled the battery, powered up and quickly restarted into recovery. Then I factory reset from recovery and after that I re-flashed my shift ROM and all is good so far. *knocks on wood* Anyone think its the new radio I flashed that prompted this or did they push everyone??
zx12dak said:
I woke up to my phone stuck on the black screen with the little Android man also. I pulled the battery, powered up and quickly restarted into recovery. Then I factory reset from recovery and after that I re-flashed my shift ROM and all is good so far. *knocks on wood* Anyone think its the new radio I flashed that prompted this or did they push everyone??
Click to expand...
Click to collapse
I had the same issue -- I received the update even though I had not accepted or checked for it. Took my phone out of my bag at work and saw I was at the Android man and exclamation point screen.
I wiped cache and wiped Dalvik cache, and the update stopped. I did flash the new radios though for the .9 update and have been sitting fine on 4G for the last two hours.
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
marf3 said:
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
Click to expand...
Click to collapse
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
pradctgign said:
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
Click to expand...
Click to collapse
I noticed problems with my ear speaker as well. And i cant make phone calls. The phone doent respond anymore when i try to.
Same problem after android 8.0 update
If you have installed the latest Google phone/dialer app, that is likely the problem, was for me.
Find the app in settings and uninstall,it will roll back to a previous version and hopefully fix your issues.
Sent from my Pixel using Tapatalk
My pixel does the same thing, ever since I updated to 8.0, have you tried doing a factory reset? I haven't done it yet, I have been uninstalling apps for the last couple of days, when it is in safe mode it works good, but when it's not, it freezes and restarts. I'm going to try uninstalling the latest version on google dialer to see if it helps.
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
droid4lif3 said:
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
Click to expand...
Click to collapse
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
wrong place sry
Had this on my pixel xl. I was on the 8.1 beta.
factory reset, rolled back to 8.0
8.1 ota official
haven't had a reboot in over a week now
Murrzeak said:
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
Click to expand...
Click to collapse
Yea, the issue is back, has been for about 2 weeks. This phone is really starting to be a pain in the ass, I can't believe that it happens so often. Did you do a warranty fix?
That's a pity. Yes, I did. Got the device roughly two and a half weeks ago. Flashed 8.0 and then sideloaded 8.1 right away. Knock on wood, all good. But there's still a report every other day in Buganiser of a phone even on 8.1 doing this.
Got mine at release. November 16. Google won't replace it either. I have a one pixel brick
I have the same problem. However, it is not frequent enough on Android P beta. But as soon as I go back to the stable build, it starts to do the same thing. Did you guys have any luck resolving this or should I send it back to the vendor I bought it from. They won't replace the device in Pakistan but may be will fix it in some manner.
Pixel 2 XL on Android P DP2 since it was released at I/O. Yesterday my phone randomly reboot while using it and after I received the notification of DP3. I thought it was weird but whatever. Several times throughout the night it would shut down and go into a boot loop at the G screen. It would eventually correct itself and boot into the OS. At this point I had yet to even tap the notification that DP3 is available for download.
When I got home I attempted to update to DP3 to see if it would fix the issue. It did not. This morning I managed to get back into the phone and did a factory reset. That did not resolve the issue, so I decided to un-enroll from the beta program and waited an hour for the Android O OTA to appear, it never did and still hasn't.
I downloaded an Android O image and loaded it onto the device, it made everything worse. I couldn't even get past the lock screen. In all my troubleshooting I found out that my phone will last longer if it was plugged into a power source.
I contacted Google Support and the end result was because I didn't wait for the Android O OTA and side loaded it, that was the cause of the Android O Issues. I would need to re-enroll into Android P Beta and then wait for the Android O OTA.
So I'm here waiting for the Android O OTA to appear, in the mean time I've barely touched my phone except for a few texts.
I decided to pull a bootlog.txt from the device after the most recent reboot but have no idea how to decipher it, I'm not that technical if it would be helpful to share.
Any advice would be great.
Cerealbowl218 said:
Pixel 2 XL on Android P DP2 since it was released at I/O. Yesterday my phone randomly reboot while using it and after I received the notification of DP3. I thought it was weird but whatever. Several times throughout the night it would shut down and go into a boot loop at the G screen. It would eventually correct itself and boot into the OS. At this point I had yet to even tap the notification that DP3 is available for download.
When I got home I attempted to update to DP3 to see if it would fix the issue. It did not. This morning I managed to get back into the phone and did a factory reset. That did not resolve the issue, so I decided to un-enroll from the beta program and waited an hour for the Android O OTA to appear, it never did and still hasn't.
I downloaded an Android O image and loaded it onto the device, it made everything worse. I couldn't even get past the lock screen. In all my troubleshooting I found out that my phone will last longer if it was plugged into a power source.
I contacted Google Support and the end result was because I didn't wait for the Android O OTA and side loaded it, that was the cause of the Android O Issues. I would need to re-enroll into Android P Beta and then wait for the Android O OTA.
So I'm here waiting for the Android O OTA to appear, in the mean time I've barely touched my phone except for a few texts.
I decided to pull a bootlog.txt from the device after the most recent reboot but have no idea how to decipher it, I'm not that technical if it would be helpful to share.
Any advice would be great.
Click to expand...
Click to collapse
You won't get the OTA until you pull out of the Android beta program. You can pull out for any of your enrolled devices here:
https://www.google.com/android/beta#devices
Just opt out there and you should receive the OTA to go back to Oreo. You won't get any OTA otherwise
TCUofficial said:
You won't get the OTA until you pull out of the Android beta program. You can pull out for any of your enrolled devices here:
https://www.google.com/android/beta#devices
Just opt out there and you should receive the OTA to go back to Oreo. You won't get any OTA otherwise
Click to expand...
Click to collapse
Did that yesterday afternoon, still waiting on the OTA to come through. Ironically the reboots has lessoned considerably, only twice today so far. I've used it minimally though and 1 time was due to trying to open the camera.
Cerealbowl218 said:
Pixel 2 XL on Android P DP2 since it was released at I/O. Yesterday my phone randomly reboot while using it and after I received the notification of DP3. I thought it was weird but whatever. Several times throughout the night it would shut down and go into a boot loop at the G screen. It would eventually correct itself and boot into the OS. At this point I had yet to even tap the notification that DP3 is available for download.
When I got home I attempted to update to DP3 to see if it would fix the issue. It did not. This morning I managed to get back into the phone and did a factory reset. That did not resolve the issue, so I decided to un-enroll from the beta program and waited an hour for the Android O OTA to appear, it never did and still hasn't.
I downloaded an Android O image and loaded it onto the device, it made everything worse. I couldn't even get past the lock screen. In all my troubleshooting I found out that my phone will last longer if it was plugged into a power source.
I contacted Google Support and the end result was because I didn't wait for the Android O OTA and side loaded it, that was the cause of the Android O Issues. I would need to re-enroll into Android P Beta and then wait for the Android O OTA.
So I'm here waiting for the Android O OTA to appear, in the mean time I've barely touched my phone except for a few texts.
I decided to pull a bootlog.txt from the device after the most recent reboot but have no idea how to decipher it, I'm not that technical if it would be helpful to share.
Any advice would be great.
Click to expand...
Click to collapse
You really should post this in the XL forum. There seems to be a much larger userbase, and you'll get more device-specific information and help there.:good:
I have an HTC 10. I have heard so many horror stories on significant battery drain issue after the Oreo update so I have not updated to Oreo yet. I have read somewhere the issue has been resolved on Android's end but there is no more update on the HTC end to incorporate this update for the HTC 10. So every time the Oreo system update prompt came up I did not allow to update to proceed. I had it set to update only on WIFI and always ask me prior.
This morning I must have accidentally hit OK when the prompt came up while I was scrolling the screen for something else and it started to update. I immediately turned off WIFI but it continued the download with my mobile data. So I turned off mobile data as well on my phone. Right now I am at:
Software Update: 3.16.617.2 (1.32GB) Download is paused because your data connection was lost.
Shows a status bar at 3%.
I cannot find a way to cancel or stop this download and subsequent update. Is there a way?
I tried long press on the download screen, the Updater only has options of: Block all, Show silently, On the lock screen, Override do not disturb, all having to do with notification presentations but nothing to cancel the download altogether.
I went into Settings > Apps and popped up Device Configuration and did a FORCE STOP. that didn't do anything. There is an option there to UNINSTALL UPDATES but I didn't touch it since the update hasn't started yet and not sure if this app even deal with system updates.
Just tried a Wipe Cache Partition and rebooted. The system download is still being queued. There is no way to stop this?
I am surprise it will continue to download this huge file even with WIFI off. I had it set to not download any updates unless WIFI, but I guess now I understand it means this is only checked when download started, once it started it will download on my cellular network if WIFI goes out of range? This is a poor design.
Now if I let it download, is there a way to stop the update once the download is completed?
I went ahead and turned on WIFI to allow the downloading to complete. Once it completed it asked me about installing with two options:
Install Now
Install Later
I selected Install Later and it gave me a choice of being reminded again in:
30 minutes
1 hour
2 hours
4 hours
So I selected 4 hours and dismissed it for now. It will ask again in 4 hours, I assume there is no way to dismiss it for a month or a year.
So now I have two questions:
(1) Is there a way to disable this reminder prompt?
(2) Where is this downloaded file? Can I find it with a file manager and delete it? and if it is deleted will it trigger an auto download again or will it go back to just prompting me to download once in a while like before?
miamicuse said:
I went ahead and turned on WIFI to allow the downloading to complete. Once it completed it asked me about installing with two options:
Install Now
Install Later
I selected Install Later and it gave me a choice of being reminded again in:
30 minutes
1 hour
2 hours
4 hours
So I selected 4 hours and dismissed it for now. It will ask again in 4 hours, I assume there is no way to dismiss it for a month or a year.
So now I have two questions:
(1) Is there a way to disable this reminder prompt?
(2) Where is this downloaded file? Can I find it with a file manager and delete it? and if it is deleted will it trigger an auto download again or will it go back to just prompting me to download once in a while like before?
Click to expand...
Click to collapse
There may or may not be a method to disable the update notification but it will require root. You'll probably have to figure out how to disable the notification for yourself.
Try doing a Google search for:
"Disable update notification (your model number)"
Or
"Disable update notification on android"
Sent from my LGL84VL using Tapatalk
well,it just get better and better LOL.
I didn't want to install the system update, but it happened, accidentally. I was out and about, and was in a middle of texting someone, and for a split second while I typed, the system update screen popped up. Since I was in the middle of typing, it took my typing as a confirmation to "Install Now" and began the update. Never mind I only had 31% of battery left at that time and never mind I was not even home and needed the phone. I just can't imagine Google never even bothered with a "Are you sure you want to update now?" prompt. Incredible.
So after it finished the update, a good 30 minutes later, it rebooted, then did more updates, rebooted, and eventually, it started up again, and a lock screen pattern dialog popped up. I put in my pattern and it says it is not recognized. I am certain the pattern is the one I set. Yet something caused the correct pattern to not be recognized. So now I no longer can access my phone. It says I have 28 more tries before it deletes all phone data.
So now I am totally crippled without a chance to even back up all my data.
Anyone know of a way to bypass the lock screen pattern?
If I have to factory reset in order to access my phone again, will the reset bring back Android 7 (original delivered version of the phone) or will it be Oreo (new updated version)?
miamicuse said:
well,it just get better and better LOL.
I didn't want to install the system update, but it happened, accidentally. I was out and about, and was in a middle of texting someone, and for a split second while I typed, the system update screen popped up. Since I was in the middle of typing, it took my typing as a confirmation to "Install Now" and began the update. Never mind I only had 31% of battery left at that time and never mind I was not even home and needed the phone. I just can't imagine Google never even bothered with a "Are you sure you want to update now?" prompt. Incredible.
So after it finished the update, a good 30 minutes later, it rebooted, then did more updates, rebooted, and eventually, it started up again, and a lock screen pattern dialog popped up. I put in my pattern and it says it is not recognized. I am certain the pattern is the one I set. Yet something caused the correct pattern to not be recognized. So now I no longer can access my phone. It says I have 28 more tries before it deletes all phone data.
So now I am totally crippled without a chance to even back up all my data.
Anyone know of a way to bypass the lock screen pattern?
If I have to factory reset in order to access my phone again, will the reset bring back Android 7 (original delivered version of the phone) or will it be Oreo (new updated version)?
Click to expand...
Click to collapse
If you want to keep all of your data intact, root the device, then try this:
https://forum.xda-developers.com/showthread.php?t=2620456
Or this:
https://www.theandroidsoul.com/change-remove-lockscreen-pattern-pin-password-adb-android-oreo/
Or, you can factory reset via recovery, it will wipe all of your data though.
Sent from my LGL84VL using Tapatalk
I have found myself in almost the same situation as the OP.
Like the OP, I don't want to upgrade to Oreo, but somehow did something that my phone interpreted as asking it to start downloading the update. Since my system update is set to download only on WiFi, turning off WiFi stopped the download at 0% done.
*Unlike* the OP, my phone is still in the state of having not yet downloaded the update, so I'm still (for now) securely on Nougat. But my notification bar icon now shows the animated download arrow, and the notification shade shows my system update as "Queued". I'm guessing that this is causing extra battery drain, and it's also really annoying.
I've tried a web search on cancelling a scheduled Android update, and found some interesting information suggesting that I stop the DMClient app. But this wasn't specific to either my phone or to a 7-8 upgrade, and I couldn't find an app by that name installed on my phone. I think I found something else recommending that I stop the Google Play services app and clear its cache. I *do* see that app, but I don't feel like experimenting with random web advice, and so thought I'd check here.
Here are two questions:
1) Is there anything I can do to stop my phone from trying to download and install the Oreo update?
2) If I do a factory reset, which Android would I be on after the reset?
Thanks for any help!
LLGreenGuy said:
I have found myself in almost the same situation as the OP.
Like the OP, I don't want to upgrade to Oreo, but somehow did something that my phone interpreted as asking it to start downloading the update. Since my system update is set to download only on WiFi, turning off WiFi stopped the download at 0% done.
*Unlike* the OP, my phone is still in the state of having not yet downloaded the update, so I'm still (for now) securely on Nougat. But my notification bar icon now shows the animated download arrow, and the notification shade shows my system update as "Queued". I'm guessing that this is causing extra battery drain, and it's also really annoying.
I've tried a web search on cancelling a scheduled Android update, and found some interesting information suggesting that I stop the DMClient app. But this wasn't specific to either my phone or to a 7-8 upgrade, and I couldn't find an app by that name installed on my phone. I think I found something else recommending that I stop the Google Play services app and clear its cache. I *do* see that app, but I don't feel like experimenting with random web advice, and so thought I'd check here.
Here are two questions:
1) Is there anything I can do to stop my phone from trying to download and install the Oreo update?
2) If I do a factory reset, which Android would I be on after the reset?
Thanks for any help!
Click to expand...
Click to collapse
Flash the marshmallow firmware for your device via PC using your devices specific flashtool. It will remove everything and put you back to what you had before triggering the update.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Flash the marshmallow firmware for your device via PC using your devices specific flashtool. It will remove everything and put you back to what you had before triggering the update.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the response, Droidriven.
I actually figured out a way to stop the phone trying to download the update, which I'll describe below, but first I have two questions about the solution you offered: Is there a reason you said to flash Marshmallow firmwaer rather than Nougat, since the update I'm trying to avoid is the one to Oreo? And, if I did that, how would I get back to Nougat?
But I said that I figured out a solution, and I hope that it may help if someone else finds themselves in my situation. Here is what I did:
1) I determined that the app trying to perform the update on my HTC 10 is a system app called "Updater"
I found this by long-clicking on the notification shade item about the update, and selecting more information. The phone displayed notification options for the Updater app.
2) I cleared cache and data for the Updater app
I went to Updater's app info page via via Settings >> Apps >> All apps. Updater is a system app, so I had to use the kebab menu in the upper right corner of the All apps screen to tell the phone to display system apps. Once there, I went to the "Storage" screen and cleared cache and data.
3) I restarted the phone, and "cleaned up" after what I had done
When my phone powered back on after the restart, there was *nothing* at all related to a system update in the notification bar. I turned on cellular data (but left WiFi off), and went to Settings >> About >> Software Updates. The phone checked for a few seconds, during which I could see (behind the "checking" popup) that the box for downloading only over WiFi was clear. This made sense, since this setting must be an option for the app I had just wiped. After maybe 15 seconds, the phone displayed a screen offering me the 3.16.617.2 system update. I used the back button to close that window, which left me on the screen where I could re-check the option to download system updates only over WiFi. Naturally, I re-checked this option.
That's it. My phone is now once again displaying a notification bar icon offering me the Oreo update, but it no longer thinks I told it to proceed with this update. I have been on WiFi a couple of times since doing this, and the phone has not tried to start the download.
I'm guessing that I could get this notification bar icon to go away by hiding notifications for the Updater app, but have not yet done so.
Thanks again, Droidriven, and I hope what I figured out is helpful to someone else.
LLGreenGuy said:
Thanks for the response, Droidriven.
I actually figured out a way to stop the phone trying to download the update, which I'll describe below, but first I have two questions about the solution you offered: Is there a reason you said to flash Marshmallow firmwaer rather than Nougat, since the update I'm trying to avoid is the one to Oreo? And, if I did that, how would I get back to Nougat?
But I said that I figured out a solution, and I hope that it may help if someone else finds themselves in my situation. Here is what I did:
1) I determined that the app trying to perform the update on my HTC 10 is a system app called "Updater"
I found this by long-clicking on the notification shade item about the update, and selecting more information. The phone displayed notification options for the Updater app.
2) I cleared cache and data for the Updater app
I went to Updater's app info page via via Settings >> Apps >> All apps. Updater is a system app, so I had to use the kebab menu in the upper right corner of the All apps screen to tell the phone to display system apps. Once there, I went to the "Storage" screen and cleared cache and data.
3) I restarted the phone, and "cleaned up" after what I had done
When my phone powered back on after the restart, there was *nothing* at all related to a system update in the notification bar. I turned on cellular data (but left WiFi off), and went to Settings >> About >> Software Updates. The phone checked for a few seconds, during which I could see (behind the "checking" popup) that the box for downloading only over WiFi was clear. This made sense, since this setting must be an option for the app I had just wiped. After maybe 15 seconds, the phone displayed a screen offering me the 3.16.617.2 system update. I used the back button to close that window, which left me on the screen where I could re-check the option to download system updates only over WiFi. Naturally, I re-checked this option.
That's it. My phone is now once again displaying a notification bar icon offering me the Oreo update, but it no longer thinks I told it to proceed with this update. I have been on WiFi a couple of times since doing this, and the phone has not tried to start the download.
I'm guessing that I could get this notification bar icon to go away by hiding notifications for the Updater app, but have not yet done so.
Thanks again, Droidriven, and I hope what I figured out is helpful to someone else.
Click to expand...
Click to collapse
Yeah, I actually, meant to say nougat, lol.
Sent from my SM-S767VL using Tapatalk