[SOLVED] What is the Safest way to ROOT an android phone?
Linux - MobileThis forum is for the discussion of all topics relating to Mobile Linux. This includes Android, Tizen, Sailfish OS, Replicant, Ubuntu Touch, webOS, and other similar projects and products.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
We are using some Android phone in a closed network (no Internet access)
and we want these phone to be able to solve DNS query.
But the thing is, they try to query 8.8.8.8 google DNS not our internal DNS server.
Althrough it is distributed via DHCP, the android phone still try to query the Google DNS.
After some research it seemd that there is no way to specify DNS manually without rooting the device.
So here is my question: How do I root my device in a safe way? (That mean, without using KingRoot or any other untrusted software. As we don't really know what these softwares do)
and how do I secure my device after I rooted it? (as "I might be wrong here" there will be no password to prevent users to run a program as root)
you dont mention the which device (every manufacturer/model/firmware version require a different root exploit).
the only devices that are securely root-able would be nexuses since google orders them to be able to be rooted. all other manufactures make it difficult to r00t requiring l33t h4x0rz to provide a solution.
Thanks for your reply.
These phone will be use in a workshop as internal telephony system.
Therefore we cannot afford to use expensive phone as there is a big chances that the phone we will use will be not handeled with care.
Anyway here are the phone spec:
Device-info:
OS Version: 3.4.5-1588582-user(S7390GXXUAOB1)
Android: 4.1.2
Device: kylevess
Model (and Product): GT-S7390G (kylevessxw)
Manufacture: samsung
Display: JZO54K.S7390GXXUAOB1
Brand: samsung
NetWorkType: Wifi
Soooo ...
You want to rely on the largesse of people that go out of their way to provide a custom ROM (in their own time, unpaid), but you don't trust them.
Interesting attitude.
Rooting relies on finding an exploit - that means (smart) hackers are involved. To me, that means you have to be prepared to go all-in, or not at all.
It also relies on some-one bothering to do the leg-work - and generally that means only for popular models. I just looked at my notes for trying to root a Samsung GT-S6010. Several days of frustration and none of the root kits I tried was successful. I also bricked the device and had to use KIES to reload the initial firmware (twice, as the first had no effect).
if it was a closed network 8.8.8.8 would be unreachable. From the other hand dhcp will give dns address, I do not really understand why those devices want to use google. For example it works at home, in my home/local network. Probably I misunderstood something but that should not be an issue.
Soooo ...
You want to rely on the largesse of people that go out of their way to provide a custom ROM (in their own time, unpaid), but you don't trust them.
Interesting attitude.
Please don't get me wrong, I know what it takes to code at our own expense. (I did contribute to Nagios, PNP4Nagios and now I took over the LETS-Software project, all of these program are open source, so if anyone don't trust these program they can dig into them and check what it does)
I'm just saying that, this program is not open source, so, we can't be sure what it does exactly. That's all.
Now if you tell me it is safe, I would gladly trust you.
But how can you be sure?
Quote:
Rooting relies on finding an exploit - that means (smart) hackers are involved. To me, that means you have to be prepared to go all-in
I'm ready, but the thing is that I never touch an android device before few weeks back.
Which mean I know nothing about it(At least nothing compare to what you probably know about these devices)
But one thing is sure, is that I'm exited about it
@pan64
Quote:
if it was a closed network 8.8.8.8 would be unreachable. From the other hand dhcp will give dns address, I do not really understand why those devices want to use google. For example it works at home, in my home/local network. Probably I misunderstood something but that should not be an issue.
We want to setup our mail server on it and we need to resolve some internal address.
But to keep this post clean (with only one issue), we will forget about that DNS issue and keep only the rooting issue.
Hm, I bought rooted devices too, and I rooted some others. At first you need to have some practice, need to understand how can you safely make a brick. Probably it costs a few phones. The safest way is to know exactly what are you trying to do (and obviously it depends on the device you have - not only on the brand, but on the real hardware and os).
It appears I did indeed mis-interpret your initial post.
Being able to read the code is no protection against possible exposures. Heartbleed recently proved that.
You may convince yourself that there is no obvious deliberate "back door", but even that is very questionable.
Has the inability to examine all the code stopped you buying phones and/or computers ?. What about smart TVs ... ?
As for resources, get searching - in my case a couple of days searching and a couple of further days reading was sufficient to dive in. Likely you'll find yourself spending quite a bit of time reading forum.xda-developers.com
if it was a closed network 8.8.8.8 would be unreachable. From the other hand dhcp will give dns address, I do not really understand why those devices want to use google. For example it works at home, in my home/local network. Probably I misunderstood something but that should not be an issue.
Distribution: Kubuntu 20.04 LTS / Windows 10 21H2 (paused forever) / Windows 2016 Server
Posts: 23
Rep:
Shouldn't need to root the phone to change dns on your wireless network. DHCP will deliver whatever dns you have configured it to deliver..not googles or the service providers.
For example: I have a router that serves out 8.8.8.8 for wireless connections. When I look at my phone it says my dns for the home wireless connection is 8.8.8.8, if I change my dhcp server to send 8.8.4.4 to my wireless clients guess what? Yep..you guessed it my dns is now 8.8.4.4
I also have my own dns server (yah, yah I know...it's a home network..but MY dns NEVER goes down,...not so for my ISP's or even google..well, google doesn't go down but it does get slow..mine does not get slow...I am digressing..yet again...sigh...)
So, I can manually edit the home wireless connection directly from my phone, and I do, and change it o my internal dns server, which is authoritative.
So, even if you are running your own LTE/4G service out to clients/employee's or whatever...the phone should pickup whatever DNS you DHCP server sends to it right?
I'm not a programmer, only a lowly technician so what do I know:-)
oh.... and towelroot (search in google) SHOULD work on any phone below 5.0 (lollipop), which includes yours.
I supposed you could save the default firmware and configs using ADB or whatever, then root it using towelroot and compare the difference afterwards? I don't know how hard that would be but for a programmer it should be easy, peasy.
first you should make sure your phone is suitable for rooting. before rooting, backing up Android phone is necessary. lastly, use a good toll to help root your phone can be helpful.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.