Related
I think the problems started ever since I rooted the device. That's the only thing I can think of. I will say that I only rooted it, I did not freeze or remove any apps, install anything or otherwise modify the system. I haven't even installed a recovery yet.
Is it possible the root made my system unstable? What do you guys suggest I do to try and fix this problem?
Thanks
Sent from my GT-N5110 using xda app-developers app
have you tried un-rooting? Anytime you mess with the system it has the potential to make it unstable.
Sent from my GT-N5110 using Tapatalk HD
I installed software on mine which changes color balance and runs as a service.
When it was running, the device crashed occasionally.
Once I uninstalled it, the behavior stopped.
Rooting probably doesn't create a problem, but try uninstalling any software you've added, then stepwise walk through adding in apps.
I've also seen some apps create lockups for the camera app.
theraker007 said:
I will say that I only rooted it, I did not freeze or remove any apps, install anything or otherwise modify the system. I haven't even installed a recovery yet.
Click to expand...
Click to collapse
Then why did you root? Just waiting for the development to come around?
I'm rooted and haven't seen this issue. Its rebooted once, maybe twice on its own in the 2 weeks or so since rooting.
Yeah I thought we'd have custom roms by now. How do I safely uproot and get back to factory. I would like to wipe everything and start from scratch
SuperSU
Using framaroot.apk with Aragorn exploit, I noticed that the SuperSU option is more stable that Superuser.
I ran into problems with my first Note 8 after I installed XMBC. It would lock up within 10 seconds or so of reboot. I would highly recommend that you take advantage of the root toolkit in this forum, install CWM recovery and make a full backup once you get it behaving again. It is good to have something to go back to if you have unexpected problems!
EDIT: You can flash back a stock image using the toolkit: http://forum.xda-developers.com/showthread.php?t=2251033
well i dont know what the heck is going wrong with the toolkit, but i did everything correctly, installed all the drivers, serial # shows up in the toolkit, checked off developer debugging mode. I tried to flash CWM from toolkit in PDA and everytime i try to go to recovery it just has the stock recovery there not CWM.
So I looked into all the stuff for rooting my T-mobile Note 3, checked to make sure that the multi touch bug wasn't there (I think I did it right), red up on the process and watched the video for the CF auto root 3 times before I did it. The root went without a hitch, I was able to install a few root programs (titanium, pimp my rom, Greenify, FullScreen, DriveDroid, Good Mood Droid Gesture Control, Stick Mount, AFWall+, Samba File Sharing, and some others I can't recall off the top of my head).
I was able to make a back up with Titanium, I went into AFWall+ and tweaked all my apps (only white apps in the list) and there was another "security" app I used, but it's name eludes me at this time (it was fairly similar to AFWall+. After that the phone just goes through a incessant boot loop. Starts up (which takes a little bit longer then normal), works for about 60 seconds normally, locks up and restarts. I tried pulling the battery and shutting it down, but it continues to do it.
I'm just wondering what could have caused this, how to fix it and what to do to ensure it doesn't happen again.
Thanks
DictatorZero said:
So I looked into all the stuff for rooting my T-mobile Note 3, checked to make sure that the multi touch bug wasn't there (I think I did it right), red up on the process and watched the video for the CF auto root 3 times before I did it. The root went without a hitch, I was able to install a few root programs (titanium, pimp my rom, Greenify, FullScreen, DriveDroid, Good Mood Droid Gesture Control, Stick Mount, AFWall+, Samba File Sharing, and some others I can't recall off the top of my head).
I was able to make a back up with Titanium, I went into AFWall+ and tweaked all my apps (only white apps in the list) and there was another "security" app I used, but it's name eludes me at this time (it was fairly similar to AFWall+. After that the phone just goes through a incessant boot loop. Starts up (which takes a little bit longer then normal), works for about 60 seconds normally, locks up and restarts. I tried pulling the battery and shutting it down, but it continues to do it.
I'm just wondering what could have caused this, how to fix it and what to do to ensure it doesn't happen again.
Thanks
Click to expand...
Click to collapse
If I were you I would start over again and Odin flash the stock official N900T 4.3 stock rom from
SamMobile.com or any other place which has it available for downloading.
After doing that, use the cf-auto root to root the phone and odin flash twrp or cwm recovery.
Once that's done make a Nandroid backup in recovery so next time when you have these bootloops,
lockups and other issues you can simply restore your rooted Nandroid backup.
All those apps you mentioned with the exception of titanium backup which you used to "TWEAK" your
phone are causing the issues you are having, there is no good reason to even use all those tweaking
apps and most likely are totally un-necessary in the first place.
If your phone works properly after odin flashing official stock firmware and rooting it then the fault
is not in the phone, or the official rom but the fault is in one of those tweaking tools you like to use
either because it's faulty, or you don't know how to use it.
If you can get into advanced settings of your WiFi connection in the 60 seconds before freezing, uncheck "always allow scanning". This had been known to cause boot loops for some people.
If it still loops, try uninstalling all those apps one by one to see which so is causing the issue.
And if that doesn't fix it, I would do as suggested above with the restore.
Sent from any phone that isn't made by Apple.
Maybe you could try something simple first: safe boot. In safe boot the culprit app should not start and if the damage is not in system files, that should give you chance to delete programs one by one and possibly find a culprit, otherwise, if you restore the ROM, you'll never know which one caused the problem. I would assume you wiped cache and if all failed, maybe factory reset?
So AT&T completely ruined my phone. They force me to update, and now my phone is basically unusable.
I know problems are running rampant after this update. All of my apps crash and freeze within minutes of opening them (so far I've had to reopen this app 3 times).
Phone itself and Internet (or anything using data, whether it's 4G or Wifi) are super slow now as well.
Does anyone have any suggestions on how to make this thing more than a paperweight?
I had the same issue. The only thing that ended working for me was wiping the phone clean and start fresh.
After that it was working fine.
Sent from my iPad using Tapatalk
That's unfortunate. Especially because when I wipe my phone I do it without backup because I want to eliminate any possibility of it screwing up again.
I guess that's the route I have to take though.
Nitroglycerin said:
So AT&T completely ruined my phone. They force me to update, and now my phone is basically unusable.
I know problems are running rampant after this update. All of my apps crash and freeze within minutes of opening them (so far I've had to reopen this app 3 times).
Phone itself and Internet (or anything using data, whether it's 4G or Wifi) are super slow now as well.
Does anyone have any suggestions on how to make this thing more than a paperweight?
Click to expand...
Click to collapse
the problems are caused by all of your personal apps being installed in a KK environment with dalvik runtime as default, Lollipop uses ART as the default runtime and this tends to cause compatibility issues
Mine seem to speed right back up after a factory reset but i went back to kk for temp root
Is there a permanent downgrade I can do instead of a factory reset?
I also didn't know there was a root out (been a loooooong time since I've worried about it). But if there is, that's what I want to do since I miss my root from my S4
Nitroglycerin said:
Is there a permanent downgrade I can do instead of a factory reset?
I also didn't know there was a root out (been a loooooong time since I've worried about it). But if there is, that's what I want to do since I miss my root from my S4
Click to expand...
Click to collapse
temp root only and it is still in beta, there are a few guides for downgrading in the general forum plus the needed files to do so
Just to clarify, temp root means two things. First, it will unroot if you reboot the phone. Second, devs are still attempting to finalize a non-temp root.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Nitroglycerin said:
Is there a permanent downgrade I can do instead of a factory reset?
I also didn't know there was a root out (been a loooooong time since I've worried about it). But if there is, that's what I want to do since I miss my root from my S4
Click to expand...
Click to collapse
Also if you decided to downgrade (which you can make perm.) it still wipes your phone. If you choose to stay on LP, factory reset as mentioned should remedy your problems.
Either way you will have to do it, unless you just want a screwed phone lol
Ugh. I hate AT&T so much for forced updates. All my stuff, gone. And why? Because they don't want me to be able to root? It's not their problem. I paid for this phone to be mine. So unless they want to give me my 700$ back, they shouldn't be able to force me into a new firmware.
Regardless, that's not the point. Since there's no way to save my stuff, I guess I'll have to wipe it.
Thanks for all the help guys/gals.
Its finally happened. I picked up my note 8 today from my nightstand and said "why not try" and low and behold, Kingroot 4.1 successfully rooted my Note 8!
Thanks , just download the apk 4.1 version of kingroot and get root acces for 4.4.2
Gracias , solo descarguen el apk version 4.1 de kingroot y listo acceso root para la i467 at&t , que hace tiempo ando buscando
excelente !
Done!!
Just rooted with King root 4.1
Thanks for the heads up on this!
---------- Post added at 09:46 PM ---------- Previous post was at 09:24 PM ----------
EDIT: After rooting with kingroot, I used the app from the Google play store called "SuperSu Me" This app removes king root and installs supersu while keeping root... it took less than a minute to do.
Amazing app
I tried this on two tablets and it failed. Is there specific procedure?
KC
Not sure which version of kingroot you're using, but o.p. specified to use version 4.1.
I downloaded king root v4.1... and ran it... no tricks.
Here is a link that I found to the app for kingroot for you:
https://userscloud.com/33vyymss3kkq
Hope the picture uploaded....I get this screen using 4.1.
Do this first : flash with odin 3.09.3 the original firmware 4.1
: select "AP" choose the at&t firmware it comes with 4.1 android version
then update to kit kat , rename the file on internet called xxxx.cfg to xxxxxx.zip
put this file in your micro sd card, reboot on recovery stock and flash the update , and get 4.4.2 android kk, then , download the apk 4.1 , do not connect the tablet online to the website of king root , this method does not work, it is with the apk 4.1 version of kingroot and done!
Importante : tablet on mode developer option and usb debugging check
None of the king root versions I found work. Gets to 24% then reboots.
No luck yet. Will keep waiting.
That was my experience as well. Not sure if this is viable based on my experience.
It's definitely a feasible process, it worked fine for me. I'm really confused why it works for some people but not for others...
For those still trying to gain root access using Kingroot... here is a link to a few different versions of "kingroot", a version of "kinguser" (their version of supersu), and a version of "purify" (their version of a memory manager). If it didn't work easily, it may still work with a bit more trial and error, as it did for me (after losing root yesterday).
https://drive.google.com/file/d/0B3w...ew?usp=sharing
Yesterday morning, i woke up to find that I had somehow lost root on my tablet... I tried to re-root using the previous process, and it no longer seemed to work. Soooo, I spent a good chunk of time figuring out how to get root back yesterday. The good news is, I got root back... the process however, was somewhat convoluted.
So I tried to find a step by step reproduce-able way to get root every time - and I was not successful at coming up with an exact process that works every time... I was however able to get rooted every time, but the process seemed to vary a bit each time... so trial and error seems to be the key here. I experimented for hours doing this... gaining root, uninstalling root, and retrying - all in the name of trying to help others figure out how to do it on their device.
So here is the basics of how I achieved root... DISCLAIMER - I TAKE NO RESPONSIBILITY FOR YOU, YOUR ACTIONS, OR THE FUNCTIONALITY OF YOUR DEVICE - BEFORE/DURING/OR AFTER YOU TRYING ANY OF THESE PROCESSES THAT I TRIED. THINGS CAN GO WRONG - YOU CAN END UP WITH PROBLEMS - A BRICKED TABLET, A DIVORCE, A DEAD DOG, OR HIT BY A NUCLEAR BLAST. ANY OF WHICH, I TAKE NO RESPONSIBILITY FOR. IF YOU PUSH THE BUTTONS, ITS YOUR RESPONSIBILITY.
Since there is no factory image for 4.4.2 on our device, proceed with caution... if something goes really wrong, you will have a paperweight. There is no Kies or Odin to save you... Also, my knox warranty void count shows as 1 and custom device status, so if you are worried about that be aware...
1) download all the files in the folder at the link above, extract them from the folder and put all the apk's on your device, but dont install them yet (doesn't matter internal/external memory)
2) Boot into stock recovery and wipe cache. reboot.
3) Install kingroot v4.0.1.237
4) open kingroot and try the rooting process. the device will likely reboot at around 18 to 25% or so... once the device reboots, open kingroot again and let it finish the rooting process. If it works - you should go buy lottery tickets, because you just got really lucky! If it doesn't work, proceed to the next step.
5) Install Purify. Run Purify process. Take notice after running the process - at the top of the app does it say root is achieved?? If not, return to step 4 and try rooting again. If that does not work...
6) Install kinguser. open kinguser, does it say you have root access? If not, try the prompt to repair root access (if it shows up)... if not, return to step 4, and try to root again. If no root, try step 5 again. If not, try step 6 again...
7) If still no root access, uninstall kingroot, and install one of the other versions of kingroot... try all of the above again. If still no root... uninstall all 3 apps and start over at step 2 using a different version of kingroot to start with.
I wish I could say there was a logical rhyme or reason for what works and what doesn't... but there didn't appear to be an exact process that works every time. Fortunately, I was able to get root if I tried long enough and tried different combinations of processes. Periodically clearing the cache from the stock recovery really seemed to help increase my odds of success when things weren't going well.
Occassionally the process landed me in a bootloop at the at&t screen... after holding the power button for an eternity, the device would power off - then I would reboot and it would boot normally.
Additionally, I tried on many occasions to swap "kinguser" with "supersu" using an app call "Super-Sume". Sometimes the process worked, and successfully removed kingroot, kinguser, and purify - while keeping root and installing Supersu... Other times the process removed the kinguser, kingroot, and purify - but I also lost root. I tried both the paid and free versions of Super-Sume, but the free version is the one that seemed to work best.
It's up to you if you want to go through all of this - it was tiresome... but if you really want root, maybe trying something like this might help you - maybe not. I also noticed that kinguser seems to sometimes have root access, sometimes not... so sometimes it was just a matter of opening one of the 3 apps and re-running a process or two and root would be restored... not sure why that happens - which is why i opted to use super-sume to remove kingroot once root was achieved. but we will see if i keep root now... if not, at least I know the process above seemed to work for me.
Thanks Dandroid, I will try your suggestions. I got this tablet 2 months ago, rooted it right away with Kingroot, worked great. But was suspicious of the app, so used supersume to remove. Had root for a few more days then lost it. My first thought was the Samsung Security updates patched the root. So I download Kingroot and run it again and it doesnt work anymore. Why is root not working? Either the Samsung security updates closed the loophole or somehow Kingroot punishes you for removing their app. I believe Kingroot puts you on a blacklist because they have your IP address and IMEI. These are just my suspicions. So Dandroid do you still have root after all this time?
dandroid7 said:
For those still trying to gain root access using Kingroot... here is a link to a few different versions of "kingroot", a version of "kinguser" (their version of supersu), and a version of "purify" (their version of a memory manager). If it didn't work easily, it may still work with a bit more trial and error, as it did for me (after losing root yesterday).
https://drive.google.com/file/d/0B3w...ew?usp=sharing
Yesterday morning, i woke up to find that I had somehow lost root on my tablet... I tried to re-root using the previous process, and it no longer seemed to work. Soooo, I spent a good chunk of time figuring out how to get root back yesterday. The good news is, I got root back... the process however, was somewhat convoluted.
So I tried to find a step by step reproduce-able way to get root every time - and I was not successful at coming up with an exact process that works every time... I was however able to get rooted every time, but the process seemed to vary a bit each time... so trial and error seems to be the key here. I experimented for hours doing this... gaining root, uninstalling root, and retrying - all in the name of trying to help others figure out how to do it on their device.
So here is the basics of how I achieved root... DISCLAIMER - I TAKE NO RESPONSIBILITY FOR YOU, YOUR ACTIONS, OR THE FUNCTIONALITY OF YOUR DEVICE - BEFORE/DURING/OR AFTER YOU TRYING ANY OF THESE PROCESSES THAT I TRIED. THINGS CAN GO WRONG - YOU CAN END UP WITH PROBLEMS - A BRICKED TABLET, A DIVORCE, A DEAD DOG, OR HIT BY A NUCLEAR BLAST. ANY OF WHICH, I TAKE NO RESPONSIBILITY FOR. IF YOU PUSH THE BUTTONS, ITS YOUR RESPONSIBILITY.
Since there is no factory image for 4.4.2 on our device, proceed with caution... if something goes really wrong, you will have a paperweight. There is no Kies or Odin to save you... Also, my knox warranty void count shows as 1 and custom device status, so if you are worried about that be aware...
1) download all the files in the folder at the link above, extract them from the folder and put all the apk's on your device, but dont install them yet (doesn't matter internal/external memory)
2) Boot into stock recovery and wipe cache. reboot.
3) Install kingroot v4.0.1.237
4) open kingroot and try the rooting process. the device will likely reboot at around 18 to 25% or so... once the device reboots, open kingroot again and let it finish the rooting process. If it works - you should go buy lottery tickets, because you just got really lucky! If it doesn't work, proceed to the next step.
5) Install Purify. Run Purify process. Take notice after running the process - at the top of the app does it say root is achieved?? If not, return to step 4 and try rooting again. If that does not work...
6) Install kinguser. open kinguser, does it say you have root access? If not, try the prompt to repair root access (if it shows up)... if not, return to step 4, and try to root again. If no root, try step 5 again. If not, try step 6 again...
7) If still no root access, uninstall kingroot, and install one of the other versions of kingroot... try all of the above again. If still no root... uninstall all 3 apps and start over at step 2 using a different version of kingroot to start with.
I wish I could say there was a logical rhyme or reason for what works and what doesn't... but there didn't appear to be an exact process that works every time. Fortunately, I was able to get root if I tried long enough and tried different combinations of processes. Periodically clearing the cache from the stock recovery really seemed to help increase my odds of success when things weren't going well.
Occassionally the process landed me in a bootloop at the at&t screen... after holding the power button for an eternity, the device would power off - then I would reboot and it would boot normally.
Additionally, I tried on many occasions to swap "kinguser" with "supersu" using an app call "Super-Sume". Sometimes the process worked, and successfully removed kingroot, kinguser, and purify - while keeping root and installing Supersu... Other times the process removed the kinguser, kingroot, and purify - but I also lost root. I tried both the paid and free versions of Super-Sume, but the free version is the one that seemed to work best.
It's up to you if you want to go through all of this - it was tiresome... but if you really want root, maybe trying something like this might help you - maybe not. I also noticed that kinguser seems to sometimes have root access, sometimes not... so sometimes it was just a matter of opening one of the 3 apps and re-running a process or two and root would be restored... not sure why that happens - which is why i opted to use super-sume to remove kingroot once root was achieved. but we will see if i keep root now... if not, at least I know the process above seemed to work for me.
Click to expand...
Click to collapse
Yes, I still have root.
I recently read in a forum for a different device that king root is actually a temporary root??? I have not seen that said anywhere else, just in that forum, so not sure if that was device specific?? But that does seem to explain why we lost root...
Since I used super-sume to remove king root and retain root, that may be why I still have root. As soon as I installed supersu, I also checked the survival mode box on supersu to try and keep root.
typhoonk said:
None of the king root versions I found work. Gets to 24% then reboots.
No luck yet. Will keep waiting.
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/galaxy-note-8-0/help/root-sgh-i467-4-4-2-success-t3182211
It's supposed to reboot... after it reboots, reopen the KingRoot app and let it finish the process. The English version of the app clearly says that it will need to reboot and then finish the rooting process.
I used the computer version. Worked prefect. Then unistalled with superseme
Sent from my SAMSUNG-SGH-I467 using Tapatalk
I appreciate everybody's input on this. It seems that some of us have been successful. I however have not.
Is there any way to get a system image from one of you folks that are already rooted, so the rest of us can load in our tablets? I don't know if this is a stupid question I'm not that well versed in loading via Odin.
King root v4.1
It seemed to work fine with my note 8 I'm running sgh-i467 4.4.2 but yet to find any custom rom, when there is one made please let me know! Just rooted today and I love the freedom but would like to learn a lot more about the different stuff I could do with this, any suggestions??
till this newest ver, 46.2, Kingroot never worked on mine but somehow it rooted my device with this new version..
Not sure why, but I love this having root on Note8 now.
I have a VS985 LG G3. I was running marshmallow yesterday, but after trying to root and unlock mobile tethering and hotspot (because I am on unlimited data) I managed to brick my phone while typing in adb commands because my phone decided to randomly shut off. So after plugging it into the USB and figuring out a way to put it into download mode, I flashed it to VS98510B. After that, I rooted with Stump Root and installed SuperSU, following some guides. It works fine once again but I'm not where I want to be.
After multiple times trying to open adb shell and get it to just recognize my device, I'm done. I know there are people out there who know this stuff by heart, so please, at this point, just tell me what to do step by step so I can do it and move on with my life. I have spent hours upon hours on this and it never seems to just work. Please.
All I want is to be able to install the latest TWRP or whatever is recommended., and then install either the SkyDragon Rom or the stock marshmallow VS98546A rom, but with the verizon apps disabled since in one guide it warns that those report for modified device, which I am not sure what that means but it doesn't sound good.
I'm on VS98510B. Rooted and SuperSU installed.
I want to be able to use mobile hotspot and tethering.
There's just information overload to the extreme, I'm overwhelmed.
Thanks again if any help is possible.
If you're already rooted with TWRP installed, the hard part should really be over. You shouldn't need to be plugging into a computer and running adb commands at this point. You also said you need step by step instructions, and to really spell it all out would be a lot, but considering how far you already got I don't think you really need every little detail, so I'll give you the general idea then if you have questions I can try to fill those gaps.
Basically you'll need to find and download the new ROM you want. The easiest thing to do is download it directly from your phone so you don't have to mess around with transferring it from your computer to your phone. Many custom ROMs will also require Gapps, but if you're flashing a stock ROM (or a custom ROM based on stock) you don't need to do this because it's included in the ROM.
After you've downloaded the ROM (should just be a zip file), you need to reboot to recovery (TWRP). If you don't know how to do this, there's an app called Quick Reboot that can do it for you (01400) personally haven't used it but I assume it works).
Once you're in recovery, you normally want to make a backup first in case anything goes wrong. This is done by selecting the backup button. After you have a backup, you want to "wipe" data before installing. Select the wipe button, then I click advanced and select everything except internal data and external data. This will wipe all apps, settings, etc. from your phone so make sure you're ok with that before you do it,
After wiping, you're ready to install. Back at the first main screen of TWRP, select Install, then browse to where you downloaded the ROM and select it, then select the Install button and swipe to confirm. Assuming all goes well, when it's finished it'll give you the option to reboot. Do this and it should start booting up to your new ROM.
Also, you mentioned SkyDragon, but I just wanted to point out that this isn't the latest version of Android, I believe that's still Lollipop (not Marshmallow). You also mentioned not wanting your rooted status to be reported to Verizon, but if you're currently on stock, rooted, and don't have any apps disabled, then you already are running this risk.
Let me know if you have any questions. I think this will be easier than me trying to walk you through every detail and confirmation screen.
I don't have TWRP installed. What is the best course of action to take to install it?
As far as disabling verizon apps, is it as simple as just going into the application manager and disabling them or is there a tool I need to download?
Thanks for all the help so far!
I see, it's been a couple years since I installed TWRP and I was thinking it was part of the rooting process. I believe this is the post I followed to install TWRP: http://forum.xda-developers.com/lg-...mp-unlock-lg-g3-twrp-d852-d852g-f400-t2900614
Like I said, this was a few years ago and it's kind of a one-time thing. I don't know if there's something better available now or what, and I don't remember the details. I don't remember running into any problems, so if you happened to have any I'm not sure how good I could help.
As for disabling things, the things that need to be disabled are system apps and can't just be disabled from the stock application manager (Verizon doesn't want to make it easy for you to disable their software ). There are different ways this can be done, but I personally use Titanium Backup to disable (or "freeze" as they call it) apps. It will let you freeze anything, which also means it gives you the ability to break things, so don't just go in freezing random things. I don't remember if freezing requires the paid version of the app or not, but you can get it from the play store and find out.
Sent from my VS985 4G using Tapatalk
As far as Titanium Backup goes, is it along the same lines as TWRP? Like do they do the same things? Do you recommend I do one over the other?
Also as far as verizon apps reporting root, what do they do and what does that matter?
Also, I'm currently dealing with the LG DemiGod Crash Handler problem that seems to have started up on my phone the other day. I'd never rooted or messed with my phone in any way and that started happening, I thought perhaps flashing a new ROM might fix it, but I guess not. If you have any sort of tips on how to fix that, other than replace the battery (which I have not yet done, but supposedly that can solve the problem) I'd be grateful.
Titanium Backup and TWRP are two different things. Titanium Backup is a "normal" app that you can get from the Play store, while TWRP is a custom recovery and isn't ran from within your ROM. TWRP lets you do full image backups of your phone (like your entire phone in a single backup) and can also be used to install ("flash") ROMs. Titanium Backup lets you backup, freeze, and uninstall specific apps.
I use them both because they both serve a specific purpose. You have to use TWRP to install ROMs, then as far as backups, I use TWRP to make a backup of everything in case I flash a ROM that I end up not liking (I can use the backup to easily go back to my previous ROM and still have apps and everything all setup just like they were). If I do like the new ROM I flashed, I'll use Titanium Backup to restore a lot of my apps/data to the new ROM (ex. text messages, my alarm clock app, etc.)
As far as Verizon knowing about your root status, honestly I'm not sure what all that would mean. I'm sure they wouldn't like it, rooting voids your warranty so you probably couldn't get things replaced under warranty, if you have insurance through Verizon they would maybe use your root status as a reason to deny a claim, etc. I don't think you'd have to worry about them calling you up or cancelling your service or anything like that, but getting them to assist you with problems might be more frustrating than usual
Regarding the demigod crash thing, I know what you're talking about but I don't really know much about it. A while ago I would get those every once in a while and it was frustrating. I think at the time I kind off wanted to try a new ROM anyways and I think I did but I still got it occasionally. Now that you mentioned it though I haven't had one in quite a while. I'm not sure if those ROMs both happened to cause it, if it was a Lollipop thing (doesn't seem like I've had it since Marshmallow), or if it's all just a coincidence or I've just been lucky. I haven't gotten a new battery though, so that's definitely not it (for me anyways).
Sent from my VS985 4G using Tapatalk