yashsingh1/xdaforums huggingface dataset:
[SuperSU] occtec:
Can anyone tell me how the heck you flash twrp recovery zip on stock? I've unlocked the boot loader and want to flash recovery then super su
[SuperSU] Mercado_Negro:
Probably a bad download. Get the file again and try to flash it one more time. It's a 1,12MB file.

---------- Post added at 10:48 PM ---------- Previous post was at 10:46 PM ----------

Fastboot flash recovery nameofyourrecovery.img

---------- Post added at 10:51 PM ---------- Previous post was at 10:48 PM ----------

By the way, thanks for what you've done, Chainfire. I purchased the pro version of SuperSU a long time ago and I've never regretted it.
[SuperSU] occtec:
Anybody please tell me am I safe flashing Franco kernel r165 would like to use 'touch control' but need custom kernel. Will this affect my super su or root??

Cheers
[SuperSU] osm0sis:
Custom kernels won't work on 4.3 until they've at least updated their ramdisks. I made a nice little f.K + JB4.3 ramdisk hybrid for the Galaxy Nexus. :cool:
[SuperSU] Leion:
Redownloaded the file and flashed successfully!

Thanks! I am now a rooted happy android 4.3 user :D
[SuperSU] MidtownHD:
so

1. flash 1.43 zip

2. update to 1.44 in play store

3. done?
[SuperSU] GldRush98:
Right now, yah. 1.44 seems to only exist on the Play Store at the moment. Not sure what is different. Chainfire is probably getting some rest after a long day of bug squashing.
[SuperSU] cmstlist:
I believe only the app was changed from 1.43-1.44, not the binaries.
[SuperSU] Erroneus:
God damnit Chainfire, you rock!

v1.43 works perfectly here, no issues anymore with "su binary not found".

And yes, just update to v1.44 via the market and then remember to install your pro key ;)
[SuperSU] mosd:
aha this root dont work on custom kernel? Im running custom at the moment and 1.43 dont work
[SuperSU] steviewevie:
I was on 1.41 worth 4.3 and everything was fine. This morning I saw the 1.44 update on the Play Store so I updated. The app update itself went fine, but when it asked to install the binary it hung just saying "Installing, please wait".

I had to flash 1.43 from recovery to get it all working again.

Is 1.44 supposed to be ok for 4.3?

Sent from my Nexus 4
[SuperSU] lvnatic:
Does script manager work for you guys in 4.3? I run scripts as root but nothing happens.
[SuperSU] Chainfire:
There will be a new version released soon, possibly today. Lots of bugs fixed.

High CPU load issue and zombie processes causing it should be gone now. Not sure about the preferences remembering, what can help solve that. I have not been able to replicate this behavior as of yet.

I found the problem and fixed it. It had to do with how you send the command: you write the command to STDIN, then flush and close STDIN. Though obviously possible this is not exactly "expected" behavior. I'm surprised that actually works on normal sh/su - I would have half expected the command to simply be dropped. Had you either padded the command with \n and closed STDIN, or padded with \nexit\n (as would be normal for the way you run scan) and no closed STDIN, there would not have been a problem. Interesting edge-case though. This will work in the next update.

No idea. You can try :)

That is one bad app... I have adjusted SU to use much less CPU during full logging and nothing is going on, but this app just fires off SU process, and never closes them. If you start this app 20 times, you have 20 SU processes running around eating your resources :)
[SuperSU] shaggyskunk:
It's quite possibly my own newbieness & lack of knowledge, but when I look at the logs setcpu seems to be asking for permission almost constantly?

In comparison, chainsDD superuser hardly ever logs permission for setcpu?

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] vlt96:
setcpu sucks... uhm... anything...(battery, CPU) it drains more battery than it gets... use No-frills, these constant superuser requests mean that it is constantly doing something in the background, and it has nothing to do with the Superuser app you use;)
[SuperSU] shaggyskunk:
Thanks for the reply! But one of the things that I don't understand, is why one superuser would show almost no logging & another would show very frequent logging?

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] vlt96:
The only logical explanation is a coincidence... maybe the profiles in SetCpu were much more solicited, but just a coincidence;)
[SuperSU] shaggyskunk:
Uhm.. I'll try to figure it out.

You mentioned that you thought setcpu was not a great app... Just curious as to why?

Thanks again!

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] vlt96:
Constant service doing pointless things:

1. For screen off profile, use a governor like conservative/interactiveX/smartassV2

2. Battery low profile, you can go and change it fast, it drains battery just to see how much battery you have left... it is just like Juice Defender...

3. For temperature, PUT THE HAND ON THE FREAKING PHONE:D:D(just saw a CAPS LOCK post on 9GAG:))

Use No-Frills, and just go in the app to change, or if you have CM, you can use performance settings, and add a shortcut to main screen (you can)
[SuperSU] shaggyskunk:
CM? Did you mean CWM?

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] Chainfire:
No, he meant CM == CyanogenMod
[SuperSU] DarkhShadow:
He probably means cyanogen

Sent from my ice cream powered Nexus S
[SuperSU] Chainfire:
v0.83 released !

SuperSU has been updated to v0.83. Lots of fixes :)
[SuperSU] dark_knight35:
Thx man, I'll always use your su for now.
[SuperSU] II_DiE_4:
I have "There is no SU binary installed and SuperSU cannot install it" etc.

What can i do?
[SuperSU] DarkhShadow:
Are you already rooted?
[SuperSU] shaggyskunk:
Thanks!

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] shaggyskunk:
Thanks for the update!

You're one hard working dev!

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] II_DiE_4:
Yep i am. Actually I get the popups asking for root access.

Only when I open SuperSU i get the warning for the binary.
[SuperSU] niteh@wk:
Interesting features in OP. Trying this now.. A question: how is new su binary updated? I do not see an option in the apk (UI) to update binary. Is it updated automatically by the UI when there's new binary update?
[SuperSU] DarkhShadow:
When a update is required it tells you

Sent from my ice cream powered Nexus S
[SuperSU] kmakro:
great info, thanks
[SuperSU] Xeodus:
I get the same thing - anyone got a solution for this?
[SuperSU] Erroneus:
Update to 1.43 from recovery and then update to 1.44 from play store.
[SuperSU] mdalacu:
Hi, does OTA protection work on Nexus 7 4.2.2 in case of an upgrade to 4.3? Thank you very much.
[SuperSU] maciek82:
I constantly get "Failed to locate the APK file" when trying to uninstall any program using Titanium Backup. Sorry if this was covered already, but can someone help?
[SuperSU] polobunny:
??

Is this related to SuperSU in any way?
[SuperSU] maciek82:
Started happening after 1.43 upgrade so I'm asuming so :confused:
[SuperSU] My Gnexi:
Hello [MENTION=631273]Chainfire[/MENTION],

I'm writing a guide on rooting (on other forums), and I want to link to SuperSU.

However if I put a link like this: http://download.chainfire.eu/339/SuperSU it frequently becomes outdated.

I can (and do) solve it by putting a link to this thread however it is not ideal because users may not be technically skilled, and the might not know english.

So I suggest/request you make a web page for SuperSU and put the link to the latest version there. You may want to have archive with links to older versions there.

This will make life easier for your users and may be good for SEO as well (if I google "supersu" the fourth result is http://download.chainfire.eu/282 which is very old)
[SuperSU] bsoplinger:
Why not use a link to the Play Store Web page for SuperSU? IE: https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[SuperSU] My Gnexi:
Ummm... because the app doesn't root the device? You need to download ZIP and then flash it from recovery.
[SuperSU] TeamDraven:
Trouble flashing this via CwM

Hi Guys.

I have previously flashed 'superuser' via CwM, (believing that it would grant Root, but it didn't), a user on another thread advised flashing SuperSU in CwM to gain root.

When I try to flash SuperSU via CwM I always get an "install aborted" message.

Is that because I already have superuser installed?

unfortunately it seems I'm unable to uninstall superuser.

So I currently have an HTC One, with its bootloader unlocked, CwM Touch Recovery, superuser flashed, but no Root access.

Any assistance would be great.

Cheers.

Greg.
[SuperSU] ironia.:
same problem here...on crespo with stock jb 4.1.2

i have to shut down the phone
[SuperSU] TeamDraven:
All's Well.

I downloaded Hasoon2000's All-In-One toolkit and rooted my HTC One from that.

:)

Greg.
[SuperSU] jesssiii:
No, it was happening to me even before the 1.43 upgrade. Titanium needs to update for 4.3.

Galaxy Nexus Toro
[SuperSU] AlxMAX:
[MENTION=631273]Chainfire[/MENTION]: I have noticed that daemonsu and su are 2 identical files. Consequently, in order not to occupy too much space, you may keep the su binary and create a symbolic link to it called daemonsu in /system/xbin at the installation time. To achieve this, you may modify the updater-script file and put symlink( "/system/xbin/su", "/system/xbin/daemonsu" ); instead of set_perm(0, 0, 06755, "/system/xbin/daemonsu");

If you use the file name (which is usually argv[0] in C) to detect how your executable is launched, the mechanism is perfectly safe.
[SuperSU] ygvuhb:
I think these is a bug in the new super su v1.43

I always have to disable superuser as i play puzzle & dragon JP

In Super Su 1.43 after disable supersu , when i enable Superuser again , it show installation fail

but this version and the older version supersu have not this problem

http://download.chainfire.eu/340/SuperSU/SuperSU-JWR66N-S005-130625-1.41.zip

anyone confirm it?

i am using nexus 4 android 4.3
[SuperSU] :
Search for an thread called motochopper

It's always so much harder when you have to try (David Gray).
[SuperSU] str355:
Thanks for the update, v1.43 works fine on my GNex (stock 4.3).
[SuperSU] Heathered:
[MENTION=631273]Chainfire[/MENTION]: Upload v1.44 here (cwm)...
[SuperSU] nyepo:
Hi!

I have a rooted Nexus 4 with stock recovery (I used WugFresh kit just to root). So, I have now SuperSu v1.25. As I already have stock recovery and haven't deleted any system app, I can OTAupdate my device (same as I did before with 4.2.1 -> 4.2.2).

So, do I need to uninstall SuperSu (and unroot the phone) before getting the OTA or it really doesn't matter if I did? Last time I did not and all gone well. I mean, just wanna have my Nexus 4 with 4.3 rooted and stock recovery again, and SuperSu new v1.44. So, uninstall supersu, unroot, OTA, and then WugFresh rootkit again (when updated)?

Or no need to uninstall SuperSU before OTA? If I don't do anything, will it be overwritten by new SuperSu 1.44? (I bet yes).

Thanks
[SuperSU] ProfMozz:
I updated my Nexus 7 today (by OTA) without unrooting/unflashing custom recovery and gladly "almost everything" works fine (I lost root access though, but it seems not quite hard to regain at least in my device).

UPDATE: I regained root access by flashing "SuperSU v.1.43.zip" first and then updating it from Google Play. Back to normal!
[SuperSU] bsoplinger:
Guess I should have explained more. The Google Play Store page has the link to Chainfire's site where the latest version is always available.

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[SuperSU] khaytsus:
Did you seriously just tell Chainfire how to use ln?
[SuperSU] lion7718:
Has anyone with a stock rooted Nexus 4 been saved by Survival Mode upgrading OTA to 4.3.3..??

Also, should I un-root it 1st..??
[SuperSU] Chainfire:
This will break update functionality. If you do this, SuperSU will not be able to update binary to new version in case it's updated.

You cannot currently update from 4.2 to 4.3 and keep root without re-rooting.
[SuperSU] Chainfire:
v1.45 released

Biggest change is a fix for a possible credential check bypass in the daemon, recommend updating immediately.
[SuperSU] CBers:
What's the easiest way to re-root please?

I've seen several suggestions, but what's easiest?

TIA.

Sent from my 16Gb Nexus 4
[SuperSU] stuart0001:
I can't be certain if SU was the cause but with 1.43 Android OS was pegged at 1026 CPU usage. Unrooting and a reboot fixed that.

I forgot to get a logcat but I will if it repeats.

Note it didn't happen in the 1st 16 hours but after an overnight charge.
[SuperSU] shoey63:
SuperSU-JWR66N-S005-130625-1.41.zip worked perfectly on newly compiled AOSP 4.3 firmwares for Xperia Z. Shall I try this build? (On account of security enhancements) Or is it unnecessary?
[SuperSU] jesssiii:
Fastboot custom recovery, flash zip of SuperSU in OP.

Galaxy Nexus Toro
[SuperSU] CBers:
Thanks jesssiii, I've used Wug's toolkit (v1.63) to re-root my Nexus 10.

Manually downloaded TWRP (v2.6.0.0) & SuperSU v1.43 zip.

Changed Recovery Image to v2.6.0.0.

Installed TWRP via toolkit (ROOT button) then flashed SuperSU zip when TWRP started up.

All rooted again :cool:
[SuperSU] gpvecchi:
Each time I flas a package with TWRP I lost root...This is driving me mad...
[SuperSU] GroteBozewolf:
Did you disable recovery protection? This new SuperSU uses the .sh file that is deleted when this recovery protection is enabled.
[SuperSU] osm0sis:
I notice the binary auto-update works again (didn't for me in 1.43 or 1.44). :)

The Install SuperSU to /system option seems to work, but I notice you have to do it twice:

-1st time it deleted the current /system/app/Superuser.apk and reboots.

-2nd time it moves the newer version from /data/app to /system/app/Superuser.apk and doesn't reboot, just closes itself and gets hidden from the app drawer.

I also notice your symlink to /data/media doesn't appear to work with all apps either. Check out AntTek Explorer and enable Native mode (root view). :(

Any way to improve this, or anything we can do manually to improve sdcard access for root apps?
[SuperSU] gpvecchi:
Ehm, where is it?
[SuperSU] Chainfire:
The binary auto-update *always* works. If it doesn't tell you to update, you don't need to update. Explained a million times.

I'm not even testing this at the moment, low-prio compared to other issues.

It's the apps problem. If you look closely, you see AntTek Explorer simply fails to navigate any symlink. The symlink is there and it works. I'll transition to binds sooner or later, which should solve that issue (but still, this is also a bug in AntTek)
[SuperSU] GroteBozewolf:
It's a CWM setting. Dunno exactly where to find it. Still waiting for my 4.3 OTA.
[SuperSU] osm0sis:
Not what I meant. Updating 1.41 to 1.43 or 1.44 would say that it failed to update it and require the zip reflashed, 1.45 seems to actually handle it correctly itself. Either way, it works, so fantastic job! :good:

Understood. Just wanted to make sure you were aware. ;)

Yeah it does have it's foibles but it's one of the best out there otherwise. Glad you've got a couple more tricks up your sleeves for the sdcard issues, regardless. :) Any way to easily manually bind things in the mean time?
[SuperSU] ogre_x:
Does the installer preserve the original /system/etc/install-recovery.sh?

Will you be able to do an OTA or will the changed file cause problems?

This is for Nexus 4 mako (can't find that file in the GNex factory image)
[SuperSU] osm0sis:
Here's another little oddity. In Terminal Emulator, after typing su to get the root # prompt, pressing up (with Hacker's Keyboard) doesn't properly display the previous command anymore. This wasn't an issue with the old su. Works fine with the user $ prompt so I guess the problem probably lies with the new daemonsu.
[SuperSU] My Gnexi:
That really doesn't make sense. The Google Play page has a tiny "Visit Developer's Website" link.

Then you get to Chainfire's blog not download site, and you need to find the latest SuperSU (might not be the top post), then click "Read this article" (clicking on heading doesn't work). Only then you get a link to the download page where you have to click again to download.

That's too complicated for users to do (five clicks!). I want to write an easy guide.

To prove my point, try to google "rooting galaxy nexus supersu". A randrom article I clicked suggested to download:

Android SDK http://developer.android.com/sdk/index.html

CWM http://www.clockworkmod.com/rommanager or TWRP http://teamw.in/project/twrp2

SuperSU http://download.chainfire.eu/267/SuperSU/CWM-SuperSU-v0.97.zip

You see? only SuperSU got a direct link to an outdated version. All the guides either link to old version or give you a pre-made zip with stuff you need including outdated version.

It would have been much easier if the for a site like for example http://download.chainfire.eu/latest/SuperSU...
[SuperSU] Chainfire:
That's just blind luck really. Still working on the daemon update. Strangely, it's suffering from an issue on the official 4.3 releases that wasn't there on the SGS4 4.3 leak. How cool is that! :)

Not that I know of ...

It doesn't need to be preserved, it doesn't do anything useful, it's annoying as hell if you're running a custom recovery even, and those tend to try to remove it.

That being said, to prevent that removal, I've made the file difficult to remove, which currently also messes with OTA updates. I recommend a "full unroot" (from SuperSU's settings) before applying an OTA. You'd have to re-root after the OTA.

Due to the remote terminal, pre-su and post-su command buffers are cleared.

The first post of this thread always has an up to date link. There's a latest link on my download site as well, but it's currently not public due to the multiple branches. Those are merged now so it could be public again. Maybe I'll just do that right now, stay tuned.
[SuperSU] ogre_x:
As long as the OTA doesn't try to patch the file there will be no problems I suppose if you to a full unroot before the OTA (which seems to be good practice anyway). I guess you remove the file completely upon "full unroot"?
[SuperSU] osm0sis:
Not what I meant again unfortunately. :p

I mean after I've entered commands in post-su at the root prompt, pressing up doesn't bring them up correctly. Goes to a new line and displays nothing unless you start pressing left and right, but it's impossible to make sense of it to edit the old command like you normally can. Please give it a try. Hopefully there's something you can do about it. :)

OTAs never patch that file that I've seen. In fact, it only exists in OTAs, not as part of Factory Images, so OTAs always just extract it directly. Chainfire chattr +i -ing the file should keep OTAs from being able to do that even, so I think it'll be safe. :good:
[SuperSU] ogre_x:
Thanks, that's why I couldn't find it in the factory images, but only under recovery/etc in the OTA files :)
[SuperSU] Chainfire:
I'm not sure what is going on here, and unfortunately I do not have the time to work on this right now.

Actually the chattr +i may prevent the file from being written, and thus fail, which may bomb out the OTA process. I think it's one of the very last things normally done, so even if it bombs there may not be an issue. Then again, maybe there will be ...

I talked to another dev yesterday who tried pretty much this, and he told me the process bombed. Haven't tried it myself, though.
[SuperSU] osm0sis:
No problem. Understandable that you've got bigger fish to fry at the moment, and then your vacation of course! :) Just hoping you can keep it in mind for later.

Guess it depends if they put that in an assert or not.. Checked a couple and it looks okay!

delete("/system/recovery-from-boot.p",
"/system/etc/install-recovery.sh");
show_progress(0.100000, 10);
ui_print("Unpacking new files...");
package_extract_dir("system", "/system");
ui_print("Unpacking new recovery...");
package_extract_dir("recovery", "/system");

Later it sets perms on them but still no asserts so it should all continue to work and not 'bomb' if it can't complete those commands. :) :good:
[SuperSU] Chainfire:
http://download.chainfire.eu/supersu
[SuperSU] azcv:
Hi,Chainfire.

First of all I want to say that I am not a developer and I don't have the OTA update yet.But it is very important to have working root after update.That's why I am following all the topics about the problem.As long as I know the big issue is the "nosuid" parameter for /system mount.And now I have one question:if the mount binary is replaced with modified one which will ignore this parameter only on /system mount will this fix the issue?Or there is another thigs that prevents the old root methods from working? I want to say again that I am not the developer and I want to be excused if the question sounds stupid.
[SuperSU] osm0sis:
I think you got this from the Android Police article? It's not as simple as just taking out the nosuid parameter for /system again, (in fact it's still not there in the fstab either), it's done more on-the-fly. Read the Koush post that Android Police misquoted: https://plus.google.com/110558071969009568835/posts/LtttyekSUoi

"Basically /system is mounted as nosuid to any zygote spawned process (ie, all Android apps). Root will still continue to work via adb shell, etc." :)

That said, ROMs can and some probably will revert the code changes to do the above, but unfortunately I don't think it's as easy as replacing the binary.
[SuperSU] Chainfire:
AP might have misquoted the article, but the article itself was mostly bollocks to begin with. Nobody cares about nosuid. I actually laughed when somebody pointed that post out to me ...

https://plus.google.com/+Chainfire/posts/Zt9xFo8UsXZ
[SuperSU] 78Staff:
I'm trying to replicate this with hacker keyboard and I'm not seeing it, I still am able to bring up post su commands using the up arrow - unless I am mis-understanding?
[SuperSU] Almighty2:
1.45 isn't working for me on HP Zeen Tablet running 2.2.x as when I open it, it will just show the white screen and then Android will say SuperSU is not responding, and I am given the options to force close or wait. Rebooting yields the same thing. The su binary seems up to date, and all things needing su continues to work. 1.44 and 1.43 and earlier works fine.
[SuperSU] p.chi:
stuck at boot logo after update

I'm wondering if anyone else has this issue. I just updated superSU v1.45 (7.27.2013 update) and it rebooted my phone when it asked if I have installed TWRP\ CWM or normal. I choose the TWRP\CWM option and now I'm stuck on the Samsung Galaxy Logo boot screen.

What just happened and what can i do to fix this?
[SuperSU] :
Try rebooting into recovery and wiping /cache and dalvik-cache to start and let's take it from there
[SuperSU] osm0sis:
Can you edit the post-su commands correctly, on the same line as the prompt?
[SuperSU] itasoulas:
has anyone figured it out busybox problems? Some apps misbehave or not functioning (like V4A) which says device is not rooted or no busybox installed. I am sure that with latest supersu gnex is rooted so probably we are waiting for devs to figure out the busybox issues :confused:
[SuperSU] nex86:
stupid question: OTA survival will be pretty pointless if the OTA update zip formats /system right?

what I mean are the run_program("/system/chattr", "-i", "/system/xbin/su"); commands in the updater-script of SuperSU
[SuperSU] gpvecchi:
Oh, OK. TWRP doesn't nave it...
[SuperSU] jesssiii:
Pull battery, go to recovery, reflash SuperSU, reboot. Next time choose normal.

Many apps will need to update for 4.3, don't think it's busybox.

Galaxy Nexus Toro
[SuperSU] osm0sis:
OTAs don't format, otherwise they wouldn't be able to patch files. :)
[SuperSU] 78Staff:
Yes, can use arrows to move back through the command and edit, post-su