Hello XDA,
as Zimperium demonstrated, you are able to get root shell via stagefright exploit. So wouldn't it be really easy to create a root tool that works on almost all devices? Like "its not a bug, its a feature"
Greets Xorg
TheXorg said:
Hello XDA,
as Zimperium demonstrated, you are able to get root shell via stagefright exploit. So wouldn't it be really easy to create a root tool that works on almost all devices? Like "its not a bug, its a feature"
Greets Xorg
Click to expand...
Click to collapse
Sounds legit. If it were only that easy
Sent from my Nexus 5
TheXorg said:
Hello XDA,
as Zimperium demonstrated, you are able to get root shell via stagefright exploit. So wouldn't it be really easy to create a root tool that works on almost all devices? Like "its not a bug, its a feature"
Greets Xorg
Click to expand...
Click to collapse
I just thought the same if I heard about stagefright exploit.
But I read too, that the lib-stagefright is not the same on every android os. Some companys change the code a little bit or use another environment.
But I want to ask again inname of the ts:
Is it possible to root devices with help of the stagefright exploit?
Greeings by Idijt
I_did_it_just_tmrrow said:
Is it possible to root devices with help of the stagefright exploit?
Click to expand...
Click to collapse
If you can get root (as the OP says), you have rooted it
AlvaroGzP said:
If you can get root (as the OP says), you have rooted it
Click to expand...
Click to collapse
They "only" got root shell, SELinux may prevent you from pushing files(?)
It would be lovely if it's used to root a phone like the SM-G900H (Exynos S5). Nothing so far can root it without tripping knox flag.
TheXorg said:
They "only" got root shell, SELinux may prevent you from pushing files(?)
Click to expand...
Click to collapse
SELinux is enforced for root users? In theory, root has total control of the system. For example, file permissions do not apply to root.
AlvaroGzP said:
SELinux is enforced for root users? In theory, root has total control of the system. For example, file permissions do not apply to root.
Click to expand...
Click to collapse
Not completely true. In order to change file permissions you need root in order to do it
Sent from my Nexus 5
ShapesBlue said:
Not completely true. In order to change file permissions you need root in order to do it
Sent from my Nexus 5
Click to expand...
Click to collapse
Yes, but what I mean is that, without changing permissions, root can write to unwritable files and read unreadable files, effectively bypassing file permissions. Also, root can change permissions for files not owned by him, which normal users cannot.
AlvaroGzP said:
Yes, but what I mean is that, without changing permissions, root can write to unwritable files and read unreadable files, effectively bypassing file permissions. Also, root can change permissions for files not owned by him, which normal users cannot.
Click to expand...
Click to collapse
That's very true. But as you know that can only be achieved with root. I personally have the Stagefright fix and at this point don't have to worry about it thankfully
Sent from my Nexus 5
Do t worry about this really. It is a bunch of fear mongering mostly. Also even the patch from Google as been proven doesn't fix it completely. People that release these types of things have alternative motives.
Related
I used to work with WM 5 & 6 phones, had plenty of them and enjoyed them all until I discovered the HTC Magic. What a giant leap forward!! Especially when using Google Apps as we do. I am however a bit reluctant to root the magic as it doesn’t seem like a walk in the park. I really miss being able to backup SMS messages and all the other apps that only run on rooted devices.
So my question is if the HERO is a rooted device or not.
Does anybody have an answer to this question? I’m so tempted to preorder one
the answer to the question should be probably yes seing how people have the system dump files. so its just a matter of time
In the meantime, you can back up SMS and MMS with GBackup from Market - backs up to Gmail automatically - can also back up call log and pics...
Dayzz
Apologies for my ignorance but what does rooting the phone mean? I've just come from using a Windows mobile phone - which I have been using since the original SPV!
Root access comes from Unix - Linux operating system speak (which is what Android runs on). Root basically means administrator privileges. So if you can run under root access then you have privileges to change/modify/do anything.
In the phone out of the box you do not have root to protect the phone from modifications that could brick it. People who do modifications under root access need to either know what they are doing, or follow a script from someone who knows what they are doing.
Ofcourse it's not 'rooted' when you unpack it from the box.
Eventually I'll guess the Hero will be rooted, but when and how... we'll just have to wait.
dipje said:
Ofcourse it's not 'rooted' when you unpack it from the box.
Click to expand...
Click to collapse
Easy son... He asked, I provided.
barryallott said:
Easy son... He asked, I provided.
Click to expand...
Click to collapse
wasn't ment to be offensive in any way ...
barryallott said:
Root access comes from Unix - Linux operating system speak (which is what Android runs on). Root basically means administrator privileges. So if you can run under root access then you have privileges to change/modify/do anything.
In the phone out of the box you do not have root to protect the phone from modifications that could brick it. People who do modifications under root access need to either know what they are doing, or follow a script from someone who knows what they are doing.
Click to expand...
Click to collapse
But as in Unix /Linux you use an ordinary login for normal day to operations and su to to use root. You have to consciously change your privelidges which is safer!!
Simon
Lots of useful info on allsorts, including rooting and other hacks here
http://forum.xda-developers.com/showthread.php?t=542452
Daisy xx
Is rooting mean really exploiting a Kernel vulnerability to gain root access?
If there are no vulnerabilities, no root access?
why doesn't Android allow root access by default like other Linux or windows...
silvercats said:
Is rooting mean really exploiting a Kernel vulnerability to gain root access?
If there are no vulnerabilities, no root access?
Click to expand...
Click to collapse
No, not really. Using a vulnerability is only needed when the manufacturer not allows you to root your device, i.e. using a locked bootloader not possible to unlock.
silvercats said:
why doesn't Android allow root access by default like other Linux or windows...
Click to expand...
Click to collapse
Because buying a phone, and the manufacturer guarantees not only the functionality of the hardware, but of the software as well. This is the difference compared to an ordinary computer. If you could modify the software in the device, the manufacturer would no longer be able to guarantee its function.
Another reason is DRM - for this to be work safely (for the rights owner), the device must be tamper proof. This is why many manufacturers allowing unlocking at the same time erases any DRM information from the phone.
Has a write-up ever been released on exactly how SuperSu works? After searching around for a while I found mostly guides on who to use the app, no the implementation details.
I did, however, find this official resource that is mostly directed at explaining how to use the root privileges programmatically, but explained things fairly well. The article gives information about SELinux, but not so much how its enforcement is circumvented.
There appears to be a lot of context switching to allow execution of certain events (from the point of view of those using SuperSu) otherwise denied under SELinux, but how did SuperSu get to the point at which it was able to "legally", as far as SELinux is concerned, patch SELpolicies?
It seems that the objective is to force the init process to spawn a new shell that runs the su daemon, but there does not appear to be any patching of the init process, but from the article linked:
On firmwares that use SELinux, su is generally implemented as a proxy to a daemon started from init
Click to expand...
Click to collapse
and
You might wonder why - if we're already running as the init context, as the root user ..
Click to expand...
Click to collapse
-------------------------------------------
tl;dr; How does SuperSu execute in the context of the init process?
Given as:
u:r:init:s0 - Highest init context
u:r:init_shell:s0 - Shell started from init
Click to expand...
Click to collapse
SuperSU does not provide root privilege. Root privilege exists or it doesn't. Someone more knowledgeable can explain it better than I can, but either you have access to the system partition (root), or you don't. What SuperSU and similar apps do is act as a gatekeeper for other apps that utilize root access. Primarily to allow or disallow apps, or certain functions within apps, to do whatever it is they do. And of course, it's also a safety precaution against malware, because malware with root access can cause serious damage.
As for the other questions, I'm not the one to reply; that stuff is beyond me.
OEMs use root/admin and then lock it away like on Linux so Its SuperSU tht is the admin and grants root*admin permission
Planterz said:
SuperSU does not provide root privilege. Root privilege exists or it doesn't. Someone more knowledgeable can explain it better than I can, but either you have access to the system partition (root), or you don't. What SuperSU and similar apps do is act as a gatekeeper for other apps that utilize root access.
Click to expand...
Click to collapse
This is likely misunderstood by many. You are thinking of the SuperSU app that can be downloaded from the app-store. In this regard, you are correct in that it manages root access. However, the application portion of SuperSU is only the front-end; there is an entire back-end solution to SuperSU that patches the system to achieve elevated permissions to be managed by the front-end in the first place. Check out the write-up linked in the OP.
arshad145 said:
OEMs use root/admin and then lock it away like on Linux so Its SuperSU tht is the admin and grants root*admin permission
Click to expand...
Click to collapse
This sounds like a plausible method, but I did not see any mention of this in the article linked in the OP. Could you provide further details or sources for your thought?
Android uses *linux* based kernel
So I know the root part is true but for the OEM just a guess ;p
---------- Post added at 19:07 ---------- Previous post was at 19:01 ----------
If you want to learn more about root just use a linux and go explore its deepest secret
Can be tricky to learn about the function of linux kernel but android is more or less the same
*Simplified description*
arshad145 said:
Android uses *linux* based kernel
So I know the root part is true but for the OEM just a guess ;p
---------- Post added at 19:07 ---------- Previous post was at 19:01 ----------
If you want to learn more about root just use a linux and go explore its deepest secret
Can be tricky to learn about the function of linux kernel but android is more or less the same
*Simplified description*
Click to expand...
Click to collapse
I have used Linux for some time now. It is not the architecture of Linux that I am curious about, though.
You are correct in that root access is locked away in most production phones. This is done simply by allowing the user of the phone to execute as a separate user with lower permissions. SuperSU somehow patches the system to execute a daemon in the same context as the init process, which presumably has the most privileged access from the set of contexts. I am wondering of the architecture of SuperSU such that it is able to achieve this execution.
Oh my sorry for misunderstanding :/
but no idea for SuperSU privilege accesses or loop
but if you debug it on pc u can find something?
*Hopefully*
:fingers-crossed:
---------- Post added at 19:29 ---------- Previous post was at 19:23 ----------
One thing am curious too
Why can't superSU gain permanent root unless bootloader is unlocked???
Like if there is OTA update root is gone unless bootloader unlocked ...
WHY?!
**Curious**
arshad145 said:
One thing am curious too
Why can't superSU gain permanent root unless bootloader is unlocked???
Like if there is OTA update root is gone unless bootloader unlocked ...
WHY?!
**Curious**
Click to expand...
Click to collapse
As far as I know, when a bootloader is "locked" is prevents any sort of reflash of the device unless you otherwise provide some kind of proprietary key (.e.g. to authenticate genuine OEM updates). So, you first need to unlock the bootloader in order to flash a custom recovery, which then gives you support for patching the system with the necessary SuperSU files.
Presumably, just as an educated guess, when you receive a genuine OTA the core patched files for SuperSU are overwritten, thus disabling your prior rootkit.
SuperSU is closed source. Just curious to see if anyone has any background knowledge of its implementation.
It seems not. Although this is disappointing, it was somewhat expected.
I'm new to Android on PC, so the question. (I'm somewhat versed in Linux, though.)
Why the need to root Remix OS for PC, if we can become root by pushing Alt+F1?
When I open the Terminal, I get [email protected] /$, while Alt+F1 gives me [email protected]_86_64:/#
I couldn't become root by writing su in the Terminal, but would be root in Alt+F1. Additionally, what are the commands in Android/Remix OS?
What advantages you get by rooting the hard disk installation?
There are a lot of different apps out there that require root permissions to function. While many of them would not really be applicable to RemixOS, or at least could be worked around using the root console, others still have their uses. For one, I'd rather trust Titanium Backup to backup my app data rather than manually copying things with the root console.
Granted, the root console is a very useful feature and does allow for a lot of tweaking, but without app access it's not the full story.
Actually, I want to, that what is the benefit if I am using root console
atiqursumon said:
Actually, I want to, that what is the benefit if I am using root console
Click to expand...
Click to collapse
Being able to take ota's without returning to the stock system.img. But you can tweak more if you have a rooted system.img.
Remix OS is a "desktop" user experience, and anywhere in the desktop's i want my Administrator rights .
The idea to root our phones/tablets came from the experience from the desktop era.
Personally, i think Root should be at least a choice officially for RemixOS
PlutoDelic said:
Remix OS is a "desktop" user experience, and anywhere in the desktop's i want my Administrator rights .
Personally, i think Root should be at least a choice officially for RemixOS
Click to expand...
Click to collapse
I would also like to have Administrator rights. If I root the system.img, rename it from root.img to system.img, would I be able to become root in the Terminal? If so, what would be the command? Is it su? Can I make a user, or rename the user from u0_a77 and can I change localhost to some other name? What would be my root password?
Right now, I can get to root terminal by Alt+F1, but I feel as the root is at Jide, and they can do whatever without my knowing it. The password for root is there, not with me. I am thinking the Linux way here. Android is anyway Linux, most probably Gentoo.
I don't use a tablet, only an android phone, and the only time I go to internet is to check the bus timetable. Never thought of rooting the phone. Now with Remix OS, and Phoenix OS, I'd like to dig in. Hopefully, with you guys help.
ostrolk said:
I would also like to have Administrator rights. If I root the system.img, rename it from root.img to system.img, would I be able to become root in the Terminal? If so, what would be the command? Is it su? Can I make a user, or rename the user from u0_a77 and can I change localhost to some other name? What would be my root password?
Right now, I can get to root terminal by Alt+F1, but I feel as the root is at Jide, and they can do whatever without my knowing it. The password for root is there, not with me. I am thinking the Linux way here. Android is anyway Linux, most probably Gentoo.
I don't use a tablet, only an android phone, and the only time I go to internet is to check the bus timetable. Never thought of rooting the phone. Now with Remix OS, and Phoenix OS, I'd like to dig in. Hopefully, with you guys help.
Click to expand...
Click to collapse
Yes, root is su; no there isn't a password (conditional access to SU is what apps like SuperSU are for - you could password protect apps if you really wanted to).
The u0_a* is the owner/group of the app itself, every app gets its own owner/group (I think this is part of the selinux security measures; despite RemixOS running with SELinux off (permissive)).
I have systemless root working if anyone wants to try; just writing a short how to atm.
HypoTurtle said:
Yes, root is su; no there isn't a password (conditional access to SU is what apps like SuperSU are for - you could password protect apps if you really wanted to).
The u0_a* is the owner/group of the app itself, every app gets its own owner/group (I think this is part of the selinux security measures; despite RemixOS running with SELinux off (permissive)).
I have systemless root working if anyone wants to try; just writing a short how to atm.
Click to expand...
Click to collapse
Being in permissive mode means SELinux allow more access to the system. Sometimes having SELinux enforcing affects performance because it will deny the system access to certain modules like Bluetooth, WiFi, etc. Also you can set a password in SuperSU and set apps so they always ask for permission before granting root access you have to enter the master password.
HypoTurtle said:
I have systemless root working if anyone wants to try; just writing a short how to atm.
Click to expand...
Click to collapse
Yes, I would like that. If you could write about the commands, it would be much nicer.
ostrolk said:
Yes, I would like that. If you could write about the commands, it would be much nicer.
Click to expand...
Click to collapse
I've posted it here at the top; it will take me a while to get a 32bit setup built though...
Hello masters,
I am here with a simple question, since Pixel 2 XL I have been unlocking boot loader, rooting with Magisk, and then editing the System/Build.prop file in order to enable Wifi Hotspot Native tethering. I got a new Pixel 6 and am wondering if I can edit the System/Build.prop file without unlocking boot loader or rooting the pixel 6 currently running android 13 with the latest patch as of Sep 2022.
Thank you in advance for your suggestions.
Sincerely,
Nope, no read/write access without root.
Cheers
@tom1807 ,
I actually don't agree with that, I believe it might be possible to write to the Build.prop without rooting. Especially if you can install a custom recovery image such as TWRP, because it will allow me to mount the system/Build.prop file and that way make the changes on the file save it and then unmount the system/Build.prop file?
Has anyone else experienced this scenario?
I tested it before I wrote my comment.
Filemanager without root access, saw the build.prop, but opening stated "Unable to read file." Access the build.prop with the same filemanager with root access was able to open the build.prop and show the content incl. editing.
There is no TWRP (yet) available for the Pixel 6-series, but installing that would require to unlock the bootloader.
Cheers
@tom1807 ,
Noted, if I am not able to install a custom recovery on the Pixel 6 with Android 13 then I am definitely out of luck, I wanted to avoid unlocking the bootloader because it will wipe/erase all the current data apps, etc on the Pixel 6 and I really want to avoid that.
Thank you very much for the information.
Sincerely,
Lol os13 even not possible with root access
Its depends on brands too
Like in oneplus os12 not even possible with root access twrp and also many other things to get rw
I'll pay to you or any other person if you or he can get rw in os12
So don't even think about without root edit build or modifications
@Mr Hassan,
OS 12 and OS 13 I am guessing you mean Android 12 and Android 13, in any device, not just the Pixel 6 (which is the device I am working on at the moment)?
Thank you,
Mr Hassan said:
Lol os13 even not possible with root access
Its depends on brands too
Like in oneplus os12 not even possible with root access twrp and also many other things to get rw
I'll pay to you or any other person if you or he can get rw in os12
So don't even think about without root edit build or modifications
Click to expand...
Click to collapse
No idea about OS12 on OnePlus, but I can assure you, that I was able to edit my build.prop with root access.
Maybe you use the wrong filemanager (I use FX) or don't have root access.
FX is able to switch to R/W access.
Cheers
jairunet said:
@Mr Hassan,
OS 12 and OS 13 I am guessing you mean Android 12 and Android 13, in any device, not just the Pixel 6 (which is the device I am working on at the moment)?
Thank you,
Click to expand...
Click to collapse
Op have very bad partitions table its on RO its blocks not sys parts to edits
The matter is not about editor
I can also try with pull then edit via pc notepad++ and try push but error not enough space
Or su not found or not accessible etc
tom1807 said:
No idea about OS12 on OnePlus, but I can assure you, that I was able to edit my build.prop with root access.
Maybe you use the wrong filemanager (I use FX) or don't have root access.
FX is able to switch to R/W access.
Cheers
Click to expand...
Click to collapse
Build prop edits still work ?
JazonX said:
Build prop edits still work ?
Click to expand...
Click to collapse
The system partition is read only and not even Root Explorer was able to fix that. With Magisk however I believe some files can be copied into a particular folder and run from there in place of the originals. Build.prop is almost certainly one of them.
I am rooted and I can't freaking access the damn thing either.
I'm thinking of downgrading the os to twelve. Won't give me read write access even with root.
dragonsouce said:
I am rooted and I can't freaking access the damn thing either.
I'm thinking of downgrading the os to twelve. Won't give me read write access even with root.
Click to expand...
Click to collapse
I haven't tried it, but there's this...
GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
Make system partition become read-write (it is also possible without Magisk) - GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
github.com