Related
Hey guys,
Alright, so I was on my stock rooted ROM and saw an OTA come in. I download and apply the update, but it freezes and stops the update. So I unrooted, and tried again. Still failed. So then I remember I didn't disable SafeStrap, and I go and re-root, disable SafeStrap, unroot again, and THEN try the update. Still failed.
I did delete some of the games that came with the phone (while unrooted; I didn't remove system files to my knowledge). What do you guys think the problem could be? I'd really like improved signal connectivity and eventually ICS. And Fastbooting didn't work for me the last time I used it for some reason (although I wasn't on stock ROM at the time - could that have done it?)
Thanks!
Edit: Tried factory reset, did NOT work. Looks like SBF/Fastboot is my only option. What happens if it doesn't work? I'm on stock and unrooted and everything. Maybe I just need to install the missing files? I think I only deleted thinks like NFL 12 and the similar games that were ALLOWED to be deleted. SO blown right now...ugh.
It probably was the bloatware you removed. Before the update came down, I fastbooted back to make sure there weren't any issues with the update. Several people have said that with bloatware removed, the update will fail.
How did you unroot? The only way I've done it is to fastboot it (just to be on the safe side).
I used some app called Ginger Unroot from the market. Surprisingly, it actually worked - SU operations (including SafeStrap apk tasks, SetCPU, etc) ceased function due to a lack of root. I almost feel like VZW could just reset the phone because it is TECHNICALLY not rooted and is still not accepting the OTA. Also, I have a Mac, so it's a hassle to have to borrow a friend's PC every week and try again. But I'll see. There's absolutely NO WAY to fastboot via a Mac, right?
(Also - would a factory reset put the missing apps back and allow, then, for an OTA?)
Thanks!
Things like Safestrap can prevent OTA update.
Safestrap changes the boot structure.
I removed SafeStrap though. Like, it is NO LONGER on my phone, either in bootup OR in apk form. So it shouldn't be affecting the process anymore, right?
Sorry for double post - I found a FastBoot utility for Mac that MIGHT work. Not 100% on it though, but everyone who's used it has indicated it has worked for them.
You say you are unrooted now. Have you rooted before? If so what modifications did you make?
After a very similar experience I finally an updating and it appears that the update hasn't failed. My two previous attempts failed after I unrooted (protected using OTA Rootkeeper), disable Safestrap, and reloaded my preinstall files. If you have ever used Safestrap or done anything to tamper with the preinstall files, webtop, or the bloat apps you will not be able to update.
See, that's my problem...I got rid of apps like the blockbuster app and Madden 12...you're telling me, essentially, that I'm screwed because VZW was stupid enough to make "vital" apps deletable? Also, I deleted those apps while non-rooted. How's that for ironic...
ViaCapita13 said:
You say you are unrooted now. Have you rooted before? If so what modifications did you make?
After a very similar experience I finally an updating and it appears that the update hasn't failed. My two previous attempts failed after I unrooted (protected using OTA Rootkeeper), disable Safestrap, and reloaded my preinstall files. If you have ever used Safestrap or done anything to tamper with the preinstall files, webtop, or the bloat apps you will not be able to update.
Click to expand...
Click to collapse
How did you reload the pre install files? Where did you get the files?
I'm having same issue on xt926.
Thank you very much for the help!
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've run into an issue with my jurassic root and am looking for a little advice before i do something dumb.
confusing preface: i have a razr maxx that i rooted (ICS) right away. after the update to JB, i... can't remember if i saved root or i had to re-root. i have voodoo on my phone and i remember using it, but i don't remember if it was for a particular small OTA or the whole JB. at some point in the distant past i used razr blade. i really need to write this **** down. :/ sorry about this part. ^^^^^
currently running 98.72.16 - i froze the update service before the .165 update because at the time there was a lot of question about the old roots not working, and i just never really came back to it.
either way, i've decided to experiment with safestrap and cm11... but safestrap thinks my phone is not rooted. i recently ran into a similar issue with greenify that i found out was probably related to superuser (chainsdd) -- so i'm betting this may be a similar situation.
so i tried to "hot swap" superSU into place (via play store), but when i run it, i get a prompt to update the su binary. if i cancel, the app closes; if i try to update, i get an installation failed error -- neither route even pops superuser's prompt.
here's what i'm thinking:
a. i can attempt to swap superuser with superSU via adb shell. this seems fraught with peril, but short and easy.
b. i can attempt to just run towelroot over the top of my current root, either straight or after a voodoo temp un-root and/or full un-install of superuser
c. or worst case scenario, do a factory reset and start with towelroot and move forward.
i'm also a little worried that i have used tibu to freeze off and remove much of the bloatware over the intervening years. is this going to cause a problem when i do a factory reset, or is there some evil little cache of the original .apk's that will spring into action and replace them?
oh yeah:
d. does any of this sound unreasonably insane -- because there's a much easier way to achieve this?
thanks!
lol, i think razr utility should come with message along the lines of "hey, i realize you probably don't want to, but why don't you just save yourself some time and frustration and just start from the very beginning. i know you want to keep you internal memory -- you're worried, i get it -- but mang you're just gonna have to do it again."
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.
http://www.droid-life.com/2014/12/05/lg-g3-on-verizon-gets-advanced-calling-1-0-volte-in-update/
The update mainly brings Advanced Calling 1.0 and updates to some LG apps.
It looks like Advanced Calling also needs to be enabled on your account.
http://www.verizonwireless.com/supp...Turning Advanced Calling On/Off on Your Phone
Personally, I'd like to know if someone who is stock/rooted with no system files changed can accept the update and keep root. If anyone gets it and tests that, please report back. Also, include whether or not SuperSU is in survival mode.
With the previous update, I was stock/rooted with 1 system file that dealt with headphone volume changed. I had to restore the original version of that file, then the update completed and root was kept (without SuperSU survival mode being required).
I've done the check for updates on my phone, but nothing yet.
I've actually just accepted the update and I still have root. However it may appear to run slowly at the beginning, but eventually everything came back. So if you're worried a root app won't work, then wait around 3 to 5 minutes and everything should be working again and back to normal as well. I was rooted from 10C and now I'm on the latest update.
david_hume said:
I've actually just accepted the update and I still have root. However it may appear to run slowly at the beginning, but eventually everything came back. So if you're worried a root app won't work, then wait around 3 to 5 minutes and everything should be working again and back to normal as well. I was rooted from 10C and now I'm on the latest update.
Click to expand...
Click to collapse
I see the update available to be pulled now.
SuperSU in survival mode or not? I'm on 11C, but I wouldn't think going from 10C/rooted to 12B or 11C/rooted to 12B would make a difference. I guess I'll give it a go here as soon as I can restore that system file.
lexluthor said:
I see the update available to be pulled now.
SuperSU in survival mode or not? I'm on 11C, but I wouldn't think going from 10C/rooted to 12B or 11C/rooted to 12B would make a difference. I guess I'll give it a go here as soon as I can restore that system file.
Click to expand...
Click to collapse
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
david_hume said:
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
Click to expand...
Click to collapse
I don't think survival mode is required. It wasn't went I went from 10C to 11C.
I'm holding off on this one. I bounce between 4g and 3g a lot and I heard that if you start a call on 4g and it drops to 3g, you will drop the call. Not sure if this is true, hope someone can chime in
hawkswind1 said:
I'm holding off on this one. I bounce between 4g and 3g a lot and I heard that if you start a call on 4g and it drops to 3g, you will drop the call. Not sure if this is true, hope someone can chime in
Click to expand...
Click to collapse
From what I read somewhere, I think you can turn it off if you don't like it. My update completed, it's optimizing apps now. Will post once I confirm I've kept root (or not).
I just updated mine. I upgraded from 11C and still have root. I put my SU in survival mode just in case, but I'm not sure if that was necessary or not.
Also, for those that are worried about being stuck on VoLTE. There's a new entry in the Settings menu that lets you turn the "Advanced Calling" on/off at will.
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
If someone could pm me with a link to a system partition dump (or kdz) it would be appreciated, thanks.
EDIT: nvm, got it.
j0hnnyn said:
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
Click to expand...
Click to collapse
I'm back up. I had to restore the sound system file, do the update, then put my custom file back. My frozen apps stayed frozen. I had to re-install xposed framework (didn't have to uninstall it first) and I still have root (I did not have SuperSU in survival mode). All in all pretty easy. Yes, I know the update could have included a shut out of root, but it didn't (for me).
You'll probably have to restore those system apps if you did any type of "hack" uninstall (as opposed through some sort of regular OS menu).
Other than that, you should be good. Just re-install xposed framework through the xposed installer that's still there after the update.
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
xdabbeb said:
If someone could pm me with a link to a system partition dump (or kdz) it would be appreciated, thanks.
Click to expand...
Click to collapse
I 2nd this!
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
taihard said:
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Same thing here. I hope there is something else other than using LG Flashtool to download the stock firmware
taihard said:
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Here's another thing i'm noticing... before, I downloaded a couple UI themes to change the nav buttons at the bottom through g3 tweaksbox and after removing g3 tweaksbox, the buttons changed to stock on the home screen but if I go in to settings or any other app it still shows the "LG" logo as my "home" button... maybe some left behind changes that are preventing update?
lexluthor said:
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
Click to expand...
Click to collapse
I did this earlier, it shouldn't be difficult for you, assuming your admin isn't a jerk of course. It's a feature that needs to be checked on your account, but it's also a free feature, so I'm not sure what excuse they'd have for denying your request.
taihard said:
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Can't help you with your error code, but I can say that my rooted phone also reported as "modified" status before applying the OTA and it still does afterwards as well.
Please help
Phone is rooted and has oem rom ... and xposed framework for tweakbox philz recovery mode just keeps loading after i treid the update what can i do i cant get back into my phone at all please help
Also tried resotring a backup i made yesterday before any of this and its still doing the same thing please please please helpl
j0hnnyn said:
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
Click to expand...
Click to collapse
No. Xposed will block all OTA and removing system Apps will also.
david_hume said:
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
Click to expand...
Click to collapse
lexluthor said:
I'm back up. I had to restore the sound system file, do the update, then put my custom file back. My frozen apps stayed frozen. I had to re-install xposed framework (didn't have to uninstall it first) and I still have root (I did not have SuperSU in survival mode). All in all pretty easy. Yes, I know the update could have included a shut out of root, but it didn't (for me).
You'll probably have to restore those system apps if you did any type of "hack" uninstall (as opposed through some sort of regular OS menu).
Other than that, you should be good. Just re-install xposed framework through the xposed installer that's still there after the update.
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
Click to expand...
Click to collapse
can one of you guys (or anyone else who took the update) use this code to pull the modem for us please?
(use terminal emulator)
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/modem-12B.img
Thanks!!
tech_head said:
No. Xposed will block all OTA and removing system Apps will also.
Click to expand...
Click to collapse
I had Xposed installed and it updated no problem. But I would think the system apps would make it fail though.