Did SuperUser Elite actually do anything in the end, or was it basically just a "Donate" option?
Thanks for the app Chainfire.
Yes I understand, but if you want to see the error for why the zip failed this is how.
Is it necessary to remove my current SuperUser? Will anything conflict?
Did SuperUser Elite actually do anything in the end, or was it basically just a "Donate" option?
So... I've now tested SuperSU on about 20 different phones and tablets, on anything from Eclair to ICS, and I simply cannot get the crash or "no root access" problem to occur.
If anybody has any ideas whatsoever, let me know. At one point I had somebody on the chat who had this problem, but it somehow sorted itself out and didn't occur again.
It's maddening!
@retnuh: any chance we can talk live on IRC or gtalk ?
I haven't had any app fail to get root access, only problem I have had is root explorer spazzing out and not working(guessing they need to update it?)
I only had one little glitch on reboot with avast installed as root. The 10 second prompt didn't pop up fast enough for me to allow permissions. I fixed it by going into SuperSU and selecting "Grant" as it selects deny by default. Is there a way to allow more then 10 seconds for all the apps to load after a reboot?
Stupid question alert... how do I uninstall original superuser?
Option not available in settings or the market/play store.
I'm tired and the answer is politically right in front of my face.
You need a root explorer and to delete it from /system/app
Sent from my ice cream powered Nexus S
Thanks! Ciao!Since I am very familiar with ADB and the command line, I tore apart the apk in the linked thread OP to make sure I understood what was happening during the install. I moved the original su binary and Superuser.apk to my emmc (internal memory card), manually pushed the new files out to my phone, and then rebooted.
Once CM7DX2 came all the way up, I started doing some testing and noticed the the original Superuser APK was still showing up in my app drawer. If DOESN'T appear to be conflicting with the new SuperSU APK, but I'm not sure. I have had a few times of the SuperSU app stop responding and asking to either force close or wait. After hitting wait a few times, I ended up just FCing the app.
Once everything smoothed out, the SuperSU seems to have worked, bu, I was still receiving "not responding" messages from the SuperSU app when apps were asking for Root access.
I am going to also cross-post this to the linked OP thread and see if Chainfire wants more digging into this.
Also, as a side note, I think the reason the CM7DX2 Superuser APK was still appearing is that it MAY be installed as part of 2nd-init. I'm not 100% sure about this.
So, in conclusion, for CM7DX2, I think this needs more digging in to and I will offer to work with Chainfire to see what we can do.
Ciao!
Preliminary update for Android 4.2's multi-user capabilities.
Only the main user can run the UI and gain root access.
Secondary user's apps will not be granted root, nor can
those users change SuperSU configuration.
This is all temporary. Proper multi-user support is being
worked on.
Note that if a non-user process (like ADB shell) needs to
prompt for root, that prompt will always appear on the
MAIN user's screen !