Develop Bugs

voicemail upgrade notification on latest fresh rom- annoying!!

wiped cache,data,reinstalled the rom, voicemail setting is set to my carrier with my phone number,.. still gives me installation failed everytime! I don't care about the stupid update I just want it gone! I Can't get rid of the annoying icon in notification bar!

same here i just want it gone.
sweet rom though

you guys talking about 3.1 or 3.2? if its 3.1 look at the tutorial on fresh's website about using the fresh updater, how to set up the theme server's etc, and use the fresh updater app to update the vvm. Thats what I did for mine, and it worked fine.
If youre using 3.2, which i believe is still only available to donaters of his, then I would assume youd be able to figure it out, although his current 3.2 release isnt resigned so you would be able to use sprints updater i believe.
Best of luck.

mikek9 said:
you guys talking about 3.1 or 3.2? if its 3.1 look at the tutorial on fresh's website about using the fresh updater, how to set up the theme server's etc, and use the fresh updater app to update the vvm. Thats what I did for mine, and it worked fine.
If youre using 3.2, which i believe is still only available to donaters of his, then I would assume youd be able to figure it out, although his current 3.2 release isnt resigned so you would be able to use sprints updater i believe.
Best of luck.
Click to expand...
Click to collapse
thxs i'm using 3.1, just based on what you said I manage to update the vvm via fresh updater, no tutorial necessary, took me literally 2mins, thxs again

no problem, glad i could help

i dont want it gone. i am happy to take whatever update is available.
i am using evio 1.1 and i will check his thread but any idead how to install the update?
did it on the wifes unrooted evo and of course it went thru fine.
Sent from my PC36100 using XDA App

Go to the Application Box. (The button above the Home Button)
Look for Fresh Updates app.
Open that up Tap Menu > Click on Config > Hit Theme and Settings > Manage Theme Servers > Tap Menu then update featured Servers hit yes to update.
Then you will see can go back to tweaks and choose the Voice Mail update and download/install it.

I answered this in another post, but here it is again...this method is manual as opposed to using fresh updater as stated above.
1. Download the attached, updated .apk
2. Place the apk in your android-sdk-windows/tools folder (or whatever you named it)
3. Reboot to Recovery
4. open a command prompt and do (hit enter after each line)
Code:
adb shell
mount /dev/block/mtdblock4 /system
cd /system/app
rm -f Sprint_VVM.apk
exit
then, from outside of the shell do (hit enter after each line)
5.
Code:
adb push Sprint_VVM.apk /system/app
adb reboot
You shouldn't have the update problem anymore if you complete all steps successfully
Sent from my PC36100 using XDA App

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.

[Q] su permission denied

Hello there,
I just flashed a new ROM (Gingerbread 2.3.7) last night. After signing in the Google account everything is great; the old apps got redownloaded and all. I noticed that there is no apps listed in the superuser. I tried 'su' command in the emulator terminal & I got permission denied.
Luckily all the apps are working in perfect harmony. However, how do I get the superuser permission back? It seems like my device is not rooted. Do I need to root my phone again? Fingers crossed I don't.
Initially, I tried to flash the Ice Cream Sandwich. I tried multiple times but to no avail. I even tried to change the HBOOT (from CM7 > downgrader > Stock HBOOT) but the process failed. I afraid that this might be the cause my root access got lost. Anyone can verify this?
Thanks!

Su app will be built into the ROM so you should still rooted. Sounds like Su settings are just defaulting to deny. Open Su, menu > settings and check its set at prompt (safer than allow). After flashing new Rom you'll need to launch apps that require root access to allow them permission again. You might need to update the Su app or binaries if permissions don't stick.
Sent from my HTC Desire using Tapatalk 2

beachcomber said:
Su app will be built into the ROM so you should still rooted. Sounds like Su settings are just defaulting to deny. Open Su, menu > settings and check its set at prompt (safer than allow). After flashing new Rom you'll need to launch apps that require root access to allow them permission again. You might need to update the Su app or binaries if permissions don't stick.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
beachcomber,
1. my Superuser is set at prompt.
2. I am not sure which app that require root access. Could you give me some examples so that I can run them?
3. I tried to update the su binaries, but I got this:
" checking current install path...FAIL!"
" failed to find currently installed su binary. Update cannot continue."
Therefore, what do you suggest?
Thanks.

xuminarc said:
beachcomber,
1. my Superuser is set at prompt.
2. I am not sure which app that require root access. Could you give me some examples so that I can run them?
3. I tried to update the su binaries, but I got this:
" checking current install path...FAIL!"
" failed to find currently installed su binary. Update cannot continue."
Therefore, what do you suggest?
Thanks.
Click to expand...
Click to collapse
Take a backup. Download this. Flash it through recovery. Reboot and check if it works.

Alaa said:
Take a backup. Download this. Flash it through recovery. Reboot and check if it works.
Click to expand...
Click to collapse
Thank you! It works!

Superuser just won' work!

I rooted my kindle fire using kindle fire utility 0.9.6 (after the rooting superuser wasn't installed on my kindle), downloaded twrp, flashed hashcode jelly bean ROM from this link
http://forum.xda-developers.com/showthread.php?t=1766829
and then flashed Superuser-3.1.3-x86-signed.zip which I downloaded from this link
http://androidsu.com/superuser/
but superuser won't work, when I check the root explorer in ES file explorer it tells me that this feature can't work on ur phone
Please I'm really dying out here
Someone Help Pleeeeeeeeeeeeeeeeeease !!!!!

You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
[Edit:] It's late and I'm not paying attention for some reason. Custom ROMs come pre-rooted and you have Jelly Bean installed. Perhaps there's a problem with ES File Explorer?

soupmagnet said:
You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
Click to expand...
Click to collapse
Thank you for replying so fast
how can I install su binary? and about the superuser.apk isn't that what i flashed into my device i have a superuser icon on my desktop but it just won't add any apps to its list.
Thanks again

At the Superuser website, there are three zip files. One is Superuser, one is the su binary, and the other should be both. Not that it matters at this point.

soupmagnet said:
At the Superuser website, there are three zip files. One is Superuser, one is the su binary, and the other should be both. Not that it matters at this point.
Click to expand...
Click to collapse
what do you mean by not that it matters at this point?
can't I just download the zip and flash it?

soupmagnet said:
You need the su binary installed as well. But with that being said, why don't you just install the Superuser.apk?
[Edit:] It's late and I'm not paying attention for some reason. Custom ROMs come pre-rooted and you have Jelly Bean installed. Perhaps there's a problem with ES File Explorer?
Click to expand...
Click to collapse
Maybe you missed this

soupmagnet said:
Maybe you missed this
Click to expand...
Click to collapse
I tried another app called copy paste it and when I try to use it this message appears:
"Your Phone does not appear to be rooted or has not been given root privileges. to use this application please provide root privileges to this applications"
what should I do?
[Edit] ok now i know my device is certainly not rooted i tried orbot, market enabler and market unlocker they all dispatch the same message your device isn't rooted.
can anyone tell me how to root it?

Scarfacew said:
I tried another app called copy paste it and when I try to use it this message appears:
"Your Phone does not appear to be rooted or has not been given root privileges. to use this application please provide root privileges to this applications"
what should I do?
[Edit] ok now i know my device is certainly not rooted i tried orbot, market enabler and market unlocker they all dispatch the same message your device isn't rooted.
can anyone tell me how to root it?
Click to expand...
Click to collapse
I too used the KFU to supposedly root my KF, but when I tried to install Titanium Backup, it gave me the same error message saying that my phone did not have root privileges... I wonder if there is something not installing correctly when using KFU...

"Root" consists of the su binary, which the system uses to give the user root permissions, and Superuser.apk, which keeps a database of what programs you allow to have those permissions. With "su" only, you will still have root permission, but only at the level of command line interface and your apps will not be allowed root permissions. Superuser.apk by itself is worthless. Custom ROMS come pre-rooted so the need to re-root is usually unnecessary unless something happens to one of the above mentioned programs. The only way to be sure if/which one is missing is in recovery via the command line because custom recovery will provide temporary root access.
Code:
adb shell ls /system/xbin
...look for su
Code:
adb shell ls /system/app
...look for Superuser.apk
Superuser can be installed from within the ROM using the .apk (at least in earlier versions it was possible), or in recovery using the command line or by flashing the signed .zip from the superuser website . The su binary can only be installed while in recovery.
Of course it all can be fixed by re-flashing your custom ROM.
It may also be necessary to rename the check-rooted executable, but only if you're running the stock Amazon software.
I think that pretty much covers it.

soupmagnet said:
"Root" consists of the su binary, which the system uses to give the user root permissions, and Superuser.apk, which keeps a database of what programs you allow to have those permissions. With "su" only, you will still have root permission, but only at the level of command line interface and your apps will not be allowed root permissions. Superuser.apk by itself is worthless. Custom ROMS come pre-rooted so the need to re-root is usually unnecessary unless something happens to one of the above mentioned programs. The only way to be sure if/which one is missing is in recovery via the command line because custom recovery will provide temporary root access.
Code:
adb shell ls /system/xbin
...look for su
Code:
adb shell ls /system/app
...look for Superuser.apk
Superuser can be installed from within the ROM using the .apk (at least in earlier versions it was possible), or in recovery using the command line or by flashing the signed .zip from the superuser website . The su binary can only be installed while in recovery.
Of course it all can be fixed by re-flashing your custom ROM.
It may also be necessary to rename the check-rooted executable, but only if you're running the stock Amazon software.
I think that pretty much covers it.
Click to expand...
Click to collapse
Ok now things are getting worse I tried to turn the wifi on and it didn't work, I tried to reboot and power off the tablet but it just won't work
{Edit} I want to know that by re-flashing the ROM is there a guarantee that those problems won't happen again.
One more thing is that I deleted the ROM from my kindle I can't transfer it from my laptop because the kindle hasn't been recognized after the jelly bean and I can't downloaded because wifi isn't working so what should I do
Thanks in advance

Scarfacew said:
Ok now things are getting worse I tried to turn the wifi on and it didn't work, I tried to reboot and power off the tablet but it just won't work
I want to know that by re-flashing the ROM is there a guarantee that those problems won't happen again.
Thanks in advance
Click to expand...
Click to collapse
There are never any guarantees when it comes to computers and system software, but the LIKELINESS is very high that the problem will be fixed.

soupmagnet said:
There are never any guarantees when it comes to computers and system software, but the LIKELINESS is very high that the problem will be fixed.
Click to expand...
Click to collapse
One more thing is that I deleted the ROM from my kindle I can't transfer it from my laptop because the kindle hasn't been recognized since I flashed the jelly bean and I can't downloaded because wifi isn't working so what should I do
Thanks in advance

Boot into recovery and "mount" your sdcard to USB. The computer should still recognize it.

soupmagnet said:
Boot into recovery and "mount" your sdcard to USB. The computer should still recognize it.
Click to expand...
Click to collapse
I re-flashed the Rom, wifi is working so I dl ES file explorer and checked Root explorer, but when superuser request popped, I clicked allow but it didn't work it gave me the same message, the new thing is that superuser app added es file explorer to its list but I still can't copy apps in the app/system file.
I know I bored you to death and I'm really thankful for ur help but I really need the root.

Scarfacew said:
I re-flashed the Rom, wifi is working so I dl ES file explorer and checked Root explorer, but when superuser request popped, I clicked allow but it didn't work it gave me the same message, the new thing is that superuser app added es file explorer to its list but I still can't copy apps in the app/system file.
I know I bored you to death and I'm really thankful for ur help but I really need the root.
Click to expand...
Click to collapse
Ok, well try a different ROM. If the problem persists then we can try to think of something.

I flashed the Alien droid ROM it's working fine till now but I need to know how to install an arabic keyboard please
Thanks

Ok, I have a dumb question, but from where do you run the DOS commands from? (ie. what directory?)..
c:\KFU?

Right-click on your KFU folder and select properties to find the folder's path. It may be different depending on wherever you've installed it.

soupmagnet said:
Right-click on your KFU folder and select properties to find the folder's path. It may be different depending on wherever you've installed it.
Click to expand...
Click to collapse
Thanks. but not sure i understand.
Here is what I'm attempting to do.. using the root method described here: http://forum.xda-developers.com/showthread.php?t=1638452 under "Getting to fastboot mode" there are a series of command line examples that seem to start with adb.... (ex. adb shell chmod 755 /data/local/tmp/fbmode).
Under Rooting the stock software, the first step command line is "adb shell mount system"
my question is from where do I start (directory) so that when I enter these commands they work?
Or are you saying that I need to fun all these from the KFU directory? (or KFU/tools) or some other directory..
I appreciate the help and feedback..

:h my::
Wherever adb is...Right-click on that folder to find it's path so you can "cd" or change directories to it. Alternatively, you can Shift + Right-click on that folder and select something like "Open command window here".