Transferring of apps and pictures and other data is no problem. However, the issue is transferring app data, so that you not only have your apps, but any data they've saved as well. This isn't an issue for iPhones, but I've never owned one and probably never will.
Guess for public interest I should clarify that the reply made which I described has to do ONLY with the android O/S that Powers my mobile handsets. Not a clue in the world how Apple units fare nor have I ever handled one except for short moments my daughter has had me look at her screen here & there. In the beginning when it became one or the other, the decision was made to go Android and I never been more pleased with that choice.
Another thing bloatware on the trusted ROMs I install doesn't exist. And bloatware that is disabled or uninstalled on stock or carrier ROMs. Could still be somewhere that could be spying & sucking up resources.
So you would also want to get rid of sudo in Linux? Without UAC in Windows and sudo in Linux you would not be able to install any applications. Changing that behaviour would mean that the installed applications are no longer write-protected for standard users. Any malware could easily tamper with them. I seriously doubt that this will make your system more secure. Unless everything is sandboxed by default (which is the case in Android for that matter).
When i install a software, I install it on admin account, which is never used for browsing and downloading apps. Let say you are compromised by a silent malware on SUA, then you want to install a soft while still on SUA, the soft will requires elevation to be installed, you will allow it via UAC, thanks to you the opportunist malware will get a door open to elevated itself...good job. I did not invented this scenario, such malware behavior already exist. Anyway, the thread is about rooting, not UAC.
guest, you talk about silently running processes and legitimate software including malware, so I wonder why you always say that default-deny ALONE is good security, when it obviously isn't; according to your own words here. Anyway... BTT: There already are already malicious apps that can elevate themselves to root privilege in standard android. How can it possibly get safer when you are running your device unlocked/rooted? Now all it has to do is simulate touches at the right position and boom it's root. Or if that doesn't work, it is probably easier to circumvent any third-party root-protection than it is to get root in standard Android, I guess.
You're really not missing much Mrk, unless you want to spend lots of time on another ambition that's likely to consume more effort than it's worth. Mine are R00ted alright and while it was an interesting and in many respects a useful learning curve, that was over 5 years ago and things change week to week, day to day anymore. I for one have not so much as pasted a single Custom Rom into my androids although it is been quite easy to do so with TWRP backups etc. Downloaded some with full intentions to do so, but my chief interest in R00T was more opening/unconcealing the internal branches (files/folders) and other workings of settings that might improve security and indeed has locked these handsets down tight.
Surprised to see nobody has mentioned verified boot. Starting from Pixel it's became much tedious for those who want custom ROM. Sure, only chance it makes sense is you're already partially compromised or the adversary got physical access, and nasty rootkit is trying to launch, so not much chance as long as you're careful of installing apps. Default-deny-execute ALONE is far from perfect, but it's better than default-allow-but-detect-suspicious, I think it's his (& other default-deny advocates') intention. No, 1st method doesn't work thx to sandbox. But the 2nd is possible when you use non-standard Android. Also remember (standard) Android is protected by SELinux so even root doesn't have full priv. Me too. Mine is almost empty, no pic, almost no contacts, and least apps. Only time-consuming things when I buy new phone will be disabling default bloat apps & Google's crap func, permission ctrl, and Firefox config. I don't feel need for backup.
I have and use an app that simulates touches anywhere on my device. You just need to make the user allow it, it seems.
I've toyed with the idea several times, I have an old Samsung S4 that I could try it out on, but really don't see the point in doing so. The only thing I use that phone for now is a couple games and a paper weight. My current phone is a Samsung S7 edge, I really don't see any real advantage to rooting this phone.
It all comes down to what you want to do with your phone. Yes, most people don't need it. But the examples provided earlier show that there are legitimate cases where rooting makes perfectly sense.
At least in standard Android, such behavior is not allowed unless you allow ADB debugging or device admin and accessibility service. See this.
It is not rooted and only needs an accessibility service. The app is called: AutoInput and is roughly part of a bigger app collection that complements Tasker, but stand-alone.
The complete sentence for context. I simply said I do not see any advantage to rooting MY Samsung S7 edge. Perhaps you are reading between the lines?
I don't see that my remark contradicts what you said. It was a general remark pointing to specific situations where rooting makes sense - which obviously do not apply to you. Perhaps you are reading between the lines?
OK, so if a user allowed permission for the accessibility service, only defense left is how hard it is to root the phone - it's non-trivial in recent devices but probably easier in older phones. Thanks for the info. It seems abuse of accessibility service spreads beyond OSes - so we have to be extremely careful to allow the permission, unless we really need it.
I've been rooting my phones for as long as I remember. Root is not dangerous, as opposed to general assumption. It may be, but I doubt noobs will root their phones nowadays. XprivacyLua and AFwall+ are a must. I need to take full control. I do not use google (f-droid and yalp store if needed- I use microG). Magisk + adAway and a bunch of xposed modules. But that's me, I'm a geek I guess.
I tried rooting my device in the meantime, but I can't connect via fastboot or fastboot wasn't working so I stopped. I was hoping to get LineageOS on it, but meh.
It may be useful for others with specific usage scenario but my personal phone usage does not necessitate rooting so I choose not to.
As much as I love to tinker with stuff, I need my phone to work as close to 100% reliably as possible, so I wouldn't root it. I don't use any apps on it except for the excellent Kiwi browser with its built-in ad blocker.
@SouthPark While there's no need for the majority of Android users to root their devices, doing so will have no absolutely affect on reliability.
Slightly OT there's a few negligent members in different forums I visit that are posting aio rooting solutions. It's disturbing because as great as Wilders & other forums are they are NOT rooting forums & there's zero support for rooting. By support I mean there's not dozens of qualified individuals who if asked nicely & they have the time will help. Rooting instructions belongs places like XDA Developers, Android Forums, Android Central, etc. Posting pretty much anywhere else but those sites is irresponsible. When this happens please speak up folks. Thank you.
