Ah skipped over the fact u had a pulse. Gotta read more carefully next time. So its working perfectly for u ? all root requiring apps work fine ?
[APP] Superuser 2.3.6.1 - Now on the Market [2010-09-05]
- Thread starter ChainsDD
- Start date
Ah skipped over the fact u had a pulse. Gotta read more carefully next time. So its working perfectly for u ? all root requiring apps work fine ?
how to install SUperuser 2.2.1
Hey guys, quick question
I have the old SUperuser prog on my Nexus one, but i cant recall how I installed it...
MY question is, how do I install this new Chains DD's Superuser 2.2.1 on my nexus?
DO I just simply use the "Flash zip from SD card" option from AMon Ra's recovery rom?
SOmebody please let me know if it's that easy..THx
Hey guys, quick question
I have the old SUperuser prog on my Nexus one, but i cant recall how I installed it...
MY question is, how do I install this new Chains DD's Superuser 2.2.1 on my nexus?
DO I just simply use the "Flash zip from SD card" option from AMon Ra's recovery rom?
SOmebody please let me know if it's that easy..THx
Probably won't work as advertised, working on a solution for that right now
I have to go to bed. Will get the install issue worked out tomorrow. In the mean time you can still upgrade to the latest version manually.
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.
If you're not comfortable with this method, wait for the fix.
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 rebootIf you're not comfortable with this method, wait for the fix.
Psst, I'm still a UNIX n00b. I understand the three-digit chmod notation now - one digit for users, one for groups, one for others. What's the significance of four or five digits?
hi, i have used this method, and it seemed to work (showed me the push result (XXkb), and no error on adb shell chmod, but when I open superuser app and look at the version number it still says 2.2
is that correct?
I did the commands it said, I see the new icon, and when I press 'Menu', it shows the prefrences, but when I click it, it freezes the app.
This is on a liberated Aria, no errors in adb. Using this file su-2.2.1-ef-signed.zip
This is on a liberated Aria, no errors in adb. Using this file su-2.2.1-ef-signed.zip
I got it to install, but only through extracting the .apk from the .zip in astro. I couldn't get it to flash from recovery. And even though the application opens it still says I have no root access. I am running CM 5.0.8-DS.
I'm not really sure what the first digit is for (I got the chmod line from a cyanogenmod update.zip), the second digit is so that the binary runs at the permissions of it's owner (root in this case), and the last three are standard permission codes.
Fixed that, try 2.2.2.
I forgot to include the instruction for creating the symlink in /system/bin. That might cause the problem.
You're welcome!
Apk version 2.2 up require a new su binary, it's in the update.zip under system/xbin, and that file requires certain permissions. AFIK it's only possible to set those through terminal or adb.
All that aside, 2.2.2 is up in the OP. I created a shell script that should fix the problems people have been having with installing this. If we're still having issues, it's gonna be either: a) the script didn't run properly because of your recovery image, or b) a new issue entirely.
Enjoy!
If you find a bug, please give me a detailed bug report including logs and phone/rom.
Okay... How do I go about installing this? I won't work through recovery and I don't know how to adb (I would like to learn though, but not now) and when I install the .apk from the .zip it doesn't give me root permissions. HELP PLEASE!
I still get status 0 when flashing 
Heres the log. Im running 1.7 amonra recovery on a htc magic 32a.
Gonna try removing update-script and resigning and flashing.
Heres the log. Im running 1.7 amonra recovery on a htc magic 32a.
Code:
Install from sdcard...
Finding update package...
I:Update location: SDCARD:abc123.zip
Opening update package...
I:Update file path: /sdcard/abc123.zip
Verifying update package...
I:Verified META-INF/CERT.RSA
I:Verified META-INF/MANIFEST.MF
I:Verified META-INF/com/google/android/update-script
I:Verified META-INF/com/google/android/updater-script
I:Verified fixsuperm
I:Verified system/app/Superuser.apk
I:Verified META-INF/com/google/android/update-binary
I:Verified system/xbin/su
Installing update...
E:Error in /sdcard/abc123.zip
(Status 0)
Installation aborted.
C:\Users\Danesh>Gonna try removing update-script and resigning and flashing.
Last edited:
Need more info. What happens when you flash via recovery? What phone and recovery are you using?
I am using a mt3g running CM 5.0.8-DS. When I try to flash from recovery is says:
E:Error in /sdcard/su-2.2.2-ef-signed.zip
(Status 0)
Installation aborted.
and I'm running Cyanogenmod Recovery
I currently do not an older version of Superuser installed. Idon't think that means anything, but I'm not sure.
Which update.zip? ef or cd?
Those of you using the magics, I believe I fixed your problem. Try this updated version, make sure you've rebooted recovery before flashing it.
http://bit.ly/su222cd
http://bit.ly/su222ef
http://bit.ly/su222cd
http://bit.ly/su222ef
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
118Code:
#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:
or from terminal:Code:adb remount adb shell rm /system/app/Superuser.apk adb shell pm uninstall com.noshufou.android.su
After that, you'll be able to install Superuser from the market.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')
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.21ChainsDD: 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.
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.
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.
I'll look into adding this.
What ROM are you using?
