yashsingh1/xdaforums huggingface dataset:
[SuperSU] tuiyaan:
[MENTION=6952047]grep_i[/MENTION]

i cleared all system cache davik except for ext sd.

flashed newly stock rom

i dont understand why CM traces are appearing in log

i flash again n try with sr4
[SuperSU] unarj:
I revisited this again today and got it working. poking around in the /data I noticed two .img files that were probably leftover from a previous attempt. deleted those and the '.supersu' file to get a stock flash. worked this time. woot.
[SuperSU] ruchern:
I'm running SR4 but got this message.

[MENTION=631273]Chainfire[/MENTION]?
[SuperSU] Agares69:
Not only dual sim, the problem is there with LG G4 as well on some cm based roms. Interesting that cm14.1 on my device was running without problem with SR3, but RR doesn't nor aokp. :/
[SuperSU] Pkt_Lnt:
No one has posted logs. Without logs, it is impossible to diagnose what causes it.
[SuperSU] Agares69:
Sorry, my recovery log is here:

Device: LG G4 (H815)

Rom: Resurrection Remix 5.8 (7.1)

Kernel: the one included in the rom

Problem: no sim card
[SuperSU] wmarcin:
Another Sahmu user with a bootloop. I read back and noted that files may need to be deleted from /data folder. Is it the data folder in Internal Memory, or in the root directory?

Edit: found it. Root directory. Accessed with TWRP file manager, deleted offending su.img, reflashed su.zip, and all is well.
[SuperSU] Chainfire:
There's a new SR coming up, fixing a specific SELinux issue that caused some shell scripts not being executed on 7.x firmwares. That release should fix:

- Samsung S7 7.0 Beta Wi-Fi issues

- Samsung S5 ResurrectionRemix-N-v5.8.0 Wi-Fi / modem issues

- HTC10 7.0 bootloop

Those are just the ones I personally tested. I assume it'll fix more 7.x firmwares, as such, all 7.x firmwares that are _not_ working should be re-reported after this release.
[SuperSU] ruchern:
Can't Liveboot work with this variant of Root?
[SuperSU] ulxerker:
liveboot is working with supersu only and it does that fine for me. maybe you have to update liveboot due to some recent changes.
[SuperSU] Chainfire:
v2.78 SR5 released

See the releases notes here: https://plus.google.com/+Chainfire/posts/jpR76YEgaM9
[SuperSU] Hermankzr:
Is that means that the official stable is not compatible with latest Nov patch?

If the stable SuperSU is working fine then why not.. why i need to use SR5?

Okay,let's say that SR4/SR5 was fine, it means i can use the zip from CF-AutoRoot thread which is i think used the stable inside the zip as it is the same work from [MENTION=631273]Chainfire[/MENTION]

Don't know how this all messed up SuperSU too like what happens to xposed
[SuperSU] calaiou:
Sorry chainfire, much respect, sr4 or sr5 dont work in the latest firmware ZPKK of the S7 :( , and i dont want instal phh.su. Comon chainfire :)
[SuperSU] ruchern:
Liveboot is updated and was installed from Google Play.

SR5 did not fix the problem either.
[SuperSU] daywalk3r666:
thx for the update.now supersu works on moto g 2014 without any problems
[SuperSU] Chainfire:
Works fine on ZK1 on my S7 (flat). If you want me to check it out, find me a STOCK download link for the ZPKK for the G930F.
[SuperSU] Chainfire:
It might be useful if you'd state which device and firmware you were using ...
[SuperSU] ruchern:
I am using Samsung Galaxy S5 Plus (SM-G901F) on cm-14 (Android 7.0) with your latest SuperSU SR5.

I can provide adb logcats, but which app do I filter for? The Liveboot app or SuperSU app?
[SuperSU] calaiou:
I am proud that you answered me, im not a pro chainfire, and i dont speak good, im with google trad. I dont have a STOCK download, i just instaled a rom stock of a topic of S7 rom , a rom is made by Ambassadii . Sorry Chainfire, much respect
[SuperSU] kep2008:
Huawei P9, android 7.0-test, stock.

After installing SuperSU-SR5 archive (in other versions, too) i get bootloop.

Of file manager TWRP delete /data/su.img and phone is loaded and working properly...
[SuperSU] umbc1205:
Thanks Chainfire for the 2.27 build. Love getting an early look at some of the Lollipop ROMs that are coming out for the G3

On an installation note... the first time I downloaded the 2.27zip I could not get it to flash or extract on my phone. However, after downloading to my PC and pushing the file to my phone it flashed no problem and I am good to go. Hope this helps to anyone that might be having an issue flashing the zip.

Thanks

Mike
[SuperSU] btdownloads7:
I just wanted to clarify something based on the XDA post about this latest beta -- the article says that this new method can root a device with a locked bootloader, but I'm not sure how that would work. This is a zip that needs to be flashed from a custom recovery (unless I misunderstood that point), and there is no way to flash a custom recovery without the bootloader being unkocked. So, could someone please clarify this for me -- it is actually possible to get this installed on a phone with a locked bootloader? And if so, how would you do it?
[SuperSU] jthatch12:
Thanks for this. I purchased SuperSU pro this morning :D
[SuperSU] ironia.:
yes as to be flashed with a custom recovery, I think it's not possible with locked bootloader
[SuperSU] upndwn4par:
Beta 2.27 working well on Nexus 5 running most recent AOSP build (Lollipop 5.0, LRX21V, android-5.0.0_r7). Stock kernel and boot image.

Have a drink on me:

Confirmation number: 66Y25727FK3587816
[SuperSU] SamuriHL:
It would need to be installed as part of the root exploit being used on a locked phone. No different than how it works today for locked phones. The flashable zip is the convenient way for us unlocked users. :)
[SuperSU] goTouch:
2.27 is great. Wakelock detector is working fine now. As well as Greenify. N5 LRX21O
[SuperSU] spiderflash:
Yes! Finally we have full root access. Previously some shell commands were still being denied but now everything works just as fine as it did on KitKat ;) Thanks chainfire! Im running the ElementalX kernel btw, no problems at all..
[SuperSU] CyberZeus1977:
Hi all,

just a question. I have N4 with modified kernel and Super SU v2.19.

Which is the correct order to install v2.27 and stock kernel?

I think it is:

1. install Super SU v2.27 from recovery

2. flash stock kernel

Is it correct?

Thanks
[SuperSU] Srandista:
It shouldn't matter, but I personally go through this opposite way. Just flash stock kernel with fastboot, and then just go to recovery and install already downloaded SuperSU 2.27.
[SuperSU] CyberZeus1977:
Thank you man!
[SuperSU] Bobboman:
anyone try this on a Moto G 2014 yet?
[SuperSU] danger2u:
[MENTION=631273]Chainfire[/MENTION] so for Droid turbo xt1254 with bl locked this will work??

how can we flash the zip if we don t have custom recovery or bl unlocked?

i tried with the apk but says didn t find su binaries.

thank u
[SuperSU] scott_doyland:
2.27 with stock kernel working fine on nexus 7 original (grouper). Just purchased pro supersu to support chainfire.
[SuperSU] flakinarist:
Same here on N4 Stock Lollipop...
[SuperSU] sekk:
SuperSU

Worked?
[SuperSU] Chaplan:
How do tou flash the stock kernel with fastboot?

fastboot flash boot boot.img

Is this it? I'm on lollipop, nexus 5, google images.
[SuperSU] Srandista:
Yes, I successfully flashed stock kernel and then SuperSU through TWRP.

Exactly, extract boot.img from factory image and use that fastboot command.
[SuperSU] yaonos:
I tried to update my N5 and my N7 to v2.27 tonight.

It's working fine on my N5, Android L (LRX210).

On my N7 (Grouper), running Android L (LRX21P), I was not able to make v2.27 work. SuperSu doesn't prompt me for root requests and the device reboots on its own after a few minutes of activity. I tried many times with the same result each time. I have attached a logcat.

Here is how I proceeded in order to upgrade SuperSu from v2.20 to v2.27 :

- flash stock boot and system,

- erase cache

- install v2.27 with TWRP v2.8.2.0.

I tried to install v2.20 again by using CF Auto Root after having flashed the stock boot and system again with no luck. SuperSu doesn't prompt for root permissions any more and I see some AVCs in the logcat. As it worked before, there may be a issue with one of the applications requesting root on my N7. I suspect BetterBatteryStats to be the culprit as I had troubles with this application when I first rooted after my N7 after its upgrade to L. I will try to find some time tomorrow in order to test v2.27 again without BBS. For now, I am back to stock without BBS and SuperSu and my N7 works flawlessly.
[SuperSU] daystrom:
Another successful install on an original Nexus 7 (grouper) using TWRP 2.8.2.0. Well done Chainfire!
[SuperSU] Agares69:
Thank you, SR5 is working now on LG G4 (H815) RR 7.1
[SuperSU] Chainfire:
From the log, this appears to be a kernel issue to do with loop mounts. Impossible to be certain, though.
[SuperSU] ruchern:
[MENTION=631273]Chainfire[/MENTION]

The Liveboot issue has been solved.

I have no idea what happened and how it worked.

I just full unroot with your SuperSU app and reflash SR5 on top and it worked.
[SuperSU] Leeum:
Flashed on my Galaxy S7 Flat G930F and brightness is high on the lowest brightness and capacative touch buttons don't light up anymore. Running latest ZPKK build
[SuperSU] cwalker0906:
Chainfire will this work on pixels or should I stick to the device specific thread? Thanks for your work
[SuperSU] grep_i:
Boot partition gets out of space
[SuperSU] amburator:
Same here.
[SuperSU] Muhammad Rihawi:
you tried latest one SuperSU v2.78 SR5?

Also did you unroot before you flash this one?
[SuperSU] storm119:
For the record proposed...I tested the latest v2.78 SR5 on my bacon running RR N roms (latest build 20161129)....and its working as expected. Thank you Chainfire :good:
[SuperSU] amburator:
My S7 wasn't rooted on nougat beta, just flashed latest TWRP and SuperSU v2.78 SR5.
[SuperSU] Leeum:
Yeah. Even wiped cache aswell

---------- Post added at 10:57 PM ---------- Previous post was at 10:57 PM ----------

Yeah. Even wiped cache aswell. Flashed back to v2.78 SR4 and no issues
[SuperSU] Muhammad Rihawi:
I just tried Supersu SR5, same problem, camera not working, brightness set to highest and can't be controlled, also every time I restart the phone it's take too much time on Samsung galaxy s7....
[SuperSU] Chainfire:
The S7 firmware you are all referring to is not stock. The S7 is my daily driver and thus not available for too much experimentation, sorry.

That being said, the output of 'dmesg' directly after boot (seconds matter here!) may be helpful in diagnosing.
[SuperSU] Ofthecats:
[MENTION=631273]Chainfire[/MENTION]

I'm using the pixel XL. Unlocked, stock, rooted, franco kernel.

It seems that rooting the phone initially performed a factory reset. Subsequent manual updates followed by root also wiped the device.

Is this intentional when rooting? Or is my case unique, and perhaps due to something else?

Thanks
[SuperSU] SubwayJrd:
Unlocking will factory reset your phone.

How are you performing your manual updates? It is far more likely to be that step than rooting itself.
[SuperSU] Ofthecats:
This has occurred after unlocking.

Manual updates are through fastboot. -w removed from factory image script.
[SuperSU] dratsablive:
Unlocking bootloader will wipe the device.
[SuperSU] Emoliciouss:
Will u fix the cm14.1 bug?

Because if i flash SuperSU into cm14.1 my WiFi isn't working anymore
[SuperSU] Ingenium13:
I've always manually flashed each partition via fastboot, since I never trusted -w removed to actually keep data. However, the Pixel has way too many partitions.... I switched to just sideloading the full OTAs instead. It's the safer option anyway if you want to preserve data, and it's basically the same thing as the factory images. Give that a shot on the next update

Sent from my Pixel XL
[SuperSU] alexcheveau:
Please provide checksum for releases ;)

Mine is:

File: SR5-SuperSU-v2.78-SR5-20161130091551.zip

CRC-32: c51136b1

MD4: 0c20b6858f9de27d761b848347deaa0c

MD5: b568366627fe2cfc6851a9d9b0990c0f

SHA-1: 9fd8bbd98f214293e02faf823554f18a20366169

SHA-256: 539e4a6b61d56926475b82ea7350a7ffe6028933910cc9ff2ead608f900971d9
[SuperSU] andreoide:
Samsung S5 Plus kccat6 SM-G901F stockrom updated to SR5 without any problem.

Thank you Chainfire! !!

[emoji111]
[SuperSU] Normas Interruptor:
I am using the latest Supersu SR5 in OnePlus 3 with oxygen os 3.2.8 (Marshmallow)...

I am getting "Your device does not have root" error every time in few apps...

i have tried SR4 and stable version also but same error.

Even though root explorer and es explorer working fine.

View attachment 3954035

Sent from "Oneplus 3" via XDA apps
[SuperSU] _alexndr:
Unfortunately, I can confirm that issues still exist... even in case of official-leak for S7 edge G935FXXU1ZPK4 (Odin flashable).

System partition -

without triggered dm-verity

. Before rooting - 100% pure stock, officjal binary/system status..

In my case 2.78 SR5 breaks:

- stock Camera (FC)

- stock Torch :D

- proximity sensor, light sensor etc...

- manual brightness adjustment

Phone is almost unusable, especially without proximity sensor :( :( :(

Before I came back to latest 6.0.1 - I entered dmesg command as fast as possible after restart (in terminal emulator):

su
dmesg > /storage/emulated/0/dmesg.txt

See attachment :)
[SuperSU] Chainfire:
Interesting, I'm running the exact same firmware, but G930F instead of G935F, and none of these issues occur.
[SuperSU] _alexndr:
I flashed ZPK4 firmware only for test (it automatically wiped all data), then setup wifi and google account - all things worked fine - camera, sensors, etc...

After rooting - all issues I mentioned has appeared, unfortunately... After full unroot - all went to normal :)

I just restored FF backup with BPJG, but if you need additional help/tests/logs - no problem, but maybe tomorrow in the evening.. (I have to get up for work.. early in the morning)
[SuperSU] SubwayJrd:
Have you ever updated with the -w removed, then booted into Android before installing root just to verify everything's OK?
[SuperSU] :
That's what I'm thinking to. It seems to hardly restricted on loop mounts since even if you try another partition it just won't work. Magisk won't work either. V6 installs but same issue. V7 and above actually fails to mount in twrp. But I think he uses my twrp which isn't official but does in fact patch everything needed. About the kernel. Any modification except your supersu patch seems to cause boot failure. So it have to be something with either kernel or bootloader protection by Huawei? Since if you try change something before patch it'll fail to boot after you use your patch. Same goes other way around.

You have some logs here http://xdaforums.com/showthread.php?p=69861858

It can be both systemless su and system mode su logs provided.
[SuperSU] Ibuprophen:
Please correct me if I am wrong.

When you select a router or an open WiFi to connect to, and then put your password in (if needed), and it seems to connect but, there's an exclamation mark next to the WiFi icon (at the top) and find that it just states that it is trying to connect.

And you find that this happens with any WiFi access point.

Am i correct in describing the issue you are having in CM14.1?
[SuperSU] ruchern:
Thanks.

Got a match for MD5.
[SuperSU] netfortius:
Is this a proven method for rooting HTC 10? Haven't found any other references, besides this site...
[SuperSU] Ibuprophen:
Here are some links that may assist you...

http://xdaforums.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025

http://xdaforums.com/htc-10/development

http://xdaforums.com/htc-10/how-to

As for the best way to root an HTC 10... I would advise you to post that question within one of the HTC 10 Forum threads.
[SuperSU] jcsww:
SR5 is working fine on the Nexus 6P. [=
[SuperSU] ipdev:
[MENTION=3352400]netfortius[/MENTION]

https://plus.google.com/+Chainfire/posts/jpR76YEgaM9

Not sure on the steps needed.
[SuperSU] haleem320:
[MENTION=7780062]chianfire[/MENTION]

Bro I have problem with Unicon root access

In S5 g900f stock marshmallow xposed installed

Flashed latest SR5 version

Help me

Thanks
[SuperSU] bdwilk:
Hint: he might not reply if his name isn't spelled correctly. Just trying to help out. :rolleyes:
[SuperSU] Emoliciouss:
Nope it just doesn't show any networks ;p its like my wifi card crashes or something
[SuperSU] Alxoom33:
SuperSu 2.78 SR5 working great on NEXUS 6 running Android 7.0 NBD90Z.
[SuperSU] Chainfire:
I'll give this some more thought. From your logs, it seems like a service is constantly crashing that is working fine on my device. Now I wonder if that is the same issue as those on ZPKK are seeing...

If anyone here is on ZPKK, a dmesg from as quick as possible after boot would be helpful. Logcat as well, but dmesg first.
[SuperSU] okidokiss:
No app icon

Hi all,

Just installed SR5!

Is working fine but there's no icon to start the app.

Can't find it anywhere, except with ES ESPLORER but even there I can't start it.

On Google Play reports the app as installed.

already tried to flash it again.

Was installed with zip file.

Any advice?

*See signature for system details.
[SuperSU] piskor:
Advice http://xdaforums.com/galaxy-s4/i950...enmod-14-0-t3479888/post69816694#post69816694
[SuperSU] _Exeedy_:
Dear [MENTION=631273]Chainfire[/MENTION]

On g935f edge feeds with swipe gesture won't work anymore when i use SR5-SuperSU-v2.78-SR5-20161130091551.zip.

But thanks anything else works good =)
[SuperSU] grep_i:
Did you remove the built in root of CyanogenMod before flashing SuperSU
[SuperSU] :
Navigate with a root browser or in twrp and remove the file it should be in /data/ folder and re install the apk.
[SuperSU] vandiaz_sairavinz:
help su

For miui8 build 6.11.24 not work
[SuperSU] ruchern:
Why are you moving TiBackup to System?
[SuperSU] vandiaz_sairavinz:
all move apk not work mount to system
[SuperSU] Ibuprophen:
I asked because i tried CM14 on my phone and had a different WiFi issue than yours. So i reinstalled CM13 till I get around to figuring it out further. I thought there might be a link but, i am guessing that there isn't. Sorry.

So here's my next question... What prompted you to post your WiFi issue within the SuperSU Beta Thread?
[SuperSU] Emoliciouss:
I tried stable and beta both the same problem and i didn't really know where else i had to post it ;p
[SuperSU] andrew2432:
Try other system app movers. I had to try a few when going to systemless su the first time
[SuperSU] bdwilk:
ASUS ZenFone 2 Laser (ze550kl)

RR N 20161129

SR5 works
[SuperSU] Ofthecats:
I am aware. I meant my device has gotten wiped even when my bootloader was previously unlocked
[SuperSU] Ibuprophen:
Is the device, in question, a d2vzw?
[SuperSU] Emoliciouss:
Its a SM-G900F
[SuperSU] piskor:
It wasn't my problem and as I can see my advice helped [MENTION=2314311]okidokiss[/MENTION] http://xdaforums.com/showpost.php?p=69879504&postcount=866
[SuperSU] _alexndr:
As nobody else can help quickly enough - I just made new backup and will flash (in about quarter) ZPK4 again to provide you e.g. logcat after boot and what is happening while camera crashes

In the meantime please write me what else can I do to help you before I restore 6.0.1 (because I can't live with these issues for a longer time) :)
[SuperSU] Chainfire:
I honestly don't know. You can just wait it out though, I don't have time to fix it right now anyway.
[SuperSU] jadams161:
I don't normally follow su updates, usually rely on the rom dev to do an update. I am on SR1 that was loaded with xdabbeb's 3.1.1 rom on my LG G3. Is it necessary to flash this latest version of SU?
[SuperSU] bdwilk:
It's not necessary as long as your device is working the way you want it to.
[SuperSU] _alexndr:
There is no hurry :good: please look in the attachment when you have time :fingers-crossed:

Thanks for your great work :)
[SuperSU] Fif_:
Is anyone still setting SU requests for zygote64?

Just experienced 3 of them within 10 minutes.

Feeling adventurous and with a fresh backup I granted SU access once while having full logging turned on in SuperSU.

No log record was written, which is strange.

This is with:

SuperSU 2.78 SR5

OmniROM 6.0.1 20161123

Nexus 5X bullhead

I'll try to capture a logcat next time.
[SuperSU] jadams161:
What wouldn't be working?
[SuperSU] shaggyskunk:
v2.78 SR 5 working properly on SM-N910W8 & SM-N900W8 Running Android 7.1 CM14.1 based Roms. FYI

Sent From My SM-N910W8 ðŸ‡¨ðŸ‡¦
[SuperSU] Ibuprophen:
You may need to locate a possible Modem/Baseband Update to your Device. Your model device has a handful of Modems/Basebands that were used by the manufacturer.

The following link is an S5 dummies style page:

http://androidforums.com/threads/42-galaxy-s5-models-dummies-guide.892162/

I had also found a helpful lead that will aid in getting you started:

http://xdaforums.com/showthread.php?p=52210611#post52210611

You will be able to locate your Modem/Baseband version in your devices Settings --> About Phone and scroll down till you see the Baseband Version.

NOTE: The terms "Modem" and "Baseband" is essentially the same thing.

Good Luck my Friend!
[SuperSU] lge73:
Tried on my G930F, Android 7(nougat beta ZPKK) and i can confirm camera not working!
[SuperSU] ambasadii:
check_zero_def "- Patching init.*.rc, fstabs, file_contexts, dm-verity" "$COMMAND"
[COLOR="Red"]check_zero_def "- Restored original file_contexts.bin" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-add /sutmp/ramdisk /sutmp/ramdisk 644 ${CPIO_PREFIX}file_contexts.bin $COM/file_contexts.bin"[/COLOR]

seems to patching init breaks some things on nougat beta for S7/S7E

maybe this will help you to find your solution ;)
[SuperSU] Alxoom33:
Go on Play Store, delete and reinstall SuperSU app.
[SuperSU] Rebel7022:
Can i flash this in cm 13
[SuperSU] Chainfire:
So... are you saying keeping file_contexts.bin original solves the problem?

You're being vague.
[SuperSU] ambasadii:
All most,only camera still not work with SR5. On SR4 without init patch all works.

With init patch we got more bugs like:flashlight,mtp,recent key led,camera and meaby more.
[SuperSU] surfsyco:
Delete
[SuperSU] Codebucket:
Bootloop with the latest SuperSU on my Xiaomi Redmi Note 3 with CM 14.1, will give logcat soon.
[SuperSU] Surge1223:
I guess those of you waiting could check pstore after your device boots up, when I make sepolicy edits in aosp and have boot issues, etc I almost always find out where I screwed up by checking /sys/fs/pstore/pmsg-ramoops (as long as previous boot got to bootanimation)

Since Chainfire is asking for dmesg, I assume he want to see the start up and init Initializing services etc. But console/dmesg ramoops might contain more info.
[SuperSU] Chainfire:
Right you are. pmsg-ramoops, console-ramoops, and similar files from /sys/fs/pstore/ can all be helpful. But keep in mind they are from the previous boot.
[SuperSU] jcmm11:
So where are the logs and dmesg as was requested? (see other messages on these last few pages for other files that can be helpful as well)
[SuperSU] Chainfire:
So, the interesting thing is, that I can see the camera is an SELinux issue. It's violating a rule that is explicitly whitelisted in the SELinux rules of my copy of the S7 Nougat Beta. Which is plenty weird.

Combined with the other issue regarding file_contexts.bin that has been posted, I'm quite baffled.

Please post your boot.img from the firmware both before and after SuperSU has patched it. That might help me.

Otherwise, I'm considering doing a partial SELinux-code overhaul in SuperSU in the next few weeks that might get rid of the issue altogether, but nevertheless I'd like to figure out the exact cause of these issues before I go there.
[SuperSU] mehsad89:
Hi i need superSu for samsung galaxy i9300 cm13 please help me
[SuperSU] :
For real? Can't you read? Look at the first post...
[SuperSU] _alexndr:
No problem :)

boot.img (stock) + bootsu.img (patched by SR5's ZIP installer):

https://www.dropbox.com/s/393urxf9eswa1bg/bootsu.zip?dl=0
[SuperSU] mehsad89:
My bad english .my can not read english
[SuperSU] graw2:
Finally SR5 works fine on my Xiaomi Mi5 using Android 7.0 based MIUI8....Thanks a lot!

Previous release SR4 caused IMEI2 lost and messed up SIM Cards & Mobile Network Settings