yashsingh1/xdaforums huggingface dataset:
[SuperSU] retroben:
I was told way back that,just like Magisk,SuperSU has systemless root so you don't have to nuke everything to gain root access,is this true/still true?

I read on the supersu site and saw references of systemless in features but no direct sentences saying something like "You can obtain systemless root using SuperSU which doesn't require unlocking your bootloader which deletes everything as what most other root methods have to do from the need to modify the system partition." at all.

Edit: I want root access so I can backup everything entirely for later recovery in order to solve the pesky issue of swf/flash content no longer working in any form on my SATV Pro (2015) as of 5.0.2 while it apparently works fine for someone else on either 5.0.2 or newer OTA versions.

Adobe Flash content used to work fine for me since 3.x OTA versions and on another note,I have never rooted my Shield TV Pro at all and OTA 6.3 works perfectly fine from the short time I have been using it since recently.

I tested 5.2 since it was oddly offered to me as of 6.3's release,all methods crashed,then I tried on 6.3 and still no dice.

I even tried uninstalling several apps I seldom use but still no sign of it working.

Don't give me any crud about Adobe killing off flash and please don't tell me to use Puffin either because it has several issues including bad quality and choppy frame-skipping.
[SuperSU] Ibuprophen:
I hope I'm understanding you okay...

SuperSU is Systemless Root...

The following thread reflects SuperSU System (Mode) Root.

https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120

I have a feeling that you may be confusing the 2.

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[SuperSU] retroben:
To put it simply,I want what Magisk does but wish to use SuperSU if it has the same properties as Magisk which would be that I don't touch the system partition.

Magisk can do what I want but was deemed really unstable on Shield TV.

The whole point is I want to make a full backup of all apps data including the browser cookies for retaining logins (yes I use browsers on a Shield TV via wireless keyboard and I love it) also keeping all data for all of the other apps.

I want to do this and THEN completely start over on the device to see if it fixes the issue of all swf players and adobe flash never working because of crashing since I never want to use adobe flash on my laptop since it was convenient and less of a major threat on the Android TV box excluding/while ignoring zero day bugs.

Either way if it works or not,I would then get systemless root again to restore all of my app date and regain all logins because I am too lazy to have to log in everywhere again each site I visit as a member,especially because Opera for Android crashes if you attempt to save/remember passwords which prevents saving and cancels the login.
[SuperSU] jcmm11:
Is it systemless root? Yes, absolutely.

Can you install it without unlocking the bootloader? Doubtful. Even cf-auto-root requires an unlocked bootloader. There's no way that I know of to patch the kernel externally and then flash the patched kernel, which is what you would have to do.
[SuperSU] retroben:
So I would have to just try ADB and/or Helium then with no other choice other than it wiping it all away?

Biggest issue is that Windows 10 and ShieldTV in general have had terrible track records from how troublesome it seems to be when it comes to trying either backup method before wiping everything the normal way to attempt to fix a problem that remained on both upgrades as it existed since 5.0.2 at first.

Wish me luck that it doesn't get triggered on either method,I intend to use both methods to make 2 backups just to be extra safe if either method even works,starting with the ADB attempt.

Which one,Magisk or SuperSU,would you say is best suited for a ShieldTV Pro (2015) on OTA Upgrade 6.3 in terms of stability?

All I have to go on is that Magisk was considered unstable for this device while SuperSU was recommended afterward.

I miss the old days of root exploits that didn't force you to delete everything. :crying:
[SuperSU] jcmm11:
If the Android version is 6.3 I'd go with SuperSU-SR5. It's technically a beta but it's almost certainly the last version we'll see and it's been running stable since it's release. That said, from a technical viewpoint, I really know nothing about the Shield.

I've recently, reluctantly, switched to Magisk - but I'm running 8.1 on a Nexus 5X.

As far as Windows goes - I swore off that when Vista came out (after having threatened to do it for years).

So good luck ?
[SuperSU] mielletseed:
Are you kidding!? :D

Chainfire (the creator of SuperSU) "invented" the systemless root - magisk later "adopted" the idea behind - so you are really asking whether SuperSU has systemless root or not?:eek:
[SuperSU] retroben:
I wasn't in the know about it because the existance of easy exploits evaporated and never returned.

For example,my old FireTV got rooted via Towelroot years ago and the last couple days I have recently done a full unlocked bootloader without it even wiping the storage in order to bring it to the latest pre-rooted 2018 update but with the regret of losing alt-tab access because the Fire OS devs for Fire TV are jerks since an older build and onward had it removed.

A method of rooting (like an exploit) without deleting everything again would be nice,especially if it eliminates the 3+ hours of nervous waiting for ShieldTV Pro and its SSHD at the easier risk of bricking it.

Rooting it would be worth it for a more stable Linux running on it in order to access a web browser that renders properly.

GNURoot Debian has the FireFox browser not rendering pages at all,so my only other options would be trying Limbo if it works or eventually rooting to access better chroot Linux builds.

If only there was a better Linux via proot with maximum stability and good performance.

At least you cleared up the fact of SuperSU being systemless,but sadly both still wipe storage and all apps.

Its gonna take ages to get everything backed up and restored.

My plans are to backup somehow then do a factory reset to see if a clean slate of 6.3 works for fixing lost access to swf players,and if it fixes that,I may as well get root if I can stomach the long wait then customize many things and see how the current best Linux armhf install performs on a mildly overclocked ShieldTV Pro.

I might have to get root afterward if I want all of my stuff restored such as apps and the data for login cookies.
[SuperSU] partcyborg:
The converse is true: to root using system less you have to have an unlocked bootloader, because setting up systemless requires that you edit your boot.img to change the fstab.

The fact that the new owners dont understand such a basic detail about their own software is concerning
[SuperSU] Prince8167:
:svetius:
[SuperSU] jugoslavpetrovic:
Did you guys continued development after Chainfire left it? Just curious, nothing happened since...
[SuperSU] Ibuprophen:
Technally CCMT (aka on XDA as [MENTION=7678190]SuperSU Release[/MENTION]) has taken over for [MENTION=631273]Chainfire[/MENTION] but, apparently they haven't been continuing with the development (without knowing what has/have/had been going on behind the scenes).

The following were the last 3 posts from Chainfire that should further answer your question. I don't believe that anybody but, Chainfire and/or CCMT can really state/clarify anything on a "definite" level.

https://xdaforums.com/showpost.php?p=74043289&postcount=11308

https://xdaforums.com/showpost.php?p=75024588&postcount=11735

https://xdaforums.com/showpost.php?p=75028239&postcount=11744

I just keep using what has been working for me (so far) but, what works for one doesn't mean that it'll work for everyone.

So far it's been the extraordinary "Member to Member Guidance" that has been keeping this development alive. This is an AWESOME example of why the XDA Forum is so strong!!! :)

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[SuperSU] limjialok:
Hi, I installed v2.82 on my xiaomi note 4x running 8.0 ROM. I keep losing room every once in a while. Is it normal? SU app keeps getting uninstalled and after I installed su again, it tells me that my phone isn't rooted
[SuperSU] weedbackup:
goods

man its very best supersu
[SuperSU] jugoslavpetrovic:
Has the development of the SuperSu stopped?
[SuperSU] DB126:
There has been no announcements or communications from the current SuperSU owner for more than a year. You make the interpretation.
[SuperSU] jugoslavpetrovic:
So, what actually happened then? They brought it from chainfire for what? It makes no sense. At least they could make whatever announcement to public, I am sure they are capable of doing it even in simple form. Nonsense.
[SuperSU] DB126:
New owners can make whatever business/technical decisions they choose including suspending communication/development/support. No capabilities were depreciated with the transition; product retains all features that were available when purchased. [MENTION=631273]Chainfire[/MENTION] made no promises regarding perpetual development or support. In short, you got what you paid for. Do I like what is happening? Absolutely not! But there is nothing "we" can so short of voting with our wallets should the new owners present another consumer offering for consideration. A two word rebuke immediately comes to mind.
[SuperSU] jugoslavpetrovic:
Yea, I know they are not obligated to do anything but my opinion is that they could at least. Vast of devices are running with that root and it's kind of big deal considering safety and security of data. I see no issues with latest beta build so far, the SR5 runs great on my side but who can tell if it should be updated with security since then.
[SuperSU] jcmm11:
I suspect that they're using it for there own purposes but have no desire to continue supporting it externally. If you're worried about patches etc, or if it stops working, there's always Magisk. I made that move, reluctantly, when I moved to 8.1 - but it's working fine. I really liked SuperSU though.
[SuperSU] jugoslavpetrovic:
I have not very well experience with magisk back in the days when I tried, some builds ago. I was loosing root after boot, don't know why but maybe I could give it a chance again with latest. Anyway for me SuperSU was great always.
[SuperSU] jcmm11:
Like I said I really liked SuperSU but with it being dead for all practical purposes I figured it was time to move on.

I'm running the 16.3 beta of Magisk and have had no issues so far. (Nexus 5x, Validus ROM, Franco kernel)
[SuperSU] DB126:
If you like SuperSU (suggest 2.82 SR5) stick with it until it no longer meets your needs. Works on the vast majority of devices and ROMs through Android 7.1.2. A fair number of Oreo users report successful outcomes; others not so much. The latter group usually finds some level of zen with more recent Magisk builds. While the latest is v16.x you might find 15.3 a better solution. See Magisk threads for details.
[SuperSU] jcmm11:
I agree with this. If I was still running 7.1.2 I'd still be running SuperSU. I didn't even try it on 8.1 though. Just figured I'd bite the bullet now rather than later.

I'm curious why you say 15.3 might be a better solution (when I switched it was already 16 I think, and 16.0 is the latest stable). (If I were to go backwards I'd probably go to 14.2/3 to get flashfire back)
[SuperSU] DB126:
- limited support for v16 builds which were released just prior to primary developer's military deployment

- issues raised in support forums that suggest the same level of QC was not applied to v16.x branch (likely due to developer time constraints)

- no new capabilities, features for bug fixes in v16 branch that are of immediate (personal) interest

- I put a high value on rock solid stability and will only move forward when benefit/reward outweighs potential risk and time investment
[SuperSU] NYLimited:
Just as a small aside, I have switched to Magisk (latest release) a while ago and had ZERO issues myself. The SU portion works without a hitch for me, the systemless part means I get to use Google Pay all the time now and AdAway works without patches. The added modules give me extra flexibility if I want it.

I had no issues with Chainfire - I have registered most of his software, including things I couldn't even use simply to support him. He also worked with Magisk developer on systemless if I understand correctly. The bottom line is that Chainfire is not working on this product and, as far as I can see, this is a dead (or near dead) product - next month will be 1 year since the last release. A year is a long time in this world.

Take this for what it may be worth from an ardent Chainfire supporter and current Magisk user.
[SuperSU] DB126:
I too had ZERO issues on the two devices in my small portfolio that use Magisk (15.3 core with latest manager app plus a few modules). The balance remain on SuperSU which includes representation from KitKat to Nougat. Magisk is a fine offering that will only get better with time. SuperSU is the Model T of generic root managers. Great in its day.
[SuperSU] jugoslavpetrovic:
What would be the safest way to switch to magisk from supersu?

Im not sure but I think when I didty flash my rom I loose the root so do I have to đake some other steps beside? I have SR5_2.82 supersu now.
[SuperSU] DB126:
Uninstall SuperSU (search the thread for link to 'unsu' tool) and then proceed with Magisk.
[SuperSU] jugoslavpetrovic:
I already have unsu.zip.

Thanks
[SuperSU] NYLimited:
The only thing I could add is that I like to flash an original copy of the boot.img (when I have one) in TWRP before I flash Magisk. On devices which have gone through a lot of changes/updates/whatnot it is possible that the original boot image can no longer be restored by SuperSU and, i my opinion, having Magisk modify an already modified image can be.. er.. not always the best thing. And, whatever you do,

don't forget your backups!!

:D
[SuperSU] partcyborg:
Magisk is not a reasonable alternative. Devices with locked bootloaders are not supported by magisk and it is impossible to install it on them. There simply is not a system root alternative at this time.

Wow between this and flashfire being deprecated chainfire is really putting those of us with locked bootloaders in a bad spot ?️

I recall that someone is working on a fully open source version of supersu. Im going to look into it and see if it's ready for some real world use and also offer to help with development.

If/when i find out more i will update the thread
[SuperSU] cnjax:
I've have also read a lot of people are using phh's superuser
[SuperSU] spainter:
Even with Chainfire being gone as long as he has, I will bet he can still close his eyes and see every line of code he wrote for SU
[SuperSU] DB126:
ChainFire sold SuperSU; "putting" is not applicable to that product. Hopefully FlashFire development will resume if/when CF opts to reengage.
[SuperSU] Ibuprophen:
Just as an FYI for those who may not be aware...

Please see the following post that should be helpful regarding the last position where [MENTION=631273]Chainfire[/MENTION] stands.

https://xdaforums.com/showthread.php?p=75773031

As for CCMT... I can only suggest that you take a look at the following post that has, probably, all the CCMT information there is (ie... Mailing address, email, etc...).

https://xdaforums.com/showthread.php?p=74416261

I agree with you all regarding the stagnant position regarding the SuperSU and the, apparent, halt on the further development from CCMT.

I hope this information is helpful and provides some answers to your questions.

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[SuperSU] SacredDeviL666:
Thread cleaned.

Please stay on topic :highfive:

Thanks

SacredDeviL666

Forum Moderator
[SuperSU] pkelly517:
Aww! I missed all the drama.

I'm sure there will be more.
[SuperSU] partcyborg:
This is exactly what i was thinking of, thanks.
[SuperSU] ktmom:
Y'all are complaining that SuperSu is not being supported but you want to go to another root method that is not being supported... and the developer, phhusson is recommending Magisk. [emoji12]

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] partcyborg:
I dont know who "y'all" is referring to but im going to assume its not me, as i literally said in my (now) immediately previous post, that Magisk does not support locked bootloaders, so using it is a non starter. Phh also states he is not personally providing support, but the code is open source and patches are "always welcome", which is pretty much the opposite of the supersu situation.

Actually come to think of it, im not sure who "y'all" could even be, as no one has been "complaining that supersu is not being supported" at all, at least in recent post history. There have been comments about all source code holders seemingly evaporating from existence, making even "supporting" yourself and your rom users yourself impossible, but that's not even close to the same thing.
[SuperSU] cnjax:
Wasn't complaining, just mentioned another root option for others to look into.
[SuperSU] danbro2:
I installed the SuperSU Zip file via TWRP and it soft bricked my phone. It's an LG Optimus L90 D415 and whenever I boot it up it gets stuck on the white T-Mobile screen. Is there a way to fix this without wiping all my data?
[SuperSU] jcmm11:
Install a stock boot image. Should be a gzipped backup in /data if you don't have a copy handy. Or just try installing SuperSU-sr5 over the current install. https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page1194
[SuperSU] Meditating_Apes:
Wrong hash code for v2.78 apk

FYI: According to HashTools the actual MD5 hash code for the v2.78 apk on SuperSU.com is 6C0FA9509866952AED58E06DE6BECA10, but the site shows the hash code as fcdc5c1e081d81e2e31be4d26dc37bd9
[SuperSU] DB126:
Confirmed. Reflects yet another blunder (casual indifference) by the current SuperSU owner, Coding Code Mobile Technology.
[SuperSU] spainter:
Due caution should always be observed, and backup, backup, backup.
[SuperSU] ktmom:
FWIW, many of these downloads are still available through Chainfire's G+ page. There is an index of posts available on his website.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] hammi1:
Hello everyone,

I had set a PIN on this SuperSU version, which was systemless, and have now forgotten it. As it is systemless, the pin code fle should be in /su/etc, though I cannot access this through recovery (TWRP), I can only see it on the booted Android, where I of course can not remove it.

Is there a way to get to that pin file in Recovery?

EDIT:

I have found that I could mount the /data/su.img file within Recovery. I had done so using

mount -o rw /data/su.img /mnt/temp1

and removed the pin file from there. Sorry to disturb anyone who was notified about the issue.
[SuperSU] nunopenim:
No worries, it's a solution for users that might face a problem alike and cannot find it.
[SuperSU] KaMyKaSii:
Try the beta version of SuperSU, 2.82-SR5. If it does not work, I think you should go to Magisk.

https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post55256620
[SuperSU] ktmom:
I thought LOS has it's own root zip. If that is right, you probably need to search on what to remove in order to install a different root solution. It seems to me this has always been the case with CM/LOS.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] Ibuprophen:
Your correct! :)

The Lineage Team just posted the one for the LineageOS 15.1 and the following thread post was by myself announcing it.

https://xdaforums.com/showthread.php?p=76252295

I hope it helps... :D

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[SuperSU] AnshRosenberg:
Work in treble roms?

Enviado desde mi XT1635-02 mediante Tapatalk
[SuperSU] Wolfcity:
Try.
[SuperSU] cnjax:
FYI

https://plus.google.com/+Chainfire/posts/ZVDG2SnmgM5
[SuperSU] Duncan Idaho:
So, I need some help. I want to unroot my device thats running Paranoid Android, but it and Cyanogen mod 11-12 seem to be running SuperSU in survival mode. It keeps wrting to / the SuperSu folder. I am curious on how I can remove this thing permanently.
[SuperSU] Badger50:
Search for unsu. Kinda like this :cool:

https://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703/post75115924
[SuperSU] Duncan Idaho:
That doesn't works, I already used unsu and its not giving me any results, when I reboot into Paranoid Android the folder is simply rewritten in /
[SuperSU] Badger50:
I don't know what device you have, but I'm sure there's an adb way to do it, or maybe clean flash your devices stock rom, and the PA if you want to stay on it. Does dirty flashing your rom not remove it, or is it pre-rooted?
[SuperSU] Duncan Idaho:
Kindle fire HD 7", I can't find a clean non rooted stock firmware for it.

It wasn't pre rooted, I rooted it.
[SuperSU] Badger50:
Nothing on the matter in your device forum?
[SuperSU] Duncan Idaho:
Nope, the links are all dead and no backup AFAIK.
[SuperSU] Badger50:
Bummer man! All I can suggest then is to dirty flash your rom, or search for the adb method I suppose.
[SuperSU] madbat99:
The paranoid Android rom you flashed wasn't pre rooted? Then wipe /system and flash the rom (paranoid Android). Which won't wipe your data.

Or open SuperSU app and uncheck survival mode.

Or, as stated before, clean flash. Wipe system, data, dalvik and cache and re flash your rom

You said PA and cm11 and 12 for your device are running SuperSU in survival mode, that sounds like the ROMs are pre rooted if you didn't install SuperSU on them yourself. That's what the previous post was asking when they asked if the room was pre rooted.
[SuperSU] Duncan Idaho:
Yes they were pre rooted, but I am attempting to make an unrooted PAA b y removing from the XBIN folder pre flashing the SuperSU and Busy Box and to my knowledge that should unroot it.

To be exact inside the zip there is boot.img, system and Meta inf.

Inside system there is a folder called Xbin. It countains busybox and supersu.

There is a bigger issue, the SuperSU of PAA conflicts with the google play SU causing it to display the error that the binary is occupied. So I am not sure if disabling survival would amount to anything, assuming I am able. Because I think thats a paid feature.
[SuperSU] pendor24:
http://drivers.softpedia.com/blog/Download-New-Firmware-for-Amazon-s-Kindle-Fire-HD-7-HD-8-9-and-2nd-Gen-428161.shtml

google is your friends
[SuperSU] Duncan Idaho:
If I flash in 7.4.8 will it affect my bootloader/twrp?
[SuperSU] pendor24:
Hello

I do not know I do not use this material at all.

look in the section of your material. at the bottom we will tell you better (without being hs)
[SuperSU] madbat99:
Sorry I don't use any fire tablets. Most roms aren't pre rooted anymore because not having root has become desirable. Removing root from pre rooted ROMs can be problematic. If a playstore update is causing issues, then start over with a clean flash of your rom. There are methods of hiding root on systems that old. But removing it safely, and effectively, maybe not. You can break root, but it may still be detectable by safetynet and other apps.

I would say, clean flash your rom, and use one of the suhide options out there.