yashsingh1/xdaforums huggingface dataset:
[SuperSU] Hawaiihemd:
Use the force aka 'search'... ;)

https://xdaforums.com/showpost.php?p=70985800&postcount=9167
[SuperSU] nitramus:
For some reason not working on stock nougat HTC 10. Tried 2.78 2.79 2.76 and all seems to go well. At the end it says can't mount system and if I try to reboot system it says no os is installed.
[SuperSU] Robertcamilleri1987:
Hello

Can someone explain me how to root Lenovo Vibe Z2 ?

Myemail Robertcamilleri1987 [MENTION=5499064]gmail.com[/MENTION] .

Thanks in advance
[SuperSU] piskor:
Try this http://bfy.tw/BGoj
[SuperSU] peterlee928:
hi everyone

just want to confirm

sr4 still does not work for pixel xl

as per org post?

much thx in advance :)
[SuperSU] Ch3vr0n:
If it doesn't work then perhaps post some logs so chainfire can get it to work? Or find out why it didn't?

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[SuperSU] Scrapyard Loot:
Not unless suhide was used, although unofficial.
[SuperSU] Ch3vr0n:
Nope, suhide doesn't work anymore. At least not on any rom with nov '16 security patches or later
[SuperSU] DarkDestiny08:
Stuck on Creating image S6 Nougat

This issue persists on S6 G920 running 7.0 Nougat too. will try the adb command and report the results soon.
[SuperSU] dratsablive:
I was getting the bootloop with the first SR4 for ODP1, used the one with the extra delay and it worked like a charm.

/edit/

Spoke too soon. Zip flashed and rebooted fine, but still no root. SuperSU reports it needs to update the binary, but that fails. Root checker shows no root..

Should add Nexus 6P.
[SuperSU] jhulzk:
Thanks
[SuperSU] Hugoghost:
S4 con lineage 14.1 not running

Enviado desde mi GT-I9500 mediante Tapatalk
[SuperSU] voider1:
I want to put SuperSU on the Wiko Freddy. I managed to patch the recovery image so that it would accept OTA updates signed by my own keys. I've also installed Xposed with success, just had to make some minor modifications to the OTA update (remounting /system as rw, the Wiko Freddy handles that in a different way). I can't figure out what goes wrong with SuperSU and I want to patch it so I can make it work with the Wiko Freddy.
[SuperSU] veez21:
So, this modded recovery has busybox installed?
[SuperSU] voider1:
Yes! I have Busybox installed. I installed it when I installed Xposed.
[SuperSU] veez21:
Well, what errors does it show?
[SuperSU] voider1:
I'm getting:

E: Can't run /tmp/update_binary (No such file or directory)
E: Error in sideload/package.zip
(status 255)
[SuperSU] Ch3vr0n:
I think that question is beyond the scope of this topic. I'd post your issues in the SuperSU developer discussion topic https://xdaforums.com/apps/supersu/devs-supersu-developer-discussion-t3291434
[SuperSU] voider1:
I already did, but I got no response.
[SuperSU] Ibuprophen:
That link does have "[DEVS-ONLY]" in the title. I'm assuming that may be a reason for no response (though, someone should have, at least, pointed you in the right direction or something).

Try asking in the following thread and, hopefully, someone will help you out.

http://xdaforums.com/showthread.php?t=1962550

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].
[SuperSU] SERMs:
i have bootloop on my nexus 6p

after install supersu 2.79 SR3 on my Purenexus 7.1.2

i have searched for fix it but cant help. (install Factory image , format etc )

any suggestion ?

Thx for advice .
[SuperSU] Ch3vr0n:
Adb / fastboot boot to recovery and flash/sideload the ROM again. Then post the boot image so chainfire can take a look and post on your rom topic about the boot bottom bootloop.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Adarsh balu:
Please help me

I have flashed phh superuser and ex kernel on my moto g4 plus xt1643 device...

It is working fine and i have been using it for 3 months now...

I need to change to supersu...

Please give step by step instructions for this
[SuperSU] buffer overflow:
Reflash custom rom, then​ SuperSU and ElementalX.
[SuperSU] Adarsh balu:
Im using stock rom

Is it safe .. have anyone​ tried this ???
[SuperSU] Alxoom33:
Don't know. What phone and software are you using?
[SuperSU] Adarsh balu:
Moto g4 plus
[SuperSU] Adarsh balu:
Here

Stock rom with ex kernal flashed along with phh superuser

Nougat 7.0
[SuperSU] Alxoom33:
Works great for me on Moto Nexus 6.
[SuperSU] Adarsh balu:
Have u installed superuser first and then reflashed rom and then flashed supersu ??
[SuperSU] Alxoom33:
Your issue will be cleaning up phh su and any other related files you were using.
[SuperSU] Adarsh balu:
How to do that ??
[SuperSU] jcmm11:
Get unsu script from osmosis. (Search will find it)
[SuperSU] Adarsh balu:
I didn't get it
[SuperSU] gothicVI:
Maybe search longer then one minute?

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] buffer overflow:
https://xdaforums.com/showthread.php?t=2239421
[SuperSU] Adarsh balu:
Nop i dont know how to find it and use it. I need help on that

---------- Post added at 08:30 PM ---------- Previous post was at 08:22 PM ----------

I have downloaded the file do i need to take backup ??

---------- Post added at 08:35 PM ---------- Previous post was at 08:30 PM ----------

Is this working for stock rom??

I want yi unroot phh super user on my moto g4 plus xt1643

I have flashed ex kernel and phh superuser..

I want to change to suoersu...

Just flashing this would do the job right ???

Anything else to do pls tell me
[SuperSU] jcmm11:
I think you're also going to need the stock boot image. Flash the script, install stock boot image, flash SuperSU, flash custom kernel (if desired).
[SuperSU] Adarsh balu:
Which comes first kernel or SuperSU ??
[SuperSU] jcmm11:
Stock kernel, followed by SuperSU, followed by custom kernel

SuperSU will create backup copy of stock kernel for its use for future upgrades. If you upgrade SuperSU in future it will revert to stock kernel. Simply flash custom kernel again after upgrading SuperSU.
[SuperSU] Adarsh balu:
I have a stock system backup which i will flash then supersu and then ex kernel

Im repeating this cuz in the forum which i used to root by phh superuser they were strssing to flash ex kernel...is it necessary...the first time i did not use ex kernel that time i got stuck in boot loop
[SuperSU] Thisguy129:
Dude you have to use a bootimg. Look for supersu moto g5 and 2 days ago the thread got started
[SuperSU] Adarsh balu:
G5 ??? No i need for g4
[SuperSU] rajatgupta1998:
Flash this if there's no option in phh super user for unroot (never used it) :

https://xdaforums.com/attachment.php?attachmentid=3931994&d=1478779893

Reboot and then flash Supersu v2.79 sr3. You should have searched athene forums. Always make backup before doing anything .

Sent from Lord Tywin's athene
[SuperSU] Adarsh balu:
This is unSu right ??

I asked about this before but they said something about flashing rom and some img file

Elaborate pls if u know

Thanks
[SuperSU] Thisguy129:
I! Igor the Moto g4 regular Verison myself. I still do believe with nougat ROM you need to have unlocked bootloader flash elementalx kernel on stock then use superSu but I haven't gone to nougat myself yet i was wondering myself on how I'd root nougat and looked it up. With nougat you need a custom boot img on most devices boot img has your kernel and ramdisk.

OK I found the thread i can't post links. Guide root moto g4 plus with SuperSU on Android 7.0 Npj25.93-14.

Flash twrp 3.0.2.0

Backup partitions in twrp especially boot partition

Flash elementalx through twrp

Wipe cache and art cache through twrp

Flash SuperSU 2.79r3 through twrp
[SuperSU] emef:
Hello everyone,

Since I am under the 5.8.3 (Xenial 16), with Magisk 12.0, I can not use "Titanium Backup": it declares me non-root (it could not get root privileges, Been made with the "su" command). The ideal would be that "SuperSU 2.79" works, but at the launch of this one I am asked to update the binary SU: if I accept, whether by TWRP or other, reboot I find myself Bootloop situation.
[SuperSU] veez21:
Uninstall magisk then install supersu :good:

See if that works
[SuperSU] Adarsh balu:
The thing is u are saying about first time root i have already rooted with phh superuser...

I need to remove that first...

Tell me how on that..other i know but unrooting is my problem
[SuperSU] Thisguy129:
I believe you flash you flash the unsu zip than flash SuperSU but you may have to restore your backup of bootimg to stock before you were rooted. That's all I can say I've never done it I know there isn't much out there for this. I've looked to I can't find anything .

Actually the unroot zip is for unrooting supersu just flash your stock firmware without root that you should have made after TWRP got installed then flash elementalx kernel then supersu .If you didn't make a unrooted backup you might be out of luck on unrooting it from phhs

---------- Post added at 04:49 PM ---------- Previous post was at 04:41 PM ----------

Another thing is to flash a costume rom with the super su zip and Gapps then you'll have superSu root but not on stock it's just a thought I'm trying to help I'm also looking I can't find anything.
[SuperSU] Adarsh balu:
Im waiting for an answer to my question
[SuperSU] Thisguy129:
That's the answer you will be unrooted if you made a backup from twrp before flashing phhs. Did you make a backup before you rooted with phhs? If not then you'll have to do a costume ROM and whip your system, data, flash the ROM it will replace your bootimg than flash SuperSU and gapps. There is no unroot phhs like you want to keep you at stock was why you make a backup then flash phhs. So you can go back

Last you find you stock firmware download flash

That you'll be like new out of the box then re root using SuperSU zip. Sorry that's the best I can do.

This is my thoughts disable phhs in system app. Then reflash elementalx kernel then flash supersu but that's what I would try it could brick you I don't know if you have a backup it's worth a shot cause I'm just learning on rooting nougat the bootimg has to be costume to root you need a fresh boot img I think so dirty flash your elementalx kernel then flash supersu it's just a guess .

When you flash supersu it disabled phhs and takes over it should
[SuperSU] jcmm11:
If you read the description for unsu (which was even posted in this thread) it handles multiple forms of su installation, including phh. It started out as a SuperSU remover but later expanded. He's already been told how to do what he wants to do, and the tool to do it.
[SuperSU] Thisguy129:
Alright I was trying to help the unzip su works with phhs to then Ill keep that in mind. Thanks for the info. Good looking out

In all fairness flashing a clean stock backup then flashing elementalx then SuperSU would be a better. Just my opinion. I can tell he doesn't have a backup is why he needs a unroot zip
[SuperSU] USBhost:
The app most likely needs to be updated to android L
[SuperSU] Cheater912:
You'd need to reflash the stock system image. OTAs for Lollipop work with partition changes instead of individual file changes. Nothing in the system partition can be changed.
[SuperSU] Murshad007:
2.30 is working flawlessly..

Sent from my LG G Flex F340K on LTE network, Stock KitKat 4.4.2 Rooted

using XDA mobile app
[SuperSU] JulianJenner:
Yepp, 2.30 does works for me correctly on LGE-P760 Lollipop. Nice new (material) button... Thanks & Grat [MENTION=631273]Chainfire[/MENTION]!

Redmi Note 1W Enhanched / MIUI 37.0.0 Stable Multilanguage / Tapatalk Pro 4.6.2
[SuperSU] kamathshreerat:
works brilliantly

Im not entirely convinced its because of SuperSU, but whenever i flash SuperSU and reboot, my device keeps telling me that "google play services" isnt installed on my phone. Takes a couple of reboots to fix it. I've only faced this whenever i flash the SuperSU zip. Im running stock lollipop on my N4 with Franco kernel.
[SuperSU] Nicknoxx:
Do we still need SELinuxModeChanger to run some root apps, or is it depreciated?

N4 TWRP LRX21T Hells-Core
[SuperSU] goran_oh:
2.30 is working flawlessly
[SuperSU] garzacorporations:
With 2.30 update now i have 2 icons on app drawer. N5 stock lollipop
[SuperSU] aantdesign:
Double icons on Nexus5 lollipop

Go into SuperSU -> Settings -> Launcher Icon, then select the one you want. This is because the default icon has changed this release.
[SuperSU] Srandista:
See Chainfire's reply:
[SuperSU] Midomad:
In love with the new icon so materialish [emoji4]
[SuperSU] garzacorporations:
Thank you!! Fixed
[SuperSU] Frank Westlake:
2.3 OK through TWRP on:

- Note_ SGJ-I717 4.0.3

- Note3 SM-N900V 4.3 single user Permissive

- Note3 SM-N900T 4.3 single user Enforcing

Frank
[SuperSU] Bobtehblob:
Anyone able to get a build.prop editor to work? On latest beta, stock 5.0 with Franco Kernel.

Edit: I'm a fool and didn't have busybox installed... Latest beta is working perfectly!
[SuperSU] ee_981:
v2.30

1. I flash the zip and reboot

2. SuperSU seems to work properly

3. After a while I get this error (attached)

EDIT

Device: OnePlus One

ROM: CM12
[SuperSU] Mistertac:
Have you checked out the dedicated thread CF has for the binaries not installing correctly?

Maybe you'll see something in there that will help :

http://xdaforums.com/showthread.php?t=2907365
[SuperSU] nyijedi:
So in theory, if you fastboot TWRP instead of flashing it and then later use supersu's unroot option, you should be able to receive an OTA, right?
[SuperSU] SamuriHL:
Installed apk as an upgrade on my note 10.1 2014 (4.4.2), s4 gpe (4.4.4), and nx6 and all work perfectly.
[SuperSU] vacsed:
No, this used to be correct but no longer is with Android 5. To receive OTA updates after any change on the system partition, you need to reflash system.img before starting the OTA update process.
[SuperSU] Srandista:
Yeah, and for a change to a partition is also counting rooting and then fully unrooting your device. So you always need to flash factory image, there is no way around that.
[SuperSU] Adarsh balu:
Correct i have no backup before flashing phh
[SuperSU] Thisguy129:
This will be my last text so I don't piss everyone off. You do flash the unsu zip then you also flash a fresh unrooted kernel bootimg samething. The elementalx is good choice for stock so.

Flash unsu zip

Flash elementalx

Flash SuperSU down that order

Done
[SuperSU] jcmm11:
He needs a stock boot image. ElementalX, like most custom kernels, uses AnyKernel2. That means it will pick up any existing changes to the ramdisk and incorporate them into its new ramdisk.

That's why you need a stock kernel to get rid of ramdisk changes.

The correct order is:

Unsu

Stock boot image

SuperSU

Custom kernel.

If you do it that way then anytime you upgrade SuperSU just reflash the custom kernel (or flash a different custom kernel if you want). SuperSU will, the first time it's flashed, create a backup of the untouched kernel. When it's flashed subsequent times it will reinstall the untouched kernel and apply it's new patches to that.

If the currently installed kernel already has patches applied to the ramdisk, and SuperSU can't find a clean backup copy, it will abort.
[SuperSU] CyberpodS2:
I'm not sure what answer you are waiting for, but I'll give you my answer for what it's worth. In the time it took for you to go back and forth with asking over and over you could have backed up your data, wiped and clean flashed with whatever root you desired and then restored your data. If the previous users answer does not get you where you want to be I suggest you go the clean route...
[SuperSU] Thisguy129:
That's interesting I did not know that about the ramdisk and I've downloaded flashed elementalx I always have a stock backup myself first thing after TWRP. However I have never seen that in the elementalx kernel thread they should have said that Im sure it's true.when I flash kernel I always go back to stock first. There really isn't much on this thread about the insu zip or much on XDA about what he was looking for I to searched. So we know he doesn't have a backup of stock kernel so he's out of luck he'll have to flash the firmware.

I went back I see I left out the stock boot but I wrote it in thee boot img samething I did write that.
[SuperSU] CyberpodS2:
This might not be relevant to your case at all but one thing I do whenever I install a custom Rom is I extract the boot.img from it and have it available on my phone to flash with twrp. I use it in between different kernels instead of dirty flashing the rom. It has also saved me a few times when I flubbed up a flashing sequence or something just ended up looping... :)
[SuperSU] Alxoom33:
If you had phh Su go to root/data and look for the boot.img file which if I recall correctly, should be stored there.
[SuperSU] Thisguy129:
Im not the right person

---------- Post added at 02:39 AM ---------- Previous post was at 02:32 AM ----------

Actually I'm not the personnel trying to unroot I have moto g4 already rooted with supersu however you did answer a question I had myself about just flashing bootimg extracted from a custom ROM I didn't know you could do that.
[SuperSU] Alxoom33:
Aren't you that guy? Lol!
[SuperSU] emef:
I tried. I lose the root and superSU fails to restore it. Required to restore a backup by TWRP to recover the root.

And Titanium still does not work, and SuperSU offers me to update the binary and ... it's gone for a ride. :crying:
[SuperSU] veez21:
Flash the magisk uninstaller, then reflash your rom then flash supersu
[SuperSU] Adarsh balu:
Where can i find stock boot image ???
[SuperSU] ulxerker:
its the boot.img file from the system image package of your phone. so download the package (use Google to find it) and extract boot.img from it.
[SuperSU] Adarsh balu:
Just did that..thanks

So now i have made backups and im going to do it...

Correct me if im doing wrong

First unsu flashing

Instead of flashing boot.img can i do this

i have my stock rom zip so im flashing that...since it is marshmallow i will system update it to nougat

Doing this i will get fresh system

I it is required i can do it after stock rom installation

Then flash supersu

Then EX kernel

Done ..

---------- Post added at 08:13 AM ---------- Previous post was at 07:29 AM ----------

Just got in a boot loop after unsu flashing and boot.img

Got back after twrp backup restoring
[SuperSU] grendes:
I used you your script and then installed stock boot.img from ROMs zip, but my phone just stuck in boot loop. "samsung edge +"-text just pops up again and again. What did I do wrong?
[SuperSU] Adarsh balu:
I had a twrp recovery of my stock rom before rooting i used that came back ...so i lost phh suoeruser and ex kernel ehich i had installed later..

Then i flashed the SuperSU zip and ex kernel and boot from twrp restore...But no root is detected on my device
[SuperSU] Ingenium13:
SR3 causes bootloops after installing the May update on the Pixel XL. It bootloops as soon as the bootloader screen shows up. Sometimes it will display a message about writing memory contents to an ext4 file. Reverted to the May factory image.

Using TWRP twrp-3.0.2-0-RC1 boot image with SuperSU-v2.79-SR3.
[SuperSU] TonikJDK:
+1

Happening on the May image for both the Verizon image and the 'Everyone else' image.
[SuperSU] Alxoom33:
Try 2.79 SR4
[SuperSU] eduardozeassesme:
Or wait for solutions
[SuperSU] eduardozeassesme:
Or update your recovery
[SuperSU] carlylemiii:
What if you don't normally install TWRP?
[SuperSU] TonikJDK:
Installing TWRP after booting to it throws it into bootloop also. Which makes me think this may be a TWRP issue.....the installer was broken by May.
[SuperSU] Ingenium13:
Even to install a newer version of TWRP, you still need to fastboot boot the older version first. I normally do not install TWRP.

Reports say that installing the newest version of TWRP causes the same issue as well.

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

SR4 is for 6P or 5X only. Chainfire specifically says it will not work on the Pixel.
[SuperSU] Alxoom33:
I would try,☺️
[SuperSU] cbomb101:
Will cqb firmware of the galaxy s5 get root chain fire. Its the newest one.
[SuperSU] rajatgupta1998:
Restore that unmodified Backup in twrp> flash elementalX kernel>reboot>flash SuperSU>reboot and set up SuperSU if need be.
[SuperSU] Adarsh balu:
Yes i did it it works well...since it is beta version it does not look the same as the one i previously used...
[SuperSU] AJ:
definitely bootloop on pixel with MAY security patch
[SuperSU] peterlee928:
for those using twrp

to flash supersu

see below

and/or forum at very bottom

this worked for at least 1 other person

Boot into fastboot and flash the bootloader from the April security update. Then boot TWRP.

After this, TWRP worked again. Something must have changed in the bootloader in the May security update

https://xdaforums.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312/page162
[SuperSU] Ingenium13:
Bootloader, or boot partition? I keep seeing comments here and on reddit saying bootloader, but I read the bootloader was identical between the two releases. I think the boot partition would be more likely, as that would put you on April's kernel.
[SuperSU] Taomyn:
Nexus 6P with May patch (full image sideloaded without data) and SR4 working just fine so far :)
[SuperSU] Kisakuku:
Bootloader. April is 996-012001-1702151126, May is 8996-012001-1703151359.
[SuperSU] mtw4991:
Got the May security up and fully running, with FK-15, SuperSU and TWRP. You will need the April bootloader image, as stated above, from the zip.

This is what I did, hope it helps.

In bootloader: fastboot flash bootloader c:\bootloader-marlin-april.img

fastboot reboot-bootloader

fastboot boot twrp-3.0.2.img

In TWRP: install twrp-pixel-installer-marlin-3.1.0-0RC2.zip

reboot system

Back to bootloader: fastboot flash kernel c:\fk-15

fastboot reboot-bootloader

reboot TWRP recovery from bootloader

In TWRP: install SuperSU-v2.79-SR3

reboot system
[SuperSU] Alxoom33:
Curious if the bootloader and radio are identical between the April and May 7.1.1 release​s for the Nexus 6.

I used Flash fire to update, but it doesn't update the radio and bootloader effectively. When I tried it in the past I got an error message and bootlooped.
[SuperSU] zelendel:
The radio is the same but new bootloader
[SuperSU] mtw4991:
The bootloader is definitely different for the May security update on the Pixel XL, probably the same on the N6, idk. You can always use the flash-all.bat script in the update zip, but make sure you remove the -w and resave the script or you'll wipe your data. This way, you'll update the bootloader and radio at the same time. Follow my steps above if using twrp, SuperSu or custom kernels afterwards.
[SuperSU] Ch3vr0n:
Just updated my 6p to may updates with flashfire. Booted up just fine with the updated boot image that was rooted.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] spainter:
Same with my two N 6's. Except I used a tool called House of Nexus that uses the fastboot environment from the bootloader. Great tool for flashing and re-rooting when you need to do it without a booting phone. Or are lazy like me and don't want to flash with all the separate fastboot command lines.
[SuperSU] Chainfire:
Re: Pixel (XL)

It's been a rocky few weeks with the Pixel and Pixel XL.

First, regarding Android O Preview, I do have a proper fix for the bootloops, without any artificial boot delay.

Second, regarding the May security update, I have a properly booting rooted image now. However, it may take some work to get the fix ported to running on the device rather than on my computer. Also I will be away for a few days. In the meantime, flashing back the bootloader from the April firmware also works to circumvent the issue.
[SuperSU] chazall1:
Damn Great. Thank you for your outstanding work and dedicated effort.

WOW.

Thank You
[SuperSU] mobileman88:
It's also a new bootloader for the 6p in the may update
[SuperSU] mtw4991:
New bootloaders for all, hope you're reading ?
[SuperSU] TonikJDK:
The Pixels got an extra patch for an htc bootloader security issue. That would be a likely candidate for our problem