yashsingh1/xdaforums huggingface dataset:
[SuperSU] corkiejp:
The SR3 flash of supersu is removing the supersu app, on the nexus 9 I had to install the app again from inside the zip (common folder). Don't use the playstore version or you will not be on SR3. See my post on the previous page.
[SuperSU] stevetrooper:
Tried that, says that root binary is not located on my device. I think there is something that the November security update did that is not allowing root to stick.

---------- Post added at 11:45 PM ---------- Previous post was at 11:40 PM ----------

I noticed that when I run the supersu SR3 script in TWRP it is failing with this message:

Calling user ramdisk patch script

--- Failure, aborting
[SuperSU] corkiejp:
[MENTION=2723217]stevetrooper[/MENTION] Make sure you have the latest TWRP for your device.

Alternatively try using the CFAR method to root. And if that doesn't give you the latest supersu, try using flashfire app to flash the zip.
[SuperSU] JohnCorleone:
Does the latest SuperSU beta no longer require a "force encrypt" version for people like me who have a HTC 10 and are running systemless root and systemless Xposed framework? The latest version I have found that is reliable is the BETA-SuperSU-v2.74-forceencrypt.zip. I found a 2.78 forceencrypt version that someone else made but the zip was too small to be a valid file. Thanks
[SuperSU] stevetrooper:
[MENTION=4868912]corkiejp[/MENTION] I tried using CFAR and that worked, once it rebooted, I was on 2.74, updated supersu in the play store and then the binary was upgraded to 2.78. I found that others are having the same problem with the new 7.0 November security update. Thanks for the hint...
[SuperSU] candys.world:
Rw permissions

Hi, I am having an issue where I have no rw, permissions. I have ro and that's it. With any kind of root I would think I would have read/write but its almost as if I have no root at all. My goal I guess is to pretty much do what I want as far as deleting certain things and have write permissions. Is it just this way with systemless now? Maybe I'm a bit confused on that.
[SuperSU] ashyx:
You need a root file browser with the capability to mount the file system rw.

I highly recommend root explorer.

Probably the most stable and works 100%
[SuperSU] dimitryakkai:
I've got also a I9100 and the same "ramdisk extracting" problem.

I've tried to follow your way, but after reading dozens of tutorials, trying all the i9100 6.x ROMS and thousands (almost...) versions of mkbootimg/umkbootimg and others exotics "kitchen image" tools, I've never succeded to correctly unpack/repack a Boot Image.

So far, I've concluded that samsung Boot Image don't respect standard Android Image, so the ANDROID! magic header is never detected by tools such as umkbootimg, and specific offset have to be applied for unpacking/repacking ! But I really don't know how to proceed now...

Have you succeeded to unpack/repack your Mokee ROM ?

Can you give a few hints on how you did that ? (I'd like to do the same with a CM13 or DU ROM !) Or just share your patched ROM or boot.img ?

You would be my savor for ever...
[SuperSU] corkiejp:
By the above method your probably not on 2.78 SR3?

Flash SR3 wth flashfire app and if the supersu app gets removed, Install it from inside common folder of SR3 zip.
[SuperSU] falseman:
by flashin this will i get systemless root? if not can you give me the link to the thread, cuz im searching crazy and cant find it...
[SuperSU] andrew2432:
Gotta backup? Twrp that and start over!!
[SuperSU] ashyx:
I have unpacked/repacked countless Samsung boot/recovery images no problem.

They are pretty standard boot images regardless of whether Exynos, Qualcomm or spreadtrum.

There are a few exotic ones out there, but Samsung are for the most part pretty standard.
[SuperSU] Chainfire:
Many older Samsung devices - including the I9100 Galaxy S2 - use a non-standard Android boot image containing both normal boot and recovery. These are not un/re-packable by SuperSU or other tools that expect the ANDROID! boot image.

If memory serves me right, the first Samsung using the 'standard' Android image was the I9300 Galaxy S3.
[SuperSU] rotational:
I'm having a similar issue (I've seen a number of people describing similar symptoms). Everything appears to install properly, however the device hangs on the boot animation after supplying the device PIN. I've tried a number of combinations of NBD91K and SuperSU 2.78 releases with no success - all attempts result in the same behavior as above.

I've just reverted to NBD90X and 2.78 stable and everything went normally, and will just wait for this to get ironed out.

edit: one workflow I did not try was a full unroot via SuperSU prior to flashing. I noticed after reverting to NBD90X that my SuperSU PIN was still active - when I have some time later I will try to give this a shot.

edit 2: the following procedure was successful for me just now, going from NBD90X to NBD91K:

1. Full unroot via SuperSU, forced reboot

2. Uninstall SuperSU pro

3. Reboot to bootloader. Flash everything except userdata from factory image for NBD91K via fastboot (there is a bootloader version change, so I flash that first and then reboot to the bootloader before continuing).

4. Flash (unofficial) TWRP 3.0.2-3. Enter recovery from bootloader.

5. Allow TWRP /system modifications. Reboot directly to recovery (this reboot might be unnecessary).

6. Install SuperSU 2.78 SR3 from TWRP and reboot.
[SuperSU] photolarry:
Attempted to root NPD91P which is November patch level. Went back to stock, then tried flashing SR3.... Just say on not animation for fifteen minutes until I hard booted into the loader and used phh instead. Not sure why this error happens since I'm guessing not big difference between 90 and 91. On Nexus 6

Edit: I'm about to try above suggestion of flashing factory images, unroot, etc.

Update: unroot, flash all images, re-root works fine.
[SuperSU] kimikim0:
is latest sr3 no longer support disable force encryption ?
[SuperSU] summer_love:
I thought my phone was hanging on boot after the new update like other people's 6Ps, but it was encrypting so I've lost my data after rebooting to bootloader. Please be careful updating 6Ps people. :(
[SuperSU] KPOCAB4EG:
pls add support for s7 with 7.0 thanks!)
[SuperSU] mobileman88:
That happened to me months ago. I stay encrypted now
[SuperSU] thefairlady350z:
Trying to flash this through Flashfire, do I select any of the options below?

- Auto-mount

- Mount /system read/write

- Restore boot and recovery images

TIA guys.
[SuperSU] egingell:
You don't need any of those, the script in the zip decides all that automagically.

And you definitely don't need to restore boot and recovery because you're not flashing a full ROM or OTA.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] thefairlady350z:
Thanks, should I choose anything for EverRoot too? There is an option for "Inject SuperSU". Or should I just ignore that and flash?
[SuperSU] egingell:
No, because that's what you are flashing. Those options are for full ROM/OTA.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] grep_i:
Weird question, you're flashing SuperSU and now you're asking if you have to "inject SuperSU" to the flashing of SuperSU.

Basically flashing SuperSU after flashing SuperSU [emoji30] [emoji102]

Just ignore all that and keep it simple just flash what you need nothing more nothing less.
[SuperSU] summer_love:
I really wish I had just waited it out instead of thinking it was hanging. Also wish I hadn't got quite so bad at backing up ?. Probably needed this lesson...
[SuperSU] mobileman88:
Yeah. Phone was extremely hot as it was encrypting for me too. I rebooted after 1.5hrs and nuked all my data.
[SuperSU] fjsferreira:
When flashing on the just released N7 beta for the Galaxy S7, it works but then the phone keeps complaining of unauthorized modifications and some functions (like wifi, auto-brightness and bluefilter) stop working.

Is there anything you can do?

Sorry for asking about supporting beta software.
[SuperSU] thefairlady350z:
Thanks guys, really a noob at using FlashFire.

It didn't work out for me though. Once i pressed flash, phone just turns off, waited for a few minutes, nothing being done at all. And I thought i bricked my phone. I tried turning it back on and luckily it turns back on...phew. WTF could i have done wrong??? It's a pixel XL rooted with 2.78 SR2 with ELX 0.05 kernel.
[SuperSU] egingell:
Stupid question: Is your phone rooted or are you trying to flash zips with FlashFire, which requires root, on a phone that's not already rooted?

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] thefairlady350z:
Yes my phone is already rooted as i mentioned, else i wouldnt be able to even get into flashfire at all. All I am trying to do here is update SuperSU from 2.78 SR2 to SR3.
[SuperSU] grep_i:
I'm not quite sure if FlashFire is already updated to work with Android Nougat 7.1

Look at the changelog of SuperSU 2.78 SR2

The only way to do it right now is through custom recovery or "boot to images".

Make sure you read changelogs of SR2 and SR3 carefully.
[SuperSU] egingell:
I must have missed that part. Anyway, it sounds like your phone just shut itself off. Maybe it actually did stuff and didn't restart? Check what SuperSU version it says in the SuperSU app.

Is it systemless? Maybe FlashFire won't flash over systemless? Maybe another problem. I think FlashFire keeps logs. Check those.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] thefairlady350z:
You are right, I still have to do it through boot-to-images. Thanks!
[SuperSU] summer_love:
Same here, it was the heat that worried me the most! I'm on the Nov patch now (but used SR1 because I'm scared :p). Tempted to just encrypt it myself now so I don't make the same mistake again.
[SuperSU] mobileman88:
Yep. Now that mine's encrypted for the past few months, never had to worry about accidentally encrypting it. The november update did not work for me with suhide which I use for AP. So I have moved back to the Oct update. Each time restore Nandroid, for 6.X all my SMS and call records are restored. But for 7.X it seems that all my SMS data are lost and I have to use SMS Backup/Restore app to restore it. Hope this helps.
[SuperSU] osm0sis:
Since it recently came up here, my updated unSU Script zip is now available! :D

Posted/linked in my Odds and Ends thread. It improves SuperSU support, now handles ROM su binaries, and also SuperSU Systemless (though of course an unrooted boot.img flash is still necessary). :good::)
[SuperSU] GidgetTheGnome:
tried to flash using flashfire on my rooted sm-j320az from cricket, it causes the blue screen, device is locked. installed via apk and worked
[SuperSU] followmsi:
I do have similar problems on Pixel C and the November changes ..

After SuperSU Installation with fresh boot.img the system did not boot twice - just once and started directly to encrypt my data.

Did cancel and restore data partition from backup .. takes time but no problem. :)

Tested SR1 and SR3 - same result.

My Pixel C is running on 7.1.1 Preview 1 (NFP10C).

But I do use own compiled kernel based on google tegra sources to build a new boot.img.

The used ramdisk is extracted from stock factory NFP10C boot.img

Running October kernel commits it's working fine to root .. SR1 and SR3.

But running November or even Preview 1 tegra kernel sources will kill SuperSU installation.

Here you can see the kernel change log ..

https://android.googlesource.com/kernel/tegra/+log/5369ac86bb1fec13ae7e1fc979e8f1f16b1e192b

Something between _r18 and _r36 is "killing" SuperSU installation.

Sounds still strange to me .. just the new kernel binary will disturb SuperSU.

But I can replicate the issue, at least on my Pixel C.

[MENTION=631273]Chainfire[/MENTION] do you have an idea ?
[SuperSU] Alxoom33:
Not sure, but if you first restore prior 7.0 backup, instead of flashing Android 7.0 over the 7.1.1 beta update, it may solve your issues.

I am skipping the November 7.0 update, and waiting for the beta 2 Android 7.1.1 hopefully being released soon. [emoji469]
[SuperSU] followmsi:
System.img and vendor.img are still unchanged on NPF10C - 7.1.1 preview 1.

Even the ramdisk is from 7.1.1.

I believe only the changed kernel binary is causing the failed SuperSU installation.
[SuperSU] EatBeans:
Hey, is it possible to disable dm-verity without flashing a custom kernel or this supersu?
[SuperSU] zelendel:
Simple answer is no. That flag is in the kernel.
[SuperSU] grep_i:
Didn't you know that encryption is default now starting with Android 7.1.1 as far as I know it was already mentioned by Google a couple of months ago that this would be the new default as of Android 7.1.1 it's even available in 7.0

I do it from the head now and do not know if I remembered correctly because I'm not in to the Pixels or Android Nougat bussiness but I guess they called it

File Based Encryption

or something similar

And since you are testing all this things now with your developer preview software these things can happen you were warned before using the developer preview.
[SuperSU] EatBeans:
But chainfire has included a kernel patch in his supersu file that disables dm-verity. So why wouldn´t it be possible? Couldn´t i create a simmilar kernel patch and use it?
[SuperSU] _that:
Sure, but you asked if you can disable dm-verity without flashing a custom kernel. The answer to that is no because the flag is in the kernel's ramdisk. Of course you can use a modified boot image to disable dm-verity without using supersu.
[SuperSU] EatBeans:
Okay, that's my fault :D Do you know how to write such an Kernel Patch because I've no idea how to do this :P Maybe my specs help you: Oneplus and Cm14.1.
[SuperSU] followmsi:
Excactly .. unpack boot.img .. remove "verify" flag inside fstab and repack again. ;)

---------- Post added at 10:43 PM ---------- Previous post was at 10:29 PM ----------

forced encryption is existing since android 6.0 .. at least on pixel c.

Until now, and hopefully they will keep it, SuperSU is manipulating the ramdisk of your boot.img and make several changes.

One of the changes is to remove forced encryption flag inside fstab in your ramdisk - inside your boot.img.

As we want to remove the encryption completely, the new "File based encryption" seems not to be related for this issue.

FBE is available since final version of 7.0, there were no problems on October 7.0 release.
[SuperSU] skulldreamz:
Disregard...
[SuperSU] Hannibal226:
Hey guys!

I'm experienced on my Hammerhead (N5), too, that with november patch I could flash SR1 but not boot up and tried SR3 with same behavior.

Just wanted to ask if this is an "official" problem now or ppl here could even root november patch systemless with SR3?

At this point thanks to [MENTION=631273]Chainfire[/MENTION] for all his amazing work.

CHEERS!
[SuperSU] m1st3r1:
Did you use suhide before? Remove it first to boot up.

And 278SR3 asks to update its binary in mine (im using aosp with November patch). What happened? It's working well in most apps tho.

edit: nvm, reflash supersu fixed it. i think it's because i tried to run RootSwitch.

Thanks.
[SuperSU] Hannibal226:
I updated rom with wiping System with caches. This let rom running fine.

When flashing SR3 systemless it will load boot for hours.

So u mean an previous isntallation of suhide bringing this probs? Never experienced the last two updates.

CHEERS
[SuperSU] grep_i:
You must be on custom rom because there is no November update for Nexus 5 hammerhead, Google dropped support for that device latest available patch is from October 2016.

CAn you tell us more about which rom your rocking ?
[SuperSU] m1st3r1:
Yes, even with wipe system the installation of suhide is still exist. Remove it with suhide rm, and it'll work fine (at least in mine).

I struggled with this last night :D
[SuperSU] Hannibal226:
Sure, but this souldn't make any changes on root, as it's the same "rom" as before, here u go.

Ah ok, so I'll try this. and report back ;)

CHEERS

UPDATE:

Working fine now. Thanks man.

But perhaps u better said that I even shouldn't flash the suhide back again after root, which I tried for sure :D

So root is working fine, but suhide not ;)
[SuperSU] emontes:
Hello!

I use cyanogenmod and supersu hasn't been workiny for me at all, it doesn't matter if I install via Google play or via a zip file in recovery.

When I restart and open supersu, it tells me there's no su installed. Root checker says the app is installed, shows the su binary but it cannot get root.

Tried with sr3 and the stable one.

Phone is an oneplus 3 and I use cm 14.1.

Any ideas on what I could be missing?

Thanks.
[SuperSU] ashyx:
Why would you need supersu, why not use CM's native root?
[SuperSU] emontes:
I want to use su hide for some apps and was also curious to why it stopped working (used to work fine for me on cm 13).
[SuperSU] ashyx:
Are you using SR3?

Observe the output when flashing the zip. Look out for any error messages.

Are you using TWRP?
[SuperSU] emontes:
Yes, I tried with sr3 and stable.

No error when installing at all and I'm using twrp.
[SuperSU] ashyx:
Post up the recovery log file. after flashing supersu, it may have a clue.
[SuperSU] NegativeOne:
Will this work with the OTA update released recently?
[SuperSU] emontes:
Saw some errors on the recovery log about files already existing and not being able to remove some which do not exist.

Attached is the recovery.log.
[SuperSU] nelgarciac:
Question?

this version is compatible with cm-14.1 OFFICIAL?

Devices: Motorola Moto G2 XT1063

ROM: cm-14.1 20161111 NIGHTLY

Recovery: TWRP 3.0.2-3
[SuperSU] vandyman:
CM already comes with root, not sure why you would need SR3.

Ask your question in the CM thread for an answer.....
[SuperSU] Ibuprophen:
Okay, First... Though SuperSU is not required for CM13/14, it is a user preference to use SuperSU instead of CM to manage Superuser access. I have used SuperSU for a real long time and personally prefer to use it to manage Superuser access.

Second... The SR releases of SuperSU is for testing purposes only and is stated so on the very first post by its dev Chainfire. Unless your experienced and are willing to install a test release, I would highly recommend using the Stable release of SuperSU v2.76.

Lastly... The SuperSU should be compatible with a properly rooted Android 7.1 Nougat (CM14.1). There are no guarantees for anything but, if you would like to test the latest stable version of SuperSU, be sure you do a backup and, as I always practice, hope for the best but, always prepare for the worst (ie... Reinstalling CM14.1 everything else).

Just a quick note, you should also look around your device's posts within the CM and XDA forums to see if and what was posted regarding this but, device specific. There could be a post of a similar question that has more information than this thread can provide. Always do your research.

Good luck!!!

---------- Post added at 03:14 AM ---------- Previous post was at 03:07 AM ----------

I would recommend you chilling out a bit. That was a legitimate question the user needed to be guided a bit elsewhere with (as I did).

If I don't have an answer, I don't provide one and If I had provided an incorrect answer, I have always accepted any corrections as a lesson learned to an honest mistake.

Peace and Love!

Peace and Love!
[SuperSU] bdwilk:
Yes it's working fine on my official cm14.1 Asus z00ld.

[MENTION=4769181]vandyman[/MENTION] some apps like flashfire and others created by chainfire require using SuperSU to even work. SuperSU isn't used only to gain root it is a much preferred alternative in managing root access.
[SuperSU] vandyman:
Thanks for the correct answer.

My post was not meant to be rude, but I guess it could sound like it is.

I personally would not use a rom that already has root from a different developer.
[SuperSU] kunalshah912:
Why does supersu (any version) when flashed on cm based nougat ROMs.... It breaks sensors and camera! One plus 2 device. Also phh superuser doesnt break sensors.
[SuperSU] shaggyskunk:
Flashing SuperSU v2.78 hasn't broken anything on any of my devices running Nougat 7.1 - Maybe it's just your device & rom?

Sent From My SM-N910W8 ??
[SuperSU] grep_i:
If I would guess than i'd say that your rom is prerooted with CM superuser, if you want to make use of superSU you first have to clean up the preroot.

I have a cleanup script for that flash that before flashing superSU again

follow this link for the cleanup script
[SuperSU] emontes:
Thanks! I will give it a go and report back.
[SuperSU] emontes:
Ran the script and it told me it had cm root and it was removing it.

Installed super su via recovery and then got the same error.

That's very weird, I used super su for ages and never seen that.
[SuperSU] shaggyskunk:
Yeah I've been running various CM Based Roms that had CM's root - I just Flash SuperSU without running any scripts or anything else - Never had any issues. Just go to Developer Options - Root Access and make sure that Root Access doesn't have anything checked off in it which effectively disables CM's root (if Flashing SuperSU doesn't already).

Sent From My SM-N910W8 ??
[SuperSU] osm0sis:
unSU is more advanced now. Why are you still pushing your edit? :confused:
[SuperSU] emontes:
Tried that too, same error,its just weird but thanks, man.

Will try yours, let's see how it goes. Thanks!
[SuperSU] shaggyskunk:
Maybe try a Clean Flash - Factory Reset - Advanced in TWRP - Manually Wipe System - Data and Caches - Flash Rom - Gapps and SuperSU - Reboot.

Sent From My SM-N910W8 ??
[SuperSU] emontes:
I tried that yesterday but will try again, will come back with more. What a saga! Thanks Lloyd appreciate the help.

---------- Post added at 09:04 PM ---------- Previous post was at 08:24 PM ----------

No joy, tried everything i could think of, it is just too weird.

No idea what's going on.
[SuperSU] shaggyskunk:
What device & Recovery are you on / using?

Sent From My SM-N910W8 ??
[SuperSU] emontes:
It is a one plus 3 with twrp.
[SuperSU] shaggyskunk:
If you're not on the latest version of TWRP - update it - I know that with Samsung devices and Custom Roms etc using an older version of TWRP can cause issues... But I'm just guessing at this point.

Sent From My SM-N910W8 ??
[SuperSU] emontes:
I'm on the 3.x.22 (community modified version?) so recovery works with cm14.1 but It was failing with the latest official so I don't believe that's the problem.

So I have supersu installed, su is there as 2.78 but I still get that message on the supersu screen.

If I go to terminal and type su, it asks supersu for permission (grant), I do it and it just hangs there.

Bizarre isn't it?

Edit: Hmm, just thinking here. Is this "maybe" related to the fact i use f2fs on /data? I had on /cache too but I moved to ext4 to test and no deal
[SuperSU] raptoro07:
I'm on Shamu and have tried SR3 on two different ROMs that have pulled in the November patch and neither will boot. I do believe both are AOSP built if that makes a difference.
[SuperSU] Hannibal226:
Did u have had suhide installed?

If yes, flash uninstall zip first. After reboot then flash SR3.

I had the same problem and got this hint here.

PS: suhide seems not being compatible anymore with november patch. Maybe with a new release from Chainfire

CHEERS!
[SuperSU] valeriee:
Any differences between this and the stable version (2.78)?
[SuperSU] Pkt_Lnt:
http://xdaforums.com/showpost.php?p=64916199&postcount=3
[SuperSU] nzzane:
While trying to flash SuperSU 2.78 SR3 when installing systemless - it brings up an error

Finding boot image

boot image /dev/block/mmcblk0p29

extracting ramdisk

decompressing ramdisk

checking patch status

already patched, attempting to find stock backup

stock restore failed, attempting ramdisk restore

ramdisk restore failed, aborting

PASTEBIN with entire log

I have a Z5C, unlocked bootloader, TWRP 3.0.2, latest firmware - .302. ROM: XPOWER 5

To install supersu in the first place i flashed a custom kernel.