yashsingh1/xdaforums huggingface dataset:
[SuperSU] osm0sis:
Okay something weird is going on with my end then. I'll see if I can weed it out. What device are you on? I'm on my GN.

---------- Post added at 01:49 PM ---------- Previous post was at 01:21 PM ----------

Hmm yeah, no difference whether I'm using the install-recovery.sh method or the native service method to run daemonsu.. Happens on stock kernel too.

Here's what it looks like to me. I press up to go through the last commands, but they all print out on their own lines (ls and cat), and the cursor remains on it's own new line below and I'm unable to put it back up to where the command is. Pressing left doesn't appear to do anything at first, but then pressing right afterwards displays the part of the command that I've apparently scrolled through so far by pressing left. Really bizarre. :confused:

Edit: Figured it out, sort of. It only happens in portrait mode. Even after clearing data on both apps. Still didn't happen with the old su and doesn't happen outside of the post-su prompt, but I suppose I can send an email off to the Hacker's Keyboard dev to see if it's an interaction thing he can fix on his side. :good:
[SuperSU] 78Staff:
I'm on ATT S3, running latest Task AOKP 4.2.2, using Terminal Emulator app and Hackers Keyboard. Pressing up arrow scrolls through the previous commands on the existing line, hitting enter submits the command, and able to use arrow keys to step back on the command and edit, pretty much like you would expect on any terminal. Must be something different related to the devices then, I guess?
[SuperSU] themachinist:
Since 1.45, supersu takes a few seconds longer to pop up the superuser request when I open a new/updated root app
[SuperSU] plee3:
The same thing happens on my GNex running SU 1.4.5 on Cataclysm 4.3.

Please post any response you get from the Hacker's dev.

Thanks... plee3
[SuperSU] osm0sis:
Portrait was definitely the key. Does it still work fine for you in portrait? I've sent an email, and I'll keep everyone posted since there's less output room on the screen in landscape so not being able to use portrait can kind of messing up one's work-flow. Does for me at least. ;)
[SuperSU] 78Staff:
You know, I started to post something about that, since I use the 5-row in landscape mode only most of the time, but switched portrait mode to 5-row after I saw your screenshot. However, I still am able to use the arrows in portrait mode as well. So, there must be some compatibility/difference going on due to the different screen sizes/resolution of the devices I suspect...
[SuperSU] osm0sis:
Yeah resolutions are the first things that jump to mind. That or somehow there's a LF or something getting inserted in the new daemonsu implementation that wasn't in the old su one, and it gets handled better on higher res/sized displays/devices.
[SuperSU] TeamDraven:
Hey guys.

Quick question.

I keep losing root.

I flashed supersu using the amaze tool kit and all wad well.

But it seems that after I have had the phone on for a while, I lose root access.

If I reboot the phone root access returns, but will eventually be lost again.

Any thoughts or ideas?

Cheers.

Greg.
[SuperSU] :
Try reflashimg supersu from recovery using the zip file
[SuperSU] Almighty2:
False alarm, for whatever reason, it all of a sudden just worked....
[SuperSU] :
v1.50 working OK on C5303 Xperia SP (Stock odexed)

(Installed by CWM based recovery)
[SuperSU] Cryss:
What about armv6 ?
[SuperSU] jbbandos:
From Chainfire's Google+ post announcing 1.50:
[SuperSU] Chainfire:
v1.50 release notes are here: https://plus.google.com/+Chainfire/posts/GjbpgDdF6Fq
[SuperSU] illithid:
I can't seem to update the binary on the v1.50 coming from the Play Store, stuck at the installing popup window.

Flashing the zip file provided worked fine though.
[SuperSU] omron2010:
After flashing stock Galaxy Nexus 4.3 first reboot before flashing SuperSu?

I've used this guide How To: Flash Your Galaxy Nexus Takju Or Yakju To Android 4.3 (JWR66V) And Root It Right Now to update my Galaxy Nexus to 4.3

I now want to flash SuperSu 1.50 using TWRP. Is is necessary to first boot into Android one time before flashing the SuperSU zip? Or can I flash the SuperSU straight after the last step in the guide and after the flash do a first boot?
[SuperSU] Pons:
Odd. Update from Play Store worked for me.
[SuperSU] cpanos:
No need to reboot. Typically, you go wipe, flash ROM, gapps (if not included in the ROM), custom kernel (if you want to flash one), superSU.

P.S. You need a custom recovery to flash superSU.
[SuperSU] illithid:
I updated both my Nexus 4 and Galaxy Nexus, both taking a long time to update the binary (>1 minute).

The window stated to wait 5 minutes before rebooting and trying again, but usually it took no more than a second to update.

So I just download the zip file and flash i through CWM.
[SuperSU] robgee789:
hey guys do you think there will be an update soon that will protect root when updating to 4.3?

edit sorry didnt mean to quote you mate lol
[SuperSU] CoolApps:
Any chance of a flashable zip for the recovery?
[SuperSU] Pons:
Yes, link in the OP, as always.
[SuperSU] Sloth:
http://download.chainfire.eu/344/SuperSU/UPDATE-SuperSU-v1.50.zip
[SuperSU] boonz19:
I updated from 1.45 to 1.50 through the playstore, then updated the binaries through twrp when I opened the supersu app. After that i tried to remove a system app through titanium backup but was still unable to do it. Anyone else having the same problem? Or perhaps it makes a difference to flash the zip instead of updating through playstore?
[SuperSU] guigus76:
Yes i have the same pb

My devicee says you are not root

Envoyé depuis mon GT-P5100 en utilisant Tapatalk 4 Beta
[SuperSU] Thanofski:
4.3 stock galaxy nexus....the update popup takes more than 5 minutes to update the binaries....any certain way to do it? Only tried normal way updated from play store....got twrp .
[SuperSU] lodder:
4.3 nexus 4

I have updated the app through play store but I hangs for more then 5 minutes rebooted already 2 times same result! Only did the normal since I don't have a custom recovery.

How can I fix it?
[SuperSU] Chainfire:
Flash the ZIP (first post) or flash CF-Auto-Root ( http://autoroot.chainfire.eu/ )
[SuperSU] lodder:
I have flashed the CF-Auto-Root and it works now thanks
[SuperSU] looppingz:
I started with a nexus 4 rooted 4.3 stock rom +SuperSU 1.45

I tried to install; through the app and tick the option through twrp it failed and killed the recovery.

Then I tried through the app normal install. I rebooted after 5min.

Then I reinstalled TWRP2.6, put the Zip on the phone and install through twrp. Fine.

No big deal but that auto install just failed and was just a loss of time. There might be something to correct here.
[SuperSU] DJxSpeedy:
to 1.50 Update : i had to flash the zip.. the app hangs when i clicked "normal" installation (dosnt do anything)
[SuperSU] 3DSammy:
Correction: SManager boot scripts do work with SuperSU v1.50 and Android 4.2.2

Was using SuperSU v1.45 with Android 4.2.2 and a Nexus 10 all was well.

Just received the v1.50 update and it broke full!screen.

full!screen no longer recognizes that SuperSu Pro has granted it root priviledges.

I tried re-flashing the SuperSU v1.45 zip but the playstore reinstalls v1.50 with every reboot.

As a side note under Android 4.3 and SuperSu v1.45, SManager fails to start a console at all. I suspect that it cannot find/execute the "su" command. This basically makes SManager useless. Yesterday I tried Android 4.3 but reverted back to 4.2.2 due to MX Player not working among a handful of other apps broken by the 4.3 upgrade unrelated to SuperSU.

Is there anything I can provide (e.g. logcat) to help resolve the issue related to SuperSU v1.50 and Android 4.2.2? If the answer is yes how would you like me to send it to you?
[SuperSU] b177y:
For my Galaxy Nexus and Nexus 7 the binary update for 1.50 took longer than 5 minutes. Tried again after reboots on both as instructed, still nothing. Flashed the .zip through fastboot and twrp, both devices work perfectly now. All of the issues from after 4.3 update seem solved.

Thanks! You're the best!
[SuperSU] nickcct:
Same happen to me. I think have to flash the file using custom recovery.
[SuperSU] shoey63:
One should always flash in recovery (fastbooted or otherwise), immediately after flashing a new ROM, and before booting into system.
[SuperSU] :
Thanks for your 4.3 root. Upgraded to pro. Enjoy a beer on me on your holiday :)

Sent from my Nexus 7
[SuperSU] boonz19:
Guys, titanium backup is trying to resolve the issue with the app. U can find it's test build via the link in this tweet: https://twitter.com/TitaniumBackup/status/361582620468985856 So far it seems like the issue with uninstalling system apps has been fixed, though I'm not sure if there is still any problem with restoring data. Hence, issues with titanium backup in 4.3 is most likely unrelated to chainfire's supersu :thumbup:
[SuperSU] Magissia:
A little question, is superSu ruuning in daemon mode for all or only for 4.3 users ?

Regards
[SuperSU] Mardon:
[MENTION=631273]Chainfire[/MENTION]

What happened to playstore?

Only SuperSU pro version is available but cant find the free version?

SuperSu 1.45 installed and see here theres an update but nothing in playstore?! :confused:

---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------

# Launches SuperSU in daemon mode only on Android 4.3+.

# Nothing will happen on 4.2.x or older.

# If you want to force loading the daemon, use "--daemon" instead
[SuperSU] VivaErBetis:
As other said, cannot update 1.50 from Play because it doesn't advance from updating binaries step. But updating from .zip worked like a charm!
[SuperSU] Chainfire:
[MENTION=4056970]3DSammy[/MENTION] You and any other running < 4.3, try flashing this ZIP and see if it solves the problem: https://dl.dropboxusercontent.com/u/25695577/UPDATE-SuperSU-v1.51-test.zip

Please report back ASAP as this needs an updated release ASAP
[SuperSU] menaceinc:
flashed it manually was fine here. Google Play Store got stuck in updating binary after several re-boots.

Thanks
[SuperSU] Chainfire:
From your signature it seems like you're running an ARMv6 devices... ARMv5 (which is what ARMv6 runs on, strangely enough) support has been dropped.
[SuperSU] Mardon:
Yes armv6 with fpu device, i only can see pro version now in play store, so only pro version supports armv6?

Besides that much users still runs armv6 devices, so plz keep armv6 support
[SuperSU] Chainfire:
Pro version does not support ARMv6 either. There is no more ARMv5 (or 6) support. Last SuperSU version for ARMv5 is 1.45.
[SuperSU] Mardon:
Thats really a bad news:(
[SuperSU] Chainfire:
Why? You aren't likely to see any new features in SuperSU that would benefit your device. Just use v1.45. 4.3 isn't supposed to run on ARMv5 (or v6) either, and all new stuff is going to be 4.3 related.

The only practical difference for you would be the version number. That being said, v1.45 should still be visible in the Play store for you.
[SuperSU] POWerSUrgeSW3:
I have been going through the updates from the playstorr lately. When there are new binaries to be updated, I let SuperSU reboot and install them through recovery (CWM Touch). This time I was asked if I would like to "fix" the flash to disable a recovery being flashed. Because it may restore the stock recovery. I paniced and disabled it so I had no chance of being unroofed. But wondering what that was all about?

~Max

Sent Via My WSv4.2 MD4 D2SPR
[SuperSU] Pkt_Lnt:
It is a CWM recovery feature.
[SuperSU] Mardon:
Bad news because,

4.3 btw cyanogenmod 10.2 is WIP for my armv6 device and 13 other armv6 devices. Also 4.2.2 cm10.1 wasnt meant to be run on armv6 devices.
[SuperSU] Aerowinder:
CM comes with Koush's superuser. What's the problem?
[SuperSU] Mardon:
SuperSU is better ;)

And i made modded cm10.2 for Galaxy Ace

most users also prefer the SuperSU variants.

I can see this in the OTA Stats
[SuperSU] Chainfire:
If you have a buildable CM 10.2 tree for your device, let me know and I can see what I can do.
[SuperSU] Mardon:
The builds are made by team androidarmv6

Github: https://github.com/androidarmv6 Buildbot: http://jenkins.androidarmv6.org/

Code reviewsystem: http://review.androidarmv6.org/#/q/status:open,n,z

For pico its already build successfully a cm 10.2: http://jenkins.androidarmv6.org/job/submission-test/217/

Hope you now have all the needed infos ;)
[SuperSU] Chainfire:
Yes, but I won't have time to add this back until after I return from holiday.
[SuperSU] drawde40599:
Same here, downloaded 1.51 installed threw recovery no issue , it would not install threw playstore version . stock Google IMG of 4.3 nexus 4

Chainfire u can ignore my email , just use it as info .... Thank u
[SuperSU] Mardon:
No problem its not stable enough to release it public yet.

But thanks, and have nice holidays ;)
[SuperSU] 3DSammy:
Under Android 4.2.2 running SuperSU v1.51 (test) corrected the issue with full!screen and also removed the SManager tzdata messages.

Thanks for the quick reponse. I very much appreciated a responsive developer.

I did not try it yet under Android 4.3 with the issue I mentioned with SManager. Will likely try later today. Update: Tried v1.51 with Android 4.3 but SManager rooted console still aborts (err: -9999). So no change since my Android 4.3, SuperSU v1.45 and SManager testing from yesterday.
[SuperSU] revmra:
On my 2012 Nexus 7, the 1.50 binary would not update via the app. Flashing it via CWM worked just fine.

Then I reboot and find that there is an update to 1.51. Now I can update via the app like normal. Thanks for the hard work, Chainfire!
[SuperSU] il Duce:
[MENTION=631273]Chainfire[/MENTION]

Htc one sprint m7wls, su 1.5 throws an error about tzdata
[SuperSU] bsoplinger:
Chainfire, thanks for this. Fixed SM issue for me also. But can I make a request? When you post Dropbox links can you post then "1 level up" where there is the question of either downloading or copying to my Dropbox? That way I'm not using up your download allowance and I can get it for all my Android devices "locally" via the Dropbox app? Its not too much additional bother for users without their own Dropbox accounts. I hope my request makes sense as I'm lost for the correct nomenclature to use.

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[SuperSU] POWerSUrgeSW3:
So I take it that means I should let it install and not disable the flash feature next time? Just don't want to screw myself and have to reroot my phone if I can avoid it. Thanks!

~Max

Sent Via My WSv4.2 MD4 D2SPR
[SuperSU] Pkt_Lnt:
In CWM, answer NO.
[SuperSU] samersh72:
great work CF, after re-rooting my Nexus with V1.51, "root file manager" issue is fixed :good:
[SuperSU] homemadehitshow:
What's the best way to stay up to date on new releases ? Is there any kind of auto-update ?
[SuperSU] CoolApps:
A new version of the binary already?, just got it.

Any ideas if there will be more before the 1st of August?
[SuperSU] polobunny:
Sure, provided by Google Play.

One of the last ones for sure, Chainfire is going on vacation.
[SuperSU] CoolApps:
Awesome, good reviews on this version.

Once I get back from holiday I will be reflashing my Nexus 4 whole with 4.3 and root sweetness fixing some of the issues.

Root is currently broken on my side and I don't have a custom recovery installed so I hope what I am doing will fix this issue.
[SuperSU] homemadehitshow:
polobunny, play store has no shown up for me as an updated app, at least not within a few hours. I've always downloaded and manually applied.
[SuperSU] polobunny:
I believe most issues are fixed in 1.50 for 4.3. Don't quote me, I'm on 4.2 on a Galaxy S3.

It depends on your phone. Certain phones won't get updated after v1.45 because their architecture is older and the new updates are for Android 4.3. What is your phone?
[SuperSU] CoolApps:
So 1.51 is not so good has 1.50?
[SuperSU] polobunny:
Sorry I mean v1.51, it's a typo. You should wait for the official release though instead of test version only.
[SuperSU] CoolApps:
So the flashable zip which was provided in the OP is just a test version?, when will the non-test version will be available?
[SuperSU] fireb33:
it's on the Play Store too, so yes, it's official
[SuperSU] CoolApps:
So that flashable zip I got is official?, awesome. :)
[SuperSU] polobunny:
Ah I missed the official update, ignore my previous post. I thought it was still in testing, guess not!
[SuperSU] Pkt_Lnt:
1.51 is what you get from http://download.chainfire.eu/supersu that is linked in the first post.
[SuperSU] Oletros:
I have installed 1,51 on a Nexus 4 with Android 4.3 and I have problems deleting some folders on Android/data

Is this one of the known issues with root and Android 4.3
[SuperSU] Yenkazu:
Bug

SuperSU 1.51 (from Google Play)

Failed to convert as system app, after reboot Superuser.apk gone forever
[SuperSU] CoolApps:
Damn, already there is issues. :s
[SuperSU] fireb33:
works fine here, reinstall it from PlayStore and retry

your problem != bug

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

read Chainfire post on G+

come on guys, learn to read :rolleyes:
[SuperSU] Bill Gamble:
beat me to it!
[SuperSU] Oletros:
Thanks, thanks, thanks :)
[SuperSU] Yenkazu:
Yup, works fine until I update to 1.51

So this is doesn't count as a bug ?

XD

I manage it by install SuperSU 1.45 from sdcard, update from Google Play and try reinstall as system app

And it asking just to installing to system, without need clean up

Seems like 1.51 already in there and ready for installing to system
[SuperSU] CoolApps:
Can you say out the command without the quote?
[SuperSU] samersh72:
i was on 1.45, what i did is "full unroot" with supersu app settings, reboot, flash 1.51 with cwm. everything is working great :good:
[SuperSU] fireb33:
there are thousand variables during a compless process like moving Superuser.apk from /data/app to /system/app without losing root, everything could go wrong

anyway you could have flashed 1.51 directly

---------- Post added at 10:25 PM ---------- Previous post was at 10:24 PM ----------

busybox chown -R 1023.1023 /data/media/*
[SuperSU] Yenkazu:
Yeah, I know -_-

But from 1.45 to 1.50 convert as system app works at it should

Just for 1.51 I have some little bug, just post here =)

And I'm not losing root access when my Superuser.apk gone

I will flash SuperSU.zip if my system fail to gain root access

XD
[SuperSU] simonsalo:
about to root 4.3 on i9505

So to root a new installation of 4.3 we just flash the 1.51 zip, is that correct? Not the 1.43 zip provided with the leaked rom before all the links were taken down.
[SuperSU] Craniotomy:
When I access supersu I get the update binary thing, so I update it then when I go to it again it will ask to update binary again. Any help? It's happening to my my touchpad, cm10

POWERED by the MASTER!
[SuperSU] osm0sis:
Flash 1.51 with the zip linked in the OP. Hopefully that's compatible with the touchpad?
[SuperSU] Craniotomy:
Its already at 1.51. It still keeps doing it su binary needs to be updated. Touchpad has the arm v7. Don't know else to do.

POWERED by the MASTER!
[SuperSU] ThurstonX:
Just got the Google Play store update notification for 1.51. Did the update, then went into SuperSU. It said the binary needs to be updated. I tried the "Normal" method, which I normally do, but it hung. Rebooted, tried again. Hung. Rebooted, chose the TWRP method, worked fine. Just wanted to report my experience.

Nexus 7

Android 4.3

Flashed 1.45 zip after upgrading

can't recall if I got the update notice for 1.5 after upgrading Android to 4.3, but if I did, the Normal method worked.
[SuperSU] osm0sis:
I reported this to Chainfire with v1.45, back here. You'll notice it still works, but you have to do it a second time after /system/app/Superuser.apk gets removed. He said he'd look into it when he has less pressing things to work on (like the sdcard and mount issues, which are now almost all fixed/worked-around; I've noticed FX Explorer still has remount issues, but AntTek works again, so that's a pretty good sign). :good:

I've actually had a flashable zip solution up for fixing sdcard perms for awhile now in my Odds and Ends thread. Anyone experiencing issues (or not!) please feel free to check it out. :)
[SuperSU] gamepois0n:
what is this new 1.51? can't find the changelog for it
[SuperSU] Pkt_Lnt:
delete
[SuperSU] gamepois0n:
no dude, thats the changelog for 1.50 not 1.51
[SuperSU] nhariamine:
anyone experiencing force closings after installing this update of supersu? i installed after it filexpert and it force closed, rebooted and still everything i install ends up force closing ???? please help
[SuperSU] osm0sis:
Minor fixes I'm sure, just like with v1.43 to 1.44; Chainfire posts changelogs if he deems them necessary.
[SuperSU] gamepois0n:
thanks for the info ;o
[SuperSU] jazzruby:
ASUS TF101

ROM: KatKiss-4.2.2_224

TWRP 2.3.2.3

E:Error in /sdcard/Master/UPDATE-SuperSU-v1.51.zip
(Status 0)
Error flashing zip '/sdcard/Master/UPDATE-SuperSU-v1.51.zip'

TWRP 2.5.0.0

E:Error executing updater binary in zip '/sdcard/Master/UPDATE-SuperSU-v1.51.zip'
Error flashing zip '/sdcard/Master/UPDATE-SuperSU-v1.51.zip'

-JR-
[SuperSU] plee3:
Are you the file is correct? The md5 should be

92bf3da522bbb6e86725fe3290f391cc

I had the same problem which turned out to be a corrupted file.

Hope this helps... plee3
[SuperSU] plee3:
Strange. I don't have any issues flashing this on my Galaxy Nexus with TWRP 2.5.0.0.

Perhaps there is some issue with TWRP on your TF101,

Maybe you can try CWM instead?

Thanks... plee3
[SuperSU] Dreamweaver:
please help me out...

I have a SEC GT-I9300 Stock ROM XEMC2 rooted with CWM installed.

I updated SuperSU and the phone rebooted and CWM displayed the message "rom may flash stock recovery on boot - fix it?"

I tapped NO... right?
[SuperSU] Pkt_Lnt:
Correct
[SuperSU] mayur.3.92:
Help

Hi all,

i updated this to v1.50 via CWM but again saw an update in Google Play Store(may be 1.51) and updated as usually it asked to update binaries,which i updated normally(as always did) but is shows failed! now what should i do?iam unable to unroot nor have root access!!

I even find that i lost my busybox from xbin and trying to reinstall app shows no su binaries found
[SuperSU] Pkt_Lnt:
Download the zip file from Chainfire linked in the first post and flash in recovery.
[SuperSU] ThurstonX:
Read a few posts back. I had this problem. On the third try I chose the CWM/TWRP option. My Nexus 7 rebooted into TWRP, installed it, and that was that. Give it a try,
[SuperSU] mayur.3.92:
well fine can give a try but m thinking of total unroot and a Latest Flash??

Can guide me on Unrooting??In app unroot doesnt work nor deleting from Root Xplorer working
[SuperSU] saeedmashref:
I have HTC one 801n , s _off , supercid ,unlocked , stock rom 2.29.401.1 , HBoot 1.54 , stock recovery and I want to have root ! How I do it to get perfect root ?
[SuperSU] Pons:
This sounds like a question for your device's q&a thread.
[SuperSU] Morlok8k:
1.51 fails with Groid 2 global (android 2.3.4)

supersu has been updating a lot lately, and all the updates worked fine on all of my devices until July 29th - v1.51

Normal Binary installation worked fine with my droid 4 (android 4.1), and my asus tf300t (android 4.2.1). binary installation failed on my droid 2 global, (android 2.3.4).

I remounted /system as rw manually, and it still failed.

just thought i'd let you guys know. I'm sure it will get fixed soon.

Oh, and the existing binary still works, and gives the prompt. I just cant access the SuperSu app without it tellimg me i need to update.
[SuperSU] glimmling:
With the latest SuperSU update I was no longer able to mount CIFS shares. (Nexus 7 | stock Android 4.3 | vorcers-kernel)

I flashed UPDATE-SuperSU-v1.45.zip in recovery and it is working again.
[SuperSU] Chainfire:
This is not a bug, this is by design.
[SuperSU] shoey63:
So, If on 4.3, only update by flashable, zip version, not via Play store, correct?
[SuperSU] PVL_93_RU:
I'm still on v1.43 and have no problems whatsoever
[SuperSU] CoolApps:
Zip because you will have no root anyway.
[SuperSU] shoey63:
I meant if zip was flashed on 4.3 in the first place to obtain root. Subsequent updates must still be by zip?