yashsingh1/xdaforums huggingface dataset:
[SuperSU] unarj:
hey, thanks for taking some time to reply.

the info that I'm using the fed-patcher was meant to let everyone know that I'm not using a strictly stock boot.img. I want the unencryption more than root so I haven't yet tried root without the fed-patcher applied. they both worked fine in previous images such as NBD90Z, but not the current NBD91P.

haven't used any other modifications, no suhide and no Xposed. stock rom besides what's noted above.

I've obviously read post 1 otherwise I wouldn't have the download. I went back more than 10 pages. if you would kindly show me where this info has already been discussed with SR4 and Shamu I would be content to read it and wait for a fix.

giving SR4 another go now. been using the rom unrooted for a day, no issues. after applying SR4 in TWRP I'm now sitting on the boot animation for 30mins+. I'll give it some more time and see what happens.

thanks.
[SuperSU] grep_i:
Maybe it is taking so long because your device is being encrypted there seems to be an issue on some devices with this version that it automatically is encrypting this is mentioned by some users.

The code to check device state is from a computer:

adb shell
getprop | grep crypto
[ro.crypto.state]: [[COLOR="Red"]unencrypted[/COLOR]]

in my case

The code to check device state on device with terminal app when in terminal app:

getprop | grep crypto
[ro.crypto.state]: [[COLOR="Red"]unencrypted[/COLOR]]

in my case

You can try to disable forceencrypt by adding the following line to /data/.supersu

KEEPFORCEENCRYPT=false

or in a terminal from TWRP or with adb from computer:

echo KEEPFORCEENCRYPT=false >> /data/.supersu

And flash superSU after this.

Otherwise try the last page in the fed-patcher someone is explaining how he made it work for Nougat and I'm guessing now that it is probably NBD91P.
[SuperSU] ashyx:
Has Chainfire posted details on how this works or will I need to examine the updater script?

Also its a bit confusing it being called FRP, which I guess is not related to Samsungs FRP lock.
[SuperSU] unarj:
hey again, and thanks again for taking time to write.

some good thoughts, but I don't think that either one is helpful in my situation. the fed patcher is working perfectly fine for me, I haven't done any wipes and my data partition is still unencrypted. I would think that since I haven't wiped or flashed userdata that if SuperSU was triggering it somehow that wouldn't be the case after letting it sit for 2hrs.

I will give the .supersu line a shot and see if that changes anything.

I did also try the forced-system build of SuperSU, same results.
[SuperSU] grep_i:
OK than I guess I'm almost out of options here, one question though, does this only happen with SR4 or does it happen with other versions too ?
[SuperSU] osm0sis:
That's Google's FRP lock. They've got a persist/factory reset protection pst/frp partition on all new devices since Marshmallow to control fastboot oem unlock toggling.

update-binary:

# FRP - Place files in boot image that allow root to survive a factory
# reset (true/false, PATCHBOOTIMAGE only). Reverts to su binaries
# from the time the ZIP was originally flashed, updates are lost.

if [ -z "$FRP" ]; then
# enable FRP if we're using slots, implying large enough boot image
FRP=$SLOT_USED
fi

if ($SLOT_USED); then
CPIO_PREFIX=boot/
fi

if ($FRP); then
ui_print "- Factory reset protection"
check_zero_def "" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-mkdir /sutmp/ramdisk /sutmp/ramdisk 0 ${CPIO_PREFIX}.sufrp"
check_zero_def "" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-add /sutmp/ramdisk /sutmp/ramdisk 755 ${CPIO_PREFIX}.sufrp/frp_install $COM/frp_install"
check_zero_def "" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-add /sutmp/ramdisk /sutmp/ramdisk 644 ${CPIO_PREFIX}.sufrp/file_contexts_image $COM/file_contexts_image"
check_zero_def "" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-add /sutmp/ramdisk /sutmp/ramdisk 644 ${CPIO_PREFIX}.sufrp/su $BIN/su"
check_zero_def "" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-add /sutmp/ramdisk /sutmp/ramdisk 644 ${CPIO_PREFIX}.sufrp/sukernel $BIN/sukernel"
check_zero_def "" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-add /sutmp/ramdisk /sutmp/ramdisk 644 ${CPIO_PREFIX}.sufrp/supolicy $BIN/supolicy"
check_zero_def "" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-add /sutmp/ramdisk /sutmp/ramdisk 644 ${CPIO_PREFIX}.sufrp/libsupol.so $BIN/libsupol.so"
fi

so pretty much just adds all the important stuff to /.sufrp in the ramdisk. Hmm I'll have to update mkbootfs to handle that. :good:
[SuperSU] Ibuprophen:
You will have to ask [MENTION=631273]Chainfire[/MENTION] about that.
[SuperSU] ashyx:
Ah right I get it. Had an idea it was something along those lines as it it's similar to the /.su backup in the ramdisk.

Thanks for pulling the info.

It's OK, osm0sis post explains it perfectly.
[SuperSU] calikevin:
Sorry if this is a stupid question, but are the SR releases Systemless Root by default, or do I still need to enter the systemless command before installing SR4?
[SuperSU] andrew2432:
6.0+ auto systemless, reported to work with 5.0 with the command. I even read a kk user in the pgo thread claim 4.4.2 working with the systemless

Sr isn't "system less root" is it?? hehe
[SuperSU] Ch3vr0n:
SR doesn't stand for systemless root. It stands for service release, and systemless root has been the default method since 2.65 or something provided your ROM supports it. Whether it's 2.78 or 2.99 is irrelevant.

Sent from my Nexus 6P with Tapatalk.
[SuperSU] devil-kin:
On my girlfriend's OnePlus X (onyx) I also need to force systemless root on Marshmallow. Detection keeps using system root, which fails to boot completely.
[SuperSU] nicochoco03:
Hi everyone ! I have super su sr3 on my nexus 6P with elementalx kernel 3.09. I want update to sr4 but do i must flash stock boot before sr4 or can i just flash over the sr3 ?

thank's
[SuperSU] Alxoom33:
You should just be able to flash over SR 3.
[SuperSU] dkoek:
Flashing without failure.

It looks Supersu works fine on the background but for some reason the icon of supersu is not visible.

Any suggestions ?

PS: MM6.0.1
[SuperSU] gialakias:
Install the apk inside the zip or from play store.
[SuperSU] dkoek:
Already did install the apk from within the zip.

Did not made it visible either..:(
[SuperSU] gialakias:
Is it stock mm or rom? Maybe it is in the settings menu like mine that I am with krexus mm.
[SuperSU] dkoek:
No, it's nowehere visible. (Only as an installed app in the app menu. But it cannot be opened form there also.)

ROM is MM6.0.1 RR (custom ROM and rooted)
[SuperSU] jimbomodder:
On RR it's in settings menu near bottom as it's installed as part of the system
[SuperSU] dkoek:
Can you provide a printscreen from your phone ?
[SuperSU] jimbomodder:
I can't currently as I'm on omega rom which is stock based, it should be near the bottom
[SuperSU] nedraga:
try *#*#1234#*#* , go to settings > launcher icon

---------- Post added at 10:20 PM ---------- Previous post was at 10:14 PM ----------

try *#*#1234#*#* , than change the launcher icon
[SuperSU] dkoek:
I don't know why but after the 3rd install of the apk I can finally see de supersu menu in the settingsmenu (see screenshot).

Thanks everybody for the help !
[SuperSU] jimbomodder:
Maybe it just needed a reinstall but glad it's sorted
[SuperSU] unarj:
I tried flashing stable and got same result. tried flashing SuperSU first then fed-patcher, same result. can get into an adb shell when it's sitting in boot, everything seems idle. the top 2 threads are "bootanimation" and "surfaceflinger" at 1% CPU each. otherwise nothing.

I did see other people saying that the latest patch release of 7.1 is similar (same?) problem, perhaps there was a security change in the recent patches that affected shamu differently than others.

nothing else to try a the moment, will give the next release a go when it is out.
[SuperSU] sam77744:
su zip is twrp flesheble zip for root?reply pls
[SuperSU] bamse84:
Yes
[SuperSU] sam77744:
after flesh need too sown load supersu from play store?
[SuperSU] bdwilk:
No.
[SuperSU] bamse84:
Only if you want to help the developer and buy the pro version
[SuperSU] kevtrysmoddin:
Anyone tried this on the new dev preview?

It does work dev preview 2 rooted yay
[SuperSU] tuiyaan:
i donno whether this is correct section

tried every systemless su zip [MENTION=631273]Chainfire[/MENTION] [MENTION=7678190]SuperSU Release[/MENTION]

tried it on freshl flashed stock rom, but gets same error

patching sepolicy failure abort

My device honor 4x sub model che1-l04

stock rom emui 4 mm6.0.1

actual boot.img extracted.

https://www.dropbox.com/sh/5agjjd41dm4h8ah/AACrjPtrtBvlwnNyo_-319mqa?dl=0

anyone please help
[SuperSU] grep_i:
Posting recovery log will help you better with this issue
[SuperSU] tuiyaan:
thank you for your reply

flashed fresh ROM & used SuperSU-v2.78-201609011115

recovery log is attached

https://www.dropbox.com/sh/5agjjd41dm4h8ah/AACrjPtrtBvlwnNyo_-319mqa?dl=0
[SuperSU] grep_i:
Looked at your log but could not find the main reason, but log states a couple of times that device is not 64 bit but 32bit.

Are you sure bootloader is unlocked properly ?

ro.cm.display.version=13.0-20160531-UNOFFICIAL-cherry

ro.bootloader=unknown

Have you tried flashing with older SuperSU ?

Have you pop this question in device specific thread or rom specific thread ?
[SuperSU] tuiyaan:
My device is 64bit check it n cpu z and other apps

bootloader is unlocked i flashed twrp n cm.

but CM was flashed in may 16 but its there in the log.

i tried all method systemless ,system mode all version of su 2.46 to 2.78 all fail

only magisk n phh's su workes.

but many apps not detecting this su

tried in honor 4x rom no one respond

can you look into this

- Patching sepolicy

sukernel v2.77 (ndk:armeabi-v7a) - Copyright (C) 2014-2016 - Chainfire

Loading from [/sutmp/ramdisk] ...

Saving to [/sutmp/sepolicy] ...

CANNOT LINK EXECUTABLE: "/system/lib64/liblog.so" is 64-bit instead of 32-bit

page record for 0xb6f6602c was not found (block_size=16)

--- Failure, aborting

- Applying hex patches

sukernel v2.77 (ndk:armeabi-v7a) - Copyright (C) 2014-2016 - Chainfire

Loading from [/tmp/supersu/common/hexpatch] ...

Loading from [/sutmp/boot.img] ...

Could not open file [/sutmp/boot.img]

Error reading file

losetup: /dev/block/loop0: No such device or address
[SuperSU] grep_i:
Why don't you try with newer rom there's a more recent version of this rom available.

https://download.cyanogenmod.org/?device=cherry&type=nightly
[SuperSU] egonet:
I can confirm these issues in my S7 (G935F) running Nougat ZPK4 +SuperSU 2.78 SR4 -> broken camera (FC), wifi, light sensor, even not working manual brightness adjustment! Probably there are other isssues but I could not stand and unrooted the phone 30 min after rooting (then all issues were gone) :)

I hope [MENTION=631273]Chainfire[/MENTION] at least knows about these issues already (or even experienced it as I've seen G930F in the signature - probably same problems there)

So we need to wait patiently :angel:
[SuperSU] bhavstech:
[MENTION=631273]Chainfire[/MENTION] Oneplus3 CM14.1 22nov build , i am facing issues with root such that randomly some root apps break root and i have to reboot every time this happens, this happens only if some app explicitly request super su permission ot in background, my cm root is disabled alongside supersu is set to grant.

i cannot post logs due to the fact that i cant access catlog when this happens because i have no root

---------- Post added at 08:06 PM ---------- Previous post was at 07:24 PM ----------

you can flash , the pixel is because you have enabled google assistant

and yes i am facing same issue on oneplus 3 on cm14.1
[SuperSU] tuiyaan:
Sorry bro u might have got confused:)

I used cm in may n since June im back to stock emui ROM.

I dunno how that info still there in log.

In cm it's easy as developer options has root.

I'm trying to root MM stock emui.

can you look into this

- Patching sepolicy

sukernel v2.77 (ndk:armeabi-v7a) - Copyright (C) 2014-2016 - Chainfire

Loading from [/sutmp/ramdisk] ...

Saving to [/sutmp/sepolicy] ...

CANNOT LINK EXECUTABLE: "/system/lib64/liblog.so" is 64-bit instead of 32-bit

page record for 0xb6f6602c was not found (block_size=16)

--- Failure, aborting

- Applying hex patches

sukernel v2.77 (ndk:armeabi-v7a) - Copyright (C) 2014-2016 - Chainfire

Loading from [/tmp/supersu/common/hexpatch] ...

Loading from [/sutmp/boot.img] ...

Could not open file [/sutmp/boot.img]

Error reading file

losetup: /dev/block/loop0: No such device or address
[SuperSU] grep_i:
I'm sorry I do not know anything about emui.

can you try and open up a terminal before flashing SuperSU

Type the following before flashing:

echo SYSTEMLESS=true >/data/.supersu

Flash SuperSU normally

Saw something but I'm not sure about this can you check your /data path please

Your log tells it is a symlink to /sdcard is this true ?

/data | /dev/block/mmcblk0p25 | Size: 4169MB Used: 418MB Free: 3719MB Backup Size: 418MB

Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage

Symlink_Path: /data/media/0

Symlink_Mount_Point: /sdcard

Primary_Block_Device: /dev/block/mmcblk0p25

Display_Name: Data

Storage_Name: Internal Storage

Backup_Path: /data

Backup_Name: data

Backup_Display_Name: Data

Storage_Path: /data/media/0

Current_File_System: ext4

Fstab_File_System: ext4

Backup_Method: files

MTP_Storage_ID: 65537
[SuperSU] tuiyaan:
Don't be sorry :svetius:

It trying to help me

Tried echo systemless true same result

Echo systemless false device went into boot loop

Sdcard is emulated

su runs fine in LL when zip is flashed from sdcard
[SuperSU] azuraZura:
i uninstall magisk, and then cant get root access, so i try re-flash via twrp with latest supersu.zip, but nothing changed. Anyone please help
[SuperSU] Ja_som:
Device informations, logs...
[SuperSU] azuraZura:
where is device info logs? at twrp or phone setting?
[SuperSU] bdwilk:
He means device info..... What phone, ROM, etc? And provide logs if possible.
[SuperSU] azuraZura:
Here it is:

Device: Xperia z5c, android 6.0

Uninstall magisk 9, but cant access root again

Try to install latest supersu. zip but nothing changed

Please help

Logs when install supersu. zip:

:crying:
[SuperSU] Ja_som:
DELETED, sorry
[SuperSU] fmc000:
Obviously you missed the "Calling user ramdisk patching script - Failure, aborting" part...
[SuperSU] azuraZura:
here it is (image), just like flashing failed so i cant get root
[SuperSU] azuraZura:
what can i do then to fix it?
[SuperSU] fmc000:
Summoning [MENTION=631273]Chainfire[/MENTION] and using the search function within this thread to see if there have been other occurrences of your problem.
[SuperSU] Ja_som:
Yes, I missed it, sorry [MENTION=6905673]azuraZura[/MENTION]
[SuperSU] bhavstech:
This may help

Problem loosing root repeatedly

Cm14.1 op3
[SuperSU] ashyx:
/sdcard is always linked to /data/media/0 that's normal.
[SuperSU] andrew2432:
I read flash once, run the command, flash again?? Not trying to correct anybody, just what I read someone did!

Smg900p, touch wiz, stock, 5.0 ok4 build, tried back with sr2 flash and lost data connection. Still had magisk manager installed, may have even had one of the zips phh or magisk installed still, I forget..dummy. twrp backups have ALWAYS saved me...make a freaking backup

If I ramdisk patch will rootswitch turn off root instead of using su hide?? 5.0 Aos, not 6+
[SuperSU] jcsww:
Does the latest version of SuperSU work with the Nexus 6P Developer Preview, angler-npf26f?
[SuperSU] grep_i:
Yes but that's not what I was talking about I was asking about /data.

I figured it out I guess what they mean is that on /data there is a symlink path to /sdcard, never noticed this before.

I tried to decompress the boot.img and succeeded it is 35MB in total and your /boot on device can hold 64MB so there seems to me that there is enough space.

One question though do you even have a working busybox installation on your device it seems like you are missing this according to some log entries.

Also you might wanna clean up your device and reflash everything, wipe clean all partitions prior to flashing another rom.

As your log indicates that your device claims it's working with a different rom than you think it is.

And last but not least there is still some issue on your phone with determining if it is 64 bit or 32 bit.

I guess a clean flash of rom will solve all this problems.
[SuperSU] egingell:
It's not linked there, that's where the files are actually stored. All other access points are links to that.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] kistigun:
Hi all, I'm having some problems with rooting my xperia x. After flsahing supersu v2.78 rs4 the device boots but I'm gettin 'no sim' message and I'm not gettin any signal, IMEI nr gone etc.

Device: Sony Xperia X f5121

Android 7.0

Firmware 38.1.A.0.342 Android N concept rom

SuperSu version: SR4-SuperSU-v2.78-SR4-20161115184928

No interfering su apps like bb/xposed

TWRP log in attachement(had to flash phh's superuser.zip after susperSU to obtain root and extract log, with superuser.zip I have root but cant mount system rw)

Can anyone help?
[SuperSU] andrew2432:
LG G2 D800 SN passing with: [MENTION=5031300]blastagator[/MENTION] twrp 3.0.2-1

Wipe the life out of it

Install LP bootloader

Cm13 nightly, 6.0.1, unroot with [MENTION=4544860]osm0sis[/MENTION] unsu

Use twrp to check for them su files and delete as necessary

Flash 2.78sr3

Bump boot

Flash su.55, not sure if it did anything found no GUI

Flash roots witch 1.3.3.2 but again not sure that did anything

Install roots witch apk, after finding the apk in the zip in windows :)

Disable root

Sn passes with root disabled

Xposed 86.2 maybe broke WiFi :(

Other cm could attempt the same??

MM may make it easier on my smg900p[/QUOTE]
[SuperSU] detlev24:
Hello everybody,

same here on Moto G (2. Generation).

Using v2.78 SR4 on stock (Android-Version 6.0 / Systemversion 24.41.34.titan_retde...) is no problem but when I flash it over latest

Cyanogenmod 14.1

, NO SIM card is found (before flashing SuperSU, SIMs are available!).

Any suggestions? Thank you!
[SuperSU] Slim2none4u:
Cm 14.1 has its own superuser apk. Flashing supersu breaks WiFi and possibly is the reason.

Now why supersu and cm14's superuser apk's don't play together, someone with more knowledge would have to come in.

But since cm14 came out, you can't flash supersu on it. It will break WiFi.
[SuperSU] andrew2432:
Try removing native su and all traces first??
[SuperSU] Ibuprophen:
When it comes to the inner workings of the SuperSU, asking the dev [MENTION=631273]Chainfire[/MENTION] is your best bet.
[SuperSU] John256145:
Any solution on the calling user ramdisk patch script error?

On my device, TWRP still says the zip installation was successful, but SuperSU never shows up in the app drawer, and downloading and opening the app says root is not installed.

Obviously this wasn't successful.

My phone is a Moto G 2nd Generation, running Android 6.0 Marshmallow.
[SuperSU] Fif_:
Well, can you try removing the user ramdisk patch script, then reflash?

That script is not part of SuperSU.
[SuperSU] Beast84:
Currently running phh superuser & it keeps losing root. A reboot fixes it. I'm wondering if this has the same issue? I'm on 6P running stock dev preview
[SuperSU] osm0sis:
Not true on my Nexus 7 2013 running CM14.1. Wi-Fi working great.
[SuperSU] Didgeridoohan:
In that screenshot I don't see anything about the installation being successful, quite the contrary... It tells you the script is done, yes, but it also quite clearly states that there was a failure. So no, not successful.

And before you ask: I have no idea how to help you... Sorry.
[SuperSU] grep_i:
BOOTIMAGE = like /dev/...... location path to boot partition.

STOCKBOOTIMAGE = like unpatched boot partition backup.

So yes basically what you said is correct.
[SuperSU] Z953RR:
[MENTION=631273]Chainfire[/MENTION] any news about su for galaxy s7 for nougat beta??
[SuperSU] Jole7:
Yes please take a look if it's possible to the above request.
[SuperSU] Alxoom33:
I believe your issue is due to a Magisk remnant in your /data folder. look for a file with the extension .sh and delete it. SuperSu should then flash and boot up just fine. [emoji2]
[SuperSU] fix-this!:
chainfire, any chance we can get some help with root and the su problems we have with the honor 8 - 7.0 beta? we have working twrp for nogout but supersu causes bootloops when flashed.
[SuperSU] Pkt_Lnt:
How can he help with no logs? Post your recovery log.
[SuperSU] John256145:
Dude, I can't thank you enough! I did find a file in the /data folder causing problems. I can't remember the exact name of the file, but it had ramdisk in the name and a .sh extension, like you said. Flashed the zip afterwards, and I have root! Thanks again! :good:
[SuperSU] jairoa:
Hello guys wanted to see if they could help me I tried with all the methods of root galaxy s7 and it does not work none would thank them very much thanks my phone is galaxy s7 smg930T1
[SuperSU] Alxoom33:
Glad it worked. You're welcome!
[SuperSU] UND312DOG:
I'm getting the broken WiFi problem running sr4 on resurrection remix 7.1. It's odd. Any ideas?
[SuperSU] tuiyaan:
[MENTION=6952047]grep_i[/MENTION] and [MENTION=7785649]andrew2432[/MENTION]

erased sys,recvry,boot.

flashed stock rom

tried echo systemless=false >>/data/.supersu

got boot loop

again erased sys,recvry,boot.

flashed stock rom

tried echo systemless=true >>/data/.supersu

no luck got patching sepolicy failure

both log

https://www.dropbox.com/sh/5agjjd41dm4h8ah/AACrjPtrtBvlwnNyo_-319mqa?dl=0
[SuperSU] grep_i:
Your device is still CM

ro.cm.display.version=13.0-20160531-UNOFFICIAL-cherry

There seems to be some problems with mounting /data

/tmp/updater[1390]: /system/bin/e2fsck: not executable: 64-bit ELF file

CANNOT LINK EXECUTABLE: "/system/lib64/liblog.so" is 64-bit instead of 32-bit

page record for 0xb6f6602c was not found (block_size=16)

--- Failure, aborting

Could not open file [/sutmp/boot.img]

Error reading file

Before flashing the rom again, clear following partitions through formatting or (rm -rf) first, except /sdcard obviously.

/cache

/system

/data

Now flash the rom from sdcard or from pc either with adb sideload or adb and fastboot if possible.

You need to choose one of the methods.

As long as you stay on this rom 13.0-20160531-UNOFFICIAL-cherry you will keep having the same problem.

Checked systemless=true log and saw you are installing SuperSU v2.78.

Please try again with SuperSU v2.78 SR4
[SuperSU] stathis95194:
Don't use >> as it is appending everything to the file and it might misbehave.

Use echo "SYSTEMLESS=true">/data/.supersu
[SuperSU] Hermankzr:
I'm confused wether to use this Beta SR4 or the stable one from this : http://xdaforums.com/showthread.php?t=3452703

I just need to root my Note 4 6.0.1

Forget to tell that i'm on November update just in case the stable one can't handle it.
[SuperSU] ruchern:
I have no problems with SuperSU and CM14 and CM14.1 at all.
[SuperSU] UND312DOG:
Breaks my WiFi on 14.1 resurrection remix.
[SuperSU] HaoZeke:
You need to give an adb logcat too I guess.

---------- Post added at 11:48 PM ---------- Previous post was at 11:48 PM ----------

How exactly do we get to system less mode?
[SuperSU] azuraZura:
finally i flash my mm, it works. lol
[SuperSU] ruchern:
Hi guys,

I remembered seeing a post where you can keep SuperSU even after flashing a ROM that uses other SuperSU. However, I've forgotten the keyword to search for it in this thread.

Can anyone help me with this?
[SuperSU] osm0sis:
With Samsung being like they are with security it's probably always best to use the latest beta (SR) releases since Chainfire's likely keeping up with them.
[SuperSU] dhruvpatel_9880:
No one is replaying to NO SIM issue.

Please help us , I think the issue is only with dual sim devices.