yashsingh1/xdaforums huggingface dataset:
[SuperSU] :
Chainfire or any modders interested, I have a question. It is related to root but more of a linux coding question. It's about cwm, I didnt know exactly who to go to but sense you have that great brain, it thought you could figure out a solution.

Anyway, my question is about encrypting cwm. Like, for example, you know how you can put a boot loader password on a pc. Will, I was wondering, why hasn't anyone thought of this for cwm recovery? I mean, its something so simple, that has been looked over. It would stop theives or a stolen phone from get erase and sold by someone. I gives enough time for noobs to track their phone down before people with brains, like us, get into the recovery and factory reset it.

So is it possible? And could it be as simple as a flashable mod? I don't got a clue, but thats why I like to ask. :laugh: I have actually seen post around this forum about it, but yet Jenkins hasnt answered. I think this would be great.
[SuperSU] NZgeek:
I don't believe it's possible to get the same level of protection as on a PC. The BIOS is the first part of the startup process for PCs, so it's the perfect place to enforce a password. If you get the password wrong, the whole computer refuses to boot.

It's not so easy for phones. The first component in the boot process is the bootloader, and this just does some checking before handing the boot process to either fastboot/download mode, recovery, or normal boot. Any one of these 3 areas can be used to wipe the phone. It's usually not possible to modify the bootloader or fastboot/download mode parts of the system, so any password protection would be incomplete. Incomplete protection like this is better than no protection, but not by a lot.
[SuperSU] polobunny:
The closest you'll get to something similar is full device encryption. Not really the place to discuss this though.
[SuperSU] :
Yea, didnt really think about the other modes, but thats what comes with a concept, thanks!:laugh: I know when I buy phones off ebay that havent been erase, the recovery is the first place I go, most people really dont know how to boot into fastboot/download mode, and perform a reset.
[SuperSU] Super_Dork_42:
I have a problem getting the latest binary. For whatever reason the TWRP method doesn't do anything but go into TWRP, and the normal mode fails. Then I tried going to the website and the only thing there was the whole of SuperSu (version 1.5.1 or something like that) and no binary file to download manually. Anyone know where I can get the latest binary? I've been unrooted since the latest came out and want my root back.
[SuperSU] Pkt_Lnt:
It is in the 1.51 zip file.
[SuperSU] Super_Dork_42:
Okay, so how do I go about getting it working on my phone then? Is the zip flashable? Do I need to unzip it?
[SuperSU] Pkt_Lnt:
It should be flashable from recovery. There were some issues with HTC phones and 4.3, that some have been resolved. Search back some pages for the answer. I have a GNex, so no direct instructions from me, sorry.
[SuperSU] Bill Gamble:
Yes, flash it from recovery.
[SuperSU] dehelfix:
So i rooted my nexus7 (2013) with supersu 1.51 via a flashable zip, which works great. However I setup a second profile for my wife since, and now want to make a titanium backup of her stuff. Titanium says theres no root on her profile (which it does seem theres no superSU). So my question is how do i root the second profile on my nexus 7 (root works fine on the owner profile)?
[SuperSU] nigeta_gr:
Update issue

Everytime I try to update to newest version, after moving application to system partition it turns back to an older version again (1.25).

What do I wrong?
[SuperSU] bombadier:
Not sure what you are doing wrong but if you flash the zip in the OP then you dont have to move anything as it will install SuperSU to system.
[SuperSU] LeftyGR:
Did u repeat the process a 2nd time including reboot? If not, you need to. If yes, then do as suggested and flash the zip in recovery from the op. It removes all versions of all superuser apps and installs the new version.
[SuperSU] igotroot:
I'm not sure who said having 1.51 fixes the TiBackup restore issue.....but it doesn't. I read the log and it says java.io file missing blah blah.
[SuperSU] nigeta_gr:
Still a problem

Although flashing appears to be succesful, it keeps old version. Inexplicable.
[SuperSU] dweezle:
I have SuperSU 1.51 on my Moto Xoom, stingray (armv71), on Team Eos4, nightly ver. 197. I got the message,

.Normal mode fails, the twrp update method goes to TWRP recovery and then reboots back into the system, leaving me without root access. I can recover root access by reflashing 197. I've tried downloading 1.51 and flashing it from recovery but it fails, saying

Any ideas about how to update the binary, or is the update notification incorrect?
[SuperSU] jazzruby:
See my post HERE and then follow the link to 'my original post'.

-JR-
[SuperSU] dweezle:
Thanks. Your method feels beyond my level of expertise. Is there some way of switching Superuser apps, to one that doesn't have this binary updating issue?
[SuperSU] Super_Dork_42:
Every superuser option will eventually need to update the binaries.
[SuperSU] MementoMoriM:
Thank you very much :D:cool:;):beer:

Enviado desde la muerte a través de un Nexus4
[SuperSU] mssam:
[MENTION=843111]chains[/MENTION], any plans to update because of the JSS15Q? Everything seems to work ok, but I was just curious...
[SuperSU] dweezle:
At this point I have no way of getting past the opening message that I need to update binary. I can't update from recovery (TWRP 2.6) and when the update fails from the "normal" method, SuperSU closes. I have no way of getting to SuperSU settings. Any suggestions?
[SuperSU] jazzruby:
Hi dweezle,

I gave you a workable solution, I know that it may appear too 'technical' but it really is not; if you can open/view a zip file then you can fix this.

Procedure:

1. Download the attachment/zip I posted (update-binary-sh.zip)

2. Open the zip and traverse the directory till you see 'update-binary' > right-click > copy

3. Open your SuperSU zip and traverse the same directory till you see 'update-binary' and 'updater-script'

4. Right-click an empty space > paste (overwrite update-binary)

5. Right-click 'updater-script' > delete

Back out of the zip and your done, you should now be able to flash from recovery.

If you still need help with a pkg shoot me a PM.

-JR-
[SuperSU] dweezle:
I gave it a shot. I installed in TWRP and it said successful. As I rebooted into the system, I got the message, "Your system does not seem to be rooted, swipe to root" Maybe not exactly those words, but close enough. When rebooting finishes, SuperSU is not installed. I install from Google Play and end up with the original problem, SU BInary needs to be updated. Select normal and installation fails.

SuperSU 1.51 is installed with Superuser binary 1.07 SUPERSU located at /system/xbin/su

I have regained root access by re-flashing my current ROM. SuperSU is still unable to update binary, in both the "normal" method in the app or from Recovery (TWRP 2.6.0.0)
[SuperSU] jazzruby:
I sent you an update pkg via PM, flash it in recovery and report back -success | failure-

If you get a warning about root when booting back to system just ignore it; do not let it 'fix' anything.

-JR-
[SuperSU] Super_Dork_42:
Check your PMs.
[SuperSU] thunderserpent:
On CM10.2 on my I9505, the only way I can install the su binary is through recovery; the normal method fails.
[SuperSU] osm0sis:
And if the latest nightly broke it and it's not broken in the previous nightly, why is it Chainfire's job to fix it? :confused:
[SuperSU] mrtruckincowboy:
Its not, I was just relaying info
[SuperSU] theprodigy85:
Never had this happen to me before. I updated to 4.3 on the Nexus 4 and then reflashed the SuperSU zip via TWRP. I reboot the phone, but the SuperSU app does not appear in the app drawer. I did this a couple of times with the same result. I ended up having to install it via the Playstore afterwards.

Titanium Backup says that the phone is rooted. Just wanted some confirmation from you guys that nothing is out of the ordinary and that I'm actually rooted.
[SuperSU] NZgeek:
The zip install method for SuperSU writes the application to /system/app/Superuser.apk. You might find that your kernel (or some other part of the boot sequence) is trying to ensure that you've got root and overwriting the "unknown" SuperSU apk with its own version.

The first thing I'd do is to check your /system/etc/init.d folder to see if there are any suspect scripts. If you're using a custom kernel, I'd also check its thread in case someone is posting a similar issue there.
[SuperSU] theprodigy85:
So if I see the superuser.apk in the /system/app directory, i should be good?

I'm on a nexus 4 that is all stock.
[SuperSU] NZgeek:
The presence of superuser.apk indicates that you're rooted, but doesn't necessarily mean that SuperSU is installed. If your file manager shows the icon for the app in the apk file (e.g ES File Explorer), the icon should be a yellow Superman diamond with a red hash symbol. You could also try doing a sideload install straight out of /system/app and see what the pre-install permissions screen shows as the app name.

If the apk is truly for SuperSU, but it's not showing in the launcher, then some setting somewhere must be hiding it. Check your launcher settings to make sure it's not being hidden. Check your app manager (Settings - Applications - All) to make sure that SuperSU isn't frozen/disabled. Check everywhere that looks like it might remotely be hiding a setting that affects superuser/SuperSU.
[SuperSU] theprodigy85:
Oh ok, well, I eventually just installed it via the Playstore and it would show in the app drawer then. Doesn't sound like there are any repercussions by doing this.
[SuperSU] jazzruby:
That statement can be misleading; the presence of Superuser.apk only indicates that Superuser is installed.

The only 'clear' indication that you are rooted is if the su binary is installed and has the proper owner/perms e.g. 0.0 6755 (setuid and setgid) and to a lesser extent 0.0 4755 (setuid)

-JR-
[SuperSU] recepo1:
When i flash the superuser 1.51 zip in recovery on my nexus 4 it wipes my os when i try to reboot it says no os installed could someone pls tell me the correct steps
[SuperSU] polobunny:
??

Are you trying to flash from stock recovery or something?
[SuperSU] recepo1:
No im using the latest twrp recovery
[SuperSU] polobunny:
Did you select any option when you flash SuperSU? You don't need to wipe anything when flashing it, no cache, dalvik, system or obviously data.
[SuperSU] recepo1:
Ok i did wipe cache before flashing would that cause the issue?
[SuperSU] polobunny:
Only cache shouldn't cause this issue, I could only see an issue if you wiped/formatted system honestly.

If you wiped data it would erase your personal information, not the OS.
[SuperSU] recepo1:
Exactly same thing i thought im confused why its causing this issue im stock rooted maybe i need a custom kernel
[SuperSU] polobunny:
No, kernel definitely has nothing to do with it. I'm out of ideas as to why this would happen. Maybe someone else can chime in.
[SuperSU] recepo1:
Thx for ya help
[SuperSU] bruce7373:
I could be way off base, but didn't TWRP change the order of partitions to wipe in Advanced Settings in the newer versions? I remember almost wiping data by mistake once, I thought because of this. Is it possible you simply did the same with system?
[SuperSU] Mlro Team:
He charmed me!

thanks :o

Sorry but the vercion: UPDATE-SuperSU-v1.51.zip in updater.script not run :confused:

I use GT-S5570 samsung 4.2.2 rc5 cyanogen jellybean not suport in (TWRP)

help :D
[SuperSU] recepo1:
Interesting...even when i didnt wipe cache i experienced the same problem
[SuperSU] fernandezhjr:
Have you tried booting without flashing supersu to see if the problem persists? Have you tried redownloading supersu to ensure the zip is not corrupted?
[SuperSU] recepo1:
I restored my backup and downloaded the zip several times and flashed a couple times everytime the same effect. Im originally rooted with a toolkit not sure if this would cause problems with the supersu zip
[SuperSU] fernandezhjr:
So you are saying that if you restore your backup and don't flash the supersu zip, it boots up ok? What rom is your backup, stock or custom?
[SuperSU] recepo1:
Yes backup boots fine im on stock rooted latest 4.3 update rom
[SuperSU] fernandezhjr:
Ok, so if you are already stock rooted, for what reason are you trying to flash supersu? Are you flashing a custom rom and if so, which one? Which superuser did you use to root your current stock rooted rom?
[SuperSU] recepo1:
Im tryna flash the update of superuser 1.51 because my titanium backup wont let me delete or restore apps and some apps arent working well with root as of now idk if its 4.3 issue
[SuperSU] recepo1:
Got it to work unrooted rerooted using wug toolkit it flashes superuser update no problem
[SuperSU] FlippedNL:
I tried to root my Nexus 7 LTE but when using 1.51 I get stuck at "Starting Apps"

Any idea how I may fix this?
[SuperSU] fernandezhjr:
Did you try fixing permissions?
[SuperSU] Brute.Force:
From where can I download the binary to flash through CWM?
[SuperSU] slebit:
Just flash SuperSu zip. http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
[SuperSU] recepo1:
Try wiping cache / dalvick cache after u flash it
[SuperSU] behnamsarhandi:
hi sir .

i love this app so .

according to this post :

http://androidcommunity.com/google-play-store-now-open-in-iran-for-free-apps-only-20130826/

now Iranian user can download your app in play store but if you add iran in your download app list .
[SuperSU] Chainfire:
Updated to v1.55 - Play Store should update within a few hours, or use the ZIP link from the first post.
[SuperSU] lparcshinoda:
changelog?
[SuperSU] Chainfire:
3rd post ?
[SuperSU] lparcshinoda:
missed it :) sorry
[SuperSU] Benzoman:
Sorry... could have swore I've read that as a fix in this thread. Told you I was old. :p
[SuperSU] nicholaaaas:
my solution it to just re-flash your rom. Complete wipe not required. open superuser and select allow everything (or whatever it says). then open supersu, when it asks to update binary hit ok and let it go. for some reason I've found it won't update binary initially the first time without superuser installed. @chainfire will this be a problem packaging this into a rom?
[SuperSU] Yoyoa:
Voltage control forceclosing With supersu and not with superuser when is trying to get root after it's been granted... , anyone else has this issue?

Envoyé depuis mon GT-I9100
[SuperSU] ndnesh:
I have a small problem. I have also noticed the dumpsys_alarm thing happening with better battery stats. Also, each time I install any app from market, my superSU app crashes. I don't know why this is happening. If it helps, I am on ICS stock XXLPQ and using CF-ROOT KERNEL LP7.
[SuperSU] :
Does anyone know how to completily remove supersu and get back to superuser?
[SuperSU] KMDonlon:
I am having trouble with my CWM, unable to restore any back ups....some issue reported in the log file with the .bash folder in /system. I am using rom manger premium. :confused:
[SuperSU] dimebagdan65:
Not the dreaded "some" issue! *cowers in fear*
[SuperSU] hiz99:
I seem to have lost root access....it says I need to update the binary files but it keeps saying failed...
[SuperSU] segv11:
True. Sorry to cause extra work for you :( .

The root problem here (pun intended) is that apps which aren't granted root really have no business knowing whether root exists -- it should be on a strictly need-to-know basis. Since the community has settled on using /system/*bin/su as the entry-point for root access, which android (unlike most linux) doesn't include by default, it is far to easy for a nosy program to check for the existence of that file. Ideally, root-using apps would be configurable as to the location of the su binary, so that users could install the binary in a user-configurable location where nosy apps wouldn't know to look.

I wonder it you could hide the su backup in an unpredictable place that is different on every device. Something like /system/{randomstring1}/{randomstring2}; then store that string somewhere in the apk's private data? That wouldn't stop nosy users from finding with Root Explorer, but it would be fairly hard for another app to check for it programmatically.
[SuperSU] danieldmm:
Any one have problems using ADB in ICS LPQ i9100? I me having premissions problems. .. I can acess to root system files, but I cannot create or delete files, also when entering in folders showing empty folders. Wird

Cheers its

Tanks @Chainfire for the work you done in SuperSU.

ICS Swyped pelo meu querido Galaxy S2 powered by TugaPower using tapatalk...
[SuperSU] nicholaaaas:
Try the method I posted a few posts up
[SuperSU] fromnowon:
Such a wesome job!
[SuperSU] pwelyn:
Nice,Thanks!;)
[SuperSU] KMDonlon:
I am unable to restore any backups, I believe the survival mode is not working meaning if you untick it, it still stays in OTA survival mode even though the check box is unticked. My error log reported the it is unable to format /system and do a restore because /system/.bash can not be removed. I am stumped and unable to do any restores of all my back ups...

Here is the error log:

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
Checking MD5 sums...
cache.ext3.tar: OK
data.ext3.tar: OK
system.ext3.tar: OK
.android_secure.vfat.tar: OK
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2012-03-15-12.03.20//system.ext3.tar
Restoring system...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
rm: can't remove '/system/.bash/.ssu': Operation not permitted
rm: can't remove '/system/.bash': Directory not empty
tar: can't remove old file system/.bash/.ssu: Operation not permitted
Error while restoring /system!
[SuperSU] grgsiocl:
download first sueruser from market and update it with binaries, then remove the supersu using root explorer or titanium backup. ..
[SuperSU] yoavain:
Problem with Better Battery Stats

Same problem here with better battery stats. Keeps asking for permission each time.
[SuperSU] hadi_rena:
I also have same odd behavior. Always asking for root privilege after finished charging.

BBS ver 1.6.1.0 for now...
[SuperSU] brycie:
Same here with better battery stats. Log shows failed attempt (red #) to get root after unplugging phone from charger. Asks for root every time I choose alarms from drop down list. In Supersu app it shows the app as being allowed SU access.

Using XDA version 1.7.1.0 on galaxy note N7000
[SuperSU] cbeckstein:
supersu vs remote sim access

With the newest Samsung update of the SGS2 to ICS (stock XXLPQ Android 4.0.3 firmware with CF-root kernel), Remote SIM Access Protocol for Android (RSAP, needed e.g. for certain car bluetooth sets) no longer is supported

But using the RSAP app (for usage and installation details see http://www.android-rsap.com/ , it is also available along with a separate installer App from the Market under the name "Bluetooth SIM Access Profile") this functionality can be brought back to the SGS2

RSAP needs root to work

problem is: it asks for root access each time the cell is booted and blue tooth is switched on --- even if in the supersu popup one does NOT tick the button that says "ask again"; this happening in the car bluetooth cradle renders it almost useless...

supersu logs the successful granting event but RSAP does not show up in the app list of supersu and next time the cell is started or Bluetooth is switched on RSAP again asks for root permission

is there a way around this?
[SuperSU] iBluemind:
It works nice on 2.3.5!
[SuperSU] rogconnect:
After the update...now SuperSU FC....sigh!
[SuperSU] fernandezhjr:
I just updated thru the market, which then prompted me to update the binaries. This time I was able to updates binaries normally. Previously, I had to do it in recovery. All is well for me. Thanks.
[SuperSU] anwedr:
flashed via TWRP. All's well.
[SuperSU] VivaErBetis:
+2 (done in nexus 4 and nexus 10 using TWRP 2.6.1.0).
[SuperSU] eLCruz:
SGS2 T989 is all well using twrp 2.6.1.0!
[SuperSU] Drmol:
Just to confirm I can flash the 1.55 zip instead of updating from Play Store even if I flashed 1.51 before, correct?
[SuperSU] User_99:
Yes, but via Play Store no need for reboot ;0
[SuperSU] eLCruz:
The zip is best, it automatically installs as system app without the double reboot, IMO... :thumbup:
[SuperSU] bruce7373:
Side question: I grabbed the TWRP 2.6.1 zip from the Nexus 4 thread. I can use that for the Nexus 10, right?
[SuperSU] VivaErBetis:
No, the nexus 4 and the nexus 10 TWRP recoveries are different.

For the nexus 10 use this one:

http://xdaforums.com/showthread.php?p=45144023
[SuperSU] dweezle:
Moto Xoom, Android 4.2.2. I was not able to update via TWRP 2.6.0.0, was able to update on Google Play, then when prompted to update binary was able to update using the "normal" option. That was the first time I could update from within SuperSU since 1.51. Good update!!
[SuperSU] dark_skeleton:
Quick question: After updating the app by google play, it asked me to update binaries and gave me two methods (normal and cwm). Since I wanted to test CWM, I selected CWM. My device (Xperia S) rebooted (however not into CWM, just normally) and SuperSU was happy afterwards (even apparently without updating binaries).

Now it doesn't ask to update them anymore and it hasn't created any update.zip archives on memory card.

I have re-installed it as a system app after updating though (two reboots). Does that count?
[SuperSU] Craniotomy:
apps can't access new supersu 1.55

I just updated supersu thru play store, and whenever I access supersu it doesn't list any apps at all, I have a rooted T-Mobile galaxy note 2 with jedi master v16 rom. I re-rooted my phone and still after how many reboots and fixing permissions and wipes no app can access or ask for root rights they all get stuck. I have to reboot everytime. Any help?

Edit: i uninstalled supersu with It's own uninstall option. Now all the apps that needed supersu are working properly. I even tried to install v1.51. And it was the same as v1.55, apps get stuck and cannot access super su. I've updated binaries also on both and its still the same. Any help? Please? Ideas? Solutions?
[SuperSU] jorceshaman:
1.55 running great for me. You're the man! My girlfriend loves your camera controller app too. Works perfectly for hers! (She's not rooted.)
[SuperSU] Kfler:
I am currently running a rom which has Koush superuser embedded. I want to replace it with with superSU but whenever I flash zip I get FCs. can anyone help?
[SuperSU] POWerSUrgeSW3:
Load Koush's SU app.and check settings. See if there is an option to "switch superuser app"... Just flashing SuperSU zip is probably just causing conflicts

~Max

Sent Via My WSv4.2 MD4 D2SPR
[SuperSU] Cyclu:
You must reboot, if you update with binaries.
[SuperSU] User_99:
Not here : installed via störe, started app, updated su binary and finished.
[SuperSU] doromax:
Hello, I need some help. I have a Galaxy Note 10.1 (N8000). I installed CWM-SuperSU-v1.25.zip from Philz CWM recovery 5.08.5 and I have my tablet rooted and with the app SuperSu installed. After some days I decided to do the full unroot through the app SuperSu. So far, so good. Yesterday I decided to redo the root with the same method. From recovery I flash the same package CWM-SuperSU-v1.25.zip, I rebooted the tablet but the app SuperSu missing while the root was enabled, checked with Titanium Backup. Then I thought of downloading the app from the market SuperSu and everything is back in place. App SuperSu and root functioning. Today, to try, I redid the full unroot and then using the same method (CWM-recovery and SuperSU-v1.25.zip) I redid the root. Here's the problem: the root is active, always checked with Titanium, but after installing SuperSu from the market, the app crashes and no app longer see the root. What have I done? the way that I can do a thorough cleaning without formatting, because if I can not install SuperSu have root permissions?