yashsingh1/xdaforums huggingface dataset:
[SuperSU] rgbigel:
Boot loop after Updating SuperSu from Google Play (just now)

After automatic update via Google Play just now (2.12.2014, 15:50) the system (OmegaRom 39) fails and reboots. SuperSu version v2.37 from Google.

The boot loop here occurs after I enter the pin code, apparently after successfully loading various programs (which all are terminated quickly after that), then reboot is triggered.

Problem seems to have started after it asked the SuperSu binary to be updated by TWRP 2.7.1.0.

More details on http://xdaforums.com/showthread.php?t=2253528&page=2543#post57200960
[SuperSU] Mike B.:
The update-binary script attempts to temporarily move Maps.apk, GMS_Maps.apk, and YouTube.apk. If any of those is missing (app doesn't exist or is a user app), it will still end up creating a 0-byte file on exit. When flashing via TWRP on my system I end up with empty GMS_Maps.apk and YouTube.apk files. It looks trivial to correct but probably not at the top of anybody's wish list! ;)
[SuperSU] IronTechmonkey:
Thank you for this explanation. Is there some way that the manipulation of Gmaps or the 0 sized file can change GMaps' relationship with GPS settings in the running OS? Does that script run the same when flashing from recovery as it does when updating in OS?

The scenario is that for 2 people using SuperSU on fresh CM11 msm8960 jbbl recently nightly build with same PA Gapps nano package on same Moto AHD/MB886 phone:

- One (I) installs SuperSU from play store, updates the binary and reboots. When attempting to use device only GPS Google Maps 9.1.0 persistently prompts to use High Accuracy mode even after ignore is pressed.

- The other ([MENTION=2945516]KrisM22[/MENTION] - finally got this on topic, and thanks for testing!) flashes SuperSU after flashing ROM/Gapps, therefore doesn't have to update binary from within OS. When using device only GPS Google Maps 9.1.0 ceases the High Accuracy prompt after the first time it is "ignored" - as expected.

This does not happen with previous 9.0.0 version of Gmaps and I don't think this is a problem in SuperSU, but your post is the first thing I've found that shows a connection between GMaps and SuperSU, and the installation of SuperSU seems to be the only pertinent difference between what we are doing.
[SuperSU] Mike B.:
I have no special knowledge about those issues and I merely reported what I saw by reading the update-binary script included in the current SuperSU 2.37 flashable ZIP. The mere presence of a zero-byte apk file is unlikely to have any detrimental effect over anything. If somehow the temporary move of the aforementioned apks or their return to the original location fails, it would be the same as if the apk(s) in question were deleted and probably still not enough to trigger the symptoms you describe. Your issues are probably best discussed in your device/ROM's threads.

My only SuperSU-related suggestion would be that if you have a suitable recovery, it's easier to use the appropriate flashable "UPDATE-SuperSU.-v*" file for the initial install. Once you have a fully functional SuperSU, then a quick update from the Play Store may suffice. I personally always use the flashable ZIP which automatically moves everything into place painlessly. Note that to further exonerate SuperSU, you can always set the default action to "grant", at least temporarily, so that everything that needs root access gets it. Only a functional su binary is required, and SuperSU is merely the optional gatekeeper allowing you to limit root access by some processes.
[SuperSU] IronTechmonkey:
Thanks for the even more through explanation. Although the only connection I've been able to find is to SuperSU that logical thread is thin and I really don't think SuperSu needs exoneration. On my next ROM flash I'm going to try installing SuperSU from recovery and see what happens with Gmaps and GPS. Thanks again.
[SuperSU] dingoxiii:
SU Binary update becouse pincode is enable on superSU

Hii.. How to disable pincode on superSU? I can't update SUbinary since i had a pincode on my superSU..

Thx in advance
[SuperSU] kingvortex:
See this post by Chainfire.

Sent from my C6603
[SuperSU] modemman11:
Ever since the last 3 or 4 updates, scrolling down thruogh the settings screen is a pain in the butt. It wants to scroll left to logs, rather than down through the settings. Not that big a deal but since there have been a few recent releases, this makes it a bit harder to install the supersu update to /system as that option is at the bottom of the settings screen. Is this a known issue?
[SuperSU] binaryjay:
I purchased Pro but can't find ota survival mode anywhere. What am I missing here? On android 5.0.
[SuperSU] Taomyn:
You're missing not having read or searched through this thread properly.
[SuperSU] jesssiii:
No more survival on lollipop.

VZW LG G2
[SuperSU] Ja_som:
[MENTION=631273]Chainfire[/MENTION] I only want to report, that 2.37 works without any issue on Android 5.0.1 (LRX22C) on my Nexus 7 II (WiFi).
[SuperSU] marbulas:
I don't know how to force the type of installation of SuperSU's update.zip.

I tried to flash at Temasek's unofficial CM12 build 1.3 on Galaxy Note 3 with TWRP 2.8.1.1 but update.zip flashes incompatible one for android lollipop and ART.

What'd I do to install SuperSU correctly?
[SuperSU] Giobio:
Download it from play store:

https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=it
[SuperSU] Cyclu:
Exactly what happened to me when I have updated via TWRP from version 2.35 to 2.36 and not at first update from 2.01 to 2.35 I ended up with empty Maps.apk, GMS_Maps.apk, and YouTube.apk

Thanks for your post I was really surprised to find these apk's first I did not understand what happened and only after verified the date and time of apk's in system/app with Root Explorer I realized that it's related to SuperSu.

I don't know if it has to do with SuperSu but I lost an folder data/anr/traces.txt

Sorry for my translator English.
[SuperSU] NZgeek:
Sorry, but your question makes absolutely no sense.

The only* bit of SuperSU that cares about the Android version is the code that starts the su daemon on boot. The boot process changes between Android versions, so the code here needs to do the right thing. Apart from this*, SuperSU doesn't really care about your Android version or what runtime you're using.

If you're a technical person, you can look at the updater-binary to see how SuperSU gets installed. The "binary" is actually a shell script, so it should be easy to grok.

If not, can you please tell us exactly what your problem is? We want to know what behavior you're seeing, and what behavior you expected to see. Detail is good. The people with technical knowledge can help you find the right fix for your problem, rather than you making weeks guesses.

* Yes, there is a minimum version requirement for SuperSU. The minimum version is just so old that it's barely worth mentioning here.
[SuperSU] daniello8:
I have an app that claims it didn't get root but I cannot find a way to add it to the app list in SuperSU manually (doesn't appear there either). I tried to uninstall/reinstall it - but again the same situation and no new root prompt.

Anyone got an idea how to proceed with this?
[SuperSU] marbulas:
Usually the system app on android lollipop(with ART) contains arm folder with apk file(maybe different on intel or mips). I was curious because SuperSU doesn't. I thought this is a bad installation.

I also think this curiosity occurs due to my clumsiness but this is the only way what I could get answer :p
[SuperSU] pkelly517:
Use the ROM Superuser long enough to get as request.
[SuperSU] daniello8:
Sorry .. I don't understand your instructions .. could you please elaborate a bit?
[SuperSU] Takamoto:
[quote name="Takamoto" post=57058060]what a pity, I was hoping for help..[/QUOTE]<br /><br /><br /><br /><br />

<br /><br /><br /><br /><br />

In your first Greenify screenshot, there is a reference to 'keyguard is unlocked' (keyguard = lockscreen, I think that part of greenify was badly translated in your language) ... probably it is inherent to the Pin protection offered as pro feature in SuperSU but I'm not entirely sure.<br /><br /><br /><br /><br />

<br /><br /><br /><br /><br />

Now I think we should ask to @<a href="http://xdaforums.com/member.php?u=631273" target="_blank">Chainfire</a> if this lockscreen permission may be stopped in free version without issues. :)<br/><br /><br /><br /><br />

<br /><br /><br /><br />

Can I solve the problem with the last supersu update? now i'm on supersu v 2.16<br/><br /><br /><br />

<br /><br /><br />

I've update the last version supersu..same situation.. :(<br/><br /><br />

<br /><br />

no one have a solution?<br/><br />

<br />

It was enough to simply convert supersu as system app. <br />

Thanks all.<br/>

I tried to convert supersu in system app and the process was gone..but after reboot..has reappeard.
[SuperSU] jayplusone:
Please stop quoting yourself over and over. It makes absolutely no sense and no one can help you this way. Thanks.

Sent from my Nexus 5
[SuperSU] Cyrus_94:
v2.37 working fine for my Lenovo A850+

mtk6592 device, using carliv custom recovery v2.4 and official rom.

thx for your hard work chainfire.
[SuperSU] mindmajick:
Sorry for the OT... but nice to see grok used :) glad I'm not the only stranger in this strange land.
[SuperSU] Mike B.:
Hehe. I considered acknowledging the GROK myself but I was afraid it'd show my age. Nice to see that Heinlein is still being read. If I may, I'd like to suggest a quote from that same book which seems applicable to Chainfire's endeavors:

My dear, I used to think I was serving humanity... and I pleasured in the thought. Then I discovered that humanity does not want to be served; on the contrary it resents any attempt to serve it. ​

;)
[SuperSU] pkelly517:
If you are using a ROM with a built in superuser, enable it.

Run the troublesome app. SecureSettings did this in the past. Enable root access. Disable superuser and enjoy.

Of it's a stock ROM, never mind.
[SuperSU] daniello8:
I believe there is a misunderstanding. SuperSU works well - I have about 20apps in the list. Just this one doesn't appear in that list. And I cannot force the app to request root access again. So what I am looking for is something like adding an app to the SuperSU list manually .. or anything else that does the trick.
[SuperSU] mrrocketdog:
hmmmm.... how about uninstalling yhe app , and then reinstalling? wouldnt that make it request SU access again? (worth a try?)

"all I can really do, is stay out of my own way and let the will of heaven be done"
[SuperSU] daniello8:
Already did so .. to no avail.
[SuperSU] mrrocketdog:
crap!

"all I can really do, is stay out of my own way and let the will of heaven be done"
[SuperSU] Rinoceros:
You might give us more info on which app you are talking about ;)
[SuperSU] daniello8:
It's Delayed Lock .. I had this up and running before so I don't really want to blame the app but some circumstances I ran into while setting um my new phone.
[SuperSU] Rinoceros:
Try the following:

Go to settings in SuperSU and set Default Access to Grant and untick the box with Re-authentication.

See if Delayed Lock is showing up in the allow list.

Go to Apps, tick on Delayed Lock and set the settings to whatever you want.

If so, you can set the settings back to its original ones.

Let us know :)
[SuperSU] 1ce8reaker:
Hi all,

I've a GNexus (maguro version) with official Omnirom (android 4.4.4). Since I updated SuperSU to 2.37 (from play store) every time I update Omnirom the app ask me to update binaries, why? I tried to flash the zip file from twrp recovery but nothing changed.
[SuperSU] xlollomanx:
Have you tried to uninstall SuperSU directly from the in-app feature? If hot try that and make a clean installation from flashable zip
[SuperSU] daniello8:
No .. DL doesn't show up after I change those settings.
[SuperSU] Rinoceros:
Did you set the encryption on?

Play store says:

"• Requires root if full device encryption is enabled"

Otherwise contact J4velin for this. I've used some of his software to and he is giving full support.
[SuperSU] daniello8:
No .. I didn't enable encryption .. but you are right seems to already be a failure that it even expects root then. I posted in the DL thread too since I wasn't sure which component might cause this. So I guess he is aware of this. Since reinstalling didn't help and I cannot delete data on this app (don't know why) .. I may try to clear things via shell this evening.

Thanks for getting involved.
[SuperSU] 1ce8reaker:
In the app I've 3 choices (I try to translate from italian version of the app):

re-install

change super user app

complete unroot

which one?
[SuperSU] Chainfire:
Notes on root with the Galaxy S5 Lollipop firmware: http://xdaforums.com/showpost.php?p=57245348&postcount=807
[SuperSU] xlollomanx:
First I suggest you to try change superuser app, if you get again same errore try complete unroot. Otherwise do a nandroid backup for avoid all inconvenience.
[SuperSU] matlala:
Lollipoop on nexus 5 stock kernel without patch

Thanks.

It works beautifully and today I tried to flash a kernel factory Supers 2.37 and works surprisingly without patches.
[SuperSU] Borjabpv20:
No puedo actualizar los binarios.

Siempre que le doy a actualizar me dice "¡Instalación fallida!".
[SuperSU] sancho_panzer:
In English please.

* Este foro está en Inglés, está prohibido hablar en otras lenguas.

* This forum is in English, it's forbidden to speak other languages.

Device:

Samsung Galaxy S4 (GT-I9505)

ROM:

CyanogenMod 11/M12 (KK 4.4.4)

Kernel:

Alucard-V1.4qs

Recovery:

TWRP 2.7.1.0

Modem:

I9505XXUGNE8

Device:

Nexus 7 (Grouper)

ROM:

CyanogenMod 11/M9 (KK 4.4.4)

Kernel:

Default CM11/M9 3.1.10

Recovery:

TWRP 2.7.1.0
[SuperSU] ArtZ:
Problem with v2.37 and XPERIA Z2 D6503 23.0.1.A.0.167

Guys,

I tried to build a pre-rooted ROM for my XPERIA Z2 D6503 23.0.1.A.0.167 using the latest stable zip package (UPDATE-SuperSU-v2.37.zip)

Once everything is installed (clean install), I can access to any system folders but I cannot write, modify or delete files. I use Rootexplorer 3.2

This problem does not happen when I build the ROM using the previous package (UPDATE-SuperSU-v2.36.zip), only with the latest one (v2.37)

However, if I update the binary from v2.36 to v2.37 using Google Play, SuperSU v2.37 works fine on my Xperia Z2

Any ideas

Thank you.

EDIT : Problem solved. In fact, I wanted to create a pre-rooted ROM without package Z2-lockeddualrecovery2.7.154-BETA.flashable_patched.zip just with UPDATE-SuperSU-v2.37.zip BUT if I don't use both packages to build the pre-rooted ROM, SuperSU will not work properly, even with previous versions as 2.16 or 2.36
[SuperSU] Lord_Flaya:
I have a China clone (HaiPai a9500) fully rooted and running great with supersu. However if I try to install supersu as a system app, it just uninstalls. I have to reinstall from play store. Any suggestions?
[SuperSU] Borjabpv20:
I can't update the binary.

I tried to update the binary a lot of times but it always says "Installation failed!".
[SuperSU] lynnux:
I've been having similar problems, for me it affected the whole sdcard storage once, and certain folders another time (like twrp backups).

This fixed it both times, I got it from another thread: http://xdaforums.com/showthread.php?t=1998585&page=194

In terminal, enter:

su

restorecon -FR /data/media/0
[SuperSU] ArtZ:
I found the problem. I have updated my previous post.

Regards.
[SuperSU] phab3k:
I'm noticing on my nexus 6, with supersu pro, that there is no OTA survival mode option anymore. did it move and I'm missing it?
[SuperSU] kingvortex:
It was hidden in V2.22 as it isn't supported in Lollipop.

For future reference, there's lots of useful information in post #3 of this thread.

Sent from my C6603
[SuperSU] asd87:
Sending my phone in fire warranty, and the full unroot option is not working. I'm getting stuck at the "Uninstalling, please wait" screen.

Nothing happens after that, root is still present and was wondering if [MENTION=631273]Chainfire[/MENTION] has a .zip file that can be flashed to remove root. Nexus 5 Android 5.0. Thanks
[SuperSU] CyberpodS2:
Most forums have a stock firmware available to flash. Sorry I'm not familiar with the nexus but that's what I would do on a Samsung phone.
[SuperSU] ChiDi9901:
Did you try restoring the stock system partition from your Nandroid? That's the easiest thing to do.
[SuperSU] stanislav.bebej:
Beauty of Nexus

The beauty of owning a Nexus device is you can always grab the official factory image and flash it easily. Get it form https://developers.google.com/android/nexus/images.
[SuperSU] asd87:
I have the images but my computer running Linux for some reason won't recognize my phone in fast boot. I have all the drives installed for adb and fastboot but it tells me phone is not found. But thanks everyone.
[SuperSU] Elluel:
Have you tried with sudo?
[SuperSU] kalvin807:
SuperSU no longer support puzzle and dragons(p&d). Puzzle and dragons will check root before it launch, it will close if it find any stuff related to root. Before 2.30 , I could disable root though SuperSU to launch p&d. However, after I update to 2.35+ , it is not longer working. Please make it works again ,please

Sorry for my bad English
[SuperSU] apeerenb:
Okay I finally got the OTA update to Lollipop. When it restarts the N7 to install it, I am taken to a menu for Team Win Recovery Project with options for Install, Wipe, Backup, Mount etc. I didn't even know this was installed on my device.

I HAVE tried to google information on updating, but nothing is making sense to me. TWRP has live chat, but that person is suggesting I need to find someone with advanced developer knowledge to help me out. Is that true?

Is there some way I can just update the OTA easily? Is there a way through SuperSU to just restore my device to factory stock and then I can install the OTA?
[SuperSU] :
What device you're using??? :confused:

Assuming you're using Nexus device, flash the stock firmware from here... https://developers.google.com/android/nexus/images :good:

You'll need to have fastboot installed on your computer... Go get the Android SDK if you haven't already... :good:
[SuperSU] Zeuszoos:
I am wanting to update my Rooted (SuperSU Pro) SGH-M819N Mega from my Factory 4.2.2 ROM, to the now available Factory 4.4.2 ROM. But I will lose my Root status.

Someone said that after updating, I could take the SuperSU Zip file and Flash it using TWRP/CWM/etc and that would Root my device.

Is this true? If so, then I've got everything I need and can go ahead. If not, then it sucks to be me right now. :)

Thank you in advance for your help!!!
[SuperSU] Bokoblin:
icon

You should remove or fix "invisible icon" because once activated it is IMPOSSIBLE to access Supersu app without installing a launcher which have an access to activities so neither GNL and neither default launcher)
[SuperSU] Pkt_Lnt:
From post #1

I use this all the time, works fine.
[SuperSU] Bokoblin:
Can't do it only numbers are accessible and I don't want to tap an IMEI code to access it. More over why his method erase it from search with Google Now too whereas when I had kitkat hiding app with Xposed don't erase launcher but just hide icon
[SuperSU] remo0073:
Did you tried via Play Store or Settings - Apps?

Sent from my Moto G
[SuperSU] Bokoblin:
Yes, in play store, pushing open do nothing and there are nothing in "Settings - Apps" to open an app
[SuperSU] _jis_:
Not. I cannot confirm this behaviour

Not. I cannot confirm this behaviour on any device which I own. To see all my devices press button MORE INFO on the left side of my post.

What is your device?
[SuperSU] anantk1965:
OTA failures on Nexus 7 Android Lollipop rooted with SuperSu installed

Hi Chainfire,

My Nexus 7 is running on LRX21P rooted with SuperSu v2.37 with stock recovery and no changes whatsoever apart from rooting. I uninstalled SuperSu and after rebooting, tried to install OTA LRX22C when prompted as system update, but got failure with below error messages:

================================================================================

Verifying current system..

failed to stat "/system/bin.install-recovery.sh" : no such file or directory

file "/system/bin.install-recovery.sh" doesn't have any expected sha1 sums; checking cache

failed to stat "/cache/saved.file": no such file or directory

failed to load cache file

script aborted: "/system/bin.install-recovery.sh" has unexpected contents.

"/system/bin.install-recovery.sh" has unexpected contents.

(status 7)

Installation aborted

================================================================================

Even other users are facing this issue as mentioned in http://xdaforums.com/showthread.php?p=57247765#post57247765

Any reason for this Android Lollipop OTA failure? OTA used to work on Android KitKat rooted with SuperSu.
[SuperSU] jacknicholson:
Modifying your system in any way will now prevent your OTAs from applying (this includes rooting, even if you unroot).

See here: http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
[SuperSU] egingell:
How is that a SuperSU issue? If the dev of that app wants to block rooted phones, it's his problem - not Chainfire's.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] stanislav.bebej:
To set up device detection on Ubuntu Linux:

Log in as root and create this file: /etc/udev/rules.d/51-android.rules.

Use this format to add each vendor to the file: SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"

In this example, the vendor ID is for LG. The MODE assignment specifies read/write permissions, and GROUP defines which Unix group owns the device node.

Note: The rule syntax may vary slightly depending on your environment. Consult the udev documentation for your system as needed. For an overview of rule syntax, see this guide to writing udev rules. Now execute:

chmod a+r /etc/udev/rules.d/51-android.rules

# for LG: vi /etc/udev/rules.d/51-android.rules

SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"

You can verify that your device is connected by executing adb devices from your SDK platform-tools/ directory. If connected, you'll see the device name listed as a "device."
[SuperSU] modemman11:
Motorola RAZR M XT907 w/ stock ROM

I also have a Kindle Fire 7 inch but I lost root at some point and need to reroot it so can't comment on that right now.

Since my last post though I've sort of figured out this minor glitch. Seems like if I swipe from settings left to logs, but only go about half way, then "flick" back to the right to settings, there is a very quick animation of the screen going back to the right to settings. If I try scrolling down during the animation, it resets the animation of scrolling back to the right to settings and it starts the process over. I need to wait for the animation to COMPLETELY finish, and sometimes it's difficult to tell as it's only 1 pixel off but still being animated.

Now that I've somewhat figured it out, seems like some other apps have the same issue, but others don't, so still not completely sure if it's an app issue or an issue in general with animations.
[SuperSU] _jis_:
Please, enable Show touches in Developer options and post a video about your problem, it'll be better than thousands of words :)
[SuperSU] modemman11:
https://onedrive.live.com/redir?res...037&authkey=!AA_YJGQYZ_L5HKg&ithint=video,mp4
[SuperSU] _jis_:
Wow, it is really as bad as you described in previous post, but it seems to me as touch screen controller issue. Try to check it by TSC testers:

Display Tester

Nexus 7 II Tester

Multitouch Test

MultiTouch Visualizer 2

Yet Another MultiTouch Test

MultiTouch Tester
[SuperSU] :
Yup, its true... go ahead... :good:
[SuperSU] kalvin807:
It is because it stopped working after SuperSU update, after I updated the binary. I understand it is not supersu problem , but I hope he can add back the compatibility with p＆d again .
[SuperSU] djlech:
After the last update Google Firefox browsers can't load pictures/images. Plus eBay app and gumtree doesn't display any photos.
[SuperSU] egingell:
Google Firefox?

EBay app works fine here.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9