Develop Bugs

where do i put a file i want fastboot to see

I have no idea where to put the new ra-evo recovery file so that fastboot sees it. I have looked sorry for the stupid question

your fast boot should be installed in ur android sdk tools folders so if thats where ur fast boot is then put the file in the tools folder

Fastboot flashes files from your computer not on the sdcard or anything.
Ex. Fastboot flash recovery /User/downloads/recovery.img
Sent from my PC36100 using XDA App

i am so confused
so if I am rooted and unlocked and I already have the original amon recovery i just put the new amon recovery in the tools folder. then how do I get it on my phone

if you already rooted you should have android sdk installed
easyest way
go to start
my computer
c drive or your main drive
android sdk or sdk (wat ever you named it)
tools folder
put recovery in tools forder
open a command prompt and
cd \android-sdk
cd tools
now your in the tools folder
fastboot flash recovery /recovery.img
it is easyer and faster no searching for the files if you put the recovery in the tools folder its already there no going to filesfoldersdownloads you dont need them commands its faster and easy look through the adb and sdk guides it has all commands and most recover forums tell you all this

so i need to change the name of the amon recovery image to recovery.img

No he was just using recovery.img as a example.
Sent from my PC36100 using XDA App

Here's how i did it this morning, downloaded file to pc, connect phone as disk drive, opened disk drive, placed the amon file into the sdcard, changed phone back to charge only, went to astro to verify that the amon file was on the home list of files, then wen to market and downloaded terminal emulator free, and just follow Amon's instructions to apply using terminal or adb, it was reall easy that way, i kept trying to load the fastboot way and just couldn't figure it out, so i tried this was and perfect, new recovery, and hopefully i can wipe dalvik now.

You don't need fastboot to flash a new recovery image. Like tomh said in the post above this one, put the new recovery on the root of your sdcard, open a terminal emulator on your phone and type the following:
flash_image recovery /sdcard/name_of_recovery.img
I haven't used my computer to update a recovery image since I first got my Hero.

with a terminal app you'll want to use this exact cmd's
su(press enter)
flash_image recovery /sdcard/recovery-RA-evo-v1.8.0.img(press enter)
reboot recovery(press enter)
that's just as amon_ra has it, same as what i used as well.

thanks for the help

shawnten said:
thanks for the help
Click to expand...
Click to collapse
Somewhere on your PC. You just have to give the path to the fastboot command.
Sent from my HummerPhone using the XDA App

i just downloaded the terminal emulator onto my evo but when i type the first cmd "su" it says permission denied. please tell me how do i get passed that.

ro2themax said:
i just downloaded the terminal emulator onto my evo but when i type the first cmd "su" it says permission denied. please tell me how do i get passed that.
Click to expand...
Click to collapse
Root your phone..

i jsut use rom manager. I am to lazy to do everything else currently rom manager has the latest amon ra you can tell it to flash as an "alternative" recovery. takes 2 seconds and no typing out "long" commands in terminal.

i was under the impression i was rooted...i did the OTA update to 2.2 then used the method to root that came out a week ago using unrevoked3 and unrevoked forever. but instead of going back to a rooted 2.2 i stayed on a rooted 2.1.

ro2themax said:
i was under the impression i was rooted...i did the OTA update to 2.2 then used the method to root that came out a week ago using unrevoked3 and unrevoked forever. but instead of going back to a rooted 2.2 i stayed on a rooted 2.1.
Click to expand...
Click to collapse
Huh, that's weird. What rom are you using?
If you're using a rooted rom then you should be getting a # when you type "su" into the terminal..
Do you have the SU app installed? Did you get an SU Permission request when you opened the terminal for the first time? If so, did you grant the terminal emulator SU permission?

im using a stock 2.1 rom and i do have superuser permissions installed. i also have setcpu for root users installed and "su" grants "setcpu" permission.
i also forgot to mention that i also put a "netarchy kernal" on their also which appears to me, works as it said. right now if i want to go into recovery it goes through clockwork, but i want to get amon ra's recovery on there instead.

ro2themax said:
im using a stock 2.1 rom and i do have superuser permissions installed. i also have setcpu for root users installed and "su" grants "setcpu" permission.
Click to expand...
Click to collapse
hmm.. which 2.1 stock? Was it a rooted stock (with busybox and su already in there) or did you install the su app?
Although sounds like it already had busybox if setcpu is getting permission.
If you are near your computer see if you can get a # using the adb shell. I'm a little stumped here..

the 2.1 stock came with the "su" already. i just posted a quick update on the my previous post that i flashed a netarchy kernal on my evo also. i dont know if that helps but i just forgot to mention it...
please bare with me, im by my computer and to go into adb shell do i need to plug my evo in as charge only and open a cmd from android tools to see if i get # ???

[Q] ADB Shell Won't Allow me to run as SU

So I'm trying to get into su to run gfree_verify to make sure my permaroot S-off/SIM card unlock/SuperCID was successful, but I'm getting a permission denied error.
What happens is, I type adb shell, then I type su, there's a really long delay, then it tells me Permission Denied. However, when I run the Terminal Emulator from my phone and type in the su command, I get root access just fine.
I used the "official" method that is on the HTC Vision Wiki that is located here. The only thing, however, is that my Android SDK install wasn't installed using any type of installer. I just extracted a zip file and shoved it in a random folder. I did make sure to run the Command Prompt as Administrator before issuing the adb shell command, but I'm still unable to get superuser access through the PC. Trying to use the adb root command gives me an "adbd cannot run as root in production builds" error.
Did I do something incorrectly?

adb kill-server
adb start-server
See if that works. If not, try rebooting your computer.
Sent from a Western Union telegram.

Does the Superuser app seem to be installed correctly on your phone ?
Do you have the output from gfree ? I wonder if it didn't work correctly with your kernel, it doesn't work with all kernels. What ROM/kernel do you have ?
Which procedure did you use, the one in the Wiki, or one involving dd'ing the eng hboot ?

steviewevie said:
Does the Superuser app seem to be installed correctly on your phone ?
Do you have the output from gfree ? I wonder if it didn't work correctly with your kernel, it doesn't work with all kernels. What ROM/kernel do you have ?
Which procedure did you use, the one in the Wiki, or one involving dd'ing the eng hboot ?
Click to expand...
Click to collapse
I rebooted the daemeon, computer, and also the phone. No dice.
The Superuser app is correctly installed. When I ran Adfree and attempted to go into SU in Terminal, I got the usual Allow Superuser access dialog. Both worked without any problems; like I said, I can get root access from the on-the-phone terminal, it's when I attempted to get root access from the adb shell command on my computer where I have problems.
No special ROMs, completely stock post-November OTA update. The only thing I flashed after permarooting was the Clockwork Recovery mod, but adb shell SU wasn't working before this. I initially used some outdated instructions (involving the use of the dd command, and the wpathis.ko or something). I read some more and learned these were out of dated, so I unrooted. I then used the instructions that are on the wiki using gfree to permroot.
gfree_verify works without any problems if I run it from the Terminal Emulator on my phone. Returns the proper values to indicate I'm SIM Unlocked, SuperCID, and S-off. I'm glad it works, but I still don't like the fact I can't use the adb shell. Typing characters on the G2 is a pain in the ass.
I still want to know why I can't enter superuser from the PC adb shell. Am I doing something incorrectly?
Thanks a lot for your help!

Try clearing data for the SuperUser app?

go in your recovery screen from boot, select your mount options, and mount everything lol. Not sure if it'll fix it but everytime I have adb permission issues that seems to fix it and I don't think it could hurt.

dietotherhythm said:
go in your recovery screen from boot, select your mount options, and mount everything lol. Not sure if it'll fix it but everytime I have adb permission issues that seems to fix it and I don't think it could hurt.
Click to expand...
Click to collapse
This worked perfectly! When I entered su from the command prompt, the SuperUser app popped up on the phone's side and I hit allow. It then let me through.
What exactly was broken though? Why did mounting everything from the Clockwork Recovery menu fix this?

Gfree_Verify Not Working, Not Sure if Root Worked

I followed all the steps from the Wiki: (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD).
Now the problem is when I go to verify the root. On the Wiki, where it says run "su' in computer ADB shell, I get access denied. When I run "./gfree_verify" in computer ADB shell, I get
Error: Could not open modem device; /dev/****
Error: Verify could not initialize device
But in my apps on the G2 I see an icon for superuser permissions. So did the root take or not?
Thanks for any help, new to Android.

Go in to terminal on your phone and type SU
After pressing enter if it says permissions denied, you have no root, if a Su message pops up click allow... that means you have root
Edit: I think you have no root

MacaronyMax said:
Go in to terminal on your phone and type SU
After pressing enter if it says permissions denied, you have no root, if a Su message pops up click allow... that means you have root
Edit: I think you have no root
Click to expand...
Click to collapse
After typing Su in the terminal on the phone, I get a message pop that says either allow or deny. I click allow and it gives me root permission.

Then it`s OK!
After reboot/or try again,open terminal emulator on your phone and type "su".
If you get a superuser prompt, you have root!
After "su" you should see a line with "#".

Ganii said:
Then it`s OK!
After reboot/or try again,open terminal emulator on your phone and type "su".
If you get a superuser prompt, you have root!
After "su" you should see a line with "#".
Click to expand...
Click to collapse
After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again, to root the phone (just cause I wasn't sure if I was rooted). Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Another question, is it okay to delete the files I had to push to /data/local to root? How would I delete them?
I want to really thank you guys for all the help.

boost3d23 said:
After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again, to root the phone (just cause I wasn't sure if I was rooted). Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Another question, is it okay to delete the files I had to push to /data/local to root? How would I delete them?
I want to really thank you guys for all the help.
Click to expand...
Click to collapse
# sign means your rooted or have su access.
Go under manage and restore backups in rom manager, you should have a copy of the rom you just backed up. Unless you renamed the back up its probably a date.
Its ok to delete the files you pushed to data/local use a file manager like root explorer.
Sent from my HTC Vision using XDA App

After a reboot (two actually) after I enter su into terminal I dont get the popup anymore asking allow or deny. I get "#." I actually went through the whole rooting Wiki steps again. Same results, the gfree-verfiy doesnt work and neither does the "older" method. But I get "#" after entering su in terminal on G2.
Click to expand...
Click to collapse
You get "#" then it`s right,the app don`t ask you again about allow or deny!
About gfree-verify,I don`t know.Maybe something wrong with Script
or you have done something wrong with the commands!
I also installed Rom Manager, I clicked Flash ClockworkMod Recovery and then chose Backup Current ROM. It asked for superuser permissions and I allowed it. It rebooted the phone and went to a ClockworkMod Recovery screen where I selected reboot device. Does this mean I backed up my current Tmobile ROM?
Click to expand...
Click to collapse
If you choose "Backup ROM" you phone boot into Recovery,then you have
to choose "backup/restore option to backup you current ROM.
Otherwise you don`t have a backup

Again thanks guys.
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.

boost3d23 said:
Again thanks guys.
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.
Click to expand...
Click to collapse
I use Root Explorer or SUFBS (Super User File Manager and Terminal).

boost3d23 said:
Now i downloaded Astro and ES file Managers but I cant find the files. Do I need specifically need root manager? Im guessing the ones I downloaded cant access root files.
Click to expand...
Click to collapse
You should really have posted up in the existing thread about gfree on this, or otherwise in the Q&A forum
But anyway, yes, those file managers don't handle root. Well, ES does have an option to do so, but it doesn't work on the Vision. So you'll need a root-capable file manager, as joemm said.
On the backup, that sounds a bit odd, but you'll know that it's doing a backup because it'll take a while. You'll get a different screen where it shows you it's backup up the main phone partitions, and even which file is being backed up. When it's done, make sure you copy this backup somewhere else, like your PC (i.e. so you don't just have a single copy, in case something happens to it - e.g. corrupt SD card).

Thanks to everyone who provided insight. I had the same problem and was worried about bricking my phone, but this worked and I'm happily rooted!

[Q] factory reset after permroot....still rooted or not !!!

after permroot i did factory reset and then the visionary app and superuser app went away. now even after reinstalling both of them my proxy app doesnt work , it gives an error saying failed to start redirect.sh (permission denied) . now is my DHD still rooted or not , if it is still rooted then how can i make the proxy app work ?
thanks

try to root using visionary again, if you are rooted at the moment simply nothing will happen if you use it

Edit; You shouldn't have lost root by factory reset alone, but stranger things have happened. Not sure about the proxy app.
DL Superuser again (or as suggested/implied), reintall the Visionary will install Superuser as well.
Certain apps need required SU permissions from Superuser. When prompted by Superuser, grant SU rights to that app you are running.
Alternatively;
1. DL & install Superuser & Terminal Emulator from the Market
2. Run Terminal emulator
3. Type "su"
4. When prompted give superuser rights
5. Terminal Emulator prompt will change to "#" if you still have root
Edit: If you still have root & Superuser permission for the proxy app, try reboot in CWM Recovery & "fix permissions". You can do from within ROM Manager, but I prefer to do in CWM Recovery when the phone hasn't booted the partitions.
Make a backup in CWM Recovery prior to doing anything.

Just sharing.. once I accidentally denied the permission to root access for one app and the setting was to remember it. It took me a while before I realized this and change it in superuser setting.

i tried the terminal emulator and after typing su it said permission denied , and yeah my titanium backup isnt working coz it says dat it needs root now.

Yep, you lost root.
Try visionary again, and make sure superuser rights are given when asked by superuser.
Sent from my Desire HD using XDA App

[Q] superuser permission

I have rooted my evo. I have S-off. I flashed cm7 and everything is working great. The only problem is when I open terminal emulator app. I type in su, and it tells me "superuser permission denied" There is a $ sign on every line also. From what I understand, I should be seeing a # sign. I have also installed BusyBox. Is there anyway to get superuser permission on terminal emulator?

ebnug said:
I have rooted my evo. I have S-off. I flashed cm7 and everything is working great. The only problem is when I open terminal emulator app. I type in su, and it tells me "superuser permission denied" There is a $ sign on every line also. From what I understand, I should be seeing a # sign. I have also installed BusyBox. Is there anyway to get superuser permission on terminal emulator?
Click to expand...
Click to collapse
From what i understand, you will have a $ sign until SU permission is granted, then it turns to a #.. Have you tried opening Superuser and seeing if terminal has a green light/dot next to it?

Terminal emulator is not on my allowed list in superuser. I was never prompted to allow permission to terminal. I even uninstalled terminal and downloaded it again from the market and after i opened it, I was not prompted to allow permission from superuser. Is there anyway to add terminal on the allowed list in superuser, because I cant see anyway to add it. Or would there be another reason permission on terminal is denied?

ebnug said:
Terminal emulator is not on my allowed list in superuser. I was never prompted to allow permission to terminal. I even uninstalled terminal and downloaded it again from the market and after i opened it, I was not prompted to allow permission from superuser. Is there anyway to add terminal on the allowed list in superuser, because I cant see anyway to add it. Or would there be another reason permission on terminal is denied?
Click to expand...
Click to collapse
Have you tried looking on superuser's log to see if it is even trying to request permission? If not, can you try another terminal program?
Sent from my PC36100 using xda premium

So I downloaded Better emulator pro. And under preferences, I selected "start as root" and was prompted to allow superuser permissions. When I open better emulator I see the # symbol, but when I type in su, it responds: not found. Any suggestions?