yashsingh1/xdaforums huggingface dataset:
[SuperSU] spideyngo:
SuperSU 2.82 fails to update from 2.79 on ZTE Axon 7 nougat 7.1.1 b19 US

SuperSU 2.82 fails to update supersu from v.2.79 on ZTE Axon 7 Nougat 7.1.1 b19 US. After app updates from Google Play Store it prompts to install update to supersu. ZTE Axon 7 spontaneously reboots and does not update. FYI, currently on TWRP 3.1.0.0.

EDIT: deleted quoted OP to appease the crowd. :)
[SuperSU] Ch3vr0n:
Was it really needed to quote the entire OP? I doubt it.

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[SuperSU] xda_johndoe:
Edit, delete, preview must not work :D

Quite common on all the threads with the rookies
[SuperSU] Wolfcity:
In order to keep this thread clean I´ll send you a PM with some screenshots regarding my problem and the comparement of the two roms.

I can find something in it that looks like another rooting tool. As it is signed as unrooted it would be strange though.

[MENTION=631273]Chainfire[/MENTION]: Is another rooting tool or binary the only reason for that "binary occupied" message?

The rom has over 6500 downloads and nobody seems to have that problem. Could something survive a complete clean flash and make problems with the update?

It´s so strange that this message only appears on the latest version of aosp extendend.
[SuperSU] ktmom:
I know you've been struggling with this for several days. I'm wondering what happens if you flash, in this order; your ROM, gapps, osm0sis' un-su.zip, then the superSu zip.

You might consider using ADB logcat to make a file of what's going on after first boot and maybe capture what's prompting the "binary is occupied" message.
[SuperSU] Wolfcity:
Thx, good idea. Will try that and report.
[SuperSU] hentis:
Failure patching sepolicy on SM-G925F

Samsung S6 Edge SM-G925F. Rooted a while back and custom rom. supersu asked for update, which failed, tried twrp install, which failed with

- Patching sepolicy

--- Failure, aborting
​

More digging seems to indicate nugat update was done at some point, hence no root. but cannot root using twrp, also redid twrp with odin and sudo fail there as well.

Grabbed logs from failed install and final lines are

- Patching sepolicy

sukernel v2.82 (ndk:armeabi) - Copyright (C) 2014-2017 - Chainfire & CCMT

Loading from [/sutmp/ramdisk] ...

Saving to [/sutmp/sepolicy] ...

"/su/bin/supolicy": error: only position independent executables (PIE) are supported.

Aborted

--- Failure, aborting​
[SuperSU] WaltA:
Crawling my way back to full root.

I got "caught" in the v2.80 problem, and not only lost root, but lost the ability to re-root again using the same method. I enjoy a challenge, and was able to halfass get root back.

By halfass, I mean some apps that require root don't even start up. Some apps will start, but eventually have a problem. And some apps seem to be working OK.

One of the apps that seems to be working OK, is ES File Explorer. :good:

When I open up the SuperSU app, v2.82 (which I believe is the only SU app I have installed), it tells me that my binary needs to be updated. However, if I try, it fails. :(

I am wondering, since ES File Explorer is working, is there any way I can manually install the SU binary? If so, where can I download just a copy of the current most SuperSU binary? And to which folder on my device, do I copy it? And, what should I set that folder's permissions to be (if they aren't correct currently)?
[SuperSU] Wildcat2083:
I installed version 2.82 from a xda forum to obtain root initally, the supersu app works but the google updated the pro version to the newer update apparently and it tells me a new binary is ready but upon attempting to update it simply said failed to update the binary

as far as initially the 2.82 works fine unless i update the supersu/pro from the play store from there it indicates the binary needs to be updated and just fails upon doing so, the original 2.82 binary actually works so long as play store don't update supersu

---------- Post added at 06:08 PM ---------- Previous post was at 06:04 PM ----------

it does, it uses an engineering kernel and systemless root the bootloader however is still locked

---Edit---

according to chainfire the 2.82 is part of a limited few su.img files made specifically for this phone and setup so my question is mute, the supersu app wont work if i update it
[SuperSU] Ibuprophen:
Just to be clear...

The following excerpt from a previous post from Chainfire did clarify what the purpose of the specific "SuperSU Pro" app is from the Play Store.

I just wasn't sure if you were aware of this detail when you had mentioned SuperSU Pro.

Also, have you taken a look at the following post from Chainfire regarding his "SuperSU v2.82 Test 1" that he had released as well as any status updates?

https://xdaforums.com/showpost.php?p=72429329&postcount=9810

Just a friendly FYI in case you may not have been aware of any of these... :)

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] Wolfcity:
Ok, I did another clean flash, flashed rom,gapps, unsu.zip and at last superSU 2.82.zip.

First thing I did was install catlog and let it run. Installed a couple of root apps and this time it lasts almost an hour until the "binary occupied" message appeared.

I attach the log ( it´s too big for XDA´s attachments, so I take something like pastebin ) and two screenshots, this time it happend when opening TiBu.

The part where it happend should be somwhere near the end as I stopped logging then.

I really would appreciate if you, [MENTION=631273]Chainfire[/MENTION] or someone else can take a look inside that log.

This whole thing drives me crazy....:p

Last part of Catlog: https://pastebin.com/VPHdFf81

Complete Catlog: https://drive.google.com/open?id=0B0WGdtNWubBJdFdzQl9vOFNPTHM
[SuperSU] rajkumar1221:
lineage os 14.1 nightly installed , my processor architecture is ARMV7L , help me which su arm zip i need to flash , { su (arm) , su (arm64) , su (x86) }
[SuperSU] fierogt42:
As of June 04 at 2:30 CST, the play store version is still bricking Xperia devices.
[SuperSU] ktmom:
As annoying as this is, I would do all that again but use 2.79 or 2.79 SR3. I am not incline to trust 2.8x when a problem shows up :-/
[SuperSU] Ibuprophen:
Chainfire had mentioned that specific error as follows....

It looks as though another Superuser app had previously installed an SU binary file and that SuperSU message is reflecting this, in another words, it can't install the SuperSU binary because another, Non-SuperSU binary, is already present by way of a different Superuser root method.

I hope i had explained it okay... :)

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] ktmom:
Read back at least four pages where this had been discussed. Unless you think a non-rooted ROM plus osm0sis' unsu.zip still means the poor guy's device is rooted. Based on 2 other posts I've seen, I'm betting it's a glitch in the 2.82 release. Going back to 2.79 fixed it for at least one of those two posts.
[SuperSU] Wolfcity:
I'm in your boat about version 2.82. What makes it not easier is that I did the whole process with SR3 2.79 and 2.79.... The only reason to start over with it was the new SuperSU and as my device survived all that trouble I thought ok, maybe the new SuperSU will do the job.

So now I'm at a point to stay on my nandroid and hope that future updates of my rom won't have this problem with SuperSU or learn a bit about magisk...:rolleyes:
[SuperSU] andriyana625:
SuperSU v2.82 failed to update from v2.79

I recently installed a ROM that have systemless supersu included (v2.79). But after I updated the app and proceed to update the binary, the process won't finish for 6+ minutes. Tried restarting and still failed to update. Any help? Can I update it by flasing supersu zip in TWRP?
[SuperSU] zohaib0001:
[MENTION=7678190]SuperSU Release[/MENTION]

In Sony Xperia XZ Init.d working fine with 2.79 SU, But its not working on 2.82 i test a lot of time by flashing 2.79 & 2.82 and results was same.

Init.d not working with 2.82 on Sony Xperia XZ

Running 7.1.1 Stock Sony Rom with Custom Kernel
[SuperSU] Sr. Zé Alguém:
Xperia

users should flash the version from

https://download.chainfire.eu/supersu

Not the one from Play Store

.
[SuperSU] sky0hjh:
JJ World,the developer of JJ Match Platform?
[SuperSU] Kockowan:
UPDATE-SuperSU-v2.82-20170528234214.zip works for me on Sony Xperia Z3compact with firmware D5803_23.4.A.1.264_1289-4696_R8C (Android 5.1.1, coming from SU v2.79), thanks for bugfixes :good: !

It has been installed by TWRP recovery, flashing the .zip, wiping cache/dalvik cache and finally rebooting.
[SuperSU] mielletseed:
I have a strange problem on three Samsung devices, all rooted in systemless mode. The devices are stuck on first boot screen (Samsung screen, not the boot animation) for a very long time - several minutes - before the devices continue to boot. I there any way to reduce that annoying boot lag?

best regards
[SuperSU] ktmom:
Assuming that means your devices are "optimizing apps" every reboot, a couple of people reported that in the beta thread. Exactly which version supersu (e.g. Play store, flashed 2.xx-xxxx from where) and what version android?
[SuperSU] mielletseed:
no, that's wrong. I really mean the first screen after power on. You could say pre boot. Opzimizing apps starts after the boot animation. But my issue is that the boot starts after a long delay. I had the issue with 2.79 SR3 and with 2.82. Installed zip in recovery. One device has Samsung's stock ROM, one is running CM13, one LOS14
[SuperSU] Tecalote:
Huawei Devices and SuperSU

[MENTION=631273]Chainfire[/MENTION]

I appreciate your work very much - an officially supported solution for Huawei Devices would be awesome and great :good:

[MENTION=3694505]Telperion[/MENTION] is right - Huawei has added Loop support back to firmwares up B38x - but anyway, flashing on P9 (EVA-L09 b383) was not succesful with original Version of SuperSU.

Vendor must be mountet for Huawei Devices for succesful installing SuperSU. This can be done within the update-binary or as Telperion suggests - if TWRP mounts the vendor partiton by default.

https://xdaforums.com/showpost.php?p=72557202&postcount=447

The modified SuperSU did this and added in update-binary in 2.82 Line 864/865:

mount -o ro /vendor

toolbox_mount /vendor ro

The modfied SuperSU changed also the Line 613 in 2.82:

from: for PARTITION in kern-a KERN-A android_boot ANDROID_BOOT kernel KERNEL boot BOOT lnx LNX; do

to: for PARTITION in boot_a BOOT_A kern-a KERN-A android_boot ANDROID_BOOT kernel KERNEL boot BOOT lnx LNX; do

because it must also looked for BOOT_A to find the boot.img

as mentioned by [MENTION=2247733]ante0[/MENTION] https://xdaforums.com/mate-9/development/root-supersu-2-79-t3573155

Previous Version from modified SuperSU 2.79 did also a "after rooting patching with phh superuser" - this worked until 2.81 - but not really with 2.82 - for some devices yes, for some not.

But this night I got the idea - why not using just the official SuperSU and just add those Lines and good - without anymore modification - and it works :)

Thanks to all which give me the inputs to got the idea - mentioned in my Thread: https://xdaforums.com/p9/development/root-supersu-2-81-emui-5-t3612258/

I think it is solved now. Its tested now on P9, tests in the next days will show, if it works even on the other Huawei Devices.

Of course, old modified SuperSU must be complete unrooted from Device before flashing the original SuperSU (just with the added Lines)

There's on suggestion more:

And for all Firmwares before b38x - without Loop Support like maybe Huawei P10 (b150? ) it would be good to add support to official SuperSU as Telperion suggests. - Thank you!
[SuperSU] wizark952:
Hi, i'm not sure if this is the intended behavior or not, but SuperSU is no longer prompting to disable KNOX as in version 2.79 SR4 (which if i'm not mistaken also disables the package SecurityLogAgent.apk).

I noticed this because of the following story:

I've always used CF AutoRoot after flashing the stock ROM (which installs SuperSU v2.79 SR4), then i would boot up the phone, open SuperSU then accept the message when prompted to disable KNOX, later on i would update through the play store.

But this time after flashing the stock ROM i Sideload-ed v2.82 through TWRP, and when i opened SuperSU for the first time it didn't prompt to disable KNOX (or disable the package SecurityLogAgent.apk),

later that day i got the infamous notification error message "SE for Android was turned off..." which i've never seen whenever i used the CF AutoRoot method.

Reproduced on Galaxy J7 Prime G610F

With the package SuperSU-v2.82-201705271822.zip
[SuperSU] Claudio4780:
I've downloaded it on my GT-I9192 via Play Store and got the "binary occupied" message. Then downloaded the flash file from Chainfire and everything is running now!
[SuperSU] jewanchi:
With supersu 2.82 update

Hiding the supersu

It pops up like a picture.

what reason :confused:
[SuperSU] :
1)SU Hide Is Experimental And Probably Will Not Work According To chainfire

2)You can refer following thread of SU hide with all procedures/download/user's reviews etc

https://xdaforums.com/apps/supersu/suhide-t3450396
[SuperSU] Chainfire:
In (the upcoming v2.82-) SR1, /vendor is mounted by the SuperSU installer by default. This is needed for ODP2 support on Pixel (XL) already, and will probably be required on many devices going forward, so we have this covered I guess.

This change as-is will break compatibility with slot-based devices like the Pixel (XL) and various upcoming devices. From TWRP, can you get me the output of the following ?

ls -laR /dev/block
getprop

Please keep me informed of user reports.

Skimming through my code, it seems like it should already remove that. Can I get a full /tmp/recovery.log of a SuperSU flash that fails to remove this, and the (stock/original) boot image from that device before patching?
[SuperSU] mrrocketdog:
edit
[SuperSU] ante0:
This happens if I remove boot_a BOOT_A...

Actual boot image is located at /dev/block/platform/ff3b0000.ufs/by-name/boot_a or /dev/block/sdd32.

When boot_a is removed it finds boot at /boot, else it finds it at /dev/block/sdd32

/dev/block ls: https://pastebin.com/uqRBU2d9

recovery.log without boot_a: https://pastebin.com/KGgFesJE

getprop log: https://pastebin.com/1sA8gEAj

No worries on "fileencryptioninline", it is actually removed. It was not removed in 2.79.

Edit: Why is it displaying "flags=display="boot";backup=1;flashimg"? That's TWRP flags...
[SuperSU] Tecalote:
I will answer tonight, cause I am on work (job) now
[SuperSU] Chainfire:
Thanks. Can you upload the stock boot image for me ?

That flashimg thing is because boot is read from /etc/recovery.fstab as a last-ditch-effort. Something is going wrong with the parsing though. This should have correctly picked up boot_a (obviously it didn't)
[SuperSU] ante0:
https://mega.nz/#!VhlkmQbJ!sgq55_e6cf78VwxmKvUHD7f23aJnnWUwdOehft2Lpdk

There you go. :)
[SuperSU] Chainfire:
From adb shell into TWRP, what is the output of:

cat /etc/recovery.fstab | grep -v "#" | grep -m 1 "^/boot" | tr -s " " | cut -f 3 -d " " | grep "/dev/block"

Something unexpected happens there. But I see your TWRP is very recent, so that's not it.
[SuperSU] ante0:
It displays the full line

/boot	emmc	/dev/block/platform/ff3b0000.ufs/by-name/boot_a	flags=display="boot";backup=1;flashimg

Hmm.
[SuperSU] Chainfire:
Tabs vs spaces?

cat /etc/recovery.fstab | grep -v "#" | grep -m 1 "^/boot" | sed 's/\t/ /g' | tr -s " " | cut -f 3 -d " " | grep "/dev/block"

How about ^^^ ?

-------------------------

I just sent you a link to a test version in PM. Can you check if that works ?
[SuperSU] ante0:
That one parses it correctly :D

/dev/block/platform/ff3b0000.ufs/by-name/boot_a

Edit: https://pastebin.com/75qaJqX0

- Flashing boot image
dd: writing '/dev/block/sdd32': No space left on device
8193+0 records in
8192+0 records out
33554432 bytes (32.0MB) copied, 0.031089 seconds, 1.0GB/s
cat: write error: Broken pipe
Updater process ended with ERROR: 1

:eek:
[SuperSU] Chainfire:
Sorry I left an 'exit 1' in there for testing. But that happens after flash, so if you reboot, just see if it works.
[SuperSU] ante0:
Works! :highfive:
[SuperSU] MrKaon:
Hi

My App and log page is not loading?
[SuperSU] Einwod:
Have you the correct version and binaries updated?
[SuperSU] MrKaon:
Yes flashed latest zip version from first post.

Nexus 6P latest stock image nothing else.
[SuperSU] Einwod:
Working fine here on nougat for me. Version 2.78? Right?
[SuperSU] MrKaon:
Yes 2.78 :confused:
[SuperSU] Einwod:
Can you get to the setting tab to see if it's properly installed? Or simply download and reflash the zip, it may have been corrupted.
[SuperSU] hpbrasil:
[MENTION=6910415]lt_ler[/MENTION] Not with root cloak, even using root cloak the game still does not work in Routed devices. :/

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

Not with root cloak, even using root cloak the game still does not work in Routed devices.
[SuperSU] MrKaon:
Yes second flash fixed it
[SuperSU] ianmacd:
What makes you say that?

Lots of people play with a rooted device. There are even a multitude of Xposed modules for use with the game.

---------- Post added at 12:38 PM ---------- Previous post was at 12:36 PM ----------

It works for me, even without root cloaking.
[SuperSU] corkiejp:
[MENTION=7187684]ianmacd[/MENTION] Latest update to game will prevent rooted user's from playing. Don't update.

See post's about it in 2.77 thread.
[SuperSU] RandomPooka:
It's using the Safetynet API in the latest update. To my knowledge, Magisk with modified Supersu works, as long as you don't use Xposed. To also use Xposed, you need a different "competing" root solution that I'm not going to name. Look it up if you like.
[SuperSU] ktmom:
Couldn't all this Pokemon stuff go to its own thread?
[SuperSU] Midomad:
Could you stop acting like a mod?
[SuperSU] ianmacd:
Thanks. I stopped playing when I filled the Pokedex, so Niantic are too late to stop me, but for anyone affected, yes, remaining on 0.35 is the way forward for the time being; at least until it stops working.
[SuperSU] tuiyaan:
hi [MENTION=631273]Chainfire[/MENTION] and all

my device is honor 4x che1-l04

i have been trying to root emui 4 marshmallow for quite few months and been unsuccessful

any guidance would be really helpful

i had flashed this file https://www.androidfilehost.com/?fid=24591000424939898

and get this error

patching sepolicy

--failure aborting
[SuperSU] :
One post removed.

Please don't promote alternative software to the OP software in anyone's threads. Its disrespectful. Members can research and choose for themselves. :good:

Cheers,

Darth

Senior Moderator

Edit: And yes, this is not a Pokeman thread.
[SuperSU] santod040:
[MENTION=7678190]SuperSU Release[/MENTION]

Any progress or thoughts on this...?

Would love to see it updated and working for all my HTC devices and my m9 is the only one it doesn't work on after v2.65.

That includes the HTC Droid DNA, HTC One M7, HTC One Max, HTC One M8, and the HTC 10.

I've come up with my own work-around/custom installer zip for v2.78 that works on it, but manually modifying each update(for inclusion in custom rom builds) is not an ideal solution.

Thanks for your time.
[SuperSU] ktmom:
Did you see this post in the Huawei honor 4x Marshmallow rooting thread?
[SuperSU] Federacion:
Unfortunately this cannot be done.
[SuperSU] Bormental:
Hello guys. I'm trying to SU my arm64 phone with stock android 6.0.1. There is no known method to root this model.

After installing any version of SuperSU via custom recovery I get bootloop (logcat tells me that AudioFlinger cannot start).

When I rename /system/bin/app_process64_original to app_process64 the phone boots normally. But SuperSU says I have no root.

"su" command via ADB shell does nothing.

I'll be glad of any thoughts about my issue.

p.s. sorry for my poor English

p.p.s. phone is ZTE Axon mini
[SuperSU] Telperion:
I attached the output to the post. The Honor 8 and the P9 are virtually the same device, just with different Leica camera branding. They're similar enough that the P9 kernel can be flashed to the Honor 8, so my logs should be pretty similar to [MENTION=6870018]Tecalote[/MENTION] if not the same.

Also regarding your question about Pokemon GO, devices which don't pass SafetyNet are not even allowed to play the game -- they get a "device not compatible" error when the app is launched. Their goal was to prevent botting and location spoofing, but the side effect is that numerous legitimate root users can't even play the game at all. Currently, Magisk is the only solution available to users who want to have both active, working root and the ability to play Pokemon GO (or using a device with older software and SuperSU + suhide). App (and especially game) developers are increasingly using SafetyNet as an anti-cheat tool as opposed to a compromised device tool -- Google likely never meant for SafetyNet to be used as an anti-cheat mechanism, but that's what it's turned into.
[SuperSU] Chainfire:
Sent you a test version.

As for SafetyNet and Magisk, I am well aware. There's a reason I haven't (publicly) updated my versions for a while. Possibly I will say more on this soon.
[SuperSU] Tecalote:
[MENTION=631273]Chainfire[/MENTION] Sorry for late answer, I had a long working day. I made two tests. First test I only mounted vendor (no modification boot_a) - SuperSU Installing was succesful on P9. Second test I added the Line boot_a - SuperSU Installing was even succesful on P9. All logs atached. Unroot was possible from SuperSU App. Between test 1 and 2 I restored data, system, vendor, boot. My testing device is P9 EVA-L09C432B386.

However, it works on this device, if vendor is mounted - which will be in SR1 default. Thats fine for my device and for some others :) But I dont know if this only would help for other Huawei Devices. Cause one User has Honor 8 FRD-L09C432B380 and cannot root with vendor mounted and boot_a in the Line (you know) added.

And Huawei P10, P10+ dont have Firmware with b38x

Here is my original (unmodified) boot.img: https://mega.nz/#!jVIH0TLS!DNtbxaGPr207qoHuYbFmA03-O6GkDz2oVKegK0b8Esg
[SuperSU] jfeng:
please give me some seggsiton,my phone is nexus 6p, unlocked ,with 7.1.2 official，twrp3.1.1 flash SuperSU2.82 zip，reboot，i can see SuperSU icon in system，but root semmes unsuccessful，RE explore not working，can't see any system files，is what i did wrong？
[SuperSU] Phazmos:
Use root explorer
[SuperSU] Didgeridoohan:
I believe that's been discussed in the beta thread. Here is a good place to start if you want to read about it.
[SuperSU] spainter:
Try this post as a starting point. It continues for a few posts after.

https://xdaforums.com/showpost.php?p=72570832&postcount=10295
[SuperSU] Didgeridoohan:
[OT]

I see my ninja skills are on par today...:laugh:

[/OT]
[SuperSU] spainter:
LOL Yes they are:)
[SuperSU] Rebel2k:
Happy that worked for you! ?
[SuperSU] huangsijun17:
whose there any tools to install SuperSU by adb shell?
[SuperSU] shadow2797:
Could someone please give some steps on what to do if you have a bootloop? HTC One M7 user here. Can I just install any SuperSU version over another one with TWRP? That doesn't seem right to me, but no one is giving steps on how to actually downgrade or upgrade if you don't have access to the app because your device won't boot. I'm trying to maintain my data if I can. Also, Android version is 5.0.2, which according to the SuperSU forums, shouldn't update past 2.78, correct?
[SuperSU] mielletseed:
[MENTION=631273]Chainfire[/MENTION]: I suspect SuperSU for a delayed start of boot (https://xdaforums.com/showpost.php?p=72560108&postcount=1765), do you have any suggestion how to get information what's happening in the long time before the boot process starts?

Thanx in advance