• 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

scary alien said:
I suspect the problem you are having is because you didn't remount the filesystem as "read-write" (its usually read-only). Root Explorer (a buck or two in the Market) apparently has a remount option / function that makes this pretty easy.
Click to expand...

Hi s.a.

FYI,

ES (Estrongs) File Manager also has root-awareness now, and a "remount" toggle underneath Menu -> Settings -> Root options -> Mount File System

and it's free!! ... It seems to understand the difference between system and market apps, can do installs from .apk's... et cetera. (There appears to be a lot of other stuff under the hood that I haven't looked at, either - an App manager, etc)

Since you've already got RE, I suppose there's not much reason for you use ES File Manager - unless RE can't deal with SMB/CIFS network shares or FTP servers (ES FM can handle both quite nicely).

eu1
 
erisuser1 said:
Hi s.a.

FYI,

ES (Estrongs) File Manager also has root-awareness now, and a "remount" toggle underneath Menu -> Settings -> Root options -> Mount File System

and it's free!! ... It seems to understand the difference between system and market apps, can do installs from .apk's... et cetera. (There appears to be a lot of other stuff under the hood that I haven't looked at, either - an App manager, etc)

Since you've already got RE, I suppose there's not much reason for you use ES File Manager - unless RE can't deal with SMB/CIFS network shares or FTP servers (ES FM can handle both quite nicely).

eu1
Click to expand...

eu1,

Thanks for that info...actually, I've never used Root Explorer -- just seen info about what other folks have reported.

I do most of my "traversing" and exploring via adb shell...I'm on an AIX Unix box at work and am happy/comfortable with the shell prompt :).

I've started "playing" with my Eris a little more recently now that I've got my Droid X as my main phone and have the Eris to fall back on should anything (gasp/knock-on-wood) happen to the X.

Waiting for the dust to settle on Froyo on the X to see about rooting it. Its a pretty nice phone already and I haven't really needed to root it (but am sorely tempted to).

Thank you again for the heads-up about ES File Manager. I've got it on my Eris, but haven't done anything special with it yet. I'm curious to explore the "experimental" features you mentioned recently. Sounds like the author(s) are really putting some good effort into this app (i.e., giving Root Explorer a run for their money, so to speak).

Cheers!
 
I rooted then flashed EvilEris 4.0 and now I can't get BusyBox to install. I'm a super noob when it comes to rooting so I would appreciate any help.
 
jmomma1203 said:
I rooted then flashed EvilEris 4.0 and now I can't get BusyBox to install. I'm a super noob when it comes to rooting so I would appreciate any help.
Click to expand...

Busybox is not installed in the ROM natively? Are you sure you need to (i.e., that its not already there)?

Since you didn't really say what the problem/issue was, all I can do is point you to a thread with some info about it which might help you: http://androidforums.com/all-things-root-eris/55997-busybox-one.html

Good luck!
 
scary alien said:
Busybox is not installed in the ROM natively? Are you sure you need to (i.e., that its not already there)?

Since you didn't really say what the problem/issue was, all I can do is point you to a thread with some info about it which might help you: http://androidforums.com/all-things-root-eris/55997-busybox-one.html

Good luck!
Click to expand...


Thank you Scary Alien but I'm not having much luck. My phone is finally how I want it except that I can't use cachecleaner or any other app that requires BusyBox. I can't get ADB to launch to load BusyBox manually. I rooted my Eris with this 1 click app. BusyBox is not being found on my Eris and it is not natively installed on Evil Eris.

Any other info you need to help me? I'm sorry I'm so clueless about this but I appreciate the direction of someone with my knowledge. :o
 
jmomma1203 said:
Thank you Scary Alien but I'm not having much luck. My phone is finally how I want it except that I can't use cachecleaner or any other app that requires BusyBox. I can't get ADB to launch to load BusyBox manually. I rooted my Eris with this 1 click app. BusyBox is not being found on my Eris and it is not natively installed on Evil Eris.

Any other info you need to help me? I'm sorry I'm so clueless about this but I appreciate the direction of someone with my knowledge. :o
Click to expand...

jmomma1203,

Okay, so I looked at the CachCleaner app in the Market and it does indeed say that BusyBox is needed. But it also says that you can install it from the Market.

I do see "BusyBox by Stephen (Stericson)" (free in the Market), so try installing that to see if you are now golden.

Good luck.
 
I've been a lurker here for awhile, but wanted to jump in and add that this option for rooting the phone was super easy.

I bought my Eris in June of 2010, and started to hate it within a few weeks because it was so slow. I was afraid to root it because I was worried about bricking the thing.

This was painless and I also installed a custom ROM which allowed for overclocking the CPU. It's nowhere near Droid X fast, but it is much more zippy than it was.

So, many thanks to the developers on this!
 
scary alien said:
jmomma1203,

Okay, so I looked at the CachCleaner app in the Market and it does indeed say that BusyBox is needed. But it also says that you can install it from the Market.

I do see "BusyBox by Stephen (Stericson)" (free in the Market), so try installing that to see if you are now golden.

Good luck.
Click to expand...

Thanks for all of your help ScaryA. Just in case anyone else ever asks, I now know what the problem was. The Rom I flashed has BusyBox 1.16 built in. After rooting, I downloaded BusyBox from the Market to install BusyBox because I assumed it wasn't there. It updated to 1.17 or 1.18 and it was all downhill from there. Someone in another forum told me that these BusyBox versions don't work on Eris. I'd say he's right. :)

Anyway, the fix was simple. I wiped the phone, reflashed the Rom, and now I'm good to go.
 
Rooted with the one click method over the past weekend. Could have done the other way but choose to wait it out. I previously had gone form 1.6 to 2.1 v2 to 2.1 v3 and now to root with xrtSense rom. The process was easy and effective. I have tried out many different roms now, but this one click method was flawless. Thanks again to the creator.
 
I tried the other easy method of rooting and I am unable to backup or load new ROMS because my trackball click no longer works.

Could this method give me hope of the trackball working again so that I can get the Froyo I so desire?
 
eyefarted said:
I tried the other easy method of rooting and I am unable to backup or load new ROMS because my trackball click no longer works.

Could this method give me hope of the trackball working again so that I can get the Froyo I so desire?
Click to expand...

eyefarted,

It does seem that the Achilles heel of the Eris is the trackball. Something about the proximity of the trackball to the USB connector sometimes leads to it malfunctioning.

Unfortunately, this 1-click method and virtually all of the other methods espoused in the eris-all-things-root forum use the Amon_RA custom recovery which requires the use of a trackball.

There is a custom recovery called ClockworkMod that does not use the trackball (it uses vol-up and vol-down), but some (but not all) have reported issues with this custom recovery on the Eris (it seems like the issues have been linked to the use of the ROM manager application). Here's some threads discussing this:

http://androidforums.com/eris-all-t...ete-clockwork-mod-replace-amons-recovery.html

http://androidforums.com/eris-all-things-root/102682-phone-wont-boot-into-recovery-help.html

http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies-4.html

I do think that there are probably still some Eris users out there that are using ClockworkMod because of their trackball issues, but I also think that there are more that have simply obtained a refrurb from VZW rather than deal with these issues.

If you are really set on keeping your current phone and wanting to try to use ClockworkMod recovery, I would suggest posting a new thread to solicit advice from those folks that are still successfully using it in lieu of Amon_RA's custom recovery.

Good luck and welcome to the forums!
 
Is step #3 In jcase instructions for his program the point where the reboot is done while holding the volume up button?

Thanks
 
Hi,

I have never done a root before, and I have a few questions. I have a droid eris running OTA Android 2.1.

If I use the one click method from jcase do I have to flash the rootme.zip first to root my Droid Eris, or can I just load any custom ROM that I want at that point? So, in other words, Do I gain root access before flashing the rootme.zip or after?

Also, I want to do a backup of my current ROM so that if anything goes wrong I can revert back. When during the process should I do this, and any suggestions on how I should? From what I have read, I can use Amon's recovery to do a backup.

I want to put a custom Froyo ROM on to my Eris. Is there a way to back up all of my apps and then reload them into the Froyo environment? Will there be compatibility issues?

Thanks for the help.
 
scary alien said:
eyefarted,

It does seem that the Achilles heel of the Eris is the trackball. Something about the proximity of the trackball to the USB connector sometimes leads to it malfunctioning.

Unfortunately, this 1-click method and virtually all of the other methods espoused in the eris-all-things-root forum use the Amon_RA custom recovery which requires the use of a trackball.

There is a custom recovery called ClockworkMod that does not use the trackball (it uses vol-up and vol-down), but some (but not all) have reported issues with this custom recovery on the Eris (it seems like the issues have been linked to the use of the ROM manager application). Here's some threads discussing this:

http://androidforums.com/eris-all-t...ete-clockwork-mod-replace-amons-recovery.html

http://androidforums.com/eris-all-things-root/102682-phone-wont-boot-into-recovery-help.html

http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies-4.html

I do think that there are probably still some Eris users out there that are using ClockworkMod because of their trackball issues, but I also think that there are more that have simply obtained a refrurb from VZW rather than deal with these issues.

If you are really set on keeping your current phone and wanting to try to use ClockworkMod recovery, I would suggest posting a new thread to solicit advice from those folks that are still successfully using it in lieu of Amon_RA's custom recovery.

Good luck and welcome to the forums!
Click to expand...

My phone is a new to me refurb. When setting it up like my other one (had the trackball problem) I decided to try to root. I assumed that the trackball didn't work because of a problem in the rooting process.

So what you are telling me is rooting doesn't do this, the refurb was defective?
 
eyefarted said:
My phone is a new to me refurb. When setting it up like my other one (had the trackball problem) I decided to try to root. I assumed that the trackball didn't work because of a problem in the rooting process.

So what you are telling me is rooting doesn't do this, the refurb was defective?
Click to expand...

Well, I can tell you that rooting (or any other software that I'm aware of) won't affect your trackball.

You should know that lots of folks have returned their Eris(es) [Eri?] due to trackball issues...perhaps VZW did not fix the refurb that was given to you...

Unfortunate...good luck.
 
starflorida said:
Is step #3 In jcase instructions for his program the point where the reboot is done while holding the volume up button?

Thanks
Click to expand...

The security hole which is exploited to get the Amon_RA recovery installed requires that the phone be rebooted in the usual fashion at least once. So, to clarify, do a regular reboot (at least once) before you shut the phone down and restart it with Vol-up+End.

eu1
 
cb0329 said:
Hi,

I have never done a root before, and I have a few questions. I have a droid eris running OTA Android 2.1.

If I use the one click method from jcase do I have to flash the rootme.zip first to root my Droid Eris, or can I just load any custom ROM that I want at that point? So, in other words, Do I gain root access before flashing the rootme.zip or after?

Also, I want to do a backup of my current ROM so that if anything goes wrong I can revert back. When during the process should I do this, and any suggestions on how I should? From what I have read, I can use Amon's recovery to do a backup.

I want to put a custom Froyo ROM on to my Eris. Is there a way to back up all of my apps and then reload them into the Froyo environment? Will there be compatibility issues?

Thanks for the help.
Click to expand...

cb0329,

jcase's app installs a custom recovery partition on your phone. Then, the step of flashing the rootme.zip or the custom rooted ROM is what actually gives you root. The rootme.zip does this by installing the su program and SuperUser app on your phone. A custom ROM (should) already have the su program on it and should also have the SuperUser app on it too. So, you gain root access/capability after flashing one of these items.

Regarding your ROM backup question, you could (and probably should) make a Nandroid backup of your phone prior to flashing anything. So, when you enter the custom recovery and before you flash either the rootme.zip or a custom ROM, select "Backup/Restore" from Amon_RA's custom recovery menu, then select "Nand Backup". This will make a backup of phone and allow you to restore it to its native state (excepting the presence of the custom recovery partition) should the need arise. BTW, there are excellent instructions and diagrams of this backup in erisuser1's thread http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies.html#post1186824, specifically figures 33 - 37.

By the way, its always a good idea to make a Nandroid backup before you do anything scary to your phone (like flashing something, deleting system apps, etc.).

Also, make sure that you do the wipes that are required (check the dev's ROM thread) before flashing a custom ROM. The Froyo ROMs in particular since they often require a wipe of Dalvik-cache in addition to the "Wipe data/factory reset"

As far as the app backups go, lots of folks use Titanium Backup Pro. The paid (Pro) version will apparently backup both your apps and their data. Search the forums for more information regarding this (I don't have that many apps, so its not so much an issue for me and I don't mind doing it manually). There should not be compatibility issues, but you might want tho check the various threads on the various Froyo ROMs to see if folks have reported any issue.

Hope that helps...cheers!

P.S. welcome to the AndroidForums!
 
eyefarted said:
I tried the other easy method of rooting and I am unable to backup or load new ROMS because my trackball click no longer works.

Could this method give me hope of the trackball working again so that I can get the Froyo I so desire?
Click to expand...

Have you tried cleaning the trackball? Alcohol wipes, run across the trackball several times, rolling it around and clicking, etc, have remedied problems with the trackball for some users.
 
Frisco said:
Have you tried cleaning the trackball? Alcohol wipes, run across the trackball several times, rolling it around and clicking, etc, have remedied problems with the trackball for some users.
Click to expand...

+1 Frisco, and congratulations on the Guide status!

Very nice and well-deserved (and about time, I must say :)).
 
Well, he's so very well loved.


make_android_doll.jpg
 
scary alien said:
cb0329,

jcase's app installs a custom recovery partition on your phone. Then, the step of flashing the rootme.zip or the custom rooted ROM is what actually gives you root. The rootme.zip does this by installing the su program and SuperUser app on your phone. A custom ROM (should) already have the su program on it and should also have the SuperUser app on it too. So, you gain root access/capability after flashing one of these items.

Regarding your ROM backup question, you could (and probably should) make a Nandroid backup of your phone prior to flashing anything. So, when you enter the custom recovery and before you flash either the rootme.zip or a custom ROM, select "Backup/Restore" from Amon_RA's custom recovery menu, then select "Nand Backup". This will make a backup of phone and allow you to restore it to its native state (excepting the presence of the custom recovery partition) should the need arise. BTW, there are excellent instructions and diagrams of this backup in erisuser1's thread http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies.html#post1186824, specifically figures 33 - 37.

By the way, its always a good idea to make a Nandroid backup before you do anything scary to your phone (like flashing something, deleting system apps, etc.).

Also, make sure that you do the wipes that are required (check the dev's ROM thread) before flashing a custom ROM. The Froyo ROMs in particular since they often require a wipe of Dalvik-cache in addition to the "Wipe data/factory reset"

As far as the app backups go, lots of folks use Titanium Backup Pro. The paid (Pro) version will apparently backup both your apps and their data. Search the forums for more information regarding this (I don't have that many apps, so its not so much an issue for me and I don't mind doing it manually). There should not be compatibility issues, but you might want tho check the various threads on the various Froyo ROMs to see if folks have reported any issue.

Hope that helps...cheers!

P.S. welcome to the AndroidForums!
Click to expand...
Thanks a lot for getting back to me.

So should I do a back up before running the one-click root app? or will I not be able to until Amon's RA is flashed? So, if I have to wait to flash Amon, then do a nandroid back up, will my restore image really be back to stock 2.1 that was on the phone, and be good enough to send back to VZW if I need to, or will it also still have what ever the one-click root app installed as well as Android 2.1?

I hope that makes sense.

Thanks for the help again.
 
cb0329 said:
Thanks a lot for getting back to me.

So should I do a back up before running the one-click root app? or will I not be able to until Amon's RA is flashed?
Click to expand...

The "Nandroid" (or "Nand") backup facility is part of the Amon_RA recovery boot installation - so, yeah, you can't do that kind of backup until after the first part of the "One Click" method.

cb0329 said:
So, if I have to wait to flash Amon, then do a nandroid back up, will my restore image really be back to stock 2.1 that was on the phone, and be good enough to send back to VZW if I need to, or will it also still have what ever the one-click root app installed as well as Android 2.1?

I hope that makes sense.

Thanks for the help again.
Click to expand...


That is actually a very good question, and quite insightful.

If you restore the "Stock" Nandroid backup, everything on the phone will have been returned back to it's original state - with the exception of the recovery boot partition.

But, here's the cool part. You can use the recovery boot to.... wait for it ... replace the recovery boot partition. (It is running in memory when you are interacting with Amon_RA, so it can be safely over-written in system flash memory)

The Amon_RA recovery boot also runs "adbd", which is known as "USB debugging" in the regular OS. So, if you learn how to install the SDK and get "adb" running on your PC, you can replace the recovery partition this way:

- boot into Amon_RA
- plug USB cable to PC
- run the command "adb devices" to see if you are connected succesfully
- unpack the "Leak-V3" PB00IMG.ZIP file, and, with the "recovery.img" file extracted from there, do a:
Code: 
  adb mount /sdcard
  adb push recovery.img /sdcard/recovery.img
  adb md5sum /sdcard/recovery.img
  [COLOR=red][I]( at this point you would halt if the md5 signature was wrong )[/I][/COLOR]
  adb flash_image recovery /sdcard/recovery.img
  adb umount /sdcard

Obviously, you would first restore the original Nandroid backup, and then do this process as the very last step.

There are other ways to unroot your phone too. If you are worried about having to do it in the future, make sure you have downloaded a copy of the Leak-V3 PB00IMG.ZIP file and saved a copy of these directions.

eu1
 
You must log in or register to reply here.
Back
Top Bottom