yashsingh1/xdaforums huggingface dataset:
[SuperSU] t-ryder:
SuperSU bricks Xiaomi MiPad

Sir,

I am a team member of decuro.de and we cook your superuser app into “our“ Xiaomi MiPad ROM, since the device has no MIUI security center app that can manage

permissions. It works well, but - after updating/downloading the SU binary which is done after every update flash of the ROM - the user is prompted to reboot and flash the binary

via TWRP/CWM or install the binary “normal”. When clicking “normal” at the dialogue window everything works fine. But when clicking “TWRP/CWM” accidently users brick their device, which happened

to quite some of our users. Could you provide a Superuser.apk without the option to install it via TWRP/CWM? A version that just has a button “OK, install and reboot” (for normal install) or something like that?

That version would need to be a non google play update apk, so it does not get overwritten by play updates.

I understand if you deny, but it would be great if you made this possible, so we can prevent users bricking their MiPads.

I tried to decompile Superuser.apk and fix stuff on my own, but I got errors just decompiling, and since I am not a good coder it would take some time for me anyway.

Kind regards,

t-ryder

decuro.de staff
[SuperSU] egingell:
Every time I tried changing my PIT, I would get a bigger data partition as intended in the eyes of parted, but the phone still reported the old size and wouldn't use more, so I had useless space.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Rinoceros:
I am totally not an expert, but I am already missing between lines 4 and 5 (none... and proc...) this line:

adb /dev/usb-ffs/adb functionfs rw,relatime 0 0

don't know what this mean (probably something for the developer)

And I am missing this line as well

tmpfs /storage/emulated tmpfs rw.seclabel,nosuid,nodev,raltime,mode=751,gid1028 0 0
/dev/block/vold/179:33 /mnt/media_rw/ext_sd texfat

This last one is meaning; your phone is not recognising your SD-Card at all.

I do suspect a faulty sd-card. Can you try another one in your phone? Might be a smaller one, just to test if the phone itself is working correctly.
[SuperSU] Mike B.:
According to your "mount" output, you don't have a recognized external SD Card, at least not at the expected /dev/block/mmcblk1 location, and if there's no device it's pointless to even worry about partitions on that device. You seem to have two issues. The first one is whether you can recover data on your card and since your phone doesn't recognize it, that's best done in some other way (computer?) in read-only mode. The other issue is the mystery of what happened when something apparently wiped the card. That part should be studied with another card only containing "test" data.

For future reference, it might be unwise to use W*ndows to format a card unless you know exactly what you're doing. For some reason, whatever tools are commonly used under that platform (NOT a MS user here, sorry) often create an additional partition before the actual primary partition, making that primary difficult to properly detect by many devices. It's OK to do that if it's the only way to get the phone to recognize the card, but them immediately reformat it (correctly?) from the phone, preferably as extFAT.

That said, since this doesn't seem to have much to do with SuperSU 2.46, it's best not to further clutter this thread and you may want to discuss your SD Card woes wherever your device is supported.
[SuperSU] Fuse8499:
Malicious app? Hahahaha I trust anything developed by Chainfire. Just ordered the Pro version to support him.
[SuperSU] Mike B.:
Are you now trying to control SuperSU's 'su' binary with the superuser.apk from ChainsDD/Koush/CM?

Are you absolutely positive that you got rid of all leftovers from your several previous root attempts. Something doesn't sound right AT ALL!
[SuperSU] awl14:
Final confirmation that my crash issue is unrelated:

Trying to replace a properly installed Koushik Dutta Open Source Superuser.apk by the current (either 2.46 or 2.49) SuperSU gets me back to the exact same crash log that I have already documented above. So we can clearly rule out any KingRoot involvement in this issue - rather, for unknown reasons, SuperSU has issues reading the environment from class android.os.Environment on my device and throws a NullPointerException from the static class initializer, which then causes the Dalvik VM to crash... :(

If you want me to do additional steps for debugging the issue, just let me know!

Thanks again,

awl

---------- Post added at 01:35 AM ---------- Previous post was at 01:29 AM ----------

Yes, but I'm not just trying to, I have successfully done so (but would still prefer a working SuperSU over the superuser.apk from Koush).

Yes, absolutely! Trying to replace a successfully installed Koush Superuser.apk by SuperSU apk gets me back to the exact same Dalvik crash being unable to read android.os.Environment. No remnants of KingRoot at all on my device.

So can [MENTION=631273]Chainfire[/MENTION] look into this, please? I have already bought a SuperSU Pro license for my tablet, and would be more than happy to be able to use it on my new Archos Neon 50c mobile as well... :)

Thanks,

awl
[SuperSU] Mike B.:
[MENTION=631273]Chainfire[/MENTION] is unlikely to help you in this thread dedicated to the STABLE 2.46, but even in the BETA and SUPPORT threads, he would need a concise documented summary of the exact issue you have without all the extraneous references to previous failed root attempts. Note that he will be away for most of the summer so you still have plenty of time to do some sleuthing on your own... ;)
[SuperSU] imranayub786:
problem

Hey whenever I open this it gives me an option to update binary when I click on update it gives me an error what should I do?
[SuperSU] casouzaj:
Flash the zip in recovery. And if you're running Lollipop, perhaps the beta 2.49 zip might suit you better
[SuperSU] awl14:
Hi again, Mike,

so what would be required for a "concide documented summary"? :confused:

The SuperSU Support thread does mainly address update failures.

"Required info" as stated there is as follows:

Exact device model: Archos Neon 50c (not SIM-locked or branded) - Spreadtrum 7731 quad core 1.2 GHz (armv7)

Exact firmware version: TBW9612_9715_V010012

Exact Android version: 4.4.2

Exact SuperSU version: 2.46 or 2.49, both showing the same crash after successful installation

Interfering apps: none - I swear that all remnants/remains of KingRoot - which is needed to get an adb shell as user root (there is neither TWRP nor CWM recovery for a Spreadtrum 7731 device) - have been successfully removed! :fingers-crossed:

Update methods tried: SuperSUme, Replace_Kinguser_with_SuperSU-v2.4.zip, my own script based on update-binary from the SuperSU 2.49 ZIP - all with the exact same crash as their outcome... :( Unfortunately, there is no custom recovery for my device that would allow to install through the update ZIP, as it is not signed by my device manufacturer (Archos).

What kind of root are you left with: A crash in app_process, unable to instantiate android.os.Environment with a NPE (see separate thread with logcat loglogcat log) when trying to execute su

Various logs: see attached

sulog.txt

(note that "adb shell su --self-test >> sulog.txt" also causes su to hang due to the app_process crash!)

My issue rather is that installation seems completely fine, but then when I call "su" from the adb shell, SuperSU is unable to bring up its GUI trying to ask whether I will grant su privileges, but rather crashes app_process trying to start its GUI. The interesting thing with this is that - following the source code comments in update_binary, my exact version of Android: 4.4.2 (API level 19) should not require any fiddling with app_process.

For your reference, I have also attached the end result of my scripting efforts (

doit.sh

) which is successfully uninstalling and replacing KingRoot with SuperSU - except that now su crashes in app_process...

Regarding having [MENTION=631273]Chainfire[/MENTION] looking into this: How should I refer/link from either the BETA or the SUPPORT thread to this information (I have already been criticized for cross-posting between threads...)?

Many thanks in advance for your kind help with this! :)

awl
[SuperSU] Mike B.:
This endless and apparently pointless exchange is killing my thanks-to-posts ratio! ;)

Last time you were positive there were no leftovers, you were using a CM-style superuser.apk mixed with SuperSU's su binary, not a good indicator of a clean system. Apparently you haven't reverted to a virginal stock ROM before trying anything new. If you have some root method that works for you, stick with it as it's very possible that SuperSU is simply not compatible with your device and there's no point in posting all that information(again) here where it's unlikely to be seen by anyone who can or will do much about it. If your posts in the BETA or SUPPORT threads are complete and coherent enough, [MENTION=631273]Chainfire[/MENTION] may or may not reply there after he comes back, but there's no need to further flood this thread, please!
[SuperSU] awl14:
Note that I am not a newbie/dummy/..., but rather an experienced developer with a sound background of Linux and Java who still is less familiar with Android, but enough so to only state proven facts... ;)

How did you know? I definitely start over again each time after doing a factory reset and clean cache and user data. :good:

Fine, so I'll wait until I notice that he is back and then post again in the BETA thread... :D

Will stop spamming this thread now, as it looks like I will indeed have to wait for [MENTION=631273]Chainfire[/MENTION]... :rolleyes:

Best,

awl
[SuperSU] rasoooli:
I have This Problem Too

There is Any solution Way ??

Device : P5200

Android :4.4.2

rooted With 2.46
[SuperSU] Mike B.:
I'm impressed that you searched the thread but surprised that you're replying to a post from eight months ago! ;)

That user was using Lollipop but apparently hadn't grabbed the proper (beta, at that time) Xmod version. Since your message refers to 4.4.2 you may have a different issue but make sure you have the correct version of that app for your current device and ROM.
[SuperSU] rasoooli:
Thanks .

I installed Last Version Of Xmodegames
[SuperSU] bantak136:
Sent from my SM-G7102
[SuperSU] jfogle01:
Was wondering, after rooting and installing I never received the option to disable Knox. Any idea on how I can do that? Thanks!
[SuperSU] DJSave:
Just did like post 4 said, reinstall from market thing in settings, installed test2 version and now When I scroll to settings, SuperSU FCs everytime :(

Tried several times no luck
[SuperSU] Chainfire:
Working on a fix. In the meantime, just uninstall SuperSU the usual way (through Settings or Task Manager), and reinstall the Play/Market version.
[SuperSU] DJSave:
Yep did that :)

me and my Geo guys will test this fixed version out and will fix out all bloopers :D
[SuperSU] qledo:
My superuse is bugged. it never saves the apps that i have given permision to use root, everytime i open a program that need SU it ask for the permission... any ideas ?
[SuperSU] wanam:
Arabic translation done.
[SuperSU] Tungstwenty:
Hi Chainfire,

Here's a link to some comments on an issue that might be useful to you, if you haven't already handled this in the newer versions (the changelog mentions "some ANRs fixed"): https://github.com/ChainsDD/su-binary/issues/10

It's a problem reported to occur in a situation I've not experienced myself, but with both SuperSU and Superuser sometimes there's the occasional "system hang" and whether su is the culprit or not is always a doubt.

I think rovo89's suggestion on having the app respond quickly to the binary, even if to ask for more time, could be a good measure if this hasn't already been implemented.

Hope this info can be useful, and if it's obsolete, then that's a good sign :)

I very much prefer SuperSU and it's a pitty that kernels such as Siyah started to use the previous solution after a number of complaints about ANRs. It doesn't prevent users to change the su solution afterwards but still I think the basis should be the better SuperSU if it's considered stable.

Cheers!
[SuperSU] sparksco:
I can confirm this happens to me on my HTC Evo Shift 4G on boot/startup. For some apps if I have just installed the app but not ran it yet it will prompt for su access after a reboot. Not sure if the newly installed app is to blame, supersu or what, but the prompt only shows for about 2 seconds and then disappears. A lot of times I'll miss itand not realize that it even poped up in the first place until I start wonder why the app is not working properly. Two examples are setcpu and sdcard speed increase apps.
[SuperSU] joeyfong:
Hi, I am having problem when using SuperSU with franco.Kernel updater in my Galaxy Nexus, somehow the the colors multipliers value reset after boot, which it is working with superuser, any idea??? Or I need to ask franco about this?
[SuperSU] Chainfire:
Please note that SuperSU uses a completely different codebase from Superuser. While I understand that ChainsDD's su may be experiencing a similar issue, the actual causes are very unlikely to be even related.

This application freeze / ANR thing is a pesky problem some people seem to have, but most seem to not have. Personally, I can't replicate the problem - everytime I can replicate a problem (and I assure, I spend a lot of time trying) I fix it and release an update.

If you install a root app but not run it, and it auto-starts at boot (like SetCPU and sdcrd speed increase both do) it will indeed only show a popup at boot.

The problem is that the system is very busy at boot. The su binary will attempt to trigger the prompt, but the system is so busy that it will take several seconds for the prompt to appear ... and thus it will disappear quickly, because the binary's timeout is still running ...
[SuperSU] Chainfire:
Language test #3 uploaded.

Same languages files as #2 (the language files have not been updated with the yesterdays and todays changes on getlocalisation!)

Those who had SuperSU crashing, please test if this version works and let me know !
[SuperSU] Tungstwenty:
Yes, I assume you developed this from scratch, skilled and perfectionist as you are :)

Just thought I should share the info in case the underlying concept of fast, 3s timeout for a socket response from the app to the binary might be useful even for your implementation.

I know how hard it can be tracing these pesky edge case behaviors, especially when they don't show for the developer at all.

In my opinion the recent versions show ANRs less and less often as as I said, and there's always the doubt whether su is involved at all or not.

I assume that in this situation the timeout would be 10s even for the binary and not only for the GUI, right? If it doesn't wait much longer than that it will not reach an ANR since it only occurs at about 20s IIRC.

And even in the case of missed popups at boot, one can always go to the SuperSU window later an see there an entry with "Prompt", which can be changed to Allow in order not to cause any other problems in future boots even if you'll never be able to see the popup at boot due to the heavy usage at that time.
[SuperSU] Chainfire:
The binary actually has a 30 second internal timeout before continuing. Furthermore, if it has not gotten any response at all from the visual part of SuperSU, it will simply try again after those 30 seconds, for a number of times, before really giving up.

However, many root apps call "su" from the main thread (ugh) and in this case will throw ANR.

(Really, since I've gotten into this SU thing, I've analysed a lot of "root needed" apps, and a lot of them are surprisingly shoddily written)
[SuperSU] Tungstwenty:
So, don't you think in those cases of bad usage it would be useful for the su binary to never exceed say 12 or 13s, after which an implicit Deny would be assumed?

This would be more gracious than having the system freeze for a while, even if it's not su's direct fault.

And for those situations that eventually might happen of the app not being promptly triggered by the binary because of high load or whatever, the 3s delay till an Accept / Deny / WaitForGUITimeout + RealResponse within 10s at most, would also be a good safety net?
[SuperSU] Chainfire:
If you assume that most ANRs are actually caused by this problem, it could be a fair solution. This is however not necessarily the case.

Also, a lot of people install SuperSU to replace Superuser, which is already installed. If you have a large number of root apps already installed when you install SuperSU, you will trigger this "request storm" at boot. The current method works a *lot* better in that situation than simply automagically denying on timeout (I have tested this with boatloads of root apps installed and switching between su apps).

The whole 3s thing is not present inside SuperSU.
[SuperSU] Tungstwenty:
I see your point. Well, I'll leave the suggestion just as something to be explored if you think it might useful in tracing future problems :)

Nor in Superuser, I was just a suggestion from rovo89 that I thought might make sense if the problem was indeed in GUI not responding or being fired at all, either because of SuperSU/Superuser malfunction, or system load issues.
[SuperSU] Chainfire:
v0.91 released !

v0.91 has been released and adds multilanguage support (27 languages and counting !) as well as some bugfixes.

I wanted to wait a little langer for more languages to be finished, but a few bugs really needed to be fixed *now*. There will be another language-related update soon.
[SuperSU] p1lo:
CWM.zip doesn't work on my x8 and x10mini :mad:

updated by playstore :D
[SuperSU] bitmappp:
hello Chainfire hope you can help me.

i successfully rooted my note (ICS) using dr.ketan "Download the [CWM zip] and put in your Ext SDCARD ] And [ SUPERSU-Busybox-Installer.zip] to SD card (internal memory)"

then i flash "CF-Root-SGN_DX_OLB_LP9-v5.6-CWM5.tar" using mobileODIN..

problem starts, i lost root, i cannot connect wi-fi.

tried installing "CF-Root-SGN_DX_OLB_LP9-v5.6-CWM5.zip" with PC-ODIN went fine

its still the same.. wi-fi up to obtaning IP address only:(

i flashed your latest v.91 "SUPERSU-Busybox-Installer.zip" when i open superSU to update binary its says "installation failed!"
[SuperSU] dr.ketan:
have you root using supersu busybox installer today? b'coz i have updated few hrs back and added supersu busybox installer.zip provided by ChainFire. which is having latest su 0.91.
[SuperSU] shark147:
Hi,

I have the same problem with all version of SuperSU, the PopUp "Grant/Deny" sometime don't show....

It's possible fix?

for now i came back the old superuser

Thanks
[SuperSU] FengkuiChan:
thank you.
[SuperSU] PalmCentro:
knox wasn't detected! lol
[SuperSU] jfogle01:
No sir, not detected at all!
[SuperSU] Castle2k:
I don't think it's a problem at all...

As long as u have been granted to access the root of the phone.u can do it yourself!

Sometimes it auto disable it too.. just look look at the disabled app to see!
[SuperSU] egingell:
Also entirely possible that the Knox app is not present.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] mrcarlxx:
Tagging this thread so I can find it again later lol
[SuperSU] hogze94:
I use the flashable zip (2.46), why after upgrading my rom and flashing SuperSu 2.46, it will say SuperSu is outdated. I then proceed to update SuperSu from within the app, what version does this download? Is there a flashable zip for this version? SuperSu still says 2.46 so i dont understand why it always says i need to upgrade after upgrading my ROM.
[SuperSU] Mike B.:
It's hard to be certain since you give few details, but perhaps you forgot that the SuperSU package needs TWO components, the 'su' binary and the supersu control application. If the binary (usually in /system/xbin) is out of date, the application conveniently notifies you and offers to update it. That's the correct and expected behavior. It gets complicated if your ROM includes another 'su' but SuperSU can usualy sort it out on its own. If you're unsure about which su version you have, simply execute "su -v" from your device's terminal emulator. It should show "2.45:SUPERSU" if you used the current stable SuperSU 2.46 flashable ZIP.
[SuperSU] sej87:
I8190N

Does each version is in accordance if the cwm Loading to I8190N ??
[SuperSU] Mike B.:
It's difficult to understand what you mean, but the current SuperSU 2.46 should work when flashed from a recent CWM recovery on your Samsung I8190 Galaxy S III mini. If you need more information please try a better translator!
[SuperSU] Mike B.:
SuperSU is intended for use under "true" android and I'm not sure how accurately your emulator/VM duplicates that environment. Under "normal" android, the suggestion would be to simply flash the SuperSU ZIP from a custom recovery, but you don't seem to have a recovery context. In any case, this is probably best addressed in a separate thread in the SuperSU Forums instead of in this thread dedicated to the current stable 2.46 SuperSU.
[SuperSU] h4haideralii:
Thanks 2.49 beta. solved my problem .
[SuperSU] Igorfm7:
How i flash super su in moto x 2013 Android 5.1?
[SuperSU] Mike B.:
I assume you have already tried to install SuperSU from the Play Store on your rooted device. If you're not rooted, then you must first research that task for your device (many rooted ROMS and rooting methods include a SuperSU version) . Have you tried to simply flash the SuperSU ZIP from your custom recovery? Since you're running 5.1 you may want to try the 2.49 BETA version which addresses some Lollipop-related issues. See the SuperSU and Moto X forums for details.
[SuperSU] egingell:
Um... nobody's going to call you.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] xunholyx:
Unless you promise that if you call this number it will be for a good time.
[SuperSU] egingell:
Only if I her name is Jenny and I saw her name and number on the wall.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] xunholyx:
867-5309
[SuperSU] Igorfm7:
mod edit: removed phone number for member's protection
[SuperSU] k1labban17120692:
Great work OP!
[SuperSU] doctor-who:
latest version from playstore ****ed up my 2 phones!!! promt doesnt work and slows down phone till i must remove battery! How dare you to publish app with bugs on damn playstore?!!! shame on you!
[SuperSU] pkelly517:
And yet you left Jenny available to the entire InterWebs.

:)
[SuperSU] CyberpodS2:
Either operator error or using it on devices you shouldn't... This version must have millions of installs by now. Instead of bashing the product, use this forum as it is intended and ask for some help...
[SuperSU] hgmichna:
Bad effects wrongly attributed to SuperSU

or the observed effects have another cause.
[SuperSU] Andrew_hax5:
Update

Won't let me update SuperSU binary! Help!!!!!!!
[SuperSU] Mike B.:
I see you're new here, but maybe you should read the OP, especially the part that says:

If you can't find your answers by searching, note that nobody will be able to help you until you share some useful information, such as which device, which ROM, which SuperSU version, how you're trying to install/update, what message/error you received, etc. Care to try again? ;)
[SuperSU] Mike B.:
Strange device you have! ;) At a glance, it seems that something is definitely confusing the installer. Before you spend too much time on this, have you at least tried the BETA 2.49 that rewrites some portions of that script?
[SuperSU] Mike B.:
I'm no expert, but it seems that since you apparently can't even mount /system and /data, it's no surprise that the installer fails and that's probably a good starting place to investigate. ;)
[SuperSU] Mike B.:
This thread is about the stable SuperSU 2.4.6. Since you are referring to the BETA version, it might be more appropriate to post in the BETA thread instead of in this "pre=5.1.1" area.

At a glance it seems your scripts uses Edify. I don't now what your recovery can handle, but it might be easier to use shell commands to emulate what the current install script does.
[SuperSU] vel_tins:
Ok, I will move my post to that area.

Thanks anyway