Hi everyone,
My problem began last week when I updated from the Market the latest version of SU. I tried several suggestions from other people as far as uninstalling the update that worked, but still had force close from SU. Did not know how to uninstall the biraries associated with this app. Luckily for me I had a backup of my system fromJuly of this year and had to resort to using that in order to fix all the force closes generated by SU 3.05. After restoring backup using ROM Manager from that date to the older, but more stable SU (2.3) I think, I had to d/l all updates again fro my apps (time consuming). I went to the Market and unchecked (allow autmatic updating) for SU, needless to say it updated regardless. Also, since it went ahead and updated on it's own and a message was in my notication bar saying (SU binaries out of date) I manually updated them also. Force close city... I did not have this with SU 2.3, but now, nothing but. ROM Manager, Root Explorer, ShootMe etc... I went to settings/applications/manage applications/all/and selected SU and clicked on the command button to remove all updates for this app, rebooted, went back to the same path and clicked on clear cache, rebooted again only to maintain the same problem with force closes. Note I was going to create a current backup of my system today but SU updated before I got that change. Does or is anyone else having the same problem with the new SU and if so, how did you fix it... How do you remove the SU binaries? Any help resolving this issue would greatly be appreciated... Thanks in advance~
t_reax said:
Hi everyone,
My problem began last week when I updated from the Market the latest version of SU. I tried several suggestions from other people as far as uninstalling the update that worked, but still had force close from SU. Did not know how to uninstall the biraries associated with this app. Luckily for me I had a backup of my system fromJuly of this year and had to resort to using that in order to fix all the force closes generated by SU 3.05. After restoring backup using ROM Manager from that date to the older, but more stable SU (2.3) I think, I had to d/l all updates again fro my apps (time consuming). I went to the Market and unchecked (allow autmatic updating) for SU, needless to say it updated regardless. Also, since it went ahead and updated on it's own and a message was in my notication bar saying (SU binaries out of date) I manually updated them also. Force close city... I did not have this with SU 2.3, but now, nothing but. ROM Manager, Root Explorer, ShootMe etc... I went to settings/applications/manage applications/all/and selected SU and clicked on the command button to remove all updates for this app, rebooted, went back to the same path and clicked on clear cache, rebooted again only to maintain the same problem with force closes. Note I was going to create a current backup of my system today but SU updated before I got that change. Does or is anyone else having the same problem with the new SU and if so, how did you fix it... How do you remove the SU binaries? Any help resolving this issue would greatly be appreciated... Thanks in advance~
Click to expand...
Click to collapse
I am having the same problems with the SU updates; causing me problems with other apps, such as SetCPU and Busybox.
I had to flash to an older recovery and everything works fine, until updates are requested.
I dont know what else to do other then flashing back to a previous recovery.
http://themikmik.com/showthread.php?9024-Superuser-App-Force-Closing&p=128014&viewfull=1#post128014
Clear app data, uninstall, install 3.0.2 from link above ( or anywhere else you want to download it from)
Worked like a charm for me.
Auto updating for SU
After restoring to a previous date prior to the SU market update. I manually updated all of my apps for the exception of SU. I'd say about 30 or so minutes of d/ling and installing. I did the manual install specific to NOT installing SU and UNCHECKED the "Allow Automatic Update" for this app, rebooted and went back to the Market and double checked that the auto update for this was unchecked, still during the night it updated away? I just finished running ROM Manager "Fix Permissions" rebooted and still have the same problem. I can always go back and do a system restore /w RM and update all of my apps, but even with the auto update unchecked, it will re-install the update. Also, tried SU Update Fixer, no good. Says "No problems detected"... Beats me?
Thanks Namtaru... I installed the 3.02 apk file and so far no problems. Do you know how to stop this file from updating to the 3.05 version? I had "allow automatic updating" at the markert unchecked earlier, but someway, it updated anyhow...
I had the same problem. I uninstalled, installed fixed permissions in recovery and finally I cleared data on everything that used su including su that seemed to fix it I hope hadn't fc since
---------- Post added at 02:18 AM ---------- Previous post was at 02:10 AM ----------
Sorry for the confusion. I am still using the 3.0.5 version. The clearing of the data on everything that uses su including su is what did the trick for me
Thanks for the reply donaldanttila... Right now I am good using 3.02... I'll definitely keep this in mind should I need to update to 3.05 or it updates for me...
It is clear data not cache. You are welcome
Yup, that's right, l8r...
Related
would have just asked in :
http://forum.xda-developers.com/showthread.php?t=1142872&page=67
but i don't have enough posts, and don't want to spam a bunch of useless "cool" posts to get my count up.
Anyways,I did every thing in that topic and have CM7 running fine on my Cell South Showcase. But, i don't seem to have root access superuser is there but seems to do nothing. i tried checking via the terminal with just a "su" command and got nothing. Tried Superoneclick (my go to rooter for awhile) and it just hangs at "looking for device" . and, Z4 seems to not work with 2.3.4 phones.
So is there any fix to this, or have i just hit some crazy bug?
I have seen some people allude to changing the kernel, but the last time i tried to upgrade/change the kernel on this phone i had to save it via odin
Don't you HAVE to be rooted in order to run cm7?
i know, it breaks all logic
i just know i cant grant superuser to anything, busybox installer says it isnt rooted, and Titanium cant do anything
thenumber5 said:
i know, it breaks all logic
i just know i cant grant superuser to anything, busybox installer says it isnt rooted, and Titanium cant do anything
Click to expand...
Click to collapse
Clear data on superuser app and/or uninstall/reinstall it.
Ah,I see.. yes, try above. If no. Maybe wipe and reflash?
ok cleared the data, did nothing
can you ever uninstall/reinstall superuser?
thenumber5 said:
ok cleared the data, did nothing
can you ever uninstall/reinstall superuser?
Click to expand...
Click to collapse
Yup just an app
Also:
i have already flashed via Odin back to stock once and did the whole CM7 flash again from a fully clean rom
ok, Flashed Superuser 3.0 beta 3
no go, says my SU binary is out of date, and the app crashes when it tries to update it
checked my bin and xbin, both have a "SU" file in them
in terminal when i CD in to both folders and try to run "SU" i get an error that looks like it is trying to relocate a library and failing to do so
Can i just download the new SU binary my self and manual drop it in to the folders?
well that didnt work, cant modify anything in the system folder so i cant delete that old "SU" and replace it with the one from the superuser 3.0 apk
LOL
well i got it to let me replace the SU in /bin but not in /xbin
so now i got some half confused phone, i can grate Superuser "superuser" but when it tries to update or do any thing the log says "gaining root access....fail"
i still dont know how i have have a CM7 phone that by it very nature is rooted that thinks it is not rooted
ok for anyone who cares, i just gave up flashed via odin back to stock and tried the MIUI port, worked great once i fangled MMS in to working again
I had a similar problem, at which point I grabbed stericson's busybox app from the market which allowed me to flash a working busybox which after a reboot or two and running the installer again fixed me up..there is an app called root checker that can give info on su, superuser.apk, and busybox installs
I am almost positive that when I used jrummys busybox installer our killed root access on my phone. I had superuser.apk but without busybox it was rather useless as no apps could get root. the fix was flashing busybox 1.19.0 and leaving it in xbin and letting the app do its thing once I had rebooted.. then I rebooted again and everything was fine! after bring rooted for so long I don't think I could function without it!
for others out there, my experience has been this: stay weary of the jrummy busybox installer...its never given me anything but problems...and honestly unless busybox is borked, or ya have a damn good reason to upgrade or downgrade my suggestion is to leave it! the potential problems that can arise (for me every time, using jrummy's version..3 times) can be a pain!
Sent from my SCH-I500 using XDA Premium App
i had the same issue but dont recall if it was CM7 that did it or not but i think it was.
i had to completely blow out the phone and start from scratch.
if i recall, CM7 uses a different version of SuperUser and it just want bonkers on me but completely blowing everything out reformatting and everything seemed to work.
If you're on CM7 already, you should be rooted. If not, try SuperOneClick (Google).
Hi Guys.
I'm a noob trying to root my Chacha. This phone is a parrallel import, language options are Singapore English and Thai, the plug is a euro 2 round pin and it was unlocked for carrier.
I bought an XTC clip and S-off is done. So far so good.
Then I followed this guide here: http://forum.xda-developers.com/showthread.php?t=1184118
But when installing Titanium backup (with the intent of removing facebook etc) I get the message that Titanium cannot get root access. Usually preceded by a superuser error and forceclose or report options.
Typing "su" into a terminal window gives me "permission denied".
So I went back to the very good guide here: http://forum.xda-developers.com/showthread.php?t=1184118
and I noticed I get the following messages when installing PH06img.zip. "No image" followed by "no image or wrong image".
Any ideas?
Hmm, you have stopped reading the thread after the first two posts.
There is a problem with superuser (the application itself is buggy). Go to Market and update superuser to latest version. That should fix everything.
Otherwise you'll have to use the complicated method (re-flash stock, reinstall CWM, superuser, start superuser, start Titanium).
Superuser has updated itself several times (it comes up with a random, "that was cool, do it again" loop) and ends up on version 3.0 (binary).
But that doesn't seem to help. I'm still getting (process com.noshufou.android.su) has stopped.
Titanium still tells me it can't acquire root privilieges as well.
I've tried clearing the app data to fix the force-close but with no success.
Is there a walk through for the complicated method? TIA.
Is SU 3.02 or 3.04 worth a try?
Yeah, that's the version. Not only the binaries, the application itself needs updating. Get the latest one from market.
Haha, I have it. After 12 hours.
Superuser 2.6.3 worked. I found the files here: goo-inside.me/superuser/
The latest version is no use at all. I had been trying with 3.0.5
Weird. 3.0.5 Should work fine.
Superuser is a GREAT app but latest update is horrible. Blocks all rooted access apps and causes major forces closes and freezes. I emailed the developers with NO reply. Had to move Su to my SD card and uninstall it entirely. Guess its a waiting game now.
Sent from my EVO 4G running R3CHARED ROM using XDA Premium App
Am I the only one with fully functional superuser? I've set it to auto-allow access from preferences.
Alex, which phone do you have? Do you have access to Market, Titanium, spare parts etc......?
Sent from my EVO 4G running R3CHARGED ROM using XDA Premium App
It is very strange indeed.
I tried the 3.0.5 version install about 5 times over 8 hours. Interspersed with trying everything else I could google up. No luck, same force-close result each time.
Then I started trying 3.0.4 and 3.0.2 with no luck, eventually I found in that very long SU thread a reference to 2.6.3. So I found it on goo.inside.me and it worked.
Is the anyway that someone knows of on how to stop autodating from the market for SU? I had 3.05 installed but uninstalled and installed the SU 3.02.apk and for the moment, no problems... I have removed 3.05 over the week end and went to the market and unticked the "allow automatic updatiny"... double checked twice to make sure it was not checked and somewhere between then and this morning it updated automatically anyway. I keep all of my apps updated, but this is one that I don't want updated until and newer version or the bugs are removed from this one. Question: can anyone tell me how to stop SU 3.05 from updating even though "allow automatic updating" in NOT checked? Thanks!
I had the same thing happen. I am positive I unchecked it, restarted rechecked it, the auto update was still unchecked. Then it decided to do the update anyways.. I found that odd. I just uninstalled the updates again to make sure I don't end up with the Force Close issue again. Auto updates is unchecked again, see what happens...
Download an older, working copy to your SD card. Uninstall 'su' from the Market. Now, install the copy from your SD card. There will be no link to the Market this way and therefore no auto-updating.
hallstevenson said:
Download an older, working copy to your SD card. Uninstall 'su' from the Market. Now, install the copy from your SD card. There will be no link to the Market this way and therefore no auto-updating.
Click to expand...
Click to collapse
I want to protect myself from this issue. How would I download an older working copy and how do I install it from my sdcard?
hallstevenson said:
Download an older, working copy to your SD card. Uninstall 'su' from the Market. Now, install the copy from your SD card. There will be no link to the Market this way and therefore no auto-updating.
Click to expand...
Click to collapse
The first install of SU on my phone was through a downloaded zip and installed while in recovery, when I did revolution. It automatically linked itself to the market somehow. My auto update is still unchecked so all is good for now. Not sure how it linked itself, and auto updated.
My copy of "su" was also installed similarly, via recovery (following revolutionary.io's instructions). I see no indication that it is linked to the Market though. When I look at "My Apps" in the Market, it's not listed.
My version is "Superuser v3.0-beta3 (33)".
Mine also installed through revo but it is listed under my apps - in fact it is listed as wanting an update.
If you have Titaniumbackup Pro you could try severing the market link that way.
How specifically?
After auto updating last week to SU 3.05 was nothing but a pain with all the fc's... So I followed the suggestions of another member of this forum and uninstalled the update. D/led SU 3.02 and placed it on my SDcard and installed com.noshufou.android.su-3.02.apk on 10/17/11... Worked great for almost 2 completed days. Not 1 FC's... "Allow automatic updating" was NOT checked. Re-booted and checked again, NOT checked... About 30 minutes ago I pulled down the "notification bar" and SU along with 3 other apps had been "Successfully updated"? How in the **** did that happen. This **** is getting old... After uninstalling the auto updated 3.05 and manually installing the 3.02.apk file, and without a doubt in my mind that "allow automatic updating" for SU was NOT checked. What is allowing the SU 3.05 (FC City) to update from the market? I might add that whenever I uninstalled the 3.05 update I was left with SU 2.3.6.3 at that point I used Root Explorer to install the 3.02.apk, ran ROM Manager "fix permissions" and for several days the market didn't auto update and my system ran fine. Unchecked "allow automatic update" for SU it was pushed to my phone and now I'm back to square one. Why the **** is android market ignoring this and pushing the SU update anyway? Is there any way that anyone knows of to stop or prevent SU 3.05 update from being pushed to my phone without my permission? Thanks!
Hey guys and gals,
I've got a 7.7 on stock ROM rooted using the original root method the day I purchased the tablet. I've been using my tablet happily for over a month now.
Unfortunately, late last night I opened up Google Play and started updating all my apps, including Busybox by stericson. There was a new busybox version out (1.20.1) and I decided to install it using "Smart install." I'm not sure if it tried to install to /system/bin or /system/xbin but after the install I saw the app give me an error message explaining that the install was unsuccessful. Anyways, now a lot of my root-requiring apps including Titanium Backup Pro is not functioning at all. It seems that my BusyBox installation is corrupt.
I tried using BusyBox Pro by stericson to uninstall but the corrupt busybox seems to have prevented a proper uninstall, so it still lingers. I downloaded JadeEyedWolf's root.zip from his pinned "Root" post which includes SU & BusyBox thinking that installing the root.zip from CWM Recovery would over-write the corrupt busybox. After flashing I rebooted the tablet and I still got the same corrupt busybox issues.
Anyone have any suggestions?
Thanks!
Edit: The corrupt busybox causes the Wifi to show Error when I try to turn on the radio. Not that internet is vital in repairing the tablet, but I've worked around it by tethering Bluetooth internet off of my OG HTC Evo 4G. It's strange though - I can peruse websites and view the items in the Google Play Store but it will never actually download, though the "Downloading --- " bar does display.
I had the same problem, stock rom as well. If you check the reviews for Stericson's Busybox on Google Play, the two top ones a few minutes ago both mentioned the same issue.
Trying to root again and reinstalling Superuser didn't help, neither did a factory reset (manually salvaging settings and data was a pain too).
Re-flashing the original rom fixed it, following the guide at http://forum.xda-developers.com/showthread.php?t=1469635
I switched to JRummy16 Busybox installer and it seems to work.
Surprising that no one else here mentioned the problem ...
Try this fix.
To be more specific: BusyBox installer 8.0 replaces /system/bin/sh and /system/bin/ash binaries. I don't have any idea why would it do that (considering that I specified /system/xbin as an install folder), but this quick fix restores original ash binary (and sh as a symlink to it).
Installer 8.1 and above has this bug fixed.
Had the same problem with busybox and had to re-install the rom. What does this fix do?
Sent from my GT-P6800 using xda premium
Already answered, see post above.
Deleted
Sent from my GT-P6800 using xda premium
Too late for me to try it, but thanks the same
ginkage said:
To be more specific: BusyBox installer 1.20.1 replaces /system/bin/sh and /system/bin/ash binaries. I don't have any idea why would it do that (considering that I specified /system/xbin as an install folder), but this quick fix restores original ash binary (and sh as a symlink to it).
Click to expand...
Click to collapse
Thank you so much it works well now! You're a life-saver ginkage. Should I keep the stericson busybox 1.20.1 original install or should I use the busybox installer to install a fresh copy of 1.20.1 in /system/xbin?
Thanks again!
Thank you so much it works well now!
Click to expand...
Click to collapse
That's why we are here.
Should I keep the stericson busybox 1.20.1 original install or should I use the busybox installer to install a fresh copy of 1.20.1 in /system/xbin?
Click to expand...
Click to collapse
Personally I always use /system/xbin, so that some custom kernel (like CWM) could use /system/bin if it wanted to.
BTW, the BusyBox installer bug was fixed in version 8.1, and current version is 8.2, so you should update it anyway. I was wrong to mention "1.20.1" version. Post edited.
Hi guys,
First of all, I want to apologize sincerely for the bug that my application introduced in 8.0. I didn't catch the bug because my device wasn't affected by the bug.. (I always test my app myself before releasing..yet I still miss things due to devices file structure being so different.)
At any rate, the bug was that the application symlinked all applets to Busybox. Normally, this is done if you use smart install and change the settings manually. By default smart install will not overwrite applets that are not already symlinked to Busybox.
This was not a problem with Busybox 1.20.1 but was a problem with my application and how it performed the install.
Again, I am very very sorry that this has occured, as a result I am scouring the web trying to find people with the issue and help them resolve it.
If you have this problem, it can easily be fixed by reflashing your current rom. you do not have to wipe or clear any data. Once this is done, you can download my installer, version 8.1 or greater and upgrade busybox as normal.
Please let me know if you guys have any questions.
Best Regards,
Stephen - Stericson
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Deleted
I too had the same situation, updated busybox then noticed something was awry when hidebar wouldn't work. My issues go way beyond broken root and WIFI, I've also been getting constant reboots. I was just about to re-install the stock rom until I read about the possible udate.zip fix. I'm very interested in how to apply the zip (I don't have CWM) being that i do extensive customization (with no backup, I know, I know) and I'd hate to re customize everything again. If I can get things right the first thing I'll do is install CWM and perform a nandroid backup.
ninpo said:
I too had the same situation, updated busybox then noticed something was awry when hidebar wouldn't work. My issues go way beyond broken root and WIFI, I've also been getting constant reboots. I was just about to re-install the stock rom until I read about the possible udate.zip fix. I'm very interested in how to apply the zip (I don't have CWM) being that i do extensive customization (with no backup, I know, I know) and I'd hate to re customize everything again. If I can get things right the first thing I'll do is install CWM and perform a nandroid backup.
Click to expand...
Click to collapse
you don't need CWM, just copy the fix onto external storage card,enter recovery (PWR + Vol. up Buttons) and apply the update from there. just fixed my tablet this way
regius said:
you don't need CWM, just copy the fix onto external storage card,enter recovery (PWR + Vol. up Buttons) and apply the update from there. just fixed my tablet this way
Click to expand...
Click to collapse
A thousand thanks kind sir, I'm back in business, that was pain free
---------- Post added at 07:29 PM ---------- Previous post was at 07:27 PM ----------
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Thanks for posting this, I'm in love with my 7.7 once again.
Appreciate the response stericson. I had purchased your Pro version but even after I fixed the uninstall failed and it also did not detect superuser permissions even though SU gave a notification that Busybox Pro was granted superuser. All other root-requiring apps work. Had to refund the Pro purchase though
No problem. there seems to be an issue with the application detecting root sometimes, that's why you can still try the install.
I'm looking into this issue, it just started showing up so I am not sure what is going on.
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Really appreciate this fix. On the verge of wiping out everything....
But decide to see if its busy box since its the last thing i install before all this happens....
Just to note that uninstall busybox also doesnt solve the issue...
so need to fix.
I had a lot of problems with root permissions not being granted by Superuser app. Recently I have tried SuperSu from the market and uninstalled original Superuser app (important to follow the instructions for the App! ).
My main problem was that ntfssd was not granted root permissions at startup, so I had to start it again manually. With SuperSu it is no problem. Also I use Busybox and successfully updated to the latest binary recently.
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Thank you so much for that, I had been driven crazy and had also gone through a factory reset to try and get my device back working, to no avail. Can I ask where you got the ash you're including here? It worked for my Samsung Galaxy Tab 7 Plus, on 3.2, but is it a generic enough file that it can be dropped on nearly all Android devices without any issues arising?
I only ask out of curiosity and understanding the system more.
I know there's a dedicated SuperSU thread but being a newbie on this forum I cannot post there.
I have Teclast P78HD tablet (A31 and Android 4.4.2) which I have rooted using Kingo. There is no custom recovery available for this model, AFAIK, so zip option is out of question I think. Kingo installed SuperSU 1.9.1 which does work, but as Play offered an update I accepted it, got 2.0.1. A big mistake.
The system still works, it prompts to grant root access when an app needs it. But I cannot run the SuperSU app anymore, it asks if I want to update. If I select yes after a while it fails and tells to reboot and try again. Which of course gives the same result. Selecting cancel closes the program. Uninstalling the update returns the system back to working 1.9.1. I have tried also Settings / Cleanup / Reinstall and Settings / Cleanup / Switch superuser app but both fail similarily. I also tried to replace the APK in /system/app using ES File Explorer but this method also makes an app to ask for update.
Any ideas how to update SuperSU on this tablet? Maybe I should just forget the problem and use the current one, but it is somewhat old and the changelog lists many, many changes. Plus Play keeps offering an update which is somewhat annoying
Boffortes said:
I know there's a dedicated SuperSU thread but being a newbie on this forum I cannot post there.
I have Teclast P78HD tablet (A31 and Android 4.4.2) which I have rooted using Kingo. There is no custom recovery available for this model, AFAIK, so zip option is out of question I think. Kingo installed SuperSU 1.9.1 which does work, but as Play offered an update I accepted it, got 2.0.1. A big mistake.
The system still works, it prompts to grant root access when an app needs it. But I cannot run the SuperSU app anymore, it asks if I want to update. If I select yes after a while it fails and tells to reboot and try again. Which of course gives the same result. Selecting cancel closes the program. Uninstalling the update returns the system back to working 1.9.1. I have tried also Settings / Cleanup / Reinstall and Settings / Cleanup / Switch superuser app but both fail similarily. I also tried to replace the APK in /system/app using ES File Explorer but this method also makes an app to ask for update.
Any ideas how to update SuperSU on this tablet? Maybe I should just forget the problem and use the current one, but it is somewhat old and the changelog lists many, many changes. Plus Play keeps offering an update which is somewhat annoying
Click to expand...
Click to collapse
uninstall supersu and try this one. some people have issues with supersu and have found superuser to work correctly.