fastboot flash recovery recovery.img didnt do any
thing and cd fastboot flash recovery recovery.img didnt work
i opened cmd through the folder like you said so i know i have that right
I've having some trouble with the tacoroot method as well. Initially the first command worked and I got hung up on the second command with "adb shell /data/local/tacoroot.sh --setup" giving me "permission denied" I tried a few things including reinstalling HTC Sync and now it's giving me "adb server is out of date. killing..." after the first command. I'm still getting "permission denied" and I really have no idea what I did wrong. I followed the instructions a precisely as I could but I'm not sure my phone is making it into recovery mode. Is there any way to tell with it booted up?
welcome to the forums!!!!!!!!!!!
what is your hboot? also did you go into stock recovery first before entering the commands?
You're not running those commands while you're in recovery; booting into recovery is a separate step that has to be done before anything else.I'm 2.18. I followed all the steps to get into stock recovery, but I'm still getting permission denied which is making me think I'm not really making it into stock recovery...
ok sorry forgot to mention that on your phone you need to be in fastboot. so go to the bootloader menu and select fastboot. it is the very first option. once you do that then the command will work.
Does your Bootloader say "UNLOCKED" at the top?<sorry to keep bugging you ocn but i have to the T folowed your instrutions. phone pluged in. in fastboot usb, cmd opened through the andriod folder, fastboot flash recovery recovery.img> i dont understand what im missing.
my understanding this is still not rooted right its just downgrading to android 2.3 correct?
You're not running those commands while you're in recovery; booting into recovery is a separate step that has to be done before anything else.
To boot into recovery, turn the phone completely off (fast boot, under Settings -> Applications needs to be disabled). Then, while holding the Volume Down button, press and hold the Power button, until the white Bootloader screen appears. Use the Volume buttons to select the "RECOVERY" item, and press the power button to accept the selection. The device will reboot, and in a few seconds, you should see a phone with green arrows in a circle, and then in a few more seconds, you should see a phone with a red triangle and an exclamation point. This is the stock recovery. At this point, press both volume buttons and the power button at the same time. In about a second, a menu should appear. The top option, to reboot the device, should already be highlighted. Press the power button to accept.
NOW, you can proceed with the rest of the steps. Make sure USB Debugging is enabled, of course. If you don't do the above prior to running those commands, then it won't work.
I've done all of this, several times in fact, and still get the "permission denied" response. That's why I'm wondering if something is not working right on my phone.
That's ok - It always says that.Maybe this will help, but the yellow text on the stock recovery boot screen says:
E: Can't open /cache/recovery/command
adb push tacoroot.sh /data/local/
adb shell chmod 755 /data/local/tacoroot.sh
adb shell /data/local/tacoroot.sh --setup
Not sure if you're also a member over @ XDA, but try the PC36IMG file attached to this post:Cap yes I am unlocked
That's ok - It always says that.
Ok, so we're good there. OH! I just noticed that ocn missed a step (a very important one, at that!). If you've already done this command:the next command you have to issue is:Code:adb push tacoroot.sh /data/local/
THEN you can follow up with theCode:adb shell chmod 755 /data/local/tacoroot.sh
and everything else that comes after it.Code:adb shell /data/local/tacoroot.sh --setup
We'll have to make sure ocn updates that ASAP. Sorry about that.
Did you issue the other commands successfully? As long as the device is still connected, adb should still be running. Did you do anything between steps 10 and 11?Ok, so that worked finally. Thanks! I'm now stuck at step 11 trying to get my phone stable again. I entered "adb shell /data/local/tacoroot.sh --undo" and it says "adb: not found"
Did you issue the other commands successfully? As long as the device is still connected, adb should still be running. Did you do anything between steps 10 and 11?
That is odd. Try running the command "adb remount" and see what it says. If it succeeds, you should be able to run the undo command. If it doesn't, you'll probably have to close the command prompt, re-open it, and try the undo command again.I did everything it showed and everything matched up with the command prompt displayed in the guide. For some reason it can't find adb now.
Do you have a card reader? If so, you can take the card out of the device, connect it to your PC, and move the file that way. The root of the SD card means don't put it in any folders.I'm not sure what put it on the root of my SD card. And my SD came with my phone so I don't have the big SD that craddles the micro SD in my phone. I'm not sure how to put data on my phine unless I go to the page with my handset and download straight to my sd. That pc36img I think is where I'm having isuses but I have downloaded multiple times to make sure I have the right program
That is odd. Try running the command "adb remount" and see what it says. If it succeeds, you should be able to run the undo command. If it doesn't, you'll probably have to close the command prompt, re-open it, and try the undo command again.
That looks like a problem with the su binary. Try going back into recovery and flashing it again. It may have gotten corrupted, somehow.I am currently stuck on step 8 of captain throwback guide, when I try to access the root I get this message:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Ashley Faytol>cd c:\Android
C:\Android>adb shell
$ su
su
reloc_library[1312]: 1138 cannot locate '_ZNK7android6Parcel15setDataPositionEj
'...
CANNOT LINK EXECUTABLE
$
Any body have any ideas as to what I am doing wrong?
That is odd. Try running the command "adb remount" and see what it says. If it succeeds, you should be able to run the undo command. If it doesn't, you'll probably have to close the command prompt, re-open it, and try the undo command again.
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.