Brand new V20 H918 unlocked and rooted. I've been noticing problems receiving text message. They sometimes take a half hour to receive. I also have noticed issues with apps getting root permissions. It takes a while. Rebooting doesn't help or speed things up. Could it be something wrong with SuperSU? It updated from the Play Store the latest version. Root Checker says I have root.
Edit: I rolled back SuperSU to the flashable 2.79 SR3 and apps get root right away. Text messages still have the problem. Sent is immediate. Received takes 30 mins.
Related
Ive got a weird issue that I cant seem to get around and I wanted to see if anyone else has had this problem.
I got a replacement phone from Verizon last week. It came preinstalled with JB and since we have Towelroot now, I let it take the OTA update.
I rooted with Towelroot and when I went to install SuperSU, it tells me Knox is active and asks me to disable and I say yes. At that point, the phone just sits there and grinds on disabling Knox. Ive let it sit an hour and it still just sits there grinding on Knox. Its never finished disabling Knox the first time and Ive flashed the phone back to factory and re-rooted 4 times now, Everytime its the same.
If I reboot after that and re-run SuperSU, it gives me the Knox warning again and when I say Okay, it immediately says Knox is disabled.
Check root and it shows Im rooted and behaves as such.
Then the problems start. I start getting stuff FCing all over the place. Ive tried to do a Fix Permissions from within BusyBox and that didnt seem to help at all. I unrooted and the problems went away. I rooted again and they came back and then I got stuck on the SuperSU Binary Needs To Be Updated loop where every time I update, it fails and closes SuperSU.
Has anyone had this issue and if so, did you figure out a way around it?
I had Same errors installing Chainfire's SuperSu Pro
But all is working good now.
it Gives root to what ever I grant access to, so no complaints here.
I Have seen other posts with same issue so I am sure CF is aware and working on the issue.
Also, I have not had any FC's since rooting and installing SuperSu
Thanks for the reply.. I think the FCs are due to Knox not being disabled properly but Im not sure.
Did Knox disable okay for you?
I didnt see a thread already but my G3 started downloading an update this morning without me accepting or saying anything at all. Obviously with Root and TWRP(Bump) I did not want this. I pulled down the notification bar long pressed on the update download, hit app info, then force stopped the app. I went into Titanium backup, made a backup of System Updates 1_13_10_0 then uninstalled it. I don't know if the download will come back but I don't think so. Also the update was 220ish MB and I have no issues with the phone after uninstalling this. Sorry I didnt get a chance to take a picture of the update since it was almost done lol.
System Updates Frozen
I have the System Updates App frozen in Ti BU. Haven't gotten any hint of an update and I hope it stays that way.
Same thing happened to me it tried installing the update all on its own luckily it said waiting for wifi network to update so I froze the system updates app with titanium back up.
RyanEJ25, I experienced the same thing as you. I have a Verizon LG G3 (vs985), rooted.
Trying to get more info on this system update and what it contains. I don't think it's Android 5.0 lollipop update, but more like a Verizon bug update/improvements.
I tried to run the system update that was downloaded via WIFI, but it failed due to my LG g3 being rooted.
Before I go down the path of backing everything, unrooting and upgrading and then re-rooting, just wanted to make sure the update is worthwhile.
-Kevin
RyanEJ25 said:
I didnt see a thread already but my G3 started downloading an update this morning without me accepting or saying anything at all. Obviously with Root and TWRP(Bump) I did not want this. I pulled down the notification bar long pressed on the update download, hit app info, then force stopped the app. I went into Titanium backup, made a backup of System Updates 1_13_10_0 then uninstalled it. I don't know if the download will come back but I don't think so. Also the update was 220ish MB and I have no issues with the phone after uninstalling this. Sorry I didnt get a chance to take a picture of the update since it was almost done lol.
Click to expand...
Click to collapse
trailrunner76 said:
RyanEJ25, I experienced the same thing as you. I have a Verizon LG G3 (vs985), rooted.
Trying to get more info on this system update and what it contains. I don't think it's Android 5.0 lollipop update, but more like a Verizon bug update/improvements.
I tried to run the system update that was downloaded via WIFI, but it failed due to my LG g3 being rooted.
Before I go down the path of backing everything, unrooting and upgrading and then re-rooting, just wanted to make sure the update is worthwhile.
-Kevin
Click to expand...
Click to collapse
The main thing that threw me off was that USB charge modes have changed. Charge and internet connection are removed from PC connections other than that its general improvements to the keyboard and docs and stuff.
You can temp unroot, take the update, then reroot assuming Verizon didn't load a bullet that kills root.
Voodoo OTA Root Keeper
Sent from my VS985 4G using XDA Free mobile app
I'd tend to avoid the update, at least for now, if you want to keep root and twrp. Seems to be a number of people mentioning issues, including trouble reverting to 10b.
I also froze "System updates" with TiBU, going to stay on 10b until things clear up. Freezing that app seems to do the trick.
Why are you posting here, instead of the Verizon forum: http://forum.xda-developers.com/verizon-lg-g3/general
If you take the update, you can't re-root and you can't roll back.
Some people have maintained root after updating.
I've had my Note 4 for a while and after a few Lollipop update incidents I finally after a lot of hesitation decided to root my phone (with the TWRP bootloader) and disable the update notifier. Since then, I've always stuck to the latest stock version of KitKat 4.4.4.
Since I've rooted my phone, I made the following modifications that require root priviliges: I installed XPrivacy mod, YouTube AdAway mod, NoSafeVolumeWarning mod, PlayPermissionsExposed mod, and CrappaLinks mod for the Xposed framework. I also installed Titanium backup to freeze/uninstall the updater and AdAway. After XPosed was installed I had to change a line in /system/build.prop to 'ro.securestorage.support=false' to make 'S Health' work again. I did that with the 'FX' app.
That's it, I had made no more modifications and the phone seemed to work quite well for a month or so.
Two days ago I decided to try out Instagram, I've been quite wary with social apps but figured Instagram shouldn't hurt and everything was fine. Then I installed a bunch of dating apps, I started with Match.com and Tinder. Tinder didn't work because it required FB and Match didn't work because it refused to, probably because of denied permissions with XPrivacy so I gave up on them and uninstalled them.
But I also installed OkCupid and Motesplatsen and enjoyed playing around with these apps. They didn't seem to interfere with XPrivacy and worked rather fine. Motesplatsen was rather intense with sending me notifications of girls who watched my profile and sent me (rather strange) messages whereas OkCupid was rather calm.
Then something strange happened.
Yesterday I started noticing that the battery was draining considerably faster than normal during normal day. It was almost empty whereas it usually is half full after a full day, I also noticed that the phone was unusually warm. I forgot to put it on the charger and woke up today with a dead phone. I put it on charge and after about an hour the battery was full again.
When I tried to turn on the phone it was stuck on boot loop. I first tried disabling XPosed by "touch /data/data/de.robv.android.xposed.installer/conf/disabled" using the 'terminal' tool in the TWRP bootloader. It didn't help. I tried flushing the cache/dalvik cache but it didn't work either. Then I did a total factory reset, but that didn't work. I noticed that during boot, the phone froze so hard that it doesn't even respond to button pushes. I had to take out the battery to reboot (that's one reason why I never will buy S6).
So then I decided to flash the phone with stock KitKat once again using Odin and that finally restored the phone.
Now, here's one of my questions, how can things go so bad with a phone that not even a factory reset will fix it? We're talking stock firmware here, albeit it is rooted.
What boot logs could be worth looking into when such a thing occurs and what is the easiest way to extract them? The terminal tool in the bootloader seems promising, plus I saw a 'copy log to SD' option which I neglected this time.
I'm puzzled, does anyone know what happened? I made no root modifications in the process of installing these apps and they don't advertise themselves as needing root privileges. How can a seemingly inconspicuous app directly from Google play **** a phone up like that?
I originally updated my Verizon V20 to VS99513A before doing the Dirty Santa process a while back. All was well. But in the last couple of weeks or so, I've been getting an OTA prompt for a system update, for - you guessed it - VS99513A. My phone's software info already shows 13A installed (as it was already at that revision before Dirty Santa), but I get this OTA Update prompt every day now.
Questions: What's up with that? If I can't get rid of this prompt, can I turn off the process(es) that check for updates, and if so, what processes are they? It's an annoyance to have to reschedule this update each day for 24 hours knowing it's coming back, and annoying that I already have it installed.
Thoughts?
Heyitsrick said:
I originally updated my Verizon V20 to VS99513A before doing the Dirty Santa process a while back. All was well. But in the last couple of weeks or so, I've been getting an OTA prompt for a system update, for - you guessed it - VS99513A. My phone's software info already shows 13A installed (as it was already at that revision before Dirty Santa), but I get this OTA Update prompt every day now.
Questions: What's up with that? If I can't get rid of this prompt, can I turn off the process(es) that check for updates, and if so, what processes are they? It's an annoyance to have to reschedule this update each day for 24 hours knowing it's coming back, and annoying that I already have it installed.
Thoughts?
Click to expand...
Click to collapse
Disable both system update apps and this problem will be solved. One of them can be disabled through the application manager. The other can either be frozen through titanium backup, disabled via ADB or shell commands, or you can renamed the apk itself to .bak via a root explorer and rebooting (I don't recommend this unless you really know what you are doing).
I have the T-mobile variant, successfully converted to 9.05.
No problems with anything, other than I seem to "lose" root after the phone is on standby for awhile.
A reboot always restores root access.
For example, if I run greenify, after the phone has sat unused for awhile, I get a toast stating it cannot be run. I will then open up another root app, for example, adaway, and it will be denied access as well.
I also noticed that safety net check also fails in Magisk, as well, after being in standby for awhile.
A reboot fixes all.
Rinse, repeat.
I have used both the all in one tool to root and also tried the fastboot modified image file with no TWRP, and still have the same issue.
Any ideas?
TIA!
Sent from my ONEPLUS A6013 using Tapatalk