If you noticed, Superuser updated to 2.3 - make sure you do an nandroid backup before you attempt to apply it. I was able to apply it, and when I attempted to launch the application, it FCed on me. I was able to grant ROM Manager SU rights, but I just wanted everyone to be aware. You can see the original Superuser 2.3 thread here.
I did a nandroid restore and got rid of it since it was FC like mad.
SU 2.3.1 is up, and so far seems to be working without any issues.
maltzer said:
SU 2.3.1 is up, and so far seems to be working without any issues.
Click to expand...
Click to collapse
FYI, I am also using 2.3.1 without problems. The only crash I noticed was when you checked the log before actually trying anything that used superuser it caused a FC. After using a couple of root apps, I can check the log without a crash.
Can I flash the 2.3.1 over the 2.3 version? I can't find any confirmation that this is the right procedure to update su.
Can't even get this to install properly on the Captivate. Installation aborted every time in recovery mode.
When I try to install from the market, I get package not signed properly error. What is the correct procedure to update your SuperUser.apk file?
might be helpful
rajendra82 said:
When I try to install from the market, I get package not signed properly error. What is the correct procedure to update your SuperUser.apk file?
Click to expand...
Click to collapse
if you go to the g1 thread and go to themes and ****....they got the apk for free......just gotta sideload it...ya digg
oh yeah it works perfect on my captivate....
I have su 2.3.1 and it works perfectly i upgraded it from market had 1.8 before i think on one of the one click root packages. No issues at all though and im back on stock rom right now.
Related
//EDIT: Please delete this thread. Titanium Backup installed BusyBox for me after I clicked the "Problem?" button. Sorry!
**Skip to the other asterisked line to skip the long story**
Last night I decided "(vulgarity here) AT&T!" and decided to load FroYo myself.
After reading for hours (on top of reading I've been doing for a few weeks) it seemed it was easier to root on 2.1, then update to 2.2.
I rooted, then installed 2.2 only to find out I was no longer rooted when I tried restoring my apps with MyBackup Pro. After tons of searching and trying 3 "one click" style rooting programs, many times over, the SuperOneClick method worked, only after I did the shell root, and then root button.
Awesome! I had a rooted 2.2 captivate! Restoring my apps with MyBackup Pro let me knew it worked, and then I was also able to install a non-market foreign language pack for the AnySoftKeyboard app. I also installed the MarketAccess app and I'm running the T-Mobile US code, so I'm pretty sure I've got root.
Tonight I wanted to get rid of all the AT&T garbage still on the phone, and a guide I found told me that Titanium Backup would allow me to do so (still not sure if it can all be done from the phone though). I downloaded and installed Titanium Backup, opened it up, clicked the button to allow SuperUser, but I get an error message:
Sorry, I could not acquire root privileges. This application will *not* work ! Please verify that your ROM is rooted and includes BusyBox, and try again.
Pretty sure I'm rooted, I am assuming I only require BusyBox be on the phone?
**I was under the impression that rooting and BusyBox was the same thing, or went hand-in-hand, one needing the other.
After now 4 more hours of searching, I can't seem to find a guide that only installs BusyBox, and I'm hesitant to try any of the Root and BusyBox in one methods for fear of the root not working and potentially messing something up.
I found one posting that requires a bunch of commands, but I have no idea where to do them from/in or what to do with the phone.
If anybody could link me to or tell me how to install BusyBox that would be awesome! I am rooted on FroYo. I have the drivers installed. I have DroidExplorer installed. Not sure of anything else that may have come in the .zip files I downloaded that might be installed, so assume only the drivers and DroidExplorer and installed.
Thanks in advanced!!
Busybox is an app on the market, download, open app, install, profit
Sent from my GT-I9000 using XDA App
rcvd an orange branded DHD yesterday but was able to run Visionary 14 and run temproot then permroot as device wasn't upgraded.
Applied jkoljo easy one click radio off, sim unlock and super cid thing with all looking good with radio s-off confirmed. Also from terminal emulator I have #su access.
Via clockwork Mod installed a modaco custom rom - all looking good.
My problem now is that titanium backup says it could not acquire root privileges?
I have tried downloading a clean busybox but it fails on the verify stage. Sometimes I get error: application superuser (process com.noshufou.android.su) has stopped unexpectedley.
I've also tried clearing data for both TB and SU from settings > apps > manage apps... no good.
Any ideas?
beaverHausen said:
rcvd an orange branded DHD yesterday but was able to run Visionary 14 and run temproot then permroot as device wasn't upgraded.
Applied jkoljo easy one click radio off, sim unlock and super cid thing with all looking good with radio s-off confirmed. Also from terminal emulator I have #su access.
Via clockwork Mod installed a modaco custom rom - all looking good.
My problem now is that titanium backup says it could not acquire root privileges?
I have tried downloading a clean busybox but it fails on the verify stage. Sometimes I get error: application superuser (process com.noshufou.android.su) has stopped unexpectedley.
I've also tried clearing data for both TB and SU from settings > apps > manage apps... no good.
Any ideas?
Click to expand...
Click to collapse
if you flash your backup (you did make one right?) I assume root and SU are still intact, if so possibly a bad flash of modaco, try reflashing or flashing a different ROM and report back
I did make a backup but hadn't tried re-flashing. I'm giving it a go now.
OK so dropped into clockword mod recovery, cleaned dalvik, wiped fatory reset and cache then re-flashed modaco rom.
All installs fine however still have the force close when trying to run titanium backup and get the error can't get root privilege.
SU reports it is up to date but trying to run su in terminal emulator gives the com.noshufou.android.su stopped message.
Apart from not being able to restore/backup using TB at least I can still install ROM.
The root problem is in the rom you are using, try for example Android Revolution 2.0.3. Some 1.72 based roms have problems with superuser.
try re-installing updating Superuser via the market see if that helps as it does sound like an issue with Superuser itself
ghostofcain said:
try re-installing updating Superuser via the market see if that helps as it does sound like an issue with Superuser itself
Click to expand...
Click to collapse
Thanks but that doesn't work.
beaverHausen said:
Thanks but that doesn't work.
Click to expand...
Click to collapse
which MCR are you using? is it a pre-baked or cooked one?
A baked one on the r2.
beaverHausen said:
A baked one on the r2.
Click to expand...
Click to collapse
appears to be a known issue with MCR r2 a possible work around is after a FC run superuser yourself and then the app might run normally if you try launching it again.
Edit: on further investigation, there is a patched SU available over on the G2 Forums apparently it's and issue on all 1.72.x.x Sense ROMs, wouldn't know personally as I don't use Sense
ghostofcain said:
Last edited by ghostofcain
Click to expand...
Click to collapse
Totally off topic, but going off your name, you're a fellow NMA fan?
iridium21 said:
Totally off topic, but going off your name, you're a fellow NMA fan?
Click to expand...
Click to collapse
Not 'alf mate
ghostofcain said:
on further investigation, there is a patched SU available
Click to expand...
Click to collapse
Cheers buddy, I ran the patch and now have Titanium Backup, Clockword Mod and Terminal Emulator all with SU!
I have made this for people that have suddenly lost root access the installer contains
Superuser Application < Latest
Su Binary < Latest
Root Browser < Latest
Root Browser Thread http://forum.xda-developers.com/showthread.php?t=1338582
Busybox < 1.19.0
i will be adding updates as they come out so i will be updating busybox tomorrow to 1.19.3 i have tested this and it works a charm
Download v1.0.0.1
http://www.mediafire.com/?cl89ngtk4qrv1uh
More to be added like gapps installer and tweak installers
Download Link added
cool! Will try when I go back home on tuesday
thanks eoghan i just realized when i was about to caligrate SDSL v2 that i lost root, and that mite be the reason im getting fc's and busybox doesnt want to install any version, how this happent with murki's versions and others i never had this problem.
ps: btw how does this work?
EDIT: i plugged my phone run the app as admin and no admin and all the times said permission denied, already tried twice and once being in recovery . im tired of all the issues i had had so far with sdsl v2 ill go back to v1. btw also tried Z4root with no success
Veronica
Nice program. In which language have you made this? I suppose it was made in Visual Studio, or am I wrong?
lavero.burgos said:
thanks eoghan i just realized when i was about to caligrate SDSL v2 that i lost root, and that mite be the reason im getting fc's and busybox doesnt want to install any version, how this happent with murki's versions and others i never had this problem.
ps: btw how does this work?
EDIT: i plugged my phone run the app as admin and no admin and all the times said permission denied, already tried twice and once being in recovery . im tired of all the issues i had had so far with sdsl v2 ill go back to v1. btw also tried Z4root with no success
Veronica
Click to expand...
Click to collapse
god this should have worked because all custom rom allow the adb shell command rooted or not it soulds like the rom didn't install correctly.
also it made using notepad++ to make the bat file
lavero.burgos said:
thanks eoghan i just realized when i was about to caligrate SDSL v2 that i lost root, and that mite be the reason im getting fc's and busybox doesnt want to install any version, how this happent with murki's versions and others i never had this problem.
ps: btw how does this work?
EDIT: i plugged my phone run the app as admin and no admin and all the times said permission denied, already tried twice and once being in recovery . im tired of all the issues i had had so far with sdsl v2 ill go back to v1. btw also tried Z4root with no success
Veronica
Click to expand...
Click to collapse
Z4root uses old root exploit that was patched in 2.2.1+, GingerBreak will work also Boot into recovery and mount system and connect then use this app
ill have a look at using gingerbreak aswel in the installer after it tests if root can be used without gingerbreak im currently making a new installer for google apps link market, youtube etc all the latest as possible
eoghan2t7 said:
ill have a look at using gingerbreak aswel in the installer after it tests if root can be used without gingerbreak im currently making a new installer for google apps link market, youtube etc all the latest as possible
Click to expand...
Click to collapse
That would be very Usefull, Instead of having to search for them,
For guys who don't know where the latest are go onto Cyanogenmod's website, they are all there
i will be putting the lastest market and music in it but will give the user the choice to use the old music app
Apologies if this is blindingly obvious, but I've googled and searched and have found a lot of conflicting information this, so bear with me:
I went through the Moto bootloader unlock process for my Rogers Moto X and when I boot into fastboot it says it's unlocked. I then installed SuperSU and it seems to be working when I launch apps that require SU access. And some sites say if I'm on 4.4.3 it's impossible to make /system writeable. Basically, I'm still unable to install stuff that writes to /system like Busybox.
I've read about how /system is write-protected but haven't figured out how to actually fix this - some posts say start in recovery and I should be able to write to /system, others say it should work after I've gone through the Moto bootloader unlock process.
Can anyone here help a rsomewhat-newb get this sorted?
neil.io said:
Apologies if this is blindingly obvious, but I've googled and searched and have found a lot of conflicting information this, so bear with me:
I went through the Moto bootloader unlock process for my Rogers Moto X and when I boot into fastboot it says it's unlocked. I then installed SuperSU and it seems to be working when I launch apps that require SU access. And some sites say if I'm on 4.4.3 it's impossible to make /system writeable. Basically, I'm still unable to install stuff that writes to /system like Busybox.
I've read about how /system is write-protected but haven't figured out how to actually fix this - some posts say start in recovery and I should be able to write to /system, others say it should work after I've gone through the Moto bootloader unlock process.
Can anyone here help a rsomewhat-newb get this sorted?
Click to expand...
Click to collapse
You flashed the latest version of TWRP custom recovery?
samwathegreat said:
You flashed the latest version of TWRP custom recovery?
Click to expand...
Click to collapse
Think so - this was the image file I used: twrp-2.6.3.1-ghost-4.4.img
neil.io said:
Think so - this was the image file I used: twrp-2.6.3.1-ghost-4.4.img
Click to expand...
Click to collapse
That might be the issue. It might not be compatible with 4.4.3
Try this one: http://techerrata.com/browse/twrp2/ghost
Also, which version of SuperSU are you using? There was a new one released recently. Find it here: http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip (Flash it from within TWRP - install ZIP)
Please update, and then advise whether or not your issue is resolved.
EDIT: Also, make sure you are using the "stericson" busybox variant. Others have been reported to cause issues.
Thanks a lot for the fast responses - really appreciated.
I redid recovery using the version you linked to and also reinstalled SuperSU (I was using the current version already). When I try to install Busybox using the Stericson version as you mentioned I get an immediate error that it wasn't able to open a shell w/ root access. Running Root Checker tells me that root access is working, so I'm not sure what I've missed.
Again, many thanks!
neil.io said:
Thanks a lot for the fast responses - really appreciated.
I redid recovery using the version you linked to and also reinstalled SuperSU (I was using the current version already). When I try to install Busybox using the Stericson version as you mentioned I get an immediate error that it wasn't able to open a shell w/ root access. Running Root Checker tells me that root access is working, so I'm not sure what I've missed.
Again, many thanks!
Click to expand...
Click to collapse
Open SuperSU, and check to see if busybox is listed under apps. There should be a green "#" symbol next to it. It SHOULD have prompted you to grant access to it, so perhaps at some point you either denied the su request, or didn't see it. If you see a RED "#" symbol, tap it, and change to "Grant".
Please advise...
It is, and it did have a green # beside it. I tried removing it and it requested permission as expected, but still failed.
I can't seem to get anything to install to system - Adaway also fails, for example.
neil.io said:
It is, and it did have a green # beside it. I tried removing it and it requested permission as expected, but still failed.
I can't seem to get anything to install to system - Adaway also fails, for example.
Click to expand...
Click to collapse
I would suggest a full return to stock (follow the return to stock thread in the general sub-forum). This is not normal....
You appear to be using the XT1053, correct? Take caution to NOT downgrade or you could end up with a brick.
Flashing the entire stock SBF can actually fix a corrupted filesystem - this is my best guess at what might fix your issue.
samwathegreat said:
Flashing the entire stock SBF can actually fix a corrupted filesystem - this is my best guess at what might fix your issue.
Click to expand...
Click to collapse
Thanks again for the help. I just flashed the stock SBF and that seems to have fixed whatever was blocking Adaway from properly writing its hosts file, but Busybox stubbornly refuses to install. I got the permission request for SU when I launched it, but it fails just after I initiate the install. I tried changing the location to /system/bin with no luck.
Any other suggestions? I'm ready to give up for now, but it's frustrating when my Nexus 4 was so simple to set up.
neil.io said:
Thanks again for the help. I just flashed the stock SBF and that seems to have fixed whatever was blocking Adaway from properly writing its hosts file, but Busybox stubbornly refuses to install. I got the permission request for SU when I launched it, but it fails just after I initiate the install. I tried changing the location to /system/bin with no luck.
Any other suggestions? I'm ready to give up for now, but it's frustrating when my Nexus 4 was so simple to set up.
Click to expand...
Click to collapse
How did you SBF to stock? Did you use RSD Lite? Did you retain userdata, or wipe everything (suggested)?
The stericson variant installs fine for me...granted I'm on 4.4.2 (the latest for my variant).
I did NOT use smart install...just used regular install to /system/xbin (You might consider trying smart install if you haven't yet...)
Honestly, I'm out of ideas. Although the "stericson" variant is recommended, perhaps you should try another version from the market if you need busybox.
I've done extensive searches and haven't found anyone else having a similar issue - even with Moto X on 4.4.3
I gave up and used the recovery method. Really odd - it does seem like the other installer apps couldn't mount /system as writeable, but it's weird that other apps that installed to that area worked.
Anyway, thanks again!
I have 3 apps that when I try to download (after flashing a rom) that give me an "unknown error code during application install -505"
Thoughts?
I've cleared cache and data and forced stopped the play store...
I've checked to see if any folders or files are in root or in data/data and I found some and deleted but nothing. Still won't download.
CCJ22 said:
I have 3 apps that when I try to download (after flashing a rom) that give me an "unknown error code during application install -505"
Thoughts?
I've cleared cache and data and forced stopped the play store...
I've checked to see if any folders or files are in root or in data/data and I found some and deleted but nothing. Still won't download.
Click to expand...
Click to collapse
i had one that got that code. what i did to fix this is i found that app using google(not play store), installed it that way, then uninstalled it via the pkay store, then reinstalled it in the play store.
Yea I'm getting that problem with Terminal Emulator for Android by Jack Palevich. Not sure what the deal is. Aggravating since ROM Toolbox Terminal FC, and another that I've tried. Rastapop with leanKernel.
Last time that happened to me I fixed it by using Root Explorer (any file manager with root access should work tho) and deleted the "com.appname......" file from data/data partition from system root level, not SD.
Then went back to Play Store and installed fine.
via OnePlus or N5
truckroot said:
Last time that happened to me I fixed it by using Root Explorer (any file manager with root access should work tho) and deleted the "com.appname......" file from data/data partition from system root level, not SD.
Then went back to Play Store and installed fine.
via OnePlus or N5
Click to expand...
Click to collapse
I found the location, but not the app that supposedly downloaded and didn't install. App is Terminal Emulator by Jack Palevich.
saddog5523 said:
I found the location, but not the app that supposedly downloaded and didn't install. App is Terminal Emulator by Jack Palevich.
Click to expand...
Click to collapse
Look for jackpal.androidterm file?
via OnePlus or N5
simms22 said:
i had one that got that code. what i did to fix this is i found that app using google(not play store), installed it that way, then uninstalled it via the pkay store, then reinstalled it in the play store.
Click to expand...
Click to collapse
I tried that but the outsourced .apk didn't install. It said error. Tried 3 other sources. Same problem.
saddog5523 said:
Yea I'm getting that problem with Terminal Emulator for Android by Jack Palevich. Not sure what the deal is. Aggravating since ROM Toolbox Terminal FC, and another that I've tried. Rastapop with leanKernel.
Click to expand...
Click to collapse
Man I'm sorry. I know the feeling. Is yours a -505 error #?
truckroot said:
Last time that happened to me I fixed it by using Root Explorer (any file manager with root access should work tho) and deleted the "com.appname......" file from data/data partition from system root level, not SD.
Then went back to Play Store and installed fine.
via OnePlus or N5
Click to expand...
Click to collapse
Tried that. Still the problem remains.
CCJ22 said:
I tried that but the outsourced .apk didn't install. It said error. Tried 3 other sources. Same problem.
Man I'm sorry. I know the feeling. Is yours a -505 error #?
Tried that. Still the problem remains.
Click to expand...
Click to collapse
Yes, it's a -505 error. That's the only app I've had that problem with, though I don't download too many. I just want a terminal app to use with leanKernel so I can access lkconfig. I am thinking it might have something to do with me being on rastapop which is 5.0.1, what version and/or ROM are you using?
@saddog5523 I'm on euphoria beta, about to dirty flash to the latest version 1.0 off beta.
This -505 sucks...
had this happened a few days ago. had to restore a twrp backup. in mycase, it was some frozen/degreenified app
stas333 said:
had this happened a few days ago. had to restore a twrp backup. in mycase, it was some frozen/degreenified app
Click to expand...
Click to collapse
I have no twrp backup of the play store or my apps.
Strangely the download happens from the play store, it's the install that hoses up. Making me think I have some file somewhere shettin bricks on the install.
I feel like I've tried everything.
Well. My main issue was with Terminal Emulator for Android by Jack Palevich. I clean flashed the new 5.0.1 and wiped/factory reset my device. Still had the same 505 error. It was crazy aggravating. I Google'd it to see if anyone else had the same issue, and found out that it was a permissions issue: http://android.stackexchange.com/qu...deal-with-unknown-installation-error-code-505
Every time I tried to access the baked in terminal emulator within Rom Toolbox Lite, it would force close the app. I got aggravated at Rom Toolbox Lite and uninstalled it, and while I was in the play store, decided to try Terminal Emulator for Android again. This time it worked. I uninstalled Terminal and installed Rom Toolbox Lite to test my new theory, and found that the two apps do not play well with each other for some reason. Even when I try to install Rom Toolbox Lite after I already have Terminal installed, it would give me the same 505 error. Apparently I can have one or the other, which honestly makes no sense at all.
I'm guessing that error could be fixed (possibly) by uninstalling applications that have the same feature. i.e. Terminal Emulator for Android and Rom Toolbox Lite. One of the apps you have installed might be causing the error in trying to install another app. Hope this helps someone with the same issue.
@CCJ22 @simms22 @truckroot @stas333
saddog5523 said:
Well. My main issue was with Terminal Emulator for Android by Jack Palevich. I clean flashed the new 5.0.1 and wiped/factory reset my device. Still had the same 505 error. It was crazy aggravating. I Google'd it to see if anyone else had the same issue, and found out that it was a permissions issue: http://android.stackexchange.com/qu...deal-with-unknown-installation-error-code-505
Every time I tried to access the baked in terminal emulator within Rom Toolbox Lite, it would force close the app. I got aggravated at Rom Toolbox Lite and uninstalled it, and while I was in the play store, decided to try Terminal Emulator for Android again. This time it worked. I uninstalled Terminal and installed Rom Toolbox Lite to test my new theory, and found that the two apps do not play well with each other for some reason. Even when I try to install Rom Toolbox Lite after I already have Terminal installed, it would give me the same 505 error. Apparently I can have one or the other, which honestly makes no sense at all.
I'm guessing that error could be fixed (possibly) by uninstalling applications that have the same feature. i.e. Terminal Emulator for Android and Rom Toolbox Lite. One of the apps you have installed might be causing the error in trying to install another app. Hope this helps someone with the same issue.
@CCJ22 @simms22 @truckroot @stas333
Click to expand...
Click to collapse
Thanks I will have to try this tonight.
Are you running 5.0.1 ? I had this issue with an app when I first got my phone and with some research found out the problem was apparently fixed in the 5.0.1 OTA, well it fixed it for me. This is one of the changes that fixes it.
cupfulloflol said:
Are you running 5.0.1 ? I had this issue with an app when I first got my phone and with some research found out the problem was apparently fixed in the 5.0.1 OTA, well it fixed it for me. This is one of the changes that fixes it.
Click to expand...
Click to collapse
I've got 5.0.1 and am still having this issue installing GTasks. Does anyone have a solution?
carrot34 said:
I've got 5.0.1 and am still having this issue installing GTasks. Does anyone have a solution?
Click to expand...
Click to collapse
Are you running the stock ROM?
The problem is explained here in more detail. You basically have to uninstall whatever is conflicting with the app install. A logcat should be able to tell you where the conflict is.
cupfulloflol said:
Are you running the stock ROM?
The problem is explained here in more detail. You basically have to uninstall whatever is conflicting with the app install. A logcat should be able to tell you where the conflict is.
Click to expand...
Click to collapse
Thanks. Yes, I'm running the stock ROM and not rooted. It's basically just out of the box and with the 5.0.1 OTA update. The conflict is between Pure Calendar Widget and GTasks. If I uninstall one app, the other will install. But if I try to install _both_, I get the 505 error. Is there any way around this? The post you linked to says that this has been fixed in 5.0.1, but it doesn't look like that to me.
Thanks!
Alan
carrot34 said:
Thanks. Yes, I'm running the stock ROM and not rooted. It's basically just out of the box and with the 5.0.1 OTA update. The conflict is between Pure Calendar Widget and GTasks. If I uninstall one app, the other will install. But if I try to install _both_, I get the 505 error. Is there any way around this? The post you linked to says that this has been fixed in 5.0.1, but it doesn't look like that to me.
Thanks!
Alan
Click to expand...
Click to collapse
I honestly think it's something either the developers will have to work out in a new version of their app, or Google will have to fix in a new phone update. Whichever comes first. 5.0.1 was supposed to fix it, but like you and I and others have noticed, it's still a problem. You're just going to have to use one or the other for now.
so, what you're saying is we're pretty much SOL until it is actually fixed...
the thing is, google is saying they fixed it on 5.0.1
if it's not actually fixed then people who can report it, should report it...
I do not have the permissions or "prestige" to post on StackOverFlow or code.google.com to say that the bug has not been fixed...