Different Root Methods - Verizon LG G3

Besides they all roots the phone and different ways to root the phone; any difference between those methods? Like will one cause a phone to random reboot more often (stability), battery drain, wifi, wireless signal changes, performance, etc.
IOroot
PurpleDrake-Lite
Stump Root
thank you

PurpleDrake won't work with the VS985 (Verizon) version. I used IOroot on my phone because it was the only option at the time, but I would say go with Stump Root now as it is easier/faster. In general the only thing these root methods do is exploit a security vulnerability to install the su binary on the system partition, and that is the only lasting effect. With su installed, it is possible to assume root privilege. Random reboots, battery drain, wifi, wireless signal changes, and performance loss are not directly affected by root; however it is possible that an app that uses root privilege could impact these, so be careful what you install.

I used the stump root method because it came out the day after I got my phone and I'm lazy as hell. Any phone I've ever rooted has had multiple methods and they all do the same exact thing. So I wouldn't worry too much about it. @bobcat987 I couldn't have it it better myself.

Hyper_Warp said:
Besides they all roots the phone and different ways to root the phone; any difference between those methods? Like will one cause a phone to random reboot more often (stability), battery drain, wifi, wireless signal changes, performance, etc.
IOroot
PurpleDrake-Lite
Stump Root
thank you
Click to expand...
Click to collapse
No. These different methods exploit a vulnerability that allows them to gain "root" to modify the file system to place the "su" binary on the system which in turn allows you to get privileged/superuser access.
These methods, although different, do essentially the same thing and leave "su" behind.
None of them affect the things you are talking about.

Ok, thank you everyone for the responds and information!

I used stump root. Works like a charm.

Is it pretty easy to reverse the root? My past couple phones I haven't rooted(sorta because it was difficulty, moto x), but also cause I've trying to get away from it because I was spending too much time on it lol. So I'm a little out of the loop, but is it pretty easy to reverse the root? In case of an update or something of that sort. I mainly want like wifi tether, ad block.

To unroot, you have to uninstall both su and whatever superuser app you are using to manage app access to su.
Otherwise you would have to flash the original TOT file to completely return the phone to fresh as shipped, and that is not exactly "easy".

Related

[Q] Reinstalling Su Binaries (Kyocera Rise)

I know that not many people may be able to help as this is a long story but here it goes:
I had used a root toolkit (I know that I will receive hate) to root my kyocera rise as rooting by hand has become a pain. Anyways, I had run into an issues where my phone would not run properly (possibly due to malware or the likes) and as such I reset it back to factory data. For months after I had assumed that I did not have root anymore because I had lost the supersu app (stupid me forgot to check root). Recently I realized that in one of my apps that could use root, it was using root and I did not even know it.
Seeing that this would cause some security issues, I quickly installed super su and updated the binaries. From then on, whenever an app tried to request root permission, it would then freeze. I then uninstalled super su and did the unroot setting from software and then planned to reinstall it. When I reinstalled supersu, It complained that it could not install binaries and this was bad (lol).
Anyways, the kyocera rise has a locked bootloader that prevents me from completely flashing over a new copy of the os, which sucks, and now I feel like I am stuck with an unrootable device because I can't seem to reinstall the binaries to allow super su or any other superuser program to work properly. Any Help would be appreciated. FYI, this is just stock android, nothing fancy about it.
-Fishwithadeagle
i have the same problem
i may have to say am also facing a similar problem. i mistakenly permanent unroot my phone with my binary su. now all my apps that needs root aint functioning. i tried to re-install the binarySU but jux couldn't. i have also tried using gingerbreak to start all over again just to get my phone rooted. it simply cant.....please i need help..... i want to root my phone again
Try this tutorial...
http://forum.xda-developers.com/showthread.php?t=2307306
Sent From Tweaked Kyocera

ZTE Speed, root impossible to get?

I'v ran through all root methods (that i know of) for this phone (4.4.4) and none of them work. at all. Whats the point of a root dir if its impossible to access? Seems to be limited info on a root method for this phone. Is it root proof?
dunnothename said:
I'v ran through all root methods (that i know of) for this phone (4.4.4) and none of them work. at all. Whats the point of a root dir if its impossible to access? Seems to be limited info on a root method for this phone. Is it root proof?
Click to expand...
Click to collapse
For now because of the locked bootloader
Root Achieved!!
UPDATE
I got Kingroot to root the zte speed!!!
but it doesnt keep root for very long. usually only stays rooted for a matter of minutes, and you have to reroot it everytime you reboot
I had to install "certificate installer" from google play and install a root certificate.
now im just trying to figure out how to keep it rooted
me to i cant get root to stay there maybe the kingroot guys can fix that in a updat.
dunnothename said:
UPDATE
I got Kingroot to root the zte speed!!!
but it doesnt keep root for very long. usually only stays rooted for a matter of minutes, and you have to reroot it everytime you reboot
I had to install "certificate installer" from google play and install a root certificate.
now im just trying to figure out how to keep it rooted
Click to expand...
Click to collapse
vv
Wanted to post update on this thread for people who come by via Google wanting to root that zte speed, as I was sick of coming by this thread as seeing no answer from the search results.
I did the following and was able to get permanent root with SuperSU
Source/Inspiration for this guide (thank you hroark13): androidforums / zte-speed-n9130-permanent-root-achieved.1061137
With ADB enabled and hooked up, run " adb shell reboot disemmcwp "from your PC. This helps to unlock some key parts for Kingroot to work much quicker and persist. That was the secret sauce that was not known in 2015 when everyone was trying to root this at first.
I used Kingroot 5.3.8 from APK mirror as that was easiest (no need to install the Kingroot application on PC just downloading the APK is enough to the phone). I was also running AnTuTu Benchmark Stress Test at the same time as running Kingroot, but this might not be necessary.
I installed Busy Box, and got the SuperSU downloaded ahead of time from the play store as well. I had tried to run Super SU but it couldn't replace the binary, so:
Finally, replace Kingroot with SuperSU by using the Super-Sume Pro app, pretty much just follow through the prompts in the app, but before you start be sure to disable Auto Updates in Kingroot first to prevent a possible conflict. The app will prompt you to reboot, which you can do.
Should have permanent root on your ZTE speed now, you can skip the last step if you like the Kingroot manager but generally people like Super SU better so I changed it to that (less janky).
Warning, if you screw any of this up there is no way to recover your ZTE speed so therefore you could end up with $20 brick.
Thank you, hope this helps someone out who has one of these in their junk drawer.

Root cricket Kyocera hydro view. HELP PLEASE!!!!!!!!

Can some one help me root a Kyocera hydro view with no computer . its from cricket it runs lollipop.
Try either kingoroot or kingroot... Kingoroot worked on my Hydro Icon.
Sent from my KYOCERA-C6745 using Tapatalk
I was able to gain root access for about 2 minutes before phone reset itself using kingoroot. Has anyone found an exploit or any other rooting methods?
I have been trying to root my kyocera hydro root since I got it but have had no success, I have tried every root method I could find but all have failed. The closest was kingoroot that did get su installed 2 times but the location of su was not able to update and upon reboot disappeared.
Same Boat Buddy
vanquishedangel said:
I have been trying to root my kyocera hydro root since I got it but have had no success, I have tried every root method I could find but all have failed. The closest was kingoroot that did get su installed 2 times but the location of su was not able to update and upon reboot disappeared.
Click to expand...
Click to collapse
ill touch base with you it i find something out also i have the same phone it has been a real a$# kicker:crying::crying:
Has anyone had any more luck rooting the Kyocera Hydro View? As the others before me, I've had temporary luck with Kingo Root, but nothing beyond that. This phone desperately needs Marshmallow or at least root so that the default app install location can be changed. I can live with all it's other faults, but the storage situation is hard to get past. I had hoped to be able to root and use something like link2sd or even do a 'pm set-install-location 2' to make use of external storage and get more than only a few apps installed at a time, but no luck with only the temporary root provided by Kingo Root. The improved storage management available in Marshmallow would be ideal, but I'm trying not to get my hopes too high for that.
Have you tried Kingroot? you can usually get temp root to uninstall apps, but it might reboot itself, but if your fast, you can make changes before you lose root. But you will lose your ability to get cricket updates. You'll get a warning that the device is suspected of rooting.
Still no root for this device?
Neo3D said:
Still no root for this device?
Click to expand...
Click to collapse
I finally got it to permanently root with Kingo Root. Took numerous times running it and phone sometimes rebooted, updated and optimized files. Did eventually root and stick permanently but took A LOT of patience. Have to keep running Kingo Root and rebooting phone. It will also reboot itself sometimes, have to let it do its thing. Again, lots of patience, rebooting phone, restarting Kingo Root, waiting, rebooting, re-starting Kingo Root...................on and on. Like 10 times or more maybe.
After root, how to get the system?
popeye2014 said:
I finally got it to permanently root with Kingo Root. Took numerous times running it and phone sometimes rebooted, updated and optimized files. Did eventually root and stick permanently but took A LOT of patience. Have to keep running Kingo Root and rebooting phone. It will also reboot itself sometimes, have to let it do its thing. Again, lots of patience, rebooting phone, restarting Kingo Root, waiting, rebooting, re-starting Kingo Root...................on and on. Like 10 times or more maybe.
Click to expand...
Click to collapse
After those 10 times, did the root finally stick? Bit confused by your post? Do you still have to re-root after reboot or is it permanent?
Did any one root and flash this Kyocera Hydro View from Cricket?
Was any one successfully to root this one and install new Nougat or other OS ? is this compatible?
Does any one know how to flash this with coustom recovery TWRP etc ? as I know this doesn't go in to recovery and don't want to brick this with out having a reimage Any insights are welcome!
popeye2014 said:
I finally got it to permanently root with Kingo Root. Took numerous times running it and phone sometimes rebooted, updated and optimized files. Did eventually root and stick permanently but took A LOT of patience. Have to keep running Kingo Root and rebooting phone. It will also reboot itself sometimes, have to let it do its thing. Again, lots of patience, rebooting phone, restarting Kingo Root, waiting, rebooting, re-starting Kingo Root...................on and on. Like 10 times or more maybe.
Click to expand...
Click to collapse
I see two websites for Kingo Root. Which one do I trust?
While KingoRoot was a failure, KingRoot seems to temporarily acquire root after much work, only to lose it on next reboot. Unfortunately, but has allowed me to at least remove some bloatware on this 3.5GB internal storage device. Wew.
While signing up for Cricket and finding out my T-Mobile Samsung Galaxy S 4G from 2007 wouldn't work on their network, made a snap buy of the Kyocera. None of the 3 people spoken to while signing up with Cricket mentioned an online promotion for portaling an existing number in which I could have gotten a better phone for free or a good discount on a much, much better phone. Found out next day and wanted to take advantage of the promotion but everyone says, 'portal already happened, you missed out, we own your ****, too late.'
So far I am not impressed with their customer service. My bad for snap buy of the Kyocera deserves no praise, however.
Will try it!
popeye2014 said:
I finally got it to permanently root with Kingo Root. Took numerous times running it and phone sometimes rebooted, updated and optimized files. Did eventually root and stick permanently but took A LOT of patience. Have to keep running Kingo Root and rebooting phone. It will also reboot itself sometimes, have to let it do its thing. Again, lots of patience, rebooting phone, restarting Kingo Root, waiting, rebooting, re-starting Kingo Root...................on and on. Like 10 times or more maybe.
Click to expand...
Click to collapse
Thanks for the information, well lets get started

Is Kingoroot safe?

Hi, i was wondering if Kingoroot is safe to use. I want to root my phone but i'm really new at rooting and i don't know too much about rooting.
Thanks in advance
Yes
It is however I recommend KingRoot as it is better and safer (kingroot.net)
kingoroot worked to root my old lg volt but....
...but I have a moto g3 that I rooted with twrp, and I now recognize the danger of the rooting apps. See after routing my moto g3 I installed all kinds of stupid apps that I really didn't understand. I screwed up the phone about five times now. The reason I could do that though, is because twrp has my back. Every time I have the phone running great, I create a backup in twrp. So when I get things too screwy I just go back to one of my backups.
What I'm saying is KINGOROOT is NOT AS DANGEROUS AS YOU CAN BE TO YOUR PHONE WITH ROOT PERMISSIONS AND NO RECOVERY. Every app in the playstore that requires root can screw up your phone. Believe me ive screwed the pooch enough to know.

Does this version of Kingroot work for Thor 4.5.5.2?

Someone on another forum posted that this version of Kingroot, apparently updated 1/22/17 (v 5.0.3), works for the last update of Fire OS on Thor (4.5.5.2). Has anyone tried this out? I want it to be true, because I lost root on the last update, but I don't want to brick my device or open myself up to any other issues if it's some sort of trojan. At some point I was going to try a rollback and then root, but I would much prefer to use a one and done apk if possible. Can anyone confirm that this works?
Vanb85 said:
Someone on another forum posted that this version of Kingroot, apparently updated 1/22/17 (v 5.0.3), works for the last update of Fire OS on Thor (4.5.5.2). Has anyone tried this out? I want it to be true, because I lost root on the last update, but I don't want to brick my device or open myself up to any other issues if it's some sort of trojan. At some point I was going to try a rollback and then root, but I would much prefer to use a one and done apk if possible. Can anyone confirm that this works?
Click to expand...
Click to collapse
All KingRoot builds use the same cloud database to scan for vunerabalities and match up with known exploits. The various KingRoot clients may sequence tests differently and clutter your device with varying 'gifts'... especially the v5 series. I would go the rollback and root path. It's safe, easy and fast. Only caveat is the device must maintain network isolation (WiFi off; airplane mode engaged) while the device is on FireOS 3.2.8. If the device takes an OTA update while on 3.2.8 it will brick with no possible recovery.
Davey126 said:
All KingRoot builds use the same cloud database to scan for vunerabalities and match up with known exploits. The various KingRoot clients may sequence tests differently and clutter your device with varying 'gifts'... especially the v5 series. I would go the rollback and root path. It's safe, easy and fast. Only caveat is the device must maintain network isolation (WiFi off; airplane mode engaged) while the device is on FireOS 3.2.8. If the device takes an OTA update while on 3.2.8 it will brick with no possible recovery.
Click to expand...
Click to collapse
KingRoot is basically how I was planning on rooting my device anyway. Is there any real advantage, in terms of "safety" with applying KingRoot after I've done the rollback as opposed to before doing one? And can KingRoot even be don on 4.5.5.2? I've been told ad naseum that this version of Fire OS cannot be rooted, but it looks as though it can now. If I'm going to be taking a risk with KingRoot anyway, wouldn't it be better to do so without the rollback and possible bricking of my device? Has there been any confirmation that KingRoot can in fact root 4.5.5.2 now?
eta: And just to be clear, this is KingRoot that we're talking about, right, not KingORoot?
Yes, I used Kingroot 4.8.1 to root 4.5.5.2. It took a couple of retries, but eventually it was successful.
Vanb85 said:
KingRoot is basically how I was planning on rooting my device anyway. Is there any real advantage, in terms of "safety" with applying KingRoot after I've done the rollback as opposed to before doing one? And can KingRoot even be don on 4.5.5.2? I've been told ad naseum that this version of Fire OS cannot be rooted, but it looks as though it can now. If I'm going to be taking a risk with KingRoot anyway, wouldn't it be better to do so without the rollback and possible bricking of my device? Has there been any confirmation that KingRoot can in fact root 4.5.5.2 now?
eta: And just to be clear, this is KingRoot that we're talking about, right, not KingORoot?
Click to expand...
Click to collapse
KingRoot is borderline malware but gets the job done (eventually; often takes multiple attempts) and carries no additional liabilities if the device is going to be immediately unlocked and wiped. 4.5.X -> 3.2.8 rollback is not unduly risky if network isolation is maintained on 3.2.8. TowelRoot is the tool of choice on FireOS v3; fast and reliable. Ultimately the choice is yours. Good luck.
Davey126 said:
KingRoot is borderline malware but gets the job done (eventually; often takes multiple attempts) and carries no additional liabilities if the device is going to be immediately unlocked and wiped. 4.5.X -> 3.2.8 rollback is not unduly risky if network isolation is maintained on 3.2.8. TowelRoot is the tool of choice on FireOS v3; fast and reliable. Ultimately the choice is yours. Good luck.
Click to expand...
Click to collapse
Another quick newbie question. Does KingRoot have to stay on your device in order to maintain root access? Can I use it to root and then uninstall it and still maintain root access? Is that what you mean by "unlocked and wiped?"
Vanb85 said:
Another quick newbie question. Does KingRoot have to stay on your device in order to maintain root access? Can I use it to root and then uninstall it and still maintain root access? Is that what you mean by "unlocked and wiped?"
Click to expand...
Click to collapse
Uninstalling KingRoot (KingUser) via conventional means also removes root. There are methods for transitioning a different root manager (eg: SuperSU) if you plan to stay on FireOS. SuperSume is one such tool. Does not seem to be effective against more recent KingRoot builds which actively resist removal.
Unlocking refers to the bootloader; wiping is a recommended prerequisite for cleanly replacing FireOS with a custom ROM. Wiping also removes KimgRoot detritus.
Anatinae said:
Yes, I used Kingroot 4.8.1 to root 4.5.5.2. It took a couple of retries, but eventually it was successful.
Click to expand...
Click to collapse
Have you tried installing SuperSu or another root manager as a replacement since rooting with KingRoot?
I unlocked the bootloader and installed LineageOS. Using the default root included with the latest unofficial build.
Anatinae said:
I unlocked the bootloader and installed LineageOS. Using the default root included with the latest unofficial build.
Click to expand...
Click to collapse
I see. So you replaced KingRoot with the default root manager that came with the LineageOS build?
Update: I did install KingRoot. And I installed the Google Play Store after that. I was unable to replace KingRoot with SuperSu. So, I uninstalled KingRoot, and of course, it took root access with it. But I got what I wanted, for the most part, which was to be able to install the Google Play Store on my HDX. It appears to be working fine even without root access. I would have preferred to keep root access, but I don't really trust KingRoot enough to keep it on my device. Now, I just need to block updates so Amazon doesn't mess with GPS.
Can anyone tell me if it's okay that I moved the DeviceSystemOTA.apk to another folder? It wouldn't allow me to rename it, so I cut and paste it into another folder to rename it with the intention of moving it back to the system folder. I realized after it wouldn't allow me to put the file back that I can't do anything with the system folder (can't rename things, can't add files) now that I don't have root. It only let me remove the file. Is it okay that the file is just not in the system folder? I was essentially going to make it inoperable by renaming it and removing "apk" from it anyway. @Davey126?
Vanb85 said:
Can anyone tell me if it's okay that I moved the DeviceSystemOTA.apk to another folder? It wouldn't allow me to rename it, so I cut and paste it into another folder to rename it with the intention of moving it back to the system folder. I realized after it wouldn't allow me to put the file back that I can't do anything with the system folder (can't rename things, can't add files) now that I don't have root. It only let me remove the file. Is it okay that the file is just not in the system folder? I was essentially going to make it inoperable by renaming it and removing "apk" from it anyway. @Davey126?
Click to expand...
Click to collapse
Should not be a problem provided you remember where it resides should you wish to enable OTA updates at a later time. Note there are other system files containing the characters "OTA" that should not be moved or renamed.
Davey126 said:
Should not be a problem provided you remember where it resides should you wish to enable OTA updates at a later time. Note there are other system files containing the characters "OTA" that should not be moved or renamed.
Click to expand...
Click to collapse
Good to know. Yeah, it was just the one file. Thanks so much for your help.
Took delivery of a couple of HDX tablets today. I got a chance to try a "Replace Kingroot with SuperSU script" I modded for the HDX. The script was taken from supertools which also used chainfires root.sh script.
Anyway it seems to have worked perfect, I've two HDX on 4.5.5.2 with SuperSU on them instead of Kingroot 4.8.2 which was used in the script. That kingroot version rooted on the 2nd attempt on both tablets, both factory reset and unregistered.
Files attached feel free to modify as required.
any ideas
so im rooted , ota are turned off, and safe strap is installed and here comes the but... it lets me install recovery but when i hit reboot to recovery it reboots and then powers up like normall?? it doesnt let me go into a recovery mode??? o and 4.5.5.2 is what is running
thumper_ss said:
so im rooted , ota are turned off, and safe strap is installed and here comes the but... it lets me install recovery but when i hit reboot to recovery it reboots and then powers up like normall?? it doesnt let me go into a recovery mode??? o and 4.5.5.2 is what is running
Click to expand...
Click to collapse
Please don't cross post; responded in other thread.

Categories

Resources