yashsingh1/xdaforums huggingface dataset:
[SuperSU] KahlanHaskeer:
It seems that I have the same problem to update binaries. I have an HTC Desire X running the latest version of SuperSU from the PlayStore.

If I chose the normal update, it returns a "Installation failed!" message. But if I chose to reboot into TWRP, it just put me on the main screen.

Some weeks ago, a DesireX dev told me to flash an upadate-supersu.zip and it worked fine but I don't find it on your original post.

I'm downloading Android SDK to do what you told to do to give you some info.
[SuperSU] volkmadi:
Hi,

I just did my 3 full wipe with DBT I9505XXUDMH5 (I9505).

I have still tons of fast closes, even with apps like whatsapp.

The selinux is disabled with "pm disable com.sec.knox.seandroid".

I need really help!

The phone is not usable in a state like that.

I used odin 3.07 and the last version of CF-Auto-Root-jflte-jfltexx-gti9505.

Any ideas? Has one these problems too?

Thx

Dirk
[SuperSU] asperon:
I have a Galaxy Nexus (takju) running 4.3 (JWR66Y) and i am having serious problems with SuperSU. It force closes frequently and it wont grant SU to anything. I have tried reinstalling, reflashing SU, rerooting (multiple ways), install it to /system, etc etc, nothing seems to help. Any ideas?
[SuperSU] Phhoenyxx:
To answer my own question, the binaries had not updated to 1.56.

When loading SuperSU for the first time, it did ask me if I wanted to update the binaries, and I chose Normal. I don't recall seeing an error message, but the binaries did not get updated.

I compared the filesizes of the binaries from 1.55 and 1.60:

1.55: 112,164 bytes

1.60: 112,280 bytes

I installed UPDATE-SuperSU-v1.60.zip via CWM Recovery. It then asked me to update the binaries and I again chose Normal. No error message. The binaries are now updated.

I don't know if they got updated by flashing via CWM Recovery or by updating from the app, but all is good again!
[SuperSU] ironia.:
I have updated from store, open supersu app but was not asked to me to update the binaries:confused:
[SuperSU] pan.droid:
Astonishingly naive. Just because you don't understand it doesn't make it superfluous or reprehensible.

Android is the most ubiquitous mobile OS in the world. We entrust it with our financial credentials, our whereabouts, our selfies, intimate knowledge of our relationships, etc. If you're certain the HUMAN BEINGS in our own government are infallible I'd urge you to take a look back at the Nixon years or at the systemic persecution of certain political groups by the IRS only a year ago.

Perhaps more likely relevant to law abiding people (in the near term) is fraud. You cannot put a price tag on an exploit that could compromise the financial accounts of Android users, in mass. That's to say that, without regular innovation in OS security tools it's inevitable. Not to mention the fact that Android has been named the most insecure popular OS by the FBI.

---------- Post added at 05:53 PM ---------- Previous post was at 05:46 PM ----------

Manually reboot to recovery, out should flash the new binary. If not, return to to app and it will prompt you again.
[SuperSU] KahlanHaskeer:
But where did you find UPDATE-SuperSU-v1.60.zip file ?
[SuperSU] Bill Gamble:
It's in the OP:

http://download.chainfire.eu/350/SuperSU/UPDATE-SuperSU-v1.60.zip
[SuperSU] Phhoenyxx:
There's a link to it in the first post of the first page of this thread. Third or fourth link I believe.
[SuperSU] polobunny:
Leave it to someone to bring this conversation to a debate about the government spying on people. SELinux won't solve a MITM attack. Serves nothing to debate about this right now.

As for fraud, I wholeheartedly agree with you protecting yourself is always a good idea. The problem isn't in SELinux per se, but rather the fact it is enforced upon everyone by the phone manufacturer. No power of decision. Yay.

As for FBI naming Android OS the most insecure popular OS, it's definitely something to take into account but with a grain of salt.

Their criteria for judging include:

-Device fragmentation

Inevitable considering the numbers of different devices running Android vs iOS/BB. They act as if they couldn't enforce a certain version of Android to be used and they had to allow up to v1.5 Cupcake.

-Apple Store being curated

As if the Android Play Store wasn't. Ridiculous myth.

-Different solutions being available for iPhone to make them meet government security requirements

iOS/iPhone have been out longer, it's kinda expected, but fair point.

-The number of malware attacks present on Android

Refer to fragmentation, rare/non-existent on ICS+.

-The most risible "Apple is setting grounds for future device security improvements with the lightning connector"

Yes, speculations of a probable improvement of security in the future.

Does it sound like a marketing ploy/deal to you? Sure does to me. Blackberry has the most robust system setup out of all the mobile phones OS available (was used for quite a while by government agency), but no one wants those anymore... ;)
[SuperSU] dirtyreturn:
So SELINUX is more secure?? I double clicked on it and it froze my phone on cm10.2.. It is labeled as permissive. Are thee other modes to this?

Edit - below post *haha*. That would have been an idea worth doing first I suppose. Android is still really over my head for the most part.
[SuperSU] Pons:
That's because CM10.2 is still in a nightly/bring up phase. Hardly considered stable, especially with a new feature. As for SELinux... http://bit.ly/T6x4C5
[SuperSU] DeanGibson:
"su" 1.52 binary seqfaulting on older devices

I do realize that your help is both free and non-obligatory, but I'm not willing to install either CWM or TWRP (even temporarily), for reasons that are beyond the scope of this discussion.

However, I've done some additional investigation. Using the version of "su" (112164 bytes) that successfully installs from SuperSU (v1.60) on my Android v4.x devices:

On the Nook Color (Android v2.2.1), running "su -v" reports "1.52:SUPERSU".

On the Moto Droid (Android v2.2.3), running "su -v" seg-faults.

The prior version of the "su" binary that works, reports "1.45:SUPERSU".

This all makes me wonder whether you are compiling "su" with code generation options beyond "arm-v7a". Or, perhaps there is an OS version dependency ...

I have run "adb bugreport" on both devices and can send those files if desired. Note that on the Nook, part of that report includes:

------ KERNEL LOG (dmesg) ------

<6>Initializing cgroup subsys cpu
<5>Linux version 2.6.32.9 (build@dhabuildimage16) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Fri Jun 15 13:17:18 PDT 2012
<4>CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
<4>CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
<4>Machine: OMAP3621 EVT1A board
<4>Ignoring unrecognised tag 0x54410008
<4>Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 131072
<7>free_area_init_node: node 0, pgdat c059a7e0, node_mem_map c0694000
<7> Normal zone: 1024 pages used for memmap
<7> Normal zone: 0 pages reserved
<7> Normal zone: 130048 pages, LIFO batch:31
<6>DIE ID: 761400029ED80000015EFEE00602801A
<6>OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk )

On the Droid, "cat /proc/cpuinfo" gives

Processor : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 499.30
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x1
CPU part : 0xc08
CPU revision : 3

Hardware : sholes
Revision : 0000
Serial : 0000000000000000

On the Nook, it gives

Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 297.12
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2

Hardware : OMAP3621 EVT1A board
Revision : 0005
Serial : 2004660018952003

If that helps ...
[SuperSU] MildewMan:
So I used SuperSU to do a full unroot on my Nexus 4 to install an update that wouldn't go through otherwise, and now I can't re-root it. I have tried flashing 1.51, 1.55, and 1.60, but the SU app does not appear in the drawer. Is there something else that I need to do first before flashing the zips?
[SuperSU] saintsatinstain:
I cannot find drivers for the Asus Nexus 7 and

as long as I have followed your suggestions and warnings I have not bricked my Nexus 4. I also bought your superuser; if the free was good I figure only better. I have seen directions for rooting your auto rooter by other folk. They suggest downloading sdk?

I just need the drivers for the Nexus 7 (2013) and the other necessary files for root. I do not play with custom roms and such, I just want to make the adjustments and tweaks I know how to make. I tried to find the drivers on the Asus site. Nope.
[SuperSU] The111:
Think this should work?

http://developer.android.com/sdk/win-usb.html

Also if you have the SDK installed you can download it through that interface and it will be somewhere in an easy to find subfolder of the SDK like drivers/google/ or something (not on my PC w/ SDK now).

I had some weird issues with my N7 and GS4 both where the USB driver would be installed and working fine for ADB connections made while Android was loaded on the device. BUT once I was in the bootloader and trying to use fastboot the device was no longer recognized by windows. In that case I had to go into the driver settings and change to a different type of bridge, maybe from composite to ADB or something, I forget exactly.
[SuperSU] DasKnuffel112:
Since the Update yesterday want my recovery to fix the root access. TWRP and PhilZ.

When i flash v1.45, its all ok, after update to 1.60, the Recovery want to fix the root.
[SuperSU] Chainfire:
TWRP guys are making fix for TWRP, and when PhilZ is updated to the latest CWM sources it should stop whining as well.
[SuperSU] DasKnuffel112:
Ok nice. Thank you Chainfire. Great work.
[SuperSU] Chainfire:
No worries, somehow I got from your original post that you were using CWM (re-reading I'm not sure how that happened). I think I've solved the issue - I'll PM you about a test-build as soon as I have one, you can install it whichever way you want - assuming here just the raw files is enough for you to test with ?
[SuperSU] shoey63:
I just removed the app from the zip and flashed it. Then downloaded superS from playstore. Worked a treat.
[SuperSU] DutchDanny:
Hi Chainfire,

I'm building a CWM from source of the new P5210 galaxy tab3 10.1

I have it working, but when trying to install 1.60 i get error staus 7

I have changed the update-binairy to get rid of previouw error.

but status 7 persist, and permissions are not set, so can't update binairy.

Any sugjestions what i can do?
[SuperSU] gamepois0n:
oh man, I accidentally upgraded to the new upgraded version of the 4.3 and found out I had 1.51 and it did not survive from the update .-.

on top I locked my bootloader aso I had to wipe everything to re-flash the recovery(just switched to TWRP, so much better than clockworkmod, thanks I guess .-.)

.-.
[SuperSU] jasonkhoo87:
I update to 1.60 break my supersu. Any apps now will failed to . Request supersu.

Where can I download ole flashable supersu version? If there possible to have 1.50 or 1.55.
[SuperSU] gamepois0n:
download.chainfire.eu/supersu
[SuperSU] jasonkhoo87:
I did try using the latest version but it break my root. I want try reflash old version.
[SuperSU] Bill Gamble:
Here's a link for 1.51:

https://app.box.com/s/isy14bvfep62mg67l7t4

Here's 1.55:

https://www.box.com/s/yebzcbaunkdo8jpaht6t
[SuperSU] jazzruby:
Hi jason,

You should try and find out why su has failed; SuperSU 1.60 has made some SELinux context aware changes but should only apply to Android 4.3 or have SELinux installed/enabled. Do you have 4.3? Have you disabled SELinux?

If you still can't resolve you can download 1.55:

http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip

-JR-
[SuperSU] jasonkhoo87:
Hi there,

I have jB 4.1.2. Im normal user basicall I did not change any system settings. how to know my rom SELInux enable or not?

M condition here, as new apps request su, it will succesful. But, if I remove the apps from supersu list, and re-run the apps. It will no more request su.

Thanks for the link, i will try to revert back to that version. Do I need to unroot from SuperSU menu before proceeding flash older version?
[SuperSU] swapgut:
Great app Chainfire, my choice since last spring with my OneX.

Noticed my HTC One lit up when it hadn't been touched in a while yesterday. I'm using a 4.3 ROM based on what LlabTooFeR got out about a week ago.

When I unlocked the screen there was a prompt from SuperSU 1.60 for phone 001 or 0001. I've used two 4.3 ROMs; MaximusHD 12.1.0 (LlabTooFeR) and CleanROM XE 1.1 (scrosler). The prompt had the access warning in it and timed out right then. Never seen this before.

Benign or malignant I have searched the www and threads here at xda finding nothing. Is this a 4.3 specific apk or something?
[SuperSU] sansnil:
I'm still having the boot loop issue with my gnex and 4.3 (w/security update). It doesn't seem to make a difference if I have the OTA root survival mood enabled or disabled, the device will get locked in a boot loop. Deleting the /data/system/locksettings.db and /data/system/locksettings.db-shm files using TWRP is the only way to get it to boot successfully when it happens.

Is anyone else seeing this still with the latest version?
[SuperSU] Morlok8k:
I'm following your discussion with DeanGibson, as I have the same issue with my Android 2.3.4 Droid 2 Global.
[SuperSU] Smultie:
I'm noticing very high CPU usage by system a couple of times the last few days.

Top shows daemonsu as the responsible process.

Has anybody been able to backtrack this issue and perhaps been able to find a solution?
[SuperSU] Chainfire:
I sent you a PM with a test-package that might fix this issue

Everything that happens as root will show as daemonsu being reponsible. Check your root apps ...
[SuperSU] Tungstwenty:
Idea: does it make sense to use set_process_name (as zygote/app_process does) so that it appears in the process list as daemonsu-<uid> or something similar?

(or some other mechanism for that matter, not sure how this works exactly: argv[0], ...)
[SuperSU] Chainfire:
I suggest you check ps.
[SuperSU] saintsatinstain:
I've unlocked the bootloader, but cannot root seems because of something called "secure boot." Ii it encryption. I bought my Nexus 7 from Best Buy not Google direct. My Nexus 4 didn't have this.
[SuperSU] khaytsus:
Nonsense... unlock bootloader using fastboot, Flash twrp, Flash supersu, done.
[SuperSU] Chainfire:
SuperSU v1.65 released - https://plus.google.com/113517319477420052449/posts/YjbSjKfHQ2Y
[SuperSU] Tungstwenty:
I guess you were already one step ahead, as expected :o

I hadn't looked at my device, but merely from the reporter's comment and your response not showing how to pinpoint the exact app...

I'm running 4.2.2 and don't have any daemonsu processes, so I guess even the new versions behave as they used to if below 4.3

Now checking on my device I can see that ps or ps -l indeed show the command line (top doesn't) which you lead me to believe holds enough info to understand which app is driving each daemonsu process.

I'm glad there isn't an issue at all, it's just that the same complain is bound to appear a couple of times till everyone is familiar (?) with the daemon / delegate process mechanism :)
[SuperSU] DeanGibson:
All is well in the burrows ...

Sorry, I've been offline the last four days.

I will test the ZIP you PM'ed me if you want me to, except that once I saw your above update get pushed to the Android Market, I updated all my Android devices (new and old), and all the subsequent updates of the su binary succeeded.

I'm curious, if my devices were truly ARMv7 (as I thought my prior post indicated), why did you need to "go back to ARMv5" ???
[SuperSU] Mardon:
Yeah finally support for my armv6 devices is back. Well done.
[SuperSU] androidfr33k:
Is it possible this version 1.65 zip version for twrp broke root? I did have to re-install after a rom update never had any problems before. It still does not seem to be working? I'll try v1.60 to see if it fixes the problem.

v 1.60 put me back into working order. Something wrong in v1.65 at least the zip version?

Edited:

I think its OK after a 2nd install. Jb 4.3.

Edited Again:

V1.65 has some bug. If I install any zip let's say a kernel as an example, on reboot twrp says fix supsu permissions, root permissions appear to be lost.
[SuperSU] swapgut:
Thanks for 1.65

RE: http://xdaforums.com/showpost.php?p=45437299&postcount=3696

Got the prompt again to allow phone that I have never-ever seen since getting an android phone. I ponied up yesterday Chainfire!

It's phone 1001 asking for root access, it reads:

chmod 666 /sys/subsystem_restart_properties/

subsystem_restart_reason_nonblock
[SuperSU] LOBBS:
I lost root access from today's update to v1.65 through the Play Store. I manually flashed back to v1.60 and all is well.

Edit for additional details: HTC Rezound, S-Off, modified CM 10.1.2/JB 4.2.2 ROM, TWRP 2.6.1.0. I can reproduce the lost root at will. As soon as I allow the app to update through the Play Store, I lose root. Uninstall/reinstall and/or clearing cache/data does not resolve the issue. No prompt in app to update binaries. Manually re-flashing to v1.60 immediately fixes root. SuperSU Pro user.
[SuperSU] Morlok8k:
Well, how do you like that! I get home, charge the phone, install it, confirm that it works, and then come here to let you know that it works, and youve released 1.65 that includes the fix...

Oh, and thank you very much!
[SuperSU] slebit:
It's working for me on my One X and Nexus 7.
[SuperSU] 78Staff:
zip file worked as always on ATT I747 S3 with Task's AOKP 4.3...
[SuperSU] Chainfire:
The Android 2.x and ARMv5 issues are related, as in, SuperSU has traditionally been compiled in the GB AOSP tree, and I moved it to an ICS AOSP tree at v1.45 because there were some features I needed which were not available in the GB tree. That change both lost ARMv5 compatibility and somehow broke something on 2.x (I've produced lots of binaries with ICS AOSP tree that work fine on GB, so I expected this to work).

Porting back those features I really need to the GB tree fixed both ARMv5 and the Android 2.x problem.

I'm moving out of the AOSP tree altogether soon, which should get rid of the issue altogether. Most of the reason I was building in the AOSP tree in the first place has disappeared the past year anyway, so ... :)

So if you press a button a button in TWRP that performs a destructive operation, this is somehow SuperSU's fault ? Update TWRP.

What if you flash the v1.65 ZIP through recovery ?

I had multiple people test (as usual) - somebody else just gave me the test results before you did :)
[SuperSU] LOBBS:
Yes, it does appear that I can maintain root through the flashable zip.
[SuperSU] :
hi there,

v1.60 and also 1.65 keeps ask me if i want to fix root (/system/xbin/su) ... is there a way to get rid of ? (deleting install-recovery.sh? ... what is this script?)

Thanks... latest update to 1.65 works great ;)
[SuperSU] shoey63:
That's a CWM, TWRP issue (as explained many times before) Nothing to do with SuperSU. Just ignore it and press NO.
[SuperSU] androidfr33k:
You would think the latest version of TWRP v2.6.2 would have had a fix for it?

[MENTION=631273]Chainfire[/MENTION],

Even if execute what I think is non destructive, the reboot button I get the same message which I discovered after my first post?
[SuperSU] :
I am making a rom, how do I intergrate it so it flashes with it? Its cm10.2
[SuperSU] sansnil:
[MENTION=631273]Chainfire[/MENTION], I've confirmed with a couple different Galaxy Nexus users that there is still a boot loop issue even with the latest 1.60 and now 1.65 SuperSU versions. Is there anything I can do which would be helpful to resolving it?
[SuperSU] Pons:
Easiest way would be to take apart the update zip, and put the files in the appropriate places in your ROM.
[SuperSU] :
yeah, but when i open the superuser zip, the files arent like in /system format, all i see is a common,arm, and x86 folder with just files inside
[SuperSU] Pons:
Then open the update binary/script, and do what it says. You probably only need the files pertaining to your device's arch.
[SuperSU] :
it just says and i quote:

#dummy

Nevermind, update binary

---------- Post added at 08:09 PM ---------- Previous post was at 08:05 PM ----------

update binary only shows for x86, not arm:(
[SuperSU] jazzruby:
It first sets 'ARCH' as arm and then runs an if statement to check for x86; if not x86 it proceeds with arm

arm and x86 folders contain the su binary for that architecture; copy the su binary to /system/xbin/su and /system/xbin/daemonsu

common folder contains, well... common files for both; copy Superuser.apk to /system/app/Superuser.apk

For Android 4.3 you need the following options:

install-recovery.sh /system/etc/install-recovery.sh

99SuperSUDaemon /system/etc/init.d/99SuperSUDaemon

you should also touch 2 files to /system/etc - '.has_su_daemon' and ' .installed_su_daemon' - this is helpful with other recoveries/superuser

-JR-
[SuperSU] :
I dont see daemonsu or '.has_su_daemon' and ' .installed_su_daemon'
[SuperSU] Chainfire:
Exact firmware, recovery, etc and complete steps to reproduce issue. Including what the problem is. Most helpful? Backup your GNex completely, move that backup off-device, do a full re-install of the latest GNex firmware, and document the steps to make the problem happen.
[SuperSU] LOBBS:
I lose root again as soon as I wipe cache/dalvic in TWRP recovery. Reflashing v1.65 does not regain root. I have to flash v1.60 to fix then v1.65. No prompts to update binaries for v1.65.
[SuperSU] edd080:
Hi to all i currently have the katkiss rom installed on my tf 101, i have been getting the root has been lost warning from my recovery after selecting to reboot the tablet. This happens on both cwm and twrp as i tried both recoveries which had the same behaviour. I also updated supersu 1.65 via cwm/twrp which flashed successfully. My current recovery is twrp 2.6, i read in previous threads that the problem lies in the recovery and not in supersu ;is this still the case please?