In my case I used the 2.1 unsigned. Went into my OpenRecovery 1.05 directory on my sdcard and replaced the su and superuser.apk files in the root directory with the included ones from the download. Rebooted into recovery, ran update.zip to get into openrecovery and ran root again.
[APP] Superuser 2.3.6.1 - Now on the Market [2010-09-05]
- Thread starter ChainsDD
- Start date
wiped and reflashed Cyan 5 +google apps
full boot + reboot to recovery
in recovery flash 2.1-e-signed
same error
when attempting to push via adb i get this
$ adb push /su-2.1-e-signed/system/xbin/su /system/xbin/su
failed to copy /su-2.1-e-signed/system/xbin/su to /system/xbin/su: Too many symbolic links encountered
:S
edit: wiped/flashed cy then adb pushed su it went through but there is no difference to how it was
gonna try pushing the apk see if that helps
EDIT EDIT: yup push all the files in the zip via adb and it worked perfectly man i love adb and fastboot
full boot + reboot to recovery
in recovery flash 2.1-e-signed
same error
when attempting to push via adb i get this
$ adb push /su-2.1-e-signed/system/xbin/su /system/xbin/su
failed to copy /su-2.1-e-signed/system/xbin/su to /system/xbin/su: Too many symbolic links encountered
:S
edit: wiped/flashed cy then adb pushed su it went through but there is no difference to how it was
gonna try pushing the apk see if that helps
EDIT EDIT: yup push all the files in the zip via adb and it worked perfectly man i love adb and fastboot
Last edited:
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.
So I'm ....................................................
I'm not sure if this is a bug report or a lesson learned, but here goes:
Due to commit "Perform all database interactions in the apk." (c23cf), if an activity requests su, the activity's onResume() is always called. Prior to c23cf onResume() was only called after the permission window showed up.
This means activities cannot (easily) call su in their onResume (like to update the view in case while it was paused you allowed/revoked their su privileges) without causing an infinite loop.
In retrospect, it was bad for me to do this originally as even prior to c23cf if the user didn't check "always allow" they would still have an infinite loop.
I'm looking into it a bit deeper as I'm curious.
Due to commit "Perform all database interactions in the apk." (c23cf), if an activity requests su, the activity's onResume() is always called. Prior to c23cf onResume() was only called after the permission window showed up.
This means activities cannot (easily) call su in their onResume (like to update the view in case while it was paused you allowed/revoked their su privileges) without causing an infinite loop.
In retrospect, it was bad for me to do this originally as even prior to c23cf if the user didn't check "always allow" they would still have an infinite loop.
I'm looking into it a bit deeper as I'm curious.
Last edited:
Worked Perfect On Sprint Hero with DC 2.08.1
Nice work guys. I love the improved interface. In the past the su requests we're always pretty slow to show up on my Hero, but this new version popped up right away as soon as I did an su request in terminal. Good Job!
For those with a Sprint Hero using DC's rom, the su-2.1-e-signed.zip worked perfect on the first shot.
Nice work guys. I love the improved interface. In the past the su requests we're always pretty slow to show up on my Hero, but this new version popped up right away as soon as I did an su request in terminal. Good Job!
For those with a Sprint Hero using DC's rom, the su-2.1-e-signed.zip worked perfect on the first shot.
**EDIT**
Son of a biscuit, I should be using the Eclair version - DOH!
Tried both Signed and Unsigned version for Cupcake on my G1 (ROM in Sig) by running the zip from Recovery Console. Super User app opens, but when I try to run an app that requires SU such as Wireless tether I am not prompted and Wireless Tether says it cannot start.
Tried to manually install via ADB:
adb push su /system/bin
adb push superuser.apk /system/app
both were successful in pushing the files the the destination, but still I am not ever prompted when opening\starting apps that require su.
Any ideas?
Son of a biscuit, I should be using the Eclair version - DOH!
Tried both Signed and Unsigned version for Cupcake on my G1 (ROM in Sig) by running the zip from Recovery Console. Super User app opens, but when I try to run an app that requires SU such as Wireless tether I am not prompted and Wireless Tether says it cannot start.
Tried to manually install via ADB:
adb push su /system/bin
adb push superuser.apk /system/app
both were successful in pushing the files the the destination, but still I am not ever prompted when opening\starting apps that require su.
Any ideas?
Last edited:
**UPDATE**
Changed to the Eclair version, both Signed and Unsigned. Only difference now is that when I open either Wired or Wireless Tether to test I get a warning the I don't have root access.
Changed to the Eclair version, both Signed and Unsigned. Only difference now is that when I open either Wired or Wireless Tether to test I get a warning the I don't have root access.
Last edited:
Works fine on my Milestone (better than the "old crappy one"). Gonna use it with the next release of Open Recovery.
Is there any possibility that this new su will work on data/bin/su and superuser.apk on data/app/superuser.apk? I use an Archos 5IT and the system partion is still secured but we have been getting root on data partition.
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?
New posts
-
-
Development [ROM][14][OFFICIAL][STABLE] [ProjectBLaze] [raven][15-04-2024]- Latest: Prabhat_Proxy
