Root Universal Eris Root for Dummies!

[erisuser1]

I tried searching the thread for this, but didn't see any posts about a possible problem that may come from performing a factory re-set. I did a factory re-set last week because certain features on my phone were not working. The re-set ended up knocking me off of Verizon's network, and I had to go to a store to have them fix it. According to your instructions, during the root process I will have to perform a wipe. This would potentially present the same problem where I would have to have Verizon re-authenticate my phone. Is there a way around doing the wipe or am will I be unable to root the phone? Any advice would be appreciated.

HollywoodKen481,

I answered this question this AM in this thread, because I was unable to get to your post above without my browser looping. (The site crash that happened yesterday has caused some pretty acute pathologies on the board - threads loop, posts which are there don't show up, blah blah blah).

Short answer is don't worry, be happy.

eu1

 

[erisuser1]

You need the trackball right?

Yes, it is impossible to use the menus in Amon_RA recovery without a working trackball. (There are workarounds, but you need to be a Linux wizard to do all those menu items from the command line with Amon_RA running)

Does verizon replace your phone still if your trackball is defective?

Don't know. Call them and find out. Please report your findings over in the (non-root) Eris forum because it is of interest to anyone that owns an Eris.

eu1

 

[BGdakid08]

ok thanks!

 

[eddieb1983]

You need the trackball right? Does verizon replace your phone still if your trackball is defective?

I have had my phone and my wifes phone replaced soley because the trackball would not scroll to the left.

Since rooting does void your warranty, if you needed to unroot, would you just flash the nand backup? What about the recovery? Wouldn't seeing that cause the vw techs to see that the phone was rooted and hit your bill with $400?

Not to scare anyone, just a question I have before I join the wonderful world of rooting.

 

[scary alien]

I have had my phone and my wifes phone replaced soley because the trackball would not scroll to the left.

Since rooting does void your warranty, if you needed to unroot, would you just flash the nand backup? What about the recovery? Wouldn't seeing that cause the vw techs to see that the phone was rooted and hit your bill with $400?

Not to scare anyone, just a question I have before I join the wonderful world of rooting.

eddieb1983,

Take a look at erisuser1's post (http://androidforums.com/all-things...re-stock-bootloader-recovery.html#post1363157) about returning your phone back to stock (and without the custom recovery on it).

Cheers!

 

[wapitismith]

This is the key to all my woes... ;-)

How do I mark this with a thank-you?

 

[scary alien]

This is the key to all my woes... ;-)

How do I mark this with a thank-you?

I'm betting you meant this whole thread .

If so, you're looking for references to erisuser1...I'm sure he very much does appreciate the positive feedback that lots of folks have already provided, but don't be shy about clicking the thanks button on a few of his posts (he deserves that plus a lot more) [plus I know he (and a lot of others) lost a lot of posts and thanks due to the AF site crash from this weekend].

 

[eddieb1983]

Many thanks to EU1 for this guide. I was able to root and install my ROM with no hiccups and I am really enjoying the ROM I installed.

Now I'm trying to figure out how to customize it like everyone says they can. I got the xtrROM 3.0.3.

Great post EU1!!!!!!!!!!!!!!!!

 

[Harmageddon]

Harmageddon,

Yeah, its been quite the day on AF...looks like there were lots of posts and stuff lots for the last day or so .

Glad to know you want to read and learn for yourself, so I'll just nudge you in the right directions as best as I can.

I don't have any direct experience with ROM Manager or ClockworkMod Recovery, but I can tell you what little I do know. ClockworkMod is a custom recovery, similar to Amon_RA's custom recovery. ClockworkMod was authored by Koushik Dutta (AllDroid) and Amon_RA was authored by Amon_RA (XDA). I'm sure they both perform similar functions: allow you to flash updates and ROMs to your phone, make full system (Nandroid) backups and restore them, format /sdcard partitions, etc. Apparently, who(m)ever authored ROM Manager, selected ClockworkMod as the custom recovery of choice.

Here's Koush's ClockworkMod page: Official Homepage for the ClockworkMod Recovery.

Here's the XDA link for Amon_RA's custom recovery: xda-developers - View Single Post - [Recovery] [17-Mar-2010] RA-eris-v1.6.2

As far as PlaneJane T2 goes ([ROM]Plain_JaneT2 V2.0 7/18/10 Stock With everything ROOT!! - Page 15 - xda-developers), reading the first post really doesn't reveal too much about it and I've never flashed it. But here's a more informative thread on AF re. this ROM: http://androidforums.com/all-things-root-eris/115419-rom-plainjanet2-stock-2-1-oc-a2sd-2.html which will probably answer most of your questions.

From your questions, it does sound like you do know what overclocking is, so I won't give you a spiel re. that (unless you want ).

Hope this helps. Cheers!

I would love to know what I have available to me with my current setup or if you know of a better ROM that I could use. I was trying setcpu but it kept making my phone restart. I found an overclock widget and am currently OC at 768 with no issues. How would you rate the Amon_RA recovery over the Clockworkmod recovery? Are there advantages or disadvantages from one to the other? Thanks for any info you have and thanks for sharing.

 

[scary alien]

I would love to know what I have available to me with my current setup or if you know of a better ROM that I could use. I was trying setcpu but it kept making my phone restart. I found an overclock widget and am currently OC at 768 with no issues. How would you rate the Amon_RA recovery over the Clockworkmod recovery? Are there advantages or disadvantages from one to the other? Thanks for any info you have and thanks for sharing.

Harmageddon,

Well, there's lots and lots of ROMs out there now. I'm actually running a pretty old, early one (Ivan's Eris Official 1.0) that suits my needs (I just wanted something that was pretty close to stock and works). There are newer/updated ROMs that are not only close to stock, but also contain the latest July 2010 2.1 update that was released to fix "audio" (silent call) issues. Pretty sure that it did the trick since this topic seems to have died down now.

If I were you, I would scan through the various threads (look for "[ROM]" at the start of each thread name) over at XDA (Droid Eris Android Development - xda-developers) and here at AF and read-up on the pros and cons of the various ROMs out there. Each has its own advantages and quirks.

As far as Amon_RA's recovery vs. ClockworkMod, I really can't compare since I've only used Amon_RA's. As long as it works for you and does the job, you should be fine. There are a few folks here on AF that do run ClockworkMod...perhaps its time to start a thread with those guys discussing the merits of each? I'm sure you'd get some really good feedback from that.

I would caution you to keep and eye on your overclocking speed, or rather, your phone's temperature to make sure it doesn't run too hot. 710MHz is widely considered safe and stable. I do think lots of folks can and do run at higher speeds like you are at 768MHz, but you should make sure you have a failsafe temp profile setup just in case.

Hope this helped a little. Cheers!

 

[erisuser1]

I was trying setcpu but it kept making my phone restart. I found an overclock widget and am currently OC at 768 with no issues.

Just out of curiosity, what was the maximum speed you had set up when your phone was "restarting"?

An OS crash like that is very symptomatic of using too high a clock speed, and that maximum clock speed value varies from phone to phone. (It is also statistical in nature - meaning that if you use an extremely high value, your phone will crash immediately, but if you back off the max speed, you might still experience crashes -just less frequently. I would say that a "safe" max frequency is one in which your phone never spontaneously reboots in a week or more of continuous service.)

Also, I think I saw some reports claiming problems (either battery life or sluggishness) by people using the SetCPU widget - the claims that they made were that using just the SetCPU app (with profiles and auto-start) solved their problems. I haven't verified such claims, but it might be something to be aware of.

eu1

 

[SD3]

I've been reading this forum for a while and this particular thread has been extremely helpful. I followed the instructions and loaded v.30 of 2.2 from kaos.

now here is my problem...

When i try to boot for the first time the new android logo continues to loop. I let it sit for 20 minutes with nothing new happening. Did I do something wrong?

edit: well after sitting for 45 minutes it finally came on and I am very satisfied!

Thanks for all the help in this forum!!

 

[erisuser1]

I've been reading this forum for a while and this particular thread has been extremely helpful. I followed the instructions and loaded v.30 of 2.2 from kaos.

now here is my problem...

When i try to boot for the first time the new android logo continues to loop. I let it sit for 20 minutes with nothing new happening. Did I do something wrong?

edit: well after sitting for 45 minutes it finally came on and I am very satisfied!

Thanks for all the help in this forum!!

45 Minutes seems excessively long. If you have a bunch of troubles, but want to stick with a Froyo ROM, try Tazz V8.

[ Edit ] I did a wipe and a V30 install, and the 3 skating Androids were replaced by a different (black and white) screen within 2 minutes. That splash screen also only persisted another minute or two before the "press the Android" screen came up.

I just DL'ed the V30 a couple hours ago; I'm still debating going through the effort to install it. (I switched to V29 from Tazz V8, but ended up going back to Tazz V8).

Glad you are rooted.

eu1

 

[SD3]

45 Minutes seems excessively long. If you have a bunch of troubles, but want to stick with a Froyo ROM, try Tazz V8.

I just DL'ed the V30 a couple hours ago; I'm still debating going through the effort to install it. (I switched to V29 from Tazz V8, but ended up going back to Tazz V8).

Glad you are rooted.

eu1

After all the effort of rooting and such I accidentally formatted the SD card and lost EVERYTHING. I'm hoping nothing goes wrong now as I will then have nothing. Oh well--no sacrifice, no victory.

 

[erisuser1]

After all the effort of rooting and such I accidentally formatted the SD card and lost EVERYTHING. I'm hoping nothing goes wrong now as I will then have nothing. Oh well--no sacrifice, no victory.

Ouch.

Well, now you should at least make a backup of your current (Froyo) ROM. At least you can then say "I've got a backup! (of something)".

If I stay on a ROM for any length of time, I will make a backup every couple of days or so. (I don't keep every backup, I just delete stuff I know I will never use again, or older versions of the same ROM).

Backups are a good idea any time you can get them done - not just when changing ROMs. Stuff can go wrong at any time.

Same thing applies to backing up the SD card to your computer - if you lose the phone, all those backups won't do you any good if they are only on the SD card.


eu1

 

[kaveman]

Awesome Thread. Just followed it and now have root and a new ROM!
Thanks
Kaveman

 

[bubby142]

I have gotten to "executing" part 2.... I tap it and it does stuff and the nit says "Error Writing Recovery, Failed Permissions" or something like that.... so I'm at my Whit's End. If I really can't do this can I just forget it and will I be ok?

 

[erisuser1]

I have gotten to "executing" part 2.... I tap it and it does stuff and the nit says "Error Writing Recovery, Failed Permissions" or something like that.... so I'm at my Whit's End. If I really can't do this can I just forget it and will I be ok?

You need to reboot after you have done part1 but before you do part2.

If you can't get it to work, and you just "forget it", you should be OK. You could also try the "One Click" method - look for the sticky post.

eu1

 

[bubby142]

You need to reboot after you have done part1 but before you do part2.

If you can't get it to work, and you just "forget it", you should be OK. You could also try the "One Click" method - look for the sticky post.

eu1

by reboot do you mean clicking the "reboot button"

or actually shutting down and opening the phone


and I tried the shutting down part, didnt help, and the reboot button just went to blue screen and I didnt even see any thing going on... do I just need to wait longer?

btw thank you for your quick reply

 

[erisuser1]

by reboot do you mean clicking the "reboot button"

or actually shutting down and opening the phone


and I tried the shutting down part, didnt help, and the reboot button just went to blue screen and I didnt even see any thing going on... do I just need to wait longer?

btw thank you for your quick reply

I mean actually shutting off the phone and then turning it back on, just like the instructions say.

The "Reboot phone" in the Gscript App won't do anything, because it needs root to work; see in the image where it says "needs su: true" ? (Since you don't have root at the point in time you are using the Gscript too, that can't possibly work)

eu1

 

[bubby142]

New prob

Ok so I went with the kaosfroyo v30 build on my eris.... I got to the part where I restart my phone and it boots up for the first time.... well I boots to this android screen and its going forever... I have waited 40 min and nothing.... I did some research and I think my phone is doing something called bootlooping.... I can take out my battery and go to the recovery place but thats it..... any help here?

 

[erisuser1]

New prob

Ok so I went with the kaosfroyo v30 build on my eris.... I got to the part where I restart my phone and it boots up for the first time.... well I boots to this android screen and its going forever... I have waited 40 min and nothing.... I did some research and I think my phone is doing something called bootlooping.... I can take out my battery and go to the recovery place but thats it..... any help here?

You need to perform a "Wipe data/factory reset" using Amon_RA before you flash the ROM .zip file. For people that are new to this sort of thing, failure to "wipe" causes about 95% of these reports. It's in the instructions.

In the case of a clean V30 install, it should take only about 2-3 minutes for the "3 skateboarding androids" to be replaced by another splash screen, which will in turn last for only a couple more minutes (2 or 3, maybe less).

Good Luck

eu1

 

[bubby142]

well I wasnt have trouble with the skaters just the v30 screen, but I will try what you said one more time and see if it works

 

[bubby142]

In an effort to see if I was still alive, I did the recovery thing and luckily if anything goes wrong I can alway undo that puts me at peace

 

[bubby142]

THANK YOU THANK YOU THANK YOU!!!!! ITS WORKING!!!!! I AM CURRENTLY RUNNING FROYO ON MY PHONE!!!!! THANK YOU SOOOOOOO MUCH MR ERISUSER1!!!!

I actually wouldn't consider myself a "dummy" and I'm actually that everyone asks for computer help but idk why this was so difficult but now I have this experience. Maybe I could do it with my dad's phone. Thank you for your patience erisuser