yashsingh1/xdaforums huggingface dataset:
[SuperSU] Tecalote:
You are right, for marshmallow you cannot use this boot.img. I dont think, you must reflash the original boot.img after unroot with unsu.zip - but I am not sure, because I dont have this galaxy phone. If you have TWRP or CWM I would make a full nandroid backup on external Storage. After you can just try to flash unsu.zip - maybe it is all you need and if something goes wrong you can recover your system with the nandroid backup to the last state. For further information you should use Google Search to find related informations to your issue. The other thing ist, how to root your phone after the update...

Sorry, I cannot more do for you. Hopefully you can solve your issue succesful. And if, leave a reply.
[SuperSU] mrjoy:
You great bro. Its enough information that is you provided to me. Thanx a lot. I will start the process later.
[SuperSU] mrjoy:
I tried but no luck. It just deleted the supersu apk but no files in system.
[SuperSU] Didgeridoohan:
If you've got a modified system you're screwed for OTAs anyway, so no need trying to unroot.
[SuperSU] NLBeev:
Launch SuperSU -> Settings - read under System
[SuperSU] Tecalote:
Hello - I was looking yesterday. You have Samsung Galaxy S5 and if you have root and Custom Recovery (TWRP or CWM?) - the Recovery comes in Samsung Roms always with Custom Kernel and Root. So it is difficult. I am not specialist in those Roms. I would in this case backup my data from the user apps with TitaniumBackup plus with the Samsung built in Backup Tool. After you need the flash Tool Odin and the newest full Stock firmware (for your phone http://www.sammobile.com/firmwares/ If the newest full firmware (same number as the ota) is not available yet, you have to wait. With Odin you can flash the newest firmware to your phone. You have to google for a good instruction. Odin must be executed on the PC, connected with your phone in usb Debugging Mode. With hardware keys the phone must boot in download mode. After you can flash. The original firmware will make a factory reset, you loose all your data, that's why it is necessary to backup before. After you boot into the system and configure your phone like first time. After you must find the root method for this new firmware, don't know, if the one you have before will work again. I would prefer a method for rooting without Odin to get no triangle.

Edit: Maybe you can also update to the newest firmware with Samsung Kies. (I am not sure if it is possible with root) But even with this method it makes a factory reset.
[SuperSU] thaidroid:
You need to use ODIN, Kies will detect that the phone has been changed.
[SuperSU] yohandesilva1:
Anyone tried this with the Final N Build?
[SuperSU] drewski_1:
By "Final" you mean dp5? I flashed 2.76 with dp5 on my Pixel C AOK
[SuperSU] RandomPooka:
I was wondering the same thing about "final" vs "Most recent Developer Preview" (DP5). I had zero problems with 2.76 on DP5 shamu/Nexus6
[SuperSU] Alxoom33:
Sure. Works as always.
[SuperSU] leroyleong2768:
can i use systemless root on my htc one m7 (flashed dirty unicorns) on marshmallow 6.0.1?
[SuperSU] viddy135:
Can I use systemless root with d852 6.0?
[SuperSU] SpasilliumNexus:
Seriously guys? Do you not know the purpose of a nandroid?
[SuperSU] viddy135:
No, but isn't there something different with the boot on LG devices?
[SuperSU] aboaboit:
I'm trying to balance SafetyNet Helper (and, by proxy, AP) and SecureSettings, a Tasker plugin which sadly seems to be not quite actively maintained.

I'm using SuperSU 2.76, TWRP 3.0.2 and the build is MOB30P on a Nexus 5.

Stock: SNH green (OK)

Root (both terminal and Rootchecker confirm root is present), no .supersu file: SNH green, SS System+ module cannot detect root (button to enable is missing)

Create file, reflash, reboot: SNH red, SS now happy (i.e., when clicking to enable the module a root confirmation popup will be shown)

Remove .supersu file, reflash: SNH green and... also SS System+ is happy, go figure!

Tried all the steps twice, each time using FF to revert to a rooted stock with my account already setup.

Bottom line: it's a lot of work but it is possile to enable S+ and still keep the system partion intact.

There's a catch, though, and I'm saving it for the end: it still won't be possible to enable the root actions of the plugin :(

So, yeah, it's either SNH/AP or SecureSettings.
[SuperSU] egingell:
Search this thread for compatibility mode. The problem is with Secure Settings not SuperSU.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] aboaboit:
That's just what I said, only with less words: in the end, you have to choose between the current mode (which will disable the root options of SecureSettings) or compat.mode (which will break SNH and perhaps AP).

From my research it wasn't obvious that those two goals were incompatible.
[SuperSU] RandomPooka:
Bump. The thing you're talking about is Bump. I want to say there are tools available that Bump during the TWRP session. You flash SuperSu, it rewrites the boot.img (causing it to be unbootable), then you flash the Bump tool and it bumps the file, allowing the device to boot again. AFAIK, the D851 is the only one that doesn't need it. The VS980(VZW-G2), VS990(VZW-G3), and LS990(Sprint-G3) all required it.
[SuperSU] osm0sis:
There's an add-on script that bumps automatically when SuperSU gets flashed. A quick Google for SuperSU bump should find it.
[SuperSU] viddy135:
Thanks, man and if anyone needs it

http://xdaforums.com/showthread.php?t=3273251
[SuperSU] VE2HRJ:
Thank you grep_i,

after a week with no issue, I root it back with TWRP (v3.02 I think) because I use apps that need it and the SD Card corrupted again.

Even if all the content is available in my PC.

Now I was tired of this, so I got the “Insanity S7 edge v3.3 for the S5” ROM and we will see.

Error "SD Card Corrupted" with:

- SM-G900W8

- OS Canadian Rogers 6.0.1

- TWRP

- SuperSU 2.76

Now work great! :

Hardware: S5 SM-G900W8

OS: S7 SM-G935F (Include TWRP, SUperSU and BusyBox) in ROM.

:cool:
[SuperSU] xXCoolGuYXx:
Does anyone know if here a zip to flash to root the sm-g360t
[SuperSU] ktmom:
Look! A device forum with relevant threads! Rooting Samsung Galaxy Core Prime (G360T)
[SuperSU] xXCoolGuYXx:
Thanks
[SuperSU] arpitgupta026:
Few issues !!

Hi,

It ran vey good when I flashed the rom and gapps .

But now when I am trying to connect my mobile to laptop and look for adb devices ,

it always shows "unauthorized" and I am no longer getting RSA security prompt also .

I have not flashed the Super SU because I tried with it and the ROM didn't worked out when I flashed .

Could you help me here asap .
[SuperSU] CVAngelo:
You're on the wrong thread if you're asking for help flashing a custom ROM! Has nothing to do with SuperSu.
[SuperSU] grep_i:
In phone settings search for developer options and remove all authorization disable debug and enable it again.

You should now get authorization prompt again
[SuperSU] desilynn79:
im not sure if i am postin gin the correct thread. i apologize in advance if not. and also please direct me to the proper one if this one isnt. Thank you!

with that out of the way....

i am very new to marshmallow.

my device is also new to the market and im am very new and doing research on the systemless root.

i am very interested in systemless rooting if i can actual do it to my device...

I have an alcatel dawn (was released july 9 2016) from boostmobile

running 6.0.1

do i need cwm or twrp to do this- not real sure on this. info i have read is confusing me.

most threads say you must be rooted to install cwm or twrp but thats the old way- not systemless...

is cwm or twrp ( or both) device specific or can i just install from external sd card in stock recovery or must i use adb?

how do i know if device supports gzip?

i really want to learn but i really dont want to do it the hard way.

this new device was to replace the last new device that factory reset and then would do nothing upon reboot...sigh

i dont want to have to replace another so soon. im leery because im not familiar with this method and have found no method to root this phone the old way due to its recent release and possibly because it is running 6.0.1

any and all help is appreciated. thank you

"smile ;), it makes you look better! and its contagious"
[SuperSU] Wolfcity:
Just in short form: Systemless root has nothing to do with flashing a custom recovery or unlocking the bootloader. Both is needed to root your device, if systemless or the old fashioned way. You don't have to be rooted to flash twrp or similar but you have to unlock your bl first.

The difference is that there are no changes in the system partition, a modified boot.img is used for systemless root which is normally flashed with a special superSU zip.

I would recommend you to take a look in your devices thread and in chainfires superSU thread.
[SuperSU] grep_i:
Just in short you are saying it had something to do with each other[emoji12]
[SuperSU] Wolfcity:
True[emoji6]. Don't wanna say something wrong, for example take a look here: http://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/
[SuperSU] desilynn79:
problem is im not finding any info on my device because it was just released july 9th....

thats why im reaching out for help wolfcity..

so again any help in this matter is appreciated. thank you
[SuperSU] TJKV:
In that case it always pays off to wait for more experienced or less risk-averse people to try stuff out with that device. They would then test stuff out, figure out, and share solid info and instructions for the rest of xda to safely follow :)
[SuperSU] RandomPooka:
You may run into a problem here due to this being a smaller carrier economy phone. Nothing wrong with that, but the number of developers working on it is going to be small, if there are any at all. Try searching for information on whether it has a locked bootloader or not, if you can use fastboot with it, and how to compile TWRP for new devices. Basically, with enough information about the phone through various means, you could potentially build a custom recovery at home and try flashing supersu. You'd be the pioneer for this device :)

Somebody has to be first, and you don't have something that's going to have a massive user base, like the Galaxy series or Nexus series of phones. It may be necessary to take matters into your own hands. Worst case, you'll learn quite a bit in the process and have a very different set of purchasing criteria for your next device. Best case, you will have been the first person to successfully install a custom recovery and root your device.
[SuperSU] iMessa:
I too have prompt for su bunary update at every boot and app start. I r/w the system patition amd it was successfuly instabled BUT problem still ocures. I have Z5 Compact, 6.0.1, BETA-SuperSU-v2.74-2-20160519174328. What should i do? Thank You!
[SuperSU] ktmom:
There is a link to the thread for binary update problems in the OP.
[SuperSU] gaww:
Did Google play update your app to 2.76? If so, you will get that prompt,
[SuperSU] iMessa:
I created new boot.img with latest SuperSU and now i don't get the prompt anymore. Thanks everyone and God bless! :D
[SuperSU] KaMyKaSii:
I have a question here and would appreciate if someone can answer me, after doing systemless root on Marshmallow the screen "Android is starting... starting apps" appears in every boot? SuperSU v2.76
[SuperSU] ktmom:
There is minimal information here, you're leaving us to guess what device, what ROM, what all you've flashed (e.g. xposed) in what order, how you flashed and what steps you took... Here's my guess.

Try updating SuperSu from the Play Store, then reboot fully (wait 15 minutes or so after you can unlock the screen). If after a second reboot your device is still optimizing apps then boot into recovery and wipe cache and dalvik cache. It will optimize again so when fully booted try rebooting (again wait 15 minutes or so after you can unlock the screen).

When your device is optimizing apps, it's basically rebuilding the dalvik cache. If it keeps doing this, I would think some app is preventing it from finishing.
[SuperSU] mielletseed:
Not optimizing but starting apps! I get the same message on Samsung Galaxy Note 8 N5100 running CM13.
[SuperSU] egingell:
The proposed possible fix is the same.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] gothicVI:
I get the starting apps message at every start-up running cm13 on my motog 2014 LTE.

However I'm sure there's nothing to worry about at all... It's just an informative message from the os...

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] animehawk82:
Which version should i install on J5 SM-J500H running on android 6.0.1

Please tell, Thanks for your help!
[SuperSU] RandomPooka:
Sdk23, latest version number. (86, I think?) and you pick the architecture that's appropriate for your chipset. Go to something like gsmarena.com and search your phone. It will tell you the cpu you have, and you can then search to see if that's an ARM, ARM64, or x86 cpu.
[SuperSU] nicolap8:
This is nonsense!

There is a stable version, in other thread, and is duty of the installer to select the right executable.
[SuperSU] mielletseed:
version 2.76 - why are you asking? It's the latest and supports all Android versions - there are no different versions of SuperSU for different devices...

What are you talking about? :D This is the SuperSU thread...
[SuperSU] animehawk82:
Wth!! Im positive that i posted this question on the Wanam xposed for samsumg mm thread
[SuperSU] RandomPooka:
Damn. I forgot what thread I was in because of the way the question was worded. My mistake.

And apparently got lucky enough to answer almost appropriately through my misunderstanding
[SuperSU] Oldsman1:
Thanks again for your help [MENTION=631273]Chainfire[/MENTION]! :cool:
[SuperSU] devilloki:
huawei honor7 TL01H cann't root

my devices is huawei honor7 TL01H ,soft ver is EMUI4.0.1 - 6.8.1,

supersu 2.60 can root,

but,

supersu 2.76 cann't root

reboot, display "boot.img is damaged"

upload log,pls help me.

ths.
[SuperSU] ktmom:
Upload the log to pastebin then link here.
[SuperSU] grep_i:
You have to be very precise if you need help from here.

By reading your log you are trying to flash v2.74 not v2.76

If you want to successfully flash v2.76 you have to restore to stock boot.img and just to be absolutely sure restore to stock system.img too and if you want to be absolutely very very sure just flash stock firmware before flashing Supersu v2.76
[SuperSU] zalcsooo:
Hi! Do someone know how can I enable system/compatibility-mode (for older apps) with encrypted Android N P5? I tried the Android Terminal commands (sysless, bindx), FlashFire flashing and also a decrypted P5 boot.img for TWRP and it's terminal commands but none of them worked or caused bootloop. :(
[SuperSU] devilloki:
ths,i'll try again.
[SuperSU] devilloki:
huawei honor7 TL01H cann't root

forgive my poor english.

my devices is : huawei honor7 TL01H

my soft ver is :Emui 4.0.1-6.8.1

my rom is stock boot,stock system.

flash supersu 2.76,cann't boot,display:

RESCUE MODE
Attention!
Please update system again

Error!
Func NO:10(boot image)
Error NO:2(load failed!)

upload log file,and boot image.

in log file,i found:

- Flashing boot image
dd: writing '/dev/block/mmcblk0p27': No space left on device

so,i guess new boot img is too big.

pls help me [MENTION=631273]Chainfire[/MENTION]!

thank u very much.
[SuperSU] Pkt_Lnt:
You got a reply above.

http://xdaforums.com/showpost.php?p=68067379&postcount=6864
[SuperSU] devilloki:
thank u [MENTION=4403217]Pkt_Lnt[/MENTION]

this time ,i confirm my rom is stock boot ,system.

confirm flash supersu 2.76
[SuperSU] grep_i:
I'm not sure if you mean you succeeded or you still have problems if still having problems try to explain how you flashed, with app names and versions.
[SuperSU] devilloki:
failed!

flash supersu 2.76,my boot.img is damaged!

boot img load failed.
[SuperSU] CVAngelo:
Sounds like you have a locked bootloader! Obviously you'd have to unlock it first if you're trying to root with version 2.76 zip which attempts to alter your boot elements.

Better to root with version 2.65 zip which doesn't alter boot elements.
[SuperSU] devilloki:
bootloader unlocked!
[SuperSU] ktmom:
Did you follow the advice to use 2.65 to root?

Then update from the Play Store to update to 2.76 binary.

Please take a deep breath before posting. We get you are frustrated. People are trying to help you but your incomplete sentence answers and skipping over what is asked makes it even more frustrating to the people who have been offering advice.
[SuperSU] hacknmtk:
From my experience, at least with my phone, doing this breaks root. I would stick to the flashable zips.

The new security implemented now in the newer version of Android makes root very hard to attain, and to get to stick.
[SuperSU] ktmom:
You may be right. Do you have a Huawei that you're being this opinion on? I don't ☺

This is exactly why "how do I root my phone" questions should be handled in device specific threads. I've seen posts that suggest what I proposed has worked when all else failed. But the people who have the device are most likely to have the solution.
[SuperSU] hacknmtk:
No, I have an Alcatel Pixi3 which has a RO system and root has been a big problem for me to get to stick. The flashable zips seem to work, and the play version breaks it when I update through the store. That's why I recommend to keep using the zips if they were working before.

If you can't get a new zip version, you can always flash the one you used before that was working.
[SuperSU] grep_i:
Ok but you still have not answered how you flashed with app names and versions.

Also can you give more detail about your device's internal space as the error in your recovery.log hinted on not enough space for the /boot partition.

Maybe you can look for a thread about your specific device and see if anyone there knows about your issue and if possible how to resolve it.

It seems to be rather more device or rom specific than a problem with Supersu.
[SuperSU] devilloki:
how check boot partitin's size?thank u

my TWRP is 3.0.2

my rom is emui4.0.1_6.8.1

android version is 6.0
[SuperSU] grep_i:
Supersu v2.76 is not working for your device see comments about it in the device specific thread.

http://xdaforums.com/honor-7/general/how-to-root-honor-7-t3170735/page32
[SuperSU] ashyx:
Any version past v2.52 makes modifications to the boot.img as does v2.65.
[SuperSU] SaGaR_:
How do you Flash the supersu zip if you need a Clean /System? Because if i understand correctly this means Without root, or am i Missing something?
[SuperSU] Ch3vr0n:
2.76 (and I think since 2.56) patches boot image of the device instead of system if the device supports it.
[SuperSU] FlemishDroid:
Systemless SuperSu ;)

Like Ch3vr0n says it patches boot instead of using /system if you device supports it otherwise it use the old way in /system. If systemless works on your device you can receive OTA updates also. I use systemless SuperSu from the beginning also I use systemless Xposed on my S7.

Search for your device.

Sent from my lightning fast SM-G930F (S7)
[SuperSU] ktmom:
ChainFire explains systemless root.

I think you are looking for systemless, and for many devices the supersu installer does checks to ensure it's appropriate to install in systemless mode (not in /system but as part of the boot image). If this thread is searched, a method to force system install is available.
[SuperSU] SaGaR_:
Thank you all for your answer, but what i Mean is how can you flash a zip on stock rom because Without root how can you have installed TWRP?

By the way, i am doing my research for my Xperia XP
[SuperSU] egingell:
You don't need root to flash TWRP.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] devilloki:
u just unlock bootloader,then u can flash recovery
[SuperSU] ktmom:
I think this is a device that has to have an exploit to root. I think you are right that you have to root first. The problem with posting this "how do I root my phone" question in this SuperSu thread is you'll get a variety of answers that may or may not be right for your specific device. The post previous to this one is right... for some devices.

Let me suggest that you post this question in a device forum/thread. If your goal is to end up with the SuperSu binary when you are done, then that's the question you should ask.
[SuperSU] KaMyKaSii:
I reinstalled the stock system and redid root but remained the same until I installed the new version of Magisk and its modified version of SuperSU and this screen finally vanished. You could also test to see if it works? If it works maybe Chainfire and new developers could study the change in boot.img made by [MENTION=4470081]topjohnwu[/MENTION]
[SuperSU] studiorat:
The zip is corrupt according to TWRP when I tried to Flash
[SuperSU] Pkt_Lnt:
Happens sometimes. Try a different browser or download manager. Chainfire has stated that many mobile download managers cause that. Try on a computer and transfer the file to mobile with adb.
[SuperSU] SaGaR_:
I was hoping to get systemless root for this Device

But i didnt know you have to unlock bootloader to do so, and that was the one thing i always avoided

So now its clear to me, thanks
[SuperSU] gothicVI:
I personally don't see this screen as a problem. However, if you could link the thread you're talking about I might take a look once I have time.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] KaMyKaSii:
http://xdaforums.com/android/software/mod-magisk-v1-universal-systemless-t3432382
[SuperSU] xrad:
Is it possible to install SuperSU in the Emulator of the Android SDK? I know that the emulator images are pre-rooted, but it seems that at least RootShell does not detect this as a rooted environment.
[SuperSU] egingell:
Theoretically, if you can flash a zip, you can... Theoretically.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] xrad:
That is the question, indeed: how to flash the zip in the emulator?
[SuperSU] egingell:
I don't know. My PC has the brain power of a wrist watch compared to an Android emulator, so I can never get one to work.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] Maxr1998:
Try Genymotion, it has zip flashing support (could be even prerooted, but I'm not sure).
[SuperSU] Manjot xda:
[MENTION=631273]Chainfire[/MENTION] and other devs i m on cm13 nightly nicki. when i flashed supersu systemless zip then its showing Patching Boot.img Ramdisk failed Aborting... even i disabled my cm root acess. plz help!!! i m on stock cm boot.img
[SuperSU] gothicVI:
Post the exact output of TWRP and the version of ALL software involved...

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] smohanv:
Can I unroot fully without any traces... I want to flash root and remove all bloatwares and completely unroot again. Thanks.

This is mainly because i want to continue using Android Pay without any problem.

I have Huawei P9 device to use this SuperSu with.
[SuperSU] Manjot xda:
I installed supersu with sucess after installing nightly. But my phone start hanging when i install SuperSU but when i uninstall it then my phone works like butter:silly:
[SuperSU] Crossdead:
After your nightly install try letting it have a complete boot before installing SuperSU, also wipe your caches after install. if it still bogs your phone down it may be an issue with the nightly and you would need to ask the developer of your ROM on there fourms. Hope this helps?
[SuperSU] CLETjB:
I think the fix for Secure Settings PRO ( Steps Below ) broke the root for Titanium Backup Pro, because I can get one or the other but not both working while performing these steps

Secure Settings PRO working

adb shell

su

mount -o remount,rw /system

touch /sbin/su /system/bin/su /system/xbin/su

mount -o remount,ro /system

exit

reboot

I get error "touch: '/sbin/su': Read-only file system"

If I use Root Explorer PRO and remove the SU from {/system/bin/su} {/system/xbin/su} directories Titanium Backup Pro works, and so does Secure Settings Pro until reboot, then Secure Settings fails to to set Systems+ Module