Running a froyo rom and ever since my first reboot all of a sudden it fcs constantly and my root doesn't work.. ran terminal and tried su and didn't have permissions.. do I have to run that exploit whenever I want permission or something..?
Sent from my T-Mobile myTouch 3G Slide running froyo using XDA App
I had this issue too, I can't remember what caused it but it's exactly what you're describing. The fix for it was uninstalling superuser and re-installing it. You need to find the latest superuser, I think it's 2.3.1 (ef). Then find the thread about installing it. Just in case you don't know, you will have to be in recovery and mount the system in clockwork (partitions).
KCRic said:
I had this issue too, I can't remember what caused it but it's exactly what you're describing. The fix for it was uninstalling superuser and re-installing it. You need to find the latest superuser, I think it's 2.3.1 (ef). Then find the thread about installing it. Just in case you don't know, you will have to be in recovery and mount the system in clockwork (partitions).
Click to expand...
Click to collapse
There's been a newer one out, 2.3.6.1. That was a while ago. I haven't checked for any newer ones.
Yeah I realized it a while after I posted that. I was flashing the latest nightly and came across my superuser.apk I have on my sdcard.
Related
I have been using eugene's update.zip to get into clockwork mod.(along with the engineering build) It works fine.
My problem is it contains an old version of superuser.
I had been using su-2.3.3. But every time I go into clockwork mod for anything I'm reverted back to su-2.1.
Which doesn't even work at this point, it actually breaks the app altogether, causing repeated FC.
What I've been doing is just reflashing su-2.3.3 to get back up and running, but I was wondering
is there a new update.zip for getting into clockwork mod?
Something that doesn't even have su installed.
Just remove su from that update and resign it...
-BMFC
Sent from my T-Mobile myTouch 3G Slide using XDA App
bmfc187 said:
Just remove su from that update and resign it...
-BMFC
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
OK so I removed he superuser.apk. How do I resign this? Sorry I'm a noob at this.
Personally I use ROM Manager by Clockwork in the market. Koush keeps it updated very well and there is no need to keep update.zip on your sd card with this app, it allows you to reboot directly into recovery from the app.
RavenWulf said:
Personally I use ROM Manager by Clockwork in the market. Koush keeps it updated very well and there is no need to keep update.zip on your sd card with this app, it allows you to reboot directly into recovery from the app.
Click to expand...
Click to collapse
WOW!!
Your sooo right!! I finally gave rom manager a shot and your right this is waaayy easier.
I had considered using it but I was unsure about how it could access the recovery seeing as the MT3GS has got a weird nand thingy.
Also I'm so used to the G1 and N1's aman ra recovery's that I always looked at clockwork as being lame. But I stand corrected, I'm going to buy the pay version.
RavenWulf said:
Personally I use ROM Manager by Clockwork in the market. Koush keeps it updated very well and there is no need to keep update.zip on your sd card with this app, it allows you to reboot directly into recovery from the app.
Click to expand...
Click to collapse
I agree, I do the same thing. I love how well it works to it's perfect for reboot recovery too, now extra steps in the process of getting to recovery. I do keep the update.zip on my sdcard just in case something goes bad I can get back in without relying on my apps loading.
I got a superuser update and while updating one day it updated succesfully.. now all of a sudden ts prompting update again and its not updating.. its throwing a update failed error message.
Anything that needs root access like titanium says cant get root acces..
whats going on?
The kernel you are using may not have the proper signature to update to the 3.0 binary. You can try the superuser update fixer from the market, and then update the binary, or just uninstall the new superuser from the market to revert back. I find the update fixer works temporarily for me untill I reboot, then it tells me to update binary again. I just reverted back for now.
Sent from my SPH-D700 using xda premium
I had a similar issue, where I would get something like "Obtaining root access: Failed" whenever I tried to update the binary file. I would also get a random FC of Superuser.
I uninstalled Superuser to get to the original one when I rooted my phone, and updated again via Market. It updated the binary file fine now. Hope that helps!
Note, I do also have Superuser Elite, but I didn't modify that at all.
hardrock121 said:
I got a superuser update and while updating one day it updated succesfully.. now all of a sudden ts prompting update again and its not updating.. its throwing a update failed error message.
Anything that needs root access like titanium says cant get root acces..
whats going on?
Click to expand...
Click to collapse
Had this happen a while back. Just clear the su cache and re-try, that should fix the error
Sent from my SPH-D700 using xda premium
Lol works fine on the stock kernel.
(I keep telling people that stock has its benefits) lol
Roll Tide
Works fine on ET4G stock kernel too.
Sent from my SPH-D710 using xda premium
JohnCorleone said:
Works fine on ET4G stock kernel too.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Sent you a pm, btw.
Roll Tide
Check the market, they've been updating the Superuser app, like crazy the last few days. I've now had about 3-4 updates (at least one per day).
Uninstall the update then unistall the super user app. Reinstall the super user app, reinstall the update, and then try again. This worked for me.
I had automatic updates enabled, I think it screws it up. So uncheck it and manually update it whenever it needs to be.
Here's a quoted answer from http://forum.xda-developers.com/showpost.php?p=18212299&postcount=2646
styles420 said:
The developer of su stated on his website that the binary cannot be updated if it is installed in /sbin, because that directory is actually a part of boot.img, which remains read only even if the system partition is mounted with read-write access. This is exactly how it is installed in SRF 1.2 (and probably all earlier versions, as well as several other Epic roms).
Rom developers will need to change the su install directory in order for the su app to be able to update the binary.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
But if you're using a stock setup, perhaps one of the other answers here would be more helpful.
hey guys superuser force closing alot on me im so-off.6.98 boot
it closes then sometimes its fine, titanium backup wont find root then it does seems very strange any ideas?
I also have the same problem
ok i deleted superuser 3.04 and installed 3.02 seems to be working ok.
heres zip if anybody needs,
Anyone know why the update crashes?
Sent from my HTC Desire using xda premium
I had updated SU and had the same issue but flashed the zip file above in recovery and it sorted it, so thanks for that. Currently using version 3.0, are there any advantages or new features of the new version?
Did anybody try clearing data for su via manage applications? Usually works for this
Sent from my HTC Desire using XDA App
yeah i tried it dan , didnt really help me much.
A new update came out last night, does that fix this?
Sent from my Xoom using xda premium
maybe somebody can try mines ok at the mo. and if its working for u why update!
I had problems with 3.02. I then tried to uninstall it and flash 2.3.6.3.
No joy.
Then again the market update for 3.02 showed up and I installed it.
No go.
I went to running apps and cleared data for super-user.
This solved all problems and since then I have updated via market to super-user 3.04 and all is well.
Why use old versions when newer is available
Thanx gerhard i had the same problem and your solution was the best.
I got FC with busybox but after i cleared the data everything was ok.
Thanx again.
-------
Edit : i had to clear data again...it seams i have to clear data every time i want to use it with another app.
An i'm using su 3.0.5
3.0.5 is buggy as all get out and causing all kinds of problems. Makes me wondering if the dev is trying to get people to buy the elite version?
Sorry for the "conspiracy theory" here, but there's been a bunch of SU updates, several of them FC all the time.
I've gone back to 3.0.2 per the zip on this thread. Gotta have my wifi tether working.
Use super user 2.3.6.3
Use super user 2.3.6.3 it solved all my problems.
I read somewhere that if you uncheck the "remember" option, it won't force close. Let me know if that works
I had the same problem with Super User and wasn't able to solve it . I tried cleaning data and then su started up without fc, but it couldn't get root access. So I just wiped everything via recovery (Titanium Backup before that) and reinstalled my current rom. That solved my problem.
I think the latest update fixed the force close error.
edit: No, I hadn't updated yet... my bad, I thought it did.
tangcla said:
I think the latest update fixed the force close error.
edit: No, I hadn't updated yet... my bad, I thought it did.
Click to expand...
Click to collapse
Damn. I updated mine based on this and lost root access all together
now
Sent from my HTC Desire using xda premium
I am fairly sure 3.0.6 fixed it, I updated it and haven't seen any errors since.
Also updated the binary to 3.0.1 in the Superuser app preferences.
so pi$$ed off with superuser !!,it either force closes or binary will not update ..... i have installed several zip files that are supposed to fix it,tried the one from the market numerous times !!!
i have just got my rom working great,now i cant reset my voltages cant access titanium back up or rom manager.. only one option left full wipe and flash rom again ...... bugger ...... i have tried everything ....
I have the same problem, and i must do wipe all.
Know is working.
One of my main reasons for rooting is now not working any longer - Titanium backup. It used to work perfectly fine but.....
After the small incremental ICS update that came in a few days ago I of course lost root.
I re-rooted...and the first thing I noticed was that TiBu gave an error message about insufficient SU priviledges.
I re-rooted and SuperUser gave TiBu access as per normal..but the issue persisted.
I can backup...but when trying to restore ANYTHING it just hangs.
I factory-reset...re-installed SU and TiBu...issue still there.
Not sure what to do.
Has anyone who also got the latest small ICS update been able to restore apps from TiBu since then or could you try and let me know?
That would at least rule out the possiblity that something came in with that update that breaks the root process.
Update:
I even installed an old version of TiBu just in case, for any reason, the new TiBu version fro 5/27 was the culprit - but no, the same issue.
So its either;
a) The new, small ICS update broke something when using ZN's easy-root script, or
b) my tablet is fubar'd to the point that a factory reset can't get me to place where I can root and get the access priviledges needed for TiBu.
ANY thoughts?
note: i am rooted using ZN's easy-root script...is there any chance that with this new ICS update/patch something came in that is not giving sufficient SU priviliedges using that script?
And/or is there an alternative root process I can use to see if that works better?
Darkbulb said:
One of my main reasons for rooting is now not working any longer - Titanium backup. It used to work perfectly fine but.....
After the small incremental ICS update that came in a few days ago I of course lost root.
I re-rooted...and the first thing I noticed was that TiBu gave an error message about insufficient SU priviledges.
I re-rooted and SuperUser gave TiBu access as per normal..but the issue persisted.
I can backup...but when trying to restore ANYTHING it just hangs.
I factory-reset...re-installed SU and TiBu...issue still there.
Not sure what to do.
Has anyone who also got the latest small ICS update been able to restore apps from TiBu since then or could you try and let me know?
That would at least rule out the possiblity that something came in with that update that breaks the root process.
Update:
I even installed an old version of TiBu just in case, for any reason, the new TiBu version fro 5/27 was the culprit - but no, the same issue.
So its either;
a) The new, small ICS update broke something when using ZN's easy-root script, or
b) my tablet is fubar'd to the point that a factory reset can't get me to place where I can root and get the access priviledges needed for TiBu.
ANY thoughts?
note: i am rooted using ZN's easy-root script...is there any chance that with this new ICS update/patch something came in that is not giving sufficient SU priviliedges using that script?
And/or is there an alternative root process I can use to see if that works better?
Click to expand...
Click to collapse
Did you try reinstalling busy box? If that's not working TiBu won't work. Not sure if it directly affects SU or not, but try installing it and updating binary in SU settings.
Tapatalked from my Galaxy S II.
I think I may have resolved it...
Using root explorer I mounted system directory as writable...I re-installed TiBu..it gave the same warning about priviledges..but this time it fixed it...I rebooted...and can now restore apps
I had a similar issue. Manually updating SU binaries, then Ti did a fix and rebooted. Working fine now.
Romman0 said:
I had a similar issue. Manually updating SU binaries, then Ti did a fix and rebooted. Working fine now.
Click to expand...
Click to collapse
I can confirm doing this solves the problem. Thanks!
pio_masaki said:
Did you try reinstalling busy box? If that's not working TiBu won't work. Not sure if it directly affects SU or not, but try installing it and updating binary in SU settings.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
I thought ZeroNull specifically said NOT to update busybox or you could break root for some apps. Has anyone successfully updated bb without breaking root? I had a problem after updating bb using jrummy's apk. I haven't tried the stericson apk.
Sent from my A100 using XDA Premium HD app
X.Neptune said:
I thought ZeroNull specifically said NOT to update busybox or you could break root for some apps. Has anyone successfully updated bb without breaking root? I had a problem after updating bb using jrummy's apk. I haven't tried the stericson apk.
Sent from my A100 using XDA Premium HD app
Click to expand...
Click to collapse
I didn't say update I said reinstall first then maybe update, they updated on their own and it worked so it seems to be fine to do now. I use stericson's but I never updated nor have a need to it works fine.
Tapatalked from my Galaxy S II.
pio_masaki said:
I didn't say update I said reinstall first then maybe update, they updated on their own and it worked so it seems to be fine to do now. I use stericson's but I never updated nor have a need to it works fine.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
You're right. You did say reinstall, not update. Sorry.
Sent from my A100 using XDA Premium HD app
X.Neptune said:
You're right. You did say reinstall, not update. Sorry.
Sent from my A100 using XDA Premium HD app
Click to expand...
Click to collapse
Np you did have a point, it was said to not update it, but if all else fails updating may be all that's left without wiping and starting over. Or maybe advanced restore system....but yeah that sounds like more trouble.
Tapatalked from my Galaxy S II.
pio_masaki said:
Did you try reinstalling busy box? If that's not working TiBu won't work. Not sure if it directly affects SU or not, but try installing it and updating binary in SU settings.
Click to expand...
Click to collapse
Updating the binary didn't solve it for me. But a fresh install of Busybox took care of the issue and hasn't caused any other problems.
Darkbulb said:
I think I may have resolved it...
Using root explorer I mounted system directory as writable...I re-installed TiBu..it gave the same warning about priviledges..but this time it fixed it...I rebooted...and can now restore apps
Click to expand...
Click to collapse
Same solution. I use ES explorer and allowed to mount system as writable. After that TB successfuly fixed permissions on su binary.
Sent from my HTC HD2 using XDA
Hi, I recently got a GSM Google Nexus from the Play store. Rooted it on ICS. Than got OTA for JB.
After the update I noticed that my Superuser permissions are acting weird like Rom Manager, Superuser itself and Quickboot are getting denied.
Also, Apex launcher reset itself to default without me doing anything.
And my GPS doesn't work on T-Mobile.
Is it one major problem, with a root issue or multiple problems with multiple issues?
Sent from my Galaxy Nexus using xda app-developers app
smartedpanda said:
Hi, I recently got a GSM Google Nexus from the Play store. Rooted it on ICS. Than got OTA for JB.
After the update I noticed that my Superuser permissions are acting weird like Rom Manager, Superuser itself and Quickboot are getting denied.
Also, Apex launcher reset itself to default without me doing anything.
And my GPS doesn't work on T-Mobile.
Is it one major problem, with a root issue or multiple problems with multiple issues?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
update your su. get the SuperSU app from the play store, open it, update your su.
I cant updated Superuser nor SuperSU
smartedpanda said:
I cant updated Superuser nor SuperSU
Click to expand...
Click to collapse
explain? what do you mean you cant update?
heres a flashable in recovery SuperSU. flash it, boot up, open the app, and update to the most recent.
I can't update it, I downloaded SuperSU from the Playstore, hit update it says Superuser has been denied. I tried to update Superuser, it denies itself. It can't flash anything in recover because it won't reboot into clockmodROM, it says clockmodRom denied too.
smartedpanda said:
I can't update it, I downloaded SuperSU from the Playstore, hit update it says Superuser has been denied. I tried to update Superuser, it denies itself. It can't flash anything in recover because it won't reboot into clockmodROM, it says clockmodRom denied too.
Click to expand...
Click to collapse
I had a similar problem where my root permissions were acting weird after the OTA to JB. Also, my su binary was out of date and I couldn't update through Superuser. So I put the phone to debugging mode and hacked away with adb. I made sure I mounted system to r/w (which I could, I dunno why), I updated the su binary with a push and downloaded SuperSU through Google Play.