-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [Revised] Rooting Gingerbread 2.3.5 Dummies Guide
- Thread starter ocnbrze
- Start date
-
- Tags
- htc evo 4g
Rxpert83
Dr. Feelgood
no it needs to be on the root of the card no folders. it looks correct as the files are extracted as well.
JacobGates
Member
yes, step 5 has not been an issue sense I was told to hit the power button after the volumes. they are extracted, i still have the zip files, do you think I should extract them again and replace the ones on the sdcard?
and the card is an 8gb, the one that sprint gave me when I got the phone.
maybe try a fresh download of each file again might help. also maybe you might want to think about re-formatting the card or try a different card.
JacobGates
Member
Okay, I will try the fresh download first. If I reformat the card what way is best? on the phone or on the computer?
on the phone I would suggest unless ocn thinks otherwise...
JacobGates
Member
on the phone I would suggest unless ocn thinks otherwise...
redownloaded all the files and started from the very beginning and still got the same thing at step 12: No such file or directory
so I am going to format my sdcard and try again.
JacobGates
Member
I formated the sdcard via the phone and put the flash_image and mtd-eng files back on the card, still having the same thing at step 12: No such file or directory. I noticed in the command prompt when I do the
adb shell /data/local/tacoroot.sh --root
command it has usage instructions and one, --recovery, says "you must have booted recover at least once after your last factory reset." should I do this command before --setup or does step 5 count as that?
adb shell /data/local/tacoroot.sh --root
command it has usage instructions and one, --recovery, says "you must have booted recover at least once after your last factory reset." should I do this command before --setup or does step 5 count as that?
As long as you did the steps in exact order, step 5 should be done and then you are done booting to recovery....i.e....after a successful step 5, you are good to go...
well taco root uses an exploit that is through the recovery log. you have to go there once in order for taco root to work. however, when you type su and you get # that means you have root access. if you get a $ then taco root did not work.
I just noticed something that made me think of another person's issue.....
At step 8,9,10...it has the "adb shell" followed by the rest of the command.
Shouldn't a person hit the "enter" key after the "adb shell" command, then issue the rest of the command? follow?
At step 8,9,10...it has the "adb shell" followed by the rest of the command.
Shouldn't a person hit the "enter" key after the "adb shell" command, then issue the rest of the command? follow?
JacobGates
Member
then why is this not working? aaah, it's killing me. do you think the /sdcard/flash_image could be different on my phone. Like maybe not "sdcard" but "sd" or something like that?
JacobGates
Member
so you are saying it should be like this?:
adb shell (press enter)
push tacoroot.sh /data/local/
adb shell (press enter)
chmod 755 /data/local/tacoroot.sh
so on...
no not like that
once you are in adb shell there is no need to enter it again.
you just need to be in adb shell and then enter the commands hitting enter after each one.
JacobGates
Member
okay, something interesting happened this time. I tried what Mikestony said about the adb shell and it acted a little differently. After doing the /data/local/tacoroot.sh --setup command it said "rm failed for /data/data/recovery/log, No such file or directory". I made note of this but continued and step 12 still said flash_image wasn't there. but ocn, you said that tacoroot uses an exploit in the recovery log so I thought this might be the issue.
So at step 8, the only time he needs to type "adb shell".
at step 9 and 10, no need to type "adb shell"
Now I'm getting confused
oh i see what you are saying. no in taco root you need to type adb shell with the taco root command and then hit enter.
in the step 11 you need to enter adb shell and then enter the adb commands.
JacobGates
Member
I also just tried something like that: in step 12 i just typed "cat" then typed the rest of the command and the other commands after that. after typing cat it looked like this:
adb shell (step 11)
# cat
cat
/sdcard/flash_image > /data/flash_image
/sdcard/flash_image > /data/flash_image
/sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
chmod 755 /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
/data/flash_image misc /sdcard/mtd-eng.img
/data/flash_image misc /sdcard/mtd-eng.img
/data/local/tacoroot.sh --undo
/data/local/tacoroot.sh --undo
/data/local/tacoroot.sh --undo
the first of each is my input the next to is what it put out... not sure what this means or if it did anything.
Not sure either....what does your phone say now??
JacobGates
Member
well I continued with the instructions (in hope that it worked) and when I got to the part where the bootloader was supposed to update the PC36IMG it said something fail do I want to reboot... I rebooted and check the hboot and it still says 2.18.
this is closer. the out put needs to match what is in the guide exactly or it will not work. you have to stop skipping things. without the right output the your misc partition has not been downgraded which in turn running a Pc36IMG ruu will not work.
JacobGates
Member
not meaning to sound rude but I am not skipping things. I am doing them, i'm just not getting what is said I should be getting and continuing assuming that it was done successful. there is a problem with the picture in the instructions and what I am told to do... the picture shows "su" was typed... but the instruction do not say to type su at any point. Am I supposed to type su?
su is only needed if you have a "$" in the command line. typing su should yield "#". if you have "#" then you do not need to type su.
if everything matches up with what is shown then your bootloader should have changed from unlocked back to locked.
JacobGates
Member
well it's not matching up... i either get the no such file message or if I type cat then press enter then type the commands i get that triple output look but the # only appears once before I type cat. here is an exact copy and paste of what my prompt looks like with what I tried:
C:\Users\Jacob (last name)\Desktop\andriod>adb shell
# cat
cat
/sdcard/flash_image > /data/flash_image
/sdcard/flash_image > /data/flash_image
/sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
chmod 755 /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
/data/flash_image misc /sdcard/mtd-eng.img
/data/flash_image misc /sdcard/mtd-eng.img
/data/local/tacoroot.sh --undo
/data/local/tacoroot.sh --undo
/data/local/tacoroot.sh --undo
but the way the instructions say look like this:
C:\Users\Jacob (last name)\Desktop\andriod>adb shell
#cat /sdcard/flash_image > /data/flash_image
/sdcard/flash_image: no such file or directory
should I reset the phone to factory settings?