yashsingh1/xdaforums huggingface dataset:
[SuperSU] Frank Westlake:
Thanks, got it.There doesn't appear to be anything useful regarding SuperSU, but I'm not Chainfire. He might look at it some day after Monday.

Frank
[SuperSU] JulianJenner:
Beta2.17 working for me without problem on LGE-P760, CM11 by Artas182x

CM11 4.4.4 by Artas182x with F2FS filesystem / LGE-P760 / Tapatalk Pro 4.6.2
[SuperSU] jesssiii:
Your avatar is a little scary, lol.

LG G2 VS980
[SuperSU] JulianJenner:
Dear [MENTION=2861395]jesssiii[/MENTION]!

Maybe I'm outrageous however,. I'm not dangerous...

I am God-fearing believer...
[SuperSU] Chainfire:
New beta - v2.19
[SuperSU] robygt:
Thanks Sir.
[SuperSU] jcarreira:
OK on OnePlus One
[SuperSU] Carpe Noctem 11:
Thanks [MENTION=631273]Chainfire[/MENTION], works fine on S3 mini --> CyanogenMod 11.0 (20141101)
[SuperSU] rcobourn:
Boot loop issue on Note 4 is resolved. ?

Looks like it still needs to be defaulted to grant all requests, can't press allow on the pop-up.
[SuperSU] Frank Westlake:
2.19 OK on:

- Note3 SM-N900V 4.3 Permissive

- Note3 SM-N900T 4.3 Enforcing

2.19 had troubles on Note_ SGJ-I717 4.0.3:

- Installed through TWRP. No reported errors. Collected debug data, stored in zip subdir "recovery".

- Booted Android. I have 'su' do things in '/' during my boot process and they succeeded.

- Launched SuperSU. Apps and Logs both showing perpetual busy indicators. Prefs OK. Hit HOME button and collected debug data, stored in zip subdir "device".

- Rebooted Android.

- Launched SuperSU. No apparent problems. Collected debug data but did not keep because logcat had nothing "installer|supersu".

The only thing I could find is at the end of the recovery.log in the "recovery" subdir:

Running boot script...

sh: invalid number '1000000000000'

I:/sbin/runatboot.sh process ended with ERROR=1

Frank
[SuperSU] Chinaboy5216:
Running great on the Chinese Note 3 SM-N9008V

Edit: TF101 also no problem

Thanks Chainfire, great job on Lollipop :cowboy::cowboy:
[SuperSU] shekinahsmoke:
I was told to uncheck tapjacking in Settings. :good:
[SuperSU] sefrcoko:
That didn't work for me. Unchecked the option in supersu and rebooted, but still getting the same result in TB.
[SuperSU] RusherDude:
Thanks. It would be cool is something got automated into supersu to do those kind of stuff by default, like permit an install like this and show a warning "The install of X requires a reboot in order to be mounted correctly" or something like that. Systemless stuff is going to get us headaches like this continuously in the following months... I still hope [MENTION=631273]Chainfire[/MENTION] keeps offering an in-system option.
[SuperSU] drothenberger:
[MENTION=631273]Chainfire[/MENTION] said in the release notes for 2.62 that the bind is likely a temporary thing. The correct long-term solution is for application developers to fix their apps so the don't expect su at a fixed path.

You could try just disabling the bind mount. You might now have any misbehaving apps installed. I don't.
[SuperSU] andresee:
Yes It was working on Monday... so i was just seeing if anyone else was having the issue. I know google is giving 20$ giftcards to bestbuy if you use pay in the US, so didnt know if they changed the check.
[SuperSU] courageousrobot:
Okay, I'm pretty sure I'm doing something wrong here, but I can't for the life of me get 2.62-3 to play nice with Franco Kernel r37 on my Nexus 6. Everything I've seen here and on the FK thread (and yes, I've used the search function), indicates that this is the right way to go. I'd love a thumbs up thumbs down to whether or not I'm doing things properly.

Here's what I'm doing:

* Using Wug's Nexus Root Toolkit I flash stock + unroot to 6.0.1 (this way the /system partition should be clean/stock)

* Install TWRP

* Flash Franco Kernel r37

* Flash SuperSU-v2.62-3-20151211162651.zip

Once done, the SuperSU installer script says everything's good, the phone boots up, shows that Franco Kernel is still running r37, but there's no SuperSU app installed, and the phone does not appear to be rooted.

Am I missing something here?

Edit: Doh. Had to install SuperSU through the play store. I guess I'm used to the other "install root" methods also tossing in the SuperSU APK onto the phone in the process.
[SuperSU] Fischfuss:
Hello Guis,

I rooted my HTC One A9 with the jcase-method. Root-Apps like TitaniumBackup working well, but for some reason I can not write the system-partition.

Now I want to try the systemless root, but Unfortunately, I do not have a backup of my stock boot.img, only the modified a9-ee-635503.7.zip from this threat: http://xdaforums.com/one-a9/development/root-htc-a9-t3244141

Maybe here is someone who has a stock unlocked Boot.img (htc_hiaeuhl:6.0, CL635503, TMO_DE_1.10.111.7) for me. no matter whether a fastboot flashable img or TWRP-Backup

This is my Phone: htc/hiaeuhl_00111/htc_hiaeuhl:6.0/MRA58K/635503.7:user/release-keys

Thanks for Help
[SuperSU] g.andy:
Sorry. With supersu 2.52, first is necessary to flash a custom kernel (franco, elementax ecc) for nexus 5 with stock rom?

Inviato dal mio Nexus 5
[SuperSU] Chahk:
I'm curious as to what benefit there is to using systemless root if you are planning to modify system anyway with Xposed, for example.
[SuperSU] ashyx:
The benefit is that Chainfire has done all the hard work to auto patch the boot.img to allow root on root restricted devices.

There is no actual benefit as regards system or systemless if you intend to modify system anyway except for the fact root is easily removed.
[SuperSU] hocuspocus69:
Problem supersu 2.62-3 hellscore b16

Stock kernel supersu perfect

Hellscore kernel supersu revert to stock kernel...
[SuperSU] wind0zer:
Hopefully on my Sony handset I can get OTA updates, with systemless root, and have host level ad blocking. It remains to be seen after further testing.
[SuperSU] eradicator006:
Has anyone noticed higher than normal battery usage after installing supersu 2.62-3? I am on cyanogenmod 13 and was using the builtin root. I switched back to supersu (was using it before but some apps don't like the systemless root) last night and noticed my battery is draining quite fast.
[SuperSU] andresee:
Well DPI might affect it but adaway or busybox doesnt effect it. Even though you can use adaway without moding the system as well as busybox.
[SuperSU] andresee:
I havent had any issues with root with systemless. Im sure some people have but its worth a try.
[SuperSU] hocuspocus69:
Try blu spark 45 kernel 6.01

but

same thing supersu revert me to stock kernel something about just patched!!
[SuperSU] osm0sis:
Nope. The correct way to keep it systemless is to bind mount /system/etc/hosts to /su/etc/hosts with a su.d script and leave AdAway thinking it's modifying /system. There's even a flashable zip that sets this up for you in [MENTION=3355398]mrRobinson[/MENTION]'s awesome AdAway thread. :good:
[SuperSU] andresee:
Cool thanks I check that out. But why wouldn't using adaways symlink not be systemless?
[SuperSU] ashyx:
No I don't mean devices with locked bootloaders.

I mean devices that have security policies in force that are enforcing root restrictions.
[SuperSU] chazall1:
I flashed SU SU 2.62-3 as well and in SU settings it indicates SU 2.62
[SuperSU] osm0sis:
Because you're modifying /system by replacing /system/etc/hosts with a symlink. :good:
[SuperSU] chazall1:
I was just informed that in beta 2.26-3 it will indicate 2.26 in settings.
[SuperSU] Jamesits:
about SuperSU 2.62.3 systemless root

I've noticed if you don't wipe dalvik cache immediately after installing SuperSU, the system never boots - it stuck on a lot of ART fatals. So please add this to the install script.

Android 6.0.1, SuperSU 2.62.3, Nexus 5X
[SuperSU] Didgeridoohan:
I've installed SuperSU 2.62-3 on stock Android 6.0.1 on both a Nexus 6 and a Nexus 6P without wiping anything and they boot just fine.
[SuperSU] Blzfrost:
6.62-3 worked great. Thank you. I guess I was lucky to wipe dalvic and cache after installing.
[SuperSU] brandonabandon:
a factory reset is wiping root. im running 6.0.1 with v2.62-3 on a mako. any suggestions?
[SuperSU] Ja_som:
2.62 is systemless root, so SuperSU is installed as user app, not system app (If I'm not wrong), and factory reset deletes all your user apps...
[SuperSU] gamerZ1:
Hello. I have flashed the latest Cataclysm ROM (14 december Android 6.0.1) and want to root.I read the SuperSU thread but don't want to brick my phone and want to ask how to sideload SuperSU?And which boot image to flash?

cauze there are 2 post from Chainfire I don't know which one to use?I want to flash after installing SuperSU franco kernel

Device:Nexus 5 16 gb TWRP 2.8.7.1 ROM C

Rooting procedure:

- flash/upgrade to Marshmellow (done)

- flash modified boot.img

- flash/boot TWRP and sideload latest v2.50+

- Flash stock /system ----what stock image?

- Flash the attached boot image

- Flash the attached SuperSU ZIP in TWRP
[SuperSU] ashyx:
Did you read ANY of this thread at all? :banghead:
[SuperSU] gamerZ1:
Yes.
[SuperSU] ashyx:
Then you'll be fully aware that a modified boot.img is not required and the latest beta is 2.62-3.:rolleyes:

Plus the info posted countless times in this thread how to flash.
[SuperSU] rebretz000:
Sorry if this has been mentioned or answered, I tried searching for the answer but

With Systemless root 2.62 v3 I notice that my phone, the Nexus 6P, boots twice. It goes from warning screen to Google to boot animation (for 2 seconds), back to the warning screen then goes through the normal boot sequence. I've reflashed everything but always does that. Is that normal?

I'm running Cataclysm ROM wit either Franco or Lean Kernel.
[SuperSU] jcsww:
I would say so, based on my own experience on stock.
[SuperSU] Jamesits:
Do you still have this problem after multiple reboots? I've also noticed that on the first reboot after installing and from the second time it's all normal.
[SuperSU] rebretz000:
Okay. So yours double boots also? That makes me feel better. Thought I did something wrong.

---------- Post added at 08:39 PM ---------- Previous post was at 08:30 PM ----------

Honestly I've never reboot again after the first install. I only boot after i install a new kernel and SuperSU. Going to reboot and see.

Okay your were right. It boots normal after initial boot. I just rebooted and it went fine. One boot sequence. Thanks a lot. I appreciate it. I always figure I must have done something wrong.
[SuperSU] Sophos1:
My 6p rebooted twice (just the first time). It's done it on the initial boot each time I have rooted. Subsequent boots are normal.
[SuperSU] jcsww:
It only did the first boot after installing SuperSU. After that, it boots normally.
[SuperSU] Mircolino:
On my Nexus 6P (bought on Google Play) it wasn't.

Had to add "net.tethering.noprovisioning=true" to /system/build.prop
[SuperSU] i_pk_pjers_i:
How do I install this on my N5x, just flash the beta 2.62.3 ZIP in TWRP and then I have root or do I have to do anything special?
[SuperSU] P4P3RB4G:
Does this work with 6.0.1? or should I upgrade to 2.6.0?
[SuperSU] ashyx:
It's normal, Chainfire even mentions it somewhere.
[SuperSU] smallfish82:
Battery drain with S6

There appear to be at least two other posters who have raised a point about high battery drain (~40% in 12 hours) on the S6 phone. I would like to reiterate this is a problem with my standard S6 phone too running the latest Samsung firmware with TWRP.

I will have to uninstall shortly as battery life no longer is reliable with SuperSU 2.62-3 (and I suspect earlier builds as I was running a 2.5x version at first when I noticed).

Also note that after some boots my phone is saying it is not rooted. Intermittent issue solved by a reboot.
[SuperSU] Judim:
Hey I just want to report an easy and succesfull use of Root without modifying /system - SuperSU 2.62-3 on my Nexus 5X.

Thanks Chainfire!

I updated from Android 6.0 root SuperSu 2.52 with modified boot and /system to Android 6.0.1 by first flashing 6.0.1 radio, boot, system, vendor. Then adb sideloading SuperSU-v2.62-3-20151211162651.zip

CF Lumen works fine with it, wich is my main raison I want root.
[SuperSU] illuminae:
Hi Chainfire, I did as you said and it worked perfectly fine - thanks a lot! Now I am prompted the 6.0.1 OTA. Can I unroot in any way, install the OTA and re-do the root? Thank you!
[SuperSU] ishivam:
Anybody please tell me that how to ROOT intex aqua trend 4g 5.1
[SuperSU] kundica:
Most likely SuperSU isn't the problem. The S6 has an issue with not entering deep sleep when using a custom recovery. There are few ways to resolve this.

1 - You can reflash the stock recovery and wipe cache. (I did this and my battery life has greatly increased with betterbatterystats now showing the phone entering deep sleep.)

2 - You can run a custom kernel that implements the deep sleep fix.
[SuperSU] nixie2121:
This may have nothing to do with SU but I am lost so thought I would try here.

I am using the verizon FIOS mobile app. I can watch DVR content anywhere. When I set it up the app complained that I had modified my phone so would not work. I deleted /su/xbin_bind and the app started working. When I left my home network to use LTE, the app thinks I am out of the country!!!! So weird. I assume this has nothing to do with supersu, but like I said, i'm lost and if there is a chance I thought I would ask. Using the latest 2.62-3. THanks!
[SuperSU] Flyview:
Hey [MENTION=631273]Chainfire[/MENTION] I've been using the context switching you helped me out with about a year ago to make the root commands work in my app LeanDroid. You probably don't remember but when Lollipop was new you showed me how to use your supersu library to switch context to system. Maybe I'm not remembering correctly but this was in order to get around selinux restricting my root commands which involve system processes. I have been requiring my users to have SuperSU as their root, as for example CyanogenMod's built in root still isn't working. Is SuperSU still the only root option that allows context switching?

I posted this on page 379 but you probably missed it. You're obviously very busy.
[SuperSU] yusuflala:
Plz tell me my supersu say bainery update needed but I m not able to update... How to get that
[SuperSU] Pkt_Lnt:
This thread in the same SuperSU forum.

[SUPPORT] Update failures
[SuperSU] smallfish82:
Thanks. Had not read properly about that bug (and read that can also be triggered by BT).

1 - I've tried but it made no difference. A complete factory reset, total wipe (all partitions!) and odin install of Samsung stock firmware, TWRP and then SuperSU (via TWRP).

2 - I was unikernel but made the mistake of installing Vindicator Kernel over unikernel, which messed up the phone (always on charge icon when phone was off etc). I'll research the other kernels. I am sceptical of unikernel as Smart Manager detects it changing things that maybe it shouldn't. I believe there are three kernels with their source open to everyone to review though (including unikernel I think?).
[SuperSU] nixie2121:
I'm thinking the app knows I'm rooted, is this possible using systemless root Evan though I deleted the xbin_bind?
[SuperSU] osm0sis:
Definitely possible. It just depends how smart the app dev was; anybody who wanted something solid to exclude root users would have it just make a basic root request to test, regardless of where the su binary is.

You might want to clear the app data though to see if it was leftover from a previous check before you deleted the xbin bind.
[SuperSU] nixie2121:
I tried clearing the data. is there a way to hide root?
[SuperSU] Alxoom33:
I don't think it's a rot issue. It's probably the app. Try deleting and reloading the app.[emoji106]
[SuperSU] nixie2121:
I just tried that again and still same issue. is there a way to hide root from the app to test it?
[SuperSU] pluto6496:
The modified boot.img of mdb08i did not work on mmb29k, will you release a new copy of boot.img for mm29k ?

PS:the device is Nexus 5X
[SuperSU] Alxoom33:
Sure, you can unroot using the indoor feature in SuperSu app's settings or use the su unrootusung zip that's has been floating around the various threads.
[SuperSU] nixie2121:
turns out it was adblock, I disabled and all worked!
[SuperSU] Ch3vr0n:
Likely no, because you didn't read. The latest beta doesn't need a modified boot image. It does that itself. Flash stock boot/system, flash beta 2.62-3

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] TR2N:
Hi guys, Sterricsons Busybox got updated with systemless root support. It was installed to su/xbin_bind before. Is it save to delete the whole folder it to reinstall Busybox? I know it is possible that this is already answered, but is this affecting other files, that Android stored in system/xbin? I deleted the _bind folder and noticed that the whole system/xbin folder was empty. I rebooted and checked the xbin-folder again - two files are in there - dexdump and wlutil. Anything i should care about?

Sorry for this noob-problem..
[SuperSU] Midomad:
I'm unable to delete system apps with Titanium back up with last systemless root method?

Envoyé de mon Nexus 5 en utilisant Tapatalk
[SuperSU] Seronez:
I get this:

Extracting ramdisk

decompressing ramdisk

Failure, aborting

with CM13 so root is not working.
[SuperSU] pluto6496:
I got it, thank you very much!
[SuperSU] :
I have the same issue with Titanium Backup and SuperSU 2.62. Cannot restore applications either. Restoring data only works but results in fc for the specific app. Changing system apps is processed by TB but doesn't work actually.

Root is detected and works. Installed busybox from playstore in preselected /su/bin. Did not delete /su/xbin_bind folder after root. Changing app processing mode in TB doesn't do the trick.

I'm on Note 4 SM910-F stock 5.1.1 with latest TWRP and SuperSU 2.62.3.
[SuperSU] Ch3vr0n:
TB just needs an update most likely to work normally with systemless. Just like other apps do

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Vadzhik:
Hello! How to make for razor (flo) 6.0.1 MMB29K system SuperSU, for him, there are modified boot.img?

Thank You!
[SuperSU] Ch3vr0n:
U don't, read the last dozen pages or even the first one. The latest systemless beta modifies the boot image on its own

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] bunklung:
I am all OVER this command: "settings put global policy_control immersive.xxx" The cool part is that is sticks on reboot!

I created a quick settings tile with https://play.google.com/store/apps/details?id=com.quinny898.app.customquicksettings The bonus is that you can also enable battery percentage.

With a custom quick tile you can:

On press is invokes an application (Tasker app factory app) that performs: "settings put global policy_control immersive.full=*" as a root shell command.

On long press the tile runs a Tasker app that performs: "settings put global policy_control immersive.full=-*:immersive.full=com.android.chrome" as a root shell command.

So basically I can turn on and off full screen immersive mode from the quick settings and still keep Chrome always on. I don't need Xposed App Settings anymore because I can manually add certain apps to have full immersive by Tasker. I also figured out how to enable/disable airplane mode by command line when within range of Wifi via Tasker. This was another Secure Settings feature I don't need anymore, but WAS required by Tasker to automate! So bye bye Secure Settings, Xposed, GMD, and those other buggy full screen mods.

Commands:

On Airplane:

settings put global airplane_mode_on 1;am broadcast -a android.intent.action.AIRPLANE_MODE --ez state true

Off Airplane:

settings put global airplane_mode_on 0;am broadcast -a android.intent.action.AIRPLANE_MODE --ez state false

ALL ON IMMERSIVE:

settings put global policy_control immersive.full=*

ALL OFF *NOT* PREFERRED (IMO):

settings put global policy_control null

ALL OFF PREFERRED

settings put global policy_control immersive.full=-*

OFF JUST CHROME

settings put global policy_control immersive.full=-com.android.chrome

ALL OFF EXCEPT CHROME

settings put global policy_control immersive.full=-*:immersive.full=com.android.chrome

You can also mix and match stuff below with just hid the navigation and/or just hide the status bar:

settings put global policy_control immersive.status

settings put global policy_control immersive.navigation

Combo example (turns ON myfunapp to have navigation controls hidden, turns ON mylauncher to have status bay hidden, turns OFF Chrome browsers full immersive mode (if it was on before)

settings put global policy_control immersive.navigation=com.android.myfunapp:settings:immersive.status=com.android.mylauncher:immersive.full=-com.android.chrome

Hope this helps.

Referenced here: https://android.googlesource.com/pl...droid/internal/policy/impl/PolicyControl.java
[SuperSU] Chainfire:
I would like to subscribe to your newsletter.
[SuperSU] TacoKing0218:
Is the beta 2.52 really stable? I would like to update to 6.0.1 but keep root, and I heard keeping 2.46 when you update will cause a soft brick (a bootloop, to be specific).
[SuperSU] cLogic:
not having any probs here ... running TB 7.3.0, superSu 2.62-3 on unofficial CM13 for d2tmo
[SuperSU] bunklung:
[MENTION=3355398]mrRobinson[/MENTION] has a work around for systemless AdAway (http://xdaforums.com/showthread.php?t=2190753)

I tried to use his work to hack around build.prop edits. I was successful in creating an alternative build.prop located in /su/system and added a script to su.d (mount -o bind /su/system/build.prop /system/build.prop;)

This worked, but build.prop must be loaded before su.d is executed? I am just trying to edit my build.prop without mounting /system.

-Newsletter #2 :)
[SuperSU] GamaX320:
how to flash supersu 2.62 on cm13:confused: every time I flash it suck at bootanimation
[SuperSU] gorilla p:
Try flash stock, reboot to bootlloader, push twrp from PC, reboot to twrp/recovery, wipe/factory reset, flash rom, flash gapps, flash unroot, flash systemless.

Maybe a link to unroot in OP would be good? I didn't see it there.
[SuperSU] thgxda:
Hi all,

I'm trying to get the "init.d" working on my Moto G 4G XT1039 with the latest CyanogenMods, currently cm-13.0-20151218-NIGHTLY-peregrine.

So one "solution" was, making a new cm13 build, using SuperR's kitchen, that includes SuperSU Beta 2.62-3. To replace the CyanogenMod "su" by the SuperSU one, you just have to dis-/enable the "root"-function in the kitchen once, the new build will come with SuperSU installed then.

I was almost "done", in "either way", while everything seemed to work with my CM13.0 kitchen-build, means root, init.d, autostart crond, a show stopper just popped up :(

"pm" is not working anymore, when I make a "su -" after login via "adb shell", same for "logcat", that only produces an empty output:

# /system/bin/pm list users
Error: Could not access the Package Manager. Is the system running?

Without using "su" it works as it should and "logcat" also lists the log as expected, with the original cm13-image it also was working after changing to root with "su -".

Any idea? Maybe a bug in SuperSU?

Thanks a lot,

kind regards,

thgxda
[SuperSU] FernBch:
I have an issue I need help with. Today I flashed SynergyCM13.0 for jfltevzw and cannot get SuoerSU 2.62-3 to install. It goes through the process but doesn't "take".

Here's my recovery log:

https://www.dropbox.com/s/kmc3bafuvlfq20v/recovery.log?dl=0
[SuperSU] egingell:
The package manager has never been available from recovery or during boot when "init.d" executes.

Sent from: SGS4 - JB 4.2.2 MF9
[SuperSU] thgxda:
hi egingell,

thank you very much for your answer!

I do not want to start the pm during boot, I want to start the BusyBox crond.

There is a cron-job that uses "pm" for doing some work, the cronjob itself works, but not the "pm"-commands.

And while after an "adb shell", "su -" using the command "pm list users" (or any other "pm" and "logcat") normally should work, it does not, even not if you "go back" to the shell user with "su - shell", after installing SuperSU 2-62-3.

If you just login via "adb shell" and then do a "pm list users", it works as expected, so I assume, that it has s.th. to do with SuperSU?

Thanks a lot, kind regards,

thgxda
[SuperSU] Captain_Throwback:
If you're using SuperSU, why don't you just use su.d instead of init.d?