[Q] Installing the latest OTA - Verizon Samsung Galaxy S III

I'm running stock rooted with a few minor tweaks - Notification toggles and Google now installed. Last night I received the message that there was an software update. What happens if I install it? Will I just lose root or will everything be changed back to stock?
EDIT: I misclicked and posted this in the wrong forum. Mods, can you move it?

JoeyBert said:
I'm running stock rooted with a few minor tweaks - Notification toggles and Google now installed. Last night I received the message that there was an software update. What happens if I install it? Will I just lose root or will everything be changed back to stock?
EDIT: I misclicked and posted this in the wrong forum. Mods, can you move it?
Click to expand...
Click to collapse
I updated mine and lost root.
Went through the rooting process again and I have root. No big deal.

Related

[Q] How do I avoid the OTA update?

I got an update notification yesterday, from the DM, and the notification is persistent, popping up and reminding me every few hours. But I do not want to try it since I'm rooted, so many application level mods, and at&t crapware removed.
how do I avoid updating and remove update notifications?
Or, is there a safe way to upgrade while still retaining root and other app mods?
thank you.
I was rooted when I got the ota and it worked fine. I still had the bloatware, no lagfix or other mods. You could always do a Clockwork of the update I897UCJH7 - OTA System, Kernel, Modem - Clockwork Flashable - Rooted and then restore.

Verizon trying to update Custom ROM- TW Eclipse 1.0

Hi, as the title states, yesterday I received a notification from Verizon that a new update is ready to be installed. I can only defer it for 5 days, which I did. I'm running TouchWiz Eclipse ROM 1.0. I went ahead and renamed SMD.apk to SMD.bak, because I read somewhere that's what I needed to do to prevent Verizon from pushing updates.
What I wanted to do is confirm that what I did would work (as in prevent Verizon from updating my awesome ROM and thus bricking my device). Also, I think the update is already downloaded and just ready to be installed. Will that affect anything? Would renaming SMD.apk still prevent it from being installed, or is that only to prevent it from being downloaded?? Please halp!!
Cheers,
ED
ExcludedDroid said:
Hi, as the title states, yesterday I received a notification from Verizon that a new update is ready to be installed. I can only defer it for 5 days, which I did. I'm running TouchWiz Eclipse ROM 1.0. I went ahead and renamed SMD.apk to SMD.bak, because I read somewhere that's what I needed to do to prevent Verizon from pushing updates.
What I wanted to do is confirm that what I did would work (as in prevent Verizon from updating my awesome ROM and thus bricking my device). Also, I think the update is already downloaded and just ready to be installed. Will that affect anything? Would renaming SMD.apk still prevent it from being installed, or is that only to prevent it from being downloaded?? Please halp!!
Cheers,
ED
Click to expand...
Click to collapse
Best way to check is to go into Settings/About Phone/Software Update. If it force closes then you're all set. Renaming or uninstalling "smd 1.0" causes the phone to not actively poll for future OTAs from that moment on. Using a file explorer, check in /cache and delete the update.zip for VRBMF1 cuz you deferred the OTA which means it saved to your phone already.
I checked Settings>About device but there's no Check for upgrade option. I assume it was taken out as part of the ROM. I went ahead and deleted some sort of fupgrade in /cache. Then went and wiped cache in recovery and fixed permissions just to top it off. I think I'm good!! Thanks
ExcludedDroid said:
I checked Settings>About device but there's no Check for upgrade option. I assume it was taken out as part of the ROM. I went ahead and deleted some sort of fupgrade in /cache. Then went and wiped cache in recovery and fixed permissions just to top it off. I think I'm good!! Thanks
Click to expand...
Click to collapse
i think eclipse is aosp not touchwiz , iam running the same thing but its aosp eclispe here the link to verified
http://forum.xda-developers.com/showthread.php?t=2142267 if it is you will never have problems of verizon trying to push ota updates
xavierxxx2p said:
i think eclipse is aosp not touchwiz , iam running the same thing but its aosp eclispe here the link to verified
http://forum.xda-developers.com/showthread.php?t=2142267 if it is you will never have problems of verizon trying to push ota updates
Click to expand...
Click to collapse
There is a touchwiz version, it just wasn't updated in awhile and it's pretty buried in the development section.
Sent from my SCH-I535 using Tapatalk 4 Beta

[Q] Received OTA update, failed while Installing. Not getting OTA update notification

Hi folks,
I received the OTA update notification for Android 5 yesterday, downloaded it and while installing it - I received an error and the device restarted to normal Android mode (Kitkat 4.4.4 - Nexus 5). I dont know what went wrong, the OTA notification is gone now. And I tried many times for updating the device via OTA, but there is no update information.
Wanted to know the following things:
1. Does any one had similar problems like this?
2. What really went wrong?
3. Will I get the OTA update or should I follow any of the manual method?
PS: Device Used : Nexus 5 - running Kitkat 4.4.4 - Rooted via TowelRoot - Stock ROM
If you feel I miss any major inputs, please do comment, so I can add it.
TIA Have a Great day !!
If it failed chances are you've made a change to a system app/file which is why it's failing. You have to be 100% stock to successfully apply an OTA update
Thanks for the quick response !!
EddyOS said:
If it failed chances are you've made a change to a system app/file which is why it's failing. You have to be 100% stock to successfully apply an OTA update
Click to expand...
Click to collapse
Thanks for the quick response !!
Does unroot help in here? How about unroot and factory reset?
Will I get the OTA anyway?
gladijames said:
Thanks for the quick response !!
Does unroot help in here? How about unroot and factory reset?
Will I get the OTA anyway?
Click to expand...
Click to collapse
If you're the chosen one then, yes, you should get it again.

Android updating and apps reverting after reboot

After every reboot, I get the android is updating screen as well as all the apps i update, revert back to the unpdated verison. I am running the lastest update rooted and i flashed the zip to enable hotspot, any help would be great.
danny249 said:
After every reboot, I get the android is updating screen as well as all the apps i update, revert back to the unpdated verison. I am running the lastest update rooted and i flashed the zip to enable hotspot, any help would be great.
Click to expand...
Click to collapse
I don't remember what the deal is but this problem has been discussed recently. I think it has something to do with duplicate /data folders or something like that. Search around, it's here somewhere. Possibly in more than one Q/A or Rom development thread
danny249 said:
After every reboot, I get the android is updating screen as well as all the apps i update, revert back to the unpdated verison. I am running the lastest update rooted and i flashed the zip to enable hotspot, any help would be great.
Click to expand...
Click to collapse
http://forum.xda-developers.com/ver...lipop-apps-reverts-to-version-reboot-t3076563

[SOLVED] OTA updates and root : need help

Hello xda.
A few weeks ago I started getting this notification telling me a new system update was available but when I tried to do it, it wouldn't install. I quickly discovered it was because my device was rooted. I followed this guide to get the update (more to get rid of the annoying notification really) ; I made sure do download the right stock image (my device is a XT1541 2 GB) and to flash all the system.img_sparsechunk files (there are 8 in this case) and it went smoothly (booted alright) up until the rooting part.
Basically, I followed RootJunky's video tutorial but after applying the root I can't get past the bootloader's warning screen. The only difference between me and RJ is both TWRP and SU I used are more recent versions (the latest ones).
In the end I just restored the backup I had made "just in case" before the manual update (boy am I glad I made this one) and my phone's back to working order, except not updated.
So here I am : what can I do about it? Is it still possible to root this phone (youtube commentaries indicate I'm not the only one with this issue)? Worst case scenario, is there a way to get rid of the update notification?
Any help is appreciated.
You'll need a systemless root.
Broadcasted from Zeta Reticuli
How to root ANY Moto G 2015 model on Marshmallow
Thank you both for your answer.
Turns out the method linked didn't work for me. Not only was the root not applied according the supersu app, but I still got an update notification after 'rooting' the phone (even though I checked for update after booting the newly installed rom for the first time and there wasn't any).
I decided to go a different route and used Titanium Backup to freeze the Motorola Update app. Hopefully this will do the trick of sparing me the notifications until I can figure out how to get OTA updates.
Isley_FR said:
Thank you both for your answer.
Turns out the method linked didn't work for me. Not only was the root not applied according the supersu app, but I still got an update notification after 'rooting' the phone (even though I checked for update after booting the newly installed rom for the first time and there wasn't any).
I decided to go a different route and used Titanium Backup to freeze the Motorola Update app. Hopefully this will do the trick of sparing me the notifications until I can figure out how to get OTA updates.
Click to expand...
Click to collapse
No offense, but if you didn't have root then TiBu wouldn't work properly... Obviously the rooting worked.
Rooting itself doesn't prevent updates or there notification, it just keeps it from being applied properly. Freezing the app in TiBu should prevent it though.
acejavelin said:
No offense, but if you didn't have root then TiBu wouldn't work properly...
Click to expand...
Click to collapse
I forgot to mention I restored my functional backup when I saw my manipulations didn't work. I used TB after that.
Isley_FR said:
I forgot to mention I restored my functional backup when I saw my manipulations didn't work. I used TB after that.
Click to expand...
Click to collapse
Fair enough..
Quick update : after a couple more tries I successfully rooted my phone by following this method.
I now have the latest stock rom and it's rooted
Thank you for existing XDA! :good:

Categories

Resources