yashsingh1/xdaforums huggingface dataset:
[SuperSU] grep_i:
Because mine is good enough to clean up cm superuser and that's what he was describing he had.

I pushed yours all the time although I wasn't even using it, recently I started pushing mine which helped the people who used it except this fellow because his problem is something else.

Something he probably forgot to mention.

But do I understand it correctly you're telling me to not push my edit ?
[SuperSU] shoey63:
[MENTION=4544860]osm0sis[/MENTION]'s tool is more complete. And your edit is based on his older work. His new tool should be vigorously pushed to the maximum. It will benefit all users going forward.

Edit [MENTION=6952047]grep_i[/MENTION]

What problem did the user have that can't be solved by Osm0sis's new script?
[SuperSU] grep_i:
Do whatever you like you're free to do so and I'm not the one stopping you or telling you not to do so.

But please don't act like you're superior or something with repeating facts and selectively reading posts.

Never said that users had problems that couldn't been solved with osm0sis new script.

Never used his new script so I would not know that.

If you were not biased while reading you would have seen that I merely stated that my edit was good enough for the problem being described and that it worked for other users with similar issues.

But read carefully:

I said it didn't work for "emontes" as he probably has another problem that he forgot to mention.

PS, "emontes" did also try osm0sis script which didn't resolve the issue.

That would be the answer to your question:
[SuperSU] Nekromantik:
Is it a known issue that this version installs su file into /system/xbin?

As twont let suhide to get installed.
[SuperSU] neofiliate:
Hi,

Sorry I am quite a n00b at rooting stuff, how do I use this?

I previously (2014-ish) used Hasson2000's all in one toolkit to root my HTC M8. This used installing TWRP which installed SuperSU (via a zip that came with TWRP). I never did more than this with it but now I would like to remove root, uninstall SuperSU and restore my boot. Is this the correct script to allow me to remove SuperSU in this case?

I have tried using the "Complete unroot" option in the SuperSU app but it does nothing as far as I can see. After a reboot the SuperSU app is still their as a system app and still apparently rooted (I can still use it to grant access to TitaniumBackup for example). I have not been able to see any trace of the app itself in /system/ or /data/ when using the TWRP file browser though there is a /supersu/ directory. I am not sure if this /supersu directory is just the files that wwere used to install SuperSu or if they are what was actually installed (I have very little idea of how SuperSU works, LOL!

Many thanks, N
[SuperSU] grep_i:
No problem everybody was a noob once.

I assume you flashed the .zip script in TWRP custom recovery ?

Is it possible for you to take a look with a filebrowser in your device's

/cache/recovery/last_log

If you don know how to read the log can you upload it here so we can take a look at your log.

Or if you are adventurous try this little script to clean up old remnants from SuperSU or CM superuser.
[SuperSU] Hannibal226:
That's not an issue, the rom u use is just pre-rooted.

Use TWRP to first mount system and afterwards the file manager to delete the SU file in /system/xbin/

Afterwards u can flash suhide.

But 2 things:

1) with actual November patch it will run in endless boot (don't use suhide)

2) please next time use the suhide thread for questions relating to this

CHEERS ;)
[SuperSU] neofiliate:
Many thanks grep_i, attached should be the last_log file.

If I want to run that script how do I do so? At a first guess I need to unzip it and place it on my device... Any particular location? How to then initiate the script?

Again, many thanks!
[SuperSU] grep_i:
Put it on your /sdcard

Just flash it from TWRP like you would flash any other file like for instance SuperSU.

No need to unzip the file just flash it.

Forgive me if I'm wrong but I don't see your attached last_log
[SuperSU] neofiliate:
Whoops, typical I forgot to attach the file! attached to this one with a .txt extension to allow the forums to see it as a valid file.
[SuperSU] grep_i:
Looking at you last_log I see two things:

You are using a rather old custom recovery, try upgrading it to latest version.

twrp-3.0.2-0-m8.img

After that find out how to flash .zip flashable files in TWRP if not already known.

There's no mention of anything being flashed in TWRP custom recovery are you sure you flashed something ?
[SuperSU] neofiliate:
I think I used the process from this video https://www.youtube.com/watch?v=Krw6H4gQ6g0 (kinda hard to remember that far back!), SuperSu install is about 6:10-ish
[SuperSU] grep_i:
You still can use the tool if you are feeling comfortable with it but make sure you flash a newer custom recovery, the one I provided you a link for in previous post and the rest goes the same.
[SuperSU] neofiliate:
Final question then, will my boot backup I made with this older version of TWRP still work for restore with newer versions of TWRP?

Thanks!
[SuperSU] grep_i:
I do think so but you can always make a new backup of boot with the new version of TWRP if you want.
[SuperSU] andrew2432:
I thought twrp backups were compatible across updates?? Won't that clean backup also remove the systemless su back to a clean state as well?
[SuperSU] grep_i:
I never said it would not.

If you mean restoring a backup of clean boot than I guess yes but I have to say I never did restore boot from backup I only did a reflash of boot.

Which in my opinion clears boot partition and flashes new files to it.

1 or 2 times I created backups with TWRP but I never restored I always found another way to resolve my issues.
[SuperSU] andrew2432:
Reflashed a stock boot or flashed your own backup? And I've done a few restores, it wipes clean whatever you selected to restore right before it restores. This is my Internet connection so when I lose apns, I can't Google how to fix :crying:haha
[SuperSU] grep_i:
Reflashed a stock boot and reflashed a backup from SuperSU flashing.

APN's are not so hard to get working again if you have the most important one on paper as a guidance.
[SuperSU] andrew2432:
Hehe put it on a notepad on my comp after restore. It's titled sprintapndata.txt lol
[SuperSU] osm0sis:
You can technically do whatever you want, but it's derivative of my work and now that I've updated mine we don't need more old versions of it floating around, it's just not logical. Especially considering my new unSU handles all that and more.

Also why are you uploading it every time? You've uploaded it 6 times between the 2 threads. You seem to have a chip on your shoulder about this judging from your response to [MENTION=4675598]shoey63[/MENTION] and I'm honestly not sure why. :confused:
[SuperSU] grep_i:
I can and will push what I want even if it's from anyone else then you, you do not have the monopoly to push something and it seems you counted it for me as well thanks for that, I did upload it multiple times because it was easier to do that than link it back to another upload which I did also a couple of times maybe you count those too.

Also I did not test your new script so I shouldn't be the one pushing it as I have no knowledge of how it's working or not.

Personally it does not matter to me if you understand why I do not like shoey63 response I think I have explained myself enough on the matter and wish to go back and help others on this forum where I can and however I can.

No hard feelings whatsoever this is only my opinion.
[SuperSU] andrew2432:
"ELE"

Jackie Moon, 1976 via 2008
[SuperSU] Roberto Nigel:
I get a bootloop in the latest CM13 nightly, tried flashing SR1 2 and 3 same thing
[SuperSU] jimbomodder:
Try changing selinux to permissive
[SuperSU] tau.gi.mo:
I tried to install SuperSu 2.78 SR3 Systemless on my Xiaomi Redmi Note 2 running CM13 but the Installation abortes at "Calling user ramdisk patch script", what does this step do, or how to fix this?
[SuperSU] grep_i:
Did it work before there are rumours that the November patch bootloops devices when using suhide or Xposed but I'm only guessing now.

Maybe if you give some more details about how you flashed and on which device and with what software.
[SuperSU] osm0sis:
No, if it was not an edit containing some work by you then I would request you stop since I don't allow mirrors of my work, but as I said, this is a derivative work and you can technically do what you will. You did look at my new version and say "looks good" however, so I really didn't expect this from a helpful power user such as yourself.

Ah well.. yes, no hard feelings. All people do tend to get a little precious about things they've worked on, so I get it. Back to the regularly scheduled "customer service". ;)
[SuperSU] JonathanRAZ:
Delete
[SuperSU] Alxoom33:
Hey guys, won't you take your tiff to PM's or a friendly phone call?

We like and respect both of you. Please!
[SuperSU] osm0sis:
If it wasn't clear we're done so please stop dragging it out by commenting on it further. ;)
[SuperSU] grep_i:
Yes you are right I opened the source and read the code and that "looks :good:" did not test it though.

You know I pushed mine when yours was not ready yet.

Maybe a couple days too long after yours was finished too but I do not see the wrong in that, basically you are saying if I make a better script than yours you will stop pushing yours, I do not see how that's helpfull.

All code may exist and users can choose which one to use and which one they don't wanna use.

But if you have such deep feelings about this script although I'm entitled to do as I please with it, I will then not push mine anymore, just to make you happy.

Can we shake on it now then. :highfive:

PS. [MENTION=4544860]osm0sis[/MENTION] I see your reply post on alxoom33 but that was too late I already responded on that without his response I would have let it, my apologies for that.:angel:
[SuperSU] Alxoom33:
Done. Thanks.
[SuperSU] Roberto Nigel:
it used to work before and I had systemless xposed installed

I'm on HTC desire 816
[SuperSU] desilynn79:
please help, this is all very new to me and confusing

this systemless root is very new to me and i dont want to mess things up....

my household recently bought 2 lg tribute hd- (also called the lg x style)

all other root method i can seem to get to work because i can find an actual twrp or cwm for this phonte and one click and pc methods dont work either...

i would love to try to do systemless root if i could get help. ,ost of the info i am getting isnt helpful or just confuses me more..

right now my main reason is that we use wifi from our phone to use the computer... boost is limiting my buil;t in tether to something like 8gb of transfer and then shuts it down.

on other phones with the "normal" way to root i had an app called wifi tether router that bypasses all of that and i can tether without that limitation... however this app requires root... and atm i cant root my new phones to do the same.

any and all help will be appreciated. i will provide you with any in to help you help me if i can.

model of phone is lg ls676, running 6.0.1, kernel3.10.49, build number MXB48T, software is ls676zv3.

in order to help you help me, some info you need you might have to explain to me how to obtain it.

again thank you!
[SuperSU] Pkt_Lnt:
This is a thread about a root MANAGEMENT tool. not how to root. Start here and use the links and resources there.

http://www.xda-developers.com/root/
[SuperSU] desilynn79:
right i got that but this is where it sent me looking for the systemless root which is supersu beta.... followed thread links. so could you klnidly point me to the exact page i am lokking for which is chainfires systemless root for 6.0.1???
[SuperSU] grep_i:
This is one of those pages and you can find the links in first post or OP.

---------- Post added at 07:18 PM ---------- Previous post was at 07:11 PM ----------

Then I would advise you to take a look in the rom specific thread to see if they know a work-a-round or have a solution already for this issue.
[SuperSU] Pkt_Lnt:
(sigh)
[SuperSU] desilynn79:
I have done my research thank you very much... Im asking for help.. Thats why im here! Can we say rude much??? I thought thats what the forums are for, to learn and ask questions/ for help. Traditional root methods dont work.... I havent been able to locate a trwp or cwm.... I want root, systemless because its 6.0.1..... Im confused and dont want to screw things up.... Hence asking for help.... Oh but wait, everyone here must know everything, right?

My mistake i obviously came to the wrong forum or thread thinking someone would help..... My bad....

Still looking for some actual help since my research findings have only left me unanswered or confused.

Also the systemless root page by chainfire links you here for questions..... Hmmmm.....

Just saying!
[SuperSU] shawkes:
SuperSU does not root your phone. If there is no custom recovery available for your phone and traditional root methods don't work you are probably out of luck.
[SuperSU] desilynn79:
Thats why im looking into systemless root... Any help on this matter since that page refers me here....?
[SuperSU] Portgas D. Ace:
SuperSU will either be system-based or systemless, depending on a little file which has to be created manually (search for "echo systemless", if interested). But for that, you need a custom recovery. So even the systemless variant of SuperSU won't help you here.
[SuperSU] Alxoom33:
You first need to find out on your device thread how to unlock your device and load a custom recovery. Then you can root.
[SuperSU] grep_i:
I have no clue against who you are so angry I only see people trying to help you.

I do not know anything about your research but what I did was go to Google and type:

root lg x style

This gave me 4.000.000 hits

After studying the first 10 hits I think you will manage to root this device probably with Kingoroot, Framaroot or cf autoroot install flashfire and in flashfire flash SuperSU or even install TWRP manager from the playstore after being rooted and let it install TWRP custom recovery for you if possible.

Better yet do try the first 10 hits from the search results.

If this still is not sufficient you probably have to wait for someone to find a way to root this device as it seems to be that it is a quite new device and probably not yet picked up by a lot of peoples and developers.
[SuperSU] desilynn79:
Thank you. I have found something i will hopefully be able to try tonight or tomorow that claims to unloxk the bootloader. Is that what you mean by unlock? It just want root period and i would love to learn for this device if anyone is willing to help even if it means building some things lol.

Im not knowledgeable myself to figure it all out by myself..
[SuperSU] grep_i:
Yes that's what is meant by unlocking the bootloader.

After that it should be possible to flash custom recovery and in custom recovery flash root.

There are some other ways but this is the most common one.

Good luck with gaining root on your device.
[SuperSU] andrew2432:
[MENTION=5921492]desilynn79[/MENTION]

Lgs are funky. If you traditional root, install cwm or twrp recoveries you can then uninstall root application, go to recovery and flash an unsu zip of some sort, there's a few moded versions and some official ones I hear. Then you'll flash new magisk, flash cbump because LG bootloaders are weird, flash phh and good to go. It's step one that will be tough.

Try searching LG one click root

Try using your exact model number in a Google search

Try twrp repositories for adb commands to install twrp manually for your device

My LG used stumproot to start the nonsense.

Good luck
[SuperSU] JulianJenner:
2.08 working on LG Optimus L9 P760. Thanks for your work! And LG Optimus L5II P460 too. :) And not work with SG Gio (old little device)... :(
[SuperSU] netdeanz:
Latest BETA works good have not encountered any issues.
[SuperSU] JahSam:
Hi !

1st, thanks for your work ! :)

2nd, I've read on the 2 and 3 firsts posts that you're working on a SELinux a bit more permissive allowing a full root for the LPV.

I've just read this thread so I don't know if you're already knows or not, but there is a version of the LPV with a permissive SELinux. Maybe you could work together on this ? (maybe they just allow to much things and that's not want you want for us I definitly don't know ^^')

Just un case : [MENTION=1050103]sykopompos[/MENTION] [L][5.0] Android Lpv Dev for N5 Enhanced --> they made a version for the N4 too

BTW : just flashed the last beta on the nexus 5 and everything seems alright ! :)
[SuperSU] Aaahh:
I'm on 2.08,

I have tapjackprotection enabled by defualt, I noticed it blocks touchs to the dialog while my app is ope:

https://forums.oneplus.net/threads/yellow-band-software-fix-no-uv.100868

Is there a whitelist so that my users can still use my app and supersu without disabling tapjack?
[SuperSU] Chainfire:
There is nothing wrong with SELinux or root on LPV. It is a "full" root. Just not all root apps have been updated to work with it - but I assure you, most apps *can* be updated. AOSP and retail L builds are different stories, and we need some adjustments to SELinux for that. Those I have working, but this is certainly not the same thing as switching SELinux to full permissive, which is a terrible idea. It's like breaking down the walls of your house to get in when your door jams - I would fix the door instead.

No, there is not, and there will never be. Tapjacking protection is meant specifically to block apps like yours - a malicious app can overlay information over the dialog making the user thing he's pressing something different than "deny".

I am considering adding an intent (broadcasted only to apps that have "granted" root status) on dialog show/hide so apps like yours can temporarily disable overlays and automatically re-enable them again. What do you think about that?
[SuperSU] Aaahh:
That might work better, is there any modification I'll need to incorporate or will your app disable views?
[SuperSU] Chainfire:
Well, if I do this, your app will have to (a) request root and (b) respond to the intent to turn the overlay on and off
[SuperSU] Aaahh:
Well my app does not use root, it uses a service with the run on top permission. The problem is, since its always running, when the user uses other apps, the user has trouble granting root since it trips off tapjack

I can run a broadcast receiver if your app can sent one when the popup pops up
[SuperSU] Chainfire:
Yes I have considered it, but I don't think it's the right option for SuperSU.

Regarding reboots, have you tried the procedure outlined here: http://xdaforums.com/showpost.php?p=55400320&postcount=6524 ?

Under investigation. Which recovery and recovery version do you have ?

Which exact firmware are you running on the Sprint S4 ? And which recovery and recovery version ?
[SuperSU] Chainfire:
Not needing root does not prevent your app from requesting root, now does it ? :) The first time the user opens the app, just disable the overlay (if its active), call su yourself, then re-enable the overlay. You can even detect if SuperSU is installed first.

Point is, I'm not going to send anything to an app the user has not confirmed root rights for, as that would be a security issue.
[SuperSU] Aaahh:
I understand what you mean,

I'm trying to make my app small, do I need to use your class for calling root?
[SuperSU] egingell:
Just call "su" from the command line. Android already has the API for command line built in to the SDK.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Chainfire:
This should trigger the su prompt (untested, though):

Runtime.getRuntime().exec("su -c id").waitFor();

Of course, I recommend using my classes as the above can certainly fail in some edge cases, but if you want to keep it simple, it should work in virtually all cases.
[SuperSU] Aaahh:
Yeah I used that in my last app, will that allow the app or is there a method for detecting the popup?
[SuperSU] cbeckstein:
[MENTION=631273]Chainfire[/MENTION]:

regarding the problem with SU 2.08 beta on my XXUBMGA SGS4:

I am running latest Philz recovery for the SGS4 and the latest KT-Kernel available for Android 4.2.2
[SuperSU] sndrdg:
Recovery Philz Unified jflte v-6.57.5

Firmware info below.

SU is "working" (granting access to previously approved apps - just can't bring up the list or log tabs content from the GUI - spinning circle). I can assist you further just tell me what you need.

Regards, Doug

FIRMWARE INFO

Bootloader Version: L720VPUAMF9

Baseband Version: L720VPUEMK2

PDA Version: L720VPUEMK2

CSC Version: L720SPTEMK2

OS INFO

Changelist: 1927016

Build Number: JSS15J.L720VPUEMK2 (L720VPUEMK2)

Build Fingerprint: samsung/jfltespr/jfltespr:4.3/JSS15J/L720VPUEMK2:user/release-keys

Build Description: jfltespr-user 4.3 JSS15J L720VPUEMK2 release-keys

Build Date: Sat Nov 16 11:11:45 KST 2013

Android Version: 4.3
[SuperSU] scoobyjenkins:
I've just updated PacMan Rom on my Pollux_Windy with SuperSU v2.08 already installed and got the update binary prompt again. Hitting the button to use recovery method didn't work, nothing happened, so cleared the app out of recents and chose the normal method then rebooted.

Tapatalked that shiznit.
[SuperSU] Chainfire:
Can you try TWRP ? Can't get my SGS4 to accept the XXUBMGA firmware flash :(
[SuperSU] JahSam:
Thanks for your work, your time and your explanation, so i think i'll back on the original LPV until apps i'd like to use were update (bye synapse and greenify ^^)
[SuperSU] mojanson:
beta supersu

Very big improvement!!!

On my lg g3 d855 i flashed the zip with a tethered recovery and it works great ! After using the tethered revovery i usually couldnt acsess supersu and i had to reinstall it every single time...but with the update everything works fine thanks dude!!!
[SuperSU] Cheater912:
Has anybody tried setting a start-up pin on the latest beta?
[SuperSU] Drifus Dreskeke:
Nexus 9 LRX21R, dirty updated from LRX21Q - patched kernel cleared, v2.27 installed through adb sideload. Running fine. :good:

Nexus 5 LRX21O - patched kernel cleared, v2.27 installed through TWRP 2.8.2.0. 100% working. :good:

Mr. Jorrit "Chainfire" Jongma was nominated for Nobel Prize in Root'n Happy category. :laugh:
[SuperSU] nightfishing:
del
[SuperSU] dream21:
Nexus 5 LRX210 root 2.27 version

adfree works

Pry-Fi works

WiFiKill does not work
[SuperSU] 0.0:
Moto X 2014 pure edition

v2.27 works. I added back the stock boot.img for my device then flashed SuperSU. Adaway and root explorer works

sent from my Moto X Pure Edition
[SuperSU] livelie:
XModGames on Lollipop

Nexus 5 Android 5.0 SuperSU beta 2.27

XModGames still doesn't work
[SuperSU] JulianJenner:
Nice. Works on Samsung Gio too! "Wonderfull" !

Redmi Note 1W Enhanched / MIUI 37.0.0 Stable Multilanguage / Tapatalk Pro 4.6.2
[SuperSU] nkos719:
can i #adb push the files to my g3 stock 5.0 lollipop?
[SuperSU] :
v2.27 working fine on AOSPA 4.6 BETA5 running on Moto E XT1022 Dual Sim... :good:
[SuperSU] mieszk3:
Nexus 5, going stock (flash stock boot) after previous root with kernel change.

BETA sideloaded in CWM 6.0.4.5, everything works great.
[SuperSU] Khaon:
nexus 10 v2.27

Nexus 10 LRX21P with custom kernel unpatched on SU v2.27: working like a charm, so far no bugs to report
[SuperSU] mirfanmian:
super on i9515 special edition

i have Samsung s4 i9515 after rooting with cf autoroot on custom rom mobile restart after 2 or 3 hours aromatically and no touch working

after updating supersu 2.25 no restart no hang my mobile is 100% working fine

thanks great team for great work :good::good:
[SuperSU] goTouch:
I am running lollipop LRX21O on my n5 and already applied root 2.20.

Can I install version 2.27 over it without problems or do I have to make a clean install and wipe everything ?
[SuperSU] Srandista:
You can install it without messing with kernel or wiping. Chainfire just ask users to try it on clean system/stock kernel for testing purposes.
[SuperSU] vacsed:
Works on my encrypted N5 with stock LRX21O, flashed with TWRP 2.8.2.0 :)
[SuperSU] käsebr0t:
v2.27 works great on latest Liquid Smooth nightly with SELinux set to strict [emoji106]