Develop Bugs

Terminal Emulator

I cannot enter any SU commands in TE since I updated to 3.29. Ex. Reboot and reboot recovery - get "Not Permitted" error message. Anyone else?
Thanks!

I just rooted using the latest Unrevoked (3.21).
The process indicated success.
But attempting "su" in an effort to manipulate "perms" results in "Permission denied".
Does this mean I am not actually "rooted"?
Or do I need a something in addition to being "rooted".
I seem to remember something called "Super User application".
Is this a requirement? If so, where might I find it?
Thank you for all your time and consideration.
--Chris

You can download Superuser from the market. Skull and crossbones icon.

bender1077 said:
You can download Superuser from the market. Skull and crossbones icon.
Click to expand...
Click to collapse
Thank you for your reply bender1077.
Is this app required in order to make changes like deleting apps and stuff on a "rooted" stock ROM?
Thanks again.
--Chris

If you are using an app that requires Superuser permissions yes. Depends on how you are removing the apps. I always delete through ADB.

bender1077 said:
If you are using an app that requires Superuser permissions yes. Depends on how you are removing the apps. I always delete through ADB.
Click to expand...
Click to collapse
Thank you again bender1077.
I used Unrevoked 3.21 to root it. When it had completed, I found that SuperUser was/is
now installed, and available on my HTC-EVO-supersonic.
On the downside, when prompted by SuperUser when I launch Terminal Emulator to allow
su (root), I answer YES. But when attempting (like you) to delete apps, or what-not,
I'm told "read only file system". So the attempt fails.
Seems we're having the same issue - no?
Thanks again.
--Chris

CTH-EVO said:
Thank you again bender1077.
I used Unrevoked 3.21 to root it. When it had completed, I found that SuperUser was/is
now installed, and available on my HTC-EVO-supersonic.
On the downside, when prompted by SuperUser when I launch Terminal Emulator to allow
su (root), I answer YES. But when attempting (like you) to delete apps, or what-not,
I'm told "read only file system". So the attempt fails.
Seems we're having the same issue - no?
Thanks again.
--Chris
Click to expand...
Click to collapse
You have to remount in -rw in order to delete apps iirc.

I'm not trying to delete apps through TE, I do that through ADB.
BUUUUUTTTTTT.... Please just go into TE, and see if you are able to enter a simple command like reboot, and confirm if it works on 3.29.
I still get "not permited!" error.
It is funny that TE has permitted mispelled by the way!
THANKS!

bender1077 said:
I'm not trying to delete apps through TE, I do that through ADB.
BUUUUUTTTTTT.... Please just go into TE, and see if you are able to enter a simple command like reboot, and confirm if it works on 3.29.
I still get "not permited!" error.
It is funny that TE has permitted mispelled by the way!
THANKS!
Click to expand...
Click to collapse
Greetings bender1077,
Code:
% su
message from SuperUser:
permission granted to Terminal Emulator for su
# _
# reboot
permission denied!
# _
I hope that made sense. Superuser granted permission to me
to su. I got the hash in the upper left hand corner (#), indicating
I was root. But as you can see, I was not granted permission to "reboot".
HTH
--Chris

Oh boyzie!
OK... I will run Quick Boot for reboots, and reboot recovery for the time being!
Thanks,

Hey bender are you nand unlocked? I don't know if that would make a difference.
Sent from my GiRLiE Evo

princessakiki said:
Hey bender are you nand unlocked? I don't know if that would make a difference.
Sent from my GiRLiE Evo
Click to expand...
Click to collapse
Yes.
Worked fine on 3.26... there has to be an issue somewhere ..... /system/bin/toolbox?

Titanium Backup says "error could not acquire root", yet I "am" rooted???

Titanium Backup says "error could not acquire root", yet I "am" rooted???
Ok, so my v2.1 evo was rooted using Unrevoked 3.21, I install Titanium Backup this morning and when I launch it an error comes up that says "Sorry, I could not acquire root privileges. This application will not work. Please verify that your rom is rooted and includes busy box and try again."
Whats the deal wit this error? Unrevoked said it was succesful.

did you download busybox? when you open TB hit the problems? button. download busy box and try again.
you can also verify root by downloading terminal emulator and opening it. when its open type SU and hit enter. # means root. $ means no root.

Be weary. I used unrevoked3 for mac on a froyo Evo. I'm having some issues currently. Be careful before you proceed. You should download ROM manager as well. Once you download busybox perform your backup. A friend recommended Appbrain over Titanium Backup. Once your done with your back up, reboot into the bootloader and try to go into recovery to perform a nandroid backup. If you select recovery and it takes you to the htcevo 4g white screen and nothing happens, you're having the same issue as i am. I wouldn't recommend flashing any radios or roms yet. I'm working with some other members to try to figure this issue out. Apparently this is why other experts don't like unrevoked3.
There might be a missing pc36img or unrevoked forever might need to be install, but I don't want to lock my phone into root with unrevoked. From my understanding, if you use unrevoked forever, you wont be able to unroot.

jontorres said:
Ok, so my v2.1 evo was rooted using Unrevoked 3.21, I install Titanium Backup this morning and when I launch it an error comes up that says "Sorry, I could not acquire root privileges. This application will not work. Please verify that your rom is rooted and includes busy box and try again."
Whats the deal wit this error? Unrevoked said it was succesful.
Click to expand...
Click to collapse
[highlight]Mod Edit: If you have nothing useful to say, say nothing at all. The question in the correct section this time.[/highlight]

jontorres said:
Ok, so my v2.1 evo was rooted using Unrevoked 3.21, I install Titanium Backup this morning and when I launch it an error comes up that says "Sorry, I could not acquire root privileges. This application will not work. Please verify that your rom is rooted and includes busy box and try again."
Whats the deal wit this error? Unrevoked said it was succesful.
Click to expand...
Click to collapse
What about any other app requesting root? Like setCPU or ShootMe? I'd install one of those to confirm root. If it works then you might you need to reinstall TB if not well then root was not properly achieved.

TruSlide said:
did you download busybox? when you open TB hit the problems? button. download busy box and try again.
you can also verify root by downloading terminal emulator and opening it. when its open type SU and hit enter. # means root. $ means no root.
Click to expand...
Click to collapse
Thanks for the suggestions, will try those out and report back what happened.

Sporkman said:
take the time to read the info it tales you have to fix said issue
Click to expand...
Click to collapse
MOD PM'd, apparently you are following my threads now to post the same "ignorant" response, your sanction from the mod will follow, enjoy.
Everyone else, thanks for actually offering helpful suggestions.

TruSlide said:
did you download busybox? when you open TB hit the problems? button. download busy box and try again.
you can also verify root by downloading terminal emulator and opening it. when its open type SU and hit enter. # means root. $ means no root.
Click to expand...
Click to collapse
Ok, so I did update BusyBox, and now Titanium Backup doesnt show the error, also installed Terminal Emulator when you launch it the 1st line of text says"
$ export PATH=/data/local/bin:$PATH
$
On the 2nd line where the $ i typed SU and hit enter and it goes to the next line and displays # is this what its suppose to do?
Thanks

Ok, here is some things for you to try.
1. Make sure you are using the latest version of TB.
2. Make sure you hit Problems? and download Busybox 1.60 (whether or not the ROM you have is using 1.60 or not, do it anyhow.)
I assume you did those two based on what I read. So here is what else to try.
Upgrade Superuser to the latest version, then update the binary. Make sure Titanium backup is not blocked by going to Superuser and there should be a green circle next to TB, if it is red that means it is blocked. If it still doesn't work, remove it from Superuser and then have it ask for permissions again.
If STILL not working, take out your battery for around 10 seconds, plug it back in and try again. Lastly, uninstall and reinstall TB then do these steps all over again.
That is a bunch of stuff to try, see what happens and hope this helps

jontorres said:
Ok, so I did update BusyBox, and now Titanium Backup doesnt show the error, also installed Terminal Emulator when you launch it the 1st line of text says"
$ export PATH=/data/local/bin:$PATH
$
On the 2nd line where the $ i typed SU and hit enter and it goes to the next line and displays # is this what its suppose to do?
Thanks
Click to expand...
Click to collapse
That's exactly what it's supposed to do. $ is the prompt you get when you are a regular user. You get # when you are root.
If you type 'id' (without the quotes) now, you should get:
uid=0(root) gid=0(root)

ricsim78 said:
Upgrade Superuser to the latest version, then update the binary. Make sure
Click to expand...
Click to collapse
I launched Superuser, the one with the little niña guy, and it showed TB and the emulator both with green on the right side, but no idea how to "update" superuser, seeing as all appears to be ok should I still update it? If so, hoe would I do that? If not then I guess now my next step s finding the best 2.2 ROM that still keeps HTC Sense, any recommendations?

timdsmith72 said:
That's exactly what it's supposed to do. $ is the prompt you get when you are a regular user. You get # when you are root.
If you type 'id' (without the quotes) now, you should get:
uid=0(root) gid=0(root)
Click to expand...
Click to collapse
the prompt b4 I typed anything was $, after typing SU and enter it went to #

jontorres said:
the prompt b4 I typed anything was $, after typing SU and enter it went to #
Click to expand...
Click to collapse
Yep. That's what is supposed to happen. You are root when you have the # prompt.

Problem
I just flashed CM 7.1 stable version, i cant launched TB couldt aquire root privileges i read this post and typed SU in the terminal emulator and it came up with a $ sign. So that means im not rooted?
Any cure to get my phone rooted again but i want to keep CM 7.1 what should i do?

aks1081 said:
I just flashed CM 7.1 stable version, i cant launched TB couldt aquire root privileges i read this post and typed SU in the terminal emulator and it came up with a $ sign. So that means im not rooted?
Any cure to get my phone rooted again but i want to keep CM 7.1 what should i do?
Click to expand...
Click to collapse
Flash the super user zip from http://androidsu.com/superuser/
Should fix you up, not sure how you lost it, but this souls fix it nevertheless.

[GUIDE] Temp to permanent root, using rage instead of visionary

There's already a guide here for obtaining permanent root using VISIONary, but some folks in #G2ROOT are having issues with the way that VISIONary modifies parititons. Using rage directly is a bit cleaner, since you know exactly what it's going to touch at each step of the way. I did NOT come up with any of this on my own, I'm building completely off of work that others have done. Speaking of which-
None of this would be possible without the tireless work that scotty2 put in. He stayed with the project for well over a month, through lots of smashed hopes and dead ends, until the solution was finally found. Were it not for his work, as well as the help of a few other key folks- we wouldn't be here. He deserves our thanks and some donations! We're talking hundreds of hours of work here, a couple bucks is not too much for that. His paypal is:
[email protected]​Send him some love! I'm not asking for anything myself, because I spent a half hour putting this together, and that doesn't deserve any donations!
[size=+2]G2 ROOT INSTRUCTIONS[/size]
=================================================
These are modified instructions based on the ones posted at http://bit.ly/g2root that use Visionary. A number of people have run into issues with the way that Visionary juggles around temporary partitions, and using the original root exploit is a much easier, and cleaner method for achieving permanent root. This tutorial will walk you through the rooting process by first achieving temporary root, and moving on to permanent root.
[size=+1]REQUIREMENTS[/size]
=================================================
Visionary disabled at boot or uninstalled completely
Android Terminal Emulator app
ADB
vision-combined-root.zip (Attached to this post, OR these two files: )
G2TempRoot.zip (http://forum.xda-developers.com/showthread.php?t=797042) NOTE: only download the files! Don't follow these instructions yet
vision-perm-root.zip (http://forum.xda-developers.com/showthread.php?t=833965) NOTE: again, just download the files from the thread.
In the commands to run below, $ or # represent the prompt and should NOT be entered as part of the commands.
[size=+2]VERY IMPORTANT![/size]​Visionary has caused filesystem corruption for some users during the rooting process. Before attempting the instructions below, make sure that you have "auto run on boot" turned OFF, and reboot your system. Since you will not need visionary anyway after this, you might as well just uninstall visionary and reboot NOW before doing anything.
[size=+1]TEMP ROOT[/size]
=================================================
ON YOUR PC:
Unzip the G2TempRoot files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
Code:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
ON YOUR PHONE:
Launch Terminal Emulator
/data/local/tmp/rage
Wait for the message: "Forked #### childs."
Menu > Reset Term - Terminal Emulator will exit.
Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
**NOTE**: in the original directions from the XDA thread, you are instructed to run the /data/local/tmp/root script here. DON'T do this
just yet. Leave the terminal window open.
[size=+1]PERM ROOT[/size]
=================================================
ON YOUR PC:
unzip the vision-perm-root.zip and navigate to that folder. There will be four files. You will need to push two of these to your phone- hboot-eng.img, and one of the wpthis-[..].ko files.
If you HAVE applied the OTA update, push wpthis-OTA.ko.
If you HAVE NOT applied the OTA update, push wpthis-pre-OTA.ko.
Code:
$ adb push hboot-eng.img /data/local
$ adb push wpthis-OTA.ko /data/local
ON YOUR PHONE:
You should still have terminal emulator up, at a root prompt. Now run:
Code:
# insmod /data/local/wpthis-OTA.ko
You should see:
Code:
init_module 'wpthis-OTA.ko' failed (Function not implemented)
That means it worked. This next step is CRUCIAL. You must make sure that you are writing to the proper partition here or you could brick your phone. To be absolutely clear- the partition is mmcblk(zero)p(one)(eight)
Code:
dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
You should see some messages indicating that it was written. Next, run:
Code:
# /data/local/tmp/root
This will lock in root, and give you 'su' access in the future. Next, run:
Code:
# sync
Now wait at least a minute, just to be safe. After waiting, reboot your phone using the power button. After it finishes starting up, launch the terminal emulator, and type 'su'. You should get the prompt asking you to grant permissions. If you got the prompt, congratulations! You have permanent root!

I used these instructions and they worked brilliantly.
Sounds like it's a little safer than using VISIONary, which some people in the thread are reporting can get confused and not let you root because it thinks you already have root, etc.

I love it when a plan comes together. Perma-root. thanks man, i never had much luck getting visonary to work so this was spot on. worked like a charm

*not smart enough*
*leaves thread*
I really try to leave ADB out of the equation since I'm not comfortable navigating it.... I suppose I could dedicate my time to learning it, but it's not worth it since I would only use it once every two years to root my phone. In 16 hours I'm sure there will probably be a one click perm root method out anyway.

It worked flawlessly!
I always get so stressed when I root my phones, especially without tutorial vids.
I first did my G1 and that worked perfectly fine.
My second attempt at rooting was with my MT3G and that resulted in a bricked device because one of the lines of code was incorrect in the thread.
This, however, was clearly and plainly spelled out exactly to what happened to my phone.
I give you my thanks.

Awesome- glad to hear it's working well for people. If anybody sees areas that I could improve in the description just let me know.
sinistersai4d4d said:
I really try to leave ADB out of the equation since I'm not comfortable navigating it....
Click to expand...
Click to collapse
ADB is worth it IMHO because it makes moving files around easy, whether you're rooted or not. You don't have to turn on SD card storage, you can just do adb pull/push etc to grab or put files when you need them. Worth the effort. The one click root should be out within the next couple days though, you are right about that one.

trigeek,
I already perm rooted earlier, but just wanted to say you gave a very nicely detailed explanation that anyone should be able to follow. Well done!

Great guide. I liked it a lot more than Unforgivens just because it doesn't rely on VisionARY which might mess things up.

Guide worked absolutely great, no problems. I did not try the visionary method first, but for some reason I just felt safer doing it in adb.
Thank you!

Sorry for the noob question...? but does this mean we have fully rooted to G2 and now we can load ROMS on it when they come out ????
Edit: Nevermind I didnt see the sticky

RaffieKol said:
Sorry for the noob question...? but does this mean we have fully rooted to G2 and now we can load ROMS on it when they come out ????
Click to expand...
Click to collapse
You got it!

RaffieKol said:
Sorry for the noob question...? but does this mean we have fully rooted to G2 and now we can load ROMS on it when they come out ????
Edit: Nevermind I didnt see the sticky
Click to expand...
Click to collapse
Custome ROMs, custom Recovery...the whole 9 yards

Thanks for posting this, it was so easy!

Thank you so very much it was a success

this is my first rooting on an android device... im freaking out... but here i go.... if something happens i will just report my phone lost and get a new one i guess ahahah still... im scared.

Issues
I was temp rooted before using rage and then thru Visionary. But I decided to go back to stock till we have permanent root. I perm rooted today using this method. But I'm having the following issues:
1) adb remount
- remount failed: Operation not permitted
2) when using Root Explorer in /system, toggling Mount R/W does not work
- the only way to mount it R/O is thru terminal/adb shell. Once mounted R/O, the only way to mount R/W again is thru a reboot. Issuing mount -o remount ro /system either in terminal or adb shell does not work.

i actually changed my mind... im going to wait for a one click untended root i guess.... to scary...

joackie27 said:
I was temp rooted before using rage and then thru Visionary. But I decided to go back to stock till we have permanent root. I perm rooted today using this method. But I'm having the following issues:
1) adb remount
- remount failed: Operation not permitted
2) when using Root Explorer in /system, toggling Mount R/W does not work
- the only way to mount it R/O is thru terminal/adb shell. Once mounted R/O, the only way to mount R/W again is thru a reboot. Issuing mount -o remount ro /system either in terminal or adb shell does not work.
Click to expand...
Click to collapse
make sure you have debugging enabled.

juanshop said:
i actually changed my mind... im going to wait for a one click untended root i guess.... to scary...
Click to expand...
Click to collapse
Not gonna happen.

then i guess.... im going to jump in it.... wish me luck...

[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?

[Q] busybox installed, but where?

Hi there,
i'm actually trying to do the wimax backup found here:
http://forum.xda-developers.com/showthread.php?t=887900
I went through all of this trouble trying to install busybox until I found out that Titanium backup already installed 1.16 on my phone. However I can't seem to find where it was installed to and the,
busybox sed -n '/BEGIN CERTIFICATE/,$p' /dev/mtd/mtd0 > /sdcard/rsa_OEM.key
command isn't working. Any thoughts? Sorry if this is the wrong spot to post. I'm still getting the hang of this forum.

I have the same problem. I think I'm getting this error in the terminal emulator because I don't have the system Busybox installed, just Titanium's app busybox, which is apparently different?. When I try to run Busybox installer, it errors saying I'm possibly not nand unlocked... I used UR3 and UR forever, and can confirm that I am S-Off. Doesn't S-Off = nand-unlock?

I haven't played too much with busybox to know much of its capabilities, but if you want to know the directory it is located in, run this from Terminal Emulator, or adb.
find -iname "*busybox*"
that will get you any and all file listings with busybox in it.

says denied, so I typed su, and get the #
then I type the find command, and tells me that 'find' is not found.
topdawgn8 said:
I haven't played too much with busybox to know much of its capabilities, but if you want to know the directory it is located in, run this from Terminal Emulator, or adb.
find -iname "*busybox*"
that will get you any and all file listings with busybox in it.
Click to expand...
Click to collapse

greyopaque said:
says denied, so I typed su, and get the #
then I type the find command, and tells me that 'find' is not found.
Click to expand...
Click to collapse
you should be able to run find without a hitch. I have had issues running a find while executing a remove, but find had always worked...
try remounting the system:
Code:
su
remount rw
find -iname "*busybox*"
Edit: I just ran find with only SU. What rom and kernel are you running? The only two things I can think of are:
1: The dev removed it from the rom
2: User error-- ensure the commands are lower case, there is a space where appropriate (denoted by ">")
Code:
find>-iname>"*busybox*"

The busy box that tb installs doesn't have all the commands. I had to install from the market to get all the commands.
Sent from my PC36100 using XDA App

its in system/bin most of the time but can be in different spots

Usually you can find busybox in /system/xbin

OMG... I feel stupid... I had install location set for SDCard. That's why busybox installer was failing. I changed it back to auto, and installed busybox, and now everything is working!

Don't waste your time with the rsa keys backup. You'll never be able to restore them.
Use the recovery (amon's 2.2.x) to make a backup of the entire wimax partition. Should the need arise, recovery will be easy. To date, i've yet to see instructions how to restore just the keys.

That's exactly what I did. Thanx!
gpz1100 said:
Don't waste your time with the rsa keys backup. You'll never be able to restore them.
Use the recovery (amon's 2.2.x) to make a backup of the entire wimax partition. Should the need arise, recovery will be easy. To date, i've yet to see instructions how to restore just the keys.
Click to expand...
Click to collapse