Related
A basic question: is "unlocking bootloader" the same as "rooting"?
This is in reference to the HTC's promise to make their bootloaders unlockable throgh a web tool.
What exactly does "to unlock the bootloader" mean? Is it the same thing that we also know as "rooting"? Is it just a first step towards "rooting"? Or is it something totally different?
Unlocking the bootloader is NOT the same as rooting. Unlocking the bootloader is turning off/removing the security flag of the bootloader. When the bootloader is locked, the security flag is on (S-ON) which prevents rooting easily and flashing of roms not made by the company (who made the device). When the bootloader is unlocked (S-OFF), you will be able to root easier, flash whatever you want,etc. Also, having S-OFF gives rooted devices much more access and freedom to many things. Example: some apps only require root, but others which do many more things require root + S-OFF.
Oh, I see. Thank you for the answer. So, we are talking about what is usually informally referred to as "S-OFF".
TheKorbenDallas said:
Oh, I see. Thank you for the answer. So, we are talking about what is usually informally referred to as "S-OFF".
Click to expand...
Click to collapse
Yes. Exactly.
Actually, this time the security flag was stored in the radio, not the bootloader (for the Evo 3D/Sensation), but the explanation was pretty much correct.
Root is a user/permission that grants a user or application total control over a system. It's a Unix/Linux term. The equivalent on a PC would be Administrator (or really System, but to keep it simple, Administrator). For Android, all you need to think of it as is the Superuser app and the "su" binary (a binary is an executable or command in the form of a file). Superuser can be downloaded from the Market, which is no problem. But it's useless without the "su" binary (file), which needs to be flashed/stored in the /system partition of the phone.
Well if you can't write to /system without root, and you can't get root without writing to /system, you have a bit of a problem. You see, most phones can be easily rooted with apps like Gingerbreak or SuperOneClickRoot because their bootloaders aren't locked. But HTC likes to add a second layer of protection: S-ON.
See this picture? It's a picture of the bootloader on the Evo 3D. It was pretty much the same exact thing for the Evo 4G, and is the same for the Sensation. In the top right corner, you see how it says S-ON? It stands for Security ON. S-ON is a flag in the bootloader (or in this case, radio) which disallows any non-system applications from touching the /system partition. What AlpharevX and TeamWin did was develop a tool which, through an exploit, allowed the flag to be changed to S-OFF, thereby allowing us to install a custom recovery (ClockworkMod or twrp), which now allows us to flash things (like the zip to install Superuser, and the su binary).
One last thing I left out is that most apps that require root also need busybox, which can be installed through the app from the Market, "BusyBox Installer", but it's useless without root.
Hope that helps!
Product F(RED) said:
You see, most phones can be easily rooted with apps like Gingerbread...
Click to expand...
Click to collapse
One minor spelling error (Which can confuse someone who's just learning). It's not Gingerbread, it's Gingerbreak.
Theonew said:
One minor spelling error (Which can confuse someone who's just learning). It's not Gingerbread, it's Gingerbreak.
Click to expand...
Click to collapse
Whoops. Thanks for that!
I just want to know the difference
Sent from my Wildfire S using XDA
There is no difference. If you unlock bootloader you can gain root.
Sent from my Wildfire S using XDA
SanderTheNinja said:
There is no difference. If you unlock bootloader you can gain root.
Sent from my Wildfire S using XDA
Click to expand...
Click to collapse
Of course there is a difference. Rooting lets you have complete admin rights on your phone, eg access to write files to the system partition for example or delete all the files. Or uninstall system apps.
Unlocking lets you flash an entire new rom or a custom recovery.
OP - There is plenty of info elsewhere, don't be lazy, just do some reading
with an unlocked bootloader, then you are able to root your phone and install custom roms and overclock and root stuff.
an unlocked bootloader is something you must do before having full access to your phone
scott_doyland said:
Of course there is a difference. Rooting lets you have complete admin rights on your phone, eg access to write files to the system partition for example or delete all the files. Or uninstall system apps.
Unlocking lets you flash an entire new rom or a custom recovery.
OP - There is plenty of info elsewhere, don't be lazy, just do some reading
Click to expand...
Click to collapse
I mean, you can only get root if you unlock your bootloader.
Sent from my Wildfire S using XDA
Root
Rooting a device is a method to gain full access to the operating system. With root you can do all the administrative stuff, write to locations normally restricted to the system and customize your device deeper.
Root enhances your privileges and you are able to change almost anything inside of your rom.
The rooting, however, affects ONLY your operating system (Android)
Unlocked Bootloader
In most devices, the Bootloader is the instance that calls the operating system (Android) and manages direct access to the device's partitions. Having an unlocked bootloader enables you to flash custom roms, custom kernels, recoveries and so on.
Bootloader and Rooting Teamplay
Often it is the case, and so, too in our devices, that a locked bootloader also locks write access to several partitions like the system partition. This is the reason why rooting is not able without unlocked bootloader. Rooting needs write access to the system partition (for storing the superuser binary and the superuser app)
Without unlocked bootloader, only a temporary half-root can be achieved.
Thanks alot guys
Sent from my Wildfire S using XDA
How to unlock bootloader ,but the way that I can lock it again
prdonja said:
How to unlock bootloader ,but the way that I can lock it again
Click to expand...
Click to collapse
Do some research. There are hundreds of posts on this topic.
scott_doyland said:
Of course there is a difference. Rooting lets you have complete admin rights on your phone, eg access to write files to the system partition for example or delete all the files. Or uninstall system apps.
Unlocking lets you flash an entire new rom or a custom recovery.
OP - There is plenty of info elsewhere, don't be lazy, just do some reading
Click to expand...
Click to collapse
19 months after the question was asked, i just happened to be wanting to answer the same question for myself, so I searched and found this thread...
I am happy he asked the question, as it was the first answer I saw in google search... so maybe he could also have done a search 19 months ago, but his question was useful to me, and your response seemed rude and unnecessary. You never know who may benefit from a little generosity.
Mark.
scott_doyland said:
Do some research. There are hundreds of posts on this topic.
Click to expand...
Click to collapse
I know that you're not rude (even though you sounded so). You replied what was correct and appropriate.
But my research for the question in question (pun unintended) on google pointed me straight to this very thread.
So, it would be greater if someone had posted some more good links besides their rude looking remark (again, not rude, but just looking so).
theq86 said:
Root
Rooting a device is a method to gain full access to the operating system. With root you can do all the administrative stuff, write to locations normally restricted to the system and customize your device deeper.
Root enhances your privileges and you are able to change almost anything inside of your rom.
The rooting, however, affects ONLY your operating system (Android)
Unlocked Bootloader
In most devices, the Bootloader is the instance that calls the operating system (Android) and manages direct access to the device's partitions. Having an unlocked bootloader enables you to flash custom roms, custom kernels, recoveries and so on.
Bootloader and Rooting Teamplay
Often it is the case, and so, too in our devices, that a locked bootloader also locks write access to several partitions like the system partition. This is the reason why rooting is not able without unlocked bootloader. Rooting needs write access to the system partition (for storing the superuser binary and the superuser app)
Without unlocked bootloader, only a temporary half-root can be achieved.
Click to expand...
Click to collapse
Thanks for this useful info
I agree. It is the autumn of 2014, and I've been reading webpages until my eyes are bleary. This is the 1st thread that actually explains how the two concepts relate rather than descending into buttonology. I think the OP's question hits the nail on the head (well, one of them at least) and he doesn't need to be treated in a demeaning manner.
Wow, 1 year after last post, I thanked he asked this question! Was thinking as same as u, loll
fredphoesh said:
19 months after the question was asked, i just happened to be wanting to answer the same question for myself, so I searched and found this thread...
I am happy he asked the question, as it was the first answer I saw in google search... so maybe he could also have done a search 19 months ago, but his question was useful to me, and your response seemed rude and unnecessary. You never know who may benefit from a little generosity.
Mark.
Click to expand...
Click to collapse
Root vs bootloader
If i have an unlocked bootloader can i install apps that require root. Will they still work even though im not rooted?
Deogracias said:
If i have an unlocked bootloader can i install apps that require root. Will they still work even though im not rooted?
Click to expand...
Click to collapse
I'm not an expert, but here's my understanding from months of reading up on this: Unlocking the bootloader lets you install a program known as Recovery, which is another program that lets you install operating systems, e.g., stock Android, CyanogenMod. Whether you have root or not is determined by settings made after the operating system is installed. So unlocking a bootloader is different from root. You can have either one without the other. However, I am also left with the impression that software that helps you unlock the bootloader also give you root (and perhaps vice-versa). This dual functionality is designed into the software, but they are separate things which don't have to both happen.
I just reviewed my answer and realized that it doesn't really address the quoted question very directly. Unfortunately, there is no "delete" function. So hopefully, it helps a bit. As further info, I unlocked bootloader, changed the Recovery, and replaced the native Android OS from Koodo with CyanogenMode. However, I did not root. Hopefully, someone else can chime in with further experience.
I've been wondering about this for years, as well. I don't feel confident doing things to my phone that I don't understand. I'm sure I'll never have a thorough understanding, as I'm not a programmer, but even a rough one would suffice. This is the same reason why I will only attempt certain operations on my car -- if I muck it up, I'm boned.
I rooted my phone (or maybe unlocked the bootloader?) a couple years ago, and never got around to doing anything else with it, because I couldn't figure out how to "do a recovery" (still don't know what that means, exactly). Or maybe I unlocked the bootloader, and never rooted it? I'm still confused. I see LOADS of folks who throw the terms around, whom I suspect, actually have no clue. I have a Verizon S4 MDK 4.2.2, and I just now finished the process -_- Better late than never? Now, I'm trying to decide if it's worth the headache, and possible risk, of installing custom ROMs, etc. Also, I know my phone is "SO old!!' and blah-blah-blah. At least if I screw things up now, I can get a new phone with a new contract, etc.
I really wish Verizon weren't such dirtbags about the locked bootloader thing.
No
SanderTheNinja said:
There is no difference. If you unlock bootloader you can gain root.
Sent from my Wildfire S using XDA
Click to expand...
Click to collapse
Heee is full difference between rooting and unlocking bootloader
Rooting - Administrative access to the entire file system including the ability to change system files such as installing system-wide ad-blocker by modifying the host file on your device, or uninstalling system apps, such as bloatware that comes pre-installed on your device. Without root, one can only see files in root directory instead of editing them. Some alps and mods only work with root.
Unlocking bootloader- To understand this term, one need to know the meaning of bootloader first. In simple terms, bootloader is like a person which checks many functions at the time of boot. It's on of the most important part and boots the first. Unlocking bootloader means asking that person to give us rights to do some modifications in our device like flashing custom recovery, rom etc.
prdonja said:
How to unlock bootloader ,but the way that I can lock it again
Click to expand...
Click to collapse
ADB
Hey guys, I recently got my Gnex(internation version from expansys) last week, but I'm a little bit on the fence when it comes to rooting as this is my first Android device. What are the benefits? I mean, I know that you guys get a ton of options with the variety of roms available to download/install, but I'm liking the stock ics that came with the device. If somebody cold convince on on doing it, then I'd be grateful. My baseband is XXLA2, is that the recommended one if I'm living in the US?
The ability to control your phone like you should. However being a really new person to android I wouldn't recommend you do it right away. Maybe browse the forum and learn somethings. Knowledge is power.
Sent From My Sprint Galaxy Nexus
Root gives you admin access to your phone. Definitely you should root, even if you want to stay on stock factory rom.
RogerPodacter said:
Root gives you admin access to your phone. Definitely you should root, even if you want to stay on stock factory rom.
Click to expand...
Click to collapse
Only if he sees the benefits for himself. There's absolutely no reason for him to root if he doesn't understand what it does or how it will help/hurt him.
As mentioned previously, root access is admin access to the phone. Some benefits of it include being able to use the Adfree app to block advertisements in apps or Titanium Backup to backup apps the data associated with them. I'd take the time to get to know the phone and operating system first and then decide if you have a need for apps that require root access.
Off the top of my head:
-Fastest updates
-Ad removal
-Firewall
-True call blocking
-Lightflow
-Theming
-Backups (titanium, nandroid)
-Custom ROMs and all the millions of features they have (you could write pages and pages about this alone)
-Custom kernels (better battery+performance, touch wake, etc)
Since you have the Galaxy Nexus(a dev phone) as opposed to another locked-down phone, rooting is very, very easy. Unless you do something totally retarded you'll be safe. Just don't use toolkits -- do it manually.
fredryk said:
-Fastest updates
-Lightflow
-Backups (titanium, nandroid)
Click to expand...
Click to collapse
-You don't need to root to get fast updates. You can flash update files the day they come out via fastboot w/ an unlocked bootloader.
-Lightflow also works w/o root.
-You can do backups with ADB also.
martonikaj said:
-You don't need to root to get fast updates. You can flash update files the day they come out via fastboot w/ an unlocked bootloader.
-Lightflow also works w/o root.
-You can do backups with ADB also.
Click to expand...
Click to collapse
I guess I was thinking of "root" being synonymous with unlocked bootloader. My old phone required root...still need root for TB.
fredryk said:
I guess I was thinking of "root" being synonymous with unlocked bootloader. My old phone required root...still need root for TB.
Click to expand...
Click to collapse
Yes this is usually the case with other phones. With the Nexus, its extremely easy to unlock the bootloader and not root. I'd recommend unlocking the bootloader on this phone, but I'm not so quick to recommend rooting. People on XDA or too quick to recommend rooting to people who have absolutely no idea what it is and end up bricking their device.
martonikaj said:
Yes this is usually the case with other phones. With the Nexus, its extremely easy to unlock the bootloader and not root. I'd recommend unlocking the bootloader on this phone, but I'm not so quick to recommend rooting. People on XDA or too quick to recommend rooting to people who have absolutely no idea what it is and end up bricking their device.
Click to expand...
Click to collapse
+1. Exactly.
You do not need root to flash custom ROMs, get updates, etc. if you have an unlocked bootloader. I totally agree with martonikaj: you SHOULD unlock your bootloader, but you shouldn't mess around with root until you know what root is and need it.
Sent from my Galaxy Nexus using Tapatalk 2
I would unlock the bootloader immediately if you think you'll ever want to root the phone. Reason why is that you can unlock the bootloader easily with a single command, but it will wipe your phone, and there's no good way to do a real backup without rooting it. Better to do it now, before you have everything set up the way you want it and all of your apps installed.
For rooting, I agree that you shouldn't do it until you have a better idea what it is and why you want to do it.
I've been back and forth between root and non-root (always unlocked bootloader) and other than a few things already mentioned (Ad-free, Titanium Backup) I'm the type that can live with Stock ICS. I do flash custom ROM's once in a while to see if I enjoy them but I've always come back to Stock (for now) because of random reboot issues.
I'm reading this thread while on my way to root my phone (virgin like the guy who started this thread) I've been reading about rooting for a year, what's the difference between root and unlocked bootloader
Sent from my SPH-D710 using xda app-developers app
kennwoodkenn said:
I'm reading this thread while on my way to root my phone (virgin like the guy who started this thread) I've been reading about rooting for a year, what's the difference between root and unlocked bootloader
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
From someone who knows just enough to get by....
Unlocking your bootloader allows you to flash custom recovery/ROM/Stock version/etc. You don't need root for this.
Root allows you full access to the phone with superuser permissions and install some apps that require full access to system files.
kennwoodkenn said:
I'm reading this thread while on my way to root my phone (virgin like the guy who started this thread) I've been reading about rooting for a year, what's the difference between root and unlocked bootloader
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
You couldn't have been doing a lot of good reading if you've been reading for a year and don't know the difference. But don't feel bad -- there are lots of senior members that use the terms interchangeably which is completely and utterly wrong.
Root means having root user access to the file system. Kinda like being the administrator user on Windows machines. You can access all the files and modify and delete anything. The process consists of placing two files on the /system partition of your device. The problems with this process, is finding a way to make /system write-able to place those two files there (as it is read-only by default when you are booted in Android). Chicken or the egg -- You need root to get root.
Think of the bootloader as the BIOS of a computer. It loads up before the operating system, and allows you to perform certain basic tasks. In our case, the bootloader allows you to flash images to your device, and to boot images on your devices (without actually writing them to the NAND). Unlocking the bootloader removes the security on the bootloader, which means that the bootloader no longer verifies the signature of images you are trying to flash or boot and, thus, allows you to flash or boot non-Google signed images.
Now, are rooting and unlocking your bootloader related? Well, to a certain extent yes. If you unlock your bootloader, you can easily obtain root access. This is true because you can flash or boot a custom recovery, which will allow you to write files to /system without being booted into Android. So, with an unlocked bootloader, "rooting" becomes trivial. However, there are other ways to root -- by using exploits. GNex Android builds up to ICL53F can be rooted by mempodroid (see link 4 in my signature), but to-date, an exploit has not been found for IMM76D and higher.
For the epic touch it looks pretty easy to root in Odin mode it seems to be a way to go I know I want root for all the reasons above
My process
Root with ODIN
Install CWM
And like what I see in the AOKP ROM
I HAVE NOT FORGOTTEN TO BACKUP
Am I on the right track
Sent from my SPH-D710 using xda app-developers app
kennwoodkenn said:
For the epic touch it looks pretty easy to root in Odin mode it seems to be a way to go I know I want root for all the reasons above
My process
Root with ODIN
Install CWM
And like what I see in the AOKP ROM
I HAVE NOT FORGOTTEN TO BACKUP
Am I on the right track
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Why don't you ask in the Epic Touch forum??
Rooting your gnex doesn't need to be seen as taking a dive off a cliff while blindfolded. This is a myth perpetuated by people who have either never rooted their devices or did something retarded and bricked it. It's easy, painless, and uncomplicated if you follow the instructions. If you can take advantage of the ad removal, backups, call blocking, etc with ease....why not do it?
Use this: http://forum.xda-developers.com/showthread.php?t=1529058
Thanks for all your help!
I'll proceed to unlock the bootloader, but will remain on stock for a while until I get the hang of it and want to expand my options.
In trying to root my phone, I have discovered that full r/w access is somewhat required... and that it is also something I do not have. Is there a way to get this without root, or am I going to have to try to find a way around it?
Omegaclawe said:
In trying to root my phone, I have discovered that full r/w access is somewhat required... and that it is also something I do not have. Is there a way to get this without root, or am I going to have to try to find a way around it?
Click to expand...
Click to collapse
It sounds to me like you don't know what root is, let alone know how to get full read /write access. But if you want full read /write access first thing you do is unlock your bootloader, then you get urself a recovery image, then you make a backup, and then you can root. Keep in mind that you will NEVER find a way around having to root in order to get full read / write access to your phone.
In order to get full read / write access to your phone, you have to root it first.
Sent from my XT907 using Tapatalk 2
sniperkill said:
It sounds to me like you don't know what root is, let alone know how to get full read /write access. But if you want full read /write access first thing you do is unlock your bootloader, then you get urself a recovery image, then you make a backup, and then you can root. Keep in mind that you will NEVER find a way around having to root in order to get full read / write access to your phone.
In order to get full read / write access to your phone, you have to root it first.
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
You really don't have to be so condescending. I am aware of what root is, and that it could easily get me full R/w access. It just sounds kinda useless to have root methods that require something you can only get with root, so I assumed either there was a way to get it over ADB that initial Google results didn't show, or the "unlock on any firmware" part was clearly false advertising because full r/w straight out of the box is typically a huge security vulnerability.
It would also appear that these root methods are for phones with locked bootloaders, since with an unlocked bootloader, you can get root without having to muck around with exploits.
So, to clarify, the root exploits are not working because I do not have write access to the locations they require files to be written to, and chmod is not allowed on those locations. I'm pretty sure I only need write access to /data/local/12m/, actually. If that cannot be done, I may have to attempt a more dangerous approach.
Omegaclawe said:
So, to clarify, the root exploits are not working because I do not have write access to the locations they require files to be written to, and chmod is not allowed on those locations. I'm pretty sure I only need write access to /data/local/12m/, actually. If that cannot be done, I may have to attempt a more dangerous approach.
Click to expand...
Click to collapse
Try this thread - Root Achieved
Enables you to mount the system as read/write via ADB
Omegaclawe said:
You really don't have to be so condescending. I am aware of what root is, and that it could easily get me full R/w access. It just sounds kinda useless to have root methods that require something you can only get with root, so I assumed either there was a way to get it over ADB that initial Google results didn't show, or the "unlock on any firmware" part was clearly false advertising because full r/w straight out of the box is typically a huge security vulnerability.
It would also appear that these root methods are for phones with locked bootloaders, since with an unlocked bootloader, you can get root without having to muck around with exploits.
So, to clarify, the root exploits are not working because I do not have write access to the locations they require files to be written to, and chmod is not allowed on those locations. I'm pretty sure I only need write access to /data/local/12m/, actually. If that cannot be done, I may have to attempt a more dangerous approach.
Click to expand...
Click to collapse
Well I apologize if you think that I was talking down to you. I didn't mean to sound like a prick, lol. As for the unlocking of bootloader, and no phone comes with an unlocked bootloader, it's just up to the manufacturer to decide on whether or not the bootloader is unlockable. And they leave it up to the user to unlock the bootloader themselves.
Sent from my XT907 using Tapatalk 2
I know this is not the right place to ask. I need to know. Do we have developers working on root for this model?
Sent from my SAMSUNG-SM-N920A using Tapatalk
Yes and No...still having booloader issues!
And yes wrong place...this post belongs in Q&A!
We need firmware release so we can restore after. Tell then no one really wants to try because just messing with options in recovery disables the phone.
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=N920
Will firmware release happen for our model?
Sent from my SAMSUNG-SM-N920A using Tapatalk
amwbt said:
Will firmware release happen for our model?
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
AT&T has to because it's open source. They however can keep it for like 6 months to a year or something. With the cracks down on root AT&T and Verizon it might be a long wait with the locked bootloader saidly and we need a custom kernel to get root and we can't flash kernels with locked bootloader. Just watch the website I linked and when we get our firmware then we can possibly expect root and someone to try and unlock the bootloader. I'm not sure if there is a "anti root" in the AT&T phone because I'm not going to lose my phone. I already had to return for warranty due to defective screen and spen. Look at how long it takes the new iPhone software to get jailbroken.
TechNyne66 said:
AT&T has to because it's open source. They however can keep it for like 6 months to a year or something. With the cracks down on root AT&T and Verizon it might be a long wait with the locked bootloader saidly and we need a custom kernel to get root and we can't flash kernels with locked bootloader. Just watch the website I linked and when we get our firmware then we can possibly expect root and someone to try and unlock the bootloader. I'm not sure if there is a "anti root" in the AT&T phone because I'm not going to lose my phone. I already had to return for warranty due to defective screen and spen. Look at how long it takes the new iPhone software to get jailbroken.
Click to expand...
Click to collapse
Needing a custom kernel for root is actually a false statement. A custom kernel is not needed to get root for this device. The AT&T S6 for example got root without the bootloader being unlocked or a custom kernel.
Which leads me to the bootloader being unlocked. There is probably a 100% chance that we don't get an unlocked bootloader for this device. It's extremely difficult and there hasn't been an AT&T device in a very long time that has had it unlocked.
And since we would need that for a custom kernel and aosp roms, those things will probably never happen unfortunately.
The very best we can hope for is root and a recovery like FlashFire like the S6 got. And even then we would be limited to only Touchwiz roms.
We will more then likely need custom kernel with permissive set. AT&T and Verizon are saying there's anti root and that would be in the kernel and would need to be killed. If we do obtain root with stock kernel the phone is said to not boot.
http://www.idigitaltimes.com/samsun...d-features-att-and-verizon-models-wont-468357
It is one of those things where they're will be zero development until some Uber-geek cracks the bootloader issue. Then there will be 20 devices or more that will be released from developer quarantine...
Sent from my SAMSUNG-SM-N920A using Tapatalk
AOSP will never happen without unlocked bootloader.
I do have hope for a root such as Ping Pong. Honestly, with how clean these phones ship nowadays, all I want root for is to replace emojis with iOS style throughout the system so I can grasp more context from my text messages lol. Also, LCD Density change would be nice too.
Is there anybody working on root for this phone?
Sent from my SAMSUNG-SM-N920A
Have no need for root either except for xposed. Only want root for like 4 xposed modules.. Otherwise this device is nearly perfect
I need to change muy dpis
Enviado desde mi GT-N7100 usando Tapatalk 2
Planning on getting this phone today..
I have rooted and installed ROMs on almost every phone I have owned and really hope that eventually a safe way of rooting is obtained.
jellybear456 said:
a safe way of rooting
Click to expand...
Click to collapse
heh. I know what you mean, but I'm grumpy this morning so I'm going to pick this apart anyway.
If root is found on a boot loader locked device, it's usually via an exploit... Basically, most rooting mechanisms are similar to computer viruses. Sure, most of them are controlled viruses, but they exploit and expose security holes that something malicious could use just as easily. Instead of copying a "su" binary, that same exploit could install something that uploads your private data somewhere, or monitors the android keypad entry when you type credit card numbers, etc.
Don't get me wrong... I don't think that most of the root exploits here on XDA are doing that... but any time you use one, you should seriously consider that it might be. It would only take a single mishap to completely destroy your life outside of XDA.
To that end, you should REALLY pay attention to the entire filesystem both before and after an exploit is applied. See what files, if any, are modified and/or added. If an exploit adds a "su" binary (which most of them do), try to replace that "su" binary with one from a trusted source BEFORE you put personal data on your phone. Never "root" a device that has any data on it.
Remember that no matter what precautions you might be taking, a rooted device has a lower level of security than one that isn't. Not only have you added a "simple" root mechanism, but you likely had to defeat the security mechanisms that are part of the security enhanced linux kernel. (There are exceptions to this, of course, but I've never seen the exceptions here on XDA or any other sites that aren't focused on security.)
If this message made you a bit more paranoid, that's a good thing. You should be paranoid about it. I'm not saying not to do it, and I'm certainly not saying that XDA is overflowing with malicious code...
garyd9 said:
heh. I know what you mean, but I'm grumpy this morning so I'm going to pick this apart anyway.
If root is found on a boot loader locked device, it's usually via an exploit... Basically, most rooting mechanisms are similar to computer viruses. Sure, most of them are controlled viruses, but they exploit and expose security holes that something malicious could use just as easily. Instead of copying a "su" binary, that same exploit could install something that uploads your private data somewhere, or monitors the android keypad entry when you type credit card numbers, etc.
Don't get me wrong... I don't think that most of the root exploits here on XDA are doing that... but any time you use one, you should seriously consider that it might be. It would only take a single mishap to completely destroy your life outside of XDA.
To that end, you should REALLY pay attention to the entire filesystem both before and after an exploit is applied. See what files, if any, are modified and/or added. If an exploit adds a "su" binary (which most of them do), try to replace that "su" binary with one from a trusted source BEFORE you put personal data on your phone. Never "root" a device that has any data on it.
Remember that no matter what precautions you might be taking, a rooted device has a lower level of security than one that isn't. Not only have you added a "simple" root mechanism, but you likely had to defeat the security mechanisms that are part of the security enhanced linux kernel. (There are exceptions to this, of course, but I've never seen the exceptions here on XDA or any other sites that aren't focused on security.)
If this message made you a bit more paranoid, that's a good thing. You should be paranoid about it. I'm not saying not to do it, and I'm certainly not saying that XDA is overflowing with malicious code...
Click to expand...
Click to collapse
Yes, I do realize that rooting a device often does take advantage of any security holes found, and I also realize that there is no, in the literal sense, "safe" way to root a phone considering it is exploiting security flaws. Personally, I have never had such an issue of having something malicious on my phone after rooting(at least not to my knowledge)
By "safe" I meant a way to root without having the phone locked down and unable to boot. I am not worried about AOSP ROMs as I am completely content with using an AOSP themed launcher. But I would love to be able to uninstall bloat, ad block, greenify/amplify etc.
But I do appreciate your input on the subject as I have never put much thought into the security of the phone before and after root, or replacing the su binary with one from a trusted source or checking if it is from a trusted source.
It is also great to see someone else on the forums from Pittsburgh:highfive:
I have n920a. Please share the path to rooting this phone.
Cuando se podra rootear el dispositivo Samsung Galaxy Note 5 N920A?
Possible way to root?
I don't know if this would work. But what about flashing one of those new root.tar eng kernal then manually pushing the survey binary and super apk into phone then reflash stock kernal. I'm just intermediate at all this stuff. So idk if it would work or if this is stupid.
vahalaru said:
I don't know if this would work. But what about flashing one of those new root.tar eng kernal then manually pushing the survey binary and super apk into phone then reflash stock kernal. I'm just intermediate at all this stuff. So idk if it would work or if this is stupid.
Click to expand...
Click to collapse
It's possible, after flashing the eng-boot do this:
adb shell mount -o rw,remount /system
Then manually push SuperSU to system, or install King/Kingo Root
Just be careful this is still a tethered root.
I have posted a teathered root process that Michael31 found from the AT&T s6 section. It works and you can get reboots with hoot booting. The locked bootloader causing issues with the kernel needed add commands on hard boot to change to permissive mode. Few of us have tried to fix this issue and haven't found anyway yet.