Related
Hi Guru's.
Im back and i got my new gadget but im not too sure what to do on it quiet yet. i been searching online all day to try and find a better market place and been seeing all this tec talk that i dont understand about APK's and roots stuff. So im hopeing that some one will be able to help me a little by DUMBING some terms and directions down for me so i can make the best of my tablet or it will be returned and ill have the easy IPAD come tax returns lol.
Im tec savy, but yall are so good at what you do here so im hoping that some nice person will guide me in the right direction.
Also ive seen some threads with questions on what apps to install and such, but then i was confused on which apps to really install beucase folk has had issues with the apps that they installed. so believe me before i get a ignorant response to my topic i have done my leg work and ive read over 50 pages of talk about this tablet. And i have an idea on what to do but im still not sure.
Thanks a Bunch
<3 Chayda B
Unfortunately I am also not so great with this but will explain some terms as best I can...(I'm also a noob)
APK: Is the term used for applications on the Android Operating System.
Root: Is a term that describes unlocking your phone's true potential. This is accomplished because normally the Android OS has certain permissions unlocked for the user and other super permissions locked. This defines what the unrooted OS will let you do to the device without harming it. Rooting basically unlocks those hidden(super) permissions allowing you to do much more to the software and hardware like overclocking your CPU to make it faster... umm also allows you to do things like backup applications or extract them and on some devices play around or look through the device's scripts and system files. Ask the community about rooting as they can probably explain it better than I can. Sorry!
Sadly about the Market, it is not fully unlocked in all countries and I think you need special licensing to access certain apps or apks on the market. As for your Silvania I would recommend going to Androidtablets.net and search for your device. There is a mini community there for your tablet, maybe you can get more help there.
this tablet become truly enjoyable once you have the real Marketplace on it.
I put together a walk through that takes you through all the steps necessary to get it installed and working on your tablet here.
I take zero credit for any of the work that went into getting it working. I mainly made the page as a reference for myself in-case i need to do it again.
If you hit a snag let me know and i'll do what i can to help.
just as a note i also have the gingerbread keyboard and live wallpapers working on mine. i'll see how my market guide is received before i put together anything about putting these others on our tablet.
Does rooting provide any protection against malware or does it make it worse?
Sent from my Nexus 7 using Tapatalk 2
Best protection against malware = user.
If you just root, and don't use a custom recovery and custom ROMs, immediately install SuperSU, antivirus, and make sure you protect yourself. SuperSU will at least notify you when an application is trying to use root permissions (aka - modify or access system files) which is not something you want every program doing.
The nice thing about having root is you can change things on your phone a launcher can't touch - boot animation, screen DPI, backup apps like Titanium Backup, and of course clearing out carrier bloatware.
If you do go with a custom recovery, TWRP for example, and flash ROMs, CyanogenMod for example, you are often provided with SuperSU tools and other options as part of the package. Just be very sure you are using images from reputable sources. Lord knows what kind of stuff someone who published a custom ROM could get off your device if they had ill intents.
If you are new to rooting, flashing, etc then I would suggest starting with root access only. Explore what you can do with it, learn it, and be conscious of security as you go. After you are comfortable with it, try CyanogenMod to see how a custom ROM really differs from stock.
Rooting will not give any protection against malware you have to install antivirus or use any app that will help you against this with root
Oh, and to answer the question 'should you root'... We tinker with all the things because we like to. We like knowing how all the things work. We like having more control of all the things. If you don't like this, then don't.
clago87 said:
Does rooting provide any protection against malware or does it make it worse?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Android is blamed for earning malware for your device but hey! the user of the device is 100% responsible for it. Stop clicking on spammy links and visiting those websites which allow you to earn malware Problem will be solved.
Now rooting. Rooting is the best way to taste your android device at fullest. Use custom ROM, tweak the kernel and much more
clago87 said:
Does rooting provide any protection against malware or does it make it worse?
Click to expand...
Click to collapse
I'm not an expert and have found the site to be filled with a lot of great, detailed information including howto instructions if you decide to root. I've rooted a few phones but not the N6 yet. I'm waiting for 5.1 to be available only because I'd rather the OTA download and didn't want it to break root and have to spend a day playing with the phone to get it set up again. Yes, lazy too. My two cents:
There were a few articles back when 5.0 was being released saying how root for this OS would need to bypass much of the built-in security features with this OS version. I don't have a clue if it is true. If I decide to root, I'll go back and see if this is a real problem.
Why root? The exposed framework gives you nice features. Apps can have access to the phone os/hardware that is blocked, for example, you can get the notification LED to work, the battery statistics allow more access so you can see what app is killing your battery. There was one or two other apps I used that required root, can't recall now.
Its easy to say malware is a user problem, some of it is like careless sideloading. But I have no idea if a web page is loading something on my phone. Worse, if you look at the permissions you grant apps, you would load very few on your phone. I find the service providers , like T-Mobile (mine) and Verizion (Fios) to be the worst in asking for access to the phone data for no apparent reason. Does my app to see visual voicemail really need access to my microphone and camera or apps I have loaded on the phone? In my opinion this is spyware as you have no idea what is being uploaded to the app developer. Many of the apps in google play have questionable permission requirements.
That's actually another reason to root, the xposed xprivacy module (haven't used it). Or, using a DNS that will filter malware web site (I think you need root to change the DNS in Android). I'm not sure about the status of xposed on the nexus 6 so you have to read the threads. I don't know why you want to root, so you have to determine if it is worth the effort.
Simple answer is No.
if you're asking if you should root then you do not know what root is and the benefits to it. if you are happy with the phone and all the apps you have suit your needs, then stay as you are and do not download any dodgy apps from the play store
IINexusII said:
Simple answer is No.
if you're asking if you should root then you do not know what root is and the benefits to it. if you are happy with the phone and all the apps you have suit your needs, then stay as you are and do not download any dodgy apps from the play store
Click to expand...
Click to collapse
Couldn't agree more. If you have to ask, the answer is no.
IINexusII said:
Simple answer is No.
if you're asking if you should root then you do not know what root is and the benefits to it.
Click to expand...
Click to collapse
Terrible answer! Just because someone doesn't already know something is piss poor justification for telling them not to learn it.
If someone asked the forum if there were any benefits in C#, would you tell them not to bother learning to program, just keep buying Microsoft products?
FFS...
Elnrik said:
Terrible answer! Just because someone doesn't already know something is piss poor justification for telling them not to learn it.
If someone asked the forum if there were any benefits in C#, would you tell them not to bother learning to program, just keep buying Microsoft products?
FFS...
Click to expand...
Click to collapse
What a terrible response. is root a programming language?
Elnrik said:
Terrible answer! Just because someone doesn't already know something is piss poor justification for telling them not to learn it.
Click to expand...
Click to collapse
No, it is the best answer. He is not asking to learn it, he is askign us to make a decision as to whether he should root or not. If he knows the benefits of root, he should make teh decision himself based on the usecase. If he doesn't know the benefits, he should read a sticky thread that lists the benefits. If he doesnt know whether he should root, then he shouldnt because it is not something to um and ahh over.
Rooting in and of itself will have no effect on your getting infected with malware or not. It may affect the degree in which something can muck up your system, because if rooted, that program can get further into the OS than if you were not.
Now, that said, the real meat of it is that if you allow sideloading, that's the one that will let apps install from downloaded files, etc.
Ever notice where they say all the android handsets are getting infected? not here in the US anyways.
If you stick to known downloads and are not trying to get hacked apps, you won't have to worry.
I have to agree with RootSU here, his last paragraph sums it up nicely.
IINexusII said:
What a terrible response. is root a programming language?
Click to expand...
Click to collapse
Well, I can't resist using your own logic... If you don't know that root isn't a programming language, you shouldn't root. You probably shouldn't even reply to posts. Further, If you can't understand the example I provided, I'm not going to waste my time and explain it. You should just go read the stickies on the benefits of examples, or something. After all, you shouldn't um and ahh over this.
Facetiousness aside, if you read my example you'd see that I in no way called root a programming language. My entire point is that there are better ways to tell someone not to root. If your point to the OP is this: No, you shouldn't root because it can be dangerous, can brick your device, and that you really need to do your homework on it before you just go and do it, then tell them that! Don't condescend to them and/or future readers of the thread that not knowing it is reason enough not to do it ever. It's insulting. At least it is to me. It IS a discouragement, and in IMO, and in the spirit of XDA, we should try to point people in the right direction so they can learn and make them aware of the risks and benefits so they can make informed decisions. Sure, if it's already been covered, post a link to the thread or sticky. No need to rewrite it. But sending the message of "If you don't already know, abandon all hope now" is crap.
If you disagree with me, then I'll agree to disagree with you.
That's the last I'll say about this.
Peace
Elnrik said:
Terrible answer! Just because someone doesn't already know something is piss poor justification for telling them not to learn it.
Click to expand...
Click to collapse
I interpreted it to mean that learning more about root and what it might offer/require of a user is probably best before actually rooting and then deciding later on if that's what you really wanted to do. That is, being conservative here is probably not the worst suggestion.
- ooofest
Alright, so we now have root (somewhat), but now, we yearn for BL unlock. I've been investigating, but I've come up short. I'm in no way a developer (other than some basic HTML/CSS knowledge), so maybe the community can brainstorm and churn out ideas. If you have 'em, let 'em rip! :good:
EDIT: Ok, yes, I realize that I 'dun goofed. There are multiple threads about this and I made a mistake between root and WP. I know maiko1 has worked hard on getting us root, and I and everyone else appreciates it. My apologies for disturbing the peace.
jake7405 said:
Alright, so we now have root (somewhat), but now, we yearn for BL unlock. I've been investigating, but I've come up short. I'm in no way a developer (other than some basic HTML/CSS knowledge), so maybe the community can brainstorm and churn out ideas. If you have 'em, let 'em rip! :good:
Click to expand...
Click to collapse
http://forum.xda-developers.com/droid-turbo/general/bounty-disable-write-protection-unlock-t3067615
There are already multiple threads on this topic you are bringing up. Also what u have is root....there is no somewhat or in between. If you dont understand what moforoot does for the turbo then you shouldnt be tweaking your device in the first place.
I think the way is have a moto maxx and droid turbo together and study what changes with unlocking in maxx
the_rooter said:
http://forum.xda-developers.com/droid-turbo/general/bounty-disable-write-protection-unlock-t3067615
There are already multiple threads on this topic you are bringing up. Also what u have is root....there is no somewhat or in between. If you dont understand what moforoot does for the turbo then you shouldnt be tweaking your device in the first place.
Click to expand...
Click to collapse
Right, but that's a bounty thread. This isn't, I must made this for general brainstorming and idea sharing. Also I only called it somewhat root because of write protection, but I get what you mean. Sorry if I'm bringing up an already discussed topic, but I know everyone is yearning for some kind of unlock, and I figure that discussion and brainstorm is good to help keep the idea moving forward.
what gets me, and no offense to anyone, but those with the skills and knowledge to do this do not brainstorm said ideas on xda, but in other resources and areas or in idfferent areas of xda. Too many people who have no idea what they are doing would hinder the process of accomplishing the goal. while i think this threads are a good thing in a way, they are really useless because the ones with the knowledge do not really come here and discuss the insanely complicated procedure of what must be done in order to accomplish things.
Here is another thread with the same idea called Droid Turbo Think Tank.
Nearly every person I've come into contact with has said it is possible to unlock the bootloader so that gives hope. But just don't expect it soon.
jake7405 said:
Alright, so we now have root (somewhat), but now, we yearn for BL unlock. I've been investigating, but I've come up short. I'm in no way a developer (other than some basic HTML/CSS knowledge), so maybe the community can brainstorm and churn out ideas. If you have 'em, let 'em rip! :good:
Click to expand...
Click to collapse
When will this issue die? Root ACCESS, and write protection are NOT the same thing. Totally independent of each other. Everyone assuming that they are the same thing is starting to get ridiculous it has been explained here multiple times.
renegadeone8 said:
When will this issue die? Root ACCESS, and write protection are NOT the same thing. Totally independent of each other. Everyone assuming that they are the same thing is starting to get ridiculous it has been explained here multiple times.
Click to expand...
Click to collapse
Can you explain this difference? I now understand they are different. I previously thought root was defined by having read write and execute permissions everywhere (including to the system)
Clearly I'm not right. But maybe you could explain that to me
Diego1751 said:
Can you explain this difference? I now understand they are different. I previously thought root was defined by having read write and execute permissions everywhere (including to the system)
Clearly I'm not right. But maybe you could explain that to me
Click to expand...
Click to collapse
I may be wrong. That said, how I see it and how wiki answers:
Rooting "is the process of allowing users...running the Android mobile operating system to attain privileged control (known as "root access") over various Android's subsystems."
Privileged control "is the act of exploiting a bug, design flaw or configuration oversight in an operating system or software application to gain elevated access to resources that are normally protected from an application or user"
So by that, we have root. We (really maiko1) have exploited a bug that has given us elevated access to the system partition which is normally protected from us, the user.
Write protection is literally what it is. Protection from unauthorized code to be written.
I look at it as, we have root. A (seemingly large portion) of people had the same definition of Root as you, so those people are all upset merely because they started from an incorrect assumption of what they want. (Write access)
So say every birthday (phone) you have, Im going to get you a cake (Root) And every birthday that cake comes out and all your friends (Write access) surround you to celebrate. Well I never said I was bringing your friends, I just said cake. Then one year no friends come and all you have is cake. Now youre saying this isnt cake, where are my friends.. And my response is, no no no, I said I was giving you cake. Heres your cake, Its not my fault you assumed the friends always came with the cake.
Diego1751 said:
Can you explain this difference? I now understand they are different. I previously thought root was defined by having read write and execute permissions everywhere (including to the system)
Clearly I'm not right. But maybe you could explain that to me
Click to expand...
Click to collapse
Basic Analogy: Compare Android to Windows for a second. Pretend that Microsoft removed the Administrator account, so nobody could use it, and they set up write-protection on C:\ and restricted your write abilities to C:\Users\YourUserName. So someone (maiko1) comes along and finds a way to re-enable the Administrator account, and you can use it, but due to write protection, you can only write to anywhere in C:\Users. Make sense?
r3pwn said:
Basic Analogy: Compare Android to Windows for a second. Pretend that Microsoft removed the Administrator account, so nobody could use it, and they set up write-protection on C:\ and restricted your write abilities to C:\Users\YourUserName. So someone (maiko1) comes along and finds a way to re-enable the Administrator account, and you can use it, but due to write protection, you can only write to anywhere in C:\Users. Make sense?
Click to expand...
Click to collapse
ntxct said:
I may be wrong. That said, how I see it and how wiki answers:
Rooting "is the process of allowing users...running the Android mobile operating system to attain privileged control (known as "root access") over various Android's subsystems."
Privileged control "is the act of exploiting a bug, design flaw or configuration oversight in an operating system or software application to gain elevated access to resources that are normally protected from an application or user"
So by that, we have root. We (really maiko1) have exploited a bug that has given us elevated access to the system partition which is normally protected from us, the user.
Write protection is literally what it is. Protection from unauthorized code to be written.
I look at it as, we have root. A (seemingly large portion) of people had the same definition of Root as you, so those people are all upset merely because they started from an incorrect assumption of what they want. (Write access)
So say every birthday (phone) you have, Im going to get you a cake (Root) And every birthday that cake comes out and all your friends (Write access) surround you to celebrate. Well I never said I was bringing your friends, I just said cake. Then one year no friends come and all you have is cake. Now youre saying this isnt cake, where are my friends.. And my response is, no no no, I said I was giving you cake. Heres your cake, Its not my fault you assumed the friends always came with the cake.
Click to expand...
Click to collapse
thanks for the explanation guys. I completely understand that root and write protection are different things. I USED to think this when Mofo was released it was the first root I had to pay for and I was also curious about this write protection thing because I had thought (when others explained root to me back when I was a noob) that root was defined by advanced control to the system (which it sounds like it is but this is a VERY loose definition) including read/write/exc acceses to the system and subsystems. after reading for a while to learn the difference I happily bought mofo (partly assuming more dev work will maybe unlock bl or wp) But now people in this thread (and many others) now know
Can we stick to one thread!
Looks like kinguser and supersu are going head to head.
http://forum.xda-developers.com/showpost.php?p=61899071&postcount=1277
I sort of agree with kingteam on this, without their hard work there would be no root for a lot of people.
On the other hand they shouldn't force a third party app on to someone's device, but maybe offer it as part of the root process.
Still supersu doesn't block users from changing to another super user app, so they shouldn't neither.
So now we know why Chainfire won't support kinguser in flashfire.
hopefully Kingteam changes their policy about removing their propriety apps. Super-sume wouldn't have been made if it were for Kingteam's policies.
The question is why anyone who offers a rooting method wishes to force the use of their software.
louiscar said:
The question is why anyone who offers a rooting method wishes to force the use of their software.
Click to expand...
Click to collapse
Well i think thats obvious. If youve ever spent time and effort developing something you'd understand, its not nice that a developer puts all the effort in and then the glory is taken by another. Its obvious Kingteam put a lot of effort into their root methods and creating the root management for it to just be immediately removed without even trying it. Its actually quite good, i used it for months on my htc m8 to no ill effect.
Itd be a shame if they decided to throw in the towel and discontinue any more development because of it.
ashyx said:
Well i think thats obvious. If youve ever spent time and effort developing something you'd understand, its not nice that a developer puts all the effort in and then the glory is taken by another....
Click to expand...
Click to collapse
I don't think this is about glory. I understand your point but ... the whole idea of rooting is to gain control of your device, so prohibiting you from being able to choose what you have running on your device is defeating that purpose and fundamental principle.
Although I'm prepared to accept that their reasons for doing this may not be malicious it does little to encourage trust when they appear this desperate to stop you removing their software especially since it has root access. AFAIK this isn't open source and perhaps a lot of other stuff isn't but we have a basis of trust in most of those cases.
IMHO their strategy should be as any other dev who has gained a reputation, through the right channels (such as Chainfire). It takes time but their efforts and results would speak for itself and they could allay any fears by showing their code is safe. IF they really want people to TRY their software then the route to this is not to create fear and doubt about the integrity of their software but to do the exact opposite and allow people to have peace of mind whilst they give it a bash.
They claim that their reaction to Chainfire et al not responding to their communication has resulted in the denial to the user of the rights to choose what software runs on their devices. This reaction to me is rather childish and does little to persuade the likes of Chainfire or Supersume devs to change their minds.
They (Chainfire / Supersume) may or may not be actively trying to throw this software out or 'bad mouthing it as such', I don't know I've not heard their story but it could just be they are simply maintaining the ethics of user choice in offering to remove something that Kingroot team have deliberately made difficult to do.
On the other hand if they are telling people that Kinguser 'causes conflicts' they should back that up openly and offer the choice to remove purify or not - it is a request I note Kingxteam make and would be valid IMO unless there are good reasons why not. Good reasons would be closed source or why the code may conflict, if no one can verify the software is doing only what it is supposed to (now and in the future) it's a good reason not to have it in your device.
Call me sceptical but what is really in it for them? They aren't gaining any money by you running their software, but they sure act like there is something to gain. They spent a lot of time and effort in finding root solutions but they don't appear to be like other devs who do it for the challenge, or for themselves with a mind to share and who by the way don't try to 'sell' or 'force' their methods on us - you take it or leave it, and we do with thanks and donate or buy their pro versions to show appreciation.
Kingroot (Kingteam) on the other hand appear more like a company to me but who knows. That's the whole point, we don't seem to know a whole lot about their motives and that perhaps creates doubt whether rational or not.
And I agree providing there's nothing nasty in there it would be a shame if they threw in the towel but they are going the wrong way about it to gain people's trust - I'm sure many people would love to try their software and apps provided they don't have any nagging doubts.
You misunderstand what I'm saying. I don't condone the way they are going about things, but I do agree with their reasons. Its wrong that everyone is automatically removing kingroot/kinguser without even trying it.
Like I say I used it for a while and I actually preferred it to supersu, but now that devs like chainfire have prevented the use of kingsu with flashfire and only allows the use of his own or cwm there's no choice but to use supersu.
Now why has chainfire done that? He has basically forced people to use his own app. That's just as bad as what kingteam have done.
Don't get me wrong Chainfire is a stellar dev, but I dont understand that and that's how a lot of this has come about. Many have been converting to supersu to use flashfire. I bet there are loads that would have stuck with kinguser just for simplicity's sake if flashfire worked with it.
They don't prevent the removal of purify, I don't even think it gets installed as a system app, so its no big deal to remove. They shouldn't force install it though, that should be offered as a choice after successful root.
Neither do they prevent removal of kingroot and kinguser, it can all be cleanly removed from within kinguser.
As for being closed source that's no different to chainfires apps. His root solution is closed source and so is flashfire.
Kingteam have been around now for a while and have gained notoriety lately because their root solutions have worked for many. If they had any dishonorable intentions I'm sure it would have come out in the wash by now, but asfaik nothing untoward has happened to anyone.
I'm not protecting them in anyway just understanding their point of view, put it this way how many how have used their root exploit then clicked the link to their XDA thread and thanked them?
Probably not many, credit were credit's due I say.
Hard work deserves some recognition. Maybe I should add the link in my root thread.
Sad that this situation has occurred. I am very appreciative of Kingroot providing a method to root my Tab S without tripping KNOX. Without it I would not have rooted until my warrenty had come close to expiring. Unfortunitely I would have removed Kingroot apps for SuperSU for a few reasons
1) I already paid for SuperSU Pro and use it on my other devices
2) Flashfire providers most of my custom recovery needs which Kingroot does not. There is an argument for Flashfire being decoupled from SuperSU but not the development overhead when you flash an updated firmware ( e.g. B0E2 to B0E3). Flashing an upgrade requires the preservation of the root manager. I want OS updates that automatically preserve root so need Flashfire. Of course I've not mentioned other Flashfire features but I'm trying to stay relevant to the topic.
3) SuperSU's policies have provided methods to work around Samsung's bootloader SELinux enforcement. Without it I would not be able to use Viper4Android and an Ext4 formatted OTG microSD card.
I would have been happy to donate money to Kingroot for their rooting service but to the best of my knowledge they do not have a donate option. I would have only done so through PayPal or the Playstore. That brings me to my hesitation to using rooting methods from sources I do not know. I can say I was hesitant to use Kingroot at all and let others be the guinea pigs. Call me paranoid but I've seen first hand and read everyday the malicious nature of the net. At least Chainfire is a known developer on the Playstore.
In the end what maybe more of a question is the lack of rights that customers who purchased, not rented, their devices have. Why are unlocked bootloaders not a right with root management built in? Where do the manufacturers get off restricting me from doing what the heck I want with my devices? Sure limit my warrenty in some way (e.g. Overclocking burnout) but if hardware becomes faulty independent of rooting why should they be off the hook?
I hope some balance/compromise can be met between these important contributors.
Sent from my SM-T800 using XDA Premium HD app
ashyx said:
Its wrong that everyone is automatically removing kingroot/kinguser without even trying it.
Click to expand...
Click to collapse
Can you say that? The main reason people do it is because of the doubt and uncertainty of something new. Getting root is one thing and people are grateful for that but running something they are not familiar let alone trust is another.
And of course as for me too this is one of my reasons:
3DSammy said:
1) I already paid for SuperSU Pro and use it on my other devices
Click to expand...
Click to collapse
.. and I'm used to using it. I should have that choice surely? And his other reasons are good and valid too.
ashyx said:
... devs like chainfire have prevented the use of kingsu with flashfire and only allows the use of his own or cwm there's no choice but to use supersu.
Now why has chainfire done that? He has basically forced people to use his own app. That's just as bad as what kingteam have done.
Click to expand...
Click to collapse
I agree and I wish they'd discuss it more. I would like to know what is really going on with all this.
ashyx said:
I bet there are loads that would have stuck with kinguser just for simplicity's sake if flashfire worked with it.
Click to expand...
Click to collapse
I'm sure but it's difficult to know how many more would. Some people just want root to get some degree of control. Not all are flashaholics. Doubt and uncertainty are more prevalent here because of the immediate perceived need to remove it as soon as possible.
ashyx said:
Neither do they prevent removal of kingroot and kinguser, it can all be cleanly removed from within kinguser.
Click to expand...
Click to collapse
If you don't mind losing root. So it's a pointless exercise and it's a kind of blackmail.
ashyx said:
As for being closed source that's no different to chainfires apps. His root solution is closed source and so is flashfire.
Click to expand...
Click to collapse
But as I say there is a basis for trust that doesn't exist with Kingroot ... yet anyway.
ashyx said:
Kingteam have been around now for a while and have gained notoriety lately because their root solutions have worked for many. If they had any dishonorable intentions I'm sure it would have come out in the wash by now, but asfaik nothing untoward has happened to anyone.
Click to expand...
Click to collapse
Let's just turn on [paranoia mode] for a moment. They aren't doing anything now perhaps they just want to get as many devices running it then on a future update ..... [/paranoia mode off]
3DSammy said:
I would have been happy to donate money to Kingroot for their rooting service but to the best of my knowledge they do not have a donate option. I would have only done so through PayPal or the Playstore. That brings me to my hesitation to using rooting methods from sources I do not know. I can say I was hesitant to use Kingroot at all and let others be the guinea pigs. Call me paranoid but I've seen first hand and read everyday the malicious nature of the net. At least Chainfire is a known developer on the Playstore.
Click to expand...
Click to collapse
Exactly the point. Again what is their motivation? What are they getting out of all this furious hard work on multiple devices? I looked at the purify thread - it's a fully responsive engagement of support which is not unlike a company that has a paid product out there and keen to support it for more sales.
Cloud servers, a large (don't know) team of people? Often devs like Chainfire have little time to engage on this level, they are too busy on the product AND with their own lives / jobs. This is not their full time job in most cases.
This psychology isn't unusual. If someone came to you and offered you a free lunch you are going to be suspicious right? The first thing you are going to think of is 'what's in it for them'. Right or wrong this is how we work.
3DSammy said:
I'm not protecting them in anyway just understanding their point of view, put it this way how many how have used their root exploit then clicked the link to their XDA thread and thanked them?
Probably not many, credit were credit's due I say.
Hard work deserves some recognition. Maybe I should add the link in my root thread.
Click to expand...
Click to collapse
You are right - their threads do have a lot of thanks but perhaps not nearly as many as have used their solution - perhaps because of threads like yours where you provide a solution for a particular device so we don't automatically go to the Kingroot thread and leave our thanks. But bear in mind that the appearance of threads like yours in the first place were to tell people how to get rid of Kinguser after rooting.
Yes put a link and prompt to give thanks to them it's right.
For my part I would like to see some pressure or prompting for both parties to get something sorted out. Kingxteam to stop throwing toys out of the pram and writing restrictive code into their apps and Chainfire et al to come out and discuss their own restrictive policies and explain their concerns.
Welcome to a free world.
Kingroot are free to make their software anyway they want.
Chainfire is free to make his software any way he wants.
You (the user) is free to use one or the other or neither if you want.
If you dislike how kinguser is handeling this situation, but you still want a way to root without tripping knox then, you are free to design and write that code yourself.
Also as for what is in it for the kingxteam remember google, facebook, and quite a few others made products with not very solid monetarization ideas and now they are worth quite a bit. Much of the internet age has been make a product many ppl use and figure out a way to turn a profit afterwords.
Agreed, user choice at the end of the day, we get this same attitude in the HTC forum regarding sunshine s-off.
If you don't like it don't use it or remove it, they don't stop you doing that.
As for the fear factor of using an unknown app, isn't that what millions of people do everyday when installing apps on their device?
The average user never pays any mind to the permissions some of those apps use.
If it works they use it, simple as.
If your happy to let an exploit hack your device and gain high level privileges to it you can't be that concerned with Security otherwise you wouldn't root in the first place.
Too much paranoia going on here me thinks.
Personally I don't give a fig about kingteam planting a time bomb on my device, what's the worst that can happen? Once I get root I can weed out any naughty stuff.
Today's devices are becoming very secure for the average user, but the tinkerers don't like that, so what do the majority do? Root, flash custom kernels, Roms and recoveries and override all that security that's been implemented.
And were worried about a couple of little apps? Come on.
acdbrn2000 said:
Welcome to a free world.
Click to expand...
Click to collapse
There's always someone who'll come up with the age old saying of 'well if you don't like it don't use it.'
Frankly there's not a lot left to say to such posts and that is probably a good point to leave it.
Well it's quite interesting to read this over a year later and seeing how Kingroot has an app in the play store but I have looked everywhere and it's installed as a system app on my phone, I was actually researching FlashFire hoping to be able to get an OTA update and now I am looking to uninstall KingRoot 5.0.0 to go back to an older version of KingRoot. I would like to be able to switch out KingSU for supersu. But each belongs to each developer.
So, after looking around the threads, I've noticed that it is apparently possible to root an S6A running the 5.02, which mine is, because I never bothered to update it. However, I only found bits and pieces of info, and am in need of a clear guide if possible. I am only a poweruser, and my programming knowledge is limited to gaming mods and one time when I made a batch file to use my printer as an alarm clock, so I need something I can understand as a lowly wannabe nerd. Anywho, I'd be very grateful to anyone who could help me out by explaining the process. Help me XDA-Developers, you're my only hope.
P.S. I'm not overly concerned with voiding a warranty or messing up Knox, I use a BlackBerry as my primary device and as such all my important junk is on it, so as long as I can de-bloat and use root apps, I'll be very happy.
P.P.S. I apologize in advance if I overlooked a good rooting guide, I looked around for a good ten minutes before posting this, but didn't see anything, however this may simply be due to my own ineptitude.
P.P.P.S. Also, my device doesn't have a SIM, I use it as wifi only, I don't know if that's important, but I thought I might should mention it.