I am having an issue with updating via OTA with Verizon. The OTA update came out a couple of weeks ago but I never received notice. When I went to search for it I got an error message, no matter where I was or whether it was on 3g, 4g or wifi. The message states "service unavailable". My service is working fine and I can use the internet without any issues. I called Verizon and they didn't know what was causing it but they did confirm I have an update available. I have powered off, taken out the battery cleared cache, tried to update manually with ODIN (which failed) and have come to my wits end. I am trying to avoid factory resetting the device and having to wait for all my apps to be reinstalled. I have rooted several devices before but don't want to do that this time.
Does anyone have a suggestion to help me accept the OTA from Verizon? Again, I am locked and unrooted running everything stock.
Thanks for your help!
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
JayWulf said:
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
Click to expand...
Click to collapse
You need to start over from scratch
post your fastboot getvar all (minus you serial.no and IMEI)
Most likely your using AT&T so if you have s-off you can flash these two and get back two stock. take the OTA Update then re flash recovery and root.
flash this first
http://fs1.d-h.st/download/00101/a1w/4.18.502.7 Custom Firmware.zip
fastboot oem rebootRUU
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot reboot bootloader
now stay on the bootloader
and run this RUU from your PC > http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Take the Over the air update and your all set to start rooting again.
clsA said:
post your fastboot getvar all (minus you serial.no and IMEI)
Click to expand...
Click to collapse
What is this, and how do I do it?
JayWulf said:
What is this, and how do I do it?
Click to expand...
Click to collapse
go to the folder where fastboot and adb are
open a command window (right click / command prompt here)
with the phone plugged into the PC
Type fastboot getvar all
it will output all the specs for your phone
remove the serial no and IMEI when posting it
what if your s-on
I'm having all the exact same problems except I'm 4.3 and s-on. Help please!
Gonna kinda bump this thread a bit because I've got another question - what about the "full unroot" option within SuperSU? Will this help the situation at all, or make it worse?
My ZW2 has never been able to take an OTA update. I have, so far, been manually updating by sideloading with ADB. It's paired to a HTC One M8 and I checked that all the various services are up to date, but I get "downloading" followed by "something went wrong". I've tried it with just the BT connection and with wifi. It just refuses to download the update.
Also, so far only people here seem to have been posting the update zips. Is there an official repository for these updates anywhere?
Thanks!
Note: the watch is bone stock with nothing touched. It's not even bootloader unlocked.
Solved - turned out to be a firewall issue
So, I figured out that it was my phone's firewall causing the problem. I had the Zenwatch manager app blocked. I failed to realize that the phone depended on a local app to download updates.
I am having some issues with the G9 I am working with. I have root using the latest Magisk. But every time a "security update" installs and reboots the phone, I lose root. So I go back into fastboot and reflash the boot img. That solves the problem. But it is a minor nuisance I am trying to workaround. I have tried searching for days, trying to figure out how to STOP system updates. I installed a root service disabler and disabled a few different services.
I still cannot seem to figure out what service is downloading updates. I have already gone into Developer Options and disabled automatic updates. And there was an update waiting that I kept paused. Last night I got the popup reminding me about it. And it was supposed to "remind me later". But instead installed it in the middle of the night.
I could care less about opinions on whether or not to allow updates. I would just like to know what service or file I need to cripple to get it to stop. I want to decide if or when something runs on my phone. Any ideas? Android 9.
And you will lose root after update, it's normal
Sent from my K10 using Tapatalk
If you are using a G9, not a G9 Pro, could you please link me to the stuff to root it?
Last week on Thursday, I allowed Verizon to install their Software Update 21 (April 2020.) It made it as far as the going through the optimizing apps and then was stuck in a boot loop. The phone would be usable for about a minute, then would freeze, and then reboot. If I clicked on the System Update option in settings, it would say that a system update was in progress. I chatted with Verizon, and they ended up telling me that the only way to stop the update was to do a factory reset, which I am doing everything I can not to do that as I don't want to lose my data.
I changed it into maximum power mode and it did stop the update for that time being and I was able to use the phone, texting, etc. This allowed me to at least connect the phone to my computer to backup all of the directories. After many reboots, on Friday it finally stopped doing the update and gave me an error which I think was 410. It thought it was updated, though did show as failed. When checking for updates, it said it was the current version. Twice I was able to get the phone to stop by freezing when going to the app and stopping some programs (sadly, I was not able to remember the exact combination that worked) which allowed me to use the phone like normal. All this while, I was uninstalling a large amount of the apps that I had installed hoping that would minimize whatever may have been causing the problem.
Went to each of the google and samsung apps, stopped, disable, and reverted them all back to factory defaults. Guess that was a bad idea, from then on I received an error as soon as the phone started which caused it to go directly into recovery mode. I chatted with samsung and they thought it might be a hardware issue. I still think it is related to their software update, so not a hardware issue.
By using Odin, I loaded the firmware from March 2020, and when it rebooted, it did go as far as optimizing the apps, though anytime it booted up, it would never get past the white verizon loading screen. It took me hours before I discovered that Odin was failing to load the firmware on the phone as the Windows 10 laptop only had USB 3.0 ports which don't always work with Odin, and ended up being successful using my old Windows XP laptop as the USB 2.0 ports worked fine. After a bit hanging on the verizon loading screen, it would reboot and never went past. I have been able to load the March and April 2020, though none of them will ever get past that white verizon loading screen. I did see something say that in loading TWRP, I could possibly do a full backup of the phone which is what I would like to do.
One time I only loaded the AB file for a different version than I had loaded, and it was the first time it went beyond the white screen, only to tell me that the verification failed and it would need for me to do a factory reset. I was able to reboot the phone without actually doing the reset.
I have read many posts here and the forums on androidcentral, and with so many things, I really needed to post to get guidance from people here that can point me in the right direction for any other things that I can try. As you have read, doing everything that I can to get the phone working by keeping my data. Any help would really be appreciated.