I bought a second hand xperia play that has a superuser app so i thought i might have a rooted phone, i downloaded titanium backup to delete some pre installed games and apps but when i read more about rooted phones i decided to make the most of my phone by downloading adfree, hide it pro and rom manager but all three apps say i require root, so my questions are
1) is my phone rooted
2) how do i check to see if it is rooted
3) is it possible that i would just have to update my root
4) can you use titanium and superuser without root as the 2 apps seem to work.
Thanks in advance.
1. From the information given, yes it must be rooted.
2. Download Root Checker for free and it will let you know.
3. As far as I know, a root can't be updated. Once it's rooted, that's it.
4. It's possible to have them without root, but you have to be rooted to use them.
I hope I helped
Sent from Sony Xperia S using XDA Premium
Join my threads here and here.
Check out this [GUIDE] How to be a New User (and not a noob)
Thanks for the response, I have downloaded several root checker apps but all of them including the adfree, busybox and Rom manager seem to think I am not. I just find it strange that I have superuser and titanium that both work fine.
Persevere80 said:
Thanks for the response, I have downloaded several root checker apps but all of them including the adfree, busybox and Rom manager seem to think I am not. I just find it strange that I have superuser and titanium that both work fine.
Click to expand...
Click to collapse
Yes they my work fine, but there usage is limited, they canot access the system partition.
HTC Sensation z710e
ICS 4.0.3
Sense version 4.0
Software Sense-o-maniac v1.4
Kernel. 3.0.30 Bricked v1.4
Radio 11.68.3504
Does that mean to say there are parts of titanium that can be used unrooted.
Root binaries and the App can be updated.
While we are it, what does my app say about your root status?
Persevere80 said:
Does that mean to say there are parts of titanium that can be used unrooted.
Click to expand...
Click to collapse
Yes, you can backup all your installed apps in batch mode and restore in batch mode. You will not be able to freeze or delete system apps.
HTC Sensation z710e
ICS 4.0.3
Sense version 4.0
Software Sense-o-maniac v1.4
Kernel. 3.0.30 Bricked v1.4
Radio 11.68.3504
Related
I'm confused! I have superuser installed and as of yet no app has asked for permissions; they just work. With the exception of ROM Manager which just freezes (needs long hold on back key). On previous ROMs I've flashed, requests for permissions pop up and you allow/deny etc. I've tried using the updater from the marketplace (force closes) and updating the binary (force closes). Am not able to uninstall superuser. I've turned on/off USB Debugging, fixed permissions, almost everything else I've found on the net.
As apps are working it isn't the end of the world but I'm confused about why they are working and also slightly concerned over the security aspect of apps not asking me and just running.
Apps that work without asking include: Titanium Backup, CPU Master, NSTools, File Explorer
I9020
Matr1x 15 Kernel
Orca 1 RC-0.1 (Drew Garen/BamtauMod)
What version is it? Try flashing version 3.0.7, this was the first to work with ICS if I remember correctly.
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
Hi,
According to the app it's version 3.0.7 (41).
I should've mentioned that it's an ICS ROM, sorry.
flodb113 said:
What version is it? Try flashing version 3.0.7, this was the first to work with ICS if I remember correctly.
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
Click to expand...
Click to collapse
You sir, are awesome! Thank you for link. I installed it and now my apps are requesting permissions.
Dynamo Nath said:
You sir, are awesome! Thank you for link. I installed it and now my apps are requesting permissions.
Click to expand...
Click to collapse
Glad you're happy with it! When ICS came out, we had to wait a week (I think) for the update to make SU work properly. Great work from the dev, as always.
I have find a new supersu here
http://forum.xda-developers.com/showthread.php?p=23427715
It is working good so far. Is it possible to remove the original super user bundeled with the custom roms. Or it can get some bad effect on custom rom.
Yerp saw this back in march...see it's been updated....:thumbup:
Thx
Probably not that great. Superuser is used universally for a reason.
wayzata said:
Probably not that great. Superuser is used universally for a reason.
Click to expand...
Click to collapse
guess you know this because.....
Actual it is....but you prob installed it and ran it huh?
I have deleted the /system/app/SuperUser.apk through Root Explorer
SuperSu is working fine.
(It should only be done after installing SuperSU from the market, then run it a popup will come up asking to update binary say yes.)
Bought it a while back to support Chainfire.
wayzata said:
Probably not that great. Superuser is used universally for a reason.
Click to expand...
Click to collapse
And you would be wrong. SuperSU comes from a well respected developer (Chainfire), and was created because Superuser has some major bugs that ChainsDD still hasn't fixed - such as su crashing if Android wasn't fully booted. (This was a pain for me for CM9 work when combined with their new "don't default to root in ADB" policy. ADB not going straight to root + broken su = pain)
Most I9100 and N7000 firmware developers have switched over, and when on Touchwiz firmwares I have too. Superuser's one advantage - it's open source which is why it is in CM9, I don't believe SuperSU is.
Entropy512 said:
And you would be wrong. SuperSU comes from a well respected developer (Chainfire), and was created because Superuser has some major bugs that ChainsDD still hasn't fixed - such as su crashing if Android wasn't fully booted. (This was a ****ing pain in the ass for me for CM9 work when combined with their new "don't default to root in ADB" policy. ADB not going straight to root + broken su = pain)
Most I9100 and N7000 firmware developers have switched over, and when on Touchwiz firmwares I have too. Superuser's one advantage - it's open source which is why it is in CM9, I don't believe SuperSU is.
Click to expand...
Click to collapse
Would you recommend using SuperSU over superuser in CM9?
stratatak7 said:
Would you recommend using SuperSU over superuser in CM9?
Click to expand...
Click to collapse
Not in CM9
Entropy512 said:
Not in CM9
Click to expand...
Click to collapse
so for any ROM other than cm9, you recommend it? and if so, how would you recommend we install? i assume we need to install it first, then update, then delete the "regular superuser"?
TDuran said:
so for any ROM other than cm9, you recommend it? and if so, how would you recommend we install? i assume we need to install it first, then update, then delete the "regular superuser"?
Click to expand...
Click to collapse
Just for kicks, I installed it and tried it. This probably isn't the "proper" method and you could possibly mess something up but anyway here is what I did: 1. Delete superuser.apk from your app folder in /system. 2. In Play store download superSU and install. It will ask you to update binaries. Do it and you should be golden.
**Delete files at your own risk** I used Root explorer and make sure you mount app folder as r/w before deleting and then put it back to normal when you're done.
failed... on galnet miui.. time to reinstall old SU
I have flashed the infusion kernel and old super user came back again. It means rooted kernel got Super User pre-packed with them
Working great for me on the infuse and the nook. Both cm9. CF is a great dev.
Sent from my NookColor using Tapatalk 2
ndhanta said:
I have flashed the infusion kernel and old super user came back again. It means rooted kernel got Super User pre-packed with them
Click to expand...
Click to collapse
Yes. Many Rom devs include SU.
Sent from my Emancipated Infuse having Communion.
ndhanta said:
I have flashed the infusion kernel and old super user came back again. It means rooted kernel got Super User pre-packed with them
Click to expand...
Click to collapse
This is one of the reasons I removed autorooting from my kernels.
In my case, I just flashed the CWM-flashable SuperSU package in CWM - It will automatically remove legacy Superuser I believe.
I personally would like to see it in CM9 (or at least the Superuser problems that caused Chainfire to write SuperSU fixed) - but I believe that the free version of Superuser is open source while SuperSU is not (I could be wrong about this).
I am not getting any source information of SuperSu. It seems closed source.
Entropy512 said:
This is one of the reasons I removed autorooting from my kernels.
In my case, I just flashed the CWM-flashable SuperSU package in CWM - It will automatically remove legacy Superuser I believe.
I personally would like to see it in CM9 (or at least the Superuser problems that caused Chainfire to write SuperSU fixed) - but I believe that the free version of Superuser is open source while SuperSU is not (I could be wrong about this).
Click to expand...
Click to collapse
SuperSU is free on the market (there is also a $$ pro version). I'm seeing the same thing ndhanta is with the infusion kernel. There is a script called install_su.sh which does the old ef su install but I haven't been able to track down the parent script that calls it, or figure out where the $source and $dest variables are being set... I'm assuming it may be possible to stop the script from performing the su install by changing the modify date of the file specified in the $dest var.
Any chance a version of the 4.4.12 GB kernel might materialize that supports OC? (Or an update to the infusion kernel that removes the su installer?) This would help eliminate the issue...
I just Re-rooted my SGS2 and I now have SU and SuperSU ??
Im assuming that SuperSU was installed automatically with the root ROM??
I have puirchased the Pro Version of SU .. so is it safe to Remove SuperSU without messing something up ?
Yes no problem
Just update the binaries of SU.
I tried upgrading from su 2.6.3.1 to superuser 3.0.7 over the weekend and after flashing 3.0.7 , none of my apps that required root work - is there a way around this [im using the latest update (1.63...)] Id like to update but seems stuck with older version for now - at least it works.
I did see a Superuser elite in the market... does the new version require you to pay for the license to get root (not that its about money but im just curious)?
Also yes there us an "update fixer" which requires root privileges which the new 3.0.7 version doesnt provide so i cant use that.
try flashing su in recovery http://androidsu.com/superuser/
yeah thats exactly what i did...
I rooted my phone long ago and just got the new update so had to reroot it after installation... which seemed to work fine (with the older su-2.6.3.1) but sadly now that i got this nonworking superuser 3.0.7 (elf).zip in my phone none of my apps that need root access work
At this point im trying to figure how to go back to the older version (unless i can get this one working). Was just hoping i dont have to start all over as i cant even seem to reflash the older version - as it now gives me errors. Might just have to wipe the phone and start all over with the update.
But yeah so I updated the latest htc update and had to reroot my phone, I was able to flash the su-2.6.3.1 via CMR and this worked fine. It seems as i should have stopped there as i saw that the 2.6.3.1 is an older version, so i tried flashing the latest 3.0.7 (elf) superuser -(which appeared to install just fine) but now I dont seem to have root anymore (although i see the superuser app - none of my apps that require superuser work). Ideas? Using adb .. I do see proper permissions on su at /system/bin but - for some reason SU is not working.
Did you make regular Nandroid backups?
You should have made a Nandroid backup through CWM after installation of Superuser 2.6.3.1. I take it this isn't the case, because that backup would mean you could perform a factory restore, reflash CWM, and restore the backup. Any time you are making changes to your phone, backup before and along the way, just in case something like this happens. Titanium has its uses, but if your phone environment gets borked and you can't use it, it kind of defeats the purpose. Nandroid backups are more reliable in my book, and aren't app-dependent.
Sounds like you will have to start from scratch, although I'm unsure as to why Superuser 3.0.7 didn't work as expected. Possibly there was a conflict in moving from 2.6.3.1 to the newer version. I don't know of any specific problems 3.0.7 has with the MT4GS, and I'm running it on my phone with the latest binary without any problems. I do get an error message for one app, Quick Boot, when I use it to boot into recovery, but that doesn't stop the app from functioning as expected. I think that difficulty is related to the app itself and not Superuser.
Hopefully someone with a little more Superuser experience will chime in here. I'm afraid I don't have any ideas beyond the above.
Good luck --
--
KingCheetah
steve_77 said:
It seems as i should have stopped there as i saw that the 2.6.3.1 is an older version, so i tried flashing the latest 3.0.7 (elf) superuser -(which appeared to install just fine) but now I dont seem to have root anymore (although i see the superuser app - none of my apps that require superuser work). Ideas? Using adb .. I do see proper permissions on su at /system/bin but - for some reason SU is not working.
Click to expand...
Click to collapse
I had a similar problem before with SU after switching ROMs. Don't know if it might help but with Titanium Backup it showed that I had no busybox so I dl'ed busybox then SU wouldn't allow the apps to gain root access. Couldn't figure out what the problem was at all. Then I went to the SU app then saw that under the apps that were allowed or disallowed root access, the SU app itself was there. Once I deleted it from the list all the other apps that needed access worked fine. Hope that helps...
KingCheetah said:
You should have made a Nandroid backup through CWM after installation of Superuser 2.6.3.1.
Click to expand...
Click to collapse
Yeah i know - as fate would have it this is the one time i did not make a backup yet as i was hoping to gut out all the crap apps before doing a backup. Guess ill need to get more religious with the backups.
manimmal
Yeah i had Titanium Backup running with busy box before i had the "bright" idea to upgrade to 3.0.7 - but i guess i could try that but likely i might have to start-over from scratch (and forget about the 3.0.7 version) - unless anyone has any other ideas.
The only thing I can think of is perhaps the first su was flashed using one version of CMR and the second another version of CMR (updated after i installed rom manager perhaps)?
Even more interesting is the "su-2.3.6.1-ef-signed" with su having a datestamp of 8/17/2010; while the "Superuser-3.0.7-efghi-signed2" su version has a datestamp of 2/29/2008 - which seems a bit weird....
steve_77 said:
I tried upgrading from su 2.6.3.1 to superuser 3.0.7 over the weekend and after flashing 3.0.7 , none of my apps that required root work - is there a way around this [im using the latest update (1.63...)] Id like to update but seems stuck with older version for now - at least it works.
I did see a Superuser elite in the market... does the new version require you to pay for the license to get root (not that its about money but im just curious)?
Also yes there us an "update fixer" which requires root privileges which the new 3.0.7 version doesnt provide so i cant use that.
Click to expand...
Click to collapse
I'm running Superuser v3.0.7 with no problem, I flashed it in recovery. It has the su binary 3.0.3.2.
Fuzi0719 said:
I'm running Superuser v3.0.7 with no problem, I flashed it in recovery. It has the su binary 3.0.3.2.
Click to expand...
Click to collapse
do you still have the exact same zip file you used to install 3.0.7 ? (perhaps you have a slightly different one then whats available on the website)
I have no doubt that it works on some peoples devices, but i just dont know why it doesn't work on my device. I am pretty much running stock rom with the latest htc update, CMR 5.0.2.7 , rom manager 5.0.0.6 , superuser 2.3.6.1, su binary 2.3.1-ef - this works ( i have root) but if i boot into recovery and install the latest su for froyo 3.0.7 I loose root. (made nandroid backup this time)
I was thinking of trying to use chainsdd "su update fixer" in the market - but dont know how to use this app.. if it helps in debug i am also having a hard time installing busybox. i use "partitions info lite" to check status of my partitions, root access, and that i have busybox installed... i tried installing it via "busybox" [Stephen (Stericson)], which didnt seem to be recognized so uninstalled and tried "busybox installer" [JRummy16] - they are probably separate issues but who knows...
steve_77 said:
... and install the latest su for froyo 3.0.7 I loose root. ...
Click to expand...
Click to collapse
You answered your own question.
Froyo was the version of Android that predates Gingerbread.
The only official release of software for this device is on Gingerbread.
We are moving forward into Ice Cream Sandwich, but not officially.
You are basically trying to install a Windows 7 Program on Windows 95, to craft an analogy.
Stick with the gingerbread release of superuser.
The reason why the version is higher is because for the Froyo version of Android it went through more iterations.
Shame I didn't see this thread sooner, someone else had this same issue a while ago and I gave the same answer, should be around here somewhere. Would have saved you some trouble.
Some confusion here, I think...
Here's what is at ChainsDD's official site, http://androidsu.com/superuser/
Eclair/Froyo/Gingerbread/Honeycomb/IceCreamSandwich (2.1 – 4.0.3)
md5: fc462fa0630379edbe10006b1d19d9b1
Superuser-3.0.7-efghi-signed.zip | mirror | RM Web Connect
binary only
md5: 26d08a253f1883c13561d173094d70b9
su-bin-3.0.3.2-efghi-signed.zip | mirror | RM Web Connect​
The lines after the md5 codes are links for the zip files. Superuser 3.0.7, according to the dev, is applicable to all flavors of Android as listed. This is also the exact file that I flashed and am using on my phone. There is a separate file for Donut 1.6, and it also is designated 3.0.7, but with a slightly different filename: Superuser-3.0.7-d-signed.zip.
I still think updating from 2.3.6.1 is part of the problem. If you go straight to 3.0.7 after your reformatting, it should work properly.
Also, Manimal's suggestion to check that Superuser isn't disallowed within the app itself is a great idea. It's weird, but an easy fix if this is the case.
I believe the update fixer Chains has available is to correct problems with the Superuser app updating new binaries. I don't think this would be of benefit to your situation.
Chains would be the best source for help, I think; an e-mail couldn't hurt --
--
KingCheetah
2.3.4 is froyo right?
Either way the one i installed (i.e. Superuser-3.0.7-efghi-signed.zip) was from the official site (http://androidsu.com/superuser)
which according to the notes shouldn't matter which version as long as its not 1.6 which it certainly isnt as its 2.3.4
will try it again... but thanks for the reply
So why not install the working version, and then just update the binary from within the app?
That would be one way.
Sent from a digital distance.
steve_77 said:
2.3.4 is froyo right?
Either way the one i installed (i.e. Superuser-3.0.7-efghi-signed.zip) was from the official site (http://androidsu.com/superuser)
which according to the notes shouldn't matter which version as long as its not 1.6 which it certainly isnt as its 2.3.4
will try it again... but thanks for the reply
Click to expand...
Click to collapse
Android 2.3.X is Gingerbread. Froyo is 2.2.X. Anyway, the SU you have SHOULD work, it is the same as I used. Have you tried flashing it via fastboot? I simply flashed the 3.0.7 version via recovery when I installed my ROM (stock 1.63.531.2).
Hello, since the vipers rom thread is to full with people posting. I might as well ask here. Okay, previously in version 1.2.1,I had this problem. Built in vipers superuser doesn't allow any of my root apps like titanium backup. This still happens even though I set as always allow. So, I looked up the thread and someone posted a super supersu zip for version 1.2.1. I flashed it and still supersu doesn't allow my root apps. I was thinking it was because I had both superuser and supersu on my phone so I manually uninstalled superuser from system/app and still nothing worked. I heard the problem was because the built in vipers superuser doesn't have the option to update binary. So, I manually deleted supersu and downloaded superuser again from the market and tried to update binary but it failed saying binary is SUPERSU (in red font). I was so fed up, I did a fresh install of 1.2.1 again with data wipe. All was fine again. A couple days later, vipers 1.3.0 came out, flashed it and everything was okay. Until a couple of days, the same thing came again, the built in superuser won't allow my titanium backup. I looked up the thread again and there was someone also posted another supersu for 1.3.0. My question is, what do I do to avoid the same thing happening again? I just want my root apps to work again, that's all. Thanks in advance.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
do this install supersu from market ..open it ..it updates the binaries..then use it normally ..supersu will take control of superuser permissions ..if not go to settings and check enable superuser
thats all ..
dont remove the inbuilt superuser app
So it is okay to have both supersu and the superuser built in with the vipers rom in the same time? No conflicts?
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
I have rooted android L LRX21O
when I launch titanium backup and it grants root permissions (it does) it suddenly says:
"Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted, and try again.
This attempt was made using the "/system/xbin/su" command".
I have rooted LRX21O with ElementalX 2.03 kernel stock rom.
I am sure i have root access (superuser, busybox).
please help me.
2 things
1) you MUST have the beta version from titanium twitter feed
2) if still not working, you may need either permissive boot.img before elemental x or that pie patch.
rootSU said:
2 things
1) you MUST have the beta version from titanium twitter feed
2) if still not working, you may need either permissive boot.img before elemental x or that pie patch.
Click to expand...
Click to collapse
You are amazing!
1) solution worked.
Thank you so much!