yashsingh1/xdaforums huggingface dataset:
[SuperSU] Frank Westlake:
I wonder if '/system' is failing to remount to read/write. I you install SuperSU manually you'll have to remount system ('mount -o remount,rw /system') so notice if it fails.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium

---------- Post added at 02:30 AM ---------- Previous post was at 02:23 AM ----------

I have never used the Play Store so I have no idea what it does and I assumed you installed SuperSU through the Recovery program on your device. If you have not tried it that way you should; the ZIP file is in the first message of this thread.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] MarkV.:
Hello,

I'm trying to root my Galaxy S3 with version android 4.3

Normaly i use the prerooted manual from infamous http://www.infamousdevelopment.com/forum/topic/215-how-to-make-prerooted-stock-odin-flashable-ie-root-method/

But when i trt to start supersu it says that there isn't a binary installed.

Also tried to preroot the new 1.91 version, no luck.

I read a lot of things here, but can someone make a step by step tutorial, so i and all other... android noobs... can make a preroot with there beloved su root app :laugh:???
[SuperSU] kulguy:
Very often, daemonsu:10216 is top of the running processes, and I see two of quadcore is running and clock is very high, above 1.52ghz. Is it related to SuperSU and does anyone experience similar problem? My device is Galaxy S4 lte-a, using Snapdragon 800 processor, JB 4.3.
[SuperSU] Chainfire:
Figure out which app has ID 216 ... (if you "forget" all the apps in SuperSU's list, and re-auth them one by one, this number will show up in the dialog)
[SuperSU] Smultie:
Does this happen after updating AdAway? If so: downgrade to version 2.5
[SuperSU] kulguy:
No, I don't use AdAway...

Thank you! I didn't know what the number meant..

I did what you said, and finally found GMDGestureControl was the one, ID 216.

I guess it can be culprit because it hasn't worked well recently. Now things are made clear.. I should report it to the dev..
[SuperSU] GroteBozewolf:
Off topic: which app are you using here?
[SuperSU] GldRush98:
OS Monitor
[SuperSU] Frank Westlake:
http://eolwral.github.io/OSMonitor/

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] en11gma:
think i found the culprit....its SuperSU :)

i have sprint sph-l720 (Sprint Galaxy S4)

when im on stock offiical rom (no root or cust reocery)

i flash philz cwmr which i then at that same time install supersu1.86.zip

when i gets to desktop it updates when i run it.

i can no longer do dialer codes like ##3424# to get into DIAG mode.

can not get into ##72786# for SCRTN

no ##786# RTN either

i was doing some investigating thinking it could be philz cwmr but now that i came here and see in 1st post that you guys are messing with the dialer i bet i found my cultprit

STAY OUT OF THAT AREA

you all are making my like hell :)

please fix or investigate

like i said...its either you guys or philz but since i seen the "- Launch from dialer: *#*#1234#*#* or *#*#7873778#*#* (*#*#SUPERSU#*#*)

NOTE: Not all phones take both codes. On some phones you need to use single *# instead of double *#*#" im betting its you guys
[SuperSU] mbunal:
enter ghost mode from adb

hi

is it possible to enter ghost mode from adb shell? latest supersu used.
[SuperSU] Frank Westlake:
I wonder if this is related. I don't use the device as a telephone and I have deleted most of the phone related applications. No dialer. The only thing I haven't been able to delete without getting an annoying dialog each boot is 'SecPhone.apk'. The dialog reports "Unfortunately SecPhone has stopped", even though it is not even present. Not a SuperSU problem -- just thinking this might somehow be related to me not getting SuperSU Knox related errors.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] 11wallace11:
ShareKM broken after 1.80

Hi Chainfire,

I've been using your SuperSu script for quite a long time now, and never encountered an error like that.

I'm using an app called ShareKM, which was unfortunately abandoned by it's developer.

I recently purchased a Nexus 5, and found out that the app claims my device is not rooted (even though it is). After a long investigation, I found out that version 1.8 works just fine, while 1.85 and up don't.

Checking the changelog, I think the suspect is one of these changes:

- Fix su to non-root user on 4.3+
- Fix su permission reset on 4.4 (will not be an issue until Samsung comes out with stock 4.4 ROMs)
- Completely removed nag capability

I wonder if there's something that could be done, other than just sticking with v1.8, as there's no way to change the app itself.

Thanks in advance.
[SuperSU] asdfasdfvful:
I might not be understanding this correctly, but what exactly is the function of the backup script? It may be that I always flash the SuperSU zip before even booting into the rom, but every time I open it I have to redo all the permissions for the dozen rooted apps I have. Does that (or survival mode), save the granted permissions (and the black theme) or do I need to redo it with every flash?
[SuperSU] putr4s:
The function of the backup script is to ensure that SuperSU is not deleted/replaced when you update your custom ROM. All permissions and settings should still be there.
[SuperSU] white7561:
To install the SuperSU on A ROM that have a superuser app

Find the Superuser app on the rom ( /System/app/ ) .... After that delete the superuser.apk....after that reboot to recovery and flash the SuperSU Flashable ZIP..and reboot your device and ....SuperSU Is Installed!!!:fingers-crossed:
[SuperSU] asdfasdfvful:
So if I wipe a rom will it just be there or does it have to reinstall from the play store?
[SuperSU] putr4s:
It should still be there if you wipe data, except for the settings and permissions. However, if you wipe system partition, you will lose SuperSU, and you'd have to install it again.
[SuperSU] asdfasdfvful:
Darn. I always flash on a full wipe. Guess I should just start granting access as default so that I don't go through everything every time.
[SuperSU] Pkt_Lnt:
Most roms automatically wipe system with the install script to make sure that system changes are clean.
[SuperSU] husky69:
I keep losing su after updating OmniROM through OpenDelta updater, although I have copied the zip file from download.chainfire.eu/supersu/ to /sdcard/OpenDelta/FlashAfterUpdate/

After removing SuperSu completely through the option under settings and reinstalling it from scratch I found that the backup scripts apparently remained installed.

Where's the location they've been installed? I'd like to try and remove them so I'm back to zero again.

Or maybe someone has other hints for me? I'd appreciate :)

Thanks for your help :)
[SuperSU] AA1973:
Omni > /system/addon.d > 99-supersu.sh

If you still lose root after an update, then either you are flashing in secure mode(=no zip files in flash after update folder will be flashed) and / or your backup script hasn't been installed properly. Or a mixture of both.

I am using omni on a tablet while flashing insecure (kernel flash afterwards) and a Note N7000 in secure mode (only Rom, nothing else is flashed). On both devices I never lost root. Current version SuperSU 1.91.

Secure / insecure flash > look in open delta settings

Sent from GALAXY TAB2 P5100 // OmniROM 4.4.2 // Dhollmen Kernel // ART
[SuperSU] :
[MENTION=2952258]AA1973[/MENTION] !!

Sent from Nexus 5 on Slimkat
[SuperSU] Pons:
Does (both available in SuperSU settings) first installing to /system and then installing backup script not work?
[SuperSU] AA1973:
They work fine for me. As I flash SuperSU only via recovery (version1.91), it is already installed in system and upon first launch, you'll get a pop up to install the backup script.

If you dismiss this pop up, then the install option within SuperSU does work, too.
[SuperSU] husky69:
It didn't so far. Removed and reinstalled backup script.

Will try tomorrow with next nightly again :)
[SuperSU] husky69:
Ok, thanks a million to you all - now it works :D
[SuperSU] avi30na:
Hello everyone

when i try to install SuperSU on any rom (through google play) it successfully installs the su binary but when i reboot the phone itll stuck on samsung logo

i tried it on both liquidsmooth and CM roms (galaxy s3 t999v) (both android 4.3) (clean install)

and they both have superuser as default pre-installed root managers

what am i doing wrong?
[SuperSU] AA1973:
Flash SuperSU via recovery.

http://download.chainfire.eu/supersu
[SuperSU] Colt77:
I currently have already mentioned in this thread problem with daemonsu eating the battery and locking the phone.

I am on SGN2 N7100 with Hurricane 8.0 custom ROM (though I do not believe it is ROM-specific cause the same happened to me on DN3 ROM, yeah, both are 4.3) and Agni 3.9 kernel.

It usually happens when the phone is in a deep sleep for a few hours. When I try to wake it up it does not respond in any way and when after reboot I look into SystemPanel monitor I can see daemonsu loading 100% CPU for some time (from a few minutes to a few hours) right before the reboot.

Other than this issue everything works great, the phone is fast and responsive and I have lowest battery consumption I ever saw on SGN2 (when deamonsu does not go ballistic) so I'd rather try to fix the problem than flash another ROM.

I understand that this is caused by some app(s), and I started attempts to pinpoint the culprit already by removing apps one by one and waiting for a day or two.

Last time it happened I had only three apps installed with permissions granted:

GMD GestureControl

LBE Security Manager

Samba Filesharing

I removed GMD (since according to log it was asking for root far more often than other apps) and waiting for results, but now I have a question.

Should I look only into apps which are listed by SuperSu, or there could be problem with apps which could potentially ask for permissions, but I never saw them doing so, since I have apps like Greenify, for example, restored from backup, but never ran them yet, and thus, never granted/rejected permissions to them myself.

Could it be that they somehow ask SuperSu during the phone's deep sleep, but aren't in logs because everything just hangs up? (I understand it may sound like a dumb question, but I'd rather know).

Thanks in advance :)

Edit:

Well, GMD it is, which is sad :( Great app with great functionality :( Hope there will be some fix soon.
[SuperSU] asdfasdfvful:
Any chance that the zip in the chain fire site will be updated?
[SuperSU] Pons:
It's not? I just glanced at the page, and it says 1.91.
[SuperSU] Colt77:
Yup. Flashed it yesterday, got 1.91.
[SuperSU] asdfasdfvful:
And on my pc, the site says version 0.94...Strange

Edit: I need to learn to scroll up more.. guess my bookmark is outdated and google is showing the wrong site
[SuperSU] bhiga:
Use http://download.chainfire.eu/supersu to make sure you're pointed to the newest version rather than an old archive page. :)

Sent from a device with no keyboard. Please forgive typos, they may not be my own.
[SuperSU] simonsalo:
Are we getting an updated version for the i9506 soon that roots without tripping the knox flag to 1?
[SuperSU] darwusch:
When supersu is disabled in the settings menu, is there a way to enable it through adb?
[SuperSU] matteebee:
Worked, thanks. The only other request I have is 5G(n) wifi, only 2.4 available. This is so :highfive:awesome!
[SuperSU] zman519:
I thought I would get back to my earlier post inquiring about a Aocp 7.0

I had some time today, nandroided flashed in recovery via twrp. All's good.

Sg3 710

Sent from a thing running on Electrons
[SuperSU] DESASTER75:
@ Chainfire and/or all:

I think you'll have been asked this question 10000000 of times and answered already same often times, too!

I'm using an SONY XPERIA Z1 with iHackers-CR 2.0 (status: rooted and LB) and your app in PRO-version (SuperSU)!

GP offers the update and now SuperSu was gone (only PRO-license remained)! So I went to GP and installed SuperSu (1.91) again, went to app-drawer and now, tadaaaaaaaaaaaaa, SU-Binary must be updated but 'Normal-version' failed!

quesions:

- Am I able to update SU-Binary-file WITHOUT loosing root-permissions AND/OR dual-recovery?

- If there micht be a possibility, can you please let me know how to proceed (step-by-step)?

- What will be the steps if there will be an GP-update showing-up to avoid troubles for SU-binary-file-update(s) in future, too?

Following file already on external SD: UPDATE-SuperSU-v1.91.zip Anything to do with it or delete?

Thank you very much
[SuperSU] kingvortex:
Flash the SuperSU update zip in recovery. It includes the apk and su binary. If you update that way in future, you should avoid problems like the one you have encountered.
[SuperSU] DESASTER75:
Hi!

And by doing this way, there can't be any unexpected troubles with something (lost root-access or lost dual-recoveries)? 1000000% safe?

Thx
[SuperSU] kingvortex:
There's always a small chance that something will go wrong.

Having said that, it's very, very unlikely that a problem will arise from flashing the update zip as it will not touch the area of /system where the dual recovery is installed.
[SuperSU] DESASTER75:
Hi!

Thanks a lot! I did and it worked well! YOU MADE MY DAY! Will always do SuperSU-Update by downloading from Chainfires webpage and installing through CWM!

Thanks,

DES75
[SuperSU] kingvortex:
You're welcome.
[SuperSU] gothicasshole:
I'm using a boot strap type recovery it's safe strap based off of twrp (locked boot loaders suck) I'm having an issue with an app I granted it access but it says I didn't keeps throwing no root error is there an update for the binaries? Can I manually update with a boot strap recovery?
[SuperSU] dimebagdan65:
By the way, this is what I mean when I say email the dev of the app you're having problems with, not post "another app that doesn't work" in this thread. Here's a letter I wrote the Tasker devs outlining the problem, what I did to troubleshoot and determine the cause, and a proposed fix:

I've confirmed, it wasn't because I had Tasker as a system app that it couldn't detect root, it's how Tasker polls for if root is present. I installed Superuser from the Play Store and without opening it or updating the binaries, went in to Tasker to attempt a root access and sure enough, my SuperSU prompt popped up. Make sure in your code you're not just checking for the presence of the superuser.apk cause even non rooted devices can have that (not that it would do them any good lol) but rather check for a su*.bin that way it looks for the binary and will work with su.bin used by Superuser and the custom su binary from SuperSU. Hope this helps!

Now please, I'm not a mod nor am I working for Chainfire, I'm just an apartment manager with too much time on his hands trying to keep this thread on topic. Only report bugs with the SuperSU app itself. If Chainfire gets tired of hearing all the complaints about problems that are beyond his control, he might get burnt out on this project and stop with the awesome updates and I for one don't wanna see that happen! Rock on CF!
[SuperSU] segv11:
So far SuperSU (pro) is still rocking for me on my LTE Galaxy Nexus under 4.0.2. Only issue I ever had was a the grant not "sticking" for a couple of apps until I did it manually in SuperSU.

One interesting test will be if survivor mode can survive the 4.0.4/4.0.5 OTA if VZW ever gets around to pushing it.
[SuperSU] dimebagdan65:
For those having problems with supersu

I recently wrote up a review of SuperSU and I just got done adding a how-to guide of how to get it to work flawlessly with any app and what exactly to do if it doesn't! Check it out and feel free to include it in the OP if you like it and approve my methods Chainfire! Personally, I friggin love this app and can't wait to see what else you can do with it!
[SuperSU] shaggyskunk:
Is anyone having force close issues with Titanium Backup pro? Also LBE PRIVACY policy is failing to start properly.. Stock rom, rooted.. Don't think that there were any updates, other than Lookout security.

Titanium lets me do a couple of things before fc???

I'm not sure if it's related to chainfire SUPERSU?

As far as I can see, Titanium is the only app that fcs & LBE's issue of not launching properly is the same as when superSU was first installed, but that was fixed with the next update... Dunno? :confused:
[SuperSU] DarkhShadow:
TB pro works fine here

Sent from my ice cream powered Nexus S
[SuperSU] shaggyskunk:
Yeah, it's the first time that I've noticed any issues.. Again, I don't know if it's related to su... With the exception of LBE.

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] dimebagdan65:
How have you set up your SuperSU, did you check out the guide I posted?
[SuperSU] shaggyskunk:
I just downloaded it from the market... But other than the very first release (problem with LBE) it has worked flawlessly!

No I haven't seen your guide.. But I have read chainfire's & there was one by a guy whose screen name starts with Dr something.

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] dimebagdan65:
I show how to set it up as a system app and what to do if you find an app that doesn't play nice with SuperSU (I don't get paid per view, only clicks on Google ads, so not trolling for page hits, just tryin to help ^_^)>b
[SuperSU] shaggyskunk:
Thanks.. In the mysteries of the Universe.... It's just started working properly again???

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] themadba:
Hi,

I've read a few posts, but I want to be entirely sure.

I have a ROM on my SGS2 that uses SuperUser, and I want to upgrade to SuperSU. I have heard that having the two packages running side-by-side is not good (which is kind of obvious.) What is the best way of going about this?

People suggested deleting the superuser.apk from the system/apps, and then flash the supersu.apk file through CWM. Will this work, or is there something I am missing? I won't lose root by deleting the superuser.apk file or anything?

Thanks,

Chris.
[SuperSU] dimebagdan65:
Scroll up, I posted a link to a guide that shows step by step how to go from using superuser to SuperSU as well as what do do if you run into any wonkiness, hope it helps!

Edit here ya go: http://xdaforums.com/showthread.php?p=7231
[SuperSU] Pons:
Have Superuser installed and working. Download SuperSU from market. Go into SuperSU settings and make sure you have the binary for it installed (it should ask). Let it install binary and grant it permissions from Superuser. Now, go into Superuser, menu, preferences. Scroll down to Su binary, and it should say something like v0.84:SUPERSU. That's good. Now uninstall Superuser if you want (I didn't). Apps should now ask SuperSU for permissions and you should be good to go.

Edit: @dimebag What do you think about adding the step about checking the SuperSU binary from Superuser to your guide? I personally like verifying that it's setup.
[SuperSU] dimebagdan65:
Gimme a minute, I'll update, good call!

Edit: done ^_^
[SuperSU] themadba:
Thats it!

One more thing to annoy you with, how do I move SuperSU to the system/app directory? I know that apps installed off the Play Market are stored in the user/app directory, but where is it? I can't find it, and I have Root Explorer by the way.

Thanks,

Chris.
[SuperSU] Pons:
You can either use TB pro to do it automatically, or move it manually using Root Explorer. I don't remember the name off the top of my head, but http://www.dimedroidhq.com/2012/03/if-youre-rooted-you-need-this-app.html?m=1 has it.
[SuperSU] dimebagdan65:
Here you go ^_^ Guide/Review for SuperSU
[SuperSU] shaggyskunk:
Great link dimebagdan! I left out the 65... Too formal :p

Got a question though... Every time that chainfire updates the version #, you have to download the latest zip, right? So how do you keep your version of superSU current?

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] Pons:
That's why I install (and update) through Google Play. Just like any other app.
[SuperSU] sparksco:
I wanted the app installed to my system so I flashed the CWM zip and then with the updates from the market I just used titanium backup to merge the updates into system.
[SuperSU] TriMoon:
You should really ask that question to the maker of your app that complains about no root.

There are other root programs around that your application might be checking for instead of SuperSU.

If SuperSU would not work others would not used it ;)

Send from my SGN10.1 via xda-developers app
[SuperSU] .rootCoder.:
Thanks A lot DEV Chainfire ;)

both of you(Chainfire and koush) are making the best work

keep it up :cowboy:
[SuperSU] Frank Westlake:
Yes. The first message of this thread that you read has one.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] stuart0001:
Couple of Qs

If I install SU as a system app and hide from app drawer, will it stay hidden following a 'Factory Reset'?

Is it possible to disguise SuperSU so it has an innocious name?

The reasons are that I have Cerberus installed (as system app and disguised), so in the even of my phone being stolen I can factory reset my device remotely, then continuing to track my phone. I would like to give as little clues as possible to the thief that the phone is running anything other than stock apps.

I've changed the settings in SuperSU to not display notifications and to allow system apps so it should at least be silent after reboot.

Many thanks
[SuperSU] stuart0001:
Also, I've got Cerberus installed as a system app is system/priv-app and have trust system app checked in supersu but it still prompts for access. Can anyone advise please.
[SuperSU] [NUT]:
[MENTION=631273]Chainfire[/MENTION]

On Sony Xperia models with the JB4.3 update I am running in to a confusing situation, I hope you are able to help me out here.

When a ROM has built in init.d support or drafts this support from XZDualRecovery, the fact that 99SuperSUDaemon gets the chance to run is intended functionality. IF you then chmod 644 /system/etc/install-recovery.sh it all works fine until the SuperSU app 'repairs' it and it kicks in to action again. From that moment onward it will start daemonsu twice, confusing the app and even though root keeps working, it drops back to the 'no app' behavior, making the phone vibrate every time root is requested or a su call has been made.

Is there any way to prevent the app from reactivating the install-recovery.sh file?
[SuperSU] Chainfire:
That's strange. What happens if you disable 99SuperSUDaemon instead?
[SuperSU] [NUT]:
Then the su+app will remain working. But the problem is, that it gets restored by the app too :D
[SuperSU] Chainfire:
OK I'm asking because you should be able to start the daemon as often as you like, and only the first one would stick. So I had expected one of the two scripts malfunctioning. But as I understand it, either one will work, just not both ?
[SuperSU] r00t4rd3d:
Chainfire do you plan on hacking the Chromecast at all? Now that the SDK has been released I think root might soon become a necessity.
[SuperSU] :
Chromecast sucks.

Sent from Nexus 5 (?) on Slimkat
[SuperSU] [NUT]:
That is correct.

I'm expecting it to be something Sony specific though. Sony seems to be the only manufacturer who still does not really use selinux. The Roms are set to permissive and filecontexts are completely unset.
[SuperSU] Chainfire:
There's been Glass on my desk for almost two weeks now and I haven't even had the time to play with it :'(
[SuperSU] Chainfire:
If possible can we do some live test/debugging over IRC ? Surprising SELinux is still not used by them, I do believe SuperSU expects that if API level indicates 4.3+, that may well be one of the issues.

Well, at least I can chalk up this issue as 'the [NUT] case' in my docs, so it has that going for it ...
[SuperSU] [NUT]:
:D :laugh: I seriously LoL'ed there :laugh: :D

What is the best time to join IRC to meet you? :)

Or if you use hangouts, I could PM you my handle?