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.
Apologies up front... I'm sure this has been discussed ad nauseum, but my searches can't turn up the answer I'm looking for.
I'm not ready to grab the new update, kernel, or radios. I'm running perfectly the way I want with Nils GingerSense 1.5 (GB).
The first OTA nag, I was able to reject. This morning, the OTA downloaded (found the OTAPkg.zip in /cache/fumo), but I was only able to defer several days, no reject option.
Question: Is there anything I can do to prevent future Verizon OTA attempts and forget about this until I'M ready to move forward?
I used to have fotakill.apk in my cm7 rom for the incredible . Maybe you can download any cm7 rom and extract that file. Might work?
I believe you can just delete otacerts.zip from /system/security and it shouldn't prompt you. I think that's what some people did on the Inc to block it before. Some also modified their build.prop, but I'm not sure what the line was, or what to change it to now.
I'm not to be held liable if anything goes wrong after modifying any of these things. Make a backup first!
Sent from my ADR6425LVW using XDA Premium.
SteveG12543 said:
I believe you can just delete otacerts.zip from /system/security and it shouldn't prompt you. I think that's what some people did on the Inc to block it before. Some also modified their build.prop, but I'm not sure what the line was, or what to change it to now.
I'm not to be held liable if anything goes wrong after modifying any of these things. Make a backup first!
Sent from my ADR6425LVW using XDA Premium.
Click to expand...
Click to collapse
I see a otacerts.zip in /etc/security , so I'll try renaming that, thanks.
Well, about an hour after I renamed /etc/security/otacerts.zip to otacerts.zip.bak, another OTA download has begone, so that's not going to do the trick. I've restored the file, and the download is continuing. I'm deferring again, not sure what to try next.
Resigned
DIncLover said:
Well, about an hour after I renamed /etc/security/otacerts.zip to otacerts.zip.bak, another OTA download has begone, so that's not going to do the trick. I've restored the file, and the download is continuing. I'm deferring again, not sure what to try next.
Click to expand...
Click to collapse
You will have to stare at this thing to be ready ... it snuck the OTA at me when I wasn't looking, and I only realized it when the phone vibrated as it leaped into recovery and started flashing the OTA. Never asked my permission, and I never gave it.
I simply deleted every apk in the /system/app folder that said either Verizon or VZW.... I have not gotten any prompts about the OTA and it definitely has not installed or attempted to.
htcdm showed up as "hogging data" in one of my data trackign apps when i got my update message, hope that helps.
Would be nice to reject this OTA.
It don't even ask before trying to apply it!
I'm suprised that people on custom roms are getting the update attempt. Usually on a custom ROM, that kills the OTA updates. This is usually only a problem on those that are on a stock rooted type rom.
Very weird
I'm at a loss. I don't know whether to accept the update or not. I think with the Mainver fix, I can always go back...right?
My thinking is the update might patch a leak that might help us get S-Off. If I'm way off base, please let me know, because ignorance is bliss.
jdmba said:
You will have to stare at this thing to be ready ... it snuck the OTA at me when I wasn't looking, and I only realized it when the phone vibrated as it leaped into recovery and started flashing the OTA. Never asked my permission, and I never gave it.
Click to expand...
Click to collapse
I'm just stock ICS rooted, only did it for removing bloat and using tethering. Now my phone tries to do this update automatically too and it just reboots into twrp and sits there... One of these days it will do it overnight and i'll miss my alarm!! Pisses me off. ha
brettokok said:
I'm just stock ICS rooted, only did it for removing bloat and using tethering. Now my phone tries to do this update automatically too and it just reboots into twrp and sits there... One of these days it will do it overnight and i'll miss my alarm!! Pisses me off. ha
Click to expand...
Click to collapse
I registered just to reply to this. I took did a stock ICS root to get rid of bloat. Last night, it attempted to do an install at 2 AM est, got to recovery and hung. I rebooted it and went to sleep. 7:30 AM, my back-up alarm goes off, I look over at my phone, and it's stuck in recovery again, they tried to push another update while I was sleeping, and I missed my early alarm.
This is unacceptable. I need to find out how to permanently reject this blasted thing.
solo_xda said:
I registered just to reply to this. I took did a stock ICS root to get rid of bloat. Last night, it attempted to do an install at 2 AM est, got to recovery and hung. I rebooted it and went to sleep. 7:30 AM, my back-up alarm goes off, I look over at my phone, and it's stuck in recovery again, they tried to push another update while I was sleeping, and I missed my early alarm.
This is unacceptable. I need to find out how to permanently reject this blasted thing.
Click to expand...
Click to collapse
Yeah, happens to me once or twice a day, and if you don't notice it as it happens, it ends up just rebooted sitting in twrp. So I don't get calls or texts or alarms.
Anyone out there have any idea how to block the OTA's? Or can anyone answer if the following is possible.... I have never used titanium backup for actually doing any backups. I have just used it for removing stupid verizon apps. Could I do a backup of setting/apps and then flash the newest stock ICS ruu or whatever, re-use the root tool, and then restore my stuff from my backup?
Googled it and it was the first result...
http://www.chargeforums.com/forum/d...s-ota-update-very-easy-but-requires-root.html
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Googled it and it was the first result...
http://www.chargeforums.com/forum/d...s-ota-update-very-easy-but-requires-root.html
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
About 8 posts back someone said that didn't work for their rezound. I tried it regardless. Had tried renaming that file with astro file explorer and i didn't have permission so I bought root explorer and it let me do it. We'll see if it keeps doing it to me like it did to the above poster...
brettokok said:
About 8 posts back someone said that didn't work for their rezound. I tried it regardless. Had tried renaming that file with astro file explorer and i didn't have permission so I bought root explorer and it let me do it. We'll see if it keeps doing it to me like it did to the above poster...
Click to expand...
Click to collapse
I used titanium backup pro and froze the updater.apk so far so good. all day and no popups. I am Stock and Root.
ckupsco said:
I used titanium backup pro and froze the updater.apk so far so good. all day and no popups. I am Stock and Root.
Click to expand...
Click to collapse
I'm stock and rooted.
Last night, I froze the updater app in Titanium Backup. I rebooted for good measure. This morning I woke up to my phone booted in recovery.
I rejected the update and booted back up. So this is still an issue...
Just chiming in that I'm also affected, but havne'tthat on Sunday this push broke my GB image, so bad that I had to RUU it to ICS. Now I've been finding my phone at TWRP every morning with an OTA.zip failing to flash.
Additionally, I got a message that offered me to defer my update and I chose 3/10 at 7pm. But it still tried overnight.
Use tibu to freeze the ota updater package.
Or flash a custom recovery like amon ra for rezound. Or even a custom rom, say simplistic if you want to stay on an ics/sense based rom
To get the ota, one must have: a relatively unmodified stock rom (key system apps can't be frozen or missing) and the stock recovery tool. If you change either of those, you won't get prompted to do the OTA.
Sent from my Infected Rezound using Tapatalk 2
---------- Post added at 01:55 AM ---------- Previous post was at 01:49 AM ----------
AndroidGraphix said:
I'm at a loss. I don't know whether to accept the update or not. I think with the Mainver fix, I can always go back...right?
My thinking is the update might patch a leak that might help us get S-Off. If I'm way off base, please let me know, because ignorance is bliss.
Click to expand...
Click to collapse
If you're s-on, you can't rewind the firmware on your phone. The mainver fix is just to get certain roms installed.
While it's possible they could patch the current s-off method, I doubt they care much at this point. Verizon has depleted their stock of replacement rezounds and HTC has moved onto new devices.
Sent from my Infected Rezound using Tapatalk 2
Greetings,
I know the easy answer to this is going to be to flash a new rom, but if I wanted to do that I would have already. I'd rather find and repair the source of the issue and learn from it.
That being said, shortly after getting my tbolt (when they were first released) I used the revolutionary root and added in VPN software for work. Being unaware that OTA updates hadn't been blocked during the rooting, the phone took an update and went into a death-boot-loop. I found a clean updated OTA rom, flashed and unrooted the phone as the VPN software didn't work well for what I intended anyway.
Great, now the phone is all back to stock (or so I thought).. After a while, another OTA update came down, it asked to update, I allowed, and it said update failed.. Repeat ad nauseum for the next several weeks. Since I was happy with the way the phone was operating, I didn't care if it got the updates or not.
So last week, I decided that since the phone is out of warranty anyway, I might as well root and get rid of some of the bloat, and while I'm at it, get rid of the damn nag screen every tine I hook it to a computer. Searched around, found thunderbolt tool 1.0.1, downed it and tried it out, and it proceeded to say unable to lock my phone.
After a little screwing around, the "update status" on the phone itself reports ROM Version: 2.11.605.9, while the tool was getting a response of 2.11.605.5, so it was using the wrong method to get into the phone. So I edited the batch file to use the .9 method no matter what it reported back, and it proceeded to root, add the recovery, and superuser.
Ahhh, life is good, the phone is rooted again, time to start doing my own customization.
Except that after a couple reboots, everything loses the root rights.
Running titanium backup says "asking for root rights" and then "titanium has been granted superuser permissions" but it just hangs there at the "asking for root rights" screen.
Wireless tether similar story... Start the app and it says "press to start tethering" and touching the screen gets "wireless tethering has been granted superuser permissions", then hangs at "please wait while starting".
Won't do anything that requires root, unless I run the tool again and select "S-off but no root", and it will go through a procedure and root will work again for a while.
Also, as I'm typing this, I discovered that it doesn't necessarily require rebooting to lose root. I had root working last night, but when I picked up the phone to get the proper messages to type, it is not showing root again, and it hasn't been rebooted since root was working.
Thoughts on how to repair this without flashing a rom?
Have you attempted to run the "fix permissions" option in your recovery?
If that does not help, You could use something like OTA RootKeeper to protect root, if you loose it you would just click one button to get it back.
Last thing I can think of is to just reflash the same ROM you are using now on top of what you have so you loose no data and any messed up settings or files will be rewrote.
**edit**
You should really think about installing a custom ROM, because until you do, or you block OTA updates, this will be a reoccurring issue.
You could easily install a stock rooted ROM of the exact same thing you have now. nothing would change except it would be properly rooted and OTA updates would be blocked.
That is because only temp root is applied to the official 605.19 Ruu. You need to downgrade back to 605.5 after getting temp root on the 605.19 Ruu then apply the perm root zip in recovery and then flash a newer rom from recovery. If that doesn't work don't lose hope. I may be misunderstanding the situation you have but it sounds like you're only applying temp root. The tool doesn't need to be edited and you may need to flash the 605.19 stock Ruu, relock and s on and then run the tool again.
Sent from my ADR6400L using Tapatalk 2
Milimbar said:
Have you attempted to run the "fix permissions" option in your recovery?
If that does not help, You could use something like -edit- to protect root, if you loose it you would just click one button to get it back.
Last thing I can think of is to just reflash the same ROM you are using now on top of what you have so you loose no data and any messed up settings or files will be rewrote.
**edit**
You should really think about installing a custom ROM, because until you do, or you block OTA updates, this will be a reoccurring issue.
You could easily install a stock rooted ROM of the exact same thing you have now. nothing would change except it would be properly rooted and OTA updates would be blocked.
Click to expand...
Click to collapse
Haven't seen the fix permissions option anywhere I've been, care to point me in the right direction?
I'll check out the rootkeeper.
disconnecktie said:
That is because only temp root is applied to the official 605.19 Ruu. You need to downgrade back to 605.5 after getting temp root on the 605.19 Ruu then apply the perm root zip in recovery and then flash a newer rom from recovery. If that doesn't work don't lose hope. I may be misunderstanding the situation you have but it sounds like you're only applying temp root. The tool doesn't need to be edited and you may need to flash the 605.19 stock Ruu, relock and s on and then run the tool again.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Never took the .19 update, and both the tool and phone report as .05 now. (if I remember correctly the .09 reverts back to .05 to get in)
damm315er said:
Haven't seen the fix permissions option anywhere I've been, care to point me in the right direction?
Click to expand...
Click to collapse
What recovery are you using?
I only use 4ext and would recommend that.
The fix permissions will take up to 5 min and may not help your particular issue, but shouldn't hurt to try.
If 4ext - Boot into recovery, select tools then select fix permissions.
If CWM I think its in the advanced menu.
and If TWRP I think it is in the advanced menu again.
Good luck and listen to the others here, they go out of their way to help people a lot
Ok earlier I misread your post. I thought it said 605.19. Still though something you're doing is causing you to only get temp root. Reread the op of the allinone tool and make sure you meet the requirements before you start it. That away when you run it this time you are in the best possible situation for it to work. Trter is very helpful and if you post your issue in his thread he will probably assist you with anything you need.
Sent from my ADR6400L using Tapatalk 2
I remember having a similar problem about 6-7 months ago.
I would randomly loose root, though not as often as he is describing.
In my case it was a combination of an outdated root method and a flawed ROM.
If everything he is using is current, including the ROM, he shouldn't have an issue.
If it were me I would flash Santod's stock deodexed ROM and be done with it.
It is the stock ROM with nothing changed except it is prerooted.
I understand that you would like to "fix" this issue without flashing a ROM, however the ROM itself could be the problem. this solution is the simplest I can think of.
Using everything from the thunderbolt toolkit, so yes, 4ext.
Found and ran the fix permissions, ran for 15 minutes before it finished so we'll see how it goes.
I get what you're saying about the rom being screwed up, and am starting to think my only choice is to reflash it, so I'll start looking into a new rom.. That being said I'm still pursuing fixing this until I find a rom that serves my purpose.
Is there a good stable ICS for thunderbolt, pre-loaded with root and good battery life?
Yea the one in the post above yours. If you want something a that is faster and has better battery than it then head over to infectedrom.com and check out all the different options santod has made.
Sent from my ADR6400L using Tapatalk 2
I didnt realize at that time, that the update he was doing would block root. If I factory reset, will it put me back to pre-update so that when i boot up the phone I can root it first thing? Thanks for any help.
hondaboi20002 said:
I didnt realize at that time, that the update he was doing would block root. If I factory reset, will it put me back to pre-update so that when i boot up the phone I can root it first thing? Thanks for any help.
Click to expand...
Click to collapse
From what I have read the answer is NO. I think you are SOL until a new root method is found.
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
hondaboi20002 said:
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
Click to expand...
Click to collapse
I believe that is your only option, yes. To my knowledge, there is no way to revert back and you're stuck. Unless you'd like to just keep your current phone and wait until someone roots the new update, but your only other option would be to exchange it.
In your opinion, do you think the devs will find a way to crack this update and obtain root?
hondaboi20002 said:
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
Click to expand...
Click to collapse
Correct. That is *IF* the new phone doesn't already have the update installed, or the sales rep doesn't install the update while activating it and getting it ready for you.
Rumor has it that they already have root, but aren't releasing how until they can find a way to also unlock/patch the boot loader. They are said to be afraid of having Samsung/Verizon block this root method before they can use it to unlock the boot loader. Will they ever get it? Will they ever release the root method? That is anyone's guess.
So for now, it looks like the 16gig DEV edition direct from Samsung, without warranty, is the only option if you definitely want to root and flash custom roms now and "forever". But is it still available? or did they sell out yet?
Spoke with my rep and he told me bring it back, exchange it and all he will do is activate it and hand it right over to me and will not install the update. Now once I do get the new phone without the update and obtain root, can or will that verizon update still try and come thru and ask me to install it?
You can block the OTA updater with titanium backup. I'm not on a stock ROM, so I don't remember the updater app name.
Sent from my SCH-I545 using Tapatalk 4 Beta
SDM
That sucks. You gotta keep your eye on those reps :cyclops:
i never let any sales person set up, activate or even power up any phone i buy. if they chose to do so i cancel the order and buy on line where it comes sealed. i always tell them i'm in a rush and i'll take care of activating it afterwards. only one has ever refused and i told him to cancel the sale since he decided to open a product i purchase without my consent. he did get me a new one after that.
hondaboi20002 said:
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
Click to expand...
Click to collapse
That is assuming the new phone you get isn't updated b4 u turn it on...
Sent from my SCH-I545 using xda app-developers app
Ok, got a new S4 and this worked !!
Ok, everyone I got a new S4 and activated at Verizon which it immediately started download pretty much as soon as it was turned on. I immediately disabled mobile data, turned it off and then took out the sim card. Once I got home, I hooked this baby up to my PC and rooted...success, finally! I used the I545 all-in-one-root tool which includes OUDS clockwork. http://www.droid-life.com/2013/05/30/all-in-one-root-tool-released-for-verizon-galaxy-s4/
My questions is I have installed ROM Manager so that I could do a backup, but when I first open ROM manager, it says I need to install a custom recovery even though I have OUDS clockwork built in. Do I need to install clockwork from within the ROM manager app? I can reboot into recovery, but its the OUDS "generic" recovery, for lack of a better word. Is that recovery good to go for backing up, flashing another ROM or do I need to use the ROM manager to install CWM from with the app itself? Hope this makes sense. Thanks everyone!!
I'm a VZW rep and every time I activate a new S4, the update automatically starts downloading and there's NO way to tell it to "differ" to a different time.
Trust me, its not OUR fault. It just happens sadly :-\
I too hope devs get a way to root past this OTA because I have friends that would like me to root for them, but the OTA just muscles its way through.
I haven't upgraded anyone to an S4 today, but will report back with more info when I do. I'm pretty sure that after we activate the phone, the download starts and the notification just sits there until you click it (then it updates) or if you restart the device, it may force the update. I'll test on my next customer and let y'all know the real answer
Sent from my SCH-I545 using xda premium
dopediculous said:
I'm a VZW rep and every time I activate a new S4, the update automatically starts downloading and there's NO way to tell it to "differ" to a different time.
Trust me, its not OUR fault. It just happens sadly :-\
I too hope devs get a way to root past this OTA because I have friends that would like me to root for them, but the OTA just muscles its way through.
I haven't upgraded anyone to an S4 today, but will report back with more info when I do. I'm pretty sure that after we activate the phone, the download starts and the notification just sits there until you click it (then it updates) or if you restart the device, it may force the update. I'll test on my next customer and let y'all know the real answer
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
My experience with the update is that it will tell you the download is ready and at that point you can postpone it to a later time. It even gives you a little wheel to select when to install the update. The phone is still completely rootable during that time. When the notification comes back you can again postpone until a later time.
brw9100 said:
My experience with the update is that it will tell you the download is ready and at that point you can postpone it to a later time. It even gives you a little wheel to select when to install the update. The phone is still completely rootable during that time. When the notification comes back you can again postpone until a later time.
Click to expand...
Click to collapse
That's what happened to me. During the initial setup it was downloading the OTA update. As soon as I could, I enabled "Airplane mode" to kill the update, but no, it had already downloaded and asked if it was OK to install.
I deferred it until 1:00 AM and immediately started the rooting process. Got root, installed SuperSU Pro and enabled Survival mode. I also installed Voodoo OTA RootKeeper, but that wasn't necessary.
So I'm now running stock with superuser available and protected. Unfortunately, no custom recovery.
Since I have been doing smartphones, I have NEVER updated, I wait until someone has tried it. and even then, I wait for a dev to cook it up. And everyone better hope you do not have to do any replacements thru the carrier, you WILL get a bootloader locked device with the newest release, NO bootloader fix.
Need to find alternatives.
k1mu said:
That's what happened to me. During the initial setup it was downloading the OTA update. As soon as I could, I enabled "Airplane mode" to kill the update, but no, it had already downloaded and asked if it was OK to install.
I deferred it until 1:00 AM and immediately started the rooting process. Got root, installed SuperSU Pro and enabled Survival mode. I also installed Voodoo OTA RootKeeper, but that wasn't necessary.
So I'm now running stock with superuser available and protected. Unfortunately, no custom recovery.
Click to expand...
Click to collapse
That's great news to hear! Unfortunately my location was dead yesterday and I didn't sell any S4's. Just stupid idonts to bubblegum chewing pop tarts and grandparents. Ugh *face palm
Sent from my SCH-I545 using xda premium
brw9100 said:
My experience with the update is that it will tell you the download is ready and at that point you can postpone it to a later time. It even gives you a little wheel to select when to install the update. The phone is still completely rootable during that time. When the notification comes back you can again postpone until a later time.
Click to expand...
Click to collapse
Yeah, I ordered my S4 online, and it let me defer the update. It downloaded, then said ready to install would you like to install now or later? I set the timer to 12 hours, rooted, installed recovery, flashed AOKP, and bam, no worrying about OTA updates.
Sent from my SCH-I545 using Tapatalk 4 Beta
hondaboi20002 said:
Spoke with my rep and he told me bring it back, exchange it and all he will do is activate it and hand it right over to me and will not install the update. Now once I do get the new phone without the update and obtain root, can or will that verizon update still try and come thru and ask me to install it?
Click to expand...
Click to collapse
What I suggest is what I did.
Do not place the sim into the phone.
My phone came from Wirefly.com without the sim card installed.
Power up without sim card, boot directly to download mode, connect to pc usb port, run Odin, follow rooting procedure.
Only after you freeze SDM using titanium backup, should you consider inserting the sim card.
Also while on wifi samsung will ask to install update, say no.
P. S. I installed samsung drivers, and Odin. I did not install kies which I have read also tries to install the update.
I just downloaded a OTA update on my S4, which I hoped was 4.4.4, but it looks like it is still Android 4.4.2. During the update, it says it was also updating KNOX, does anyone know what this update is, I was hoping it was the 4.4.4 upgrade. It did update KNOX to 2.0, so hopefully I can move my work stuff into KNOX now, and not have my basic phone subject to my work's locking policy.
The build number is KOT49H.I545VRUFNG6.
reckert said:
I just downloaded a OTA update on my S4, which I hoped was 4.4.4, but it looks like it is still Android 4.4.2. During the update, it says it was also updating KNOX, does anyone know what this update is, I was hoping it was the 4.4.4 upgrade. It did update KNOX to 2.0, so hopefully I can move my work stuff into KNOX now, and not have my basic phone subject to my work's locking policy.
The build number is KOT49H.I545VRUFNG6.
Click to expand...
Click to collapse
It's just small bug fixes for bluetooth connectivity and updates for KNOX 2.0.
Oh noze! Search is borken again.
How do you stop the ota updates
siouxhockey11 said:
How do you stop the ota updates
Click to expand...
Click to collapse
Download Titanium Backup and try to freeze SDM, you might have to purchase Titanium Backup Pro to freeze apps.
When it asks just click , No Thanks.. Update won't show again till you manually look for an update in settings.
I see the method for rooting the G6 involves the roll back to G5 and flashing G6. I've already towel rooted G5, will accepting the G6 OTA remove root for me because of the knox update? IOW if I want the LAG, is it better to flash G6 via odin, or can I just accept the OTA?
Thanks for your time!
BrianLayman said:
I see the method for rooting the G6 involves the roll back to G5 and flashing G6. I've already towel rooted G5, will accepting the G6 OTA remove root for me because of the knox update? IOW if I want the LAG, is it better to flash G6 via odin, or can I just accept the OTA?
Thanks for your time!
Click to expand...
Click to collapse
You will lose root if you flash NG6 on Odin or Accept the OTA update. The only way to keep root is to follow that flash back method if you want the update and keep root. My advice is not to updated at all. The NG6 update has issues with random reboots.
Fadtydawg said:
You will lose root if you flash NG6 on Odin or Accept the OTA update. The only way to keep root is to follow that flash back method if you want the update and keep root. My advice is not to updated at all. The NG6 update has issues with random reboots.
Click to expand...
Click to collapse
I would also advise not taking the NG6 update. I did and I went back to NC5. The random reboots seem to be unfixable and there really wasn't anything new and exciting with NG6, unless you need Knox 2.0 for some crazy reason! STAY WITH NC5!!!
michaely123 said:
Download Titanium Backup and try to freeze SDM, you might have to purchase Titanium Backup Pro to freeze apps.
Click to expand...
Click to collapse
I disabled SDM with 'No Bloat". Annoying notification for update is gone.
wulto said:
I disabled SDM with 'No Bloat". Annoying notification for update is gone.
Click to expand...
Click to collapse
Will this work for non-rooted phones?
dwmartin6341 said:
Will this work for non-rooted phones?
Click to expand...
Click to collapse
No u need a rooted phone.
Fadtydawg said:
When it asks just click , No Thanks.. Update won't show again till you manually look for an update in settings.
Click to expand...
Click to collapse
Say what? Mine is prompting me to install the update. It only gives me 2 choices "Install now" and "Install later", and if I choose later, it prompts me to pick a time for it to install. There is also a checkbox that says "Install automatically", which I am leaving unchecked. So, I think it's going to prompt me every day from now on, unless I root and then freeze something.
stuartv said:
Say what? Mine is prompting me to install the update. It only gives me 2 choices "Install now" and "Install later", and if I choose later, it prompts me to pick a time for it to install. There is also a checkbox that says "Install automatically", which I am leaving unchecked. So, I think it's going to prompt me every day from now on, unless I root and then freeze something.
Click to expand...
Click to collapse
It will just keep bugging you with the prompt everyday unless you root and freeze the apps.
With my wife's phone I went in to settings, application manager scrolled over to all & found SDM app & forced stopped it. Notification is now gone.
She IS NOT rooted.
I also have it auto hibernate using greenify so it does not come back.
Sent from my SCH-I545 using Tapatalk 2
So is this update buggy for those who were unrooted? Or just for those who were rooted and took the update?
I wonder if we were to unroot, take the update, then follow the root instructions if many of the problems go away?
Sent from my SCH-I545 using XDA Free mobile app
My wife's S4 is totally stock and she's had zero problems with the update. Took it earlier today.
After playing around with the update for a while, it looks like we have finally lost write access to the SD card like we were supposed to since the first Kit Kat update. I cannot write to the SD card (unrooted) with any file explorer, and my SMS backup app fails at writing to the SD card.
Zelmo88 said:
I would also advise not taking the NG6 update. I did and I went back to NC5. The random reboots seem to be unfixable and there really wasn't anything new and exciting with NG6, unless you need Knox 2.0 for some crazy reason! STAY WITH NC5!!!
Click to expand...
Click to collapse
I read your post..updated for the heck of it..FDR'd it...random rebooted after a a few minutes.
Its been 2 days so far, and the thing reboots 3-4 times a day.
I noticed that sometimes before it reboots, I'll unlock it, and it wont even register my security swipe..Then it reboots..Sometimes, if it does let me in, tapping on an icon does nothing...then it reboots...Other times, like this morning, it was just sitting on the end table, and it rebooted. Boy, you weren't kidding about the reboots.
BTW..All stock.
Here's what I did, worked.
I used the towel root method posted here (and other places I'm sure):
Ok...Forum won't let me post a link because I'm new. So Google "Root Verizon Galaxy S4 SCH-I545 on I545VRUFNG6 Firmware" and it will be the top choice from droid views.
Read the comments section too I posted the issue I was having then reinstalled super SU, flashed the NG6 Kernal and I've been good to go.
Hope it works out for you, I'm on NG6 with root, no errors, no reboots.