To root or not to root & viruses - Android Q&A, Help & Troubleshooting

Fact: 99% of mobile viruses are for Android.
In general it is never wise in a *nix environment to be root.
See this: http://www.howtogeek.com/132115/the-case-against-root-why-android-devices-dont-come-rooted/
So if I have an older Android device (the Defy+ in particular) I have the option of either root it and try the later CyanogenMod or not to root and stay with Gingerbread forever?
Is there a way that after I installed Cyanogenmod I somehow de-root or un-root the device for safety? I am not that technical; I guess it's not possible; so it remains more like a philosophical question. Not only about the Defy+ in particular but in general.

Un-rooting can depend on the device and the method used to root it.
Of course, you could always just delete your superuser app, or use an app encrypter to require a password to use it. I wouldn't bother though. The benefits of root are too good to pass up if you've already taken that leap. Back-ups, ad blocking, Xposed tweaks, etc.
Doing stupid stuff with a rooted phone can certainly ruin it. The solution is not to do stupid stuff. The best way to keep your device safe is to just use your head. If you want to clean up bloatware, use Clean Master or a similar app that lets you know whether uninstalling something will affect your phone. Only side-load apps from sources you (and other people) trust. Do you research before doing anything that cause a problem. If you don't know, ask here.

That "Fact" you have is absolutely pulled straight out of someone's @$$. Viruses - no. Malware - yes. Don't install shady apps from unknown developers and "99%" of the problems won't even be an issue. And you can run a custom rom without root, such as Cyanogenmod. All root is is enabling admin access of your phone. You can even enable and disable as needed. When you have a superuser app, it controls the root permissions of the phone and you have the option of denying root, allowing root once, to request in a certain time frame, or to run it always.

Related

Temporary root access to install unsigned software?

Forgive my ignorance, but ive never used android before and expecting my phone delivered tomorrow (htc hero! )
As i understand it, the android app store signs the apps similar to iphones itunes store to prevent piracy and malware.
Is this correct?
Ive read about how one can "root" the device by loading a image file thru the bootloader over usb, but i wonder, is there a sudo command or similar to temporarily enable root access and later return to default state?
I suppose i could flash it with the root image, install the app and then flash back the default os image, but that feels pretty awkward procedure and would probably raise a bunch of new problems as how the default os would launch the app installed under another os.
I was hoping to start tinkering with programming, but im unsure if i can "throw in the app" and expect it to work..?
After using macĀ“s for over 20 years ive become too used to stuff just working right out of the box, so i dont feel like experimenting on my own...
There is an option in the settings that lets you install unsigned apps, so no rooting required.
xarvox said:
As i understand it, the android app store signs the apps similar to iphones itunes store to prevent piracy and malware.
Is this correct?
Click to expand...
Click to collapse
Not exactly! Many paid apps are copy protected, but most of the free ones are not. Unlike the iPhone, where you can only install "unauthorized" apps if you jail break the device, Android allows you to install and run applications from a variety of sources on a stock device.
In essence, you do not need to root the device to develop for it, but there are certain things that applications can only be done on a rooted device (for example, receiving a file via Bluetooth, WiFi tethering etc).
I was hoping to start tinkering with programming, but im unsure if i can "throw in the app" and expect it to work..?
Click to expand...
Click to collapse
Well, programming errors aside ( ), and as long as you don't need to do anything that requires root privileges, yes you can. You should bear in mind that the *vast* majority of Android devices will not have been rooted, and therefore the vast majority of available applications do not require rooted phones.
Personally, I expect that later Android builds will remove many of the restrictions that require applications to have root access, so that they can function without requiring a device to be rooted.
Regards,
Dave
Ive found a app that would tether my laptop (mac) over wifi, but requires me to root the device.
Is there a way to temporarily do this, install the app and make the neccisary changes and then switch back to default state?
I don't believe so.
As far as I'm aware, the application requires the elevated privileges when it runs as opposed to just configuration changes. I don't think that even a setuid would help, since I believe the app expects to find and use su/sudo.
Regards,
Dave

im rooted now what?

i finally rooted my phone, ive been hearing lots of stuff about rooting your phone being a great way to explore your phone.
1. what does it really do?
2. whats cool features can i do to the rooted phone?
3. what do i do now that im rooted?
(if i post this in the wrong section im sorry)
Unix based systems run files based on permissions. If you don't have permission, you can't do certain things. Rooting gives you root access i.e. gives you superuser permission i.e. you have access to system files.
Some apps require that level of access to change things. That's pretty much it.
are there any useful apps i should know about?
Titanium Backup lets you create backups of all applications and settings. The awesome thing is, rather than just download the game onto a new phone (or a restored old one) and start over, you can install on multiple phones, bringing the applications right back to where you started.
This is a must have application for anyone doing mods to their phone.
Umm... well I can think of others but those don't directly relate to the Atrix... there are screen shot apps,...
But you can install ROMs and kernels after routing as well.
Rooted/ROM Captivate (For Sale)
Rooted Atrix

[Q] root & webtop2sd technical question

Hi,
I am new to the Atrix, but have a background in software development and was a sys admin on unix for a number of years.
I would like to know if, after a phone is rooted, do all apps run as root? or does routing simple install a setuid "su", and root apps call that when they need root access?
The webtop2sd post looks very complete and also something I will try soon. Do I need to unlock the bootloader to run a modified webtop from my sd card?
I would like to keep my phone as stock as possible, but enable a hacked webtop on the sd card.
Also there are 1000's of root threads, what is the safest canonical method (that can easily be undone)?
Many thanks and sorry for asking for your time. I have not found these answers around, but then again, there is a great amount of mis-information out there.
thx,
Scott.
Hi Scott.
I can only partially help you out; someone with more experience will answer at some point I'm sure. I'm running stock Gingerbread & rooted.
Regarding rooting: I followed the instructions on this site (which are duplicated across multiple sites, I'm sure). It worked just fine with no errors or other reasons to cause concern. That said, I'm not sure how to undo the rooting process other than by accepting an over-the-air update to ICS. Which is totally going to happen. ... <crickets>
I might be able to answer your root-app question: whenever an app requests root access, a dialog box pops up prompting me to allow or deny it. While I'm sure it's possible for a rogue rootkit to get in there if installing shady programs is your thing, I haven't yet had a problem. (A sidenote: there's an app on the market called LBE Privacy that gives you full control over app permissions: access to phone state, contacts, SMS, etc.)
Can't really help you on the webtop2sd thing, though I did install this modification to run the webtop over my HDMI cable, no lapdock required.

[Q] What does "rooting" mean to an android from a linux users perspective?

Folks,
I just got a Galaxy Note 1717 the other day and i'm still learning. I'll probably root it once ICS comes out for it on AT&T, but i'm still a bit confused about what that *means*. The threads i've read on it here and there seem to make some assumptions that as a linux user i'm not making properly.
When you root an android phone what actually happens?
If i root an android phone does that mean:
a) I've allowed acess to the root user by either changing the sudo rules or setting home to /root instead of /bin/false or /bin/nologin?
b) when i'm using the phone i'm doing so as the root user instead of [whatver user i am when it's not rooted. I don't know what name user 1000 has becuase i can't find the passwd file and probably wouldn't have the rights to it even if i could]
or is it some other thing that's actually happening when you root a phone?
As a Gentoo linux user i find this a bit confusing, even if it is a linux/gnu based system.
A) would mean that various programs are able to acces the root user when they need to.
b) would mean that i'm essencially logged in as root all the time, which in the linux word is a THOU-SHALT-NOT.
Thanks,
Bearcat
From a practical point of view, when you root, you are able to give some apps superuser permissions.
Now this means
Apps like Titanium backup can remove vendor installed apps, which is otherwise not possible.
Phone locator kind of apps can turn on and turn off GPS radio. You do not have to manually enable it.
From a linux users perspective, you can fire up terminal and do a rm -rf / . But do not do that!
Thanks.
So, to clarify: if i root my Note and then fire up mxplayer and watch a movie ,then fire up pageonce to look at my bank accounts, does that mean that i've just done both of those things as the root user?
Here's a more technical explanation of how root works that answers some of your questions:
http://cjix.info/blog/misc/how-rooting-works-a-technical-explanation-of-the-android-rooting-process/
Quick answer to your question - no. things are only run as a su if they need to, or rather, if the app has some functions that need it. Eg - titaniums access to /system needs root access, so the app fires up with su permissions. Only apps that need root access get it, and you have to allow the app the access.
Sent from my SGH-T989 using XDA
Thanks for the link jr67, i'l read that over.
New Ion? thanks for the clarification. I understand it more now, and think i'll root my phone after ICS comes out for AT&T on the note.
Its very worth it, if even only for titanium. First thing you should do is backup everything.
Ooh and the paid version is the single most worth it app ever. Many apps ive paid for and havent touched really, TB's paid differences you use every time.
Edit - titanium, root explorer and wifi kill are the only apps I have that use root access. Just fyi
Sent from my SGH-T989 using XDA
Wow! Titanum back up looks fantastic! Granted, i don't know what all the terms mean (dalvik? Isn't that a Dr. Who thing? :") ). I grabbed ES File explorer but Root Explorer looks even better.
Side question: Is there any such thing as updating a rom once i have one installed, or do i have to backup, re-flash and restore with each update that comes out for a particular rom?
Android is programmed in Java. since Java cannot be run, but needs a virtual machine, we use the dalvik vm. When you install cwm, you will have the option to clear it, and you probably should, depending.
As for updates, it all depends on what the dev tells you to do. Example: cm9 nightlies only require cache and dalvik wipes, however the roms I run usually require a full wipe. It can suck, but there are ways to make it better.
Look into the advanced restore function of cwm. I've never used it, but I know done swear by it
Sent from my SGH-T989 using XDA
Thanks. I don't know what cwm is (at least anything more than it's some sort of rom). I'l look it up.
It replaces the stock recovery, and allows the user to interact with it. i think its hosted at clockworkmod.com as well
Sent from my ASUS Transformer Pad TF300T using XDA

Android Pay error on rooted devices.

Ok, So i got the new updates from Google Wallet to the new Google Wallet and Android Pay.
When I attempted to setup Android Pay, I received the error that my device couldn't be "verified as being compatible."
A little browsing turned up some information that Android Pay doesn't like rooted devices, and even gave a couple of solutions.
1. Disable Superuser access if your Superuser app has the capability.
2. If option one isn't possible, then go back to stock, activate, and re-root.
This fix will NOT work for everyone, but since it is a simple setting change, it can't hurt to try this before looking into more 'drastic' measures. This will most likely only work on rooted stock ROMS.
I know that I use Chainfire's SuperSU app, and it has the ability to be disabled so the operator does not has superuser access until it is re-enabled. Simply go to your SuperSU app, go into the "Settings," and uncheck the "Enable Superuser." Different versions and other apps may be a little different, but principle should remain the same if it is an option.
After disabling SuperSU, open Android Pay and complete your initial setup. Once completed, return to the SuperSU app and re-enable Superuser access. The Android Pay app has continued working since then for me.
Based on information given by 'rbeavers,'
https://koz.io/inside-safetynet/
Guess I'm screwed
Click to expand...
Click to collapse
it appears rooted stock ROMs will probably work if you disable superuser (no guarantee though). Custom and ported ROMs most likely will never work unless the devs figure out a workaround. I would also imagine a otherwise stock ROM running a custom kernel wouldn't work either based on rbeavers' link.
Another note, I've integrated updated system apps and certain other apps into the system partition, so that probably won't matter if anyone is curious about that. (Could be different for other people though.)
Original Posting:
Just got the new Android Pay. I received an error that my device couldn't be verified as being compatible. Found some where else that it doesn't like rooted devices . Fix with SuperSU is easy. Go to SuperSU, touch Settings, and uncheck Enable superuser. Setup Android Pay, then re enable it, and so far, it's working for me.
Click to expand...
Click to collapse
Tried it didn't work for me "turned off " SU. My bank isn't on the "list". So that might be it?
Maybe? I didn't think Android Pay used the bank account, only Wallet does. Pay requires you to link your debit or credit card. Both apps automatically pulled my information, so I didn't have to dig into that very much.
Another thing my ROM is otherwise stock.
I've also read that Android Pay just doesn't like some ROMs, so users on custom or ported ROMs and a few devices in general are probably going to be left out in the cold... unfortunately.
Hopefully someone with more knowledge of the Android system can help us out here soon.
https://koz.io/inside-safetynet/
Guess I'm screwed?
Interesting read. Thanks for sharing
So, rooted stock ROMs will probably work if you disable superuser (no guarantee though). Custom and ported ROMs most likely will never work unless the devs figure out a workaround. I would also imagine a otherwise stock ROM running a custom kernel wouldn't work either based on your link.
Another note, I've integrated updated system apps and certain other apps into the system partition, so that shouldn't matter if anyone is curious about that.

Categories

Resources