yashsingh1/xdaforums huggingface dataset:
[SuperSU] jdegreef:
And now you have problem with your payment :D

How did you manage to have so many problems ?

I wish you 2017 being a more successful year for your android experience ;)

Btw, happy to read that you succeed changing you battery, flashing a new rom and succeeded rooting your phone.
[SuperSU] ktmom:
You really should be getting help from N10 users in the Here's the warning I get from TWRP. Should I pull the trigger anyway? Why does it say it's incompatible? Maybe it's just surprised to see Android 6 on a Nexus 10? Does SuperSU work on Android 6?[/QUOTE]

There is a slew (technical term) of reading you need to do before you clobber your device. Amongst the things you don't know that you don't know is that MM introduced changes to security. This affects the ability to root.

Had it occurred to you that posts like this in a dedicated development thread for a subject that has little to nothing to do with N10s might be why people are less than courteous to you?
[SuperSU] permutations:
People here are almost always less than courteous (to put it mildly), which is why I read a lot more than I post. This site draws a lot of people who enjoy answering questions with, "You're a know-nothing moron below responding to." It's a very clique-y site. If there is any way to say "Gotcha!", "You didn't research enough before posting!", "You're asking the question wrong!", or "You're asking the question in the wrong place", someone here will do it with sadistic delight and in the most condescending tone possible.

I posted my question in exactly the right place. I tried to upgrade SuperSU from 2.65 to 2.79, I got into a bootloop, then I lost root permanently (until I completely wiped my device and started again). I only mentioned what device it was because I thought it might be relevant.

When it became clear to me that I needed to wipe my tablet to regain root, I chose to upgrade to Android 6. Why do all that work with no payoff? There's nothing wrong with my mentioning I made that choice. I didn't ask anyone here to help me upgrade to Android 6 - I just did it. Nor did I ask anyone here to help me swap out the dead battery and install a new one.

There was nothing at all wrong with my mentioning that I had PURCHASED SuperSU to support Chainfire's work. I purchased his StickMount utility, too. He's a very good programmer. My purchases weren't recognized until I went into the Google Play Store and downloaded the Pro versions of these apps. Maybe mentioning this necessary step was a good reminder for someone else. Maybe mentioning the Pro version reminded a few people that they should support Chainfire with actual MONEY, too.

These incessant criticisms of me are just the Gotcha game so many play here. I feel sorry for people who need to (try to) make others feel small so they can feel big. It's not a good character trait. Maybe you're very young and you'll grow out of it.

Luckily, that's just 80% of the people here, and not 100%. Thank you to the people here who helped me, without snark, to understand what went wrong with my SuperSU upgrade so I could fix it.
[SuperSU] culiacanazo:
I'll tell you what a brick is.

When not even J-tag can help you, now that's a brick like i did to this baby a while back

Edit i messed up the screenshot uploading process but obviously I'm not talking about the one I'm using right now
[SuperSU] culiacanazo:
Just the teacher in me, nothing personal, moron speaks of a character, not abilities, one can be a genius moron

---------- Post added at 12:46 AM ---------- Previous post was at 12:34 AM ----------

And it does work, just saying

---------- Post added at 12:52 AM ---------- Previous post was at 12:46 AM ----------

Maybe I'm late to the party and you've already been addressed, I'm catching up.

•But older versions are not that hard to find if you ask your 7-year old nephew AND straight from Chainfire.

•Chainfire IS involved still

•Lol! ("i don't want CCMT so i download the amazonaws one")

Keep up, man, it's been a couple years, where've you been?
[SuperSU] egingell:
PSA: Hard brick vs soft brick.

Hard brick: not recoverable with all data lost except what's on the external sdcard.

Soft brick: recoverable with possible loss of data.

Flashed bad ROM. No notification light, no recovery, no download, no system. Hard brick.

Flashed correct stock ROM; however, that ROM has a bug that sometimes fries the board. Only blue notification light. No recovery, no download, no system. Hard brick.

Bootloop (defined as being stuck on the bootanimation or bootimage). Can still get to recovery and download. Soft brick.

Reboot loop (defined as the device boots into the system as normal, but reboots shortly after and repeats). Recovery and download still​ available. Soft brick.

Boots directly into recovery, bootloader, or download. Soft brick.

I've lost four phones to the hard brick. I've recovered from soft bricks numerous times.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] culiacanazo:
I recently ended up without root as well, due to SuperSU, from either it or cm's built in, but since i didn't file it and i quickly fixed it due to not being any major, supply-disrupting, crisis-causing chaotic wreck of an emergency, i don't remember how i fixed it, which leads me to believe those reports must be from newbies (not in a demeaning way) and should be taken with a grain of salt
[SuperSU] culiacanazo:
Thank you! That should be a mandatory read before being allowed to post :silly: allow me to upload what i intended to earlier and failed

(I miss that baby)

It's the only one i haven't been able to CPR it

EDIT: I guess i suck at uploading screenshots :eek:
[SuperSU] egingell:
FYI: If you flash 2.65, you'll end up systemless. That's where it all began.

Tapatalk uses its own server for uploads and I have never had a problem.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] culiacanazo:
I'll check it out, thank you!
[SuperSU] vandyman:
Is this the super user stable thread?

I have not read much about su topics in the past few pages! Hmmm

Sent from my Nexus 5X
[SuperSU] Mesmurized:
This is it!
[SuperSU] vandyman:
Yeah, I was being a smart arse.

Sent from my Nexus 5X
[SuperSU] annoyingduck:
I just read this whole reply and I gotta say, it's very easy to slam users if your "in the know". I follow as much as I can, but life does step in. If you are alive and haven't been glued to the forums, the whole systemless vs system install script that has to be entered IS ABSOLUTELY NOT clear as day. I'm not bashing or causing trouble, I just want it to be clear that some things aren't as I obvious as one may think. I think the users questions were valid, and not lazy in nature because the changes aren't obvious and really are so much different without any clear warnings towards them. I have yet to find an exact description from the supersu devs in a main OP describing the adb command in detail, it's always buried deep and one "must know" prior to flashing supersu whether or not to run the script command via adb or via twrp or they would have to know to look for whether or not to even think about it. I still don't know if I'm supposed to do it on the 4 devices I keep custom.

The work here is incredible, but very confusing at times with the whole system/systemless options - especially between older/newer devices. Be kind to everyone, I'm following as much as I can, I search and search always, and I still find it hard to get the answers.
[SuperSU] grep_i:
You do understand that this is written this way due to the guys own condescending tone towards this forum and the users on it who were trying to help him out.

If you read my post which you quoted thoroughly, you also see I came with suggestions and was not only bashing.

The guy failed to come up with log files even though it was asked.

With his merely vague story there was no simple way to help him out.

And last but not least he used some of the advice given in my post so it was not bad advice and now he even solved the problem him self, thumbs up for the guy

[emoji106]

PS nobody called him a moron I have no clue where that comes from.

We were only stating the rules of the forum and that his tone was a little strange for someone who needs help.

And yes you are right these things can be quite difficult so that's why you have to study this things with full attention as they can go deep into your device and break things if you do not do things right.

That's why everybody keeps on telling to read up and study hard on these things.

And another thing I'm alive and not glued in this forum I'm not here everyday although I try to but due to being alive that's not always possible but still I managed enough time to figure this things out with the help of the forum.

If I can do it without being someone special, others can too I guess when they put their mind to it.
[SuperSU] annoyingduck:
Hopefully you noticed your own Freudian slip of the word moron (which you used just now to describe that user, and I did not). I never stated, nor implied that, which sums up my diatribe. Please do not reply, it's not an attack I'm giving here, it's a statement of what some may consider obvious, others do not. Please look up my started threads, I choose as much detail as possible and try to perceive the unknown that I may not know that users may not know as well. I'm not as smart as the amazing people here, but I do understand common logic, and lately here in xda the tone really makes me appreciate how different other forums are. I'm not responding after this, and I appologise, but this really needs to be fixed here.

Thank you for supersu and the continued development. I look forward to everything down the road.
[SuperSU] Mesmurized:
Happy New Year :)
[SuperSU] permutations:
There's clearly some sort of bug in the upgrade process since there are multiple reports of permanent loss of root (short of wiping the device and starting again) after upgrading from 2.65 to 2.79. I experienced it myself, and I saw it reported across the internet when I was googling for a solution. It has nothing to do with being a "newbie". (((rolling eyes at the incessant compulsion to snark here))) This is a bug report that Chainfire may choose to follow up on or not. He's his own boss.
[SuperSU] culiacanazo:
?

What part of the world you live in?

Anyways, thanks for breaking up the ice and the argument preceding you and happy new year to all
[SuperSU] NLBeev:
M. Monroe to A. Einstein:

' a child with your brains and my beauty'

A. Einstein to M. Monroe:

'Beware.... when it's the other way around'
[SuperSU] jdegreef:
Easy to quote only part of a discussion to prove people wrong !

BTW, I don't really understand how your latest post did help people solving their Supersu problems.
[SuperSU] grep_i:
Nice story, still don't understand the moron part even after this post in which you used the word yourself to describe that I used it to describe another user but instead I was using it to say that I don't know where he picked it up as nobody called him that.

There are different kind of forums and maybe this one is not to your liking that's always possible and your entitled to have your own opinion.

Giving as much detail as possible and not choosing as much detail as possible is common in this thread.

Of course not everyone knows the same and that's understandable but still you have to ask nicely for help and you will see that everybody that knows the answer is willing to help.

But as I now understand I'm wasting my time here as you won't even answer anymore after writing such a post.

Anyways I wish you the best for the upcoming year 2017?
[SuperSU] NLBeev:
It's OT like your post; you could try to see it as critics including humor.

Imo nobody is wrong.

EDIT

Just see that we are neighbors;

Happy 2017 to all[emoji322]
[SuperSU] culiacanazo:
•I don't know how much reading you do but I read "A proper quote includes only the relevant paragraphs" quite often...

•Concise, brotha! Someone states that "x" product doesn't work with "y" product, only "z" works with "y"... If it's a false statement, why not correct them so other people can benefit? I really would love to hear your answer.

•my latest post was not created with helping anyone in mind, just out of the spirit of the season and to reply to someone who wishes people well... So: if you're right, i won't see any happy new years tonight or the day after in all of XDA
[SuperSU] grep_i:
It's already said in here but I love to say it again.

Happy new year to everyone ??

---------- Post added at 03:46 PM ---------- Previous post was at 03:38 PM ----------

https://vimeo.com/197611883
[SuperSU] ldeveraux:
Do you have any thoughts you DON'T type here? It's getting real tired.
[SuperSU] permutations:
I stand up for myself when I'm insulted. Stop insulting me, and I'll have nothing further to say, since my SuperSU problem is solved.
[SuperSU] DB126:
Excellent. Happy New Year, mate.
[SuperSU] permutations:
Happy New Year!! :)
[SuperSU] Ibuprophen:
I took out my oldie (but still googie) Motorola Electrify MB853 device and it has an ancient Android v2.3.5.

With that said, i obtained root access and, while in the Play Store, noticed that the Free version of the SuperSU 2.79 was considered compatible but, the SuperSU Pro Key (i purchased a long time ago) is considered incompatible?

To be honest, i didn't expect either of them to be considered compatible but, I'm not sure if [MENTION=631273]Chainfire[/MENTION] had just listed the Pro Key appropriately and just forgot about the Free version but, I'm not sure if it was meant to be the other way around.

I have another Superuser app (as well as another BusyBox app) i owned for quite a while that's intended for the older Android versions but, noticing how the SuperSU & Pro was listed with a minor conflict had thrown me off a bit. The Pro Key is specifically for unlocking the pro features within the Free SuperSU app only.

Can [MENTION=631273]Chainfire[/MENTION] please clarify the Compatibility conflict for me?

Thanks a bunch!

Sent using the d2vzw Communicator from the Bridge of the U.S.S. Enterprise (N.C.C. 1701).
[SuperSU] jdegreef:
By following this thread on a daily basis I know how you struggled to fix your problems.

I was sometimes frustrated by not having solutions to offer.

But you did go on despite what was said and finally solved your problems.

I'm not sure who is the moron in this story !

I wish you the best for 2017. As to a bunch of people dedicated to help in this thread.
[SuperSU] CyberZeus1977:
Happy new year!

Sent from my interstellar 6P
[SuperSU] chudy_85:
Happy new year
[SuperSU] pkelly517:
Yay!
[SuperSU] Pkt_Lnt:
https://www.xda-developers.com/root/
[SuperSU] Ibuprophen:
It's how plants and trees get their nourishment.

https://en.m.wikipedia.org/wiki/Root

Sent using the d2vzw Communicator from the Bridge of the U.S.S. Enterprise (N.C.C. 1701).
[SuperSU] sev7en:
Good afternoon,

I would like work around the rooting of the Xiaomi Amazfit. It is a MIPS based watch but where I can find the SU compiled for that architecture?

Thanks,
[SuperSU] egingell:
A link to the right place to seek help is literally one post above yours.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] sev7en:
Thank you, which one is the one compatible with MIPS architecture? Many needs the bootloader mode but I cannot reboot the device in that as it shows that: error:closed

ADB DEVICES works well and I can also access to the shell.
[SuperSU] egingell:
There's a forum for (most) every device. Find yours and ask there.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] ale5000:
Is this compatible with CyanogenMod / Lineage OS 14.1 (based on Android 7.1.1)?
[SuperSU] shaggyskunk:
It is for me.

Sent From My SM-N910W8 ??
[SuperSU] anup807:
is it compatible with Oxygen OS 4.0?
[SuperSU] ulxerker:
It should, just check it out.
[SuperSU] doppelhelix:
Yes
[SuperSU] superresistant:
Hi, I installed SuperSU from the zip you provided in recovery mode but the app tell me to update (the SU binary needs to be updated Continue ?).

I'm on a fresh install of CyanogenMod 13.0-20161013-ZNH5YAO21L-klte. Android 6.0.1

The normal install won't work either.
[SuperSU] jdegreef:
What's the name of your zip ?
[SuperSU] superresistant:
SuperSU-v2.79-201612051815.zip
[SuperSU] jdegreef:
That's the last stable version.

Did you have any error during the flash process because if it worked SU shouldn't ask you to upgrade ?
[SuperSU] PAGZLY:
The problem:

It is not possible to switch SuperSU the system.

Android 6.0
[SuperSU] egingell:
That kinda defeats the purpose of systemless.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] PAGZLY:
How to solve the problem?
[SuperSU] tag68:
What is the problem? Is anything not working?
[SuperSU] ridobe:
http://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703/post70327081
[SuperSU] egingell:
It's not a problem. It's working as intended. Is there some specific reason you need to have it moved to system?

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] culiacanazo:
I thought the problem was something about binaries not updating
[SuperSU] lordmartyn:
To one plus 3t users who just upgraded to nougat or OS 4.0 superuser unfortunately blocks sim radios or there are issues there. WiFi is fine though. Shame really as I like SU. Looks like I'm waiting for an update...
[SuperSU] denilriveraa:
I can not update the binaries always from error
[SuperSU] permutations:
Thank you! :)
[SuperSU] Ja_som:
http://xdaforums.com/apps/supersu/support-update-failures-t2907365/
[SuperSU] grep_i:
Wow you're good man I think it's more than six months now that you keep repeating this as answer.

Everytime answering this same question with the same answer without getting agitated, respect [emoji106]
[SuperSU] jdegreef:
[MENTION=631273]Chainfire[/MENTION]

Does it mean that all installation/update problems should be directed to this thread ?
[SuperSU] mcscout:
SM-G800H

I have a Samsung Galaxy s5 mini duos mit Android 5.1.1. Now it's an firmware-udate to 6.0.1 aviable. Root with SuperSu is posible?
[SuperSU] culiacanazo:
Why would you lose it? And it is with the S5, i really fail to see why it would be more difficult with the mini
[SuperSU] mcscout:
I have no idea. Thats why I ask.
[SuperSU] culiacanazo:
Well plain and simple, it is possible up to nougat, which i doubt you're getting, so, mind more info? Such as Knox state to begin with, to know if we go left or right?

Might wanna add current root state (not only nay or yay, but system vs systemless, recovery type? You know, the usual... and if you don't, then you need to head into your device's forum for rooting
[SuperSU] mielletseed:
I'm using this configuration for months. But why did you doubt?
[SuperSU] celoxocis:
Im trying to install SuperSu using TWRP but i keep getting "Read-only file system.

here is my SuperSu install Log, pastebin: http://pastebin.com/4YMZAhEy

I'm thankful for any pointer in the right direction.
[SuperSU] Yeti47:
In TWRP go into mount and untick the 'Mount system partition read-only' checkbox. Caught me out as well... ☺️
[SuperSU] anilkumar121989:
Thanks.
[SuperSU] RandomPooka:
Yeah, that announcement was forever ago
[SuperSU] 2159687:
I know, but this thread is opened by Chinese. Only CCMT can really understand my meaning.
[SuperSU] KbaB.BroS:
XDA rules is enforcing its users to use English no matter the ethnicity.
[SuperSU] haseoxth:
To be more specific, all Chinese speakers can understand what do you want to express.

But actually this thread also belongs to XDA forum, so rules come first ;)
[SuperSU] digezter:
sorry, i have a question. This SuperSU file can be flash via zip for Redmi Note 2 ?
[SuperSU] diongdyh:
SuperSU works on almost every device. Backup before flashing if you're unsure.
[SuperSU] m0han:
yeah. [MENTION=7678190]SuperSU Release[/MENTION] agreed to this when he/she/it/they joined up and created this thread. :D
[SuperSU] digezter:
one more question, after success install via zip. but nothing happen to my phone, supersu still not appeared on my phone.

Note : Redmi Note 2 MIUI 8 Chinese Stable Version
[SuperSU] Jessy142:
Thank you!
[SuperSU] ali nz:
Where is chainfire?:D
[SuperSU] egingell:
He posted less than a day ago. I don't know if you knew this, but even programmers need to sleep.

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] Federacion:
So after the supersu update Xposed users have to reinstall it manually? Am I correct?
[SuperSU] t33n:
Don't use this zip file on Moto G4 Plus

Today I just unlocked my Moto G4 Plus, Installed twrp and I downloaded Supersu file from this thread OP post. And Get stuck my phone at Moto Logo. What I did I go to old thread SuperSU Old Thread and downloaded latest version, Install via Sideload and boom. Device boot again. So something wrong with this supersu version.
[SuperSU] RandomPooka:
Only if you reflashed your entire rom
[SuperSU] Federacion:
Really??
[SuperSU] RandomPooka:
With system based xposed, yes. If you're using systemless or magisk, that may change. But, supersu doesn't overwrite xposed. Flashing your rom would. Or, in the case of systemless, wiping data would likely destroy xposed and root.
[SuperSU] Federacion:
So I can't do anything to update supersu and continue to use Xposed right now! Good to know.
[SuperSU] ciopik:
Zip version can't install on my Z5C but I need install by TWRP
[SuperSU] grep_i:
I had the same problem and also had to reflash my custom kernel too.

I guess that's because SuperSU patches stock boot.img so first it restores to stock kernel and because of that your systemless Xposed is gone too works with patched boot.img too.
[SuperSU] Federacion:
So if I update and then flash only custom kernel will it work?
[SuperSU] celoxocis:
Yeah I tried it. Still doesn't work.

Any other reason it could be Read only?
[SuperSU] Yeti47:
Sorry, that's the only reason I know.
[SuperSU] culiacanazo:
Some guys manage to get into some unreproducible problems, it bewilders the question mark out of me...
[SuperSU] egingell:
Problems without logs bewilder my question mark.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] jdegreef:
[OT] This time I agree with you ;) [/OT]
[SuperSU] Thiha Htut:
Su Binary update

I very thank fot

:):)

---------- Post added at 04:23 PM ---------- Previous post was at 04:17 PM ----------

I very thank fot

:):)
[SuperSU] damnitdannn:
Hi. I'm having issues installing SuperSU through zip. Every time I flash it, it doesn't install the app and when I ddo have SuperSU app installed thru play store, flashing tthe zip uninstalls the app. Any way to fix this cuz I used tto be rooted up until idk what day and it disappears.
[SuperSU] grep_i:
One tip to you please do not post whole log files as text rather upload as file or use hide tags if insisting on posting as text.

Such long log file text is quite hard to read on mobile devices.

I guess you answered your own question.

Try to symlink SU SYSTEMLESS binary to systemmode binary and see if that solves your problem if not please replace this app with a more recently updated one cause honestly an app that is working this way is not updated for a very long time and I would toss it aside for everyday work.
[SuperSU] l7777:
Seeing some strange behavior that might be TWRP related. I have a Pixel that I just updated to the January build with fastboot update. When trying to re-install TWRP 3.0.2-0 RC1 and SuperSU, supersu kept trying to install in system mode instead of systemless. I did create the .supersu file with SYSTEMLESS=true but that made no difference. Previously the device had TWRP 3.0.2-0 Alpha2 and SuperSU. After several attempts and various re-applications of the google factory image I tried to install supersu with TWRP Alpha2 and it finally did a systemless install of SuperSU. Any ideas?
[SuperSU] KaMyKaSii:
First, I think you'd better use SuperSU beta v2.79 SR2. Second, Chainfire has already said that because TWRP is installed in boot.img, it and SuperSU can not work together. You should have just booted TWRP with "fastboot boot twrp.img", not flashed. Then install the factory image again. Just boot into TWRP and install SuperSU from there. Whenever you need to use TWRP, just boot it, not flash