• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Forever Rootless?

Gmash said:
....My GS3 I haven't even rooted, the bloat argument is outdated when you can disable and hide the offending apps in a junk folder. You don't even see them....
Click to expand...
Is this just for the GS3? Or is there an app that'll disable bloatware without root?
 
zapjb said:
Is this just for the GS3? Or is there an app that'll disable bloatware without root?
Click to expand...
On my Atrix 2, which is still running ICS, by the way, I was able to disable apps I didn't want, such as Facebook, via System Settings. IOW, without root and without anything extra.
 
jefboyardee said:
As some of you know, I have proudly maintained my rootlessness for over two years, mostly due to brickophobia. Well, yesterday, bored enough to watch videos about how easy rooting is, I said the hell with it, I can always buy another phone. So, armed with that courage...

First, from my folder full of root-somedays, I tried How to Root the Huawei Ascend II (Straight Talk), using Poot. I followed its instructions step by step, but just like it mentioned, it couldn
Click to expand...
 
for me i will always root my phones. the freedom far out weigh the risks....plus it is pretty hard to brick a phone......the key to it is do your research ahead of time. read as much as you can and come here to AF and ask as many questions as you need.....then root your phone.

my rooted phone runs faster and has a much better battery life then a non rooted phone.
 
Just tried it again so I could dictate its message:

A demon has materialized while pooting. Error code: 87.
su binary was not written
you need to restart your device (which I did).

Path is:
“/sbin:/vendor/bin:/system/sbin:system/bin:/system/xbin”

I have no idea what any of that means, maybe you do...
 
I did have a feeling that su referred to something else, since it originally said to install superuser after I root, but when the error came up, I was clutching at straw.
 
But I did find this:

Assuming everything worked as it should, Poot will have written an su binary in /system/xbin. This binary goes with the Superuser app (not the SuperSU one). You'll want to install Superuser from the play store to finish the process and allow apps to use the su binary.
 
Something that will always make me root, besides having complete control over my device is custom roms. Even when a manufacturer is slow on updates or abandons a phone, I know I can always turn to the modding community to put some more life into my phone.

I'm really happy with my Galaxy S4 right now, and rooting and installing the Google Edition rom has been like a dream come true. Add a little xposed framework and it's literally the perfect device for me.

Also, thanks to root, lots of my tasks are automated now. Don't even have to think about them. Such as auto-toggling GPS when I launch certain applications(and turning it back off when I exit to save battery), automated backups of everything on my device, then another automated backup to copy that information to my personal computer on my home network.

Being able to transfer all the application data back and forth is great too. Saves a lot of time.

Rooting is can be a scary proposition for people because you're venturing into unknown territory. The way I always explain it is akin to how people view desktop PC's. If you ask someone if they'd be willing to give up administrator access on a PC, most people would say no way. Now apply that same concept to your Android device. Because it's just a portable computer with communication radios, after all.
 
funkylogik said:
Even as a matter of principal, any phone geek should unlock root access because we can and because its rediculous that we even have to do it in a sneaky way instead of just flipping a switch in dev options :D imo :beer:
Click to expand...

This is the kind of thing I miss from webOS.
 
I rooted my Samsung the day I got it in a hotel room, because that's what you do. Although I haven't actually done anything that requires root though, no need so far.
 
mikedt said:
I rooted my Samsung the day I got it in a hotel room, because that's what you do. Although I haven't actually done anything that requires root though, no need so far.
Click to expand...

Uh, Mikedt.....isn't what you do in a hotel room supposed to be your own business? :p :D
 
Rooting - essential for GB phones (at least for the Wildfire S, to overclock and move/link Apps to an SD card) less need in ICS and later. I'm in the process of investigating root for my Xperia U, to O/C it and ust Titanium and do a Nandroid. I might root my Huawei Y300 later, but that's very smooth and has plenty of space on an 8GB SD card. Also I don't mind Huawei's UI that much.
 
I don't mind Huawei's UI that much.
Click to expand...

For my needs and wants, everything is fine with this cheapy Ascend except internal memory, which is hogged by crap I never use, like Google+. That, not fancier ROMs, is my only motivation to root.

Right now, I have about ten apps that I
 
MoodyBlues said:
Just curious, do you only have Linux computers available to you, and/or did you root your phones using Linux computers?

I honestly haven't even thought about rooting my Atrix 2 lately. I gave up when I first got it and could find nothing for rooting on Linux computers. I have no idea if there are such things available now, but if others here have been able to root their phones from Linux then I may take another look.
Click to expand...

I rooted my wife's ancient T-mobile G1 the other day with the assistance of my linux rig (running Ubuntu 13.10 pre-release). The adb and fastboot tools are now in the standard ubuntu/debian repositories, so if in theory your root method involves .bat files that are invoking adb or fastboot, you should simply translate the .bat file commands to compatible .sh script, make sure adb and fastboot are installed, and hit the gas. :D
 
Joelgp83 said:
I rooted my wife's ancient T-mobile G1 the other day with the assistance of my linux rig (running Ubuntu 13.10 pre-release). The adb and fastboot tools are now in the standard ubuntu/debian repositories, so if in theory your root method involves .bat files that are invoking adb or fastboot, you should simply translate the .bat file commands to compatible .sh script, make sure adb and fastboot are installed, and hit the gas. :D
Click to expand...
In the past, all I found were window$ files, including executables. So that was always a dead end. (I can't recall now if I tried running them via wine, but if I did they didn't work.)

I just checked Synaptic and there's no sign of ADB or fastboot--but I'm still on 12.04. :D
 
MoodyBlues said:
In the past, all I found were window$ files, including executables. So that was always a dead end. (I can't recall now if I tried running them via wine, but if I did they didn't work.)

I just checked Synaptic and there's no sign of ADB or fastboot--but I'm still on 12.04. :D
Click to expand...

Interesting. Specifically, I used:

sudo apt-get install android-tools-adb android-tools-fastboot

And it both installed and set up the proper paths so I can invoke them from CLI whilst anywhere in the file system. :p
 
You must log in or register to reply here.
Back
Top Bottom