[Q] Superuser or SuperSu - Samsung Galaxy Nexus

It seems that Superuser has problems with Nexus 4.0.4, SuperSu is running more smoothly with this rom, did anyone have the same problem if so help

naelmnael said:
It seems that Superuser has problems with Nexus 4.0.4, SuperSu is running more smoothly with this rom, did anyone have the same problem if so help
Click to expand...
Click to collapse
Thats the first I'm hearing of problems.. ChainsDD SU works great for me!

while installing rom manager and flashing the recovery to make rom manager work it stucks after the download and can t get superuser grant and that on stock firmware. SuperSu did not have that problem, but i prefer using Superuser that is why i asked.

Weird when i have uninstalled the light flow led control application the problem i had with superuser was fixed

I've had zero problems ever with superuser and I'm also using LightFlow
have you tried booting into CWM recovery and fixing permissions?
are you running a rooted rom?

I have never even once had the slightest problem with ChainsDD's superuser. It has never failed me whatsoever in any aspect and I find it to be the best superuser management app there is.

I have made the switch to SuperSU as a ROM I flash had it. Like the featuresm, speed, and the icon is better ;-).
They both do the same. Just a matter of preference.

I tried supersu for a week, on stock. It seemed to allow access faster than superuser.
Just flashed cm9 nightly 2 days ago. I will probably be checking supersu on this setup in a few days to see if the same holds true.
For my purposes, many of the features of both are superfluous. Nice to have, but I really only rely on it to grant proper access. So I can't speak about the feature list... but I'll go on record saying su was granted faster by supersu.
Sent from my Sprint Galaxy Nexus using xda premium

The feature I like the most on SuperSU is the OTA Survival update (which is unfortunately available only on pro).

naelmnael said:
while installing rom manager and flashing the recovery to make rom manager work it stucks after the download and can t get superuser grant and that on stock firmware. SuperSu did not have that problem, but i prefer using Superuser that is why i asked.
Click to expand...
Click to collapse
I also have never had that problem, and I have LF installed as well.
lex25288 said:
The feature I like the most on SuperSU is the OTA Survival update (which is unfortunately available only on pro).
Click to expand...
Click to collapse
OTA Root Keeper does the "survival" feature and its a free app. I think its by the same dev.
Anyways I will prob never switch from SU, its always been good to me, I have the Elite version, and I see no benefit of SuperSU.

It's not by the same dev.
Anyway I prefer using SuperSU because it's updated more often.

lex25288 said:
It's not by the same dev.
Anyway I prefer using SuperSU because it's updated more often.
Click to expand...
Click to collapse
Improvements are nice, but updates for the sake of updates, is like fixing something that is not broken.
I paid for superuser elite, all the features work, what more can I ask for?
Sent from my Galaxy Nexus

Related

[Q] how to update superuser

last week i root my galaxy s2 t989 with superuser 3.0.5.
however, i recently check it, i should root my phone with superuser 3.0.7.
i m a new user for android, and i don't know how to update it.
please help
If your already rooted, then there is no reason to root again.
is not good to make an update version ???
like normally updating software
lauwaifa said:
is not good to make an update version ???
like normally updating software
Click to expand...
Click to collapse
Not really, once you're rooted you're rooted. Unless there are some additions that you really want on the new version then update, it wont (shoulnt) cause any troubles
Sent from my SGH-T989 using Tapatalk
thank you so much !
In the app store look up SU binary. That should bring up an option that would update your SU. Sometimes you won't be able to do certain things if you don't update.

"No Tripping Flash Counter" root isn't rooted

I installed the rooted ROM at [HOWTO] [ROOT] No Tripping Flash Counter [SPR L710VPALEN] (http://forum.xda-developers.com/showthread.php?t=1774722), although I stopped before installing CWM.
It appears I don't have root. I even try to let Superuser update itself from a 3.0.x version to 3.1.1. I am never prompted to grant root access, and it eventually says "Superuser has been denied Superuser permissions".
If Superuser itself cannot get root, then how can this be called a rooted ROM?
P.S., I would have posted in the thread, but I am apparently too much of a n00b per the forum settings.
I know this doesn't help you, but Superuser worked fine for me after using the same method. All I can suggest is to try flashing it again.
Edit: make sure you don't have both Superuser and SuperSU installed. They can conflict with each other.
novasource said:
I installed the rooted ROM at [HOWTO] [ROOT] No Tripping Flash Counter [SPR L710VPALEN] (http://forum.xda-developers.com/showthread.php?t=1774722), although I stopped before installing CWM.
It appears I don't have root. I even try to let Superuser update itself from a 3.0.x version to 3.1.1. I am never prompted to grant root access, and it eventually says "Superuser has been denied Superuser permissions".
If Superuser itself cannot get root, then how can this be called a rooted ROM?
P.S., I would have posted in the thread, but I am apparently too much of a n00b per the forum settings.
Click to expand...
Click to collapse
You need cwm.. Flash It and you will profit....
Sent from my SPH-L710 using xda premium
EndlessDissent said:
I know this doesn't help you, but Superuser worked fine for me after using the same method. All I can suggest is to try flashing it again.
Edit: make sure you don't have both Superuser and SuperSU installed. They can conflict with each other.
Click to expand...
Click to collapse
Thank you!
I only have Superuser installed. It's what came with the ROM. I haven't installed anything else since doing the ROM.
I already flashed twice, got the same results each time.
However, after the flash but before it started installing updates, I ran Superuser, clicked Info, and the entire line above tap to check for updates was green. However, after allowing the first update to install, the line had the left side red:
-rwxr-xr-x root shell /system/xbin/su
It was the same after the third update. I wonder if something about those two updates is disabling root?
Naddict said:
You need cwm.. Flash It and you will profit....
Click to expand...
Click to collapse
Are you sure CWM is needed to get root? My understanding is you must have root before installing CWM?
novasource said:
Are you sure CWM is needed to get root? My understanding is you must have root before installing CWM?
Click to expand...
Click to collapse
Track down the team epic site that walks you through... You should be able to do those steps successfully... Here found link
http://forum.xda-developers.com/showthread.php?t=1743780
Sent from my SPH-L710 using xda premium
Naddict said:
Track down the team epic site that walks you through... You should be able to do those steps successfully... Here found link
http://forum.xda-developers.com/showthread.php?t=1743780
Click to expand...
Click to collapse
Thanks. Just to make sure, are you saying that the original instructions (in the thread linked at top) are wrong to suggest you have a rooted ROM if you haven't installed CWM?
Also, that would mean http://www.androidauthority.com/gal...ot-l710vpalen-stock-rom-flash-counter-103351/ is incorrect.
novasource said:
Thanks. Just to make sure, are you saying that the original instructions (in the thread linked at top) are wrong to suggest you have a rooted ROM if you haven't installed CWM?
Click to expand...
Click to collapse
CWM is used to install root and rooted roms. I have root for my wifes phone but I do not have CWM and all works fine. She actually would never use recovery but I do know how to flash one on there if necessary.
I am quite sure the tutorial is not incorrect and just a misunderstanding somewhere
playya said:
CWM is used to install root and rooted roms. I have root for my wifes phone but I do not have CWM and all works fine. She actually would never use recovery but I do know how to flash one on there if necessary.
I am quite sure the tutorial is not incorrect and just a misunderstanding somewhere
Click to expand...
Click to collapse
I'm scratching my head because there's not much to misunderstand here. The instructions are simple; either you've installed the ROM or you haven't. Since Superuser appeared for the first time after installing the ROM, and the phone prompted me to install two updates after installing, that tells me that the ROM installed correctly.
Wonderful. Just followed the instructions for installing CWM that were linked from http://www.androidauthority.com/gal...ot-l710vpalen-stock-rom-flash-counter-103351/. Not only did that not give me a working copy of CWM, that also made CUSTOM BINARY DOWNLOAD report Yes (1 counts).
novasource said:
Thank you!
I only have Superuser installed. It's what came with the ROM. I haven't installed anything else since doing the ROM.
I already flashed twice, got the same results each time.
However, after the flash but before it started installing updates, I ran Superuser, clicked Info, and the entire line above tap to check for updates was green. However, after allowing the first update to install, the line had the left side red:
-rwxr-xr-x root shell /system/xbin/su
It was the same after the third update. I wonder if something about those two updates is disabling root?
Click to expand...
Click to collapse
I see what your problem is. You're taking the OTA updates. Those erase /system/bin/su and unroot you. Before you take either OTA, install Voodoo OTA Rootkeeper from the Play Store, and back up your root. Then take both updates, reopen, Rootkeeper, and restore root.
No CWM needed.
EndlessDissent said:
I see what your problem is. You're taking the OTA updates. Those erase /system/bin/su and unroot you. Before you take either OTA, install Voodoo OTA Rootkeeper from the Play Store, and back up your root. Then take both updates, reopen, Rootkeeper, and restore root.
No CWM needed.
Click to expand...
Click to collapse
Good catch... Hard as hell to get knee deep into troubleshooting while driving
OP... If that. Doesn't work... http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html?m=1
Sent from my SPH-L710 using xda premium
EndlessDissent said:
I see what your problem is. You're taking the OTA updates. Those erase /system/bin/su and unroot you. Before you take either OTA, install Voodoo OTA Rootkeeper from the Play Store, and back up your root. Then take both updates, reopen, Rootkeeper, and restore root.
No CWM needed.
Click to expand...
Click to collapse
YOU ARE CORRECT! I'll add that to the comments of http://www.androidauthority.com/gal...ot-l710vpalen-stock-rom-flash-counter-103351/. Thank you for the help.
EDIT: Voodoo OTA Rootkeeper doesn't work. More details later.
Bad news: While it is correct that the OTA updates are killing my root, Voodoo OTA Rootkeeper won't work. Even with it installed,
When you start the app, it says it is "useless" for "Samsung phones updated via KIES or Odin...".
Will check on alternatives.
novasource said:
Bad news: While it is correct that the OTA updates are killing my root, Voodoo OTA Rootkeeper won't work. Even with it installed,
When you start the app, it says it is "useless" for "Samsung phones updated via KIES or Odin...".
Will check on alternatives.
Click to expand...
Click to collapse
http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html?m=1
Have you tried this?
Naddict said:
http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html?m=1
Have you tried this?
Click to expand...
Click to collapse
I tried once using the instructions at .http://www.androidauthority.com/galaxy-s3-sph-l710-sprint-clockworkmod-recovery-99305/. Not only did it not install, it incremented my binary counter. Fortunately I was able to use Triangle Away to reset that.
I'm still not clear how CWM will help me. This is supposed to be a rooted ROM already. Not sure why I would need CWM.
novasource said:
I tried once using the instructions at .http://www.androidauthority.com/galaxy-s3-sph-l710-sprint-clockworkmod-recovery-99305/. Not only did it not install, it incremented my binary counter. Fortunately I was able to use Triangle Away to reset that.
I'm still not clear how CWM will help me. This is supposed to be a rooted ROM already. Not sure why I would need CWM.
Click to expand...
Click to collapse
It is a combo deal...It is not a ROM though...Try it...you may like it
this? http://www.youtube.com/playlist?list=PL7011CD883D5201B8&feature=view_all
Naddict said:
It is a combo deal...It is not a ROM though...Try it...you may like it
this? http://www.youtube.com/playlist?list=PL7011CD883D5201B8&feature=view_all
Click to expand...
Click to collapse
OK, I tried it, and it appears to work. I had to use Triangle Away to get rid of the binary counter increment.
It's important to note that I only got this to work by not using the "No Tripping Flash Counter" ROM.
novasource said:
OK, I tried it, and it appears to work. I had to use Triangle Away to get rid of the binary counter increment.
It's important to note that I only got this to work by not using the "No Tripping Flash Counter" ROM.
Click to expand...
Click to collapse
Good?!?
Sent from my SPH-L710 using xda premium
Naddict said:
Good?!?
Click to expand...
Click to collapse
Yes!

[Q] Factory Reset lead to problems with Titanium Backup (using CWM)

I've looked around and cannot find a solution specific to my issue. If someone can direct me to where I can find a solution I would be grateful.
I have a Samsung Epic 4g (Galaxy S) and have CWM on it. I recently did a factory reset of the phone and after resetting, Titanium Backup (not Pro) is stuck on the "asking for root rights...." screen, even after Superuser Elite asks to allow it.
I've seen things that say to uninstall the updates to SU and I've tried that. I've tried uninstalling SU Elite and Titanium Backup then reinstalling and I can't figure it out.
I'm somewhat of a novice when it comes to this, and brand new to this site so I'm hoping someone can help me with this while walking me through it if need be.
Thank you greatly.
Re-root maybe?
Sent from my Incredible S using xda premium
Sounds like you may have lost root somehow.
nikon120 said:
Sounds like you may have lost root somehow.
Click to expand...
Click to collapse
That's what I was thinking, but once I booted up my phone after the factory reset, superuser was still there. Doesn't that mean my phone is still rooted? Not to mention, I've booted up cwm a bunch still after the reset? I'm confused.
ET5115 said:
That's what I was thinking, but once I booted up my phone after the factory reset, superuser was still there. Doesn't that mean my phone is still rooted? Not to mention, I've booted up cwm a bunch still after the reset? I'm confused.
Click to expand...
Click to collapse
To be sure, why not download the app root checker from the play store? Then you will know what you got.
TeamBringIt said:
To be sure, why not download the app root checker from the play store? Then you will know what you got.
Click to expand...
Click to collapse
Awesome idea, I wasn't aware. However, I downloaded it, ran it and it verified my root access with no issues. HMPH. I have no idea what to do.
DEFINITELY A RE-ROOT, I say.
Superuser is just an app managing "ALLOWs" and "DENYs". The real issue should be that you lost/broke your su binary in /system/xbin... If you have CWM then easily recover by flashing the latest SU zip package found at http://androidsu.com/superuser/ . Good luck
Sent from my Incredible S using xda premium
Team Epic has a CWM flashable that should also clear any binary remnants and get you back rooted the right way.. You can then flash TWRP and all that afterwards if you want.
epiccm.blogspot.com/p/about-epic-cm.html is the site link...mught help you.
AndyYan said:
DEFINITELY A RE-ROOT, I say.
Superuser is just an app managing "ALLOWs" and "DENYs". The real issue should be that you lost/broke your su binary in /system/xbin... If you have CWM then easily recover by flashing the latest SU zip package. Good luck
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
Well, you have all been a big help. I downloaded this latest su zip and was about to see if it was the issue. Right before I did that, I said "what the hell" and tried flashing via rom manager one more time. You guessed it, it worked. All the headaches for no apparent reason. However, I thank everyone. I'm a new member to the site and it's refreshing to see many try and come to your aid.

Root manager other than SuperSu in 4.3?

Hello, I cannot get either "Superuser" to work in mk4 4.3.
Every time I try, I end up having to dirty flash my ROM to get a working root again.
Any help is great!
Thanks
Sent from my SPH-L900 using Tapatalk
MeetFace said:
Hello, I cannot get either "Superuser" to work in mk4 4.3.
Every time I try, I end up having to dirty flash my ROM to get a working root again.
Any help is great!
Thanks
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
Because I've had so much interest, and so few takers, I'll add that this may be specific to Synergy ROM mk4. When I get a chance to flash lorjays again I may update my experience.
Sent from my SPH-L900 using Tapatalk
May I ask why do you prefer Superuser over SuperSU? Don't they kinda do the same thing with SuperSU being updated constantly?
Use Kingoroot. In the end it'll put SuperSU on your phone, but you should be able to then install Superuser and remove SuperSU.
ecs87 said:
May I ask why do you prefer Superuser over SuperSU? Don't they kinda do the same thing with SuperSU being updated constantly?
Use Kingoroot. In the end it'll put SuperSU on your phone, but you should be able to then install Superuser and remove SuperSU.
Click to expand...
Click to collapse
Well, in the past, for whatever reason I had problems running an app or two using a certain su app.
I thought this may have been the problem with my current mk4 ROM, turns out it may relate to the boot.img that is currently being used.

[Q] Broke my SuperSU app by installing busybox?

(My first post on the forums! You guys have helped me out so much in the past, and I'm excited to finally communicate with you. Wish me luck!)
I recently installed the 4.3 OTA update on my Samsung Galaxy S3, using the zips and instructions from these threads:
http://forum.xda-developers.com/showthread.php?t=2387423
http://forum.xda-developers.com/showthread.php?t=2538991
It went perfectly, without a hitch. Everything was running great, and I was loving everything about stock, de-samsungized 4.3, root and custom bootloader.
I was very interested in the dSploit app, and installed it, found out I needed Busybox. I installed it using the busybox installer. This is where the trouble begins. SuperSU needed a binary update after I installed busybox for some reason, even though I was fairly certain I already had the latest binaries. I tried running it through the automatic update with my teamwin bootloader, but it only booted into recovery and nothing installed. After googling it for a bit, decided to re-flash SuperSU. Suddenly, I began recieving the message "Unfortunately, SuperSU has stopped working" every time I tried to access anything requiring root priviledges. Anything that had already been granted root access (including Titanium Backup, thank goodness) seemed to work fine as long as it didn't need to request additional privileges. Unfortunately, I'm now locked out of ES File Explorer and the xposed framework (all prior installed modules continue to function though)
My initial thought was to wipe and reload using the process I used to get here in the first place, but I'm running 4.3 now, and I understand that downgrading is impossible now, and no flashable 4.3 stock roms seem to exist.
So I'm lost, guys. I need my root back somehow... If I forgot any information you think would be relevant and/or helpful, let me know and I'll provide anything you need. I've been googling and searching the forums for days, but I haven't found anyone with this exact problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
RidleyofZebes said:
(My first post on the forums! You guys have helped me out so much in the past, and I'm excited to finally communicate with you. Wish me luck!)
I recently installed the 4.3 OTA update on my Samsung Galaxy S3, using the zips and instructions from these threads:
http://forum.xda-developers.com/showthread.php?t=2387423
http://forum.xda-developers.com/showthread.php?t=2538991
It went perfectly, without a hitch. Everything was running great, and I was loving everything about stock, de-samsungized 4.3, root and custom bootloader.
I was very interested in the dSploit app, and installed it, found out I needed Busybox. I installed it using the busybox installer. This is where the trouble begins. SuperSU needed a binary update after I installed busybox for some reason, even though I was fairly certain I already had the latest binaries. I tried running it through the automatic update with my teamwin bootloader, but it only booted into recovery and nothing installed. After googling it for a bit, decided to re-flash SuperSU. Suddenly, I began recieving the message "Unfortunately, SuperSU has stopped working" every time I tried to access anything requiring root priviledges. Anything that had already been granted root access (including Titanium Backup, thank goodness) seemed to work fine as long as it didn't need to request additional privileges. Unfortunately, I'm now locked out of ES File Explorer and the xposed framework (all prior installed modules continue to function though)
My initial thought was to wipe and reload using the process I used to get here in the first place, but I'm running 4.3 now, and I understand that downgrading is impossible now, and no flashable 4.3 stock roms seem to exist.
So I'm lost, guys. I need my root back somehow... If I forgot any information you think would be relevant and/or helpful, let me know and I'll provide anything you need. I've been googling and searching the forums for days, but I haven't found anyone with this exact problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Have you tried uninstalling and reinstalling SuperSu?
Since SuperSU was flashed to the device via Odin, it is registered as a system app. The app store only has the open option, and I can't access the app in the system folder without root privileges, which it won't give me, so...
Yeah. Unless there's a script I can run through recovery, that's a dead end.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
there is a zip of SuperSU you can flash from recovery
Sent from my SGH-I747M using Tapatalk
I've tried this. In fact, that was when SuperSU began force-closing. I just need to completely uninstall it and start fresh, I think.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Have you tried the cleanup/unroot options inside supersu settings? Then starting over?
I might not have stated this directly before, but the SuperSU app won't launch. I tap on it and immediately get the "Unfortunately" error. I have no way of accessing anything within the app.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
RidleyofZebes said:
I might not have stated this directly before, but the SuperSU app won't launch. I tap on it and immediately get the "Unfortunately" error. I have no way of accessing anything within the app.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Ok well then find one of the 4.3 roms in development that you can use. I'm on s3rx 3.0 and other than some hiccups (still a wip atm) that are liveable, its pretty stable. You can flash this safely in recovery without the bootloader/modem package since you already took the OTA without risk of bricking. Its prerooted so no worries there. Good luck
pre4speed said:
Ok well then find one of the 4.3 roms in development that you can use. I'm on s3rx 3.0 and other than some hiccups (still a wip atm) that are liveable, its pretty stable. You can flash this safely in recovery without the bootloader/modem package since you already took the OTA without risk of bricking. Its prerooted so no worries there. Good luck
Click to expand...
Click to collapse
Thank you for that. It's always good to have a fallback option.
I'm still wondering though, is there a script I could flash that would completely remove SuperSU / BusyBox / superUSER (CWM) to scratch and allow me to re-flash CF-Autoroot? Barring that, how difficult would it be to code one myself?
FIXED IT.
Apparently, flashing the latest version of SuperSU from the developer's website (1.86) will not work on Android 4.3. I flashed version 1.65 as provided in the original 4.3 Rooting Guide, then updated it in the Play Store followed by a binary update and re-installed BusyBox, and everything is back to running order. Thank you all for your help and advice!

Categories

Resources