Developer Admin / Senior Recognized Developer
Thanks Meter 10292
Join Date: Nov 2009
Location: United Kingdom Likes: Galaxy Note 2 Dislikes: Noobs
Originally Posted by MightyBear007
You just did a ro.secure in the ramdisk
Am I right?
Nope. Setting ro.secure=0 is NOT the right way to root.
The ramdisk is modified, it will detect if you have root already, and if not, it will install SuperSU and the corresponding su binary on root. I also set ro.adb.secure=1, to add extra security for the device (now you need to approve ADB connections to unrecognised computers).
If you use ro.secure=0, this will break many apps with "root detection", as well as being a horrendously ugly hack, which introduces all sorts of vulnerabilities. ro.secure should always be set to 1
I strongly advise you don't use root methods that set ro.secure=0, as well as any kernels that do it. It's much safer to not have a rooted ADB shell lying available to anything that connects to your device... Including... you know... an app running on your device that initiated an adb connection to 127.0.0.1
So yes, this gives you root without adding stupid extra security holes like many kernels and "root methods" do
Having trouble getting an answer?
| What is XDA about?
| How to ask for help?
if [ $PM.incoming.type = $type.question.ROM.how_to_use ] || [ $PM.incoming.type = $type.question.ROM.silly_question ]; then mv $PM.incoming /.trash; PM.response($responsetype.ignore); $PM.sender.ignore_in_future=true; init.sequence($boy_who_cried_wolf); fi;