Okay, what one-click root method, if any, can be applied after the latest OTA update (1.70.605.0)? I just bought the phone already updated, and I cannot find if there is one compatible. I'm to much of a noob to root without one click, so don't send me in that direction please! Any help is appreciated, Nick
Easyroot is about as close as you're going to get to a one-click for the Thunderbolt.
It should still work fine after the latest OTA.
Easyroot: http://forum.xda-developers.com/showthread.php?t=1005292
Instructions: http://forum.xda-developers.com/attachment.php?attachmentid=552281&d=1301123842
Has this worked for you with the Thunderbolt ?
Or you could just go to http://revolutionary.io Those easy root scripts are notoriously unreliable. I would also recommend getting ADB up and running and learn to use it and fastboot as well. They can be life savers when you get in trouble.
Sent from my HTC Thunderbolt
Yea, I saw Rev had another update for Tbolt yesterday so maybe it will work nicely for you.
Seriously though...if you're looking at Easyroot vs Manual method....learn from other panicking users and go the Manual route.
http://forum.xda-developers.com/showthread.php?t=996616
Absolute_Zero said:
Yea, I saw Rev had another update for Tbolt yesterday so maybe it will work nicely for you.
Seriously though...if you're looking at Easyroot vs Manual method....learn from other panicking users and go the Manual route.
http://forum.xda-developers.com/showthread.php?t=996616
Click to expand...
Click to collapse
Disagree. I looked at the manual vs easyroot method, and if your goal is to just flash custom roms, then theres nothing useful about learning ADB and what any of it means/does. Thats like saying to use windows you should learn C++.
RunNgun42 said:
Disagree. I looked at the manual vs easyroot method, and if your goal is to just flash custom roms, then theres nothing useful about learning ADB and what any of it means/does. Thats like saying to use windows you should learn C++.
Click to expand...
Click to collapse
No. That isn't accurate by any stretch of the imagination. It's more accurate to say if you want to use Windows, you should learn something about command line DOS. You absolutely SHOULD and I'm fairly certain most devs would agree. Please don't advocate ignorance.
I'm disappointed by the OP's flat rejection of obtaining new skills to perform a somewhat technical task and I think we, as a community, should not support that attitude, but rather foster an environment of support and encouragement towards increasing knowledge and experience.
Furthermore, the Revolution and AlphaRevX sites are still down which means obtaining a beta key to use their tools will not be possible. When these or other resources become reliable in the eyes of their creators as alternatives to the jcase method, and I have time to evaluate them, I will be adding them to my thread stickied at the top of this Q&A section. Until then, if your concern is to backup data before a manual root, then I'd suggest TwistedUmbrella's tools to perform that task.
RunNgun42 said:
Disagree. I looked at the manual vs easyroot method, and if your goal is to just flash custom roms, then theres nothing useful about learning ADB and what any of it means/does. Thats like saying to use windows you should learn C++.
Click to expand...
Click to collapse
While the comparison of learning C++ to typing (or copy/pasting) ADB commands that are listed verbatim in procedural order for you is a spot on* comparison, I will also have to disagree.
The problem is that when these scripts error/do not work (and they do quite often) the user has no idea whatsoever the step that caused the error. I'm going to have to say that the majority of users on here (along with a large number of users that panicked when the auto rooting scripts screwed up) will agree that the manual method is the way to go. Not only does it help you troubleshoot if something didn't work and therefore get help faster (b/c you know what command errored) but the failure rate is much lower to begin with. The manual method is actually very quick and painless (as many users have noticed after trying the auto scripts). Maybe it's just people's avoidance of anything that says "manual".
I suppose I (along with a majority of users here) will have to agree to disagree with you.
*read "not even remotely reasonable"
RunNgun42 said:
Disagree. I looked at the manual vs easyroot method, and if your goal is to just flash custom roms, then theres nothing useful about learning ADB and what any of it means/does. Thats like saying to use windows you should learn C++.
Click to expand...
Click to collapse
C++ is much harder to learn than adb (and perhaps one of the harder languages period to master due to the leadway it gives a user to screw things up). C++ you actually learn something useful. I dont think anyone will hire you because of your 1337 adb copy/paste skills alone
Overall I'd say that was a metaphor fail. I'd say learning to use adb is more like learning to use cmd.exe. Mostly useless unless you really really really need to do something out of the ordinary.
*full disclosure: i hate cmd.exe and use cygwin when on windows
RunNgun42 said:
Disagree. I looked at the manual vs easyroot method, and if your goal is to just flash custom roms, then theres nothing useful about learning ADB and what any of it means/does. Thats like saying to use windows you should learn C++.
Click to expand...
Click to collapse
So while your flashing those ROMS you end up with a bad flash and bad luck loving to come all at once your recovery gets corrupt as well. On top of that you don't have any recent backups for apps or a nandroid. Now the link to the bootloader flashable recovery is down. So now what?
Not the most likely scenario but still very possible. I guarantee when someone says "oh that's easy just fastboot a recovery on" your going to be wishing you had learned how to fix your phone before you messed it up.
Sent from my HTC Thunderbolt
JBO1018 said:
So while your flashing those ROMS you end up with a bad flash and bad luck loving to come all at once your recovery gets corrupt as well. On top of that you don't have any recent backups for apps or a nandroid. Now the link to the bootloader flashable recovery is down. So now what?
Not the most likely scenario but still very possible. I guarantee when someone says "oh that's easy just fastboot a recovery on" your going to be wishing you had learned how to fix your phone before you messed it up.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
Sure you could end up with a bad flash as a result of improper script. But if you were just copy/pasting command lines then you still dont know wtf to do, so what difference does it make? In fact, since all of you are advocating just copy/pasting one line at a time, exactly what the hell are you learning from this process? You still have no idea what any of the commands mean or what they're doing, you're just taking 10x as long to do what a batch file does for you.
Because if you copy and paste the commands one by one and you run into a problem at least you know what step it happened on. So now when you go asking for help you can provide some useful information to those trying to help you.
Revolutionary makes all that moot in a way. The fact remains however you can still very easily end up in a situation where you need to fastboot a recovery on. So having ADB and fastboot installed and working plus knowing how to use them are definitely things EVERYONE who is rooted SHOULD know.
Sent from my HTC Thunderbolt
I also just found another damn good reason to know how to use ADB and fastboot. Until Alpharev and Unrevoked release an s-on tool the ONLY way, I'm fairly certain, to get back to stock s-on after using Revolutionary or the hard patched hboot is with fastboot and a special command.
Sent from my HTC Thunderbolt
loonatik78 said:
..the Revolution and AlphaRevX sites are still down which means obtaining a beta key to use their tools will not be possible. When these or other resources become reliable in the eyes of their creators as alternatives to the jcase method, and I have time to evaluate them, I will be adding them to my thread stickied at the top of this Q&A section.
Click to expand...
Click to collapse
Hmm.. pardon my confusion, but I just came back from a jcase thread on how to root and in red letters, it says NOT to use that method anymore.. that it was outdated. But if the Revolution and AlphaRevX methods are not available then the jcase method is really the only option.
I am all for learning how to do this. I never was a monkey at a keyboard that just followed a flow chart to solve a problem, I want to know what I am doing. But while I am still reading and learning, it would be helpful to know what I am reading is correct, up to date, and not out of date as I am no expert at rooting yet. Maybe a different disclaimer on that post is in order?
Hot Carl said:
Hmm.. pardon my confusion, but I just came back from a jcase thread on how to root and in red letters, it says NOT to use that method anymore.. that it was outdated. But if the Revolution and AlphaRevX methods are not available then the jcase method is really the only option.
I am all for learning how to do this. I never was a monkey at a keyboard that just followed a flow chart to solve a problem, I want to know what I am doing. But while I am still reading and learning, it would be helpful to know what I am reading is correct, up to date, and not out of date as I am no expert at rooting yet. Maybe a different disclaimer on that post is in order?
Click to expand...
Click to collapse
I believe he meant the rest of the post was outdated and to use revolutionary.io as of August 14th.
The old method will still work. It just does not give you the opportunity to save your apps and data like revo will.
Related
Hi All,
I have been checking a lot of ROM's recently i have find 2-3 settings in all ROM's which might sound a good choice for dev's however i am not sure whether they should be the same for user or not.
Some of the samples include
Code:
chmod 0777 /system
and all internal places.
this effectively allows us to do a adb push easily and without any hassels however per my study this allow just about anyone to mingle with any file whatsoever on my system.
Note : Having root of my own device to tinker with it is one thing. and handing over my device all permissions to someone else is another thing.
also another setting which bothers me is
Code:
ro.secure=0
which effectively allows adb to open shell in root mode directly.
can any dev help me in understand is this necessary for normal users.
also the reason why this thread is here is coz this needs discussion as this could very well turn out to be a security issues, as android platform is starting to get the limelight so will be getting eyes of both good and bad too....
also would love if someone can help me in compiling tips for normal users what they need to do and not do.
example
USB debugging should only be enabled when it is needed and not everytime.
Mod's I hope i am not voilating any rules by posting this here.
My point of view is cleary no and the obvious reason for that is that most users dont really know what they're doing, just try (most of the times to reach performance) something that someone who knows what are doing to get this or that.
I think what needs to be done is something like linux system.
You may have root but to get some modifications at least should appear some kind of msg or password needed like super root (is this the name? Cant remember, but you know what im talking )
Edit:
I wonder with some behavior of some guys and with super root access that de had what could happen to the most of users around here if we have a real bootloader crack instead of bypass. Probably need to be rich to buy a new like avery week
Cheers old IBM'ER friend
Sent from my X10i using Tapatalk
Wait, rendeiro, I think you meant Super User. But SU=Root. SU is just a method to make things simpler and safer as logging in directly as root is very dangerous.
@OP -- by CHMOD-ing the system folder to 777, you're completely vulnerable. 777 basically allows everyone to access it.
I'm not sure about the ro.secure=0 setting, but the default value is 1 instead of 0, root exploits change the value to 0 -- which lowers the security, hence allows you to be root. I think this value is also available in the kernel, just like what D did with Arc's insecure kernel -- yes, it makes the kernel insecure to allow you to root your phone.
@Hzu
You're write about the name I just forgot it since I wont use linux for about four years (since I work where im on now) but I think you get my point
Cheers
Sent from my X10i using Tapatalk
But you are still right though, people messing with the system without knowing what they are doing, and then blames the system for corrupting.
Seems like OP has did research, it should be OK for him to continue his research.
Hzu said:
Wait, rendeiro, I think you meant Super User. But SU=Root. SU is just a method to make things simpler and safer as logging in directly as root is very dangerous.
@OP -- by CHMOD-ing the system folder to 777, you're completely vulnerable. 777 basically allows everyone to access it.
I'm not sure about the ro.secure=0 setting, but the default value is 1 instead of 0, root exploits change the value to 0 -- which lowers the security, hence allows you to be root. I think this value is also available in the kernel, just like what D did with Arc's insecure kernel -- yes, it makes the kernel insecure to allow you to root your phone.
Click to expand...
Click to collapse
thats what i also thought and that's why posted here to make everyone atleast think once.
ro.secure setting i understand is to allow adb to run as root or not... basically ro.secure 1 disallows pushing to /system... also it puts you to $ prompt and you need to manually su.
Another thing i notices is we see a lot of update.zip's floating around i am not puting a question mark on anyones ethics however i suppose there should be some mechanism to check what's inside the zip or what that zip will do user should be aware of the stuff that may happen... I will try to write something in this regard in case people agree.
basically i want user to know
1) what files will be tampered specially bin xbin etc folder stuff
2) shell scripts executed.
3) partition format or permission change specially something like 777 stuff should be indicated.
and ya i will keep checking all these, i don't have any plan on launching a ROM however will keep a close eye on what others are cooking.
anantshri said:
thats what i also thought and that's why posted here to make everyone atleast think once.
ro.secure setting i understand is to allow adb to run as root or not... basically ro.secure 1 disallows pushing to /system... also it puts you to $ prompt and you need to manually su.
Another thing i notices is we see a lot of update.zip's floating around i am not puting a question mark on anyones ethics however i suppose there should be some mechanism to check what's inside the zip or what that zip will do user should be aware of the stuff that may happen... I will try to write something in this regard in case people agree.
basically i want user to know
1) what files will be tampered specially bin xbin etc folder stuff
2) shell scripts executed.
3) partition format or permission change specially something like 777 stuff should be indicated.
and ya i will keep checking all these, i don't have any plan on launching a ROM however will keep a close eye on what others are cooking.
Click to expand...
Click to collapse
Even though I tend to agree with the above posts, I have to say that there is also another side that we should all consider.
Each and every one of us, should try and be "educated" on Android. XDA forums can be a mess, but with patience and a little time every now and then, we can all learn more about what our phones do and how.
I've seen people eager to flash an update.zip with a tweak that they have ABSOLUTELY no idea what it does. Sometimes we just sit back and wait for everything to be done for us.
I am always actively interested in development and I learn new things every day.
Developers give us the tools, we need to learn how to use them.
Xperia X10i via Tapatalk
rendeiro2005 said:
I think what needs to be done is something like linux system.
You may have root but to get some modifications at least should appear some kind of msg or password needed like super root (is this the name? Cant remember, but you know what im talking )
Click to expand...
Click to collapse
Is that not what the superuser app does?
I'm not a dev but I kno enough about linux to want rw to /system but I agree most users are stupid (well at least don't know what there doing). Apps that let you do damage to /system like root explorer allows you to easily mount it rw anyway. I can't see much extra danger having it always rw when you've already got root.
Each and every one of us, should try and be "educated" on Android. XDA forums can be a mess, but with patience and a little time every now and then, we can all learn more about what our phones do and how.
I've seen people eager to flash an update.zip with a tweak that they have ABSOLUTELY no idea what it does. Sometimes we just sit back and wait for everything to be done for us.
I am always actively interested in development and I learn new things every day.
Developers give us the tools, we need to learn how to use them.
Click to expand...
Click to collapse
Agree ppl flashing roms should take a little time to learn about what they're doing but ppl are too lazy and want a quick fix. But if someone soft bricks their phone because they don't understand what their doing and don't read the instructions properly then its their fault and not the devs. But its not hard to connect to PC companion and repair and they've learnt a valuable lesson in the process.
No, the superuser app don't ask for password. Like in linux distros for the pc, you can set whether to have password or not, this can be done via visudo. Just google for visudo then you will understand.
Sent from my X10 using XDA App
Yeah the post requested a message or password, superuser provides a message. Yeah I use linux for a PVR so know what you mean.
resurrecting an old thread just to inform all dev's i have compiles some of the issues that i see could be a potential security issues.
http://blog.anantshri.info/whitepaper-security-issues-in-android-custom-roms/
hope this could help making ROMs more secure.
From http://blog.anantshri.info/whitepaper-security-issues-in-android-custom-roms/#comment-66733
"
Hi Anant
After i´ve read your white paper i got 2 conclusions:
1. you`re absolutely right and explain it as it should but…
2. If Devs consider all that why develop anything?
As principle i think you´re right but that fact is if any rom will be developed as “closed” almost anyone use it and no matter what make you develop you certain won´t develop for 1/2 guys/gals. For that we have stock ones
Now. I can agree with something like a big alert on every rom development section/thread about the potential risk by install an “open” rom but more than that it will kill all development in the end
Cheers pal
"
Perhaps the way forward is to have the warnings you have mentioned, but also encourage our devs to have a "security tester", another dev with the time and skill to give approval to the zip package. Zips have worried me too. This is a community after all, security is in all our interests.
Sent from my X10i using XDA App
Hi All,
few things to clarify.
see i am not against development.
the point is when we have developer style softwares like say flashtool its just too good for people like us.
now look from a prospective of a person who is visiting this forum just to get a new rom coz he is told they are good.
he is handling his faith to us.
in this case lets say we say in flashtool for example
after rebooting, check usb debugging and unknown source.
however we never say to disable it after you are done with flashtool or tell that this could be a problem.
also most of the rom's have ro.secure set to 0. Good for dev's i loved it.
but no use for a normal user besides the prospects that due to ignorance a person could actually move in and install a backdoor or malware in.
All i am saying is we should have something like two profiles
1) if you are supporting dev launch this
2) if you are normal user use this.
hope you all get my point.
besides that issues like custom recoveries. right now as i said the efforts are towards improving them and people might look at security prospective after that.
I know some of you might say if a person is visiting a after market forum he should be smart enough to read a bit.
that's idealism, not reality.
NOTE :
I am excited about 4.0 ICS coz with that comes features like disk encryption etc.
anantshri said:
Hi All,
few things to clarify.
see i am not against development.
the point is when we have developer style softwares like say flashtool its just too good for people like us.
now look from a prospective of a person who is visiting this forum just to get a new rom coz he is told they are good.
he is handling his faith to us.
in this case lets say we say in flashtool for example
after rebooting, check usb debugging and unknown source.
however we never say to disable it after you are done with flashtool or tell that this could be a problem.
also most of the rom's have ro.secure set to 0. Good for dev's i loved it.
but no use for a normal user besides the prospects that due to ignorance a person could actually move in and install a backdoor or malware in.
All i am saying is we should have something like two profiles
1) if you are supporting dev launch this
2) if you are normal user use this.
hope you all get my point.
besides that issues like custom recoveries. right now as i said the efforts are towards improving them and people might look at security prospective after that.
I know some of you might say if a person is visiting a after market forum he should be smart enough to read a bit.
that's idealism, not reality.
NOTE :
I am excited about 4.0 ICS coz with that comes features like disk encryption etc.
Click to expand...
Click to collapse
Hi bro
i did get your point! maybe i didn´t explain my point very clearly sorry if i didn`t
i perfectly support your idea...as you say ... "that's idealism, not reality."
like i said before, may devs should include those issues on there threads, i agree, but more than that...do no know it´s like ...hey! i got a custom rom but...i can´t do nothing...
cheers R
Crowds said:
Hi bro
like i said before, may devs should include those issues on there threads, i agree, but more than that...do no know it´s like ...hey! i got a custom rom but...i can´t do nothing...
cheers R
Click to expand...
Click to collapse
actually that's my point
keeping
say ro.secure=1
disabling usbdebugging, unknown sources or portecting custom recoveries
I still see a normal user can use all the benifits of rooting inside the device.
i am right now focusing on what third party can do when phone is giving out data outside.
well we both agree that its a point that needs some consideration so i think i have succedded in making my point heard.
anantshri said:
actually that's my point
keeping
say ro.secure=1
disabling usbdebugging, unknown sources or portecting custom recoveries
I still see a normal user can use all the benifits of rooting inside the device.
i am right now focusing on what third party can do when phone is giving out data outside.
well we both agree that its a point that needs some consideration so i think i have succedded in making my point heard.
Click to expand...
Click to collapse
ok, ok, you won
but regarding that ro.secure
i understand your explanation on white paper and try to include on my current build.prop file but...can´t see any diference why? my phone "behaves" exactly the same way as before
Crowds said:
ok, ok, you won
but regarding that ro.secure
i understand your explanation on white paper and try to include on my current build.prop file but...can´t see any diference why? my phone "behaves" exactly the same way as before
Click to expand...
Click to collapse
change in ro.secure need to go to ramdisk.
also after that setting try pulling /data/data or /system in adb.
nothing except adb's default behaviour will change.
ive read the thread in the general forum for noobs.
but i still dont quite understand all these things and what purpose they serve.
im SUPER new with all this stuff. so my apologies.
could someone help a brother out?
what is your question specifically?
just curious about what they are and do basically.
kevinallen4325 said:
ive read the thread in the general forum for noobs.
but i still dont quite understand all these things and what purpose they serve.
im SUPER new with all this stuff. so my apologies.
could someone help a brother out?
Click to expand...
Click to collapse
I'll try and help.
First you must ROOT your phone. This basically grants you access/permission to FIDDLE with a lot of things you can't normally. I use the word *fiddle* loosley, meaning you can install root tools (like overclock) custom Roms, change system settings, flash themes... the list goes on. It's kind of like the equivalent to "jailbreaking"
Rooting is the "first and foremost"... basically do this first. and all other things follow.
kevinallen4325 said:
just curious about what they are and do basically.
Click to expand...
Click to collapse
Well the sticky in the main forum really is a good place to start, as all these terms are defined there:
http://forum.xda-developers.com/showthread.php?t=1483113
As well as step-by-step instructions how to root. That should get you started!
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
kevinallen4325 said:
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
Click to expand...
Click to collapse
It is much more than that. I wrote this out before, so I will copy it again:
People have problems when rooted because they are not careful or do not know what they are doing. Rooting gives you (to put in Windows terms) full Administrator rights to your phone. With this right comes responsibility, so you must be careful and do research. This is why rooting also voids the warranty. The phone is now open for the user to do whatever they want, and circumvent any restrictions put on the phone by the manufacturer (including those in place to prevent harm to the device). But like a computer with Admin rights, rooting allows you to install any application, any "OS theme", and tweak the hardware to do what YOU want with it, not what the manufacturer wants.
So please be sure to READ READ READ all you can before you start!!! You don't want a $600 phone coaster. Just browse the forums for a couple weeks and learn from the posts.
kevinallen4325 said:
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
Click to expand...
Click to collapse
It depends what you consider a benefit. Sure..theming can be a benefit, but rooting provides the gateway to address any negative or less than ideal aspects of a device. For instance, The Note has been perceived as being somewhat laggy. So rooting allows you to free up system resources by eliminating unneeded bloatware that you can't remove if you remain stock. Also the lagginess has been addressed by overclocking, modding and building kernels that do specific things and of course making custom roms. The Note is still very early in the developmental process, so many things to improve the user experience of the device will become available over the course of time....but it all starts with being rooted.
Sent from my Samsung Galaxy Note LTE™
kevinallen4325 said:
ok so root first. got it. would any of this benefit my phone in anyway? or is it mainly just to put custom themes and such on?
Click to expand...
Click to collapse
Android isn't like iOS. I had an iPhone for four years before my Note and I know where you coming from. What the other guy was saying is that rooting can be viewed similar to jailbreaking, but it is kind of completely different. You don't need to be rooted to use themes (or most of the stuff on Cydia). Rooting allows you to back up apps, flash custom ROMs, etc. Otherwise, you most likely don't need root.
tbran said:
It depends what you consider a benefit. Sure..theming can be a benefit, but rooting provides the gateway to address any negative or less than ideal aspects of a device. For instance, The Note has been perceived as being somewhat laggy. So rooting allows you to free up system resources by eliminating unneeded bloatware that you can't remove if you remain stock. Also the lagginess has been addressed by overclocking, modding and building kernels that do specific things and of course making custom roms. The Note is still very early in the developmental process, so many things to improve the user experience of the device will become available over the course of time....but it all starts with being rooted.
Sent from my Samsung Galaxy Note LTE™
Click to expand...
Click to collapse
if i were to root it and do whatever else would that affect the notes ability to update itself when the time comes?
like if i were to put some custom rom or whatever on it and lets say ics came out (lulz) would it still be able to update to it, and would it basically remove everything i did to it
kevinallen4325 said:
if i were to root it and do whatever else would that affect the notes ability to update itself when the time comes?
like if i were to put some custom rom or whatever on it and lets say ics came out (lulz) would it still be able to update to it, and would it basically remove everything i did to it
Click to expand...
Click to collapse
Trust me, if you go the root and custom rom way, you will never install an official update. not because you can't, but because it will be leaked and debloated months before it is official.
i installed saurom. with and ics theme. i like it alot. but i cant get into setcpu or any program that requires root access. which is kind of an issue. no one else seems to be having that as an issue.
I rooted my Note a couple days ago and am still trying to figure out the benefits of doing so. I guess just spend time reading through this forum for the answers. That's what I am doing, but so far I see no benefit at all. The phone does all I want it to do so far. Maybe I am missing something.
Also, When i run quadrant, the scores are consistently lower after rooting the device then they were before. Not sure why though.
You are correct that the Note and newer phones may need no help. Not like two years ago. But, the big advantage to rooting even if you don't want to flash roms is Titanium Backup for app mgt and nandroids or full image backups--imho. The other like mentioned is earlier os releases. I have had ICS on my N1 for quite awhile and is still not on most new phones.
Ken
kevinallen4325 said:
i installed saurom. with and ics theme. i like it alot. but i cant get into setcpu or any program that requires root access. which is kind of an issue. no one else seems to be having that as an issue.
Click to expand...
Click to collapse
If you are sure you are rooted, a dialog box with a little Android head wearing an eyepatch will pop up asking if you want to allow the application to have root access. You must allow it here.
ok, i have a question, should i root my lg thirve (lg optimus one) just because i want to go from stock froyo to gingerbread made by cyanogen-mod.
thats all i would want, because my phone is not getting the update, and to get gingerbread i would need to root.
so should i do this, what are the dangers of it, i mean will my phone be vulnerable to dangerous things, will it break or mess up in any way?
No dangers, really. But yes, root. If you are interested in overclocking, tweaking, and installing any app that requires root (just search "root" on market and see what goodies come up), you should root, no questions asked. I highly recommend CyanogenMod as there are so many additional and useful features and it is pre-rooted (obviously). If you don't like modding or experimenting, then stick to the stock ROM.
I gotta be honest with you, when I first landed on the Android world I made myself that very same questions over and over again, until one day I said "what the heck!" and done it.
To be truth, isn't that big of a deal, rotting isn't difficult and isn't bad, you just gotta be carefully about what you do because you'r having access to the System folder, so you can really harm your phone, but if you don't mess up with it, you have nothing to worry about.
Some apps need root access because they use the system folder to make changes, so don't simply install any app that request you so, just those that are known and that you need.
So, in conclusion, Root your device, just don't go on the system folder and make changes if you have no idea what you'r doing.
Root is good and healthy to your phone. It gives you more freedom on using your phone. Really, it lets you do a lot more things that you can't do it on an unrooted stock ROM.
Most of us did that before, and it wont harm you phone's health provided that you don't root/unroot too many times in a week (it is similar to what my parents told me when I am still young and innocent)
Rooting process in most cases wont brick your phone unless you are trying to flash a rooted ROM without knowing it.
But anyway, if you want to try something new, you need to take the risk. And don't blame on others when you bricked your own phone. Maybe you can search on youtube videos or websites for those step by step rooting guides for your phone.
feenius danger
Yes.. root its worth it.. Speeds up your device by removing unnecessary crap, can customize the look much more, rather easy to do.. Just follow a guide on here and good luck .
YES!!!!!!!
rooting you phone adds infinitely more possibilities, and makes your phone a lot faster
also, cyanogen-mod is an amazing ROM,
go ahead, give it a try,
JUST REMEMBER BACK UP EVERYTHING BEFORE FLASHING CYANOGEN-MOD
good luck
dosage1 said:
Yes.. root its worth it.. Speeds up your device by removing unnecessary crap, can customize the look much more, rather easy to do.. Just follow a guide on here and good luck .
Click to expand...
Click to collapse
That's right, there a quite a few (a ton!) sites describing the benefits of it:
http://www.androidcentral.com/root
http://www.appsgeyser.com/blog/2012/03/20/should-i-root-my-android-phone/
http://www.androidpit.com/en/android/forum/thread/403299/So-what-exactly-is-rooting-and-is-it-for-me
http://www.addictivetips.com/mobile/top-10-reasons-to-root-your-android-phone-2/
The only thing I recommend is that you know what you're doing. If thats not the status: In the forums are a lot of posts
Definitely go for it.
The optimus one especially benefits from rooting/applying a new, better rom.
Don't root and unroot your phone too many times.Thats the caution,otherwise as said it gives you more control over your hardware than unrooted phone.
Sent from my LG-P350 using XDA
Gaining full control of your device is a big advantage. In addition to this some really useful apps just run with root.
ricky1001 said:
Don't root and unroot your phone too many times.Thats the caution,otherwise as said it gives you more control over your hardware than unrooted phone.
Sent from my LG-P350 using XDA
Click to expand...
Click to collapse
Actually, if that were true, ROM developers would have long given up and we wouldn't have any of the awesome ROMs floating around out there today. There's absolutely nothing wrong with rooting and unrooting repeatedly, as long you follow the correct procedure every time. Although why anyone would do that stumps me. Either you like your phone rooted, or not.
@singular9:
First off, "upgrade" is a very subjective term. Are you certain the ROM you're looking at will give you significant advantages over the one your phone's running now? While I don't doubt that the people behind the CM ROM for your phone are doing some brilliant work, always assume that something may go wrong. (Unlike Apple, other phone manufacturers source their hardware from all sorts of different places. Two phones, same model may have differently branded components.) If something DOES go wrong, are you prepared to undergo the arduous process that unbricking a phone will involve?
I'd say root your phone if - and ONLY IF:
1. You're a careful person who will read instructions and follow them to the letter, in the order they were set;
2. You're prepared to read up on what "root" is, what the terms used are, and accept that your "upgrade" may not quite offer you the benefits you were looking for (whatever they are, as you didn't specify)
If you're okay with the above, then yeah, I guess I'd say go ahead. My phone's rooted - I love it, and loved every step of the journey I took to root it.
terradune said:
Actually, if that were true, ROM developers would have long given up and we wouldn't have any of the awesome ROMs floating around out there today. There's absolutely nothing wrong with rooting and unrooting repeatedly, as long you follow the correct procedure every time. Although why anyone would do that stumps me. Either you like your phone rooted, or not.
Click to expand...
Click to collapse
haha, it is a joke dude, don't take it seriously. I don't see any reason for unrooting android unless you are preparing to send the phone back for warranty or get it repaired by its manufacturer and tell them : "ohh, I dunno what happened, it just stop working by it self this morning".
Cheers!
Root is the better way to take totally control of your phone !
Absolutely yes!
Yes U should, but read each instructions carefully before u root ur device.
.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
I'm contemplating getting this phone, and being fully-rooted with s-off is a very important part of a phone experience for me. I have read a lot of threads saying that the s-off is "in the works, and will just take time", but are people being overly optimistic? Is it too good to be true considering that no modern HTC device without an SD card has achieved s-off, or do the developers actually feel like they're making headway? Finally, if s-off is never achieved, what kind of features would we be missing compared to an s-off device?
By the way, I would really like to thank the dev's for working so hard on the root and s-off. Its amazing what they've accomplished in such a short time.
TL;DR: Are the s-off rumors overly optimistic?
Alidaco said:
I'm contemplating getting this phone, and being fully-rooted with s-off is a very important part of a phone experience for me. I have read a lot of threads saying that the s-off is "in the works, and will just take time", but are people being overly optimistic? Is it too good to be true considering that no modern HTC device without an SD card has achieved s-off, or do the developers actually feel like they're making headway? Finally, if s-off is never achieved, what kind of features would we be missing compared to an s-off device?
TL;DR: Are the s-off rumors overly optimistic?
Click to expand...
Click to collapse
DSB said it was in the works, but as adrenalyne stated i wouldnt get hopes up unless Jcase says its coming...
Where can I go to see the dev threads for this stuff so that I can keep updated?
Sent from my Incredible 2 using xda app-developers app
Alidaco said:
I'm contemplating getting this phone, and being fully-rooted with s-off is a very important part of a phone experience for me. I have read a lot of threads saying that the s-off is "in the works, and will just take time", but are people being overly optimistic? Is it too good to be true considering that no modern HTC device without an SD card has achieved s-off, or do the developers actually feel like they're making headway? Finally, if s-off is never achieved, what kind of features would we be missing compared to an s-off device?
TL;DR: Are the s-off rumors overly optimistic?
Click to expand...
Click to collapse
Worse case scenario, you will have to flash kernels through fastboot, and you will have limited access to /system. So yeah, we are all hoping for s-off, but we can still do quite a bit even if we are stuck with s-on.
Dri94 said:
DSB said it was in the works, but as adrenalyne stated i wouldnt get hopes up unless Jcase says its coming...
Click to expand...
Click to collapse
Didn't jcase say he wasn't involved with the people trying to get s off.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Didn't jcase say he wasn't involved with the people trying to get s off.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I don't believe he's working on it, but if it's close, or accomplished, he'll know about it.
Alidaco said:
Where can I go to see the dev threads for this stuff so that I can keep updated?
Click to expand...
Click to collapse
There's an inner circle working on S-OFF. You will not hear about it until it's done.
seeingwhite said:
Worse case scenario, you will have to flash kernels through fastboot, and you will have limited access to /system. So yeah, we are all hoping for s-off, but we can still do quite a bit even if we are stuck with s-on.
Click to expand...
Click to collapse
We can already do quite a bit if you know the commands in adb.
trickster2369 said:
I don't believe he's working on it, but if it's close, or accomplished, he'll know about it.
Click to expand...
Click to collapse
jcase is not working on S-OFF. The first few people he unlocked before public release are (these are the inner circle, if you will). He will certainly know when it's accomplished.
Is this entirely necessary? As far as I can tell full read/write access is achieved in recovery. Really it's kind of nice because if something blows up or you get some malicious app that claims to require root, you're safe. While the option would be nice to have, I don't really think we're limited at all as things are right now. It just takes a couple more steps.
paulguy said:
Is this entirely necessary? As far as I can tell full read/write access is achieved in recovery. Really it's kind of nice because if something blows up or you get some malicious app that claims to require root, you're safe. While the option would be nice to have, I don't really think we're limited at all as things are right now. It just takes a couple more steps.
Click to expand...
Click to collapse
The main things that we won't have is stuff like ad blocking apps, on the fly build.prop editing, the giant customization settings apps that many sense roms are coming with, etc etc
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
The main things that we won't have is stuff like ad blocking apps...
Click to expand...
Click to collapse
Adblock Plus just came out with a new app yesterday with enhanced features for rooted users: https://play.google.com/store/apps/details?id=org.adblockplus.android
paulguy said:
Is this entirely necessary? As far as I can tell full read/write access is achieved in recovery. Really it's kind of nice because if something blows up or you get some malicious app that claims to require root, you're safe. While the option would be nice to have, I don't really think we're limited at all as things are right now. It just takes a couple more steps.
Click to expand...
Click to collapse
Funny....I remember a couple months ago when people were saying the exact same phrase in the d2vzw forums. We are all sharing the same optimistic thoughts.....but in the back of our minds, we all know its a load of sh*t.....we want s-off, trust me.
Alidaco said:
I'm contemplating getting this phone, and being fully-rooted with s-off is a very important part of a phone experience for me. I have read a lot of threads saying that the s-off is "in the works, and will just take time", but are people being overly optimistic? Is it too good to be true considering that no modern HTC device without an SD card has achieved s-off, or do the developers actually feel like they're making headway? Finally, if s-off is never achieved, what kind of features would we be missing compared to an s-off device?
By the way, I would really like to thank the dev's for working so hard on the root and s-off. Its amazing what they've accomplished in such a short time.
TL;DR: Are the s-off rumors overly optimistic?
Click to expand...
Click to collapse
Do not buy a device based on what may be possible in the future. Buy it based on what is possible now. If s-off is important to you, then you do not want the DNA at this time. If you can live with the limitations, then go for it, but be careful not to turn into one of the disgruntled owners because you really wanted s-off and believed the rumors that it is "coming soon".
The kernal flashboot problem has been bypassed on the EVO 4g LTE I'm sure the devs can make their kernals S-On friendly. As far as S-On vs S-Off on the EVO there isn't much except for flashing unsigned radios through the bootloader
Sent from my EVO using xda premium
luigi311 said:
The kernal flashboot problem has been bypassed on the EVO 4g LTE I'm sure the devs can make their kernals S-On friendly. As far as S-On vs S-Off on the EVO there isn't much except for flashing unsigned radios through the bootloader
Sent from my EVO using xda premium
Click to expand...
Click to collapse
there are significant differences on this phone between dev unlocked and s-off (for those on pre release units that were lucky enough)
kernels: atm, s-off can flash in recovery, unlock in hboot (yes scripts can be done, but still)
radios: no-go on dev unlock, yes on s off
reverting to older RUU's: well none exist currently, but s off can, dev unlock cant
splash images: cosmetic, sure...but not possible on dev unlock
updating/reverting other firmware: only possible to update through a signed RUU for non s-off folks...s off folks can revert or update with just parts of the RUU that are extracted
/system access: only possible in recovery for those with dev unlock, s off can access it in android....this might not seem like a big deal to the average user...but for devs?, pretty horrid....for example, if i want to mod Rosie for some reason (landscape, app drawer, cosmetic, whatever) typically i can just adb push the apk and test it....now i'll have to boot to recovery, push the apk, reboot to android to test it (a lot more time consuming and annoying)
Dri94 said:
DSB said it was in the works, but as adrenalyne stated i wouldnt get hopes up unless Jcase says its coming...
Click to expand...
Click to collapse
I have nothing to do with s-off. I'd wait for hyuh and/or fuses to say something.
I really wouldn't buy a phone based on what you're hoping for. If s off is that important for you, I wouldn't buy it. All that does is lead to a lot of disappointments and complaining honestly. I see a whole lot of posts and entire threads on the forums where people are posting complaints about model xyz phone not having updates fast enough or not being s off, not having a different OS/UI working without bugs yet, things like that.
Buying something on hopes and dreams is a mistake in my opinion, and if fastboot flashing kernels and not having splash screens is important to you, I would buy a different phone now and get the DNA after it's s off. Any rumors or speculation that you hear is just that. The guys who are really working on it wont be posting about it much because even in a best case scenario, things change mid development as progress is made.
CharliesTheMan said:
I really wouldn't buy a phone based on what you're hoping for. If s off is that important for you, I wouldn't buy it. All that does is lead to a lot of disappointments and complaining honestly. I see a whole lot of posts and entire threads on the forums where people are posting complaints about model xyz phone not having updates fast enough or not being s off, not having a different OS/UI working without bugs yet, things like that.
Buying something on hopes and dreams is a mistake in my opinion, and if fastboot flashing kernels and not having splash screens is important to you, I would buy a different phone now and get the DNA after it's s off. Any rumors or speculation that you hear is just that. The guys who are really working on it wont be posting about it much because even in a best case scenario, things change mid development as progress is made.
Click to expand...
Click to collapse
Sir, your logic is NOT welcome here!
nitsuj17 said:
...
/system access: only possible in recovery for those with dev unlock, s off can access it in android....this might not seem like a big deal to the average user...but for devs?, pretty horrid....for example, if i want to mod Rosie for some reason (landscape, app drawer, cosmetic, whatever) typically i can just adb push the apk and test it....now i'll have to boot to recovery, push the apk, reboot to android to test it (a lot more time consuming and annoying)
Click to expand...
Click to collapse
Just to add, you can push and test, but it'll revert back on reboot. Did so many times already
QD2DC said:
Just to add, you can push and test, but it'll revert back on reboot. Did so many times already
Click to expand...
Click to collapse
Is anyone able to remove bloatware from their DNA? This revert back issue with s-on seems to prevent it.
You have to unlock it, install a recovery, root it, and you can install a debloated stock Rom or a custom Rom.
Hi all - just signed up. I'm receiving my 10 Monday. I have an Infinity and wanted to give the Nexus 10 shot as it seems like a great tablet. I'm not likely to root either one. Is there anything you all suggest to get the most out of the Nexus 10? I'm fairly new to the tablet world although have owned an android phone for several years.
Thanks!
Welcome and congrats! Here is a link someone started that shares your question.
http://forum.xda-developers.com/showthread.php?t=2023608
Sent from my Nexus 10 using Tapatalk HD
^ Great thread for starters but make sure and DO YOUR READING before you unlock and root your device -- or you will end up with a $400 makeshift frisbee disk. Unlocking your boot-loader/rooting is what makes android so much fun, I would recommend it
Derp: sounds you've rooted before, but I suppose the above statement still stands lol
TheEmpyre said:
^ Great thread for starters but make sure and DO YOUR READING before you unlock and root your device -- or you will end up with a $400 makeshift frisbee disk. Unlocking your boot-loader/rooting is what makes android so much fun, I would recommend it
Derp: sounds you've rooted before, but I suppose the above statement still stands lol
Click to expand...
Click to collapse
I did read that thread but as I said - I'm not likely to root...at least not right away.
stormricker said:
I did read that thread but as I said - I'm not likely to root...at least not right away.
Click to expand...
Click to collapse
Sounds like quite a few people are unlocking / rooting and leaving the stock ROM which is likely what I will do. I like having the freedom that Root provides to install some apps etc.
Nexus 10 will be my first tablet also, so I'll be having quite a bit of fun for the first few weeks figuring out how exactly I will be using it
TheEmpyre said:
Sounds like quite a few people are unlocking / rooting and leaving the stock ROM which is likely what I will do. I like having the freedom that Root provides to install some apps etc.
Nexus 10 will be my first tablet also, so I'll be having quite a bit of fun for the first few weeks figuring out how exactly I will be using it
Click to expand...
Click to collapse
Still a little nervous about the rooting process....and its risks. What exactly are the benefits?
stormricker said:
Still a little nervous about the rooting process....and its risks. What exactly are the benefits?
Click to expand...
Click to collapse
From what I've gathered, and from experience, I think the benefits of Root give the user a great deal more control of what goes on with his/her device -- that is, in part, what apps are accessing resources. For example, with my HTC One XL, I was able to install an app (which requires root access) that allows me to freeze apps while they are not in use -- launch them to unfreeze and use them when I need but when I'm not using, they aren't going to automatically run processes that drain my battery. I also installed a custom Kernel, and there is a root-required app that allows me to adjust my CPU frequencies and voltages to maximize battery life and performance.
I am relatively new to rooting devices, as I started in late October, but I can tell you that I have had a ton of fun doing it.
In any event, I really dont think rooting is that valuable to mainstream users if you ask me -- If you aren't looking into flashing custom ROMs or using special utilities/apps on your device then I wouldn't bother rooting/unlocking bootloader.
Since you asked risks I'll address that too: The risks are bricking (completely unusable) your device if you flash an incompatible ROM, but this is easily avoided by sticking only to flashing ROMs for the Nexus 10. You can also damage the components of your device if you overclock too much etc....Other risks are that ROMs are buggy sometimes despite the very hard work of the devs here (They are truly amazing here) but the bugs may take away from your experience potentially. There may be plenty of other risks but these are the ones I can think of so far.
I was completely unaware of root/unlock up until about 2 months ago and was completely new to the process. I was able to read great guides put together by the XDA community here that walked me through the process and I was successful in unlocking my One X and I now finally feel like I am getting the moneys worth out of my device that I payed good $$$ for.
stormricker said:
Still a little nervous about the rooting process....and its risks. What exactly are the benefits?
Click to expand...
Click to collapse
Rooting is quick and painless if you use the Nexus 10 Toolkit available in the development section! My Galaxy Nexus also has a toolkit from the same dev, makes things SO much easier/quicker.
The risks of rooting are almost non-existent. Really, if the procedure doesn't work for you, nothing changes & you just won't have root permissions. I've personally never had anything bad happen, but I'm sure there is someone out there who has tried some sketchy method to root...the methods here are far from that, just read up and follow the instructions.
Benefits are basically the freedom to remove system apps and make backups of any of your apps. There are also a ton of root apps that allow you to customize your device the way you like it. With root, you get full control and the freedom to tinker.
Nexus devices are absolutley meant for consumers who don't root or unlock, but what is great about them is if you want to do either of the latter..it is much easier to do.
Also, I suggest you try and personally compare your N10 and Infinity before you read any of the general comparison threads. lol
Oh and welcome to the vanilla side of Android! :good:
- Mac
xIC-MACIx said:
Rooting is quick and painless if you use the Nexus 10 Toolkit available in the development section! My Galaxy Nexus also has a toolkit from the same dev, makes things SO much easier/quicker.
The risks of rooting are almost non-existent. Really, if the procedure doesn't work for you, nothing changes & you just won't have root permissions. I've personally never had anything bad happen, but I'm sure there is someone out there who has tried some sketchy method to root...the methods here are far from that, just read up and follow the instructions.
Click to expand...
Click to collapse
Toolkits are a nice method for rooting for beginners, but (imo) it's better to learn how to flash (and do generally other stuff) without the need of a toolkit.
When I rooted my Nexus 10, I just unlocked the bootloader (manually with fastboot), restocked, installed custom recovery (TWRP; fastboot) and then flashed a SuperSU CWM-flashable package from recovery. I did a lot of messing around with flashing and stuff on my SGT7 and Nexus 7, so this wasn't really anything new or difficult at all. I started out with a toolkit on my Nexus 7, and found it very annoying after a while when trying to flash a custom recovery (generally took a while for the device to end up having to reboot and unlock, and if I already did unlock then I think the toolkit wouldn't continue on unless I selected another option, and then if drivers aren't installed properly (I switched between a few devices) then that can also cause the toolkit to mess up, drivers and adb would be outdated from the toolkit in-comparison to what Google offered, etc.).
Simply put, Toolkits might be nice in the beginning, but I wouldn't recommend relying on them forever If your only mission is to just root the device though, a toolkit can do that pretty painlessly.
espionage724 said:
Toolkits are a nice method for rooting for beginners, but (imo) it's better to learn how to flash (and do generally other stuff) without the need of a toolkit.
When I rooted my Nexus 10, I just unlocked the bootloader (manually with fastboot), restocked, installed custom recovery (TWRP; fastboot) and then flashed a SuperSU CWM-flashable package from recovery. I did a lot of messing around with flashing and stuff on my SGT7 and Nexus 7, so this wasn't really anything new or difficult at all. I started out with a toolkit on my Nexus 7, and found it very annoying after a while when trying to flash a custom recovery (generally took a while for the device to end up having to reboot and unlock, and if I already did unlock then I think the toolkit wouldn't continue on unless I selected another option, and then if drivers aren't installed properly (I switched between a few devices) then that can also cause the toolkit to mess up, drivers and adb would be outdated from the toolkit in-comparison to what Google offered, etc.).
Simply put, Toolkits might be nice in the beginning, but I wouldn't recommend relying on them forever If your only mission is to just root the device though, a toolkit can do that pretty painlessly.
Click to expand...
Click to collapse
Absolutely agree with you on that one. My first Android device was a Infuse 4G. Every root and recovery procedure was absolutely manual. Not to mention most of the methods were hackjobs from the OG Galaxy S and required some extra coersing w/ Root Explorer and a terminal lol. Once I got my GNex, I could do anything I needed to do manually; I was actually rather shocked at how simple things were w/ a Nexus device.
Really though, I don't at all mind these toolkits, it might be important to learn what goes on behind the scripts, but lots of ppl here would have never attempted to tinker w/ android w/o some sort of script/batch automation. That said, i'm sure they cause quite a bit more traffic in the Q&A section when things to go wrong. lol
Thanks for all of the replies.
It should arrive today and I'll compare it with my Infinity first and then go from there.
Looking forward to know the N10
When I first received mine, I didnt think that I would recieve it till closer to the end of day, as stated with UPS. But it arrived at 10am! Hoping it happens the second time around for my replacement. Would love to have the whole day playing with it
Sent from my SPH-L710 using xda app-developers app