yashsingh1/xdaforums huggingface dataset:
[SuperSU] lucadalba:
Anyway I have solved:

I have putted in DeoXPer/SuperSU the su.zip and a folder named supersu that contains the files contained in su.zip .

The problem is that su.zip (when is started) want to extract own files in /tmp/supersu and, when it is started by my rom zip, it fails and there is no file in /tmp/supersu , so su.zip can't work .

But with the procedure descripted above and this commands

it works fine because in DeoXPer/SuperSU there are su.zip and the extracted one in folder "supersu" .

So when DeoXPer/SuperSU is extracted, in /tmp there will be /tmp/su.zip and /tmp/supersu .

When I start su.zip it will fail to extract own files anyway. But when su.zip want to access to /tmp/supersu/xxxxx/xxx it can do it because I have before "manually" extracted the zip!

In Italy we say "Good is everithing that finishes good".. so thank you anyway[emoji6]

And obviously a BIG THANK YOU TO [MENTION=631273]Chainfire[/MENTION] for SuperSU[emoji6]
[SuperSU] el_charlie:
Hello,

The latest TWRP doesn't work on N DP3. I read somewhere that someone rooted his 5X with CF Autoroot. Is it safe?
[SuperSU] ohad129:
Im on latest 3.0.2 works great
[SuperSU] ianmacd:
I tried installing 2.74 on my S7 Edge from the APK in the /common directory of the ZIP file, but the update failed after 60 seconds and left me without root.

I reflashed CF Auto Root via ODIN, rebooted and was back with root and 2.74.
[SuperSU] Chainfire:
Try the new link from the first page. v2.74-2-...
[SuperSU] Captain_Throwback:
New version works! Thanks :).
[SuperSU] j1gga84:
I installed 2.74-2 via TWRP but it is installed as user app now and not as system app anymore, is that normal? :confused:

regards
[SuperSU] egingell:
For systemless? Yes.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Chainfire:
Release notes for v2.74 - https://plus.google.com/+Chainfire/posts/XMFgencRR11
[SuperSU] j1gga84:
Okay, thanks for information, strange indeed because 2.72 was installed to /system when flashed zip in recovery.

2.74 was installed to /data, allthough I flashed it the same way :confused:

regards
[SuperSU] corkiejp:
Flashed v2.74-2 with a temporarily booted TWRP on encrypted Nexus 9, SuperSU app still reports it as version v2.72.

I will try again later and not flash ElementalX straight afterward.

Is the CFAR update for DP3? The site still lists NPC56P

Edit: Just sideloaded v2.74-2 again and it worked. Didn't have to re-flash ElemetalX, as the custom kernel was still present.
[SuperSU] egingell:
I'm pretty sure he explicitly stated that the version number would not change.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Ja_som:
I have 2.74
[SuperSU] egingell:
My bad. I misread. I thought he said he went from 2.74 to 2.74-2.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] yanleites:
Nexus 5X - 3rd Android N - SuperSU 2.74 works great !

p.s. ES Explorer doesn't get root... Help will be appreciated :)
[SuperSU] SlimSnoopOS:
Contact the dev of ES Explorer and get them to properly look for root. That app really does not seem to work well with root, just do a search for "ES File" in this thread and you will come to the same realization. Use a different file explorer like Holo, Solid or Root Explorer.

Edit: You might be able to get root working with ES by running the BINDSYSTEMXBIN=false>>/data/.supersu terminal command from this explanatory post then reflash SuperSU.
[SuperSU] gpvecchi:
I remember that it was possible to select SuperSu theme, but it seems that option is no more there... Any dark theme around there?
[SuperSU] edzamber:
Always Here....
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] i flashed 2.74 through flashfire and lost all root access on my nexus 5. As indicated by screenshot attached, lastlog included. I forgot to copy over the other log. I was able to regain root by flashing 2.72 through twrp. However all previous entries in SuperSU were lost (every app had to re-request su, as well as settings were reverted 30sec timer back to 10, namespace was back on, reverify was back enabled...). However root checker screenshot does display that su was found.

The weird thing, i flashed 2.74 the exact same way on my nexus 7 v2 and everything worked just fine.

[MENTION=4507636]edzamber[/MENTION] please u

tags, even on my 24" monitor i need to scroll multiple times to get past those images.
[SuperSU] osm0sis:
Hmm. I had no issues updating my N5. :confused:

I used FlashFire to flash the SuperSU 2.74 zip (and restore stock boot/recovery + preserve custom recovery), then flash the latest franco.Kernel AK2 zip. EverRoot disabled. Worked perfectly. :good:
[SuperSU] drewski_1:
see the Compatibility section in the Changelog => https://plus.google.com/+Chainfire/posts/N6EARb8LF3d

and use a different Root File Manager. ES now has Spyware incorporated!

---------- Post added at 01:42 PM ---------- Previous post was at 01:40 PM ----------

For whatever reason, it does not show if SuperSU is incorporated into Settings of the ROM. is that how your ROM is?
[SuperSU] Ch3vr0n:
[MENTION=4544860]osm0sis[/MENTION] i didn't select restore as chainfire previously notified me this was not needed for a straight simple su update. It's also in the info when you select to flash the zip "disable for non-ota updates". I'll try again.

** edit * retry succesful. Must have been a hiccup somewhere. Worked fine 2nd time around. cflumen kicked in, root checker access granted.

[MENTION=631273]Chainfire[/MENTION] i've attached lastkmsg & ff lastlog in this zipfile. Perhaps it'll shed some light.
[SuperSU] HorstiG:
In BETA-SuperSU-v2.74-2-20160519174328 is the App Version 2.65

View attachment 3756061
[SuperSU] yung40oz84:
I flashed 2.72, 2.74, and both of the only boot loop on Google logo for latest DP3 N preview, what root is everyone using? My TWRP works fine, I'm decrypted
[SuperSU] drewski_1:
SuperSU 2.72 with no issues. Maybe your downloads got corrupted?
[SuperSU] quincho54:
Flashed SuperSU v2.74 on Note4 costume rom (sixperience v.6) . Everything works fine.
[SuperSU] casonswag:
It works fine here on latest N build
[SuperSU] Tkbf:
Flashed v2.74 on Note 4 running MM stock, and Tab S 8.4 wifi running MM AOSP, no problem here.
[SuperSU] Alxoom33:
Read this thread!
[SuperSU] joe_clasher!:
Same for me
[SuperSU] brinsleyparagao:
error on:

Motorola X 2014

CM13 - 18-05-2016
[SuperSU] gpvecchi:
Exactly! Thanks! Couldn't this be a feature to add?
[SuperSU] bonerserk:
2.74 on AOSP 6.0.1 on Samsung s2vep

No problems!
[SuperSU] leso60:
Hi, how can i get SuperSU 2.74-2 in System Mode?
[SuperSU] DjDiabolik:
Whit SuperSU latest beta ( i have now the 2.74-2 but same problems i have also whit 2.71... and .72) on latest COS13 there's here some member can't be obtain the ROOT ACCESS on stock "File Manager" ??

On "Advanced Setting" i don't see the settings for activate the root access................ other apps like MixEplorer (picked from here) and "Es File Explorer" working like a charms, it's a trouble created by the Beta or SuperSU ?? Some members using the stable 2.65 reports workings.........
[SuperSU] grep_i:
Guess this is problem of your rom or yourself.

To be sure go find if there's a thread for your rom and look if more people have this problem and ask there for support.
[SuperSU] xda-unknown-developer:
When I reboot my device after flashing, it boots in safe mode, why? Nexus 6 Developer preview 3
[SuperSU] mauam:
Here:)
[SuperSU] shoey63:
2.74-2 Working on Xperia Z3 N-preview 3 :highfive:

Did you fix something regarding Sony Chainfire?
[SuperSU] Gandalforce:
Lol where is FlashFire? Is it EOL?
[SuperSU] koko115:
Still no root in es explorer (2.74). I go buck to 2.68 in this version root work on ES Explorer.

Galaxy S7
[SuperSU] ianmacd:
More like start of life. It's still in beta:

https://play.google.com/store/apps/details?id=eu.chainfire.flash
[SuperSU] Gandalforce:
Haha. Thanks

I went to beta opt in, but link to play store was invalid
[SuperSU] Pkt_Lnt:
https://plus.google.com/communities/116661625291346007584
[SuperSU] ianmacd:
If you mean that you signed up for the beta, but then couldn't download the app, you just need to wait a few minutes to an hour for your beta status to sync with the Play Store. At that point, you'll be able to download the app.
[SuperSU] ohad129:
Works for me on N3
[SuperSU] mitchdickson:
Great post.
[SuperSU] Alxoom33:
Got bootloops with 2.74-2 on Nexus 6 N preview 3.
[SuperSU] aheeejd:
Just flashed on ls990 (Sprint LG G3) running Resurrection Remix 6.0.1 & all is fine with updated v2. 74

Edit - Also just flashed on manta (Nexus 10) running AICP 6.0.1 & working perfectly. Thank you
[SuperSU] cidriyan:
saved

Thanks alot dude this saved my phone from a bootloop after i installed SuperSu binary on TWRP on my LG G3
[SuperSU] miloytyn:
Is it still possible to install OTA updates with 2.74 or does the changes in making backups prevent this?
[SuperSU] Ch3vr0n:
You can't install ota's with superSU. Flashing superSU by itself voids ota because of modified boot. The backup changes probably doesn't change that.
[SuperSU] DjDiabolik:
mmmmm... here in this forum i can find the thread of mirrors of cos13..... but not an official thread for discussion.

Otherwise on official board there's some similar thread like this:

https://www.google.it/url?sa=t&rct=...PWTtREpCgG74eip8Q&sig2=ufrGQ3n6pF9OyIcQ0DfAfA

Or this:

https://www.google.it/url?sa=t&rct=...maw7i77AUAt61OMeQ&sig2=fmXgfo5eFpffTOqMl8TjZg

Apparently the problems it's a trouble created whit using of 2.7x beta version :)
[SuperSU] tag68:
OTA on "ancient" Android versions used to work after undoing system changes (changes to build.prop, hosts). If you changed more, you needed to undo that also (recovery if twrp flashed not booted, logo if modified, kernel if xposed etc.).

Since Android 5 it was additionally necessary to do SuperSU unroot, but OTA worked after full unroot. But with Android 6 at least for Motorola devices (X Play, G 2014) no other version of SuperSU than 2.62-3 worked (using twrp flash 2.46 bootloop, 2.62 bootloop, 2.65 bootloop, 2.67 bootloop). Full unroot only shows a short message "unsuccessful", at least after updating to 2.65 (didn't test by now without that update). That's why I asked some time ago if full unroot is supposed to work and if that problem is known, but never got an answer.

Current versions of SuperSU are said to work on Motorola devices with Marshmallow if done systemless, but causing bootloop if not. I wanted to wait for an answer regarding my unroot question before testing anything.
[SuperSU] Murshad007:
Restart Ur cell two times...

Sent from my LG G Flex F340K Stock KitKat 4.4.2 Rooted

using XDA Free mobile app
[SuperSU] StupidIdea:
I think I solved it. For some reason jar must be owned by root on N4.
[SuperSU] A10Loogie:
SuperSu doesn't respond to taps

I'm having a weird anomaly. I just flashed to 5.0 LRX210 on my N5 using TWRP 2.8.1.0. Had to do CF-Root to re-obtain root. Success there. When an app requests root access then SuperSu pops up the normal confirmation requester and the timer starts to count down. However, the SuperSu requester will not respond to any screen taps at all so the timer counts down and the app is denied. Another interesting thing is that only the first app (Nova Launcher) that requested root access is listed on the apps screen, but they all show up in the log. Normally I would get all the apps (approved or denied) in the log and then I could toggle their approval status. If I set the default status of the app to "grant" instead of "prompt" then everything seems to work fine, but I don't want to leave it set up that way for obvious reasons. I tried uninstalling and re-flashing beta 2.23 but it made no difference. BTW, this also happened on 2.20 before I flashed beta 2.23.

I apologize if this is a redundant issue. I did a couple of searched but didn't find anything.
[SuperSU] greyhd:
If you have lux autobrightness app, whitelist SuperSu.
[SuperSU] areyouanand:
404 error with the link
[SuperSU] Bhaskara Rao:
Working fine on Samsung Tab 2 p3100 Android-Andi's CM12-Snapshot-M12 with Next Kernel 2.4
[SuperSU] A10Loogie:
I AM running Lux! That helped a lot! I couldn't figure out how to 'whitelist" SuperSu, but once I enabled plug-in support and downloaded the Nexus 5 plug-in it seems to be working fine. Thanks!
[SuperSU] envoy510:
I'm here to report that XPrivacy doesn't detect root on Lollipop

I installed 2.23 via TWRP on a Nexus 5 with 5.0. When I run XPrivacy, and hit the "check for root" button, the "device is rooted" checkbox is grayed out.

Just reporting it in case it's not a known issue.
[SuperSU] someonesim:
Previously in beta as well but Helium got issue, TiBu works fine though. Flashed this beta and Helium works fine now. Praise Lord Chainfire :good: :good: :good:
[SuperSU] Dark9781:
First I just wanted to say thanks for ensuring we could get root access on Lollipop. I installed 2.23 on my Nexus 7 2013 and all my apps that require root work fine except extended controls. I use it to reboot my tablet instead of powering off. Extened controls is granted root access, but does nothing.
[SuperSU] yanner2012:
A few days ago titanium has been update. Just download it from playstore.
[SuperSU] dough29:
Hello !

Just installed SuperSU V2.23 BETA on my Nexus 5.

I am using Llama and Taskkill for some automation (Launching Waze when connected to the car's bluetooth, kill Waze when disconnected and so on...) and since I am on Lollipop :

- Taskkill doesn't work : selected app is not killed

- Llama can't trigger when an app is running or not

Are these points "root"-related or do I have to ask the each developper for support ?

Thanks ;)
[SuperSU] Massi-X:
Thanks for latest update,resolved the problem with ccswe app manager and I don't find any bug :)
[SuperSU] squigs:
Rom toolbox (pro) freeze /defrost feature works again (this was broken).

Nexus 5, Android L LRX21O
[SuperSU] Idalvar:
Flashed 2.23 on Nexus 4 running stock Lollipop, SuperSu throws the following error : "There is no SU binary installed..."
[SuperSU] ji_llona:
Installed on Nexus 4, stock lollipop.

I was unable to modify mobile data on/off with PowerToggles (sent me to the settings screen). Now it works.

Thanks! :D
[SuperSU] playahate:
You still need to use CFAR (AutoRoot) first, to modify kernel and only then flash that zip. there will be separate kernel patcher soon.
[SuperSU] Idalvar:
Thanks, I missed that step.
[SuperSU] wojwem19:
For me extrating from common folder supersu apk and installing it then rebooting to recovery to install binaries.does not work. Had to go to recovery ( twrp ) and flash 2.23 .zip mannually and now everything works perfectly.
[SuperSU] Streetwalker:
OK I figured it out. Somehow su -d doesn't auto start at boot causing this issue. If I start an adb root shell and run it manually I have root until the next reboot. I'll try to see how I can fix it.

Edit : OK, that was ****ing stupid. I had install-recovery.sh disabled in my init.rc.
[SuperSU] Ch3vr0n:
No it's not, the problem is with apps like ES using hard coded paths and not calling the correct variables. That's not superSU's fault, the dev needs to fix the app
[SuperSU] rakeshbro:
Flashed latest beta on sony z2 android mm after boot no root :laugh::laugh:

Now I've flash lolipop back to get root access, and then mm :silly:

Only success is with BETA-SuperSU-v2.68-systemroot.zip.

What's the problem?
[SuperSU] kforkai:
2.74-2 working on galaxy s6 sm-g920i mm6.0.1 stock 920f permissive kernel. Running since last nite. No errors except flashing thru twrp device didnt get pass boot logo but led indicator still active. Rebooted and reflash with fs, tadaa.. Thanks
[SuperSU] Mike02z:
2.74-2 working perfectly on N6 with Multirom. Preview 3 as primary with Elemental N4.0.4 and Omni 5/21 nightly as secondary with B14CKB1RD-v 1.81.
[SuperSU] DjDiabolik:
Infact i thinks you are correct.......... i have upgrade my ES Pro to 1.0.6 and also here Root Access it's no granted....... but there's no problems when i use MiXplorer.....

Ah stupid question:

If i disable the "Namespace option"...... i can obtain some problems ? Now i'm disabled it (and it's report Compatible) but if i activate it (and restart my opo) when i use Titanium Backup i obtain an error at start say to me whit this fuction i can obtain some problems...........
[SuperSU] skulldreamz:
All pertinent info inside zip. Also 1st time ever getting fc using supersu, but as always thank you.
[SuperSU] Alxoom33:
It's alive!!!

Android Pay working again on Android N Preview 3!!!!

Joy. :)

---------- Post added at 10:50 AM ---------- Previous post was at 10:49 AM ----------

with Systemless Root!
[SuperSU] ifwillems:
Can you describe the steps you followed to make this happen? Did you use SuperSu 2.74?
[SuperSU] Alxoom33:
First I dl'd the P3 update from the beta ota. Rooted, then I pressed the AP app ;)

---------- Post added at 11:11 AM ---------- Previous post was at 11:11 AM ----------

No, I am using 2.72

---------- Post added at 11:12 AM ---------- Previous post was at 11:11 AM ----------

I am having problems getting 2.74 to work. Bootloops ;( However, I don't think I need it for my Nexus 6.

---------- Post added at 11:14 AM ---------- Previous post was at 11:12 AM ----------

Sorry, I coulden't resist! ;)
[SuperSU] Pkt_Lnt:
Chainfire has asked repeatedly that Pay discussions be posted in this thread and not here.

http://xdaforums.com/apps/supersu/supersu-safetynet-android-pay-t3298115
[SuperSU] Alxoom33:
Yes, I know. But this was an awesome discovery. I apologize to [MENTION=631273]Chainfire[/MENTION].
[SuperSU] miloytyn:
I forgot to mention that Imeant installing OTA with flashfire.
[SuperSU] USBhost:
Segmentation fault

Problem with BETA-SuperSU-v2.74-2-20160519174328.zip Nexus 9

If I flash FIRE-ICE kernel before SuperSU-v2.74-2 it fails but with

SuperSU-v2.72 it worked just fine. Note: the kernel edits the ramdisk

i get

----- file_contexts -----

Loading from cpio:[file_contexts.bin] ...

Decompiling binary file_contexts format ...

Saving to cpio:[file_contexts.bin] ...

Loading from cpio:[file_contexts.bin] ...

Append@0383 []
Append@0384 [# SuperSU]
Append@0385 [/su(/.*)? u:object_r:system_file:s0]

Saving to cpio:[file_contexts.bin] ...

----- done -----

Saving to [/sutmp/ramdisk] ...

- Creating ramdisk backup
[COLOR="Red"]Segmentation fault
--- Failure, aborting[/COLOR]

*************************
IMPORTANT NOTICES
*************************
First reboot may take a
few minutes. It can also
loop a few times. Do not
interrupt the process!
*************************

- Unmounting /system
- Done !
I:Updater process ended with RC=0
I:Legacy property environment disabled.
Updating partition details...
I:Data backup size is 1478MB, free: 23717MB.
I:Unable to mount '/usbstorage'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=0

just a thought. it would be nice if the script did not exit on every error or an override to stop it
[SuperSU] Chainfire:
Please post a link to the exact download of the kernel you are using.

No.
[SuperSU] krico:
Thanks Chainfire. I now have root back again. ????
[SuperSU] USBhost:
Here you go! :cowboy:
[SuperSU] JustMeToo:
I have the Samsung Tab S2 T817W. I had Android 5.1.1 with root. I wiped everything and odined Adroid 6.01. Odined TWRP and flashed the latest Beta 2.74 but had no root. Wiped everything, odined Android 6.01, downloaded the CF Auto Root for my tablet and odined it. Still no root. For a second I thought I had root since it showed the SEAndroid warning when it first rebooted after I odined but it rebooted immediately 2 more times and in those reboot the warning was not there anymore. I tried to read the instructions here, https://plus.google.com/+Chainfire/posts/XMFgencRR11 but I must admit I didn't understand what I'm supposed to do to gain root.
[SuperSU] SAGI1:
Description: Secure Booting Error - Boot certification verify message on boot (supersu issue)

Device: LG G PAD 8.3

Software: Android 4.4.2 V50020F Upgrade to 6.0.1

Steps to reproduce:

1.	Download and install IORoot25 from the provided link http://xdaforums.com/showthread.php?t=2703825

2.	Install gpad usb drivers on your PC

3.	Root your device as explained in the next video https://www.youtube.com/watch?v=05T3mYVnYYE

4.	Navigate to play store and download root checker and see that the device is rooted

5.	Navigate to Play store and download TWRP recovery

6.	Install TWRP 3.0.2.0 recovery

7.	On SD card Make A new folder with: open_gapps-arm-6.0-nano-20151203.zip

BETA-SuperSU-v2.74-2-20160519174328.zip and cm-13.0-20160520-UNOFFICIAL-awifi.zip

8.	Navigate to Recovery twrp 3.0.2.0

9.	Press wipe and Wipe Dalvik + cache + system + data + internal storage

10.	Navigate back and select install

11.	Install Rom + Gapps + SuperSu

12.	After All success press reboot system

Expected results:

The Gpad will load the new rom as expected

Actual results:

Secure Booting Error - Boot certification verify message on boot

Comment: flash again without supersu it worked as expected which version of supersu do I need?

tried 2.68 same results

tried 2.45 stuck on lg icon
[SuperSU] H4X0R46:
Hey guys, quick question. Where does SuperSU backup your boot partition? I see the su.img in /data, but can't find where the backup is, or su.img the backup? Thanks! The thing I'm trying to do is delete the backup so I could reflash a stock boot.img, install a new version of my custom kernel, and then reflash SuperSU without having it restore that backup. Thanks guys!
[SuperSU] egingell:
It's not "su.img", that gets mapped to /su, but it's in the same directory. Mine is named "stock_boot_[some hex number].img.gz". If it's not there, then I don't know where else it would be.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] H4X0R46:
I see that on mine! So this would need to be deleted for my needs here? Also, the dev for the kernel I am going to use said to also delete su.img as well when flashing the update, does deleting the su.img completely break SuperSU? (I assume it does) Would I be able to delete su.img using a root explorer successfully? I know it's a bit strange, but the dev said to delete the backup as well as su.img before flashing a clean one, so SuperSU doesn't have any recollection of a backup or being installed before. Thanks so much for your help! Much appreciated!
[SuperSU] egingell:
I don't know why you wouldn't be able to delete them. At worst, you just reflash the stock ROM, TWRP, and SuperSU to get them back.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Fif_:
SuperSU won't install if it detects an already patched boot image and can't find the original boot in the backup file.
[SuperSU] H4X0R46:
I would flash a stock boot.img with fastboot, then install a kernel. SuperSU should install fine after these steps correct?
[SuperSU] Fif_:
Yep.
[SuperSU] 84Odin:
I have installed on my Galaxy S5 SM-G900F , the Sixperience S7 Port V1 Rom. With the SuperSu Beta 2.70 . Can I install with TWRP Recovery, the SuperSu Beta 2.74 ? Or I'll get problems with my installed Rom ?

Thanks for any help and answer .

Greeting 84Odin
[SuperSU] knpk13:
In the 2.74 update, are both the normal and ramdisk backups created? Or does the ramdisk backup permanently replace the normal backup?
[SuperSU] Fif_:
What are normal and ramdisk backups?

I think you may be confused.

During the initial SuperSU installation, the boot partition is backed up to /data/stock_boot_*.img.gz, then patched.

In systemless mode, a "ramdisk" (actually a loopback filesystem) is created in /data/su.img. This "ramdisk" is then mounted on /su.
[SuperSU] knpk13:
No, not that. In 2.74, a new backup mechanism was introduced. Read the Google+ post changelog by chainfire. I want to know whether that replaces the older mechanism, or whether both mechanisms exist in 2.74 (because chainfire mentions at the end of the Google+ post about custom Roms/kernels compatibility)

Edit : You can see a few posts back that 2.74 didn't work with someone (it was [MENTION=5501864]USBhost[/MENTION]) using a custom kernel which modified the ramdisk

I'm using 2.74 without any problems by the way.
[SuperSU] Fif_:
Ah, that partial backup.

It supplements the older /data/stock*.img backup mechanism.