[APP] Superuser 2.3.6.1 - Now on the Market [2010-09-05]

Search This thread

madt24

New member
Apr 4, 2010
2
0
Tried flashing using SPRecovery and it failed, anybody else having issues using SPRecovery? At work or would look into it further.
 

ristafas

New member
Aug 18, 2009
2
0
SU 2.3 not in app list

Just installed 2.3ef for my Nexus One running CM5.0.8 and its allowing root access for my apps that need it but it force closes when I try and open it from the app drawer. Ive flashed it 3 times now and made sure the hashes matched. It doesnt show up on any uninstall apps or in Menu>Settings>Applications. I wanted to try clearing the cache from there but its MIA. Any thoughts? Thanks
 
G

Geochelone

Guest
I like the new UI.

Anyway, I'm having force closes when clicking Log. Attached is the logcat.

Code:
E/AndroidRuntime( 1265): FATAL EXCEPTION: main
E/AndroidRuntime( 1265): java.lang.ArrayIndexOutOfBoundsException
E/AndroidRuntime( 1265):        at com.noshufou.android.su.LogActivity$LogAdapter.configurePinnedHeader(LogActivity.java:271)
E/AndroidRuntime( 1265):        at com.noshufou.android.su.PinnedHeaderListView.configureHeaderView(PinnedHeaderListView.java:143)
E/AndroidRuntime( 1265):        at com.noshufou.android.su.LogActivity$LogAdapter.onScroll(LogActivity.java:230)
E/AndroidRuntime( 1265):        at android.widget.AbsListView.invokeOnItemScrollListener(AbsListView.java:675)
E/AndroidRuntime( 1265):        at android.widget.ListView.layoutChildren(ListView.java:1660)
E/AndroidRuntime( 1265):        at android.widget.AbsListView.onLayout(AbsListView.java:1147)
E/AndroidRuntime( 1265):        at com.noshufou.android.su.PinnedHeaderListView.onLayout(PinnedHeaderListView.java:123)
E/AndroidRuntime( 1265):        at android.view.View.layout(View.java:7035)
E/AndroidRuntime( 1265):        at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1249)
E/AndroidRuntime( 1265):        at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1125)
E/AndroidRuntime( 1265):        at android.widget.LinearLayout.onLayout(LinearLayout.java:1042)
E/AndroidRuntime( 1265):        at android.view.View.layout(View.java:7035)
E/AndroidRuntime( 1265):        at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1265):        at android.view.View.layout(View.java:7035)
E/AndroidRuntime( 1265):        at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1265):        at android.view.View.layout(View.java:7035)
E/AndroidRuntime( 1265):        at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1265):        at android.view.View.layout(View.java:7035)
E/AndroidRuntime( 1265):        at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1249)
E/AndroidRuntime( 1265):        at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1125)
E/AndroidRuntime( 1265):        at android.widget.LinearLayout.onLayout(LinearLayout.java:1042)
E/AndroidRuntime( 1265):        at android.view.View.layout(View.java:7035)
E/AndroidRuntime( 1265):        at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1265):        at android.view.View.layout(View.java:7035)
E/AndroidRuntime( 1265):        at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1265):        at android.view.View.layout(View.java:7035)
E/AndroidRuntime( 1265):        at android.widget.FrameLayout.onLayout(FrameLayout.java:333)
E/AndroidRuntime( 1265):        at android.view.View.layout(View.java:7035)
E/AndroidRuntime( 1265):        at android.view.ViewRoot.performTraversals(ViewRoot.java:1045)
E/AndroidRuntime( 1265):        at android.view.ViewRoot.handleMessage(ViewRoot.java:1727)
E/AndroidRuntime( 1265):        at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1265):        at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 1265):        at android.app.ActivityThread.main(ActivityThread.java:4627)
E/AndroidRuntime( 1265):        at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1265):        at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 1265):        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
E/AndroidRuntime( 1265):        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
E/AndroidRuntime( 1265):        at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager(  512):   Force finishing activity com.noshufou.android.su/.Su
W/ActivityManager(  512): Activity pause timeout for HistoryRecord{43efc2a0 com.noshufou.android.su/.Su}
 

flibblesan

Senior Member
Feb 12, 2008
472
203
Nottingham
Nothing Phone 1
App is force closing for me also. Huawei Pulse, Android 2.1

Code:
08-11 01:35:00.673: DEBUG/Su.AppListActivity(2322): onResume()
08-11 01:35:00.683: WARN/dalvikvm(2322): threadid=3: thread exiting with uncaught exception (group=0x40026268)
08-11 01:35:00.683: ERROR/AndroidRuntime(2322): Uncaught handler: thread main exiting due to uncaught exception
08-11 01:35:00.703: ERROR/AndroidRuntime(2322): java.lang.RuntimeException: Unable to resume activity {com.noshufou.android.su/com.noshufou.android.su.Su}: java.lang.RuntimeException: Unable to resume activity {com.noshufou.android.su/com.noshufou.android.su.AppListActivity}: java.lang.IllegalArgumentException: column '_id' does not exist
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2950)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:2965)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2516)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.app.ActivityThread.access$2200(ActivityThread.java:119)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1863)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.os.Handler.dispatchMessage(Handler.java:99)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.os.Looper.loop(Looper.java:123)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.app.ActivityThread.main(ActivityThread.java:4363)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at java.lang.reflect.Method.invokeNative(Native Method)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at java.lang.reflect.Method.invoke(Method.java:521)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at dalvik.system.NativeStart.main(Native Method)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322): Caused by: java.lang.RuntimeException: Unable to resume activity {com.noshufou.android.su/com.noshufou.android.su.AppListActivity}: java.lang.IllegalArgumentException: column '_id' does not exist
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2950)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.app.LocalActivityManager.moveToState(LocalActivityManager.java:170)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.app.LocalActivityManager.dispatchResume(LocalActivityManager.java:518)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.app.ActivityGroup.onResume(ActivityGroup.java:58)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1149)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.app.Activity.performResume(Activity.java:3763)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2937)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     ... 12 more
08-11 01:35:00.703: ERROR/AndroidRuntime(2322): Caused by: java.lang.IllegalArgumentException: column '_id' does not exist
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.database.AbstractCursor.getColumnIndexOrThrow(AbstractCursor.java:314)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.widget.CursorAdapter.changeCursor(CursorAdapter.java:257)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at com.noshufou.android.su.AppListActivity.refreshList(AppListActivity.java:143)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at com.noshufou.android.su.AppListActivity.onResume(AppListActivity.java:87)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1149)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.app.Activity.performResume(Activity.java:3763)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2937)
08-11 01:35:00.703: ERROR/AndroidRuntime(2322):     ... 18 more
08-11 01:35:00.883: INFO/DumpStateReceiver(1242): Added state dump to 1 crashes

I still have superuser for apps that had it granted already and it will grant su for new apps that need it (tested with root explorer). But launching the superuser app itself force closes.

Edit: I've removed all traces to the superuser from packages.xml and removed the folder from /data/data/ incase the script in the update.zip didn't run right, but it's made no difference. Update was flashed using Clockworkmod Recovery 2.5.0.4
 
Last edited:

antikryst

Senior Member
May 18, 2010
173
10
Quezon City
Extract system/app/Superuser.apk and system/xbin/su from the proper update.zip for your firmware and install it with the following adb commands.

Code:
adb remount
adb push Superuser.apk /system/app
adb push su /system/xbin
adb shell chmod 06755 /system/xbin/su
adb reboot

If you're not comfortable with this method, wait for the fix.

would it be the same commands if i were to push 2.3 manually? stock rooted froyo here with locked bootloader. thanks.
 

j_r0dd

Senior Member
Jun 9, 2009
806
287
Last house on the block
i even built it from source and included it my full rom. i did a full wipe and re-flash and it still FC's on my Cliq running 2.1 when I try to open the Superuser app. But when I try this on my N1 running froyo the app opens just fine. The one common thing I am picking up here is everybody with the FC's has a HVGA device.

here is what catches my eye
Code:
08-10 21:47:13.620: ERROR/AndroidRuntime(995): java.lang.RuntimeException: Unable to resume activity {com.noshufou.android.su/com.noshufou.android.su.Su}: java.lang.RuntimeException: Unable to resume activity {com.noshufou.android.su/com.noshufou.android.su.AppListActivity}: java.lang.IllegalArgumentException: column '_id' does not exist
 
Last edited:

XBrav

Senior Member
Feb 16, 2010
197
20
Calgary
Love the new prompts. But yes, FC'd on opening.

HTC Dream, CM 5.0.8.

Phone does seem faster though now with it!
 

MotoCache1

Senior Member
Aug 10, 2010
62
32
Tried flashing using SPRecovery and it failed, anybody else having issues using SPRecovery? At work or would look into it further.

Failed for me too when flashing using SPRecovery. Seeing all the problems folks are having with it, I'm glad it failed. I'm going to hang back and watch for now and see how everything sorts out.
 

FHL09

Senior Member
Dec 4, 2009
67
3
34
Hawkes Bay
www.fhl09.wordpress.com
Forcecloses

ChainsDD

Hey man, 2.3 Cupcake/Donut Forcecloses on start-up it won't even open any advice?

I've attached a log for reference.

Device: HTC Magic 32B
ROM: Dwang 1.17.1
 

Attachments

  • alogcat.2010-08-12-00-01-02+1200.txt
    3.3 KB · Views: 18

ghidda

Senior Member
Feb 1, 2009
139
8
Installed!
Before update need remove the old version ;)

Sent from my X10i using XDA App
 

tcsheen

Member
Sep 15, 2009
34
0
FC

CDMA Hero running Fresh 2.1.2
FC on opening, and of course FC on anything requiring super user.
Can't remember if my ROM had SuperUser...
Also, don't know how to get log, but thought id post on it

**EDIT** - I let it sit for a few minutes, literally, did nothing to the device for about 5 minutes. Then when I tried accessing su via Terminal Emulator (first few times it FCd) and it worked! Voila!
Tried a few other programs that were FC-ing and the popup for access came up every time. Not sure what I did, or didn't do, but it is working -
Although accessing SuperUser via LauncherPro drawer is still causing FC on SU, not sure I care anymore now that it is working...whew, forgot the nandroid this one time, oi.
 
Last edited:

buenso80

Senior Member
Jun 14, 2010
336
18
OnePlus 5T
OnePlus 8T
ver. 2.3 doesn´t work on froyo aosp 1.1 tattoo??? it´s starting up when trying to add an app but is just counting down from 10 and loops? No add or ok key?

maybe it´s something with the screen resolution???

help!!

News: Tried to wipe cache and reinstall. Now I can´t even install .zip(zip corrupted)
Tried to download and install -no-fixsuperm-signed.zip and it installs butsadly FC :-(
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 118
    Code:
    #include <std_disclaimer.h>
    /*
     * Your warranty is now void.
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at me for messing up your device, I will laugh at you.
     */

    I got tired of the old, quite unreadable, Superuser app that's being used in most every build, so I refreshed it entirely. Some of the new features include:

    - Each permission is shown by it's name, rather than it's UID
    - Many translations (Spanish, German, Czech, Greek, French, Italian, Dutch, Russian and Danish (Some are full translations, some are only partial))
    - Optional notifications
    - A dialog that shows details of each permission
    - Full logging system
    - A much clearer request window.
    - Permissions are removed when an app is uninstalled to prevent another app from possibly getting permissions you don't want it to have.
    - A bunch of work behind the scenes to smooth things out.
    (New for 2.2)
    - Changed requests to a broadcast intent to prevent app murder.
    - Using new permission scheme for better security
    - Fixed several database leaks.
    - Version display for app and binary in preferences.
    (New for 2.2.1)
    - Install fixed. Will clear old permissions, but it's the last time I'll delete your permissions.
    - Fixed AndroidManifest to allow install on cupcake.
    - Russian translation thanks to stari4ek
    (New for 2.2.2)
    - Install really fixed this time thanks to a trick little shell script in the update.zip
    (New for 2.3)
    - New layout of main app
    - Full logging
    - New request layout
    - Fixed boot/widget bug
    - Date/time format options
    - Better notification system
    - New icon
    - Better allow system
    - A whole mess of code cleanup
    - Rearranged drawables so that only one apk needs to be built for any firmware
    (New for 2.3.1)
    - Big bugfixes
    - Better support for landscape mode
    - better support for ldpi devices
    (New for 2.3.2.1)
    - Now lives in the market!
    - Bugfixes
    (New for 2.3.3)
    - More bugfixes
    - App can now update it's own binary without using update.zip
    (New for 2.3.4)
    - App downloads binaries if necessary
    - Entry in Settings to check for updated binaries
    (New for 2.3.5)
    - Better handling of su binary versions (Thanks ATomCZ)
    - Polish translation (Thanks Piter1225)
    - Fixed bug that prevented Apps from showing up if they didn't have a log entry
    - Added Clear Log button to preferences
    - Added a check to ensure that no other apps are trying to respond to Superuser requests
    (New for 2.3.6.1)
    - Traditional & Simplified Chinese translations
    - Updated French & Greek translations
    - Added clear log button to menu on log screen
    - Bugfixes

    And the best news, CM6 Stable users can update pain free from the market!

    There are 2 versions, one for cupcake/donut, one for eclair/froyo. Pick the one appropriate for your firmware and flash via recovery mode.

    su-2.3.6.1-cd-signed.zip
    md5: e1abb445d770075f49edc8810aa80758
    - Cupcake/Donut

    su-2.3.6.1-ef-signed.zip
    md5: 6d490575092a1c5d91af56b94c2328f4
    - Eclair/Froyo

    Or download from the market:

    If install from the market fails, use adb to issue these commands:
    Code:
    adb remount
    adb shell rm /system/app/Superuser.apk
    adb shell pm uninstall com.noshufou.android.su
    or from terminal:
    Code:
    $ su
    # (remount for your phone, Nexus One is 'mount -o remount,rw /dev/block/mtdblock3 /system', other phones will use the same pattern, but may vary on the '/dev...' bit)
    # rm /system/app/Superuser.apk
    # pm uninstall com.noshufou.android.su
    # (same remount command as above, but with 'remount,ro' instead of 'remount,rw')
    After that, you'll be able to install Superuser from the market.

    Special thanks go out to MotoCache1 for keeping this thread under control and repackaging the update.zip to work on more phones, velazcod for his huge help with this release, Zinx for the su app this is based off of, Cyanogen and koush for their help and support, Fnorder for motivating me to finally fix the allow system properly, bartito, sacarino2k2, thiasB, RedVirus, regunus, leonnib4, Eug89, MrSnowflake, MarkM83 and stari4ek for translations, and whoever it was that wrote fix_permissions for the help writing fixsuperm.

    I make no guarantee that this will work on your particular setup, but I will try to help get it working. There's also the community that can help. Post your questions with logs here in the thread and we'll try to get you an answer. If your phone bursts into a ball of flame, I can't help at all.

    If you have any issues, please post them to the issue tracker on my github. It'll make them easier to keep track of.

    Note: You will have to re-authorize any apps you want to have permission, unless you are already (successfully) running a 2.2 or higher version.

    Note: I don't have a phone to test the cupcake/donut version on, should work no problem tho. Please let me know if there are any problems.

    Note: Apps may still crash if they try to get permissions on boot that have not been granted yet. Once an app is in the whitelist, it should have no trouble at all getting permissions on boot.

    As always, source is located at my github in my sig.
    33
    Glad you like it. Sorry to keep you waiting so long... :eek:

    Thanks for pointing out that you have to re-allow everything. I forgot to mention that. I'll put it up in the OP.
    21
    ChainsDD: Weird. Coming from Cm5.0.7 I didn't have to re-allow anything. However, your previous releases (from the older thread) indeed made me re-allow everything :p.

    Only those people that haven't been running 2.0 will have to re-allow everything. This one uses the same database as in 2.0.

    Did not work on a HTC dream with Cyanogen test 5 i flashed both eclair versions with the same end result

    there is a superuser app in the tray but does not ask for permission Eg. SetCPU ask's if i have root and terminal says $ su: symbolic link loop

    any ideas?

    You'll want to use su-2.1-e-signed.zip. I've seen the symbolic loop before on an older cm5.0.7test. Try flashing 5.0.7test5, booting fully, booting into recovery and then flashing su-2.1. If that doesn't work, push the su binary from the zip to /system/xbin and it should fix it.

    hi,
    has su 2.1 the ability to set the su shell in order to forze the use of bash or other?

    command line: su -s /system/bin/bash

    i have reported this issue in the 2.0.3 thread.

    Agree!

    I'll look into adding this.

    i have got a milestone too and replace it but dont see it. which one have you taken? i have 2.1 rooted.

    What ROM are you using?
    8
    Bump for latest version. See OP
    8
    Try reflashing, get me a logcat if you can.