i have successfully rooted my droid eris (according to this thread) but when i loaded the terminal emulator onto my phone and did the "su" command, it says permission denied and gives me the "$" sign .. before i decide to wipe my phone and install a custom rom, i want to make sure that i am actually rooted and wiping to install a rom will not completely mess up my phone .. i appreciate any help!
Ran through the steps a second time, same thing. All the way through the second step with it saying " you have root" and reboot. Hold Vol+ and End at the same time and it boots normal.....
I also have the same problem. Running the scripts went fine. It said "you have root." But I cannot run the next part which is powering on the phone with vol+/End and then flashing. It just loads as normal.
In addition, I feel as if my phone loads slower if not runs slower overall. I'm a little bit nervous now about what I did to my phone :-P.
Okay, so the way around the vol+/end problem is simply vol-/end and then "recovery."
From there I just continued to follow the instructed on the front page.
One thing that popped in my mine was when I made sure that the rom I was using was still in .zip format before doing the clearing. Had I not done that, I don't know what would have happened when attempting to flash.
Papadroid rules! You are absolutely correct. I did a little more research and finally figured-out how I think the mid.txt exploit works (devilishly simple, actually). Anyway, I edited my original reply to your post to include the following:
edit: okay, now that I'm looking at the contents of engtools.zip, I see it contains the superuser.apk and a replacement su command. I guess I don't really understand how the mid.txt link exploit actually gains you root (or rather, what it does to allow you to install the custom recovery image). Still looking...
2nd edit: okay, I got it! Papadroid is absolutely right! You do need to install a custom ROM and/or the engtools.zip in order to get root access. The way the mid.txt exploit works is to soft link the recovery partition (/dev/mtd/mtd1) to a file (/data/local/rights/mid.txt) that already has full access ("a=rwx") permissions. This is what allows you to overwrite the recovery partition with a custom recovery and subsequently allow you to install a root (custom) ROM.
I don't think anyone has actually explained how the exploit works before (state secret?) or maybe I just hadn't run across it yet...
Sorry for the confusion, but I really learned a lot from researching this!
Wow I posted a big long response to this last night on my phone, and I now see that it never posted. Nice. Another reason Im looking foreward to root lol. First off thank you Papadroid and Scary alien for all of your efforts and research yesterday. I was afk ( had to put son down for a nap, and of course had to take one with him lol) I believe that I am caught up with the conversation though. If I understand correctly, I need to either flash the engtool.zip from my sd card or a custom rom, and this should fix my problem correct? This is no problem since both are on my sd card. My noob question is this. To flash either one of these I just do it the same as we did when we instaled the leaked versions of 2.1. ( put on root of sd card turn of phone vol down and end the option install from sd card right? I know its probably basic android 101 , but the only experience I have with flashing is lv2 and lv3. as long as it is vol down and end Im golden. vol up and end is where my trackball issue comes into play. also which one would you advise , the engtool.zip, or a rom or both? again thank you both for you efforts
edit 0715 i tried the vol down and end and it sent me back to recovery which is where the track ball freezes i see the opt install zip from sd card, but cant get to it. looks like the only way to get this to work is to go back to adb commands which suckk cause i was stuck on that too adb command not recognized etc but that is a different thread. oh well might just go with the wait til oct option.
Last edited by kamots; July 22nd, 2010 at 06:19 AM.
I also have the same problem. Running the scripts went fine. It said "you have root." But I cannot run the next part which is powering on the phone with vol+/End and then flashing. It just loads as normal.
In addition, I feel as if my phone loads slower if not runs slower overall. I'm a little bit nervous now about what I did to my phone :-P.
Help please?
I am noticing this to.my phone is super lagtastic when I type on it now. I dont know if it has anything to do with this, or the ota i got the other day either way ,it sucks. come on root! lol
Last edited by kamots; July 22nd, 2010 at 06:14 AM.
The only lag I noticed is when it first starts up and needs to get running. But that maybe the way it is. Before doing the prior steps, I had maybe rebooted the phone 3 or 4 times within a couple weeks of having it. So I'm going to go with it being ok for now.
i have successfully rooted my droid eris (according to this thread) but when i loaded the terminal emulator onto my phone and did the "su" command, it says permission denied and gives me the "$" sign .. before i decide to wipe my phone and install a custom rom, i want to make sure that i am actually rooted and wiping to install a rom will not completely mess up my phone .. i appreciate any help!
just confirming that you did the nand back up / wipe/ rom install? cause i had this problem to but that caus eof track ball issued i couldnt select it if your track ball works your should be golden, and I am jealous lol read through this thread though , either papadroid or scary alien answered the same question for me short answer if I understood, is your dont really have root until the whole process is completed.
edit : this makes sence because if you go back and look at both scripts you are instructed to uncheck the super user box. the terminal emulator ask for super user access i believe
Last edited by kamots; July 22nd, 2010 at 06:57 AM.
This brings me to a new question. since i cant install from my sd card through recovery, can i send the engtools.zip or custom rom through gscript lite and install them that way? ( please say yes lol)
This brings me to a new question. since i cant install from my sd card through recovery, can i send the engtools.zip or custom rom through gscript lite and install them that way? ( please say yes lol)
kamots,
Sorry, but I think you have to flash engtools.zip just like you would have to for a custom ROM .
I wish I could give you my trackball setup, lol. I have very rarely ever used it.
Clockwork Mod Recovery doesn't use the track ball to move betweeen selections, it uses the volume up and down buttons. Is there a way to edit the second script to get it to load instead of amon's?
The Following 2 Users Say Thank You to varkie For This Useful Post:
Sorry, but I think you have to flash engtools.zip just like you would have to for a custom ROM .
I wish I could give you my trackball setup, lol. I have very rarely ever used it.
hmmm . you must not have gotten the memo. no bad news before 9am. lol j/k well that sucks Ill just stick with it until oct then. I appreciate all your help and advice.
Clockwork Mod Recovery doesn't use the track ball to move betweeen selections, it uses the volume up and down buttons. Is there a way to edit the second script to get it to load instead of amon's?
I wonder if re downloading htc sync and re installing drivers to my phone would help?
I think it would be better to try and get the adb working rather than flashing clockwork recovery. For one it's always a good idea to have a working adb with a rooted phone just in case. And I have heard of other eris users having major problems with clockwork recovery. Clockwork recovery is great with other phones like my Droid but for some reason it has problems on the Eris.
The Following User Says Thank You to Papadroid For This Useful Post:
I think it would be better to try and get the adb working rather than flashing clockwork recovery. For one it's always a good idea to have a working adb with a rooted phone just in case. And I have heard of other eris users having major problems with clockwork recovery. Clockwork recovery is great with other phones like my Droid but for some reason it has problems on the Eris.
This would be great is i could get my adb shell to work. comp wont recognize phone when i type adb devices, whoooooollllleeeee nother issue. will have to start that process from scratch on another comp after work today.lol have another data cable so im hoping that will solve the issue. out of 50 or so tries i have only seen found new hardware loading adb message twice.
Last edited by kamots; July 22nd, 2010 at 08:48 AM.
Reason: spelling
This would be great is i could get my adb shell to work. comp wont recognize phone when i type adb devices, whoooooollllleeeee nother issue. will have to start that process from scratch on another comp after work today.lol have another data cable so im hoping that will solve the issue. out of 50 or so tries i have only seen found new hardware loading adb message twice.
I found this thread over at xda that should be able to help you load roms via adb if you are able to get it running. There are links in thread under Scripts available via adb which gives more details on using the scripts. From looking at it a little it looks as though you may have to partition your sd card to get it to work properly but I'm not positive on that, you could try it first to see if it works then maybe partition it if it didn't.
I think it would be better to try and get the adb working rather than flashing clockwork recovery. For one it's always a good idea to have a working adb with a rooted phone just in case. And I have heard of other eris users having major problems with clockwork recovery. Clockwork recovery is great with other phones like my Droid but for some reason it has problems on the Eris.
I only suggested it for the people that have trackball issues not for everyone. If the op could edit the file and add Clockwork then edit the script to install it then the problem would be solved for people with trackball problems. You can always flash back to amon's at any time after but of course if you don't have a working trackball you still couldn't use amon's. I see no reason why there couldn't be a second version of script #2 for people with non-functioning trackballs.
Also in the original (day 1) thread on XDA forums by captainkrtek (tereg) for rooting a leaked eris clockwork was the recovery that was installed. And I've been using it for at least a month without problems now. In fact after re-rooting my phone using this method I switced back to it as I like to using ROM Manager.
The Following User Says Thank You to varkie For This Useful Post:
part1 = OK
part2 = OK
REBOOT with volume+ / end = NORMAL STARTUP
REBOOT with volume- / end = STOCK BOOTLOADER
I followed the directions exactly as stated. I even went back and executed part1 / rebooted / executed part2 / rebooted and the same results were reached.
The only difference which should not matter ( at least I dont believe so ) is that I downloaded the files on my computer and transferred them over to their correct directories on the phone through USB.
ERIS 2.1 OTA
Just wondering if anyone has encountered the issue above and has been able to work around it...Thanks...
I only suggested it for the people that have trackball issues not for everyone. If the op could edit the file and add Clockwork then edit the script to install it then the problem would be solved for people with trackball problems. You can always flash back to amon's at any time after but of course if you don't have a working trackball you still couldn't use amon's. I see no reason why there couldn't be a second version of script #2 for people with non-functioning trackballs.
Also in the original (day 1) thread on XDA forums by captainkrtek (tereg) for rooting a leaked eris clockwork was the recovery that was installed. And I've been using it for at least a month without problems now. In fact after re-rooting my phone using this method I switced back to it as I like to using ROM Manager.
alright , since i am having the worst luck with root , lets weigh options. if I flash clockwork, how much damage can it do to my phone if it goes wrong? or do we know?
I found this thread over at xda that should be able to help you load roms via adb if you are able to get it running. There are links in thread under Scripts available via adb which gives more details on using the scripts. From looking at it a little it looks as though you may have to partition your sd card to get it to work properly but I'm not positive on that, you could try it first to see if it works then maybe partition it if it didn't.
thank you i will take a look at this
edit alright i downloaded it to a thumb drive for later, but now that i look at it , i believe this is the amon ra recovery that i already have on my phone, unless im looking at it wrong should I re flash this? also im not to familiar with partitioning the sd card , i will have to research it
Last edited by kamots; July 22nd, 2010 at 09:53 AM.
I only suggested it for the people that have trackball issues not for everyone. If the op could edit the file and add Clockwork then edit the script to install it then the problem would be solved for people with trackball problems. You can always flash back to amon's at any time after but of course if you don't have a working trackball you still couldn't use amon's. I see no reason why there couldn't be a second version of script #2 for people with non-functioning trackballs.
Also in the original (day 1) thread on XDA forums by captainkrtek (tereg) for rooting a leaked eris clockwork was the recovery that was installed. And I've been using it for at least a month without problems now. In fact after re-rooting my phone using this method I switced back to it as I like to using ROM Manager.
For the record I use and love clockwork recovery on my Droid. And I understand that you are only suggesting it to those with trackball issues but like I said there have been many users with problems on clockword with an Eris. But I will concede that if you're able to use adb and Amon_Ra you should be able to flash clockwork and then back to Amon_Ra if clockwork doesn't work.
alright , since i am having the worst luck with root , lets weigh options. if I flash clockwork, how much damage can it do to my phone if it goes wrong? or do we know?
The worst that should happen is it won't boot into recovery. If that is the case then you can just flash back to Amon_Ra.
For the record I use and love clockwork recovery on my Droid. And I understand that you are only suggesting it to those with trackball issues but like I said there have been many users with problems on clockword with an Eris. But I will concede that if you're able to use adb and Amon_Ra you should be able to flash clockwork and then back to Amon_Ra if clockwork doesn't work.
Even if he can root his phone through adb and get amon's on it he still wouldn't be able to use it as it requires a trackball. He is stuck using another recovery. There are other recoveries out there besides clockwork and amon's I was just familar with clockwork because that is the ones the devs used on the eris leak root method and I just kept using it.
I'm not sure if script root_part2 uses fastboot to install amon's but all that may be required is to replace the amon's recovery image in the gscript tools folder with the clockwork image (or other recovery image) making sure it has the same name as the original image file, and see if that works.
Just wondering if anyone has encountered the issue above and has been able to work around it...Thanks...
cnp112, are you trying to invoke the custom recovery? (i.e., power-off your phone, then press Volume-UP button AND the End/Power buttons simultaneously)
I'm not sure if script root_part2 uses fastboot to install amon's but all that may be required is to replace the amon's recovery image in the gscript tools folder with the clockwork image (or other recovery image) making sure it has the same name as the original image file, and see if that works.
cnp112, are you trying to invoke the custom recovery? (i.e., power-off your phone, then press Volume-UP button AND the End/Power buttons simultaneously)
It seems as though several people have had this problem of getting into recovery. I believe another way you can get to recovery is by holding the call/send button and the power/end button at the same time. It will give you two options fastboot or recovery, select recovery.
this is a link to the latest clockwork mod recovery image. you have to scroll down through the list to the droid eris. it would have to be renamed "recovery" if someone wanted to try it who doesn't ahve a working trackball.
The Following User Says Thank You to varkie For This Useful Post:
It seems as though several people have had this problem of getting into recovery. I believe another way you can get to recovery is by holding the call/send button and the power/end button at the same time. It will give you two options fastboot or recovery, select recovery.
My problem is that when I select recovery it sends me to the three dancing droids bootup image and then it just locks up. I had it sit for about 20 min and it still hadn't unfroze, so I really don't know what to do from there.
cnp112, are you trying to invoke the custom recovery? (i.e., power-off your phone, then press Volume-UP button AND the End/Power buttons simultaneously)
I have actually tried this several times as well. I have powered down my phone and rebooted holding VOLUME UP / END simultaneously...however I enter the normal phone startup. If I hold VOLUME DOWN / END then I enter the stock recovery.
My problem is that when I select recovery it sends me to the three dancing droids bootup image and then it just locks up. I had it sit for about 20 min and it still hadn't unfroze, so I really don't know what to do from there.
Quote:
Originally Posted by cnp112
I have actually tried this several times as well. I have powered down my phone and rebooted holding VOLUME UP / END simultaneously...however I enter the normal phone startup. If I hold VOLUME DOWN / END then I enter the stock recovery.
Try starting over including redownloading the gscript.zip file. Delete the current directories for the gscript on your sdcards first. The only thing I can think of is that your downloaded files are corrupt.
Try starting over including redownloading the gscript.zip file. Delete the current directories for the gscript on your sdcards first. The only thing I can think of is that your downloaded files are corrupt.
I tried this already. I redownloaded it, and this time extracted everything from my phone, and ran them again. It did not produce any results.
Try starting over including redownloading the gscript.zip file. Delete the current directories for the gscript on your sdcards first. The only thing I can think of is that your downloaded files are corrupt.
I tried this is as well. The first time I downloaded to computer - then moved the files to the phone. The second time I downloaded straight to phone. Both times I received the same result - either normal phone startup(volume up / end) OR stock bootloader(volume down/end)
I tried this already. I redownloaded it, and this time extracted everything from my phone, and ran them again. It did not produce any results.
Quote:
Originally Posted by cnp112
I tried this is as well. The first time I downloaded to computer - then moved the files to the phone. The second time I downloaded straight to phone. Both times I received the same result - either normal phone startup(volume up / end) OR stock bootloader(volume down/end)
OK, lets try this. Go into your sdcard/gscript/tools folder and delete flash_image and recovery.img. Then go here and download the hack-v4. Unzip the hack-v4 same as you did the gscript.zip. Copy and paste the flash_image and recovery.img from hack-v4 to gscript/tools and start over.
ok guys .. im rooted and have downloaded senseable 3 .. everything installed properly as far as i can tell .. so it appears that this post is definitely the best out right now .. especially since i was told over and over i couldnt root with hboot 1.49 .. thanks!!
OK, lets try this. Go into your sdcard/gscript/tools folder and delete flash_image and recovery.img. Then go here and download the hack-v4. Unzip the hack-v4 same as you did the gscript.zip. Copy and paste the flash_image and recovery.img from hack-v4 to gscript/tools and start over.
That worked, I now have the recovery screen showing. Thanks tremendously!
OK, lets try this. Go into your sdcard/gscript/tools folder and delete flash_image and recovery.img. Then go here and download the hack-v4. Unzip the hack-v4 same as you did the gscript.zip. Copy and paste the flash_image and recovery.img from hack-v4 to gscript/tools and start over.
ok wait what?!! did you fin a fix? you are my hero. I will try this when I get home and report back. can i do all this with my phone, or do i have to have a pc too?
Papadroid is the man! Sorry, been to slammed here at work to be of much help today.
Work!!! What is that? Maybe I'll get to that pile of paperwork on my desk at some point today, LOL.
Edit: I'm not even the man sitting next to the man, sitting next to the man, sitting next to EU1! I'm just your average IT guy that loves android and is trying to learn some of this linux stuff.
Last edited by Papadroid; July 22nd, 2010 at 12:42 PM.
ok wait what?!! did you fin a fix? you are my hero. I will try this when I get home and report back. can i do all this with my phone, or do i have to have a pc too?
Don't want to get your hopes up again, but I think Papadroid just had him basically re-download and install the files from a different source (wag3slav3's thread, I think) to make sure they were good, clean, whole files. Papadroid, can you confirm?
Did you follow / understand the discussion about using the Clockworkmod custom recovery above? If so, you might be able to use it in place of the recovery.img (Amon_RA's that is, that is used by this thread). Since it apparently doesn't need a trackball, it might work for you. I have no first-hand experience with it though, so I can't really encourage you in that direction if you know what I mean (I've read the same cautions about it posted previously).
OK, lets try this. Go into your sdcard/gscript/tools folder and delete flash_image and recovery.img. Then go here and download the hack-v4. Unzip the hack-v4 same as you did the gscript.zip. Copy and paste the flash_image and recovery.img from hack-v4 to gscript/tools and start over.
I will definitely give this a try when I get home - I see that it has already worked for Kaseladen. Thanks Papadroid.
ok wait what?!! did you fin a fix? you are my hero. I will try this when I get home and report back. can i do all this with my phone, or do i have to have a pc too?
Quote:
Originally Posted by scary alien
Don't want to get your hopes up again, but I think Papadroid just had him basically re-download and install the files from a different source (wag3slav3's thread, I think) to make sure they were good, clean, whole files. Papadroid, can you confirm?
Did you follow / understand the discussion about using the Clockworkmod custom recovery above? If so, you might be able to use it in place of the recovery.img (Amon_RA's that is, that is used by this thread). Since it apparently doesn't need a trackball, it might work for you. I have no first-hand experience with it though, so I can't really encourage you in that direction if you know what I mean (I've read the same cautions about it posted previously).
Yes all I had them do was replace two files in the process because they were not able to load recovery at all which is not kamots problem. Kamots what you can do is download the clockwork recovery from the below link that varkie provided. Place the recovery image into your sdcard/gscript/tools folder. Delete your old recovery.img and rename the new Clockwork image to recovery.img Then start the process again and it will give you the clockwork recovery.
this is a link to the latest clockwork mod recovery image. you have to scroll down through the list to the droid eris. it would have to be renamed "recovery" if someone wanted to try it who doesn't ahve a working trackball.
The Following User Says Thank You to Papadroid For This Useful Post:
Yes all I had them do was replace two files in the process because they were not able to load recovery at all which is not kamots problem. Kamots what you can do is download the clockwork recovery from the below link that varkie provided. Place the recovery image into your sdcard/gscript/tools folder. Delete your old recovery.img and rename the new Clockwork image to recovery.img Then start the process again and it will give you the clockwork recovery.
ok yep i got excited thinking the other thing was the fix.i think i am caught up now. so I need to copy the clockwork recovery go into gscrips tools delete that recovery renane clockwork recov ro recovery.zip and replace said file right? i just want to be crystal clear before i do this
ok yep i got excited thinking the other thing was the fix.i think i am caught up now. so I need to copy the clockwork recovery go into gscrips tools delete that recovery renane clockwork recov ro recovery.zip and replace said file right? i just want to be crystal clear before i do this
The file you downloaded should be recovery-clockwork-2.5.0.1-desirec.img you're going to rename it to recovery.img Just make sure to delete the old recovery.img first.
After getting some time to look at it again, I went and tried to get into the bootloader, but this time went through the original one, clicked on system recovery, and it brought me to the screen pictured at figure 32. Able to install KaosFroyov24 finally. Ill see how I like it.
Took forever to boot up, like the how to states, and was lagy at first. Ill see how it is in a bit.
RyRy
P.S. Im already missing the SenseUI.....any way I can turn it back on? or am I really better off without it?
Last edited by ticklemedaly; July 22nd, 2010 at 03:08 PM.
The Following 2 Users Say Thank You to ticklemedaly For This Useful Post:
The file you downloaded should be recovery-clockwork-2.5.0.1-desirec.img you're going to rename it to recovery.img Just make sure to delete the old recovery.img first.
alright. i know its probably semantics, but i am getting nervous. do you use the rom or manually. looking for what you would do since you know a ton more
and all this time i have been wrong my screen looks like 32, not 31. sorry
ok so i dowloaded the rom and i want to flash clockwork right? will this just put is on my sd card and I can move it manually from there to gscripts ?
Last edited by kamots; July 22nd, 2010 at 03:23 PM.
alright. i know its probably semantics, but i am getin nervous. do you use the rom or manually. looking for what you would do since you know a ton more
I'm not sure what you're asking. BTW, there is no reason to be nervous but I understand.
The HTC Droid Eris launched for Verizon Wireless on November 6th in part as the carrier's first Android Phone. However it was overshadowed by the other member of the inaugural Verizon Droid duo - the Motorola Droid. The Droid Eris might look fa... Read More
ok so now im stuck
BTW, there is no reason to be nervous but I understand.
