Root Whats the worse that can happen if u root?

[erisx]

Well, what is it?

 

[Frisco]

Your refrigerator could suddenly stop running and your beer will turn warm.

 

[Frisco]

Kidding aside, the "worst thing that could happen" is quite subjective.

For me it would be messing up my CPU by aggressive overclocking, permanent damage is a possibility.

So I stopped overclocking on my default ROM and go carefully, in baby steps, on 2.2 ROMs. I may stop overclocking those, as well.

 

[andrizoid]

Kidding aside, the "worst thing that could happen" is quite subjective.

For me it would be messing up my CPU by aggressive overclocking, permanent damage is a possibility.

So I stopped overclocking on my default ROM and go carefully, in baby steps, on 2.2 ROMs.

not likely to happen. i tested on a throw-away eris. had it clocked up as high as possible (806) for as long as possible (kept it charging) and running wifi tether. phone got over 55 degrees C for 8+ hours w/o any damage

 

[scary alien]

Well, I've seen lots of complaints from folks that:

- their phone is faster, more responsive (even without overclocking)
- they have lots more memory for apps
- they can install root-only apps such as wi-fi tethering, dropcap2
- lots of custom ROMs and versions of Android are available

Seriously, you only have to worry about rooting if/when you need to return your phone to VZW (and even then, you can un-root / return your phone back to stock). There have been a few reports of folks frying their phones because they overclocked too high and too long, but other than that, there's not too much downside.

You do (or should) have to learn some things to take full advantage of rooting, but lots of folks have done it (even ones that should not have! yeah, that's right: I said it ).

 

[Frisco]

not likely to happen. i tested on a throw-away eris. had it clocked up as high as possible (806) for as long as possible (kept it charging) and running wifi tether. phone got over 55 degrees C for 8+ hours w/o any damage

I don't know, amigo.

I take heed of those warnings.. having seen my device lock up from having it tweaked up too high. I do know that the freeze up is actually the device protecting itself, but doing that too often will damage the CPU as well as other components, as will running an overclocked device, which is a bit too high for the conditions, for too long.

Data loss is common in aggressively overclocked computers (I used have to fix them).

From one manual, the risks:

• Immediate Destruction: It is possible to totally destroy a processor by attempting to overclock it. By destruction, I mean that the processor will not boot at the higher speed, and when returned to its normal speed, will continue to not function. This is basically the worst case outcome. This sort of permanent failure is very rare, but it does happen. It is made more likely by using inadequate cooling, and also by being ridiculously aggressive in how far you try to overclock (i.e., trying to run a Pentium 75 at 166 MHz.)
• Non-Functionality: The processor may not work at the new speed, but may work fine when returned to its original speed. This is a fairly common outcome when overclocking, and in most cases the processor will not be any the worse for wear.
• System Instability: The processor may boot at the new speed, but you may see the system behave strangely. Random hard lockups, parity errors, resource conflicts, strange hard disk problems, beeping, application crashes and Windows refusing to boot are just the tip of the iceberg. Particularly insidious are the overclocks that work almost perfectly, because that occasional crash may be due to your operating system, but it may be due to that overclocked chip also.
• Data Loss: It is very possible to lose data as a result of overclocking. If the processor is not functioning properly, you risk potentially damaging the structures of your hard disk's file system. It is also not uncommon for the Windows registry files to become corrupted, requiring a complete Windows reinstall. Needless to say, a full backup before overclocking is a wise move.
• Electromigration: When the processor is run at a speed that is higher than it is supposed to be run at, there is a chance that the internal components in the processor may break down over time. The internal features of a CPU are sized in the range of microns. It is possible that when the processor is stressed by running at too high a frequency, along with the extra heat that overclocking incurs, that the actual metal lines inside the processor may form shorts or opens and damage the processor over a period of time. How likely this is to happen, and how long it takes is really not known. The system may work fine for a while and then suddenly stop working.

 

[andrizoid]

I don't know, amigo.

I take heed of those warnings.. having seen my device lock up from having it tweaked up too high. I do know that the freeze up is actually the device protecting itself, but doing that too often will damage the CPU as well as other components, as will running an overclocked device, which is a bit too high for the conditions, for too long.

Data loss is common in aggressively overclocked computers (I used have to fix them).

From one manual, the risks:

• Immediate Destruction: It is possible to totally destroy a processor by attempting to overclock it. By destruction, I mean that the processor will not boot at the higher speed, and when returned to its normal speed, will continue to not function. This is basically the worst case outcome. This sort of permanent failure is very rare, but it does happen. It is made more likely by using inadequate cooling, and also by being ridiculously aggressive in how far you try to overclock (i.e., trying to run a Pentium 75 at 166 MHz.)
• Non-Functionality: The processor may not work at the new speed, but may work fine when returned to its original speed. This is a fairly common outcome when overclocking, and in most cases the processor will not be any the worse for wear.
• System Instability: The processor may boot at the new speed, but you may see the system behave strangely. Random hard lockups, parity errors, resource conflicts, strange hard disk problems, beeping, application crashes and Windows refusing to boot are just the tip of the iceberg. Particularly insidious are the overclocks that work almost perfectly, because that occasional crash may be due to your operating system, but it may be due to that overclocked chip also.
• Data Loss: It is very possible to lose data as a result of overclocking. If the processor is not functioning properly, you risk potentially damaging the structures of your hard disk's file system. It is also not uncommon for the Windows registry files to become corrupted, requiring a complete Windows reinstall. Needless to say, a full backup before overclocking is a wise move.
• Electromigration: When the processor is run at a speed that is higher than it is supposed to be run at, there is a chance that the internal components in the processor may break down over time. The internal features of a CPU are sized in the range of microns. It is possible that when the processor is stressed by running at too high a frequency, along with the extra heat that overclocking incurs, that the actual metal lines inside the processor may form shorts or opens and damage the processor over a period of time. How likely this is to happen, and how long it takes is really not known. The system may work fine for a while and then suddenly stop working.

i agree with that, but i remember reading something on xda about overclocking where the guys point was that unless the battery or internals heat up enough to warp, then there wont be issues. and it takes a hell of a lot of heat to warp it.

not to say clocking up that high is good. some phones crap out above 710-my new refurb only goes to 748

 

[erisuser1]

Well, what is it?

You girlfriend/boyfriend/spouse will leave you because you are constantly fooling with your phone. And steal all your stuff on the way out the door, too - you will be too busy flashing the newest keyboard .apk that you won't notice.

Or, it will be like that AT&T ad with the ballerina girl who's download finishes in time for her to drop her slippers: you will be flashing a new ROM when someone tries to call you with an offer to work as a campaign staffer. That opportunity would have led to you eventually becoming the President of the United States. Instead, you will slip into despair and end up drunk, homeless, and broke.

Either that, or you will just miss a couple of re-runs of "Three and a Half Men".

 

[smacky]

Theoretically, everything can go wrong. Meaning you screw the phone.

In reality, if you're safe and smart, nothing should go wrong with the hardware. As far as the software, if you mess up badly, you can always boot into recovery and fix the issue by reinstalling or clearing the cache. Factory reset in dire cases.

I'm OCd to 1.25 Ghz and have never had a lockup or anything. If it gets warm, I just turn the screen off and the SetCPU governor brings it back down to 250 Mhz and it cools off in a few minutes. It has never gotten so hot that it shut down automatically. When that happens, you've overheated.

 

[andrizoid]

Theoretically, everything can go wrong. Meaning you screw the phone.

In reality, if you're safe and smart, nothing should go wrong with the hardware. As far as the software, if you mess up badly, you can always boot into recovery and fix the issue by reinstalling or clearing the cache. Factory reset in dire cases.

I'm OCd to 1.25 Ghz and have never had a lockup or anything. If it gets warm, I just turn the screen off and the SetCPU governor brings it back down to 250 Mhz and it cools off in a few minutes. It has never gotten so hot that it shut down automatically. When that happens, you've overheated.

not on the eris your not OCed to 1.25
thats not possible

 

[erisx]

You girlfriend/boyfriend/spouse will leave you because you are constantly fooling with your phone. And steal all your stuff on the way out the door, too - you will be too busy flashing the newest keyboard .apk that you won't notice.

Or, it will be like that AT&T ad with the ballerina girl who's download finishes in time for her to drop her slippers: you will be flashing a new ROM when someone tries to call you with an offer to work as a campaign staffer. That opportunity would have led to you eventually becoming the President of the United States. Instead, you will slip into despair and end up drunk, homeless, and broke.

Either that, or you will just miss a couple of re-runs of "Three and a Half Men".

Well i guess i wont root! (Gotta watch that three and a half men xD) aha but im just afraid of messing up. This is my first smart phone and i dont wanna lose it

 

[scary alien]

Well i guess i wont root! (Gotta watch that three and a half men xD) aha but im just afraid of messing up. This is my first smart phone and i dont wanna lose it

erisx,

You are wise to wait until you are comfortable with it. When I did it, I was afraid of losing the ability to root since I thought that when version 2.1 was being pushed-out back in May, I would be unable to root. I was fully prepared to have to revert back to my old flip-phone , but thankfully, never had to.

Keep tabs on the eris-all-things-root subforum and let us know when you are ready. There'll be lots of folks ready and willing to help.

Cheers!

 

[erisx]

Thanks Scary Alien. Which root method do you guys recommend? And what ROM should i start off w/?

 

[scary alien]

Thanks Scary Alien. Which root method do you guys recommend? And what ROM should i start off w/?

When you are ready, there are at least three good options for you to root and then flash your custom ROM (all discussed in this thread Rooting HTC Eris):

1. http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies.html - this thread by erisuser1 is very detailed, thorough and guides you along with screenshots; lots of folks have used it very successfully; this method allows you to root without having to use your PC or MAC

2. http://androidforums.com/eris-all-t...is-app-apk-no-pcs-no-scripts-needed-easy.html - this thread by jcase is very quick and easy, but details are a little sparse, but its your easiest route

3. http://androidforums.com/htc-droid-eris/125436-detailed-leak-root-tutorial.html - this thread by surgeon0214 / alprazolam walks you through rooting via the Android SDK; this is a good method if you are comfortable with the Windows Command Prompt and want to know about each step in detail (you'll learn a lot by doing this).

There is also the option to simply root your phone in-place without installing a custom rooted ROM. This would give you root/superuser access and allow you to install root-only apps (wi-fi tethering, for example), overclock to make your phone run faster (you will have to flash an update to the kernel to do this and acquire the setCPU app).

If you do decide to flash a custom rooted ROM, I've heard excellent things about PlainJaneT2 (very close to stock, w/Sense); Zach's xtrSense and xtrROM have been very highly touted. There are so many...I'm really not the best person to ask since I'm very happy with my original ROM that I flashed (Ivan's Eris Official 1.0). Take a look through the threads and you'll see lots of threads w/folks discussing the merits of the various ROMs.

Cheers!

 

[roscuthiii]

Thanks Scary Alien. Which root method do you guys recommend? And what ROM should i start off w/?

I went with option #2 a while back on Scary Alien's list and I'm fairly inept at this stuff. I have to say that it was really easy.

I'm also using the Ivan's Official 1.0 ROM mentioned. This ROM seems to one of the one's as close to stock as you can get. Ivan seems to have basically just tidied a few things up. I'd recommend it as a 1st time rooter/ROM flasher's for now as some of the newer ones can sink you into the world of a2sd (w/ sd card partitioning), JIT, LWP, etc. before you may be ready.

 

[scary alien]

I'm also using the Ivan's Official 1.0 ROM mentioned. This ROM seems to one of the one's as close to stock as you can get. Ivan seems to have basically just tidied a few things up. I'd recommend it as a 1st time rooter/ROM flasher's for now as some of the newer ones can sink you into the world of a2sd (w/ sd card partitioning), JIT, LWP, etc. before you may be ready.

Hey roscuthiii, long time no "see"! Good to see you again.

By the way, I've been waiting for Ivan to release version 1.1 w/the July 2010 OTA update baked-in (plus goodies). Still no joy...

So, PlainJaneT2 is a good first ROM for folks since it does have July 2010 OTA update included (although Ivan's still works just fine--I never had the silent-call issue, so this wasn't an issue for me, but it might be for some folks).

Cheers!

 

[erisx]

so ivans doesnt have the update? hmm..well:
1) whats great about plain jane
2) whats the WHOLE process to the one click, as in after you reboot?
3) do i have to reactivate my phone again after i root?

 

[scary alien]

so ivans doesnt have the update? hmm..well:
1) whats great about plain jane
2) whats the WHOLE process to the one click, as in after you reboot?
3) do i have to reactivate my phone again after i root?

erisx,

What happened to "I'm going to wait..."? just kidding...

1) PlainJaneT2 is supposed to be very close to stock, but rooted. Here's the dev's thread over at XDA: [ROM]Plain_JaneT2 V2.0 7/18/10 Stock With everything ROOT!! - xda-developers

2) Well, read through the 1-click thread or better yet, read through the three threads that I posted. This should give you a better idea (especially in erisuser1's "Universal Root for Dummies" thread since he's got a lot of pictures and descriptions about what is going on).

The key to rooting the Eris is getting a custom recovery partition installed. From there, you can flash a custom ROM or an "update.zip"-type file.

3) I had to reactivate my phone at least once after I first rooted, but I've flashed other ROMs since then and have not had to. I don't think this is a regular thing (or I'd see more references to it in the threads). It also could have been something that I did, lol (I rooted "the old-fashioned way"--your options are much simpler and easier).

By the way, let me re-iterate an option you might not have considered or has not yet been emphasized in this thread: you can do an in-place root on your phone that does not involve flashing a custom ROM. If you choose jcase's 1-click method, you would flash the "rootme.zip" file in his step #4 instead of a custom ROM. This would give you the su program and SuperUser app and you would be rooted. You could then enjoy most of the benefits of root on your current phone's setup: i.e., install root-only apps such as wi-fi tethering, drocap2 screen capture, etc.

Then, when you are ready, you could overclock (this involves flashing a patch to replace your kernel to one that can overclock) or flash a custom rooted ROM.

There are so many scenarios and options, you almost have to at least have an idea where you want to go and what you want to do and get out of rooting first.

Think it over. Take your time. We're not going anywhere.

 

[erisx]

well the whole idea of a 'better' phone gets me pumped! lol i wanna do it right now, but i just wanna make sure i have everything down
but i might just root it and just flash the rootme .zip so i get a feel for root

 

[scary alien]

well the whole idea of a 'better' phone gets me pumped! lol i wanna do it right now, but i just wanna make sure i have everything down
but i might just root it and just flash the rootme .zip so i get a feel for root

lol, I hear ya! Just keep doing your reading to "acclimatize" yourself so your root journey will be less bumpy .

When and if you do decide to root, make sure that one of the first things you do is make a Nandroid backup. This is very nicely documented in erisuser1's "Universal Root for Dummies" thread (all three of the threads nicely complement each other since they all basically do the same things, but in different ways).

Cheers and have a great rest of your evening.

 

[erisx]

Thanks so much for the help scary alien! and have a wonderful night as well

 

[erisdenile]

I just rooted doing the root that requires no PCs, Scripts, etc with KaosFroyo v31 and love it. One question though, what settings should i have for overclock? i have 245min 710 max with screen on and 245min and 385 max when off, is 710 too much? I dont have SetCPU cause i dont wanna pay 2$ for it so im using overclock widget and max it would set is 710, i try to go to 864 but just stays on 710. Im guessing because thats the max of this phone because ive heard each phones overclock speed varies. Also, hottest Ive had it at is 101 F because it was charging, currently its at 78 F which is weird considering it was around 85 unrooted.

 

[es0tericcha0s]

The worst thing? Realizing that you've been missing out on all the advantages because you were scared.

I just rooted doing the root that requires no PCs, Scripts, etc with KaosFroyo v31 and love it. One question though, what settings should i have for overclock? i have 245min 710 max with screen on and 245min and 385 max when off, is 710 too much? I dont have SetCPU cause i dont wanna pay 2$ for it so im using overclock widget and max it would set is 710, i try to go to 864 but just stays on 710. Im guessing because thats the max of this phone because ive heard each phones overclock speed varies. Also, hottest Ive had it at is 101 F because it was charging, currently its at 78 F which is weird considering it was around 85 unrooted.

710 isn't too much. All of the Froyo roms run that stock. 864 is out of the question for 99% of Eris owners. You'll most likely get frozen and constant reboots as soon as you try. For SetCPU: SetCPU for Root Users [2.0.2] This *actually* changes everything. 08/02/2010 - xda-developers
There are tons of threads about what levels you want to run with SetCPU. Short answer, there are no magic numbers. Depends on whether you value performance or battery life and/or what combination of the 2 works best for you. Not every processor is created equal. Some people can't overclock past 710 much while others can run 806 all day. Play around with it, just don't check the set at boot option until you find your sweet spot. Once you install SetCPU, hit autodetect, then go from there. You can make the profiles to guard against excessive heat by adjusting the CPU speeds for the phone once it gets to a certain temperature. The only 2 profiles I find handy are that one and with the screen off, to save battery while it is asleep. If you need more help, hit me up on your Talk app with my screen name @ gmail.

 

[xzillerationer]

Thanks Scary Alien. Which root method do you guys recommend? And what ROM should i start off w/?

Really, the easiest ones are the automated ones. And I recommend Kaosfroyo for a 2.2 ROM. xtrSense/xtrROM or Evil Eris for 2.1, and it's not worth it to go 1.5/1.6 or earlier. But, find one you like and one that suits your needs.

 

[WormDoes]

ErisX,

I rooted using the 1 Click Method and kept my Stock 2.1 for a good month after rooting. I O/C'd and my phone became significantly faster and more responsive. The 1 Click Method is very easy. If you want a "better phone" I highly recomend this method. Just remember that it is a donate app. If you D/L and decide to use it you are required to donate to a meal to a youth or homeless center. Whatever you can afford. I don't make a ton of money right now (effin' ecconomy!) so I donated $15 to my local Salvation Army. If $15 is too much, I'm sure whatever you can afford would be greatly appreciated. IMO, it's well worth it to basically get a brand new, cooler, phone. BOL and if you have any more questions ask. This forum is an awesome place with awesome people.