So, I noticed that my S4 had a new software update and I started to download it, then walked back to my desk to read what was in it and was surprised to find out that the new update would lock the bootloader (which I definitely don't want). As of now, I'm delaying INSTALLING it but because it was downloaded, it keeps bugging me to install it.
My question was am I still good to root my phone, even if it's been downloaded to my phone? Or is it likely the bootloader has already been locked and installing the update will just install the rest of the files? I assume now is probably the best time to root it (since I likely won't have the option down the road). I just wanted to check with you guys first. Let me know when you get the chance. Thanks!
jbrookley said:
So, I noticed that my S4 had a new software update and I started to download it, then walked back to my desk to read what was in it and was surprised to find out that the new update would lock the bootloader (which I definitely don't want). As of now, I'm delaying INSTALLING it but because it was downloaded, it keeps bugging me to install it.
My question was am I still good to root my phone, even if it's been downloaded to my phone? Or is it likely the bootloader has already been locked and installing the update will just install the rest of the files? I assume now is probably the best time to root it (since I likely won't have the option down the road). I just wanted to check with you guys first. Let me know when you get the chance. Thanks!
Click to expand...
Click to collapse
You can still root it if the update wasn't installed. As long as it says your on mdk and not on me7 under "about phone" in the settings you should have no problem rooting. After rooting use a app like titanium backup or my backup pro to freeze sdm and fwupgrade....in system apps.
jbrookley said:
So, I noticed that my S4 had a new software update and I started to download it, then walked back to my desk to read what was in it and was surprised to find out that the new update would lock the bootloader (which I definitely don't want). As of now, I'm delaying INSTALLING it but because it was downloaded, it keeps bugging me to install it.
My question was am I still good to root my phone, even if it's been downloaded to my phone? Or is it likely the bootloader has already been locked and installing the update will just install the rest of the files? I assume now is probably the best time to root it (since I likely won't have the option down the road). I just wanted to check with you guys first. Let me know when you get the chance. Thanks!
Click to expand...
Click to collapse
If it only downloaded, and you did not install it, then you are good to root. I would delete the update.zip file from the cache to be safe though.
Please read forum rules before posting
Questions and Help issues go in Q&A and help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Related
Help.
I have a rooted Thunderbolt and I have been able to reject the update from Verizon until this afternoon when my phone started to update on its own. The update didn't go through and I got an error icon. Now my phone just goes through the same cycle of turning it self off and trying to update and crashing.
I am able to get to the Clockwork Mod recovery page but the only option that works is the 'reboot system now', which starts the phone and the whole cycle of trying to update is started.
Does anyone have an idea of how to get my phone working again?
Thanks in advance.
Mike
I'm really sorry to hear that happened, I'm not sure what you can do. Hopefully someone will be able to help you out. But at least I can tell you that you are not alone! I wasn't rooted, but my phone did autoupdate on its own at about 2:30pm today.
I posted about it here: http://forum.xda-developers.com/showthread.php?t=1234844
Pull your SDcard, wipe the pg05img.zip file, and try again. You might have to reflash clockwork.
This is the problem with running rooted stock ROMs. I know flashing a new ROM isn't what a noob wants to do, but it will avoid these very confusing headaches.
whats if you rooted using revolutionary? As far as i know there wont be that pg05img.zip file to delete.
Would you always be in danger is this if you are rooted and stay stock?
Why would someone want to root their phone and stay stock ??????
Sent from my Verizon LTE 4G Thunderbolt
loonatik78 said:
This is the problem with running rooted stock ROMs
Click to expand...
Click to collapse
Nope. One only has to keep up with the current releases, rooted versions of which come out within days of official release.
Are you sure it is the Verizon update?
I have the same behavior on my T-bolt since about 10 pst today. However, just before the phone shuts down to reboot, I see a note about a new version of Clockworkmod Recovery 4.0.1.5.
So I have been working on the assumption that it is CWM Recovery that is doing an automatic update.
I also am running rooted stock, and have not updated to latest release.
OK, it isn't the update to CWM Recovery that is the problem; it is the Verizon OTA update, which they have figured out how to force on us. I fixed my phone using the solution given by Mike later in this thread.
jbh00jh said:
Why would someone want to root their phone and stay stock ??????
Sent from my Verizon LTE 4G Thunderbolt
Click to expand...
Click to collapse
Debloating. Stock is pretty damn nice without all the extra crap.
*Madmoose* said:
Debloating. Stock is pretty damn nice without all the extra crap.
Click to expand...
Click to collapse
This, plus "root while you can" - there's no guarantee that rooting will be possible with each subsequent (unrooted) release, but you can root now and stay rooted to keep your options open. Also, getting full backups of everything is easier when rooted.
Did the fix work?
Mike, did you try what loonatik suggested? Did it work? Waiting breathlessly...
Unless I am misunderstanding the problem wiping cache from Clockwork recovery should clear out the update and it will quit trying to install it. For the future if you go to settings in the about phone or software update section (dont remeber which) there is an option to de-select scheduled update checks.
Sent from my HTC Thunderbolt
Wait.. what? Most ROMs I've seen are debloated.. At the very least they have VZW crap removed
Thanks guys for all your help and interest. I tried the solution offered by lunatic but it did not work. Thanks any way I was still looping through continuous on and off cycle. I did however did find a solution on another site. Here is the solution from Sele.
http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/2257-rs-guide-how-get-rid-ota-forced-reboots-rooted-phone.html
It was easier fix than I thought it would be. Step #1 worked.
I also did this to stop the update from happening again.
"If you are rooted use root explorer or super manager and set system to R/W. Then navigate to /system/etc/security. Find the file named otacerts.zip and rename it to otacerts.zip.bak and reboot. Should fix you up."
I'm sorry I can't remember who offered this solution to give credit to. I haven't had any updates yet but only time will tell.
Good Luck with your phone.
JBO1018 said:
Unless I am misunderstanding the problem wiping cache from Clockwork recovery should clear out the update and it will quit trying to install it. For the future if you go to settings in the about phone or software update section (dont remeber which) there is an option to de-select scheduled update checks.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
Yes you are correct wiping the cache fixed the problem.
mjkusa said:
Thanks guys for all your help and interest. I tried the solution offered by lunatic but it did not work. Thanks any way I was still looping through continuous on and off cycle. I did however did find a solution on another site. Here is the solution from Sele.
http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/2257-rs-guide-how-get-rid-ota-forced-reboots-rooted-phone.html
It was easier fix than I thought it would be. Step #1 worked.
I also did this to stop the update from happening again.
"If you are rooted use root explorer or super manager and set system to R/W. Then navigate to /system/etc/security. Find the file named otacerts.zip and rename it to otacerts.zip.bak and reboot. Should fix you up."
I'm sorry I can't remember who offered this solution to give credit to. I haven't had any updates yet but only time will tell.
Good Luck with your phone.
Click to expand...
Click to collapse
Definitely a handy resource.. Every time a new OTA comes out, this is a very frequently asked question.
I suppose you could always use an RUU too
mike.s said:
Nope. One only has to keep up with the current releases, rooted versions of which come out within days of official release.
Click to expand...
Click to collapse
Based on how many of these threads I see, that clearly isn't what's being done.
I dont want to update to the newest firmware on my sgs2, and i accidently checked for a new update. Now i have to keep postponing it. Is there any way to completely stop the service?
P.s. sorry i have been asking so many questions on this forum. i guess thats just what happens when i get a new phone
Jackson8r said:
I dont want to update to the newest firmware on my sgs2, and i accidently checked for a new update. Now i have to keep postponing it. Is there any way to completely stop the service?
P.s. sorry i have been asking so many questions on this forum. i guess thats just what happens when i get a new phone
Click to expand...
Click to collapse
Root, install custom Rom, uninstall device management via TiBu, done!
Probably not the answer your looking for but its one way around it
Cant u just root and delete device management with tibu without having to actually flash new firmware?
Edit: freezing device management with tibu should work just as well
Galaxy S II
Jackson8r said:
I dont want to update to the newest firmware on my sgs2, and i accidently checked for a new update. Now i have to keep postponing it. Is there any way to completely stop the service?
P.s. sorry i have been asking so many questions on this forum. i guess thats just what happens when i get a new phone
Click to expand...
Click to collapse
You only allowed to postpone 3 times (for 8 hours options).
Just to bypass the annoyance for now, just go into Application/Running Apps, force stop it. Also in Application/All, clear cache and clear data.
thanks for all the help, guys. i just deleted using TiBu
found an answer
Jackson8r said:
I dont want to update to the newest firmware on my sgs2, and i accidently checked for a new update. Now i have to keep postponing it. Is there any way to completely stop the service?
P.s. sorry i have been asking so many questions on this forum. i guess thats just what happens when i get a new phone
Click to expand...
Click to collapse
I finally figured this out on my ss g3 with ICS. did not want the jellybean update. Went to applications>all>software update and deleted data. the notification went away. plus set the update to only when wifi is available. but i guess it will come back once it downloads the update again.
eep2378 said:
Root, install custom Rom, uninstall device management via TiBu, done!
Probably not the answer your looking for but its one way around it
Click to expand...
Click to collapse
I know this is an old thread but my friend was getting this annoying update and asked for my help.I came across this thread and asked her to get titanium back up and uninstall it but there doesn't seem to be "device management" in the list of apps when she goes under uninstall system and user apps on her samsung S3.So if anyone could tell me what exactly is the name of the app so she can uninstall it and get rid of that annoying notification.Thank you.
edit: never mind hers was an at&t branded s3 so it was named "at&t software update v4".
cant really search for this seeing as i wanted to ask the developer directly but i cant due to new user restrictions but anyway...
i downloaded the generic shell helper from bunny... GSH-RC2.rar to be exact
and my question is will this program be able to disable root regardless of the method used?
before you ask, no i did not root the phone myself and the person that did it for me is out of touch. i do beleive he mentioned Zerg- if that helps at all.
thanks for the help guys
snoballz said:
cant really search for this seeing as i wanted to ask the developer directly but i cant due to new user restrictions but anyway...
i downloaded the generic shell helper from bunny... GSH-RC2.rar to be exact
and my question is will this program be able to disable root regardless of the method used?
before you ask, no i did not root the phone myself and the person that did it for me is out of touch. i do beleive he mentioned Zerg- if that helps at all.
thanks for the help guys
Click to expand...
Click to collapse
Though you don't need to unroot to take the update here are some instruction to unroot.
I don't know if that will unroot you, but I do know that an app called Supersu will.
Step 1. Download SuperSu from the market
Step 2. Delete Superuser.apk from /system/app
Step 3. Open up Supersu and update Su binary.
Step 4. Scroll all the way to the right and go to the bottom
Step 5. Select Permanent Unroot.
Your device will be unrooted!
well the reason is that ever since i had the phone unrooted, it wouldnt allow me to update the phone, as it was installing the update it would say update failed. im not sure if theres a difference between unrooting and "returning to stock" as my cousin put it.
anyway ill get on that right now and see where that puts me.
thank you so much
** actually before i do anything, i wanna clarify if unrooting is the same as returning to stock.
ive never done this before so please bear with me lol, i guess whats most important is that i dont lose the photos i have....contact can just be re-synced on google
snoballz said:
well the reason is that ever since i had the phone unrooted, it wouldnt allow me to update the phone, as it was installing the update it would say update failed. im not sure if theres a difference between unrooting and "returning to stock" as my cousin put it.
anyway ill get on that right now and see where that puts me.
thank you so much
** actually before i do anything, i wanna clarify if unrooting is the same as returning to stock.
ive never done this before so please bear with me lol, i guess whats most important is that i dont lose the photos i have....contact can just be re-synced on google
Click to expand...
Click to collapse
No, unrooting and stock are 2 different things. Unrooting, obviously, just ranges away root privileges. you can think of returning to stock as re-installing windows, like you just bought the phone.
Photos should be fine, a they should be stored on your external SD card. If you are worried about losing your pics, just plug your phone into a computer and copy your pics to your computer.
Sent from my DROID RAZR using XDA
Questions go in Q&A
Back story: I recently rooted my Droid Razr (it was my first time rooting an Android phone) and completed it without a hitch. However, the update that was released after I rooted downloaded automatically and I became annoyed with the prompt to install now or later. So I unrooted and installed the update. No problems occurred. Fast forward to this morning. A new update is available (it's been available for about a week now, I'd say) and I go to install it. The phone turns back on and says, "Software update has failed!". I am not currently rooted, I've been too busy to re-root the phone. Now I'd like to install this update. Does anyone have any suggestions on how I'd go about doing this?
Thank you for any replies.
Edit: I apologize in advance if this isn't the appropriate section.
Edit 2: I have another question. Is it possible to update a phone's firmware when they are no longer associated with a carrier. I have an older Android phone I'd like to use as a Wifi only phone for apps and such. Am I able to install updates? It seems like the answer would be no, because the phone wouldn't know where to search for the updates. Perhaps a manual install is available?
Questions belong in Q&A
I just received an extended refurbished warranty replacement for a dead VZW Galaxy S4 SCH-I545 NC5. My old model was rooted, safestrapped, custom rommed, and had ota apps disabled. This new phone is also an NC5 (build date before June, so no problem rooting with TowelRoot). However, when I activated it and rooted it, the upgrade for NG6 was downloaded but not installed. I've rooted the phone and frozen the OTA apps, but I get an annoying popup every few minutes asking if I want to install the new upgrade now or later (clicking later produces a clock to set the time for an automatic upgrade). There is no option for not upgrading. I DON'T want the NG6 build, but the constant popup, which I have to clear with the Back key each time is a roaring PITA.
Anybody know how to disable the popup? The upgrade is already downloaded and I'd like to delete this as well as it is no doubt taking up #*%@^ unnecessary storage, but haven't found the right directory yet.
Any help will be appreciated.
Yout best bet would probably be to do a full wipe, such as an Odin, and restore the phone that way, then immediately root and freeze OTA updates before the phone has the chance to downloaf them.
Beartooth01 said:
I just received an extended refurbished warranty replacement for a dead VZW Galaxy S4 SCH-I545 NC5. My old model was rooted, safestrapped, custom rommed, and had ota apps disabled. This new phone is also an NC5 (build date before June, so no problem rooting with TowelRoot). However, when I activated it and rooted it, the upgrade for NG6 was downloaded but not installed. I've rooted the phone and frozen the OTA apps, but I get an annoying popup every few minutes asking if I want to install the new upgrade now or later (clicking later produces a clock to set the time for an automatic upgrade). There is no option for not upgrading. I DON'T want the NG6 build, but the constant popup, which I have to clear with the Back key each time is a roaring PITA.
Anybody know how to disable the popup? The upgrade is already downloaded and I'd like to delete this as well as it is no doubt taking up #*%@^ unnecessary storage, but haven't found the right directory yet.
Any help will be appreciated.
Click to expand...
Click to collapse
Try this,
http://forum.xda-developers.com/showthread.php?t=1856632
you'll still get the pop up so go ahead and hit update, it wont be able to find the update so it will bomb out, and not bother you again.
Thanks - worked for a while - then popup returned
XRSTOY1 said:
Try this,
http://forum.xda-developers.com/showthread.php?t=1856632
you'll still get the pop up so go ahead and hit update, it wont be able to find the update so it will bomb out, and not bother you again.
Click to expand...
Click to collapse
I did try that. The popup went away for several days and then came back. There must be at least one root-level app I haven't disabled.
Thanks for the help, but I'm afraid I still need a bit more.
Still having popups...
socal87 said:
Yout best bet would probably be to do a full wipe, such as an Odin, and restore the phone that way, then immediately root and freeze OTA updates before the phone has the chance to downloaf them.
Click to expand...
Click to collapse
When I first got the phone, I disabled OTA, I ran the update - which failed, of course. It got rid of the popup, but I did not wipe the phone as I am a longtime Motorola Droid user and am not totally comfortable using Odin (This is my first Samsung and it's like going from Droid expert to Odin newbie). I have since restored nandroid and Titanium backups from the previous phone (this is a warranty refurb). The backups also included disabled OTA apps from my previous S4. Apparently, I missed one somewhere, as the behavior just recently returned. I'm going fishing on the root level again [sigh].
If anybody would be so kind as to list the exact .apks and their directories involved in OTA, I can make sure they are still disabled and run another failed update. This may be different from my Droids, since it is being referred to as a Samsung build update, and not an Android version update.
If anybody knows where the downloaded update is hiding, I can remove that as well.
Thanks in advance.
Im pretty sure the app u need to freeze is listed as SDM.. That should stop the update and popup.
Thanks also.
fxwrangler said:
Im pretty sure the app u need to freeze is listed as SDM.. That should stop the update and popup.
Click to expand...
Click to collapse
I always rename SDM.apk and FWUpgrade.apk, but, with Samsung (with the OTA already pushed, but not installed), I had to jump through several other hoops. To see what else you can do to solve the problem, check out:
http://forum.xda-developers.com/show....php?t=1856632
i just made a post about the same problem. I renamed them. so we will see what happens
To delete the OTA zip use a file explorer with root privileges like "ES File Explorer" navigate to /data/fota and delete update.zip
Beartooth01 said:
I always rename SDM.apk and FWUpgrade.apk, but, with Samsung (with the OTA already pushed, but not installed), I had to jump through several other hoops. To see what else you can do to solve the problem, check out:
http://forum.xda-developers.com/show....php?t=1856632
Click to expand...
Click to collapse
That link is dead. Can you please direct me to a good link for that? Thank you
re-rooting after MJ7 kernal pushed by google?
swolh said:
That link is dead. Can you please direct me to a good link for that? Thank you
Click to expand...
Click to collapse
Well - renaming SDM.apk and FWUpgrade.akp stopped the totally annoying push notification for google's new MJ7 build for the S4. But by renaming SDM.apk, my Verizon app visual voice mail stopped working. When I returned the SDM.apk file to it's original name, the visual voice mail works, but I get the annoying notification from google over and over.
I'm trying YouMail app for visual software and am waiting to hear from them about whether their app uses SDM.apk. If YouMail is like Verizon's visual voice mail and uses SDM.apk, then my next thought is to unroot the phone, let Google do their update to MJ7, then re-root. I'm wondering if anyone has done this.
My phone came with NG6. To root, I had to flash the NG5 stock kernal, then root using towelroot. Once rooted, I flashed the NG6 kernal. If I unroot and let google flash their new MJ7 kernal, will I be able to repeat the root process (flash NG5, the root, then flash MJ7)? If that route were possible, would I need to find a separate place to download the MJ7?
Is there any other way to stop google's annoying notificaton and pushing MJ7 at me? All help greatly appreciated.
---------- Post added at 09:58 PM ---------- Previous post was at 09:16 PM ----------
XRSTOY1 said:
Try this,
http://forum.xda-developers.com/showthread.php?t=1856632
you'll still get the pop up so go ahead and hit update, it wont be able to find the update so it will bomb out, and not bother you again.
Click to expand...
Click to collapse
My apology. I missed this link first time thru this thread. That link to a thread titled "[HOW TO] Disable OTA Update Notifications!!!!!!!!!!!!!" is pretty helpful. We'll see in a day or two if the notification and push attempt continues, but I'm pretty optimistic following the instructions in that thread will stop it.