Develop Bugs

[Q] Noob needs help with Unrevoked Evo

Like I said I'm a noob.But I've rotted several phones with Z4,but i tried Rooting a Evo 4g with O.T.A 2.2 update using Unrevoked. Everything went ok until I tried using anything that needed Superuser Permissions. Superuser would pop up every time i pressed Allow.I'm trying to Flash to CM7,but can't get passed SU problem. Has any one came across this problem and solved it. Any help would be Greatly Appreciated..

512heroATX said:
Like I said I'm a noob.But I've rotted several phones with Z4,but i tried Rooting a Evo 4g with O.T.A 2.2 update using Unrevoked. Everything went ok until I tried using anything that needed Superuser Permissions. Superuser would pop up every time i pressed Allow.I'm trying to Flash to CM7,but can't get passed SU problem. Has any one came across this problem and solved it. Any help would be Greatly Appreciated..
Click to expand...
Click to collapse
No I haven't had that issue, and I'm kind of confused about what you are saying.
https://market.android.com/details?id=com.noshufou.android.su&feature=search_result
try that.

What Im trying to say is. When trying to backup with Titanium Backup or use Rom Manager SU keeps popping up with no progress in the App. Say for instense i want to use WirelessTether it would say asking for Root rights, SU would pop up and ask Allow or Deny. I'll press Allow then SU would pop up again and again. Every time i pressed Allow.

512heroATX said:
What Im trying to say is. When trying to backup with Titanium Backup or use Rom Manager SU keeps popping up with no progress in the App. Say for instense i want to use WirelessTether it would say asking for Root rights, SU would pop up and ask Allow or Deny. I'll press Allow then SU would pop up again and again. Every time i pressed Allow.
Click to expand...
Click to collapse
Try installing superuser with the link I sent you or search super user in the market.

That seem to do the trick. Thanks for the help

Rooted Desire keeps asking for Superuser permissions

I've searched high and low for a solution to this that works for me, both here and everywhere else Google would point me, but I have yet to find one that works, so I hope someone can help me.
I've an original Desire running a rooted Froyo ROM, which was rooted using unrevoked ages ago (probably a year or so no). When I originally rooted it, everything worked perfectly. A few months ago I ran the newest version of unrevoked over it again to update the recovery to the latest clockwork and it appeared to work fine, but ever since I did this the superuser app will continually pop up asking for permissions every time any app that needs root is run (sometimes MANY times, as when Titanium backup is run).
I've tried different things to see if I could fix it - clearing the data for the Superuser app, clearing the Dalvik cache, even reflashing the older clockwork recovery back onto my phone with the older version of unrevoked which originally worked, but with no luck. The phone is still S-ON, but I don't see why that would matter when I had no problems with the original rooting of the phone.
I'm stuck and am not sure where to go from here, so any advice would be very appreciated.

Ommadawn said:
I've searched high and low for a solution to this that works for me, both here and everywhere else Google would point me, but I have yet to find one that works, so I hope someone can help me.
I've an original Desire running a rooted Froyo ROM, which was rooted using unrevoked ages ago (probably a year or so no). When I originally rooted it, everything worked perfectly. A few months ago I ran the newest version of unrevoked over it again to update the recovery to the latest clockwork and it appeared to work fine, but ever since I did this the superuser app will continually pop up asking for permissions every time any app that needs root is run (sometimes MANY times, as when Titanium backup is run).
I've tried different things to see if I could fix it - clearing the data for the Superuser app, clearing the Dalvik cache, even reflashing the older clockwork recovery back onto my phone with the older version of unrevoked which originally worked, but with no luck. The phone is still S-ON, but I don't see why that would matter when I had no problems with the original rooting of the phone.
I'm stuck and am not sure where to go from here, so any advice would be very appreciated.
Click to expand...
Click to collapse
When you're on Superuser app, do you see your apps with green button on the rigth ?
Witch version of Superuser app do you use ? Mine is v2.3.6.3 with cmd su v2.3.1-ef

Also, when being asked for permission, is "Remember" checked?

why not just re-root?

punky.mtp said:
When you're on Superuser app, do you see your apps with green button on the rigth ?
Witch version of Superuser app do you use ? Mine is v2.3.6.3 with cmd su v2.3.1-ef
Click to expand...
Click to collapse
Yes you should have a list of allowed apps on opening the su app itself - click apps on top left. The allowed apps shouldn't keep requesting permission each time.
You coukkd uninstall su app then reinstall from market?
Nandroid backup first!

Thanks for the all the replies, much appreciated!
@punky.mtp & @stringer7: Yes, I can see the apps I've granted permissions to in the Superuser app, each has a green button against it. I'm not sure of the current version of SU I'm running, but I know it's not the latest version. I've tried to update it from the Market but it won't over-write the existing installed SU. I'm doing a nandroid as I type and will try uninstalling and reinstalling to see if that helps.
@HiVoltage85: Yes, I've set the remember checkbox as well for each app when granting permission.
@BigMrB: I've already re-rooted with different versions of unrevoked, several times, which hasn't fixed the problem.
I'll let you know how I go.

Sorry, I'm giving away my ignorance, but how do I uninstall my current Superuser app? The uninstall button is disabled in the manage applications part of the phone's setup.
Edit - Never mind, I found how to do it.

Looks like I have it fixed. I was able to remove the old Superuser app and install a new one from recovery (v2.3.6.3) which works properly and doesn't keep asking for permissions repeatedly. Thanks for the suggestions and help!

[Q] Nand Unlocking

Hey guys, im fairly new to the whole rooting and customizing of android scene, but i rooted my epic 4g using the oneclickmethod found here. Everything has gone fine and ive been able to flash multiple roms and try different things out, but today i downloaded the font changer app which then lead me to downloading the busy box app, however i got hung up on the installation of busy box because its saying im not nand unlocked. i assumed that took place with the whole rooting method, is there anything i can do to fix that at all?

ianduh said:
Hey guys, im fairly new to the whole rooting and customizing of android scene, but i rooted my epic 4g using the oneclickmethod found here. Everything has gone fine and ive been able to flash multiple roms and try different things out, but today i downloaded the font changer app which then lead me to downloading the busy box app, however i got hung up on the installation of busy box because its saying im not nand unlocked. i assumed that took place with the whole rooting method, is there anything i can do to fix that at all?
Click to expand...
Click to collapse
I believe No nand unlock is needed, unless it goes through that when rooting. Make sure superuser is up to date. Even try to uninstall superuser and re install. I had the same problem before and am trying to remember what I did. I know I uninstalled superuser & re installed and uninstalled the APP i was trying to get to work and also re installed. So try that and see if it works

Samsung doesn't NAND lock their phones.

Even try to uninstall superuser and re install. I had the same problem before and am trying to remember what I did. I know I uninstalled superuser & re installed and uninstalled the APP i was trying to get to work and also re installed. So try that and see if it works
Click to expand...
Click to collapse
i dont mean to sound completely stupid, but how do i go about uninstalling/reinstalling superuser, do i just re-root the phone? Just asking before i try anything so i minimize my chance of bricking, thanks guys.

why dont you link us to the app not working?

If you have a ROM installed chances are that you already have busybox, there that most dev's include it on there ROMs.
I think that your trying to install Busybox in an area of your phone were its currently mounted as Read Only and not R/W. Double check the destination of the busybox installer (it will give you several options) and choose from there.

Why do I keep losing root?

My Verizon GNex is rooted, I have CWM, superuser etc, even installed this rom, but I keep losing root after an hour or so. I use root explorer, open a terminal, su, do things, do it again in a few minutes and it suddenly won't log in as root.
When this happens, my wifi also craps out. It shows signal strength too low to connect when I'm standing next to the router. Reflashing CWM or superuser does nothing. Last night I wiped and went back to stock and it worked for a while, but I've found I can also flash that rom and it will work for a while and that is easier. Root survives multiple reboots but just stops working for no reason after a while.
Example: I flashed that rom this morning and rebooted 2-3 times, went to the mall and kept opening root explorer to see if root was working. I sat and watched my daughter play at the mall for nearly an hour. When she wanted something to drink, I checked and root was still working. I went to the store nearby, got a water, sat back down and no longer had root.
I'm not getting any OTA notification or anything, it just stops being rooted out of the blue.
Any ideas?

Darn, halfway down page two already and no replies...

same issue here

I'm glad I'm not the only one. How did you root?

followed this until step 5 http://forum.xda-developers.com/showthread.php?t=1392310

Me too. I used a different guide, but it looks like it was exactly same.

Do you use root explorer? I was only using it to check if I had root yesterday -it opens when rooted, doesn't when root is lost- and after losing root I noticed its battery usage was nearly as high as the displays although I had only opened it for 2 seconds several times.
Last night I rerouted before bed and didn't touch root explorer and im still rooted ten hours later. May not be related, and I could lose root at and time, but I was losing it every hour or two, so I'm starting to get optimistic that root explorer may have had something to do with it.
Sent from my Galaxy Nexus using Tapatalk

fubaya said:
Do you use root explorer? I was only using it to check if I had root yesterday -it opens when rooted, doesn't when root is lost- and after losing root I noticed its battery usage was nearly as high as the displays although I had only opened it for 2 seconds several times.
Last night I rerouted before bed and didn't touch root explorer and im still rooted ten hours later. May not be related, and I could lose root at and time, but I was losing it every hour or two, so I'm starting to get optimistic that root explorer may have had something to do with it.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Haven't seen this specific issue much with the Galaxy Nexus yet. I had this problem 1.5 yrs ago with an older Samsung Android device though. Solution was a bit complex, but haven't seen this issue in a long while.
I know root can be a bit hidden from Android unless adb is connect or using a terminal application. For this reason, m root check application is generally a good program to run a simple diagnostic of the root configuration on the device.
The Pro version, 99 cents in the Market and free on XDA has a widget which will update at the interval you pick, 1-24 hrs with the root status and gives a more thoroughly diagnostic output of the system su binaries and their properties.
Hope that helps!

Try putting the su binary in /system/xbin. I lost root after the OTA update to ITL41F, but busybox in /system/xbin survived.

I have root checker and when I lose root, it still says everything is OK. Superuser logs also show that apps have been allowed, but the apps just don't get root. When it happens, everything loses root, terminals root explorer, titanium backup etc. even the superuser app can't update the su binary.
I still have root after 11+ hours (crossing fingers)
Sent from my Galaxy Nexus using Tapatalk

motopig said:
Try putting the su binary in /system/xbin. I lost root after the OTA update to ITL41F, but busybox in /system/xbin survived.
Click to expand...
Click to collapse
The su binary will have also remained after an OTA, same as busybox. The difference is their permissions. Every OTA re-sets the binary direction permissions as 755 stripping out the setuid attribute required by su, but not required by busybox.
This would explain why after using an OTA the user will lose "root" access but maintain busybox access. Both binaries persist, but the su binary loses the setuid attribute required to elevate access for root.
fubaya said:
I have root checker and when I lose root, it still says everything is OK. Superuser logs also show that apps have been allowed, but the apps just don't get root. When it happens, everything loses root, terminals root explorer, titanium backup etc. even the superuser app can't update the su binary.
I still have root after 11+ hours (crossing fingers)
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Well the key here, as I stated above, would be to see whether or not the su binary still has the setuid attribute and UID/GID set as root.
Any of those changes could remove the ability of the su binary to esclate permissions as root. In theory, any application which has been granted root access through Superuser, could remove root access for the whole system.
I can't imagine any reason why a developer would intentionally write an application to do that under a different title which you would be using.
Hope the technical details help!

I never had an OTA update after rooting, at least there were no notifications or anything. I do agree it acted as if the binary permissions got screwed up somehow, I don't know why I didn't check. Reflashing the su.zip didn't help. I assume flashing would set the permissions.
Well, nearly 24 hours and I still have root so, whatever it was, I'm happy now.

I just realized i no longer have root and i did the ota update recently. Problem is i cant get root back no matter what i try. I reinstalled the latest superuser from market with no luck. Any advice?
I forgot to mention i am completly stock on 4.0.1 and ITL41F. All i did with this phone is unlock the bootloader and the guide i used i think pdanet put SU apk automatically installed. My apps like root explorer all showed they did have root access. But now i tried to use root explorer and it claimed it had access, but couldnt get root.
My SU apk was updated to latest from the market. I just uninstalled the update and still no luck. Reinstall update and still no luck..

When it happened to me, the only thing that worked was to reflash the rom and go through the rooting process again. There is a thread in the development section about going back to stock where you can find the stock rom. you'll lose apps and things and may want to back them up first.
You could probably flash a new rom instead. I don't remember which one it was, but I was using a 4.0 rom that had su and didn't require wiping anything so reflashing was painless.
Sent from my Galaxy Nexus

Crap ok thanks. I cant backup anything with titanium cause it cant get root, so i guess i jyst have to lose everything. Might as well go with one of the roms i guess. I kinda was just enjoying stock with root.
Oh the other problem i have is i'm getting a fastboot error. Boot into bootloader and at the bottom of the screen says "fastboot FAILstatus" below. Any idea what thats about?

Some apps can export their settings the sdcard so don't forget to check them. I know when I lose everything there's really only 4-5 apps that require much setup while the others just require a login, but luckily those 4-5 apps can export their settings.
I don't know about the error, I'm not very good with fastboot. I use it when I get a new phone then go a couple of years without using it.

i finally got rooted again. For some reason it just wouldnt take. I had to use superboot over and over and over again and then finally it just took successfully even though i didnt anything differently. Very strange.

[Q] Recent SuperSU Updates - Issues

Figured I would start here in my device thread before trying the SuperSU thread.
Anybody have issues with SuperSU since the last few updates ago?
SuperSU does not even open. Root-dependent apps do not open. Titanium sits there at the initial screen "asking for root rights" until I kill the app. AdAway does not open... just goes right to a black screen until I kill the app. AdAway seems to work though, as my web surfing does not have ads.
I've also tried manually going in and applying the latest update via (philz) recovery.
Would I be safe to roll back to an older version of SuperSU?
Mods... if you're going to gun the thread, please at least point me in the right direction as I did search, but did not find anything related to recent issues on the Note 2 for SuperSU.
TIA for help and suggestions.

Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.

ceabbott2 said:
Oh yeah its still sitting in the play store. I lost root the last couple updates ago. I had to re flash my rom and start over.
Click to expand...
Click to collapse
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.

lennykravitz2004 said:
As part of my search, I did see Chainfire mention in his "fix" thread that some apps like wanam can cause issues. Of course, I have xsposed installed, so that could be the issue.
Do you (or did you) also have xsposed installed as well?
I have tried older versions of SU, uninstalling via philz then redownloading from Play - which now tells me the binaries are out of date and can't be done by SU, and I need to re-root.
Think I might try one of the other SuperUser apps "just to see how it works", or if it does.
Click to expand...
Click to collapse
For me, I just reflashed the ROM I was running at the time and that resolved it. Of course seeing that the update was " fixed" I attempted it and lost root again. I then did the same as before, wiped and relashed. I didn't do clean installs either time. Just wiped caches and reflashed. That sucks if you have to re-root. I mean, it's easy and all but it shouldn't have to be done.
D

Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.

DJ_Barcode said:
Before attempting any drastic measures (i.e., full wipe and reinstallation of the ROM), try this. This trick usually works for me.
Open your Application Manager, and locate your SuperSU application. Turn it off (i.e., click the "Turn Off" button). It may prompt you that updates are about to be uninstalled; that's ok. Download "BETA-SuperSU-v2.25.zip" and verify the MD5. Reboot into recovery and flash this file. Reboot and re-enable the SuperSU application from the Application Manager (it will be easy to find this time - scroll all the way over to the right, under "Turned Off"). Open SuperSU and it should let you reinstall the binaries.
Recently I've inexplicably lost root a number of times, and the above method has fixed it for me every time.
Click to expand...
Click to collapse
Thanks for the try. Did not work though.
Looks like I just need to re-flash the ROM.

My problem was odd. Before I discovered the aforementioned trick, I'd re-root with Chainfire or Kingo. I'd reboot, and my device would be rooted. But those two methods have an additional payload - they flash the stock recovery. So I'd ODIN the Philz Touch recovery back to the device, reboot, and root would be gone. Never figured out what was going on.

Yup. Issues with new version. Only last 2 or three updates.
They seemed to be perfectly fine with cm12 though.
Sent from my SPH-L900 using XDA Free mobile app

Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!

lennykravitz2004 said:
Thanks for all of the input.
After doing a full wipe, and then re-loading Classic Stock 4.4.2, life is good again! Back to running awesome for a few weeks now.
Having said that, I did want to follow-up and ask others what current version of SuperSU you are on. As of right now, I am still on v2.01 (which is what was packaged with the ROM) and have not updated yet. Only other versions of SuperSU I have zips downloaded for are: 2.25 from post above, 2.36, and 2.37.
Any suggestions or confirmations on which newer/more recent versions will not bork my root status? Or which versions to definitely stay away from trying to use?
Thanks, and I appreciate any help and suggestions!
Click to expand...
Click to collapse
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app

jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
As always, thanks for your response. Your recommendation is what I've been doing, just wanted to follow-up on this and see if there was anything else I needed to consider or change as well.
My main concern was to make sure I was not going to run into any "big" issues (especially security) by staying on current version. Thanks for explaining where the issue really lies on this too. I'm obviously not a dev, however I do want to understand what is exactly going on and responses like yours always provide that type of info. :good: Thank you.
And, FWIW, using "fool proof" to describe a process only makes me more curious (and no, not in that way) about your suggestion. :laugh:
Now I HAVE to find out more about that option... (only after some of the best BBQ in all of the land - Sugarfire BBQ in STL )

jlmancuso said:
The actual issue is not superuser or the updates. The issue is 4.4.2 and the original way we (ROM devs) had to implement superuser.
There are two routes to take to keep from losing root. The easiest for most users is to turn off auto updates and not to update superuser (app or binaries). The second is more difficult for the average user. Do a complete removal of superuser and install the latest.
I suggest the first way for everyone. It is simple and fool proof.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
How do you disable auto update of binary on SuperSU? I keep seeing it in the notification bar, very annoying.