So I rooted my tblot no problem but when i rooted my manager's i keep having a problem with the superuser process force closing. I've tried rerooting and reinstalling superuser, updating su... phone is rooted and s-off. I would try and figure it out myself but i only have access to it at work when i bring my laptop in and mess with it on my lunch. So basically i was just wondering if anyone had the same problem and how they fixed it.
Sent from my HTC Mecha
sunflash72 said:
So I rooted my tblot no problem but when i rooted my manager's i keep having a problem with the superuser process force closing. I've tried rerooting and reinstalling superuser, updating su... phone is rooted and s-off. I would try and figure it out myself but i only have access to it at work when i bring my laptop in and mess with it on my lunch. So basically i was just wondering if anyone had the same problem and how they fixed it.
Sent from my HTC Mecha
Click to expand...
Click to collapse
Did you try fixing permissions? It's in Rom Manager.
Rom manager can't run because the superuser process force closes whenever you try and run anything that requires root permissions
Another weird thing is that he is able to uninstall superuser from the manage applications menu
Sent from my HTC Mecha
There are some borked versions of superuser out there. Make sure you're installing a very well-trusted ROM with a known-good superuser app.
sunflash72 said:
Rom manager can't run because the superuser process force closes whenever you try and run anything that requires root permissions
Another weird thing is that he is able to uninstall superuser from the manage applications menu
Sent from my HTC Mecha
Click to expand...
Click to collapse
You can also fix permissions by booting into recovery.
Is there a release of clockwork mod outside of rom manager for the thunderbolt? i tried finding a zip to flash in fastboot but to no avail
Sent from my HTC Mecha
I had a similar issue a while back. I had to redo the entire root process from scratch using the adb method, then I installed a rom that had the superuser fix from rmk40; most TB roms use the fix. Good luck!
Sent from my ADR6400L using XDA Premium App
Your issue may be related to how busybox is installed. A standard "busybox --install [path]" will create a link for busybox's su. If that's earlier on the path than the correct su for Android, it will cause problems. The easy fix is, after installing busybox, remove the su it created.
Everyone seems to do different things with busybox. It may be placed in different places, and may not be "installed" with the links created.
I put it in /system/sbin, and create the links there. If you followed the common instructions for root, that su should be in /system/xbin. The standard PATH is =/sbin:/system/sbin:/system/bin:/system/xbin
From adb shell, do a "busybox which su" It should say "/system/xbin/su"
I wish someone who was setup for cross-compiling would do a busybox with no su, and with "ls --color=never" the default.
Makes sense... unfortunately i don't have too much access to his phone to mess with it. Here's hoping the tbolt gets unrevoked support soon...
Sent from my HTC Mecha
After installing Superuser I went ahead and installed the su beta that I purchased. Well bad idea. It started force closing on me, I tried uninstalling the extra app that came providing me with the beta and now su force closes on me whenever I try to open it. I lost my backups while rooting a while ago. I have tried clearing su's data, and my cache. What can I do?
Okay, nevermind. For some reason, it decided to work again when I attempted to uninstall SU's updates.
EDIT!
su force closes when an app attempts to access it's permissions.
EDIT2
It keeps force closing. Yay.
EDIT3
Okay so I really don't know what's going on. It seems that after uninstalling the updates again and updating it to the latest version it opens fine.
Fixed I guess.
YouThere said:
Okay, nevermind. For some reason, it decided to work again when I attempted to uninstall SU's updates.
EDIT!
su force closes when an app attempts to access it's permissions.
EDIT2
It keeps force closing. Yay.
EDIT3
Okay so I really don't know what's going on. It seems that after uninstalling the updates again and updating it to the latest version it opens fine.
Fixed I guess.
Click to expand...
Click to collapse
I also had this yesterday but after updating it worked fine so... not big problem i think
I just saw this on the XDA home page. Its a new super user app. As we know, the SU app on CM7 is a little buggy and doesnt always give super user permissions. Maybe this app will work better for us. Im going to be trying it out soon.
http://forum.xda-developers.com/showthread.php?t=1538053
UPDATE: So I installed it and tested all my root apps. Seems to work well. I will give it a day or two and see if I have any of the apps fail to get root permissions. If this works and fixes the SU problems we have, then this is a great thing for us CM7 users.
jsgraphicart said:
I just saw this on the XDA home page. Its a new super user app. As we know, the SU app on CM7 is a little buggy and doesnt always give super user permissions. Maybe this app will work better for us. Im going to be trying it out soon.
http://forum.xda-developers.com/showthread.php?t=1538053
UPDATE: So I installed it and tested all my root apps. Seems to work well. I will give it a day or two and see if I have any of the apps fail to get root permissions. If this works and fixes the SU problems we have, then this is a great thing for us CM7 users.
Click to expand...
Click to collapse
Since I am very familiar with ADB and the command line, I tore apart the apk in the linked thread OP to make sure I understood what was happening during the install. I moved the original su binary and Superuser.apk to my emmc (internal memory card), manually pushed the new files out to my phone, and then rebooted.
Once CM7DX2 came all the way up, I started doing some testing and noticed the the original Superuser APK was still showing up in my app drawer. If DOESN'T appear to be conflicting with the new SuperSU APK, but I'm not sure. I have had a few times of the SuperSU app stop responding and asking to either force close or wait. After hitting wait a few times, I ended up just FCing the app.
Once everything smoothed out, the SuperSU seems to have worked, bu, I was still receiving "not responding" messages from the SuperSU app when apps were asking for Root access.
I am going to also cross-post this to the linked OP thread and see if Chainfire wants more digging into this.
Also, as a side note, I think the reason the CM7DX2 Superuser APK was still appearing is that it MAY be installed as part of 2nd-init. I'm not 100% sure about this.
So, in conclusion, for CM7DX2, I think this needs more digging in to and I will offer to work with Chainfire to see what we can do.
Ciao!
Moon Shadow - NM said:
Since I am very familiar with ADB and the command line, I tore apart the apk in the linked thread OP to make sure I understood what was happening during the install. I moved the original su binary and Superuser.apk to my emmc (internal memory card), manually pushed the new files out to my phone, and then rebooted.
Once CM7DX2 came all the way up, I started doing some testing and noticed the the original Superuser APK was still showing up in my app drawer. If DOESN'T appear to be conflicting with the new SuperSU APK, but I'm not sure. I have had a few times of the SuperSU app stop responding and asking to either force close or wait. After hitting wait a few times, I ended up just FCing the app.
Once everything smoothed out, the SuperSU seems to have worked, bu, I was still receiving "not responding" messages from the SuperSU app when apps were asking for Root access.
I am going to also cross-post this to the linked OP thread and see if Chainfire wants more digging into this.
Also, as a side note, I think the reason the CM7DX2 Superuser APK was still appearing is that it MAY be installed as part of 2nd-init. I'm not 100% sure about this.
So, in conclusion, for CM7DX2, I think this needs more digging in to and I will offer to work with Chainfire to see what we can do.
Ciao!
Click to expand...
Click to collapse
Thanks Moon Shadow. The only time I had it hang on "asking for root access" is with Titanium Backup. I think that had to do with the SuperSU app freezing though when trying to get into the settings tab in the app. It just freezes up when selecting that and I had to go into application seetings and manually force stop the app. After that, everything worked fine. I think its just that settings tab for some reason.
The way I installed it was installed SuperSU from the market, then uninstalled the old Super User through the market. I then opened SuperSU and it asked to update so I did. After that, I went through all my root apps and the new SuperSU prompt popped up for all and I granted access. I too see the old SU in the app drawer. Opening that though shows that the only thing that its granting root access to is the new SuperSU app. It doesnt seem to be conflicting with anything so far.
Moon Shadow - NM said:
Since I am very familiar with ADB and the command line, I tore apart the apk in the linked thread OP to make sure I understood what was happening during the install. I moved the original su binary and Superuser.apk to my emmc (internal memory card), manually pushed the new files out to my phone, and then rebooted.
Once CM7DX2 came all the way up, I started doing some testing and noticed the the original Superuser APK was still showing up in my app drawer. If DOESN'T appear to be conflicting with the new SuperSU APK, but I'm not sure. I have had a few times of the SuperSU app stop responding and asking to either force close or wait. After hitting wait a few times, I ended up just FCing the app.
Once everything smoothed out, the SuperSU seems to have worked, bu, I was still receiving "not responding" messages from the SuperSU app when apps were asking for Root access.
I am going to also cross-post this to the linked OP thread and see if Chainfire wants more digging into this.
Also, as a side note, I think the reason the CM7DX2 Superuser APK was still appearing is that it MAY be installed as part of 2nd-init. I'm not 100% sure about this.
So, in conclusion, for CM7DX2, I think this needs more digging in to and I will offer to work with Chainfire to see what we can do.
Ciao!
Click to expand...
Click to collapse
Kind of random but Moon, you are a goddamn machine. The moment something great releases you take it apart and make it better. Good **** man, good ****.
Just including my experience...
SuperSU is working like a champ, but had major issues until I removed Superuser completely.
Here's how I installed:
- Install SuperSU from market
- Uninstall Superuser from settings > applications
- Launch SuperSU and allow it to update it's binary
- Delete superuser.apk from system/apps (use root explorer, es file explorer, terminal, etc...)
- Reboot
Since changing over to SuperSU, I haven't seen a single hang while an app is requesting su permissions.
xawen said:
Just including my experience...
SuperSU is working like a champ, but had major issues until I removed Superuser completely.
Here's how I installed:
- Install SuperSU from market
- Uninstall Superuser from settings > applications
- Launch SuperSU and allow it to update it's binary
- Delete superuser.apk from system/apps (use root explorer, es file explorer, terminal, etc...)
- Reboot
Since changing over to SuperSU, I haven't seen a single hang while an app is requesting su permissions.
Click to expand...
Click to collapse
Same here. This new SU seems to fix the issue we had with the old one. The only problem is that damn settings tab. It freezes the app.
Sent from my MB870 using Tapatalk
i find this relevant to my interest any one else test
Xb0i said:
i find this relevant to my interest any one else test
Click to expand...
Click to collapse
Follow xawen's directions and you'll be fine. It works like a charm.
Sent from my MB870 using xda premium
cant uninstall superuser from settings- applications. doesnt give the option
Xb0i said:
cant uninstall superuser from settings- applications. doesnt give the option
Click to expand...
Click to collapse
Did you go Settings> Applications> Manage Applications and hit the app? If you dont see that option, go into Titanium Backup (an app you have no excuse not having) and uninstall it. Then go into Root explorer and follow the above directions to totally remove it. Then reboot. It may seem like it isnt totally gone cause you may see the icon somewhere, but it likely is gone and a reboot is needed in order to confirm.
yea got the tiBu. but i tried force stopping and clearing data and uninstall never popped up. thought about removing in TiBu buts thats not what it said in the instructions.
Xb0i said:
yea got the tiBu. but i tried force stopping and clearing data and uninstall never popped up. thought about removing in TiBu buts thats not what it said in the instructions.
Click to expand...
Click to collapse
Its what I did. Its a bit of a deviation but it got the job done and thats what matters, ya know?
wow pretty bizzare i cant find superuser in TiBu! whats goin on lol
Xb0i said:
wow pretty bizzare i cant find superuser in TiBu! whats goin on lol
Click to expand...
Click to collapse
Did it disappear after you rebooted? If you have root explorer, go into system/app and see if SU is still gone. If so, you're in good shape.
to clarify
before i even started i backed up original superuser.apk to a folder on sdcard from root explorer, then
i downloaded supersu from market.
went to settings-app-manage apps- etc no choice to uninstall. force stopped- cleared data, still no uninstall option.
went into titanium backup to uninstall from there and superuser wasnt even listed in the apps! (ok weird)
only option left is to just delete from root explorer then continue continue to launch supersu, update binaries and reboot but im holding off.
Lowend was supersuper listed in titanium for u? y isnt it showing up in my list. i find it odd
Xb0i said:
to clarify
before i even started i backed up original superuser.apk to a folder on sdcard from root explorer, then
i downloaded supersu from market.
went to settings-app-manage apps- etc no choice to uninstall. force stopped- cleared data, still no uninstall option.
went into titanium backup to uninstall from there and superuser wasnt even listed in the apps! (ok weird)
only option left is to just delete from root explorer then continue continue to launch supersu, update binaries and reboot but im holding off.
Lowend was supersuper listed in titanium for u? y isnt it showing up in my list. i find it odd
Click to expand...
Click to collapse
I can't find superuser in TB either... it is kind of weird...
i believe u cant delete superuser from tibu cus u need superuser for root access so its like a paradox. i dunno y instructions were as someone showed cus it seems the only way to get this to work properly is delete from root explorer. but im gunna hold off till someone confirms this more legit
I don't understand why you're holding off...if SuperSU is active, go for the reboot and see if the old superuser app clears.
Sent from my MB870 using xda premium
id rather not have a headache if it messes something up.
this thread however gives some detail on supersu
looks like sum apps look for the presence of superuser.apk in data/app and possibly system/app.
a dummy file looks like it can resolve issues. ill switch when more testing is done on CM7dx2.
forum.xda-developers.com/showthread.php?t=1538053
Xb0i said:
id rather not have a headache if it messes something up.
this thread however gives some detail on supersu
looks like sum apps look for the presence of superuser.apk in data/app and possibly system/app.
a dummy file looks like it can resolve issues. ill switch when more testing is done on CM7dx2.
forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
It's odd that you guys don't see the uninstall option for it... Do you see it in Market (err...Google Play, stupid name)? That's another way to get the uninstall done. If it doesn't show up there, you should be able to use root explorer and delete it from /data/apps and /system/apps.
When we installed CM7, the instructions had us update Superuser from market. That would have installed it in /data/apps, so it just needs to be yanked from there. Uninstall via market, tibu, settings>apps or manual through root explorer should all do the same thing. Then you can delete the built in one from system.
Also, if for some reason the whole process breaks down on you...there's a flashable version of the original Superuser that will probably get you going again. I haven't tried it on CM7 though...
jsgraphicart said:
Same here. This new SU seems to fix the issue we had with the old one. The only problem is that damn settings tab. It freezes the app.
Click to expand...
Click to collapse
The most recent update (pushed yesterday) fixed this for me.
Hi everyone, i've searched this to no end, and cannot find the answer.
I had nightly 7/7 working great and decided to flash to the latest nightly 9/3 and 9/9. Also flashed Gapps to 4/13
Formatted the system partition, wiped davlik cache and normal cache and Fixed permissions.. but now when my touchpad starts up, Superuser is denied access to Root Explorer, Anatu CPU clock thing is also denied access..
I have tried to delete the superuser app, and redownloaded it but it still fails in trying to do any updates.
anyone know whats going on? did anyone else loose superuser access when moving to the newer nightly?
trueno92 said:
Hi everyone, i've searched this to no end, and cannot find the answer.
I had nightly 7/7 working great and decided to flash to the latest nightly 9/3 and 9/9. Also flashed Gapps to 4/13
Formatted the system partition, wiped davlik cache and normal cache and Fixed permissions.. but now when my touchpad starts up, Superuser is denied access to Root Explorer, Anatu CPU clock thing is also denied access..
I have tried to delete the superuser app, and redownloaded it but it still fails in trying to do any updates.
anyone know whats going on? did anyone else loose superuser access when moving to the newer nightly?
Click to expand...
Click to collapse
Get SuperSU by Chainfire from the market, SuperUser is a prick!
samething, I tried SuperSU and only 2 of my apps show up.
no idea whats going on with it..
trueno92 said:
samething, I tried SuperSU and only 2 of my apps show up.
no idea whats going on with it..
Click to expand...
Click to collapse
The apps should only shows up as they are granted permissions
Sent from my CM9 TouchPad using TapaTalk 2
I have the same problem, and trying to open Superuser closes like when you try to open Play Store without flashing it. su fix app doesnt work either.
Sent from my YP-G70 using xda app-developers app
I just upgraded to JB on my HTC Evo 4G lte. I am S-ON rooted and everything is working except SuperSU v0.99. I see several others are having the same issue. We are rooted and our apps can obtain root but when you open the SuperSU app, it wants to update the binary. If you allow it to update the phone crashes and reboots. If you select cancel SuperSU closes and you cannot get to any of the settings. There does not seem to be a solution that I have found. I would like to switch to another Superuser app but can't seem to find instructions on how to do so.Will changing to another Superuser app even solve the problem? Ideas?
Edit: Upon further investigation it appears that changing to ChainDD's superuser app may not solve the issue of not being able to update the binaries. So what is the solution?
Edit: I got my answer:
xHausx said:
The only solution is to get s-off. It looks like the new hboot locks the system partition so apps such as supersu and ad-free aren't going to work for you anymore.
Click to expand...
Click to collapse
I'm having the same issue. I switched to superuser and now I'm rooted as root checker states but I can't use adaway any more as Xhausx mentioned that the system directory in JB is locked now and the only way to make it work is to get s-off which is not available right now and i doubt it will be.
Sent from my EVO using xda app-developers app