-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Universal 1 Click Eris App Apk - No PCs, No Scripts Needed, EASY
- Thread starter jcase
- Start date
-
- Tags
- htc droid eris
mcmi11ions
Newbie
Hi all,
I downloaded, installed and booted to recovery, but when I do, all that happens is a picture displays of a phone with a red ! inside a triangle. Any idea what I did wrong? I didn't see any sort of option to run rootme.zip, and I also don't see it on my sd card after all this when I boot normally.
I downloaded, installed and booted to recovery, but when I do, all that happens is a picture displays of a phone with a red ! inside a triangle. Any idea what I did wrong? I didn't see any sort of option to run rootme.zip, and I also don't see it on my sd card after all this when I boot normally.
Not sure if i'm doing thi in the right place but i was wondering a million things.. First I am running the Droid Eris with the 2.1 update... I rooted using the 1 click Eris Root in the market and was able to get rid of some bloatware
I want to install a ROM so bad for this with the clockwork (overclocking)...(dnt know if im saying it right) I was told to try Froyo and i want to, but I have no idea how to click and install it... plus i want to know how to reinstall stock OS if i want ... also if Verizon or HTC drops another OTA update wiill i still be able to use it... i need help as u can see i am lost...even on this forum lol HELP!
I want to install a ROM so bad for this with the clockwork (overclocking)...(dnt know if im saying it right) I was told to try Froyo and i want to, but I have no idea how to click and install it... plus i want to know how to reinstall stock OS if i want ... also if Verizon or HTC drops another OTA update wiill i still be able to use it... i need help as u can see i am lost...even on this forum lol HELP!
I think that happened to me also... it was a diference in something that was chosen in the recovery menu but i got it to work
mcmi11ions
Newbie
Well, i tried it again. and again. and again. the last time, i just cycled through the different boot options, highlighting each one, then i went and selected recovery, and poof it worked.
i'm rooted.
Now to learn Nandroid and how to flash a rom.
The cause of your trouble was most likely that you did not perform a regular, "normal" reboot after running the app, but before you tried starting the recovery boot. The graphic that you describe is the splash screen of the stock recovery boot.
That means that the rooting process had not completed yet for lack of a regular reboot.
Admittedly, the instruction are a little vague on that point - if you look back a couple posts, you will see some remarks about that.
Welcome to root!
eu1
That means that the rooting process had not completed yet for lack of a regular reboot.
Admittedly, the instruction are a little vague on that point - if you look back a couple posts, you will see some remarks about that.
Welcome to root!
eu1
Well let me know when u get it bc.. I NEED TO KNOW TOO!
Installing a ROM is easy; it boils down to four or file steps.
(1) Download the ROM .zip file (of your choice) to the SD card on your phone.
(2) Make sure your phone is fully charged.
(3) Using the Amon_RA recovery boot, make a Nandroid Backup.
(4) (Still using Amon_RA) perform a "Wipe data/factory reset".
(5) (Still using Amon_RA) Flash the ROM from the .zip file on your SD card.
Reboot and wait five or six minutes for everything to finish up.
There are a set of instructions with pictures that show you how to do all the above steps (other than downloading your ROM .zip file) in this AF post
There are a few common ways that folks get tripped up doing this. By far, the two most common mistakes are:
- forgetting to do the "Wipe" step (#4)
- corrupting the ROM file when downloading it, or when transferring it to the phone.
The simplest way to have some confidence that your download is not corrupted is to:
(a) Download it to your PC.
(b) See if you can successfully unzip it (on the PC); if not, the download failed.
(c) If that works without any errors, look up the exact size of the .zip file on the PC, and then
(d) transfer the .zip file to the SD card on the phone, making sure that you use the "Safely Remove Hardware" control in the system tray after you have copied the .zip file, but before you turn off "Disk Drive Mode" on the phone
(e) On the phone, using a File Manager, look up the size of the .zip file again, down to the last byte - it needs to be exactly the same size as the file on the PC, down to the last byte.
The above method will not give you 100% assurances that the download file got to your phone in an intact condition, but it's will eliminate the "I never even checked" types of errors. If you want to look at more advanced ways to check file integrity, you can have a look at this post
good luck
eu1
mcmi11ions
Newbie
thanks eu1
I always thought that the nandroid that everyone referred to was a seperate program. I had no idea it was in recovery. the rundown you gave was perfect and made the process simple and less intimidating.
I always thought that the nandroid that everyone referred to was a seperate program. I had no idea it was in recovery. the rundown you gave was perfect and made the process simple and less intimidating.
erisx,
Do you mean can you keep your current stock 2.1 setup? Qualified "yes"...let me re-iterate what we discuss a few days ago in the other thread: the newest rooting methods allow you to install a custom recovery partition over the current stock one. Using this custom recovery, you can either give your current setup root capabilities (i.e., via flashing the rootme.zip file) or you can replace your current phone's setup by flashing a custom rooted ROM.
But, the first thing you should do when presented with Amon_RA's custom recovery for the first time would be to take a Nand (Nandroid) backup. Then you can choose to either flash rootme.zip or a custom ROM. With the Nandroid backup in-hand, you can restore your phone to whatever state it was in when the backup was taken (in your case, if your first Nandroid backup is before you flash anything, then a Nandroid restore will take you back to stock 2.1--excepting that you will have a custom recovery installed in place of your stock recovery) [that's the reason why I gave you a qualified "yes" since a Nandroid restore does not overwrite the recovery partition].
Is that what you were asking and/or did I answer your question? Let me know...cheers!
erisx,
If you want to root and keep your current setup, just follow the instructions that jcase wrote, but when you get to step #4, you would deviate only slightly...let's pretend there's a new step 3.5 between step 3 and step 4 like this:
Step 3.5) Okay, you should have now rebooted in step #3 and you should now have Amon_RA's custom recovery installed. So, let's first make a Nandroid backup (this will preserve your non-rooted 2.1 setup and allow you to restore back to it when/if needed).
So, boot into custom recovery by powering-off the phone. Then, press and hold volume-Up while simultaneously pressing the End/Power button (keep pressing volume-Up until you see Amon_RA's custom recovery menu).
When the custom recovery menu appears, navigate via the trackball to "Backup/Restore" (you press the trackball to select), then navigate to "Nand backup" and confirm that you want to make a backup. By the way, erisuser1 has this wonderfully documented in this post: http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies.html#post1186824 (figures 33 through 37).
After the backup completes, you can navigate back to the main menu using the volume-Down button.
At this point, you can proceed to step #4 and flash the rootme.zip file (that the app already placed in the top-level of your /sdcard) from the "Flash zip from sdcard" option in the main menu. This is what actually gives you root/superuser capabilities. Note: you don't want to do any wipes since you want to preserve your current 2.1 ROM's setup.
After flashing the rootme.zip file, return to the main menu (use volume-Down) and select the reboot option. Then, finish-up by doing step #5.
-----------------
I won't muddy the waters in this post by mentioning what you would do for a custom ROM install...we'll cover that when / if you need it.
Also note: after flashing just the rootme.zip, you will have a rooted 2.1 phone. Your root "powers" at this point will be the ability to run root-only applications like wi-fi tethering, drocap2, Root Explorer, etc. You will not be able to overclock [yet] (there is a way, but you've got more stuff to do).
Does this makes sense? Kudos again to jcase for putting together such a wonderful and amazingly easy app for folks to use. This really is awesome!
Good luck!
If I am interpreting what you are saying correctly, yes.
The first part of both methods is just to get the custom (Amon_RA) recovery installed. What you do afterward is up to you.
eu1
lol! wow can i just send my phone to you!?!? lol I have a few of the steps already downloaded... I downloaded Titanium Backup from the market ESTRONGS file explorer Rom manager... etc... i know which custom ROM i want ... um im not seeing Amon Ra or Nandroid or anything and im honestly scared of this lol... I rooted my eis beforehand with the custom 10click eris root in the market.. it worked... and inside the ROM manager i clicked backup ROM ... so now in the root directory of ESTRONGS i have a zip file that says rootme.zip and update.zip and in the clockworkmod folder is a subfolder called backup with the date of the backup with several .img files... and a recpvery-update.zip file... soo i guess the question is ....ummm NOW WHAT!? lol.. man i need to do something less stressful with my free time
Yes, but you will also want to go into the wipe menu first and perform a data reset wipe, then go back to the main menu before you flash the ROM. The only time that you would not perform a data wipe first is if you are upgrading to a newer version of the same ROM and the developer mentions that your phone will work without wiping data.
Frisco
=Luceat Lux Vestra=
You're got the right idea.
If it's your first custom ROM, use your trackball to select the "wipe" menu, then select first "factory," then "dalvik" once the factory wipe is finished.
Then use the volume down key to return to the main menu and select flash from zip.. etc..
.. have fun.. be sure to be patient with that first boot as it can take what seems like forever, appearing to be stuck at times.
Frisco, 5k+ posts 
! Very nice (and wow)!
Why, I remember when you were just a young whipper-snapper with only 2k posts!
Impressive, your skills are...
...I am but a padiwan...you are, the Master.
! Very nice (and wow)! Why, I remember when you were just a young whipper-snapper with only 2k posts!
Impressive, your skills are...
...I am but a padiwan...you are, the Master.
eljitto
Newbie
thanks, and out of curiosity, should this be done every time?
eljitto,
Your normal sequence of events for flashing a new ROM would be as follows:
1. Perform a Nandroid backup (he's your friend
)2. Do any wipes (usually at least 'Wipe Data/Factory reset' and sometimes 'Wipe Dalvik-cache' (the dev's ROM thread will usually direct you if you need to do this second wipe (especially for Froyo ROMs))
3. Flash your .zip (ROM) from sdcard
4. Reboot
5. Enjoy your new ROM!
If you want or need to, you can restore your phone's state from the Nandroid backup you took--so whatever ROM you had installed and whatever apps / data that the Nandroid back backed-up (there are some exceptions if apps2sd is used...I won't address that here).
Hope that helps. Cheers!
erisx,
See the post right above
.I don't think it hurts to do both wipes (its probably safer but not always necessary--not wiping Dalvik-cache will sometimes lead to bootloops)...I think the issue w/wiping Dalvik-cache is that it will have to be rebuilt when Android reboots which takes a little more time.
Cheers!
edit: by the way, I found a nice post re. this: http://www.droidforums.net/forum/droid-general-discussions/57570-what-dalvik-cache.html#post613927:
"Simple explanation:
When Android starts up, the DalvikVM looks thru all of your applications (.apk files) and frameworks, and builds a tree of dependencies. It uses this dependency tree to optimize the bytecode for every application and stores it in the Dalvik cache. The applications are then run using the optimized bytecode. This is why when you install a new ROM, sometimes it takes a very long time to boot for the first time. Any time an application (or framework library) changes, it's reoptimized and the cache is updated."